tech-invite   World Map
3GPP     Specs     Glossaries     UICC       T+       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TR 22.802 (SA1)
Study on scenarios where multiple APNs are needed

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V14.0.0    2015/06    19 p.


Rapporteur:  Mr. Macchi, Ilario
See also:  MTC-related TS/TR    


In the visionary future of Connected Life, it is foreseen that enhancements are needed to facilitate provisioning of all attributes necessary for providing the connectivity to the machine to machine UEs in the area of Health, Education, Automotive and Smart Cities. It is seen as important to provide an operator added value to connectivity services as well as ease of use for MTC subscribers.

One particular aspect of the PS Domain connectivity in 3GPP system is that a correct APN is required to establish a PDN Connection. Solutions exist where a list of APNs for different MNOs is stored in the Mobile Equipment (ME), but this places a management overhead on either the ME supplier or current Home Operator to keep such list up-to-date in the ME. For a truly global MTC Module that would mean that it have to contain and maintain a list of over 1000 different APNs to satisfy all markets. Even to cover a local geographic region, such as Europe, several hundred different APNs would need to be preloaded and maintained.

For MTC service the ME (i.e. telematics module) is often a very generic module whereas the machine to machine application is usually very specific and can often require the use of a specific dedicated APN. In the case of APN provided by the UE in PDN Connection establishment then the MNO may be forced to perform device management to the ME or perform SIM-OTA provisioning to the UICC.

The correct APN to be used depends on the MNO subscription identified by the IMSI and thereby the USIM. The correct APN may also depend on the particular application unless a multiservice APN is used. APN may also be used to identify a MTC UE for the purpose of MTC roaming SLAs. Emergency APN is needed for emergency services but such APN is provided by the network when a UE is requesting an Emergency PDN connection.

The scope of this study is:
  • to provide details about the use cases where there is a need of control of APNs;
  • to identify potential new requirements to fulfil the use cases;
  • to identify potential solutions to fulfil the use cases;
The scope of the study is focussed on Machine-To-Machine UEs but can take into account a more generic set of UEs.

This study will identify what connectivity use-cases that are needed to be fulfilled, and study if multiple APN or a multi-purpose APN per subscription (IMSI) combined with other 3GPP specified features can support those connectivity use-cases. The study will also analyse the impacts in scenarios where the service provider decides to change the MNO.


 

Here        Top

 

 

1   Scope   Word-p. 5
2   References
3   Definitions, symbols and abbreviations   Word-p. 6
4   Use cases
5   Conclusions
A   Change history   Word-p. 18

Up        Top