Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 24.524  Word version:  16.0.0

Top   Top   None   None   Next
1…   5…

 

1  ScopeWord‑p. 5
The present document describes the architecture and functionality required to support enterprise and corporate services as IMS applications hosted in the NGN operator's network on behalf of an enterprise (Hosted Enterprise Services).
The present document also specifies the protocol requirements for the UE to attach to the NGN (in particular the IMS) and also any protocol requirements related to application servers provided in support of hosted enterprise services.

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]
ETSI ES 282 001 (V3.4.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1".
[2]
ETSI ES 282 007 (V2.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture".
[3]
ETSI TS 182 012 (V2.1.4): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Subsystem; Functional architecture".
[4]
ETSI ETS 300 738 (First edition): "Human Factors (HF); Minimum Man-Machine Interface (MMI) to public network based supplementary services".
[5]
TS 23.228: "Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2".
[6]
TS 23.167: "Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS) emergency sessions".
[7]
TS 33.203: "Technical Specification Group Services and System Aspects; 3G Security; Access security for IP-based services".
[8]  Void.
[9]
RFC 3323  (December 2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[10]
RFC 3325  (December 2002): "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks".
[11]
Void.
[12]
ETSI ES 282 002 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Subsystem (PES); Functional Architecture".
[13]
TS 32.260: "Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; IP Multimedia Subsystem (IMS) charging".
[14]
TS 22.519: "Technical Specification Group Services and System Aspects; Business communication requirements".
[15]
TS 24.229: "Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[16]
ETSI TS 183 043 (V3.4.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS based PSTN/ISDN Emulation Stage 3 specification".
[17]
TS 24.628: "Technical Specification Group Core Network and Terminals; Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[18]  Void.
[19]
RFC 5031  (January 2008): "A Uniform Resource Name (URN) for Emergency and Other Well-Known Services".
[20]
TS 24.611: "Technical Specification Group Core Network and Terminals; Anonymous Communication Rejection (ACR) and Communication Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[21]
RFC 3966  (December 2004): "The tel URI for Telephone Numbers".
[22]
RFC 3261  (July 2002): "SIP: Session Initiation Protocol".
[23]
RFC 4967  (July 2007): "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier".
[24]
RFC 7316  (July 2014): "The Session Initiation Protocol (SIP) P Private-Network-Indication Private-Header (P-Header)".
Up

3  Definitions, symbols and abbreviationsWord‑p. 6

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TS 22.519, TS 24.229 and ETSI TS 183 043 [16] apply:

3.2  Abbreviations

For the purposes of the present document, the following abbreviations apply:
AGCF
Access Gateway Control Function
AGF
Access Gateway Function
AS
Application Server
BGCF
Breakout Gateway Control Function
BGF
Border Gateway Function
CNGCF
Customer Network Gateway Configuration Function
CS
Circuit Switched
CSCF
Call Session Control Function
HES
Hosted Enterprise Services
I-BGF
Interconnection-Border Gateway Function
I-CSCF
Interrogating-Call Session Control Function
IFC
Initial filter Criteria
IMS
IP Multimedia Subsystem
IN
Intelligent Network
IP
Internet Protocol
IPCAN
IP Connectivity Access Network
ISC
IMS Service Control
ISDN
Integrated Services Digital Network
LDAP
Lightweight Directory Access Protocol
MGCF
Media Gateway Control Function
MGF
Media Gateway Function
MRFC
Multimedia Resource Function Controller
MRFP
Multimedia Resource Function Processor
NASS
Network Attachment SubSystem
NGCN
Next Generation Corportate Network
NGN
Next Generation Network
NGN
Next Generation Network
P-CSCF
Proxy-Call Session Control Function
PES
PSTN/ISDN Emulation Subsystem
PSTN
Public Switched Telephony Network
RACS
Resource and Admission Control Subsystem
RG
Residential Gateway
SCP
Service Control Functio
S-CSCF
Serving-Call Session Control Function
SGF
Signalling Gateway Function
SIP
Session Initiation Protocol
SLF
Subscription Locator Function
SPDF
Service-based Policy Decision Function
T-MGF
Trunking-Media Gateway Function
UE
User Equipment
UEE
User Equipment Emulation
UPSF
User Profile Server Function
URI
Uniform Resource Identifier
URN
Uniform Resource Name
VGW
Voice over IP Gateway
Up

4  OverviewWord‑p. 7
Hosted Enterprise Services (HES) refers to a solution where an NGN hosts all business communication capabilities to a set of endpoints connected to a plurality of access points to this network. This type of network solution is also known as IP Centrex.
In the simplest configuration all endpoints are connected to a TISPAN NGN IP-CAN. Endpoints may be SIP phones or legacy phones (Analogue or ISDN) connected to a gateway. All services by HES are provided by application servers using standard IMS procedures. User may access services that are specific to the enterprise they belong to as well as services available to any other IMS users.
In more complex configurations some of the endpoints may be connected to a 3GPP IPCAN and/or a circuit-switched network, which is itself connected to the IMS via an MGCF. Endpoints connected to heterogeneous access networks may be served by the same HES.
Endpoints served by a HES shall have the ability to setup a session, identifying the communication target by:
  • a SIP URI of the form user @domain;
  • an E.164 telephone number;
  • a number within a private numbering plan;
  • local service numbers.
With regard to supplementary services, HES have strong similarities with the provision of PSTN/ISDN simulation services, although the actual set of services may be different. Examples of services that are enabled by the architecture described in the present document are:
  • All commonly used PSTN/ISDN services.
  • IMS Multimedia Messaging, Presence and Conferencing services.
  • Personal and Corporate Directory.
  • Unified Voice mail.
  • Operator assisted communications.
  • Hot Line Calling.
  • Abbreviate dialling.
  • Line Hunting.
  • Attended Communication Transfer.
  • Blind Communication Transfer.
  • Communication Pickup.
  • Manager/Secretary filtering.
  • Click to Dial.
  • Colour Ring Back Tone.
The sole purpose of the above list of services is to illustrate the type of services that are enabled by the architecture described in the present document. This list is not intended to be exhaustive nor is it expected that all implementations will support all of these services. The list actual of enterprise services hosted in a network is a matter for each operator to decide.
Up

Up   Top   ToC