This solution requires the addition of a new feature to allow the storage and use of multiple APNs in the USIM. This new feature has the following impacts:

• Enhanced ME and existing UICC based solution:
• ME only. Thus, this UICC based solution is not applicable to legacy MEs but is applicable to legacy USIM.
• Enhanced ME and enhanced UICC based solution:
• ME, UICC application and the ME - USIM interface. Thus, the UICC based solution is not applicable to legacy USIM and legacy MEs.

This new feature has no impacts on the Radio Access Network and Core Network. Standard OTA platforms can be reused to update the list of APNs and any additional information/fields, thus the UICC based solutions do not require any upgrade in legacy OTA platforms. When considering the use case "Provisioning of an International M2M service for a Business Customer", as soon as the subscription-swap operation has been completed successfully, the APN connectivity information and any additional information/fields (e.g. SMS) are immediately available without requiring a second step configuration (because APN and SMS info are part of the updated USIM application in the UICC profile). The following considerations apply to the "Automotive" UICC-based solution described in clause 4.1.5.1:

The matrix of service needs and end point devices is increasing, as illustrated in Figure 1. In this context, the advantage of a device management based solution can be seen as creating a clean buffer between heterogeneous device spread and a demanding service layer in the operator's network. The device management based solution provides the ability to handle multiple varieties of devices through a set of uniform service interfaces towards the service management layer. The device management layer also buffers the service management layer from the effect of multiple, and increasing, trust relationships in the network. Those relationships include:

• between the UICC and the service provider (e.g., automobile manufacturer)
• between the UICC and the network operator, and
• between the UICC and the device (e.g., embedded or via a connection to a UE).

In terms of enterprise and bulk service needs from M2M services, multi-tenancy can be handled seamlessly at the device management layer. Since the M2M devices and corresponding technologies are new and are expected to undergo rapid deployment to new zones, it is all the more essential to segregate different segments to restrict widespread changes in the deployed network elements for overall execution of M2M services and support. The EU has recently approved ending roaming charges and enabling swapping into any service provider's data connectivity.

• The "Connected Continent" telecoms Regulation was proposed by the Commission in September 2013. It aims to bring us much closer to a truly single market for telecoms in the EU, by ending roaming charges, guaranteeing an open internet for all by banning blocking and degrading of content, coordinating spectrum licensing for wireless broadband, giving internet and broadband customers more transparency in their contracts, and making it easier for customers to switch providers.
• Ensures safeguard of installed entities and complete automation by
  • Receiving new subscriber's and easier management of APNs/services
  • Protection of APNs and easier controls during subscriber's churn
  • Easy management during bulk, multi-tenancy and enterprise related operations

The OMA-DM server initiated bootstrap component of the device management based solution is similar to the network based solution, with the exception that the action in the device is taken on management objects rather than files.

Regarding the automotive use case in clause 4.1, it is concluded that the various connectivity requirements of this use case can be achieved using a single APN with the legacy mechanisms documented in clause 4.1.5.3 of this TR. Network based solution in this TR is based on legacy features in both the network and the UE, which means that there are no introduction problems with respect to number of supporting UEs on the market. The network based solution offer a standard solution for configuration for the operator by using network provided APN. This removes the need to keep large lists of APNs for different MNOs stored in the UE, which was part of the problem description provided by GSMA Connected Living and summarized in the introduction clause of this TR. Due to the availability of the variety of mechanisms documented in clause 4.1.5.3 of this TR, it is concluded that the various connectivity requirements of the automotive use case in clause 4.1 can be achieved using only one APN. It is also concluded that in the case that, if only one application is used at any given time, the various connectivity requirements of the automotive use case in clause 4.1 can be achieved using multiple APNs. The automotive use case use case states in clause 4.1.2 that "All the applications can be active at the same time". Due to restrictions present in all higher layer operating systems at the time of the preparation of this report, only one APN can be active at any given time. Therefore it is concluded that in the case that more than one application being used at any given time, the various connectivity requirements of the automotive use case in clause 4.1 can only be achieved using a single APN.

The considerations for this solution are mainly the same as for the UICC based solution with the following additional:

• This solution reuse OMA DM already defined management objects relative to the APNs
• The OMA DM defined ConnMO need be updated for LTE by OMA.
• OMA DM bootstrap from the UICC is already defined.
• This solution can be used without an OMA DM server.
• This solution uses the OTA server to update the APN information stored in the UICC.
• The solution does not impact OMA DM specifications.
• The solution does not impact 3GPP specifications.
• Some backward compatibility issues could be envisaged.