4.10 System enhancements for the use of ims services in local breakout (saes-ims_lbo) uid_390039

Resources: S2

References

Document	Title/Contents
WID(s)
SP-080090	SA2 WID on System enhancements for the use of IMS services through local breakout
Impacted Specifications
TS 23.228, 23.221, 23.203	S2
New Dedicated Specifications/Reports
-	-

UID	Name	Resource	Hyperlink	TS_TR
390039	System enhancements for the use of IMS services in local breakout	S2	SP-080090	23.228, 23.221, 23.203

IMS services, like voice and video conferencing, can greatly benefit of Local BreakOut (LBO). This allows reducing cost per bit of data traffic exchanged by roaming customers, since at least part of it can be handled directly by the visited operator, with no need to waste bandwidth on the international links between the home and visited PLMNs. Moreover, LBO offers better performance to the customers, since the locally routed traffic faces lower delays.

The work introduces system enhancements for LBO into Stage 2 specifications, under the assumption that IMS signalling and IMS bearer traffic are both anchored at a PDN GW in the VPLMN. In particular it identified:

• solutions for the home Operator to control whether the IMS user may access to IMS services through a PDN in the VPLMN;

• solutions to allow the UE to establish connectivity to a single PDN GW in the VPLMN and use IMS services through local breakout;

• if methods are necessary to discover a P-CSCF in the VPLMN or in the HPLMN, after the UE has connected to the visited PDN GW;

• requirements for the connectivity between the PDNs and/or interactions with network entities such as NAT (as specified in TS 23.228);

• interactions with and support of PCC;

• legal intercept implications.

4.11 Epc Data Definitions (epc-oam) uid_390010

Resources: S5

The EPC Data Definitions Building Block of the SAES Feature covers several independent Work Tasks as follows:

• EPC Network Resource Model (NRM) Integration Reference Point (IRP)

• Performance measurements for EPC

EPC Network Resource Model (NRM) Integration Reference Point (IRP) UID_380037

References

Document	Title/Contents
WID(s)
SP-070737	WID on EPC Network Resource Model (NRM) Integration Reference Point (IRP)
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TS 32.751	Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
TS 32.752	Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)
TS 32.753	Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
TS 32.755	Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition

UID	Name	Resource	Hyperlink	TS_TR
380037	EPC Network Resource Model (NRM) Integration Reference Point (IRP)	S5	SP-070737	new (32.751, 32.752, 32.753, 32.755)

The Evolved Packet Core (EPC) is defined by 3GPP with different Network Elements from the UTMS Core Network. The Network Resource Model (NRM) of the UTMS Core Network is not applicable to EPC.

The EPC system needs to be managed. 3GPP network management paradigm necessitates the standardization of the representations of various managed resources. The standardization of the EPC system managed resources is captured in the so-called EPC Network Resource Model (NRM).

The EPC architecture and capabilities evolve from those defined for UTMS Core Network. The management of the EPC system should also evolve from that for managing the UTMS Core Network. In particular, the NRM for EPC should align and resemble those specified for the Core managed network resources.

The alignment of EPC NRM with Core NRM will have the following benefits:

• The system architecture of EPC evolves from Core network and the existing Core network NRM is proven in operation. Therefore, the alignment will result in a specification that has a higher chance of being bug free when compared to a "brand new" designed specification.

• It will minimise both the standardisation and product development efforts and maintenance efforts (i.e. the cost and time for development including testing and reduction of training cost when the management paradigms for EPC and Core network remained similar);

• It will shorten the time to market for EPC systems;

• It will facilitate a seamless coexistence with Core network management systems.

TS 32.75x-series define the EPC NRM IRP using the same principles as for the UMTS Core network NRM. It has identical characteristics as those defined for other NRMs such as UMTS Core network NRM. The DN of its instances uses the same name convention as all instances, whose IOCs are defined in various NRM IRPs. Its IOCs integrate identically with other NRM (e.g. UMTS/GSM NRM IRP) with the IOCs defined in Generic NRM IRP. Operations and notifications defined in various Interface IRPs that work with existing instances of various NRM IRPs work without change with the new instances of EPC.

Similar to existing 3GPP NRM IRPs such as UTRAN and Core Network NRM IRP, the EPC NRM IRP focuses only on the representation of the network resources in question. It does not deal with the applications or usage of the IOCs.

This work defines the NRM for EPC, e.g. MME, HSS, Serving GW, PDN GW.

Performance measurements for EPC UID_390011