7.5 Ims System enhancements for corporate network access (ims_Corp) uid_360012

Resources: S2,S1,C1,C4,IETF

References

Document	Title/Contents
WID(s)
SP-080095	S1 WID on IMS System enhancements for corporate network access
CP-080220	C1 WID on IMS protocol enhancements for corporate network access
Impacted Specifications
TS 23.003	Numbering, addressing and identification (C4) Identities associated with business communication
TS 23.008	Organization of subscriber data (C4) Enhancements to HSS for business communication
TS 23.228	IP Multimedia Subsystem (IMS); Stage 2 (S2) Changes to fulfil requirements for access to corporate network
TS 24.229	Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (C1) Enhancements to SIP in order to support business communications
TS 24.503	TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] (C1)
TS 29.228	IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents (C4) Enhancements to Cx protocol to support wildcarded public user identities and any issue with PNP numbers
TS 29.229	Cx and Dx interfaces based on the Diameter protocol; Protocol details (C4) Enhancements to Cx protocol to support wildcarded public user identities and any issue with PNP numbers
TS 29.433	TISPAN; IP Multimedia; Diameter based protocol for the interfaces between the Call Session Control Function and the User Profile Server Function/Subscription Locator Function; Signalling flows and protocol details [3GPP TS 29.228 and 29.229 modified] (C4)
New Dedicated Specifications/Reports
-	-

Supporting Individual Members: Telecom Italia, Alcatel-Lucent, Ericsson, Orange, Telenor, TeliaSonera, NSN, RIM.

UID	Name	Hyperlink	Rapporteur	Notes	TS_TR
390049	SA1 aspects	SP-080095	Telecom Italia	SP#40 completed	-
360014	SA2 aspects	SP-080095	Orange	no Stage 2 impacts	23.228
390022	CT1 aspects	CP-080220	Alcatel-Lucent	CP#47 completed	24.229, 24.503
531002	(IETF) CT1	CP-080220	Keith Drage	CP#65 completed	RFC 7316 (was draft-vanelburg-dispatch-private-network-ind)
390023	CT4 aspects	CP-080220	Alcatel-Lucent	CP#42 completed	29.228, 29.229, 23.003, 23.008, 29.433

The standardization of fixed broadband access to IMS is addressed by a number of SDOs, e.g. ETSI and ITU-T in the framework of NGN. A set of enhancements to the IMS has already been implemented in Rel-7 based on TISPAN Rel-1 requirements. There is a need to capture new requirements from the industry for IMS in 3GPP Rel-8, especially to support requirements coming from TISPAN R2. One of these requirements is to support corporate, private and residential network access to IMS.

This work implements necessary enhancements to IMS within 3GPP to fulfil this new requirement. It covers IMS architectural enhancements necessary in the 3GPP system to support the access to IMS from e.g. corporate, private, residential networks. One of the scenarios required to be supported is the connection of a corporate network to IMS, where the corporate network has an IMS subscription and the users of the corporate network are owned and managed by the corporate network.

CT WGs work

There is a need to capture enhancements to IMS covering corporate network access. Business communication is covered by ETSI TISPAN, which defines only the Next Generation Corporate Network (NGCN) and AS aspects, and potentially the configuration issues of an IMS providing such business communication. Common IMS is defined by 3GPP, and any required modifications to IMS should therefore be covered within appropriate 3GPP specifications.

The SA1 parent feature (SP-080095) also mentions residential networks. Extension of this CT WGs work item to cover access to IMS by residential networks is for further study.

This work provides IMS protocol enhancements in the 3GPP system supporting the access to IMS from NGCNs. (scenarios are covered by ETSI TISPAN in DTS/TISPAN-02040). Such extensions to core IMS include:

• distinction of private network traffic from public network traffic, and any special handling of the signalling associated with such distinguished private network traffic by the core IMS, e.g. identity, emergency calls

• protocol issues wildcarded public user identities

• support of PNP numbers

• extension of trust domains to include the NGCN

• support of complex equipment on customer's premises, i.e. the end device is no longer a SIP UA as seen from IMS