|
TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
LTE;
Business communication requirements
(3GPP TS 22.519 version 15.0.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 1 ETSI TS 122 519 V15.0.0 (2018-07)
Reference
RTS/TSGS-0122519vf00
Keywords
LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.
© ETSI 2018.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 2 ETSI TS 122 519 V15.0.0 (2018-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
---------------------- Page: 3 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 3 ETSI TS 122 519 V15.0.0 (2018-07)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
4 Capabilities for the support of IP multimedia services. 8
4.1 General . 8
4.1.1 Types of traffic . 8
4.1.2 Business communication capabilities . 9
4.1.3 Business models . 9
4.1.4 Number, naming and addressing . 10
4.1.5 Identification of session originator and terminator . 11
4.1.6 Charging and accounting requirements. 11
4.1.7 Regulatory requirements . 11
4.1.7.1 Lawful intercept . 11
4.1.7.2 Emergency service . 12
4.1.7.3 Identifying malicious communications . 12
4.1.7.4 Anonymous communications rejection . 12
4.1.8 Mobility . 12
4.1.8.1 Roaming . 12
4.1.9 Routing requirements . 13
4.1.9.1 Routing to a NGCN user . 13
4.1.9.2 number range based routing . 13
4.1.10 Communication admission control . 13
4.1.11 Geographical location . 13
4.2 NGN/NGCN interconnection requirements . 13
4.2.1 NGCN site identifier . 13
4.2.2 Corporate network user identifier . 14
4.2.3 Authentication and security requirements . 14
4.3 Specific requirements for hosted enterprise services . 14
4.3.1 Security requirements for hosted enterprise services . 14
4.3.2 Capabilities provided to a HES user . 14
4.3.3 Capabilities provided to the enterprise. 14
4.3.3.1 Break-in . 14
4.3.3.2 Break-out . 14
4.4 Specific requirements for business trunking application . 15
4.4.1 Routeing capabilities. 15
4.4.1.1 Overview . 15
4.4.1.2 Break-in . 15
4.4.1.3 Break-out . 15
4.4.1.4 Bulk rerouting . 15
4.4.2 Communication barring . 16
5 PSTN/ISDN emulation service . . 16
6 Codecs services . 16
7 Network attachment requirements . 16
7.1 General . 16
7.2 Specific requirements for virtual leased line . 16
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 4 ETSI TS 122 519 V15.0.0 (2018-07)
7.2.1 Security requirements for virtual leased line . 16
8 CPE configuration . 16
9 Control of processing overload . 16
10 IP addressing . 16
11 NGN interconnection . 17
12 Transport stratum . 17
12.1 NGN/NGCN interconnection requirements . 17
12.1.1 Redundancy support . 17
12.2 Specific requirements for virtual leased line . 17
Annex A (informative): Change history . 18
History . 19
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 5 ETSI TS 122 519 V15.0.0 (2018-07)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
The present document is structured in a similar manner to ETSI TS 181 005 [2] and the main clause numbering from
this point in the document onwards therefore follows that document, with the scope of those clauses also following that
of ETSI TS 181 005 [2].
As well as the interconnection of NGCN equipment to the NGN, the NGN can be used to host various business
communication capabilities on behalf of an enterprise. These are:
a) virtual leased line, where NGCN sites are interconnected through the NGN;
b) business trunking application, where the NGN hosts transit capabilities between NGCNs, break-in capabilities
from NGN to NGCN and break-out capabilities from NGCN to NGN; and
c) hosted enterprise services, where an NGN hosts originating and/or terminating business communication
capabilities for business communication users that are directly attached to an NGN.
These hosted capabilities may be hosted using the different capabilities described in different clauses in
ETSI TS 181 005 [2] and therefore where appropriate the various clauses of the present document are broken up to
further describe interconnection requirements, and these various hosted capabilities, as follows:
x.1 General;
x.2 NGN/NGCN interconnection requirements;
x.3 Specific requirements for hosted enterprise services;
x.4 Specific requirements for business trunking application; and
x.5 Specific requirements for virtual leased line.
This structure has been followed in 3GPP TS 22.519, even though 3GPP TS 22.228 [6] (the equivalent specification) is
structured in a different manner.
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 6 ETSI TS 122 519 V15.0.0 (2018-07)
1 Scope
The present document specifies network requirements:
- to support connection and interoperation of business communication capabilities (either hosted in NGCN or
NGN) to the NGN; and
- to support connection and interoperation of business communication capabilities to other business
communication capabilities (either hosted in NGCN or NGN); and
- to support connection and interoperation of business communication capabilities to other business
communication capabilities located in or connected to the ISDN and PSTN; and
- to support PABX functionality (hosted enterprise services) in an NGN.
NOTE 1: Network requirements to support connection of NGCN directly connected to an NGN are specified.
NOTE 2: Attachment of legacy PBX functionality to the NGN is not specified in the present document. It is
assumed that existing legacy service requirements apply in this case.
The present document also specifies network requirements for communication between NGCN capabilities (including
user equipment) to other NGCN capabilities of the same enterprise through the NGN (e.g. geographically separated).
The present document does not specify NGCN services, nor does it specify network based application services provided
to a user of an NGCN.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] Recommendation ITU-T E.164: "The international public telecommunication numbering plan".
[2] ETSI TS 181 005 (V1.1.1): "Telecommunications and Internet converged Services and Protocols
for Advanced Networking (TISPAN); Services and Capabilities Requirements".
[3] 3GPP TS 33.203: "3G security; Access security for IP-based services".
[4] 3GPP TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".
[5] ISO/IEC 11571: "Information technology - Telecommunications and information exchange
between systems - Private Integrated Services Networks - Addressing".
[6] 3GPP TS 22.228: "Service requirements for the Internet Protocol (IP) multimedia core network
subsystem (IMS); Stage 1".
[7] ETSI TR 102 478 (V1.1.1): "Corporate telecommunication Networks (CN); Enterprise
communication involving Next Generation carrier Networks (NGN)".
[8] 3GPP TS 22.115: "Service aspects; Charging and billing".
[9] 3GPP TS 33.106: "3G security; Lawful interception requirements".
[10] 3GPP TR 21.905: " Vocabulary for 3GPP Specifications".
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 7 ETSI TS 122 519 V15.0.0 (2018-07)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [10] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [10].
business communication: any communication that is either:
• originated in an NGCN; or
• terminated in an NGCN; or
• originated in the NGN on behalf of an enterprise; or
• terminated in the NGN on behalf of an enterprise;
and which is subject to special arrangements between the NGN operator and the enterprise
business communication capabilities: any capability whether hosted in an NGCN or an NGN that enables and/or
enriches Business Communication
NOTE: Business Trunking, Hosted Enterprise Services and Virtual Leased Line are examples of business
communication capabilities hosted in NGN.
Business Trunking (BT): connection of an NGCN to an NGN
business trunking application: NGN application that either provides transit capabilities between NGCNs, or, break-in
capabilities from NGN to NGCN and/or break-out capabilities from NGCN to NGN
NOTE: A business trunking application may also provide additional services beyond basic breakin, breakout and
transit capabilities to the NGCN.
corporate network user identifier: identifies a corporate network user on communications entering, leaving or
transiting the NGN, either representing an originating corporate network user or as a globally routable target identity
Corporate telecommunication Network (CN): sets of enterprise premises equipment, owned by or managed on behalf
of an enterprise that are located at geographically dispersed locations and are interconnected to provide
telecommunication services to a defined group of users belonging to that enterprise
enterprise: unit of economic organization or activity, especially a business organization
Hosted Enterprise Services (HES): NGN application whereby the NGN hosts all originating and/or terminating
business communication capabilities for enterprise users that are directly attached to NGN and have an IMS
service subscription for this application in the NGN
Next Generation CN (NGCN): self-contained corporate network designed to take advantage of emerging IP-based
communications solutions and that can have its own applications and service provisioning
NOTE 1: For the purpose of the present document it is a corporate network that provides an IP-based interface to an
NGN.
NOTE 2: TR 102 478 [7] uses NGCN to collectively refer to IP-PBXs.
NGCN site: separate part of an NGCN
NOTE: An NGCN site might represent a part of an NGCN bound to a specific geographic location. When an
NGCN site serves more than one geographic location then all locations served by that NGCN site would
have access to an NGN concerned via the NGCN site's connectivity arrangement with that NGN.
Communication between different NGCN sites belonging to the same NGCN can but need not pass
through their respective NGN(s). For example, such communications might be routed by the NGN(s) only
during periods of high traffic or equipment outage within the NGCN. An NGCN site can have access to
its NGN either directly or via some other NGN that provides a transit capability. An NGCN can have
NGCN Sites in different countries.
ETSI
---------------------- Page: 8 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 8 ETSI TS 122 519 V15.0.0 (2018-07)
NGCN identifier: identifier by which an NGCN is known to an NGN with which it has a connectivity arrangement
public network traffic: traffic sent to or received from an NGN for processing according to the normal NGN rules
private network traffic: traffic sent to or received from an NGN for processing according to an agreed set of rules
specific to an enterprise or a community of closely related enterprises
Private Numbering Plan (PNP): numbering plan explicitly relating to a particular private numbering domain, defined
by the PISN Administrator of that domain
NOTE 1: See ISO/IEC 11571 [5].
NOTE 2: Terminology used in this definition and in relation to this term used in the text is as defined in
ISO/IEC 11571 [5]. For the purposes of the present document a PISN and a NGCN can be regarded as
equivalent.
PNP number: number belonging to a PNP
NOTE: See ISO/IEC 11571 [5].
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BT Business Trunking
CAC Communication Admission Control
CN Corporate telecommunication Network
HES Hosted Enterprise Services
IMS IP Multimedia core network Subsystem
IP Internet Protocol
NGCN Next Generation Corporate Network
NGN Next Generation Network
PBX Private Branch Exchange
PNP Private Numbering Plan
PSAP Public Safety Answering Point
SLA Service-Level Agreement
TIP Termination Identity Interface
UE User Equipment
UNI User to Network Interface
4 Capabilities for the support of IP multimedia services
4.1 General
4.1.1 Types of traffic
The traffic generated or received on behalf of an NGCN can be either:
1) traffic sent to the NGN for processing according to normal rules of the NGN. This type of traffic is known as
public network traffic;
2) traffic sent to the NGN for processing according to an agreed set of rules specific to an enterprise. This type of
traffic is known as private network traffic. Private network traffic is normally within a single enterprise, but
private network traffic can also exist between two different enterprises if not precluded for regulatory reasons.
NOTE: An enterprise network may separately distinguish private network calls that originate in the NGN from
private network calls that originate in the enterprise; this does not form part of the present document.
The NGN shall distinguish public network traffic from private network traffic. The NGN shall distinguish private
network traffic belonging to one enterprise from that belonging to another enterprise.
Private network traffic may require different handling in the NGN compared to public network traffic, see for example
clause 4.1.7 on regulatory requirements.
ETSI
---------------------- Page: 9 ----------------------
3GPP TS 22.519 version 15.0.0 Release 15 9 ETSI TS 122 519 V15.0.0 (2018-07)
Except between closely-related enterprises where regulations permit, the NGN shall treat traffic between enterprises as
public network traffic. In such cases, as part of the capabilities provided to the enterprise, the NGN can provide break-
out and/or break-in capabilities on behalf of each enterprise.
For private network traffic the NGN shall be transparent to any extensions of the chosen signalling protocol, except
where there is a specific need for NGN intervention required to deliver the service requested by the enterprise customer.
4.1.2 Business communication capabilities
The NGN can provide the following capabilities to an enterprise:
a) virtual leased line, where NGCN sites are interconnected through the NGN. No additional capabilities are
provided by the NGN;
b) business trunking application, where the NGN hosts transit capabilities between NGCNs, break-in capabilities
from NGN to NGCN and break-out capabilities from NGCN to NGN. A business trunking application may
also host additional capabilities beyond basic break-in, break-out and transit capabilities to the NGCN.
Typically there is no corporate network terminal equipment connected directly to an NGN. The capabilities
provided are defined in clause 4.4;
c) hosted enterprise services, where an NGN hosts originating and/or terminating business communication
capabilities for business communication users that are directly attached to an NGN and have an IMS service
subscription for this application in this NGN. This is known commonly as IP-Centrex. The capabilities
provided are defined in clause 4.3.
NOTE: NGCNs will not necessarily use IMS in their support of session-based capabilities.
4.1.3 Business models
Additionally to the business domain relationships as specified in 3GPP TS 22.228 [6] the NGN shall support the
following business domain relationships:
a) NGCN to IMS relationship: NGCN is attached to an Access network that is connected to the NGN IMS with
which the NGCN has a service agreement as shown in figure 4.1, the relationship is with the home IMS.
Relationship a
NGN
Access network
NGCN Home IMS
Figure 4.1
b) NGCN to Access network relationship: NGCN is connected to an Access Network as shown in figure 4.2. The
relationships given in 3GPP TS 22.228 [6] would normally be sufficient to enable connectivity with the NGN,
providing there is a relationship between the NGCN and the IMS. Relationship b may be required in some
cases.
NGN
Relationship b
Access network Home IMS
NGCN
Figure 4.2
NOTE: The Access Networks to which the various NGCN sites are connected may belong to different operators.
The following business model relationship is shown as it plays a role in some scenarios. The present document assumes
the business relationships descri
...