hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.5 Emergency calls | Voice call continuity for emergency calls shall be applicable to dual radio and single radio UEs.
Voice call continuity of emergency calls shall only be performed when all the following conditions are met:
- the source network is IMS;
- the target network supports emergency calls;
- the user is moving out of coverage;
- the source and target network belong to the same operator;
- the target network supports voice call continuity. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.6 Charging | It shall be possible to indicate in the charging information that a VCC event has occurred (e.g., so that appropriate ratings can be applied for the CS and IMS parts of the continued voice call). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.7 VCC Activation | It shall be possible to activate VCC based on operator policies, taking into account any of the following:
- Radio conditions e.g. radio quality thresholds and related hysteresis
- Coverage availability e.g.: Always prefer I-WLAN, if certain SSID are available |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22 IMS Centralized Services | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.1 General | The ICS user shall receive both registered and unregistered services in a consistent manner when the user accesses IMS either via the CS or the PS domain (both of which can be supported by 3GPP access networks or non‑3GPP access networks). Support of UEs enhanced with ICS capability as well as UEs without ICS capability shall be possible.
NOTE: The impacts to support non-3GPP CS domains to support of ICS are outside the scope of 3GPP. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.2 Service Consistency | Subscribers shall have a consistent user experience regardless of the domain used, subject to the constraints of the UE and access network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.3 Service Continuity | ICS shall support service continuity between CS and PS domains (both of which can be supported by 3GPP access networks or non‑3GPP access networks), subject to the constraints of the UE and access networks.
Note : The impacts to support non 3GPP CS domains are outside the scope of 3GPP.
The service continuity shall include:
- Basic services
- Non mid-call services
- Mid-call services
The support of service continuity for fax and data (CS) media components is not required. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.4 IMS Services | The set of IMS services supported by ICS shall include at least the following, subject to the constraints of the UE and access networks:
- IMS Multimedia Telephony services, including:
- speech,
- video,
- fax,
- data (CS),
- Supplementary services defined within [40]; and
- Multimedia priority service.
- IMS emergency calls, including eCall.
NOTE: Other IMS hosted services supported by an operator or 3rd party may be supported. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 22.5 Roaming Support | An ICS user shall be able to receive full ICS support from the HPLMN while roaming in the VPLMN, subject to the constraints of the VPLMN (e.g. roaming agreements, operator policies).
The Home operator shall be able to control if the UE enhanced with ICS capability shall act without ICS capability while roaming. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23 CS IP interconnection requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.1 Introduction | CS IP interconnect represents the interconnection of MSC Server functionality between 2 CS networks over an underlying IP infrastructure. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.2 IP interconnect | The IP connection used for CS IP interconnect shall be generic such that it can support all combinations of core network interconnection. E.g. the IP interconnection shall be shared between the IMS interconnection and the CS IP interconnection.
It shall be possible to handle the inter-connection of all services over this generic IP interface. The handling of security and charging shall also be generic for all IP interconnect scenarios. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 23.3 MSC server interconnect | The following requirements apply at the interconnection point when two PLMNs are interconnected by means of IP transport technology for 2G and 3G CS services.
The system shall support the capability for CS service interoperability and interworking.
It shall be possible to apply operator defined policy at the interconnection point.
The system shall support the capability to control the session resources when two different network domains are connected that may have, for example, different IP addressing schemes.
The system shall support IP inter-connection between core networks either by direct connection or by using an intermediate carrier (e.g. GSMA IPX [43]).
The system shall support both bilateral interconnection between two carriers and multilateral interconnection (e.g. GSMA IPX [43]) by means of intermediate carrier.
The system shall support either
- transparent relay of the IP signalling and traffic;
- service aware interconnection
The system shall support codec negotiation across one or multiple interconnects to minimise transcoding (and preferably eliminate it) to provide the highest quality service to the user. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24 Service Alignment & Migration | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24.1 Introduction | Services can be offered to the users via different service domains, e.g. certain teleservices and supplementary services via CS or Multimedia Telephony and supplementary services via IMS. Especially for the supplementary services given below a strong relationship exists from the user's point of view. Therefore means shall be provided to enable a consistent user experience when changing from one service domain to the other.
The requirements in this clause are applicable during the migration to an ICS. The ability to synchronise the service settings will facilitate the migration from a CS to an IMS based network and will allow network operators maximum flexibility in their migration strategies. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 24.2 Alignment of supplementary services settings | Based on user preferences and if provisioned by the home operator the network shall automatically synchronise the parameter settings of the supplementary services listed in the following table:
Table 24.2-1: Alignment of supplementary services settings
CS Voice (TS11) Supplementary Services
Equivalent Multimedia Telephony Services in IMS domain
Service Behaviour Required
CLIP/CLIR
OIP/OIR
Consistency of presentation
CoLP/CoLR
TIP/TIR
Consistency of presentation
CNAP
OIP/OIR
Consistency of presentation
Call Forwarding
CDIV
Call forwarding/CDIV shall work consistently no matter which domain the user is in. The settings (e.g. forwarding numbers) shall remain the same across domains for all the parts of the service for which there is an equivalent.
Call Waiting
Communication Waiting
The busy state of the user shall be available to both domains so that this can be applied no matter from which domain an incoming call/communication originates. The activation status of Call Waiting and Communication Waiting shall be synchronised.
Call Hold
Communication HOLD
Any calls held in one domain shall remain held on moving to a different domain. It shall be possible to re-establish a call that was put on hold in another domain.
Multiparty
CONF
Any conference (multiparty) calls set up in one domain shall remain in force if any user moves to another domain.
Closed User Group
Closed User Group
Consistency required across domains
CCBS
CCBS
Consistency required across domains
Call Deflection
Defined in CDIV
Consistency required across domains
Explicit Call Transfer
ECommT
Consistency required across domains. The UE state (i.e. if busy or not) shall be available in both domains to ensure that this can be applied consistently.
Call Barring
Communication Barring
Call/ Communication Barring shall work consistently no matter which domain the user is in. The settings (i.e. barred numbers) shall remain the same across domains.
AoC
AoC
Consistent support across domains. If the user moves from one domain to the other during the communication, the AoC shall indicate the correct charge for the total duration of the communication.
The operator shall be able to provision the user with the possibility to define which of the above settings shall be synchronised automatically and which settings can exist independently of each other. E.g. a user might decide that the activation status of CLIP/OIP, CLIR/OIR, Call Waiting/Communication Waiting etc. is synchronised but that the call forwarding status and forwarded-to-number is different from the communication diversion settings and the diverted-to-party address.
If the synchronisation of supplementary services, which use the UE's busy state for invocation, is activated the busy state of the UE shall be available in both domains.
NOTE: The "user not reachable" or "user not logged in" conditions in the different domains are independent of each other. This means, e.g. not being registered in the IMS does not affect the invocation of CFNRc in the CS domain.
Synchronisation of settings means that the most recent changes which have been applied in one domain are propagated to the other domain.
There are certain circumstances under which the synchronisation will fail e.g. when a user inserts a SIP URI as diverted-to-party address in the IMS domain which has no Tel URI associated with it. In such a case there is no valid setting for the CS domain for this particular parameter and therefore the CS domain service setting shall remain unchanged. The user may receive a notification about the failure of the synchronisation procedure and its cause. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25 System optimisation for communication with specific characteristics | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.1 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.2 Numbering Resource Efficiency | The following optional requirement is intended to provide better numbering resource efficiency for UEs that only require packet switched services.
- A network operator shall be able to provide PS only subscriptions with or without assigning an MSISDN.
- Remote triggering shall be supported with or without assigning an MSISDN.
- Remote UE configuration shall be supported without the use of an MSISDN.
Note 1: Current remote UE configuration solutions (i.e. Device Management and Over-the-Air configuration) are mainly based on SMS, which assumes the use of MSISDNs.
Note 2: The requirements in this sub-clause apply to server-to-UE communication scenarios only. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.3 Network provided destination for uplink data | The Network Provided Destination for Uplink Data feature is intended for use when all data from a UE is to be directed to a network provided destination address.
- For uplink data communication, the network shall be able to direct all uplink PS data traffic to a network provided destination address.
NOTE: This feature may be used, for example, when all data from an electricity meter is sent to a server maintained by the network operator. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 25.4 PS only subscriptions | The system shall support subscriptions that only allow packet-based services and SMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26 Single Sign-On (SSO) Service | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1.1 Requirements for the UE | An SSO-capable UE shall support 3GPP SSO Authentication, without user intervention, based on Operator-controlled credentials.
An SSO-capable UE shall be able to initiate the SSO Service regardless of the access network technologies supported by the UE.
An SSO-capable UE that supports 3GPP access and non-3GPP access shall support transparency of the SSO Service from a user perspective during transitions between 3GPP access and non-3GPP access, whether or not the transition occurs during a data application session.
An SSO-capable UE may support a request for SSO Local User Authentication from a Data Application Provider or an Identity Provider to confirm the presence of the registered user of the data application. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 26.1.2 Requirements for a 3GPP SSO Service | The 3GPP SSO Service shall provide secure, seamless and transparent access to data applications for users of the SSO Service independent of the access network technology.
The 3GPP SSO Service shall be able to interwork with Identity Management (IdM) specifications (e.g., OpenID [51]).
The 3GPP SSO Service shall support 3GPP SSO Authentication based on Operator-controlled credentials and policies.
The 3GPP SSO Service may support negotiation and use of an agreed authentication method between the UE and the 3GPP SSO Identity Provider. The negotiation of an authentication method may be repeated each time the user accesses a DAP's service.
The 3GPP SSO Service may support mechanisms to ensure the presence of the registered user of the data application to satisfy policies of the Data Application Provider.
The 3GPP SSO Service shall be transparent from a user perspective when transitions occur between 3GPP access and non-3GPP access, whether or not the transition occurs during a data application session.
The 3GPP SSO Service shall be transparent from a user perspective when the user accesses a data application using an identity created through a 3rd Party SSO Identity Provider. The user shall be able to configure which 3rd party SSO identities are used with the 3GPP SSO Service.
26a User Identity
26a.1 Introduction
Identifying distinguished user identities of the user (provided by some external party or by the operator) in the operator network enables an operator to provide an enhanced user experience and optimized performance as well as to offer services to devices that are not part of a 3GPP network. The user to be identified could be an individual human user, using a UE with a certain subscription, or an application running on or connecting via a UE, or a device (“thing”) behind a gateway UE.
Network settings can be adapted and services offered to users according to their needs, independent of the subscription that is used to establish the connection. By acting as an identity provider, the operator can take additional information from the network into account to provide a higher level of security for the authentication of a user.
NOTE: The basic concept and relations of user identity management is described in TR 22.904 [61].
26a.2 Requirements
26a.2.1 User Identifiers and user authentication
The 3GPP system shall be able to provide User Identities with related User Identifiers for a user.
The User Identifier shall be independent of existing identifiers relating to subscription or device (e.g. IMSI, MSISDN, IMPI, IMPU, SUPI, GPSI, IMEI) and of other User Identifiers.
The User Identifier may be provided by some entity within the operator’s network or by a 3rd party.
The 3GPP system shall support to interwork with a 3rd party network entity for authentication of the User Identity.
The 3GPP system shall support to perform authentication of a User Identity regardless of the user's access, the user's UE and its HPLMN as well as the provider of the User Identifier.
The 3GPP network shall be able to provide a User Identifier for a non-3GPP device that is connected to the network via a UE that acts as a gateway.
The 3GPP network shall support to perform authentication of a User Identity used by devices that are connected via a UE that acts as a gateway.
The 3GPP system shall be able to take User Identity specific service settings and parameters into account when delivering a service.
A subscriber shall be able to link and unlink one or more user Identities with his 3GPP subscription.
The 3GPP system shall support user authentication with User Identifiers from devices that connect via the internet; the 3GPP system shall support secure provisioning of credentials to those devices to enable them to access the network and its services according to the 3GPP subscription that has been linked with the User Identity.
The 3GPP system shall support secure provisioning of credentials to a non-3GPP device connected via a gateway UE, whose User Identifier has been linked with the 3GPP subscription of the gateway UE, to enable the non-3GPP device to access the network and its services according to the linked 3GPP subscription when connected via non-3GPP access.
The 3GPP system shall be able to assess the level of confidence in the User Identity by taking into account information regarding the used mechanism for obtaining that User Identity (e.g. algorithms, key-length, time since last authentication), information from the network (e.g. UE or device in use, access technology, location).
The operator and the subscriber shall be able to restrict the number of simultaneously active User Identifiers per UE.
26a.2.2 Access to services
The 3GPP System shall support to authenticate a User Identity to a service with a User Identifier.
NOTE: The requirement applies to 3GPP services and non-3GPP services that are accessed via the 3GPP System
The 3GPP system shall be able to provide information to services concerning the level of confidence of the User Identity and authentication process.
A service shall be able to request the 3GPP network to only authenticate users to the service for which the association of the user with a User Identifier has been established according to specified authentication policies of the service.
When a user requests to access a service the 3GPP System shall support authentication of the User Identity with a User Identifier towards the service if the level of confidence for the correct association of a User Identity with a User Identifier complies to specified policies of the service.
The 3GPP network shall be able to take the User Profile into account when assigning a UE to a network slice, moving a UE from one network slice to another, and removing a UE from a network slice.
The 3GPP system shall support to allow a UE access to a slice based on successful User Identity authentication.
The 3GPP system shall support to deny a UE access to a slice based on unsuccessful User Identity authentication.
26a.2.3 User Identity Profile and its User Identities
The 3GPP system shall be able to store and update a User Profile for a user.
The User Profile shall include a User Identifier.
The User Profile may include one or more pieces of the following information:
- additional User Identifiers of the user's User Identities and potentially linked 3GPP subscriptions,
- used UEs (identified by their subscription and device identifiers),
- capabilities the used UEs support for authentication,
- information regarding authentication policies required by different services and slices to authenticate a user for access to these services or slices.
- User Identity specific service settings and parameters.
Those shall include network parameters (e.g. QoS parameters), IMS service settings (e.g. MMTEL supplementary services), SMS settings, and operator deployed service chain settings.
NOTE: the above requirement assumes SMS is used for communication to the user.
- User Identity specific network resources (e.g., network slice).
The user shall be able to activate, deactivate and suspend, i.e. temporarily deactivate, the use of the User Identifiers per device or UE and the associated settings in its user profile.
NOTE 1: Suspending (temporarily deactivating) a User Identifier on a UE could also be automatically performed by the device on behalf of the user after a period of inactivity of the user at that device. The time period of inactivity of the user at that device after which a device should suspend a User Identifier may depend on home operator policy.
NOTE 2: Re-activation of a suspended User Identifier on a UE where it was suspended could involve simplified authentication (e.g. using fingerprint) at the device.
Subject to operator policy the 3GPP system shall be able to update User Profile related to a User Identifier, according to the information shared by a trusted 3rd party.
The IMS service settings (e.g. corresponding to a particular IMPU) associated with the newly activated User Identifier should replace any previous IMS service settings associated with the previous active User Identifier. In particular, a user with the new active User Identifier should not be able to access IMS service with other IMS identities from the User Identity Profile that are not active.
26a.2.4 Operator requirements
The operator shall be able to enable or disable the use of a User Identifier in his network.
The 3GPP System shall support operators to act as User Identity provider and to authenticate users for accessing operator and non-operator deployed (i.e. external non-3GPP) services
The operator shall be able to set the boundaries within which the user specific settings are taken into account in his network. The operator shall be able to restrict the feature depending of the provider of the User Identifier, the roaming status of the UE, the service and its specific parameters.
The operator shall be able to set restrictions for devices accessing the network and its services via non-3GPP access with their User Identity linked to a 3GPP subscription. The 3GPP system shall support restrictions based on the User Identity provider, the roaming status of the linked 3GPP subscription, and the network service that is accessed.
The 3GPP system shall be able to support automatically suspending an active User Identity after a certain period of time of user inactivity, e.g. up to one hour, as configured by the operator.
The 3GPP system shall be able to support a fast re-activation for a suspended User Identity, based on MNOs’ configuration.
The 3GPP system shall enable a user to configure, within the boundaries set by the network operator, which services shall be available on a device where this user logs in using a User Identifier. These services include voice, video, and messaging including SMS.
26a.2.5 Privacy requirements
The 3GPP system shall protect the privacy of a user by transferring to a service only User Identity information that is necessary to provide the service and for which this user has consented to when registering for the service.
The 3GPP network shall be able to protect the privacy of a user when accessing the 3GPP services from a UE which is shared by multiple users.
Note: Privacy protection mechanisms could be UE implementation dependent, but this is out of scope of 3GPP. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27 User plane congestion management | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.1 Introduction | RAN user plane congestion, in the context of this clause, is considered to be downlink congestion that affects the user plane, which may last for a few seconds, a few minutes, or a few hours due to arrival of new active users, increase of communication intensity of existing users, the radio environment changing, the mobile user changing location, and other reasons, thus causing the capacity of RAN resources to transfer user data to be exceeded. A short-duration burst of user plane traffic should not be identified as RAN congestion. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.2 General | a) The network shall be able to detect RAN user plane congestion onset and abatement. Mechanisms to cope with RAN user plane congestions should be resilient to rapid changes in the level of congestion.
b) The network shall be able to identify whether or not an active UE is in a RAN user plane congested cell.
c) The network operator shall be able to configure or provision and enforce policy rules to best deal with RAN user plane congestion.
d) The system should react in a timely manner to manage a RAN user plane congestion situation, i.e. that the measures taken become effective to promptly help resolve the RAN user plane congestion.
e) The signalling overhead caused by RAN user plane congestion management solutions in the system shall be minimized.
f) The network shall be able to take into consideration the RAN user plane congestion status and the subscriber's profile when coping with traffic congestion. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.3 Prioritizing traffic | a) According to operator policy, during RAN user plane congestion the operator shall be able to select the communications which require preferential treatment and allocate sufficient resources for such communications in order to provide these services with appropriate service quality.
b) According to operator policy, the network shall be able to select specific users (e.g. heavy users, roaming users, etc.) and adjust the QoS of existing connections/flows and apply relevant policies to new connections/flows depending on the RAN user plane congestion status and the subscriber's profile.
Note 1: Preferably, connections/flows need to be adjusted such that the user experience is not negatively affected. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.4 Reducing traffic | a) Based on RAN congestion status and according to operator policy, the network shall be able to reduce the user plane traffic load (e.g. by compressing images or by adaptation for streaming applications) taking into account UE related information (e.g. UE capabilities, subscription).
b) The system shall be able to adjust the communication media parameters of real-time communications so that they consume less bandwidth. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 27.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28 RAN Sharing Enhancements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.1 General | RAN Sharing Enhancements allow multiple Participating Operators to share the resources of a single RAN according to agreed allocation schemes. The Shared RAN is provided by a Hosting RAN Operator which can be one of the Participating Operators.
The Shared RAN can be GERAN, UTRAN, E-UTRAN or NG-RAN as described below.
All the following requirements shall be subject to Hosting RAN Operator configuration. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2 Specific E-UTRAN and NG-RAN Sharing requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.1 Allocation of Shared E-UTRAN and NG-RAN resources | When E-UTRAN and NG-RAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting E-UTRAN/NG-RAN Operator.
The following requirements apply:
The Hosting E-UTRAN/NG-RAN Operator shall be able to specify the allocation of E-UTRAN/NG-RAN resources to each of the Participating Operators by the following:
a) static allocation, i.e. guaranteeing a minimum allocation and limiting to a maximum allocation,
b) static allocation for a specified period of time and/or specific cells/sectors,
c) first UE come first UE served allocation.
d) the type and number of 5G slices
Resources include both user plane and signalling plane. The Hosting E-UTRAN/NG-RAN Operator needs to be able to manage the sharing of the signalling traffic independently from that of the user traffic because signalling traffic and user traffic are not always directly related. For example for MTC devices, the signalling traffic volume can be high and the user traffic volume low whereas for downloading video, the signalling traffic is low and the user traffic is high.
The following requirements apply:
The management and allocation of resources of signalling traffic over the Shared E-UTRAN/NG-RAN shall be independent from the management and allocation of resources of the user traffic over the Shared E-UTRAN.
A Shared E-UTRAN/NG-RAN shall be capable of differentiating traffic associated with individual Participating Operators.
A Shared E-UTRAN/NG-RAN shall be able to conduct admission control based on the allocated E-UTRAN/NG-RAN resources for each Participating Operator.
A Hosting E-UTRAN/NG-RAN Operator shall be able to control resource usage taking into account the allocated E-UTRAN/NG-RAN resources for each Participating Operator. A means of monitoring the usage of resources shall be provided.
All shared E-UTRAN/NG-RAN capabilities offered by the Hosting E-UTRAN/NG-RAN Operator shall be individually available for use by each Participating Operator where this is possible.
The 3GPP System shall support a Shared RAN (E-UTRAN or NG-RAN) to cover a specific coverage area (e.g. from a complete network to a single cell, both outdoor and indoor).
The 3GPP System shall support service continuity for UEs that are moving between different Shared RANs or between a Shared RAN and a non-shared RAN. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.2 OA&M Access to the Shared E-UTRAN/NG-RAN | Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a shared E-UTRAN/NG-RAN. Information exchange involved in those operations need to be controlled by the Hosting E-UTRAN/NG-RAN Operator as to prevent disclosing them to other Participating Operators, be it for business, operational, or technical reasons.
The following requirements apply:
Selected OA&M capabilities for the Shared E-UTRAN/NG-RAN, under the control of the Hosting E- UTRAN Operator, shall be accessible by the Participating Operator's OA&M functions
This would allow, for example, the Participating Operator to do the following:
- test of communication path between the Participating Operator's network elements and the Shared E-UTRAN/NG-RAN,
- obtain fault reports,
- retrieve RAN resource usage information. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.3 Generation and retrieval of usage and accounting information | To facilitate interoperator accounting between Hosting E-UTRAN/NG-RAN Operator and Participating Operator the Hosting E-UTRAN/NG-RAN Operator needs to record E-UTRAN/NG-RAN resource usage by UEs of the Participating Operator.
The following requirements apply:
A Hosting E-UTRAN/NG-RAN Operator shall be able to collect events supporting the accounting of network resource usage separately for each Participating Operator. Collected events may be delivered to the subscriber's Participating Operator. This includes:
- start of service in the Shared E-UTRAN/NG-RAN for a UE of the Participating Operator,
- end of service in the Shared E-UTRAN/NG-RAN for a UE of the Participating Operator. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.4 MDT Collection | MDT data from a Participating Operator's customer UEs allow the Hosting E-UTRAN/NG-RAN Operator to be provided with performance measurements on his Shared E-UTRAN/NG-RAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
The following requirements apply:
When authorized by the Participating Operators, the Hosting E-UTRAN/NG-RAN Operator shall be able to collect MDT data of the Participating Operator's UEs connected through its E-UTRAN/NG-RAN.
NOTE: This functionality should also allow for the case where the Hosting E-UTRAN/NG-RAN Operator does not have an adjunct core network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.5 PWS support of Shared E-UTRAN/NG-RAN | A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of E-UTRAN/NG-RAN Sharing.
The following requirements apply:
The Shared E-UTRAN/NG-RAN shall be able to broadcast PWS messages originated from the core networks of all Participating Operators.
NOTE: Rel-11 design requires a shared PWS core. However, some regulatory obligations require a solution in which no common PWS core network entity is involved. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.6 Support for load balancing | Hosting E-UTRAN/NG-RAN Operators have the need to optimize E-UTRAN/NG-RAN resource usage within the shared E-UTRAN/NG-RAN for a particular coverage area. At the same time, the agreed shares of E-UTRAN/NG-RAN resources based on a single cell and sector for each Participating Operator need to be respected. Likewise, Participating Operators have the need to optimize their E-UTRAN/NG-RAN resource usage among shared and unshared E-UTRAN/NG-RAN for a particular coverage area.
The capability to perform load balancing on an individual Participating Operator's traffic basis within a shared E-UTRAN/NG-RAN shall be supported.
The capability to perform load balancing on the combined traffic of all the Participating Operators within a shared E-UTRAN/NG-RAN shall be supported.
The capability to perform load balancing between an individual Participating Operator's traffic within a shared E-UTRAN/NG-RAN and traffic in that Participating Operator's unshared E-UTRAN/NG-RAN where the shared and unshared E-UTRAN/NG-RAN coverage overlaps shall be supported.
NOTE: Load balancing capabilities are expected to take into account the allocation of resources to each Participating Operator and the load level for each Participating Operator to the extent possible, so that the principal objective to maximize throughput is not impacted.
If load balancing in a Shared E-UTRAN/NG-RAN is supported and if a Participating Operator’s EPC indicates overload to the Shared E-UTRAN/NG-RAN in order to mitigate the overload situation then overload mitigation measures shall have minimal impact on the communication between the Shared E-UTRAN/NG-RAN and other Participating Operators EPCs. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.2.7 Dynamic capacity negotiation | In situations where a need for additional, unplanned, E-UTRAN/NG-RAN capacity by a Participating Operator arises (e.g. in the case of big mass-events) the Shared E-UTRAN/NG-RAN can provide means to allocate available spare capacity to the Participating Operator. Based on service level agreement between the Hosting and Participating operator such allocation can be automated without human intervention.
The following requirements apply:
The Participating Operator shall be able to query and request spare capacity of the Shared E-UTRAN/NG-RAN, based on policies and without human intervention.
The Shared E-UTRAN/NG-RAN shall be able to allocate spare capacity to Participating Operator, based on policies and without human intervention. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3 Specific GERAN & UTRAN Sharing Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.1 Allocation of Shared GERAN or UTRAN Resources | When GERAN or UTRAN resources are shared they can be allocated unequally to the Participating Operators, depending on the planned or current needs of these operators and based on service agreements with the Hosting RAN Operator.
The following requirements apply:
The Hosting RAN Operator shall be able to specify the allocation of GERAN or UTRAN resources to each of the Participating Operators by the following:
a) static allocation, i.e. guaranteeing a minimum allocation and limiting to a maximum allocation,
b) static allocation for a specified period of time and/or specific cells/sectors,
c) first UE come first UE served allocation.
The management and allocation of resources of signalling traffic over the Shared GERAN or UTRAN shall be independent from the management and allocation of resources of the user traffic over the Shared GERAN or UTRAN.
A Shared GERAN or UTRAN shall be capable of differentiating traffic associated with individual Participating Operators and shall be able to limit QoS available for traffic of the UEs of a Participating Operator (e.g. “best effort” if not enough resources are available).
A Shared GERAN or UTRAN shall be able to conduct admission control based on the allocated GERAN or UTRAN resources for each Participating Operator with a margin of tolerance.
A Hosting RAN Operator shall be able to control resource usage taking into account the allocated GERAN or UTRAN resources for each Participating Operator. A means of monitoring the usage of resources shall be provided.
All Shared GERAN or UTRAN capabilities offered by the Hosting RAN Operator shall be individually available for use by each Participating Operator where this is possible.
A Hosting RAN shall be able to provide an indication to each Participating Operator of how much capacity they are allocated at any one time. Signalling and User traffic shall be separately identified.
The ability to allow a single RAN (GERAN or UTRAN) to be fully shared by a number of Participating Operators shall be provided. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.2 OA&M Access to the Shared GERAN or UTRAN | Each Participating Operator can have their own OA&M capabilities, which are used for monitoring and for selected operations in a Shared GERAN or UTRAN. Information exchange involved in those operations need to be controlled by the Hosting RAN Operator so as to prevent disclosing them to other Participating Operators, be it for business, operational, or technical reasons.
The following requirements apply:
Selected OA&M capabilities for the Shared GERAN or UTRAN, under the control of the Hosting RAN Operator, shall be accessible by the Participating Operator's OA&M functions
This would allow, for example, the Participating Operator to do the following:
- test of communication path between the Participating Operator's network elements and the Shared GERAN or UTRAN,
- obtain fault reports,
- retrieve GERAN or UTRAN resource usage information. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.3 Generation and retrieval of usage and accounting information | To facilitate inter-operator accounting between the Hosting RAN Operator and the Participating Operator, the Hosting RAN Operator needs to record GERAN or UTRAN resource usage by UEs of the Participating Operator.
The following requirements apply:
A Hosting RAN Operator shall be able to collect events supporting the accounting of network resource usage separately for each Participating Operator. Collected events may be delivered to the subscriber's Participating Operator. This includes:
- start of service in the Shared GERAN or UTRAN for a UE of the Participating Operator,
- end of service in the Shared GERAN or UTRAN for a UE of the Participating Operator. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.4 MDT Collection | MDT data from a Participating Operator's customer UEs allow the Hosting RAN Operator to be provided with performance measurements on his Shared GERAN or UTRAN. The Participating Operator is responsible for obtaining and retaining any required user consent related to privacy.
The following requirements apply:
When authorized by the Participating Operators, the Hosting RAN Operator shall be able to collect MDT data of the Participating Operator's UEs connected through its GERAN or UTRAN.
The Participating Operators shall be able to retrieve this data for their own subscribers from the Hosting RAN Operator.
NOTE: This functionality should also allow for the case where the Hosting RAN Operator does not have an adjunct core network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.5 PWS support of Shared GERAN or UTRAN | A Participating Operator potentially has regulatory obligations to initiate the broadcast of PWS messages regardless of GERAN or UTRAN Sharing.
The following requirements apply:
The Shared GERAN or UTRAN shall be able to broadcast PWS.
NOTE: The Hosting RAN Operator is responsible for the delivery of PWS messages to the UEs. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.6 Support for load balancing | Hosting RAN Operators need to optimise GERAN or UTRAN resource usage within the Shared GERAN or UTRAN for a particular coverage area while respecting the agreed resource shares for each Participating Operator. Similarly, Participating Operators need to optimise their GERAN or UTRAN resource usage between Shared and unshared GERAN or UTRAN for a particular coverage area.
The Hosting RAN Operator shall have the capability to balance the Signalling and User Traffic load individually for each Participating Operator within a Shared GERAN or UTRAN.
The capability to perform load balancing on the combined traffic of all the Participating Operators within a Shared GERAN or UTRAN shall be provided. The agreed shares of GERAN or UTRAN resources shall be maintained. Signalling and User traffic shall be managed independently.
The capability to perform load balancing between an individual Participating Operator's traffic within a Shared GERAN or UTRAN and traffic in that Participating Operator's unshared GERAN or UTRAN where the Shared and unshared GERAN or UTRAN coverage overlaps shall be supported.
The Hosting RAN Operator shall be able to balance the load across all Participating Operators. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 28.3.7 Dynamic capacity negotiation | The Participating Operator shall be able to request on-demand spare capacity of the Shared GERAN or UTRAN based on policies and without human intervention.
The Hosting RAN Operator shall be able to allocate spare on-demand capacity on the Shared GERAN or UTRAN to a Participating Operator, based on policies and without human intervention.
The Participating Operator shall be able to request the cancellation of granted on-demand capacity requests.
The Hosting RAN Operator shall be able to cancel a granted request based on a Participating Operator’s request or based on agreed policy.
The Hosting RAN Operator shall be able to change the amount shared by each Participating Operator based on traffic demand. A minimum capacity (that can be set) of the Hosting RAN shall be reserved for each Participating Operator that cannot be allocated to other Participating Operators. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29 Service exposure with 3rd party service providers | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29.1 General | The intention of service exposure is that, under the assumption of a service agreement between MNO and a 3rd party, the 3GPP Network allows a 3rd party service provider to benefit from network provided services and capabilities that are exposed by the PLMN. For example the 3GPP Core Network can exchange information with the 3rd party to optimize usage and management of 3GPP resources. A standardized exposure of network services/capabilities reduces the complexity of different 3rd parties to access different 3GPP network services and capabilities.
General requirements for service exposure with 3rd party service providers:
- The operator shall be able to provide to a 3rd party service provider secure and chargeable access to the exposed services/capabilities i.e. to authenticate, authorize and charge the 3rd party entities.
NOTE 1: This requirement can be implemented by the existing standardised API frameworks e.g. the OMA API framework.
- It shall be ensured that the 3GPP services/capabilities are not disclosed to unauthorised parties and that user privacy (avoid e.g. trackable and traceable identity information of the concerned UE) is maintained subject to user agreement, operator policy, service agreement between operator and 3rd party and regulation constraints.
- The network service/capability exposure should be generic enough to support different application needs. Exposed 3GPP services/capabilities may use functionalities from different network entities and different 3GPP interfaces |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 29.2 Exposed Services and capabilities | The 3GPP Core Network shall be able provide a standardized interface to enable exposure of the following services and capabilities to 3rd party service providers:
Support of 3rd party requested MTC Device triggering
- The 3GPP Core Network shall support a 3rd party service provider request to trigger a UE that is served by the 3rd party service provider, the request shall include:
- a trigger payload, to provide information to the application on the UE to e.g. trigger application related actions,
- a validity period.
NOTE 1: The 3GPP Network will attempt to deliver the trigger message to the UE until the validity period expires.
- The 3GPP Core Network shall support the 3rd party service provider to recall or replace a trigger message that it has previously submitted.
NOTE 2: The goal of device triggering is that the UE takes action based on the content of the trigger payload. This response can involve initiation of communication with an MTC Server of the 3rd party service provider. The UE can initiate communication immediately or later within the validity period.
Support of 3rd party interaction for 3GPP resource management for background data transfer:
- The 3GPP Core Network shall support a 3rd party service provider request for background data transfer for a set of UEs that are served by the 3rd party service provider, indicating:
- the desired time window for the data transfer,
- the volume of the data expected to be transferred in a geographic area TS 23.032 [56].
- Additionally, the 3rd party application server shall be able to indicate to the 3GPP System when the background data transfer (a) exceeds the agreed maximum data volume or (b) continues beyond the agreed time window or (c) happens outside the agreed areas – e.g. due to movement of individual UEs, whether this background data transfer:
- shall be stopped by the 3GPP Sytem or
- shall continue, possibly under a different charging regime.
- The 3GPP Core Network shall be able to inform the 3rd party service provider in one coordinated response, based on locally available information (e.g. congestion level) over the geographic area, about:
- one or more recommended time windows for the data transfer and
- for each time window the maximum aggregated bitrate for the set of UEs in the geographical area indicated by the 3rd party service provider.
- Additionally, the 3GPP Core Network shall be able to inform the 3rd party service provider about the charging policy that will be applied to the 3rd party service provider if the data are transferred within the recommended time window and if transmission rates stay below the limits of the respective maximum aggregated bitrate.
- The goal of providing the time window is to favour transfer of more traffic during non-busy hours and reason for providing the maximum aggregate bitrate is to spread out traffic during that time. The goal of multiple time windows is to allow the 3rd party provider to choose one appropriate time window based on its preference like the expected charging regime and bitrate.
Support of 3rd party interaction on information for predictable communication patterns of a UE:
- The 3GPP Core Network shall enable a 3rd party service provider to provide information about predictable communication patterns of individual UEs or groups of UEs that are served by this 3rd party service provider.
Such communication patterns may include:
- Time and traffic volume related patterns (e.g. repeating communication initiation intervals, desired ‘keep alive’ time of data sessions, average/maximum volume per data transmission, etc.).
- Location and Mobility related patterns (e.g. indication of stationary UEs, predictable trajectories of UEs, etc.).
- This information may be used by the 3GPP system to optimize resource usage.
Support of 3rd party requested session QoS and priority
- The 3GPP Core Network shall enable a 3rd party service provider to request setting up data sessions with specified QoS (e.g. low latency or jitter) and priority handling to a UE that is served by the 3rd party service provider.
Support of 3rd party requested broadcast
- The 3GPP Core Network shall enable a 3rd party service provider to request sending a broadcast message in a specified geographic area (as specified in TS 22.368 [52]) expecting to reach a group of devices that are served by the 3rd party service provider.
Informing the 3rd party about potential network issues
- The 3GPP Core Network shall be able to indicate to a 3rd party service provider when data transmissions have a risk of incapability to provide expected throughput and/or QoS in a specific area (e.g. due to forecasted high traffic load in that area). Additionally, an estimate may be given when the high traffic load is expected to be mitigated.
Informing the 3rd party about UE status
- The 3GPP Core Network shall be able to provide the following information about a UE that is served by the 3rd party service provider:
- Indication of the of the roaming status (i.e. Roaming and No Roaming) and the serving network, when the UE starts/stops roaming,
- Loss of connectivity of the UE,
- Change or loss of the association between the ME and the USIM,
- Communication failure events of the UE visible to the network (e.g. for troubleshooting).
- Reporting when the UE moves in/out of a geographic area that is indicated by the 3rd party,
- Reporting when the UE changes Routing Area / Tracking Area / Location Area / Cell.
- Reporting when the UE changes the status of 3GPP PS Data Off.
NOTE: The area indicated by a 3rd party service provider can be mapped to the area used in the 3GPP network, i.e. a list of LAs/RAs/TAs/cells. The 3rd party service provider can define a geographical area as shapes (e.g. polygons, circles) or civic addresses (streets, districts…) as referenced by OMA Presence API [53] e.g. defined by shape areas of IETF RFC-5491 [54] or by civic addresses defined in IETF RFC-5139 [55].
- The 3rd party service provider shall be able to request a one time reporting or reporting at defined times (e.g. regular intervals, certain pre-defined time points) on the number of UEs present in a certain area and the location of each UE as for a Location Based Service.
- Subject to user consent, operator policy and regulatory constraints, the user privacy shall be maintained when passing location information to a 3rd party service provider.
Informing the 3rd party about a UE’s connection properties
- The 3GPP Core Network shall be able to inform a 3rd party about a UE’s connection properties.
NOTE: Connection properties of a UE describe the average data rate range or non-absolute value (e.g. high, medium or low) that the UE is likely to be able to obtain at the current location. The connection properties can, for example, be generated from the UE’s RAT type the UE is currently attached to, the load conditions at its current location and/or other parameters.
Support for non-IP small data transfer with a 3rd party
- The 3GPP Core Network shall support a 3rd party for submiting a small amount of non-IP data for delivery to a UE.
- The 3GPP Core Network shall support a 3rd party application server for receiving a small amount of non-IP data delivered from a UE.
- The 3GPP Core Network shall support a 3rd party to configuring non-IP data delivery for a particular UE (e.g. destination address, maximum number of messages, duration for which configuration applies).
NOTE: The use of the Non-IP Data Delivery feature via Service Capability Exposure Function assumes that the UE has indicated support for ‘non-IP data transfer’ and in case the Service Capability Exposure Function is used there will be no user plane EPS bearer established. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30 Flexible Mobile Service Steering | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30.1 Introduction | In order to realize efficient and flexible mobile service steering in (S)Gi-LAN, the network operator uses information (e.g. user profile, network operator’s policies, RAT type, application characteristics) to define traffic steering policies. These policies are used to steer the subscriber’s traffic to appropriate enablers (e.g. NAT, antimalware, parental control, DDoS protection) in the (S)Gi-LAN.
The term (S)Gi-LAN used in the present document represents a system which is out of 3GPP scope. Corresponding term for the 5G network is N6-LAN.
For traffic steering to service functions in 5G network, enhancement beyond the service requirements below are defined in [59]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 30.2 General Requirements | The following requirements apply:
- The 3GPP Core Network shall be able to define and modify traffic steering policies that are used to steer traffic in (S)Gi-LAN containing operator or 3rd party service functions e.g. to improve e.g. the user’s QoE, apply the bandwidth limitation and provide valued added services.
- Traffic steering policy shall be able to distinguish between upstream and downstream traffic.
- The 3GPP Core Network shall be able to define different traffic steering policies for a user’s traffic on a per session basis (e.g. for applying parental control, anti-malware, DDoS protection, video optimization).
- The 3GPP Core Network defines traffic steering policies based on one or more pieces of information such as:
- network operator’s policies
- user subscription (e.g. user’s priority, the status of optional subscriber services from the subscription data, based on service provider used, subscribed QoS)
- user's current RAT
- the network (RAN and CN) load status
- application characteristics such as: application type (video, web browsing, IM, etc), application protocol ( HTTP, P2P, etc), target address name (URL) and application provider (My tube, etc)
- time
- UE location
- information (e.g. APN) of the destination network (i.e. a PDN or an internal IP network) of traffic flow
- In case of roaming, the HPLMN shall be able to apply traffic steering policies for home routed traffic.
NOTE: Traffic steering policies for local breakout is not specified.
31 Control of traffic from UE-based applications toward associated server |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.1 Description | This feature is a set of service features that allows operators to control traffic from UEs to an application on a third-party server or the third-party server itself. When an application on a third-party server or the third-party server itself becomes congested or fails the traffic towards that server need to be controlled to avoid/mitigate potential issues caused by resulting unproductive use of 3GPP network resource. This will also make it possible to allow 3GPP network to help third-party servers to handle overload and recover from failures. (see [11]) |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2.1 Control requirements | The 3GPP network shall be able to control (i.e. block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.
For this purpose, the 3GPP network shall be able to identify the third-party server or the application on the third-party server, and the traffic towards it.
When congestion or failure of the application on the third-party server or the third-party server abates the 3GPP network shall be able to apply this feature in a phased manner to gradually restore traffic according to operator policy.
The 3GPP network shall be able to control traffic through this feature based on:
(1) the traffic load on the 3GPP network,
(2) the MNO policy,
(3) the MNO’s service subscription profiles such as access class information, and
(4) third-party service subscription profiles
without impacting the traffic to other applications on the third-party server or other third-party servers. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 31.2.2 Requirements on awareness of third-party server issue | The 3GPP network shall be able to receive a status indication from the third-party server when an application on it is experiencing congestion or failure, and when normal operation resumes. Such a status indication may be sent periodically, and/or when the status of the application changes.
The 3GPP network shall be able to detect and monitor a third-party server’s operational status e.g. congestion levels, failure and unavailability of the third-party server.
32 3GPP enhancement for TV application support |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.1 Feature description | 3GPP enhancement for TV service support is a feature whereby 3GPP networks can provide unicast and broadcast transport, referred to as “TV transport services”, to support distribution of TV programs. TV transport services can support the three types of TV services – Free-to-air (FTA), Free-to-view (FTV), and Subscribed services. Each type of TV service has different requirements in order to meet regulatory obligations and public service and commercial broadcaster’s requirements regarding content distribution, hence many requirements captured below are optional to implement depending on the type of TV transport services an MNO chooses to offer. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2 Requirements | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.1 General requirements | The 3GPP network shall be able to support on-demand network capacity assignment for TV services.
The 3GPP system shall allow the MNO to implement a network supporting downlink only broadcasting based on a set of EPS functionalities and entities which are required to offer linear TV services.
The 3GPP network shall be able to support on-demand network broadcast service area coverage management for TV transport services.
The 3GPP network shall support content delivery up to UHD resolution.
The 3GPP network shall allow the MNO to authenticate a subscriber before providing TV transport services via unicast.
The 3GPP network shall allow the MNO to authenticate a subscriber before providing TV transport services via eMBMS broadcast.
The 3GPP network shall enable an MNO to allow a UE to receive TV transport services via eMBMS broadcast without authentication.
The 3GPP network shall be able to provide FTA TV services receivable by UEs subscribed to the MNO and roaming UEs of other MNOs. A UE supporting enhanced TV transport services and in limited service state shall be able to receive eMBMS broadcast TV transport services.
The 3GPP network shall provide the ability for an MNO to meet regulatory requirements for privacy and non-identification of a receiving user by entities outside of the MNO.
NOTE: The MNO is responsible for maintaining the privacy of personal usage data collected as a result of providing access to the TV services.
The 3GPP network shall provide mechanisms to restrict the reception of some or all Subscribed TV services to groups of subscribers (e.g. based on the recipients of the services are subscribers of the MNO, roaming subscribers of other MNOs, or not subscribed to any MNO).
The quality of experience of the TV service shall be independent from the size of the concurrent audience. While receiving TV services in normal service state, subscribers of the MNO and roaming subscribers shall be able to access other subscribed services such as voice, data or SMS.
The 3GPP network shall support combinations of SD, FHD and UHD resolution TV transport services.
The 3GPP network shall allow the MNO to provide a TV service in a resource efficient manner over a large area up to the size of a country.
The 3GPP network shall enable the quality of experience of the TV service to be ensured throughout the coverage area defined for the TV service. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.2 Requirement for transmission performance enhancement | The 3GPP system shall be able to support 20Mbps over one logical broadcast channel.
The mechanisms in the 3GPP network shall be designed to support at least 10 high quality video channels of 12Mbps each simultaneously via broadcast.
The 3GPP network shall support flexible change between broadcast and unicast per traffic demand over the same carrier.
The 3GPP network shall be able to convert network unicast capacity to network broadcast capacity and vice versa so that each can range from 0% to 100% of the capacity.
The 3GPP network shall be able to support using one carrier for both unicast and broadcast distribution of TV services.
If allowed by the operator and a spare carrier is available, the 3GPP network shall be able to make use of spare carriers or free up carriers if not required anymore. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.3 Requirement for network flexibility | The 3GPP network shall be able to support network broadcast capacity assignment according to operator policies to consider the following criteria:
• OTT provider request (including TV service information (e.g., codec information, media type information, etc))
• available network unicast/broadcast capacity of 3GPP network
Within the radio resources dedicated to TV services in a geographic area the 3GPP network shall allow the MNO to specify the allocation of radio resource by the following:
• static allocation, i.e., pre-defined maximum percentage to be used for unicast and broadcast
• dynamic allocation, i.e., the pre-defined maximum percentage for both unicast and broadcast to be changed at a time-resolution of [one] minute over a period of [24] hours
The 3GPP network shall be able to support network broadcast geographic area coverage management considering following criteria:
• OTT provider request (including the potential coverage information of TV service information)
• available network unicast/broadcast capacity of 3GPP network
• number of users under broadcast network coverage
• The location information of UE
The 3GPP network shall be able to deliver media content via unicast and broadcast in an efficient manner. The 3GPP system shall be capable of ensuring the timing sequence of different media content received by different UEs at the same location, even via different transport path, aligning with the timing sequence of TV service of the OTT provider in order to maintain synchronism.
A UE shall be able to receive eMBMS from one cell site while receiving other services from the same cell site or another possibly cell site.
The 3GPP network shall allow an MNO to service all UEs in an area with eMBMS independent of which MNO network(s) they have subscription to. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.4 Requirement for TV application support | The eMBMS service layer should support audio and video formats typically supported by TV Content Providers for SD and HD TV transport services and UHD TV transport services.
The eMBMS service layer should support codecs typically supported by TV Content Providers for HD TV services and UHD TV services. The eMBMS service layer should support accessibility functions typically supported by TV Content Providers (e.g. subtitling, closed captioning, audio descriptions, anonymous reception, reporting to support ratings, reporting enforcement, etc.).
The eMBMS service layer should support regulatory mandates typically supported by TV Content Providers (blackouts, emergency alerts, etc.).
The eMBMS service layer should support interactivity functions typically supported by TV Content Providers (interactive services, second screen, personalization, etc.).
The eMBMS service layer should support ad insertion use cases typically supported by TV Content Providers (targeted ad insertion, ad replacement, etc.),
The eMBMS service layer should support encryption, security and conditional access functions typically supported by TV Content Providers.
The eMBMS service layer should support efficient concurrent delivery of multiple application components (TV service application signalling, statistical multiplexing, etc.).
The eMBMS service layer should support random access and channel change times comparable to existing HD TV services.
The eMBMS service layer should support TV service content delivery over broadcast only, unicast only and combinations of the two.
The eMBMS service layer should support delivery of real-time and non-real-time content.
The eMBMS service layer should enable extensibility and forward-compatibility to new requirements, formats, codecs and other functions to the extent possible.
An eMBMS transport layer should be able to transport TV streams formatted not compliant to 3GPP standards.
A UE should be able to access an eMBMS transport session with the support of only transport metadata.
An eMBMS system should be able to be initiated by a UE with sufficient metadata provided by a mechanism other than User Service Description for non 3GPP transport services. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.5 Requirement for RAN sharing | A participating eMBMS-enabled RAN shall be capable of distributing the content including both free-to-air content and subscribed content in conjunction with other participating eMBMS-enabled RANs.
The hosting eMBMS-enabled RAN network provider shall be able to manage the shared eMBMS network to each of the participating MNOs.
Each RAN provider shall report events supporting the accounting of network resource usage separately for each Participating MNO. This includes:
• Start of service in the shared eMBMS network for a UE of the Participating MNO
• End of service in the shared eMBMS network for a UE of the Participating MNO |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.6 Requirement for wide area support | The eMBMS network shall be able to support designated coverage area, for example national, regional and local coverage areas. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.7 Requirement for capability exposure | The 3GPP system shall be able to support an MNO offering on-demand broadcast availability to TV services.
Subject to MNO and 3rd OTT party agreement, to enable the MNO to evaluate the impact on distribution of data transfer in the network, the 3rd OTT party shall be able to indicate to the MNO the desired media format information: the volume of the data traffic expected to be broadcast in this geographic area, indication whether the streaming content can be accessed when the mobile users moves out/in of broadcast coverage area, indication whether the streaming content can be cached in the MNO network, association information among users i.e. user information, expected media content information, device information and group information of TV service and the timing relationship information of different media content.
The 3GPP network shall enable an MNO to inform a 3rd party of the result (e.g., selected media format information, mode of content delivery (broadcast only, broadcast/unicast fall-back support, consumption-based switching between unicast/broadcast), QoE of content delivery, cached content indication) of delivering a TV service to a user. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 32.2.8 Fixed reception for TV services | The 3GPP network shall allow a UE to receive a broadcast TV content using existing TV antenna equipment.
NOTE 1: “existing TV antenna equipment” means rooftop or indoor antennas directly connected to a TV or set-top box typically used to receive DTT signals
The 3GPP network shall allow a UE to receive unicast TV content using existing TV antenna equipment, at least for the downlink
NOTE 2: This might imply the uplink to take another path e.g. via a different antenna if existing TV antenna equipment is not suitable for transmission.
33 Usage over unlicensed access |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 33.1 Description | It is important to document usage over unlicensed access such that an operator has the facility to determine which type of access the traffic was transported over.
For example, LTE-WiFi Aggregation (LWA) and License Assisted Access (LAA) are two features whereby a UE is connected to two access technologies at the same time, i.e., a primary access and a secondary access, where the secondary access technology operates in unlicensed spectrum. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 33.2 Requirements | The 3GPP network shall be able to identify traffic which was transported over unlicensed access. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34.1 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 34.2 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35 Restricted local operator services | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35.1 Description | Access to restricted local operator services by unauthenticated UEs is based on FCC regulations in the U.S. related to manual roaming as noted in the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 Section 20.3 and the Code of Federal Regulations (CFR) Title 47 Chapter 1 Subchapter B Part 20 Section 20.12 (Resale and Roaming) Subparagraph c [60].
The restricted local operator services offered by an operator are out of scope of 3GPP. Allowing access to restricted local operator services is completely under the local operator’s control. The local operator can restrict unauthenticated UEs to be able to access restricted local operator services exclusively.
Authenticated UEs in limited service state may also be able to use restricted local operator services.
NOTE: Services provided through RLOS may also be available to authenticated UEs not in limited service state by other methods. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 35.2 Requirements | Based on operator policy and national regulations, the 3GPP system shall support a mechanism to indicate to UEs that restricted local operator services are available. A UE shall be able to explicitly request access to a network offering restricted local operator services in order to access restricted local operator services. A UE explicitly requesting access to a network offering restricted local operator services in order to receive restricted local operator services shall not be put into limited service state. Based on operator policy and national regulations, the 3GPP system shall support mechanisms to allow access to restricted local operator services by unauthenticated UEs. The network shall be able to isolate restricted local operator services and usage from the rest of the network (i.e., similar to security for unauthenticated CS or IMS emergency calls). When a UE recognizes an origination attempt to a restricted local operator service and has not received an indication from the serving system that restricted local operator services are available, the UE shall block the origination attempt. The UE shall include the restricted local operator service call type indicator when an origination attempt is made for a restricted local operator service. Annex A (normative): Description of optional user equipment features A.1 Display of called number This feature enables the caller to check before call setup whether the selected number is correct. A.2 Indication of call progress signals Indications shall be given such as tones, recorded messages or visual display based on signalling information returned from the PLMN. On data calls, this information may be signalled to the DTE. Call progress indicators are described in 3GPP TS 22.001 [4]. A.3 Country/PLMN indication The country/PLMN indicator shows in which PLMN the UE is currently registered. This indicator is necessary so that the user knows when "roaming" is taking place and that the choice of PLMN is correct. Both the country and PLMN will be indicated. When more than one visited PLMN is available in a given area such information will be indicated. The PLMN name is either: - Stored in the ME and associated with the MCC+MNC combination received on the broadcast channel; - NITZ (see 22.042 [17]) (in which case it overrides the name stored in the ME); - stored in the USIM in text and /or graphic format and associated with the MCC+MNC combination, and optionally the LAI, received on the broadcast channel (in which case it overrides the name stored in the UE and – if present – the NITZ name). It shall be possible to store on the USIM at least 10 PLMN Identifications (MCC+MNC combination and optionally the LAI) for which the same PLMN name shall be displayed. The PLMN name stored in the USIM has the highest priority, followed by the PLMN name provided by NITZ. The PLMN name stored in the ME has the lowest priority. If the PLMN name stored in the USIM is not available in text format and the UE is unable to display the graphic format, the PLMN name provided by NITZ has the highest priority, the PLMN name stored in the ME has the next priority. For a PLMN name provided by NITZ, operators using non-Latin characters of the local language (such as Chinese, Japanese, Korean, Vietnamese, Arabic, Hindi, etc.) may include the network name in Latin characters in addition to characters of the local language. For a PLMN name provided by NITZ, the roaming UE should skip displaying non-Latin character(s) if the language of those character(s) does not match the language of the MMI for the UE. If this would lead to no remaining Latin character in the PLMN name, the UE should skip displaying the PLMN name provided by NITZ; the PLMN name stored in the ME has the next priority instead. A.4 Service Provider Name indication The service provider name is stored in the USIM in text and/or optionally graphic format. It shall be possible to associate at least 10 PLMN Identifications (MCC+MNC combination) with the same SP Name. When registered on the HPLMN, or one of the PLMN Identifications used for Service Provider Name display: (i) The SP Name shall be displayed; (ii) Display of the PLMN Name is an operator's option by setting the appropriate fields in the USIM (i.e. the Service Provider name shall be displayed either in parallel to the PLMN Name or instead of the PLMN Name). When registered on neither the HPLMN, nor one of the PLMN Identifications used for Service Provider Name display: (i) The PLMN name shall be displayed; (ii) Display of the SP Name is an operator's option by setting the appropriate fields in the USIM. If the UE is unable to display the full name of the Service Provider the name is cut from the tail end. The storage of Service Provider name and options, and choice of options, shall be under control of the network operator. A.4a Core Network Operator Name indication It shall be possible for the UE to display the name of the core network operator the user has selected. A.5 Keypad A physical means of entering numbers, generally, though not necessarily, in accordance with the layout shown in figure A.1. See also 3GPP TS 22.030 [6] (Man-Machine Interface). Additional keys may provide the means to control the UE (e.g. to initiate and terminate calls). 1 2 3 4 5 6 7 8 9 * 0 # Figure A.1 A.6 Short message indication and acknowledgement This feature allows the delivery of short messages to a UE from a service centre. Such messages are submitted to the service centre by a telecommunications network user who can also request information of the status of the message by further interrogation of the service centre. The service centre then transmits the message to an active UE user. The UE must therefore provide an indication to the user that a message has been received from the service centre and must also send an acknowledgement signal to the PLMN to show that this indication has been activated. The PLMN then returns this acknowledgement to the service centre. The short message service teleservice is described in specification 3GPP TS 22.003 [14]. A.7 Short message overflow indication An indication shall be given to the user of the short message service when an incoming message cannot be received due to insufficient available memory. A.8 International access function Provision is made for a direct, standard method of gaining international access. For this purpose the UE may have a key whose primary or secondary function is marked "+". This is signalled over the radio interface and would have the effect of generating the international access code in the network. It may be used directly when setting up a call, or entered into the memory for abbreviated dialling. This feature is of benefit since the international access code varies between CEPT countries, which might cause confusion to a user, and prevent the effective use of abbreviated dialling when roaming internationally. Users may still place international calls conventionally, using the appropriate international access code. A.9 Service Indicator (SI) An indication is given to the user that there is adequate signal strength (as far as can be judged from the received signal) to allow a call to be made. Additionally the network should be capable of providing, and the UE may display, an indication of the serving cells' capabilities e.g. GPRS, HSDPA, HSUPA. If indicated by the registered network, the UE in idle mode may display an indication of one of the radio access technologies provided to the UE in the network on which the UE is registered with the following priority order: E-UTRAN, UTRAN, GERAN. Displaying the serving cell's capabilities and the access technology are mutually exclusive. A.10 Dual Tone Multi Frequency (DTMF) The UE shall be capable of initiating DTMF in accordance with specifications 3GPP TS 22.003 [14]. Optionally, the UE may provide a suppress function which allows the user to switch off the DTMF function. A.11 On/Off switch The UE may be provided with a means of switching its power supply on and off. Switch-off shall be "soft", so that on activation, the UE completes the following housekeeping functions: termination of a current call, detach (where applicable) and storing required data in the SIM/USIM before actually switching off. As far as possible, this procedure should also apply on power failure (e.g. remote switch-off or low battery). A.12 Sub-Address This feature allows the mobile to append and/or receive a sub-address to a Directory Number, for use in call set-up, and in those supplementary services that use a Directory Number. A.13 Short Message Service Cell Broadcast The Short Message Service Cell Broadcast enables the mobile equipment to receive short messages from a message handling system. The short message service cell broadcast teleservice is described in specification 3GPP TS 22.003 [14] A.14 Short Message Service Cell Broadcast DRX This feature enables a mobile equipment to save on battery utilization, by allowing the mobile equipment to not listen during the broadcast of messages the subscriber is not interested in. A.15 Support of the extended Short message cell broadcast channel This feature allows a mobile equipment by supporting of the extended Short message cell broadcast channel to enhance the capacity of the service. The support of the extended channel has low priority, i.e. the UE can interrupt the reading of this channel if idle mode procedures have to be executed. A.16 Network Identity and Timezone The feature provides the means for serving PLMNs to transfer current identity, universal time and the local timezone to mobile equipment, and for the mobile equipment to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the ME or have changed their name since the ME was sold. Additionally time and timezone information can be utilized by MEs as desired. The network name time and timezone information will normally be transferred from the network to the ME: 1) Upon registering on the network. 2) When the UE geographically relocates to a different Local Time Zone. 3) When the network changes its Local Time Zone, e.g. between summer and winter time. 4) When the network changes its identity. 5) At any time during a signalling connection with mobile equipment. Further details of this feature are described in 3GPP TS 22.042 [17]. A.17 Network's indication of alerting in the UE This feature provides the means for serving PLMNs to transfer to a UE an indication that may be used by the UE to alert the user in a specific manner in the following cases: - mobile terminating call - network-initiated USSD - network-initiated Mobile Originated (MO) connection, if the ME supports the "network-initiated MO connection " feature. Eight different indications are defined, whether the mobile terminating traffic is a call or USSD or related to the network-initiated MO connection procedure. These indications are sent by the network and received by the UE: - Three of these indications are used as levels, reflecting some kind of urgency: level 0 indicates that the UE shall not alert the user for USSD and remain silent in the case of call, level 2 shall be considered by the UE as more important than level 1 for the purpose of alerting the user. - The five other indications are used as categories, identifying different types of terminating traffic. The UE shall inform the user in a specific manner for each of these five categories. Nevertheless, the possible forms of the alert (different ringing tones, displayed text, graphical symbols...) is still up to the mobile manufacturer (some forms of alerts can be simultaneously used, e.g. ringing tones and text on the display). The management of the feature by the UE requires for the handling of categories that: - the SIM/USIM stores for each category an informative text (maximum 25 characters per category) describing the type of terminating traffic associated with the category. This information could be used by the UE when alerting the user (display on the screen). It is necessary for the network operator to be able to change the meaning of each category. - The user has the ability to set up his/her own association between the type of terminating traffic (identified by each category) and the different types of alert provided by the UE. To help the user in this choice, the UE uses the informative text associated with each category (as stored in the SIM/USIM). The UE should keep this association when switched off. Default settings should also be defined in the ME for the following cases: - when the UE receives a call, USSD or a request for a network-initiated MO connection with no alerting indication, - when the UE receives a call, USSD or a request for a network-initiated MO connection with a category of alerting not defined in the SIM/USIM. These default settings should be separated per type of mobile terminated traffic received (call, USSD or request for a network-initiated MO connection). A UE supporting the feature shall act according to the following points in case of mobile terminating traffic: - when a mobile terminating traffic is received without any indication (level or category), the ME shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic). - if a level is indicated, the UE shall use an alert enabling the user to differentiate between the three levels. - if a category is indicated, then: - if the SIM/USIM used in the UE does not store any information on that feature, the UE shall ignore the category received with any mobile terminating traffic and act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic). - if the category is not defined in the SIM/USIM, the UE shall act as if it was not supporting the feature, i.e. use a default alert (e.g. associated with this type of mobile terminating traffic). - if the category is defined in the SIM/USIM, the UE shall use the alert associated with this category. In addition, it would be very useful for the user to be notified of the informative text associated with this category (e.g. on the display). Some interactions between this feature and other services related to alerting are described below: - the call waiting service has priority on this feature, i.e. the call waiting tone will be played and not the alert derived by this feature. If possible, two different indications should be given to the user (e.g. the call waiting tone and a text on the display indicating call waiting, and in addition a text relative to the type of the new call received). - the presentation of the calling line identity takes priority on this feature, if it is not possible to display this information and another information related to this feature. - In case of interaction between this feature and UE specific features to alert the user (e.g. whole silent mode), the user should still be able to differentiate between the different levels or different types of terminating traffic, even if the alert itself may be changed. A.18 Network-initiated Mobile Originated (MO) connection The "Network-initiated Mobile Originated connection" feature allows the network to ask the mobile equipment to establish a mobile originated connection. The serving PLMN provides the mobile equipment with the necessary information which is used by the mobile equipment to establish the connection. Currently only the network-initiated mobile originated call feature is specified. It is mandatory for a UE supporting CCBS and is used in the case of a CCBS recall. A.19 Abbreviated dialling The directory number or part of it is stored in the mobile equipment together with the abbreviated address. After retrieval the directory number may appear on the display. Abbreviated dialling numbers stored in the UE or USIM may contain wild characters. If wild characters are used to indicate missing digits, each wild character shall be replaced for network access or supplementary service operation, by a single digit entered at the keypad. The completed directory number is transmitted on the radio path. A.20 Barring of Dialled Numbers This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers belonging to a pre-programmed list of numbers in the SIM/USIM. Barred Dialling Numbers stored in the /USIM may contain wild characters. Under control of PIN2, "Barred Dialling Mode" may be enabled or disabled. The selected mode is stored in the SIM/USIM. Under PIN2 control, it shall be possible to add, modify or delete a particular "Barred Dialling Number" (BDN) and to allocate or modify its associated comparison method(s). This BDN may have the function of an abbreviated dialling number / supplementary service control (ADN/SSC), overflow and/or sub-address. When BDN is inactive, no special controls are specified, and the barred dialling numbers may be read (though not modified or deleted, except under PIN2 control) as if they were normal abbreviated dialling numbers. Access to keyboard and normal abbreviated dialling numbers (including sub-address) is also permitted. When Barring of Dialled Numbers is active: - Considering a number dialled by the user, if it exists a BDN for which there is a successful comparison (see below) between that BDN and the dialled number, then the ME shall prevent the call attempt to that number. If there is no BDN to fulfil those conditions, the call attempt is allowed by the ME. With each BDN is associated one (or a combination of) comparison method(s) used between that BDN and the number dialled by the user. At least three different comparison methods are possible: - The comparison is made from the first digit of that BDN, from the first digit of the dialled number and for a number of digits corresponding to the length of the BDN. - The comparison is made from the first digit of that BDN, from any digit of the dialled number and for a number of digits corresponding to the length of the BDN. - The comparison is made backwards from the last digit of that BDN, from the last digit of the dialled number and for a number of digits corresponding to the length of the BDN. - If a BDN stored in the SIM/USIM contains one or more wild characters in any position, each wild character shall be replaced by any single digit when the comparison between that BDN and the dialled number is performed. - If a BDN contains a sub-address, and the same number without any sub-address or with that sub‑address is dialled, the ME shall prevent the call attempt to that number. - Numbers specified as "barred" may only be modified under PIN2 control. - If the ME does not support barring of dialled numbers, the UE with a BDN enabled USIM shall not allow the making of calls and the UE with BDN enabled SIM shall not allow the making or receiving of calls. However, this feature does not affect the ability to make emergency calls. If "Fixed Number Dialling" and "Barring of Dialled Numbers" are simultaneously active, the dialled number shall be checked against the two features before the ME allows the call attempt. In that case, a dialled number will only be allowed by the ME if it is in the FDN list and if the comparison between that number and any number from the BDN list is not successful. The UE may support other selective barrings, e.g. applying to individual services (e.g. telephony, data transmission) or individual call types (e.g. long distance, international calls). A.21 DTMF control digits separator Provision has been made to enter DTMF digits with a telephone number, and upon the called party answering the UE shall send the DTMF digits automatically to the network after a delay of 3 seconds (± 20 %). The digits shall be sent according to the procedures and timing specified in 3GPP TS 24.008 [13]. The first occurrence of the "DTMF Control Digits Separator" shall be used by the ME to distinguish between the addressing digits (i.e. the phone number) and the DTMF digits. Upon subsequent occurrences of the separator, the UE shall pause again for 3 seconds (± 20 %) before sending any further DTMF digits. To enable the separator to be stored in the address field of an Abbreviated Dialling Number record in the SIM/USIM, the separator shall be coded as defined in 3GPP TS 31.102 [19]. The telephone number shall always precede the DTMF digits when stored in the SIM/USIM. The way in which the separator is entered and display in the UE, is left to the individual manufacturer's MMI. MEs which do not support this feature and encounter this separator in an ADN record of the SIM/USIM will treat the character as "corrupt data" and act accordingly. A.22 Selection of directory number in messages The Short Message Service (SMS), Cell Broadcast Service (CBS), Multimedia Message Service (MMS), Network-initiated USSD or Network Response to Mobile Originated USSD message strings may be used to convey a Directory Number, which the user may wish to call. A.23 Last Numbers Dialled (LND) The Last "N" Numbers dialled may be stored in the SIM/USIM and/or the ME. "N" may take the value up to 10 in the SIM/USIM. It may be any value in the ME. The method of presentation of these to the user for setting up a call is the responsibility of the UE but if these numbers are stored in both the SIM/USIM and the UE, those from the SIM/USIM shall take precedence. A.24 Service Dialling Numbers The Service Dialling Numbers feature allows for the storage of numbers related to services offered by the network operator/service provider in the SIM/USIM (e.g. customer care). The user can use these telephone numbers to make outgoing calls, but the access for updating of the numbers shall be under the control of the operator. NOTE: No MMI is envisaged to be specified for these numbers and it is left to mobile manufacturer implementations. A specific example of Service Dialling Numbers is the storage of mailbox dialling numbers on the SIM/USIM for access to mailboxes associated with Voicemail, Fax, Electronic Mail and Other messages. A.25 Fixed number dialling This feature provides a mechanism so that by the use of an electronic lock it is possible to place a bar on calling any numbers other than those pre-programmed in the SIM/USIM. Under control of PIN 2, "Fixed Dialling Mode" may be enabled or disabled. The mode selected is stored in the SIM/USIM. Fixed Dialling Numbers (FDNs) are stored in the SIM/USIM in the Fixed Dialling Number field. FDN entries are composed of a destination address/Supplementary Service Control. Destination addresses may have the format relevant to the bearer services/teleservices defined in [21] and [14]. FDN entries may take the function of an Abbreviated Dialling Number/Supplementary Service Control (ADN/SSC), Overflow and/or sub-address. Fixed Dialling Numbers stored in the SIM/USIM may contain wild card characters. The Fixed Dialling feature is optional, however when Fixed Dialling Mode is enabled, an ME supporting the feature shall; - Prevent the establishment of bearer services/teleservices to destination addresses which are not in FDN entries on a per bearer service/teleservice basis. The list of bearer services/teleservices excluded from the FDN check shall be stored in the SIM/USIM. Those bearer services/teleservices are characterised by their service code as described in [23]. For instance, if the SMS teleservices is indicated in this list, SMS can be sent to any destination. By default, the ME shall prevent the establishment of any bearer service/teleservice to destination addresses which are not in FDN entries. - Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2. - Allow the establishment of bearer services/teleservice to destination addresses stored in FDN entries. For SMS, the Service Center address and the end-destination address shall be checked. - Support the reading and substitution of wildcards in any position of an FDN entry, via the ME MMI. - Allow the user to replace each wildcard of an FDN entry by a single digit, on a per call basis without using PIN2. The digit replacing the wildcard may be used for network access or supplementary service operation. - Only allow Supplementary Service (SS) Control (in Dedicated or Idle mode) if the SS control string is stored as an FDN entry. - Allow the extension of an FDN entry by adding digits to the Fixed Dialling number on a per call basis. - Allow the emergency numbers (see Section 8.4) to be called, even if it is not an FDN entry. - Allow normal access to ADN fields (i.e. allow ADN entries to be modified, added or deleted) and the keyboard. - Allow use of ADNs subject to the FDN filter. When FDN is disabled, an ME supporting FDN shall; - Allow FDN entries to be read as though they were normal ADN entries. - Only allow modification, addition or deletion of Fixed Number Dialling entries under control of PIN2. - Allow normal access to ADN fields and the keyboard. If the ME does not support FDN, the UE shall not allow the making of calls when Fixed Dialling is enabled in the USIM, and the UE shall not allow the making or receiving of calls when Fixed Dialling is enabled in the SIM. However, emergency calls (112 and other user defined emergency numbers) shall still be possible. NOTE: Wildcards are stored on the SIM/USIM. The wildcard coding is given in 3GPP TS 31.102 [19]. A.26 Message Waiting Indication A short message may be used to provide an indication to the user about the status and number of types of messages waiting on systems connected to the PLMN. The ME shall present this indication as an icon on the screen, or other MMI indication, and store the indication status on the SIM/USIM to allow the status to be retained through power off/on, SIM/USIM movement between UEs etc. The ME shall be able to accept and acknowledge these message waiting status short messages irrespective of the memory available in the SIM/USIM. A.27 Transfer of eCall Minimum Set of Data (MSD) A.27.1 General Requirements With the exception of the following specific requirements, considered necessary for the satisfactory operation of the eCall service, all existing emergency call requirements shall apply. An eCall shall consist of an emergency call supplemented by a minimum set of emergency related data (MSD). The MSD e.g. vehicle identity, location information and other parameters, is defined by CEN [46]. - An eCall may be initiated automatically, for example due to a vehicle collision, or manually by the vehicle occupants; - An IVS, or other UE designed to support eCall functionality, shall include in the emergency call set-up an indication that the present call is either a Manually Initiated eCall (MIeC) or an Automatically Initiated eCall (AIeC). - The Minimum Set of Data (MSD) sent by the In vehicle System (IVS) to the network shall not exceed 140 bytes; - Should the MSD component not be included in an eCall, or is corrupted or lost for any reason, then this shall not affect the associated emergency call speech functionality. - To reduce the time taken to establish an eCall an IVS whilst in eCall only mode, may receive network availability information whilst not registered on a PLMN. - PLMNs should make use of eCall indicators, received in the emergency call set-up, to differentiate eCalls from other emergency calls. - The MIeC and AIeC should be used by the serving network to filter and route eCalls to dedicated, eCall equipped, PSAPs. - The PSAP shall be given an indication that the incoming call is an eCall. - When an emergency call, other than an eCall, is routed to a PSAP that supports the eCall service, the eCall equipment shall not cause audible interference to the emergency voice call. Throughout the duration of the emergency call and following receipt of the MSD by the PSAP - It shall be possible for the PSAP to send a confirmation to the IVS that the MSD has been acted upon. - It shall be possible for the PSAP to request the IVS to re-send its most recent MSD. - It shall be possible for the PSAP to instruct the IVS to terminate the eCall. A.27.2 Requirements for the transfer of eCall MSD in a TS12 call The MSD should typically be made available to the PSAP within 4 seconds measured from the time when end to end connection with the PSAP is established; A call progress indication shall be provided to the user whilst the MSD transmission is in progress. Where the eCall indicators are not supported by the serving network, the time needed for the PSAP eCall modem to differentiate between eCalls and other TS12 calls, before routing the call to an operator, shall not exceed 2 seconds from when the IVS receives notification that the PSAP has answered the call. When an eCall is routed to a PSAP, that does not support the eCall service, the In Vehicle System (IVS) shall not emit any audible tones for longer than 2 seconds from the time that the call is first answered. A.27.3 Requirements for the transfer of eCall data in an IMS emergency call The MSD should typically be available to the PSAP when the end to end connection with the PSAP has been established. NOTE: There are cases where a UE delivers multiple instances of an MSD to one or more PSAPs, for example as per 3GPP TS 22.101 clause 10.1.2., when an IMS emergency call based eCall attempt has not been successful but the MSD was successfully received by a PSAP. It is out of the scope of 3GPP as to how to manage any duplicate information received by the PSAP(s) or emergency services as a result of this. Additional data (i.e. data not contained in the initial MSD) may be transferred at any time during the eCall (e.g. MSD acknowledgement, resending of the MSD if requested by a PSAP). The call setup time of an eCall shall be the same as for an IMS emergency call. The IVS shall not emit any audible tones in order to transfer the MSD or other eCall related data. A.27.4 Interworking requirements A PSAP, which is connected to the IMS, and supports either IMS emergency call based eCall or TS12 based eCall, shall be able to interwork with a TS12 based IVS using IMS Centralized Service, i.e. it shall be able to terminate the emergency call from the IVS, receive the MSD and request additional data from the IVS, using the eCall Modem end-to-end. An IVS that supports IMS emergency call based eCalls shall also support TS12 based eCalls. An IVS that supports IMS emergency call based eCalls and is attached via LTE access with no CS access available shall support the transfer of MSD via IMS emergency call to a TS12 based PSAP using the eCall Modem end-to-end. NOTE 1: It is assumed that the above scenario is very unlikely to occur on the market. Therefore the operation of eCall Modem over a PS bearer should be considered as an option of last resort [58]. As such this is not constrained by the requirements in A.27.2 and A.27.3. In case of interworking between TS12 and IMS emergency call based eCall equipment the requirements given in subclause A.27.2 shall apply, requirements given in subclause A.27.3 do not apply. A.27.5 Domain selection A PLMN shall indicate to an IVS whether IMS emergency call based eCalls are supported. An IVS that supports both IMS emergency call based eCalls and TS12 based eCalls shall support domain selection for an eCall in the same way as for any other emergency call except for determining PLMN support for an IMS emergency based eCall using the PLMN indication for this. A.27.6 Call-back after eCall For a limited time of at least one hour following the failure or release of a TS12 eCall or an eCall over IMS and if the PSAP has received the CLI of the IVS, the IVS shall be able to receive a call-back from the PSAP requesting transfer of an updated MSD. Note 1: The IVS needs to stay registered on IMS for at least one hour following the failure or release of an eCall over IMS to be reachable for callback. Continued registration on IMS and provision of updated MSD is not required after this period. Note 2: For a TS12 eCall, the PSAP would be accessed using the CS domain. However, the PSAP could use the PS domain for a call-back. In addition, the IVS may be registered with IMS (e.g. in the case of a combined attach) or the IVS may move out of CS coverage and into PS coverage. In these cases, PSAP call-back could occur using IMS. A.27.7 Test eCall A test eCall is a non-emergency services call (e.g. a TS11 call or an IMS non-emergency services call) that includes features of an eCall and is used to help verify IVS support of an eCall. An IVS with TS12 eCall capability shall support a TS11 test eCall. An IVS with eCall over IMS capability shall support a test eCall over IMS. A test eCall may be sent to a directory number or URI defined for testing purposes by a national regulator, PSAP or eCall test provider. A test eCall shall support transfer of MSD and updated MSD using the same mechanism(s) as a real eCall. The MSD shall be same as that sent for a real eCall but with an indication of a test eCall. A test eCall shall support callback from a test provider with transfer of updated MSD. A.28 Requirements for "In Case of Emergency" (ICE) information The In Case of Emergency (ICE) information are used to enable first responders, such as paramedics, fire-fighters, and police officers, to contact a victim's emergency contact(s) in order to identify the victim and obtain important medical information or other information required during an emergency. A UE shall have the capability to store one or more "ICE information" on the UICC. The "ICE information" shall list the type of information which is to be configured by the mobile operator as described in the table below. Table A.28.1: "ICE information" description ICE information type format ICE information type value ICE information value 1 ICE information value 2 ICE information value n Description Two formats shall be defined in this release: 1- Phone number format. For the phone number format it shall be possible to store a name and a phone number. 2- Free format. It shall be possible for the mobile operator to provision zero, one or several instances of a given format on the UICC. It shall be possible to store this information in text or graphic format. It shall be possible to have at least one ICE information value field. If more than one information value fields are required it shall be indicated by the ICE information type format. It shall be possible for the subscriber to add, modify, view, or delete any ICE information value. For the free format ICE information type format, it shall be possible to store information in text or graphic format. For pre-defined ICE information type formats the ME should adapt the input mode to the type of the ICE information value (e.g. numerical mode for phone number input). Present only if explicitly indicated by the ICE information type format. Present only if explicitly indicated by the ICE information type format. The following table provides an example of ICE information stored on the UICC: Table A.28.2: "ICE information" example ICE information type ICE information type value ICE information value 1 ICE information value 2 Phone Number "Contact in case of emergency" My Wife +3364566 Phone Number "Contact in case of emergency" Family Smith +3364565 Phone Number "Contact in case of emergency" My Family doctor: Dr. Jones +33643234 Free Format "Medical Information" My blood type is A+, I am allergic to etc. N/A Free Format "Home Postal Address" 15 rue de la Paix, Paris, France N/A Free Format "Language" French N/A Free Format "Travel Information" London, from 3rd July. to 29th July, 2008 N/A Provision is made for direct and unambiguous read access from the UE to ICE information stored on the UICC. The subscriber may choose not to enter any ICE information. The default configuration for this information shall be that they are accessible even when the security features on either the UE or UICC have been enabled (e.g. the keypad is locked). It shall be possible for the subscriber to change this default setting to prevent accessibility to the ICE information (i.e. a user configurable setting in the UICC indicates whether the ICE information on the UICC shall be displayed or not, if the ICE access procedure described in TS 22.030 [6] is invoked). The unlocking of ICE information shall not allow access to other secure information on the UICC or UE. The ICE information value should not be accessible to ME or UICC applications. The ICE access procedure is described in TS 22.030 [6]. Annex B (informative): Additional number use case Company X is customer of operator Z and has a subscription for voice and data with 10 SIM cards. The company also decides to subscribe to the private numbering plan feature of operator Z. A certain corporate phone number is assigned to company X, e.g. +43 676 88888 xx (with xx being the extensions of the users), and they can freely choose the extensions for up to 100 SIM cards. Initially company X take the existing 10 SIM cards (with the existing MSISDNs) and integrate them into the private numbering plan by assigning the extensions 11 to 20 to these cards via a web portal. This is not a permanent assignment, the extensions can be changed easily any time, old SIMs can be deleted from the private numbering plan and new ones can be integrated whenever necessary. Special privileges or restrictions can be chosen on a per SIM basis via the portal and special tariffs apply. The CEO of company X calls a customer. The customer's phone displays the corporate number + extension of the CEO as CLI. After a while the customer decides to call back the CEO and uses the corporate number + extension as MSISDN. Later they also exchange some short messages, again the corporate number + extension of the CEO is used as sender's MSISDN. For all these calls and short messages operator Z is able to collect charging records containing the corporate number + extension. The CEO also uses her smart phone to establish PS connections to browse the internet and to access the intranet via the operator's gateway. The corporate number + extension is used for authentication and authorisation in the company's intranet and its web applications. Charging for PS connections by operator Z is also based on this number. In general the users in company X are not aware of their "real" underlying MSISDNs in the system, they only see the corporate number + their extension and there is no need for them to know the underlying MSISDN. Annex C (informative): Change history Change history SMG No. TDoc. No. CR. No. Section affected New version Subject/Comments SMG#22 302/97 001 4.6 (Role Model) 3.1.0 SMG3 queried the separation of network operator into core and access, which, on examination, SMG1 find unhelpful SMG#22 319/97 (SMG1 WPC 125/97) 002 3.1.0 Editorial Changes: FLMPTS was replaced by IMT 2000, 2 new references given, additional clarifications. SMG#22 320/97 003 8.5, 9.3, 9.5, 17 3.1.0 Changes on Emergency Calls, User identification, Multiple profiles and additional handover requirements. After SMG#23 SMG1 433u/97 965/97 004 Draft 3.2.0 Based on Approved Changes at SMG#22 Distributed at SMG1 in Dresden Nov 3-7, 97 to be Approved at SMG#24 SMG#24 966/97 005 Sections 8, 9, 11 3.2.1 Restructuring of sections 8,9 and 11 to gather all requirements relating to multiple subscriptions into one section and to improve the clarity. SMG#24 967/97 006 Section 8.1 3.2.1 To improve the accuracy of text on numbering principles and minor editorial change to section 8.1 SMG#27 98-0551 007 Section 4.6 and misc. 3.3.0 Removal of commercial role model from the specification in order to improve clarity SMG#27 98-0552 (Not Approved) 008 New Section 18 (Not Applied) 3.3.0 To include requirements for network selection in service principles: NOT APPROVED > NOT APPLIED Pre-SMG#28 (SMG1 Tdoc 98-0893) 99-040 008 r4 Rejected New Section 18 Applied [Draft 3.4.0] Added Network Selection section - Agreed by correspondence - Jan 13, 1999 - Prepared with CRs applied with revision marks SMG#27 98-0553 009 Section 4.3 3.3.0 To remove unnecessary reference to IN and B-ISDN SMG#27 98-0682 010 Section 11 3.3.0 To improve the clarity of service requirements for multiple user profiles Pre-SMG#28 (SMG1 Tdoc 98-0869) 99-040 011 Sections 1, 2, 3, 4, 9, 10, 12, 17 Draft 3.4.0 Clean up for UMTS phase 1 Agreed at SMG1 Rome Pre-SMG#28 (SMG1 Tdoc 98-852) 99-040 012 Sections 3,8,9,11,14,15 Draft 3.4.0 Changes in IC card and terminal service requirements Agreed at SMG1 Rome Pre-SMG#28 (SMG1 Tdoc 98-0894) 99-040 013r1 Section 3.2 & 4.3 Draft 3.4.0 Clarification of general requirements for efficient use of radio resources Agreed by correspondence - Jan 13, 1999 - Prepared with CRs applied with revision marks Note Draft 3.4.0 SMG1 agreed only pre-SMG#28 99-040 015 Rejected 17 Draft 3.4.0 According to the outcome of the SMG 1 ad-hoc meeting on handover issues it is proposed that inter-operator handover is not required for UMTS phase 1.(rejected by smg#28) SMG#28 99-305 008r5 Revised Section 18 3.4.0 Network Selection presented at SMG#28 in 2201_008r4 was further revised and Approved at SMG#28. Note 3.4.0 Removal of Section 12 on UPT with CR 011 causes a skip section from Section 11 to 13. Change history TSG SA# SA Doc. SA1 Doc Spec CR Rev Rel Cat Subject/Comment Old New WI SP-03 SP-99104 S1-99202 22.101 A016 R99 B Control of supplementary services (GSM 02.04), may use MMI procedures specified in GSM 02.30 and existing GSM MMI related MS features (GSM 02.07) may also be used. 3.4.0 Post-SA#3 22.101 R99 Updated Logo, … 3.5.0 3.5.1 SP-04 SP-99229 S1-99387 22.101 021 R99 B MultiNumbering: It will be possible for multiple MSISDNs to be associated with a single subscription. 3.5.0 3.6.0 SP-04 SP-99226 S1-99395 22.101 020 7 R99 B Emergency: To route the call to the appropriate emergency service if more than one emergency number is supported in a country. 3.5.0 3.6.0 SP-05 SP-99439 S1-99737 22.101 025 R99 B Support of SAT by USIM 3.6.0 3.7.0 SP-05 SP-99439 S1-99816 22.101 024 R99 B Clarification on the usage on 2G SIM and 3G USIM 3.6.0 3.7.0 SP-05 SP-99435 S1-99851 22.101 022 R99 C Clarification of Emergency Call requirements 3.6.0 3.7.0 SP-06 SP-99524 S1-991031 22.101 029 R99 B Emergency Call 3.7.0 3.8.0 SP-06 SP-99527 S1-991038 22.101 028 R99 C FDN 3.7.0 3.8.0 SP-06 SP-99519 S1-991026 22.101 026 R99 D Mainly editorial update for GSM/3GPP use. 3.7.0 3.8.0 SP-07 SP-000060 S1-000112 22.101 030 R99 A Support of encryption in GPRS mobile stations 3.8.0 3.9.0 SP-07 SP-000070 S1-000137 22.101 031 R99 F Fixed Dialing Number (FDN) 3.8.0 3.9.0 SP-08 SP-000210 S1-000271 22.101 033 R99 D Network selection procedures removed from section 16, reference to 22.011 added 3.9.0 3.10.0 SP-08 SP-000200 S1-000350 22.101 035 R99 B Emergency Calls and numbers used 3.9.0 3.10.0 SP-08 SP-000201 S1-000362 22.101 038 R99 F CS multimedia support 3.9.0 3.10.0 SP-08 SP-000202 S1-000326 22.101 039 R99 F Clarification for USIM Application selection 3.9.0 3.10.0 SP-08 SP-000210 S1-000270 22.101 034 R00 D Network selection procedures removed from section 16, reference to 22.011 added 3.9.0 4.0.0 SP-08 SP-000200 S1-000351 22.101 036 R00 B Emergency Calls and numbers used 3.9.0 4.0.0 SP-08 SP-000213 S1-000352 22.101 037 R00 B Emergency Call enhancements 3.9.0 4.0.0 SP-09 SP-000383 S1-000603 22.101 040 R4 B Multimedia messaging 4.0.0 4.1.0 SP-09 SP-000383 S1-000605 22.101 041 R4 C Service Management requirements 4.0.0 4.1.0 SP-09 SP-000430 S1-000700 22.101 042 1 R4 F General corrections and clarifications to 22.101 for Release 2000 4.0.0 4.1.0 SP-09 SP-000383 S1-000598 22.101 046 R4 D Editorial changes to 22.101 for Release 2000 4.0.0 4.1.0 SP-09 SP-000430 S1-000698 22.101 047 1 R4 C Numbering Principles 4.0.0 4.1.0 SP-09 SP-000383 S1-000620 22.101 048 R4 C Service evolution 4.0.0 4.1.0 SP-09 SP-000391 S1-000573 22.101 049 R4 D Emergency Call 4.0.0 4.1.0 SP-09 SP-000405 S1-000649 22.101 050 R4 B Text Conversation 4.0.0 4.1.0 SP-09 SP-000383 S1-000625 22.101 043 R5 F Classification of services 4.0.0 5.0.0 SP-09 SP-000383 S1-000622 22.101 044 R5 B IP multimedia services 4.0.0 5.0.0 SP-09 SP-000383 S1-000621 22.101 045 R5 B IP multimedia session for Emergency call 4.0.0 5.0.0 SP-09 SP-000430 S1-000699 22.101 051 R5 C IM Number portability 4.0.0 5.0.0 SP-09 SP-000430 S1-000701 22.101 052 R5 F Introduction of IM CN Subsystem 4.0.0 5.0.0 SP-09 SP-000383 S1-000704 22.101 053 R5 F Subscription 4.0.0 5.0.0 SP-09 SP-000383 S1-000705 22.101 054 R5 F Roaming 4.0.0 5.0.0 SP-10 SP-000533 S1-000799 22.101 059 Rel-5 A Deleting Encrypted USIM-ME interface 5.0.0 5.1.0 TEI4 SP-11 SP-010053 S1-010072 22.101 063 Rel-5 A Handling of interactions between applications requiring the access to UE resources 5.1.0 5.2.0 Service Clean up R99 SP-11 SP-010054 S1-010208 22.101 065 Rel-5 A PLMN name indication 5.1.0 5.2.0 TEI4 SP-11 SP-010055 S1-010179 22.101 067 Rel-5 A CR to 22.101 on Introduction of CPHS features 5.1.0 5.2.0 UICC1-CPHS SP-11 SP-010056 S1-010210 22.101 069 Rel-5 A Display of service provider name in the UE 5.1.0 5.2.0 TEI4 SP-11 SP-010057 S1-010250 22.101 070 Rel-5 C CR to 22.101 on Clarifications on IMS emergency call support 5.1.0 5.2.0 EMC1-PS SP-12 SP-010262 S1-010505 22.101 072 Rel-5 A Replacement of references to 23.121 for R4 onwards 5.2.0 5.3.0 TEI4 SP-12 SP-010258 S1-010574 22.101 073 Rel-5 C Subscription and Provisioning 5.2.0 5.3.0 TEI5 SP-12 SP-010255 S1-010577 22.101 075 Rel-5 A Addition of a Streaming paragraph 5.2.0 5.3.0 PSTREAM SP-12 SP-010263 S1-010351 22.101 077 Rel-5 A CS Multimedia fallback to speech 5.2.0 5.3.0 TEI4 SP-12 SP-010253 S1-010595 22.101 080 Rel-5 A Clarification of PLMN Name Indication and Service Provider Name Indication feature. 5.2.0 5.3.0 SPANME SP-13 SP-010441 S1-010832 22.101 084 Rel-5 A Addition of a statement on parameter storage on the SIM/USIM. 5.3.0 5.4.0 TEI4 SP-13 SP-010436 S1-010889 22.101 086 1 Rel-5 F Definition of Home Environment 5.3.0 5.4.0 VHE1 SP-15 SP-020052 S1-020609 22.101 087 Rel-5 B CR 22.101 Rel.5 B Service change and fallback for UDI/RDI multimedia calls 5.4.0 5.5.0 SCUDIF SP-15 SP-020049 S1-020510 22.101 088 Rel-5 C CR to 22.101on IMS access 5.4.0 5.5.0 43000 SP-15 SP-020051 S1-020613 22.101 089 Rel-5 C CR to 22.101 on on USIM support in Rel-5 GSM only terminals 5.4.0 5.5.0 UICC1 SP-15 SP-020050 S1-020658 22.101 090 Rel-5 C CR to 22.101 on Access to IMS services using ISIM NOTE: special dispensation was given by SA #15 to allow some leeway on the section numbering. 5.4.0 5.5.0 TEI/ISIM SP-15 SP-020045 S1-020457 22.101 092 - Rel-5 A Editorial CR to correct terms and references 5.4.0 5.5.0 CORRECT SP-15 SP-020126 22.101 093 Rel-5 F Correction of references to obsolete SIP RFC 2543 IETF specification 5.4.0 5.5.0 IMS-CCR SP-16 SP-020381 22.101 095 1 Rel-5 F CR to 22.101 v5.5.0 on REL5 clean up 5.5.0 5.6.0 IMS SP-16 SP-020255 S1-020848 22.101 096 Rel-6 D CR to 22.101 v5.5.0 on Editorial for REL6 5.5.0 6.0.0 IMS SP-17 SP-020557 S1-021849 22.101 103 Rel-6 F Clarification of SIM support in Rel-6 6.0.0 6.1.0 TEI4 SP-17 SP-020557 S1-021755 22.101 104 Rel-6 B CR to 22.101 Removal of implementation details for directory number in SMS and other services 6.0.0 6.1.0 TEI6 SP-17 SP-020557 S1-021775 22.101 105 Rel-6 F CR to 22.101 Rel-6 Clean up of IMS Rel 6 to re-instate requirements 6.0.0 6.1.0 IMS SP-18 SP-020658 S1-022064 22.101 107 Rel-6 B CR to 22.101 on IMS number portability rev of 1909 6.1.0 6.2.0 IMS SP-18 SP-020658 S1-022119 22.101 108 Rel-6 B CR to 22.101 Rel 6 on Emergency calls 6.1.0 6.2.0 EMC1 SP-18 SP-020666 S1-022263 22.101 109 Rel-6 B CR to 22.101 on WLAN interworking 6.1.0 6.2.0 WLAN SP-18 SP-020651 S1-022340 22.101 113 Rel-6 A CR to 22.101 on Support of SIM and USIM in REL-6 6.1.0 6.2.0 TEI5 SP-19 SP-030022 S1-030215 22.101 114 - Rel-6 B Simultaneous connection to 3GPP systems and I-WLANs 6.2.0 6.3.0 WLAN-CR SP-19 SP-030035 S1-030269 22.101 115 - Rel-6 B Requirements for Network Sharing in Rel-6 6.2.0 6.3.0 NTShar-CR SP-19 SP-030148 S1-030257 22.101 117 - Rel-6 A CR to 22.101 Rel 6 on SIM support 6.2.0 6.3.0 TEI5 SP-20 SP-030351 22.101 125 1 Rel-6 A Alignment of Subscriber Identification requirements to current implementation 6.3.0 6.4.0 TEI5 SP-21 SP-030457 S1-030911 22.101 128 - Rel-6 A Clarification on USIM-based access to IMS 6.4.0 6.5.0 IMS SP-21 SP-030492 S1-031049 22.101 132 Rel-6 C Cleanup and modifications on identification of emergency numbers in 22.101 Rel-6 6.4.0 6.5.0 EMC1 SP-21 SP-030534 S1-031061 22.101 134 1 Rel-6 A Support of Release 4 SIM in Release 6 6.4.0 6.5.0 TEI5 SP-22 SP-030700 S1-031339 22.101 135 - Rel-6 B Automatic Device Detection 6.5.0 6.6.0 TEI SP-22 SP-030700 S1-031342 22.101 136 - Rel-6 C Correction of Core Network emergency call requirements 6.5.0 6.6.0 EMC1 SP-22 SP-030687 S1-031344 22.101 137 - Rel-6 C Clarification of emergency call requirements 6.5.0 6.6.0 EMC1 SP-22 SP-030790 - 22.101 141 - Rel-6 A Removal of unnecessary numbers from the ME default emergency number list (Rel-6) 6.5.0 6.6.0 EMC1 SP-23 SP-040084 S1-040198 22.101 145 - Rel-6 A Alignment to TS 31.102 on FDN/BDN unsupported terminal procedure. 6.6.0 6.7.0 TEI SP-23 SP-040091 S1-040215 22.101 146 - Rel-6 B Improvements to Circuit Switched Video and Voice Service procedures 6.6.0 6.7.0 CS-VVS SP-23 SP-040101 S1-040258 22.101 150 - Rel-6 D Extraction of redundant WLAN information – now in WLAN TS22.234 6.6.0 6.7.0 WLAN SP-23 SP-040101 S1-040262 22.101 151 - Rel-6 D Extraction of redundant WLAN related simultaneous connection information [ now in WLAN TS22.234] 6.6.0 6.7.0 WLAN SP-24 SP-040288 S1-040427 22.101 152 - Rel-6 F Correction of UICC related text. 6.7.0 6.8.0 TEI SP-24 SP-040292 S1-040537 22.101 154 - Rel-6 F Editorial Correction of R5 reference 6.7.0 6.8.0 IMS2 SP-24 SP-040301 S1-040513 22.101 153 - Rel-7 B Termination of location privacy override for emergency calls 6.7.0 7.0.0 LCS2; EMC1 SP-27 SP-050058 S1-050161 22.101 158 - Rel-7 A Clean-up in Core Network Operator Name Indication section (22.101) 7.0.0 7.1.0 NTShar SP-27 SP-050059 S1-050252 22.101 160 - Rel-7 A Removal of Reference to TS 22.121 7.0.0 7.1.0 TEI7 SP-28 SP-050216 S1-050519 22.101 163 - Rel-7 A Clarification on optionality of Service Provider Name indication 7.1.0 7.2.0 TEI-6 SP-28 SP-050225 S1-050581 22.101 164 - Rel-7 B Voice call continuity requirements 7.1.0 7.2.0 VCC SP-29 SP-050522 S1-050793 22.101 0165 - Rel-7 F Correction of emergency number example 7.2.0 7.3.0 TEI7 SP-29 SP-050522 S1-050873 22.101 0166 - Rel-7 F Requirements on the type of emergency 7.2.0 7.3.0 TEI7 SP-29 SP-050522 S1-050796 22.101 0167 - Rel-7 C Modification to chapter 4.2 on service capabilities 7.2.0 7.3.0 TEI7 SP-29 SP-050518 S1-050896 22.101 0168 - Rel-7 F Refinement of general description of VCC 7.2.0 7.3.0 VCC SP-29 SP-050518 S1-050897 22.101 0169 - Rel-7 C Charging requirements for voice call continuity 7.2.0 7.3.0 VCC SP-29 SP-050518 S1-050936 22.101 0171 1 Rel-7 C Clarification of VCC Triggers 7.2.0 7.3.0 VCC SP-29 SP-050522 S1-050906 22.101 0172 - Rel-7 F Clarification on the identification of emergency numbers 7.2.0 7.3.0 EMC1 SP-29 SP-050522 S1-050883 22.101 0173 - Rel-7 B Provisioning parameters stored on USIM 7.2.0 7.3.0 TEI7 SP-29 SP-050518 S1-050934 22.101 0174 - Rel-7 C Supplementary Service Requirements for VCC 7.2.0 7.3.0 VCC SP-30 SP-050750 S1-051145 22.101 0176 - Rel-7 F Correcting reference to OMA DM and Client provisioning specifications 7.3.0 7.4.0 TEI7 SP-30 SP-050746 S1-051209 22.101 0177 - Rel-7 F Clarification of supplementary servces requirements for VCC 7.3.0 7.4.0 VCC SP-30 SP-050746 S1-051220 22.101 0178 - Rel-7 F Clarification of VCC Triggers 7.3.0 7.4.0 VCC SP-30 SP-050737 S1-051236 22.101 0179 - Rel-7 A Introduction of Cell capability indicator 7.3.0 7.4.0 TEI6 SP-30 SP-050805 - 22.101 0180 1 Rel-7 B Emergency sip uri to be stored in MT 7.3.0 7.4.0 EMC1 SP-31 SP-060207 - 22.101 0182 1 Rel-8 F Inclusion of AIPN within the 3GPP service principles specification 7.4.0 8.0.0 AIPN SP-32 SP-060448 - 22.101 0186 1 Rel-8 F Corrections to align the Rel-8 and (latest) Rel-7 versions of TS 22.101 8.0.0 8.1.0 TEI8 SP-32 SP-060316 S1-060561 22.101 0187 - Rel-8 B VCC Additional flexibility 8.0.0 8.1.0 VCC SP-32 SP-060315 S1-060621 22.101 0191 - Rel-8 A Clarification of IMS voice service 8.0.0 8.1.0 VCC SP-32 SP-060435 - 22.101 0192 1 Rel-8 B QoS Parameters Provisioning 8.0.0 8.1.0 TEI8 SP-32 SP-060449 - 22.101 0193 2 Rel-8 B High Speed Interface between the Terminal and the UICC 8.0.0 8.1.0 TEI8 SP-32 SP-060320 S1-060626 22.101 0194 - Rel-8 F Clarification on handling of emergency number 8.0.0 8.1.0 TEI-8 SP-33 SP-060470 S1-060939 22.101 0197 - Rel-8 A Clarification on Domain Selection for MO and MT Operations 8.1.0 8.2.0 TEI8 SP-33 SP-060468 S1-060950 22.101 0199 - Rel-8 A Emergency calls and ISIM 8.1.0 8.2.0 EMC1 SP-33 SP-060472 S1-060964 22.101 0200 - Rel-8 B Requirements for the determination of cell capability usage - when requested by CN 8.1.0 8.2.0 TEI8 SP-34 SP-060777 S1-061321 22.101 0195 3 Rel-8 C Requirements for the addition of a data component to TS12 emergency calls and eCall MSD (data) transfer requirements 8.2.0 8.3.0 TEMCD SP-34 SP-060773 S1-061406 22.101 0201 - Rel-8 B Serving Environment / Mobile Virtual Network Identification 8.2.0 8.3.0 TEI8 SP-34 SP-060765 S1-061347 22.101 0204 - Rel-8 A Removal of IMS emergency call identifier 8.2.0 8.3.0 EMC1 SP-35 SP-070130 S1-070190 22.101 0205 1 Rel-8 D Addition of Evolved 3GPP System description and corrections to references 8.3.0 8.4.0 SAE-R SP-35 SP-070134 S1-070299 22.101 0207 1 Rel-8 B Registration in Densely-populated area 8.3.0 8.4.0 RED SP-36 SP-070355 S1-070673 22.101 0211 1 Rel-8 C Graphic format of PLMN name 8.4.0 8.5.0 TEI8 SP-36 SP-070354 S1-070802 22.101 0214 1 Rel-8 A Alignment of SPDI definition between TS22.101 and TS31.102 8.4.0 8.5.0 TEI5 SP-36 SP-070472 S1-070790 22.101 0215 2 Rel-8 F Correction of the backward compatibility requirement for the HSP interface 8.4.0 8.5.0 TEI-8 SP-37 SP-070661 S1-071314 22.101 218 2 Rel-8 B ICS Requirements – General 8.5.0 8.6.0 ICS-RA SP-37 SP-070661 S1-071315 22.101 221 2 Rel-8 B ICS Requirements - Service Consistency 8.5.0 8.6.0 ICS-RA SP-37 SP-070661 S1-071316 22.101 222 2 Rel-8 B ICS Requirements - Service Continuity 8.5.0 8.6.0 ICS-RA SP-37 SP-070661 S1-071317 22.101 225 2 Rel-8 B ICS Requirements - IMS Services 8.5.0 8.6.0 ICS-RA SP-37 SP-070662 S1-070995 22.101 216 1 Rel-8 C Clarification on graphic format of PLMN name 8.5.0 8.6.0 TEI8 SP-37 SP-070676 - 22.101 217 4 Rel-8 B Requirements for eCall 8.5.0 8.6.0 EData SP-38 SP-070850 S1-071712 22.101 0232 1 Rel-8 B ICS - Clarification of Service Continuity 8.6.0 8.7.0 ICSRA SP-38 SP-070850 S1-071713 22.101 0233 1 Rel-8 B ICS - Service Continuity Requirements 8.6.0 8.7.0 ICSRA SP-38 SP-070850 S1-071714 22.101 0234 1 Rel-8 B ICS - Roaming Support 8.6.0 8.7.0 ICSRA SP-38 SP-070850 S1-071715 22.101 0235 1 Rel-8 B Clarify UE requirements for ICS 8.6.0 8.7.0 ICS-RA SP-38 SP-070861 S1-071932 22.101 0229 2 Rel-8 B Requirements for Emergency Call-Back 8.6.0 8.7.0 TEI8 SP-38 SP-070862 S1-071927 22.101 0241 2 Rel-8 B CS IP Interconnection requirement 8.6.0 8.7.0 IPINTERC SP-39 SP-080036 S1-080309 22.101 0237 6 Rel-8 B Requirements for "In Case of Emergency" (ICE) information 8.7.0 8.8.0 ICE SP-39 SP-080042 S1-080296 22.101 0250 1 Rel-8 F Update the related contents about "Evolved Packet System" 8.7.0 8.8.0 AIPN-SAE SP-39 SP-080041 S1-080297 22.101 0251 1 Rel-8 F CS multimedia calls 8.7.0 8.8.0 TEI8 SP-39 SP-080041 S1-080298 22.101 0252 1 Rel-8 D correction of wrong referencing 8.7.0 8.8.0 TEI8 SP-39 SP-080032 S1-080314 22.101 0253 2 Rel-8 B Requirements for transfer for data during emergency calls 8.7.0 8.8.0 EData SP-39 SP-080032 S1-080266 22.101 0254 1 Rel-8 B Requirements for the transfer of eCall Minimum Set of Data 8.7.0 8.8.0 EData SP-39 SP-080043 S1-080337 22.101 0255 2 Rel-8 B RAT indicator 8.7.0 8.8.0 TEI8 SP-39 SP-080039 S1-080287 22.101 0256 1 Rel-8 B ICS requirement for roaming 8.7.0 8.8.0 ICSRA SP-39 SP-080040 S1-080237 22.101 0262 1 Rel-8 B Additional requirements for CS IP interconnection 8.7.0 8.8.0 IPINTERC SP-39 SP-080043 S1-080299 22.101 0263 1 Rel-8 B Addition of Unique Device Identifier to Calling Line Identification 8.7.0 8.8.0 TEI8 SP-39 SP-080040 S1-080327 22.101 0265 1 Rel-8 B Clarification of requirements for CS IP interconnection 8.7.0 8.8.0 IPINTERC SP-40 SP-080308 S1-080746 22.101 0267 3 Rel-8 F Emergency Call Interaction 8.8.0 8.9.0 EMC1 SP-40 SP-080299 S1-080581 22.101 0269 1 Rel-8 C eCall call back requirements clarification 8.8.0 8.9.0 EDATA SP-40 SP-080298 S1-080735 22.101 0270 3 Rel-8 F Common IMS Proposals - Requirements for Emergency Calls 8.8.0 8.9.0 CIMS_3GPP2 SP-40 SP-080306 S1-080715 22.101 0271 1 Rel-8 F Correction of reference for PLMN architecture 8.8.0 8.9.0 AIPN-SAE SP-40 SP-080299 S1-080714 22.101 0272 1 Rel-8 F Corrections to general requirements for emergency calls 8.8.0 8.9.0 EData SP-40 SP-080308 S1-080560 22.101 0274 - Rel-8 F Clarification of IMS Emergency Calls 8.8.0 8.9.0 EMC1 SP-40 SP-080299 S1-080743 22.101 0275 1 Rel-8 C Reconfigurable eCall only terminal access to test and reconfiguration services 8.8.0 8.9.0 EDATA SP-40 SP-080302 S1-080705 22.101 0276 - Rel-8 F Correction of ICE requirements 8.8.0 8.9.0 ICE SP-40 SP-080311 S1-080774 22.101 0268 3 Rel-9 B Requirements for Service Alignment and Migration 8.8.0 9.0.0 ETWS-S1 SP-41 SP-080498 S1-082192 22.101 0282 1 Rel-9 F Clarification on IMS services supported by ICS 9.0.0 9.1.0 ICSRA SP-41 SP-080643 - 22.101 0280 2 Rel-9 F RED optimization of location update 9.0.0 9.1.0 RED SP-42 SP-080884 22.101 0290 6 Rel-9 A ICS Service Continuity 9.1.0 9.2.0 CIMS8 SP-42 SP-080779 S1-084415 22.101 281 2 Rel-9 B User Data Convergence Requirements 9.1.0 9.2.0 UDC SP-42 SP-080781 S1-084177 22.101 0283 2 Rel-9 F VCC for emergency calls 9.1.0 9.2.0 IMS_EMER_GPRS_EPS SP-42 SP-080784 S1-084424 22.101 0290 3 Rel-9 C ICS Service Continuity 9.1.0 9.2.0 TEI9 SP-42 SP-080783 S1-084404 22.101 0299 3 Rel-9 B UICC applications access to IMS 9.1.0 9.2.0 TEI9 SP-42 SP-080781 S1-084096 22.101 300 - Rel-9 F Make IMS emergency calls available in all access systems 9.1.0 9.2.0 TEI9 SP-43 SP-090079 S1-090174 22.101 0307 1 Rel-9 A Clarification and enhancement of ciphering indicator feature 9.2.0 9.3.0 TEI9 SP-44 SP-090377 S1-091407 22.101 0312 4 Rel-9 F Domain selection for emergency call 9.3.0 9.4.0 IMS_EMER_GPRS_EPS SP-44 SP-090369 S1-091393 22.101 0313 - Rel-9 A eCall - PSAP acknowledgement to the IVS 9.3.0 9.4.0 Edata SP-45 SP-090475 S1-093290 22.101 0315 1 Rel-9 A Minimise delay to emergency voice calls 9.4.0 9.5.0 EDATA SP-45 SP-090480 S1-093282 22.101 321 1 Rel-9 F Domain selection for emergency call 9.4.0 9.5.0 IMS_EMER_GPRS_EPS SP-45 SP-090483 S1-093286 22.101 0316 1 Rel-10 F Add reference to MSD specification 9.4.0 10.0.0 EDATA SP-45 SP-090484 S1-093341 22.101 0320 4 Rel-10 B Selected IP Traffic Offload 9.4.0 10.0.0 LIPA_SIPTO SP-45 SP-090483 S1-093261 22.101 322 1 Rel-10 F Clarification of emergency call back requirements 9.4.0 10.0.0 TEI10 SP-46 SP-090887 S1-094259 22.101 0336 1 Rel-10 A Providing eCall indication to the PSAP 10.0.0 10.1.0 EDATA SP-46 SP-090836 S1-094262 22.101 0338 - Rel-10 A Remove requirement for operator determined eCall call-back duration. 10.0.0 10.1.0 EDATA SP-46 SP-090842 S1-094272 22.101 0330 1 Rel-10 A User data repository shall be possible to be shared among different PLMNs that have trusted relationships 10.0.0 10.1.0 UDC SP-46 SP-090844 S1-094499 22.101 0327 2 Rel-10 A Use of GTT-IP for IMS emergency calls (mirror) 10.0.0 10.1.0 TEI9 SP-46 SP-090846 S1-094496 22.101 0328 1 Rel-10 B ICS Enhancements 10.0.0 10.1.0 TEI10 SP-46 SP-090849 S1-094300 22.101 0325 3 Rel-10 B Roaming and Mobility aspects for Selected IP Traffic Offload 10.0.0 10.1.0 LIPA_SIPTO SP-47 SP-100187 S1-100321 22.101 0339 2 Rel-10 B SIPTO requirements common for macro network and H(e)NB subsystems 10.1.0 10.2.0 LIPA_SIPTO SP-47 SP-100188 S1-100445 22.101 0332 6 Rel-10 C Clarification to Emergency call selection prioritization 10.1.0 10.2.0 TEI10 SP-47 SP-100188 S1-100442 22.101 0340 1 Rel-10 C Clarification on ICS wrt data (CS) and fax 10.1.0 10.2.0 TEI10 SP-47 SP-100191 S1-100431 22.101 0343 2 Rel-10 B IMS emergency call enhancements 10.1.0 10.2.0 IESE SP-48 SP-100431 S1-101060r 22.101 0347 6 Rel-10 B Addition of Requirement for UDC Data Model 10.2.0 10.3.0 TEI10 SP-48 SP-100401 S1-101067 22.101 0350 - Rel-10 F Correction of reference 10.2.0 10.3.0 IESE SP-49 SP-100585 S1-102403 22.101 0353 2 Rel-11 B SIPTO mobility/continuity 10.3.0 11.0.0 SIPTO_SC SP-51 SP-110168 S1-110088 22.101 0360 - Rel-11 F Clarification on Service Continuity for SIPTO 11.0.0 11.1.0 SIPTO_SC SP-52 SP-110373 S1-111410 22.101 0367 3 Rel-11 B IMS emergency call requirements for additional media types 11.1.0 11.2.0 NOVES SP-52 SP-110376 S1-111209 22.101 0369 - Rel-11 D Removing text discrepancy between Rel-10 and Rel-11 for UDC Data Model 11.1.0 11.2.0 TEI11 SP-52 SP-110418 - 22.101 0372 2 Rel-11 A IMS emergency calls 11.1.0 11.2.0 IMS_EMER_GPRS_EPS Correction of typo on cover page 11.2.0 11.2.1 SP-53 SP-110582 S1-112392 22.101 0373 1 Rel-11 F SIPTO in the Mobile Operator Network and Local Residential/Enterprise Network 11.2.0 11.3.0 TEI11 SP-53 SP-110576 S1-112101 22.101 0379 - Rel-11 B IMS emergency call support with other media handover considerations 11.2.0 11.3.0 NOVES SP-53 SP-110576 S1-112344 22.101 0380 1 Rel-11 B Notification of IMS emergency call support with other media 11.2.0 11.3.0 NOVES SP-53 SP-110576 S1-112350 22.101 0385 3 Rel-11 B Domain Selection for IMS emergency calls with additional media types 11.2.1 11.3.0 NOVES SP-53 SP-110579 S1-112385 22.101 0374 1 Rel-11 F SIPTO Service Continuity 11.2.0 11.3.0 SIPTO_SC SP-53 SP-110579 S1-112393 22.101 0378 2 Rel-11 C Clarification on collection of traffic and signalling for SIPTO 11.2.0 11.3.0 SIPTO_SC SP-53 SP-110582 S1-112025 22.101 0376 - Rel-11 F Correction of clause numbers and editorial corrections 11.2.1 11.3.0 TEI11 SP-53 SP-110651 S1-112328 22.101 0383 3 Rel-11 F Moving "Network provided destination for uplink data" requirement from 22.368 into 22.101 11.2.1 11.3.0 SIMTC SP-53 SP-110651 S1-112329 22.101 0384 4 Rel-11 F Moving PS-Only requirements from 22.368 into 22.101 11.2.1 11.3.0 SIMTC SP-54 SP-110811 S1-113245 22.101 0387 1 Rel-11 F IMS Multimedia Emergency Session support for UEs in Limited Service Mode 11.3.0 11.4.0 NOVES SP-54 SP-110811 S1-113249 22.101 0388 2 Rel-11 F Correction and removal of inconsistencies to IMS Emergency call when using other media 11.3.0 11.4.0 NOVES SP-54 SP-110811 S1-113248 22.101 0390 2 Rel-11 F Indication of supported media during an IMS multimedia emergency session 11.3.0 11.4.0 NOVES SP-54 SP-110811 S1-113250 22.101 0391 1 Rel-11 F Handover of other media to networks that do not support IMS emergency voice calls 11.3.0 11.4.0 NOVES SP-54 SP-110873 S1-113093r 22.101 0392 2 Rel-11 F Media allowed on callback from PSAP 11.3.0 11.4.0 NOVES SP-54 SP-110811 S1-113094 22.101 0393 - Rel-11 F Routing IMS multimedia sessions towards the PSAP 11.3.0 11.4.0 NOVES SP-54 SP-110813 S1-113098 22.101 0394 - Rel-11 B PS additional number 11.3.0 11.4.0 TEI11 SP-55 SP-120103 S1-120256 22.101 0401 1 Rel-11 F PS only subscriptions with SMS support 11.4.0 11.5.0 SIMTC SP-55 SP-120105 S1-120346 22.101 0400 4 Rel-12 B Introduction of Small Data Applications requirements 11.4.0 12.0.0 TEI12 SP-56 SP-120286 S1-121314 22.101 0409 1 Rel-12 A Emergency calls from non CSG members in CSG cells 12.0.0 12.1.0 EHNB SP-56 SP-120288 S1-121396 22.101 0412 1 Rel-12 A Clarification of PS additional numbers requirement 12.0.0 12.1.0 TEI11 SP-56 SP-120288 S1-121392 22.101 0415 - Rel-12 A Modification of how ME treats emergency call type(s) 12.0.0 12.1.0 TEI11 SP-57 SP-120519 S1-122463 22.101 0423 1 Rel-12 A Correction of UE mandatory features 12.1.0 12.2.0 TEI8 SP-57 SP-120528 S1-122221 22.101 0416 3 Rel-12 B Definitions for integration of Single Sign-On (SSO) frameworks with 3GPP networks 12.1.0 12.2.0 SSO_int SP-57 SP-120528 S1-122433 22.101 0417 2 Rel-12 B Requirements for integration of Single Sign-On (SSO) frameworks with 3GPP networks 12.1.0 12.2.0 SSO_int SP-58 SP-120868 S1-124504 22.101 0433 5 Rel-12 D MSISDN-less SMS Handling 12.2.0 12.3.0 MTCe-SRM SP-58 SP-120919 S1-124416 22.101 0434 4 Rel-12 B Addition of UPCON Requirements 12.2.0 12.3.0 UPCON SP-59 SP-130106 S1-131033 22.101 0444 - Rel-12 D Clarification of RAN user plane congestion definition 12.3.0 12.4.0 UPCON SP-59 SP-130112 S1-131226 22.101 0445 3 Rel-12 B Add Requirement on emergency IM CN subsystem 12.3.0 12.4.0 ESID SP-61 SP-130413 S1-134180 22.101 0463 1 Rel-13 B E-UTRAN Sharing Enhancements 12.4.0 13.0.0 RSE SP-62 SP-130601 S1-135293 22.101 0464 2 Rel-13 D Editorial fixes to RAN Sharing Enhancements 13.0.0 13.1.0 RSE SP-62 SP-130601 S1-135309 22.101 0465 3 Rel-13 B Support for Load Balancing in Shared E-UTRAN 13.0.0 13.1.0 RSE SP-62 SP-130601 S1-135310 22.101 0466 3 Rel-13 B Additional RAN Sharing Requirements 13.0.0 13.1.0 RSE SP-62 SP-130601 S1-135294 22.101 0468 2 Rel-13 C Clarification of Hosting E-UTRAN Operator role 13.0.0 13.1.0 RSE SP-62 SP-130601 S1-135313 22.101 0469 3 Rel-13 C Adding explanatory text to requirements on E-UTRAN Sharing 13.0.0 13.1.0 RSE SP-62 SP-130601 S1-135312 22.101 0470 3 Rel-13 B Enabling Dynamic capacity negotiation 13.0.0 13.1.0 RSE SP-63 SP-140066 S1-140230 22.101 0471 1 Rel-13 C RSE load balancing under EPC congestion situations 13.1.0 13.2.0 RSE SP-65 SP-140501 S1-143604 22.101 0473 5 Rel-13 B Exposure of network service and capabilities to 3rd party 13.2.0 13.3.0 SEES SP-65 SP-140508 S1-143607 22.101 0476 4 Rel-13 B Co-ordinated SIPTO Change of P-GW 13.2.0 13.3.0 CSIPTO SP-65 SP-140510 S1-143279 22.101 0479 1 Rel-13 C Definition of (S)Gi-LAN 13.2.0 13.3.0 FMSS SP-65 SP-140510 S1-143556 22.101 0478 3 Rel-13 B Requirements for Flexible Mobile Steering Service 13.2.0 13.3.0 FMSS SP-66 SP-140755 S1-144611 22.101 481 2 Rel-13 B GERAN & UTRAN Sharing, change to the title of Section 28 and update to clause 28.1 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144617 22.101 482 2 Rel-13 B GERAN & UTRAN Sharing, new clauses 28.3 and 28.3.1 (Allocation of Shared GERAN & UTRAN requirements). 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144618 22.101 483 2 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.2 (OA&M access to the shared RAN). 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144533 22.101 484 1 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.3 (Generation and retrieval of usage and accounting information). 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144534 22.101 485 1 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.4 (MDT Collection) 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144640 22.101 486 3 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.5 (PWS Support) 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144619 22.101 487 2 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.6 (Support for load balancing). 13.3.0 13.4.0 GUSH SP-66 SP-140755 S1-144636 22.101 488 3 Rel-13 B GERAN & UTRAN Sharing, new clause 28.3.7 (Dynamic capacity negotiation). 13.3.0 13.4.0 GUSH SP-66 SP-140781 S1-144528 22.101 493 - Rel-13 A eCall mode of operation 13.3.0 13.4.0 EDATA SP-66 SP-140751 S1-144556 22.101 494 - Rel-13 F Align the MTC monitoring requirements with Service Exposure requirements 13.3.0 13.4.0 TEI13 SP-67 SP-150039 S1-150214 22.101 495 2 Rel-13 F Update of Definitions 13.4.0 13.5.0 GUSH SP-68 SP-150272 S1-151547 22.101 499 3 Rel-14 C Requirement to support domain selection between VoLTE and CDMA CS 13.5.0 14.0.0 eDSVCC SP-68 SP-150276 S1-151536 22.101 496 3 Rel-14 B Update of eCall definition to include IMS emergency call based eCall 13.5.0 14.0.0 EIEI SP-68 SP-150276 S1-151537 22.101 497 2 Rel-14 B Support of IMS emergency calls in ICS 13.5.0 14.0.0 EIEI SP-68 SP-150276 S1-151538 22.101 498 2 Rel-14 B Update of transfer of MSD to include IMS emergency call based eCall 13.5.0 14.0.0 EIEI SP-69 SP-150539 S1-152457 22.101 501 1 Rel-14 B Enhancements for control of traffic from UE-based applications toward associated server 14.0.0 14.1.0 CATS SP-71 SP-160100 S1-160473 22.101 0508 2 Rel-14 B Requirements for enhancements on User Location Reporting Support 14.1.0 14.2.0 eULRS SP-71 SP-160112 S1-160300 22.101 0509 2 Rel-14 B Paging policy selection criteria requirements in LTE 14.1.0 14.2.0 PPEPO_LTE SP-71 SP-160110 S1-160474 22.101 0510 4 Rel-14 B Requirements for enhanced TV service 14.1.0 14.2.0 EnTV SP-71 SP-160096 S1-160173 22.101 0511 Rel-14 F Clarification of relationship between GTT and Real Time Text 14.1.0 14.2.0 TEI14 SP-71 SP-160116 S1-160541 22.101 0512 2 Rel-14 B Accounting for usage when using unlicensed access networks 14.1.0 14.2.0 USOS SP-71 SP-160114 S1-160302 22.101 0513 Rel-14 B Requirements for supporting third-party owned (S)Gi-LAN service 14.1.0 14.2.0 eFMSS SP-72 SP-160353 S1-161594 22.101 518 1 Rel-14 A Addition of Cellular IoT non-IP transport to exposed services and capabilities 14.2.0 14.3.0 SEES SP-73 SP-160541 S1-162532 22.101 0519 1 Rel-14 F Clarification of mobility management procedures for UEs in eCall mode 14.3.0 14.4.0 EIEI SP-74 SP-160888 S1-163032 22.101 0520 Rel-14 F Update of eCall MSD reference 14.4.0 14.5.0 TEI14 SP-74 SP-160888 S1-163392 22.101 0521 3 Rel-14 F Support of Emergency sessions over WLAN 14.4.0 14.5.0 TEI14 SP-74 SP-160889 S1-163452 22.101 0522 3 Rel-14 F Clarification of the consequences of eCall second attempts on another domain 14.4.0 14.5.0 EIEI SP-75 SP-170149 S1-171437 22.101 0524 2 Rel-14 A Alignment of UPCON Service Requirements 14.5.0 14.6.0 UPCON SP-75 SP-170154 S1-171445 22.101 0525 2 Rel-14 F Support of Emergency sessions over WLAN 14.5.0 14.6.0 TEI14 SP-75 SP-170155 S1-171275 22.101 0526 1 Rel-15 C Additon of 5G RAN sharing 14.5.0 15.0.0 SMARTER SP-75 SP-170162 S1-171415 22.101 0528 1 Rel-15 B Enhancement of the service exposure for background data transfer 14.5.0 15.0.0 eBT SP-75 SP-170247 S1-171440 22.101 0530 Rel-15 F Addition of informing PS Data Off state to Third-party 14.5.0 15.0.0 TEI15 SP-76 SP-170437 S1-172231 22.101 0535 1 Rel-15 A Adding Device Triggering to the Exposed Services and Capabilities 15.0.0 15.1.0 SEES SP-76 SP-170443 S1-172281 22.101 0532 2 Rel-15 F Correction of 5G-RAN sharing => not implementable, written on another spec (22.011) 15.0.0 15.1.0 SMARTER SP-76 SP-170447 S1-172235 22.101 0536 1 Rel-15 B Requirements for access to restricted local operator services 15.0.0 15.1.0 PARLOS SP-77 SP-170694 S1-173451 22.101 0537 1 Rel-15 D Remove restricted local operator services definition 15.1.0 15.2.0 PARLOS SP-77 SP-170692 S1-173260 22.101 0539 1 Rel-15 F Correction of the term "5G-RAN" to "NG-RAN" in RAN sharing 15.1.0 15.2.0 TEI15 SP-78 SP-170983 S1-174023 22.101 0541 Rel-15 A Support of Emergency sessions over WLAN 15.2.0 15.3.0 SEW2 SP-78 SP-170988 S1-174558 22.101 0542 2 Rel-15 F Clarification of PARLOS indicator and use without a UICC 15.2.0 15.3.0 PARLOS SP-79 SP-180132 S1-180601 22.101 0544 2 Rel-15 F Requiring the UE to set the restricted local operator service call type indicator when requesting RLOS 15.3.0 15.4.0 PARLOS SP-80 SP-180305 S1-181178 22.101 0545 Rel-15 F Alignment of requirements for access to restricted local operator services 15.4.0 15.5.0 PARLOS SP-80 SP-180305 S1-181396 22.101 0546 1 Rel-16 F Alignment of requirements for access to restricted local operator services 15.4.0 16.0.0 PARLOS SP-81 SP-180754 S1-182687 22.101 0552 Rel-16 A Local emergency numbers and emergency call types for use in the IM CN subsystem handling 16.0.0 16.1.0 TEI15 SP-81 SP-180767 S1-182704 22.101 0549 2 Rel-16 B UIA Service Requirements 16.0.0 16.1.0 UIA Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2019-06 SA#84 SP-190567 0558 3 A Solving user comprehension of network name in foreign language 16.2.0 2019-09 SA#85 SP-190810 0559 4 B Service requirements for enabling Multi-USIM devices support 17.0.0 2019-09 SA#85 SP-190810 0560 4 B Support of Emergency Services for Multi-USIM Devices 17.0.0 2019-12 SP-86 SP-191026 0562 F Clarify that emergency call-back is a regulatory requirement 17.1.0 2019-12 SP-86 SP-191026 0564 1 F Description for supporting MUSIM UE 17.1.0 2019-12 SP-86 SP-191035 0563 3 B IMS emergency requirement for NPN 17.1.0 2020-07 SA#88e SP-200569 0566 1 F Correction of UICC definition and references 17.2.0 2020-12 SA#90e SP-201041 570 1 B Service requirements for enhancing SFC service support 18.0.0 2021-03 SA#91e SP-210200 572 A Correction of reference to “Master Operator” and use of “Hosting E-UTRAN Operator” 18.1.0 2021-04 - - - - - Numbering of references corrected 18.1.1 2021-09 SA#93e SP-211096 0575 1 A Handling of emergency numbers in non-public networks 18.2.0 2021-09 SA#93e SP-211096 0576 D Correction of 'air interface' terminology 18.2.0 2021-12 SP-94 SP-211494 0578 1 B Addition of PIN requirement for credentials provisioning 18.3.0 2022-06 SA#96 SP-220434 582 D Clean-up of the references for quality improvement 18.4.0 2022-06 SA#96 SP-220429 583 1 B SMS over IMS to emergency response centre 18.4.0 2022-06 SA#96 SP-220434 584 1 F Emergency service support over ProSe Relays 18.4.0 2023-06 SA#100 SP-230525 0588 1 A Aligning the RAN sharing related definitions for quality improvement 18.5.0 2024-03 SA#103 SP-240201 0592 1 F Removal of non-implemented UIA requirements 18.6.0 2024-06 SA#104 SP-240787 0593 F Re-introduction of non-implemented UIA requirements 19.0.0 2024-09 SA#105 SP-241145 0595 2 B Clarification on the privacy requirements 19.1.0 2024-12 SA#106 SP-241762 0599 3 F Alignment on CEN eCall requirements 19.2.0 2024-12 SA#106 SP-241762 0598 1 D Correcting hanging paragraph and adding new header 19.2.0 |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 1 Scope | The purpose of this TS is to describe the service access procedures as presented to the user.
Definitions and procedures are provided in this TS for international roaming, national roaming and regionally provided service. These are mandatory in relation to the technical realization of the Mobile Station (UE). |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 1.1 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] Void
[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[3] 3GPP TS 23.122: "Non Access Stratum functions related to Mobile Station (MS) in idle mode".
[4] ITU-T Recommendation Q.1001: "General aspects of Public Land Mobile Networks".
[5] 3GPP TS 22.043: "Support of Localised Service Area (SoLSA). Stage 1".
[6] 3GPP TS 22.234: "Requirements on 3GPP system to wireless local area network (WLAN) interworking".
[7] 3GPP TS 22.101: "Service aspects; Service principles".
[8] 3GPP TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[9] Void
[10] 3GPP TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".
[11] Void
[12] Void
[13] 3GPP TS 36.331: "E-UTRA Radio Resource Control (RRC)".
[14] 3GPP TS 22.220: "Service requirements for Home NodeBs and Home eNodeBs".
[15] 3GPP2 C.S0004-A v6.0: "Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum Systems – Addendum 2"
[16] 3GPP TS 22.153: "Multimedia priority service".
[17] 3GPP TS 36.306: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities"
[18] 3GPP TS 43.064: " General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2"
[19] ITU-T Recommendation E.212: "The international identification plan for public networks and subscriptions"
[20] 3GPP TS 26.114: " IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction". |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 1.2 Definitions and abbreviations | |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 1.2.1 Definitions | In addition to those below, abbreviations used in this 3GPP TS are listed in 3GPP TR 21.905 [2].
3GPP PS Data Off: A feature which when configured by the HPLMN and activated by the user prevents transport via PDN connections or PDU sessions in 3GPP access of all IP packets except IP packets required by 3GPP PS Data Off Exempt Services.
3GPP PS Data Off Exempt Services: A set of operator services that are allowed even if the 3GPP PS Data Off feature has been activated in the UE by the user.
Disaster Condition: This is the condition that a government decides whether applicable or not based on, e.g. a natural disaster or a man-made disaster. When this condition applies service interruptions and failures will be mitigated.
PLMN: A Public Land Mobile Network (PLMN) is a network established and operated by an Administration or RPOA for the specific purpose of providing land mobile communication services to the public. It provides communication possibilities for mobile users. For communications between mobile and fixed users, interworking with a fixed network is necessary.
A PLMN may provide service in one, or a combination, of frequency bands.
As a rule, a PLMN is limited by the borders of a country. Depending on national regulations there may be more than one PLMN per country.
A relationship exists between each subscriber and his home PLMN (HPLMN). If communications are handled over another PLMN, this PLMN is referred to as the visited PLMN (VPLMN).
PLMN Area: The PLMN area is the geographical area in which a PLMN provides communication services according to the specifications to mobile users. In the PLMN area, the mobile user can set up calls to a user of a terminating network. The terminating network may be a fixed network, the same PLMN, another PLMN or other types of PLMN.
Terminating network users can also set up calls to the PLMN.
The PLMN area is allocated to a PLMN. It is determined by the service and network provider in accordance with any provisions laid down under national law. In general, the PLMN area is restricted to one country. It can also be determined differently, depending on the different telecommunication services, or type of UE.
If there are several PLMNs in one country, their PLMN areas may overlap. In border areas, the PLMN areas of different countries may overlap. Administrations will have to take precautions to ensure that cross border coverage is minimized in adjacent countries unless otherwise agreed.
NOTE 1: ITU-T Recommendation Q.1001 [4] does not contain a definition of the PLMN area.
System Area: The System Area is defined as the group of PLMN areas accessible by UEs.
Interworking of several PLMNs and interworking between PLMNs and fixed network(s) permit public land mobile communication services at international level.
NOTE 2: The System Area according to [4] Recommendation Q.1001 corresponds to the System Area.
Service Area: The Service Area is defined in the same way as the Service Area according to ITU-T Recommendation Q.1001 [4]. In contrast to the PLMN area it is not based on the coverage of a PLMN. Instead it is based on the area in which a fixed network user can call a mobile user without knowing his location. The Service Area can therefore change when the signalling system is being extended, for example.
Shared MCC: MCC assigned by ITU-T as shared MCC according to ITU-T E.212 [19], except within this specification for PLMN selection purposes the MCC of value 999 is not considered a shared MCC.
Regionally Provided Service: Regionally Provided Service is defined as a service entitlement to only certain geographical part(s) of a PLMN, as controlled by the network operator.
Localised Service Area (LSA): The localised service area concept shall give the operator a basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber. An LSA consists of a cell or a number of cells within a PLMN. (3GPP TS 22.043 [5]).
Tracking Area: E-UTRAN utilises Tracking Areas (TA) for UE access control, location registration, paging and mobility management. The TA is independent of Location Areas (LA) and Routing Areas (RA). A TA comprises one or more E-UTRA cells Service requirements for E-UTRAN are specified in 3GPP TS 22.278 [8]. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 1.2.2 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [2].
ACDC Application specific Congestion control for Data Communication
EAB Extended Access Barring
SSAC Service Specific Access Control |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 2 Roaming | |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 2.1 General requirements | A UE with a valid IMSI may roam and access service in the area authorized by the entitlement of the subscription.
If a communication has been established, the UE will in principle not suffer an interruption within the PLMN area (provided the entitlement of the subscription allows it). Exceptions are possible if no network resources or radio coverage are available locally.
However, if the UE leaves the PLMN area, an established communication may terminate. If the user then wants to continue, another network providing service has to be selected and a new communication has to be established (see clause 3).
Subject to roaming agreements, a visited network shall be able to prevent incoming roamers from using a particular radio access technology (e.g. when the home network has not implemented this radio access technology). |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 2.2 International roaming | International roaming is a service whereby a UE of a given PLMN is able to obtain service from a PLMN of another country.
The availability of International Roaming is subject to inter-PLMN agreements. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 2.3 National roaming | National Roaming is a service whereby a UE of a given PLMN is able to obtain service from another PLMN of the same country, anywhere, or on a regional basis.
The availability of National Roaming depends on the home PLMN of the requesting UE and the visited PLMN; it does not depend on subscription arrangements. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 2.4 Roaming in shared networks | The following requirements are applicable to GERAN, UTRAN, E-UTRAN and NG-RAN sharing scenarios:
- Mechanisms shall be specified to enable flexible allocation of visiting roamers among core network operators that have roaming agreements with the same roaming partners. The core network operators shall be able to pre-define their relative share of visiting roamers and distribute the visiting roamers that apply automatic network selection to different core networks connected to the radio access network accordingly.
- When network sharing exists between different operators and a user roams into the shared network it shall be possible for that user to register with a core network operator (among the network sharing partners) that the user’s home operator has a roaming agreement with, even if the operator is not operating a radio access network in that area.
- The selection of a core network operator among those connected to the shared radio access network can either be manual (i.e. performed by the user after obtaining a list of available core network operators) or automatic (i.e. performed by the UE according to user and operator preferred settings). For further information see clause 3.2. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3 Provisions for providing continuity of service | |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.1 Location registration | PLMNs shall provide a location registration function with the main purpose of providing continuity of service to UEs over the whole system area. The location registration function shall be such as to allow:
- Fixed subscribers to call a UE by only using the directory number of the UE irrespective of where the UE is located in the system area at the time of the call.
- UEs to access the system irrespective of the location of the UE.
- UEs to identify when a change in location area has taken place in order to initiate automatic location updating procedures. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2 Network selection | |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.1 General | The UE shall support both manual and automatic network selection mechanisms (modes). The UE shall select the last mode used, as the default mode, at every switch-on.
As an optional feature of the ME, the user shall be able to set a preference in the ME for the mode that shall be used at switch on. If set, then the ME shall select this preference rather than the default mode.
NOTE: By defaulting to the last mode used, e.g. manual network selection, the undesired automatic selection of an adjacent PLMN instead of the desired HPLMN in border areas, can be avoided at switch-on.
The user shall be given the opportunity to change mode at any time.
Except as defined below, the MMI shall be at the discretion of the UE manufacturer.
The UE shall contain display functions by which Available PLMNs and the Selected PLMN can be indicated.
In order not to confuse the user, the same definitions of PLMN names shall be applied consistently both in registered mode and in the list presented to the user when in manual mode.
In shared networks a radio access network can be part of more than one PLMN. This shall be transparent to the user, i.e. the UE shall be able to indicate those PLMNs to the user, and the UE shall support network selection among those PLMNs, as in non-shared networks. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2 Procedures | |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.1 General | In the following procedures the UE selects and attempts registration on PLMNs.
In this TS, the term "PLMN Selection" defines a UE based procedure, whereby candidate PLMNs are chosen, one at a time, for attempted registration.
A User Controlled PLMN Selector data field exists on the USIM to allow the user to indicate a preference for network selection. It shall be possible for the user to update the User Controlled PLMN Selector data field, but it shall not be possible to update this data field over the radio interface, e.g. using SIM Application Toolkit.
It shall be possible to have an Operator Controlled PLMN Selector list and a User Controlled PLMN Selector list stored on the SIM/USIM card. Both PLMN Selector lists may contain a list of preferred PLMNs in priority order. It shall be possible to have an associated Access Technology identifier e.g., NG-RAN, satellite NG-RAN, E-UTRAN (WB-S1 mode, NB-S1 mode), satellite E-UTRAN (WB-S1 mode, NB-S1 mode), UTRAN, GERAN or GERAN EC-GSM-IoT associated with each entry in the PLMN Selector lists.
For UEs supporting any, or a combination, of NB-IoT, GERAN EC-GSM-IoT [18] and Category M1 or M2 of E-UTRA [17], the 5G system shall support a mechanism to have an Operator controlled signal threshold per access technology on the USIM to be used for network selection. The signal threshold is specific for a certain Access Technology and shall apply to all PLMNs with the corresponding access technology combinations.
NOTE 1: The use of the Operator controlled signal threshold per access technology is intended for IoT stationary devices, without user interaction.
NOTE 2: The allowed range of the Operator controlled signal threshold per access technology is between the cell selection criterion and the high quality signal as defined in TS 23.122 [3].
The UE shall utilise all the information stored in the USIM related to network selection, e.g. HPLMN, Operator controlled PLMN Selector list, User Controlled PLMN Selector list, Forbidden PLMN list, Operator controlled signal threshold.
NOTE 3: A PLMN in a Selector list, including HPLMN, may have multiple occurrences, with different access technology identifiers.
The UE shall ignore those PLMN + access technology entries in the User Controlled PLMN selector and Operator Controlled PLMN selector lists where the associated Access Technology is not supported by the UE. In the case that there are multiple associated Access Technology identifiers in an entry the UE shall not ignore the entry if it includes any associated Access Technology that is supported by the UE.
It shall be possible to handle cases where one network operator accepts access from access networks with different network IDs. It shall also be possible to indicate to the UE that a group of PLMNs are equivalent to the registered PLMN regarding PLMN selection, cell selection/re-selection and handover.
It shall be possible for the home network operator to identify alternative Network IDs as the HPLMN. It shall be possible for the home network operator to store in the USIM an indication to the UE that a group of PLMNs are treated as the HPLMN regarding PLMN selection. Any PLMN to be declared as an equivalent to the HPLMN shall be present within the EHPLMN list and is called an EHPLMN. The EHPLMN list replaces the HPLMN derived from the IMSI. When the EHPLMN list is present, any PLMN in this list shall be treated as the HPLMN in all the network and cell selection procedures.
If registration on a PLMN is successful, the UE shall indicate this PLMN (the "registered PLMN") and be capable of making and receiving calls on it. The identity of the registered PLMN shall be stored on the SIM/USIM. However, if registration is unsuccessful, the UE shall ensure that there is no registered PLMN stored in the SIM/USIM.
If a registration is unsuccessful because the IMSI is unknown in the home network, or the UE is illegal, then the UE shall not allow any further registration attempts on any network, until the UE is next powered‑up or a SIM/USIM is inserted.
If the registration is unsuccessful due to the lack to service entitlement, specific behaviour by the UE may be required, see clause 3.2.2.4.
To avoid unnecessary registration attempts, lists of forbidden PLMNs, TAs and LAs are maintained in the UE, see clause 3.2.2.4 and 3GPP TS 23.122 [3].
Registration attempts shall not be made by UEs without a SIM/USIM inserted.
An UE/ME which has not successfully registered shall nevertheless be able to make emergency call attempts on an available PLMN (which supports the emergency call teleservice), without the need for the user to select a PLMN. An available PLMN is determined by radio characteristics (3GPP TS 23.122 [3]). |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.2 At switch-on or recovery from lack of coverage | If the Operator controlled signal threshold per access technology is set on the USIM, it shall be used for the selection of the last registered PLMN (and/or EHPLMN/HPLMN) and for the automatic mode network selection steps described in this clause. In particular, if the Operator controlled signal threshold per access technology is set on the USIM the UE shall only select a network if
- the network selection conditions as described below are met and
- the received signal quality of the candidate PLMN/access technology combination is equal to or higher than the Operator controlled signal threshold per access technology.
At switch on, when in coverage of the last registered PLMN as stored in the SIM/USIM, the UE will attach to that network.
As an option, in automatic selection mode, when no EHPLMN list is present, the UE may select the HPLMN. When the EHPLMN list is present, the UE may select the highest priority EHPLMN among the available EHPLMNs. The operator shall be able to control the UE behaviour by USIM configuration.
As an option, if the UE is in manual network selection mode at switch-on
- if the last registered PLMN is unavailable and no equivalent PLMN is available,
- and the UE finds it is in coverage of either the HPLMN or an EHPLMN
then the UE should register on the corresponding HPLMN or EHPLMN. The UE remains in manual mode.
If the UE returns to coverage of the PLMN on which it is already registered (as indicated by the registered PLMN stored in the SIM/USIM), the UE shall perform a location update to a new location area if necessary. As an alternative option to this, if the UE is in automatic network selection mode and it finds coverage of the HPLMN or any EHPLMN, the UE may register on the HPLMN (if the EHPLMN list is not present) or the highest priority EHPLMN of the available EHPLMNs (if the EHPLMN list is present) and not return to the last registered PLMN. If the EHPLMN list is present and not empty, it shall be used. The operator shall be able to control by USIM configuration whether an UE that supports this option shall follow this alternative behaviour.
NOTE: At switch-on and at recovery from lack of coverage, a UE in automatic network selection mode can attempt registration once the RPLMN or, if the above option is applicable, the HPLMN or EHPLMN is found on an access technology.
The default behaviour for a UE is to select the last registered PLMN.
If there is no registered PLMN stored in the SIM/USIM, or if this PLMN is unavailable and no equivalent PLMN is available, or the attempted registration fails, the UE shall follow one of the following procedures for network selection:
A) Automatic network selection mode
The UE shall select and attempt registration on other PLMNs, if available and allowable, if the location area is not in the list of "forbidden LAs for roaming" and the tracking area is not in the list of "forbidden TAs for roaming" (see 3GPP TS 23.122 [3]), in the following order:
i) An EHPLMN if the EHPLMN list is present or the HPLMN (derived from the IMSI) if the EHPLMN list is not present for preferred access technologies in the order specified. In the case that there are multiple EHPLMNs present then the highest priority EHPLMN shall be selected. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
ii) each entry in the "User Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
iii) each entry in the "Operator Controlled PLMN Selector with Access Technology" data field in the SIM/USIM (in priority order). It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
iv) other PLMN/access technology combinations with sufficient received signal quality (see 3GPP TS 23.122 [3]) in random order. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service;
v) all other PLMN/access technology combinations in order of decreasing signal quality. It shall be possible to configure a voice capable UE so that it shall not attempt registration on a PLMN if all cells identified as belonging to the PLMN do not support the corresponding voice service.
In the case of a UE operating in UE operation mode A or B, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM. This data field may be extended in the ME memory (see clause 3.2.2.4). In the case of a UE operating in UE operation mode C, an allowable PLMN is one which is not in the "Forbidden PLMN" data field in the SIM/USIM or in the list of "forbidden PLMNs for GPRS service" in the ME.
If the UE uses the Operator controlled signal threshold per access technology and no candidate PLMN/access technology combination fulfils the Operator controlled signal threshold criteria, the UE shall repeat the network selection without using the Operator controlled signal threshold per access technology.
If there is no available PLMN except for PLMNs in the "Forbidden PLMN" data field in the SIM/USIM, and the available PLMNs indicate that Disaster Condition applies, this PLMN shall be considered allowable for registration to the UE while the Disaster Condition is applicable.
If successful registration is achieved, the UE shall indicate the selected PLMN.
If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE shall obtain user consent for restricted local operator services and the UE may use a list of preferred PLMNs for restricted local operator services stored in the ME. If none of the preferred PLMNs for restricted local operator services is available, the UE shall select any available PLMN offering restricted local operator services. If one of these PLMNs for restricted local operator service is chosen, the UE shall indicate the choice. If none are selected, the UE shall wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.
If registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services has been found, the UE shall indicate "no service" to the user, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure. When registration cannot be achieved, different (discontinuous) PLMN search schemes may be used in order to minimize the access time while maintaining battery life, e.g. by prioritising the search in favour of BCCH carriers which have a high probability of belonging to an available and allowable PLMN.
B) Manual network selection mode
The UE shall indicate PLMNs, including "Forbidden PLMNs", which are available. If there are none, this shall also be indicated. The HPLMN of the user may provide on the USIM additional information about the available PLMNs, if this is provided then the UE shall indicate that information to the user. This information, provided as free text may include:
- Preferred partner;
- roaming agreement status;
- supported services.
Furthermore, the UE may indicate whether the available PLMNs are present on one of the PLMN selector lists (e.g. EHPLMN, User Controlled, Operator Controlled or Forbidden) as well as not being present on any of the lists.
For the purpose of presenting the names of the available PLMNs to the user, the ME shall use the USIM defined names if available or other PLMN naming rules in priority order as defined in 3GPP TS 22.101 [7] (Country/PLMN indication).
Any available PLMNs shall be presented in the following order:
i) HPLMN (if the EHPLMN list is not present); or if one or more of the EHPLMNs are available then based on an optional data field on the USIM either the highest priority available EHPLMN is to be presented to the user or all available EHPLMNs are presented to the user in priority order; if the data field is not present, then only the highest priority available EHPLMN is presented;
ii) PLMNs contained in the "User Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
iii) PLMNs contained in the "Operator Controlled PLMN Selector" data field in the SIM/USIM (in priority order);
iv) other PLMN/access technology combinations with sufficient received signal level (see 3GPP TS 23.122 [3]) in random order;
v) all other PLMN/access technology combinations in order of decreasing signal strength.
If a PLMN does not support voice services, then this shall be indicated to the user.
The user may select the desired PLMN and the UE shall attempt registration on this PLMN. (This may take place at any time during the presentation of PLMNs.)
If registration cannot be achieved on any PLMN and at least one PLMN offering restricted local operator services has been found, the UE shall obtain user consent for restricted local operator services and offer the user to select one of these networks. If one of these networks is selected, the UE shall indicate the selected PLMN, wait until a new PLMN is detected, or new location areas or tracking areas of an allowed PLMN are found which are not in the forbidden LA or TA list(s), and then repeat the procedure.
If the registration cannot be achieved on any PLMN and no PLMN offering restricted local operator services is selected, the UE shall indicate "No Service". The user may then select and attempt to register on another or the same PLMN following the above procedure. The UE shall not attempt to register on a PLMN which has not been selected by the user.
Once the UE has registered on a PLMN selected by the user, the UE shall not automatically register on a different PLMN unless:
i) The new PLMN is declared as an equivalent PLMN by the registered PLMN;
or,
ii) The user selects automatic mode.
If a PLMN is selected but the UE cannot register on it because registration is rejected with the cause "PLMN not allowed", the UE shall add the PLMN to the “Forbidden PLMN” list (clause 3.2.2.4.1). The UE shall not re-attempt to register on that network unless the same PLMN is selected again by the user.
If a PLMN is selected but the UE cannot register for PS services on it because registration is rejected with the cause "GPRS services not allowed in this PLMN", the UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network. The PLMN is added to the list "Forbidden PLMN's for GPRS services". The UE shall not re-attempt to register for E-UTRAN or UTRAN PS or GERAN PS on that network unless the same PLMN is selected again by the user. The reception of the cause "GPRS services not allowed in this PLMN", does not affect the CS service.
For requirements to restrict the access of a UE to one or several specific RATs see section 7.1.
If a PLMN is selected but the UE cannot register on it for other reasons, the UE shall, upon detection of a new LA (not in a forbidden LA list) of the selected PLMN, attempt to register on the PLMN.
If the UE is registered on a PLMN but loses coverage, different (discontinuous) carrier search schemes may be used to minimize the time to find a new valid BCCH carrier and maintain battery life, e.g. by prioritizing the search in favour of BCCH carriers of the registered PLMN. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.3 User reselection | At any time, the user may request the UE to initiate reselection and registration onto an alternative available PLMN, according to the following procedures, dependent upon the operating mode.
A) Automatic Network Selection Mode
The UE shall follow the procedure defined in clause 3.2.2.2.A) above, including the use of Operator signal threshold per access technology, if set on the USIM, as described in 3.2.2.2.
B) Manual Network Selection Mode
The procedure of 3.2.2.2 B) is followed. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.4 Mobile Station reactions to indications of service restriction from the network | Different types of UE behaviour are required to support, for example, national roaming, regionally provided service and temporary international roaming restrictions. The behaviour to be followed by the UE is indicated by the network. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.4.1 "Permanent" PLMN restriction | When a registration attempt by the UE is rejected by a network with an indication of "permanent" PLMN restriction, the PLMN identity shall be written to a list of "Forbidden PLMNs" stored in a data field in the SIM/USIM.
If a successful registration is achieved on a PLMN in the "Forbidden PLMN" list, the PLMN shall be deleted from the list. However, if successful registration is achieved on a PLMN in the "Forbidden PLMN" list while Disaster Condition applies, the PLMN shall not be deleted from "Forbidden PLMN" list.
When in automatic mode, the UE may indicate any PLMNs which will not be selected due to their presence in the "Forbidden PLMN" list.
If a UE receives an equivalent PLMN list containing a PLMN which is included in the “Forbidden PLMN” list, this PLMN shall be removed from the equivalent PLMN list before this is stored by the UE. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.4.2 "Partial" and "temporary" PLMN restrictions | When a registration attempt by the UE is rejected by a network due to a "partial" or a "temporary" PLMN restriction, the UE shall perform one of the following procedures determined by the indication in the location update reject cause sent by the network (see 3GPP TS 23.122 [3]):
i) The UE shall store the tracking area identity or location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for regional provision of service" respectively and shall enter the limited service state. The UE shall remain in that state until it moves to a cell in a location area where service is allowed;
ii) The UE shall store the tracking area identity or the location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for roaming" respectively and shall use one of the following procedures according to the PLMN selection Mode:
A) Automatic network selection mode:
The procedure of 3.2.2.2. A).
B) Manual network selection mode:
The procedure of 3.2.2.2.B).
iii) The UE shall store the tracking area identity or location area identity in the list of "5GS forbidden TA, forbidden TAs or forbidden LAs for roaming" respectively and shall search for a suitable cell in the same PLMN.
NOTE: A suitable cell will belong to a different TA or LA which is not in the "forbidden TAs or LAs for roaming". When a TA supports multiple systems (e.g. 5GS and EPS), a cell of the TA may be a suitable cell for one system while the cell is not a suitable cell for other systems.. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.4.3 PLMN restrictions for PS services | When a registration attempt for PS services by the UE is rejected by the network with the cause "GPRS services not allowed in this PLMN", the PLMN identity shall be written to a list of "forbidden PLMNs for GPRS service" in the ME. This list is deleted when the UE is switched off or when the SIM/USIM is removed; the maximum number of possible entries in this list is implementation dependent, but must be at least one entry (see 3GPP TS 23.122 [3]).
If a successful registration is achieved on a PLMN in the "forbidden PLMNs for GPRS service" list, the PLMN shall be deleted from the list. |
5b09ab2cb31f10c2a9afae8755e36a25 | 22.011 | 3.2.2.5 Periodic network selection attempts | If the Operator controlled signal threshold per access technology is not set on the USIM, a UE in Automatic Mode shall make periodic attempts to look for a higher priority PLMN including associated Access Technology of the same country as the currently received PLMN including associated Access Technology or for a higher priority PLMN including associated Access Technology that uses a Shared MCC (e.g. MCC=901). If the currently received PLMN including associated Access Technology uses a Shared MCC, also a higher priority PLMN including associated Access Technology using any non-Shared MCC shall be considered. For the ranking of PLMNs the UE shall use the order used in clause 3.2.2.2. In the case that there is no associated Access Technology identifier, the mobile shall assume that all Access Technologies provided by a PLMN are of equal priority. Moreover, periodic network selection shall not lead to change of access technology within the registered PLMN.
When a Disaster Condition is applicable, a UE in Automatic Mode that is registered to a PLMN in the "Forbidden PLMN" data field in the SIM/USIM may make periodic attempts to look for an allowable PLMN of the same country as the currently received PLMN.
In the case that the UE has stored a list of equivalent PLMNs, the UE shall only select a PLMN if it has a higher priority than all the PLMNs, in the list of equivalent PLMNs, which are of the same country as the currently registered PLMN.
NOTE 1: In the context of this 3GPP TS, the term country is to be interpreted not as a political entity but as a single Mobile Country Code (MCC). For example the USA and India have multiple MCC. Such cases are in fact treated as exceptions in the 3GPP specifications. For all other countries, multiple MCCs may be used, however the specifications have not taken this into account and there could be adverse effects such as the UE being unable to detect that multiple MCCs are within the same country.
NOTE 2: There are some situations where one MCC represents multiple political entities or where an MCC is independent of political entities. Examples include Shared MCCs, where international satellite operations typically use the Shared MCC with value 901.
NOTE 3: For the purposes of PLMN selection, the associated Access Technology using a Shared MCC is restricted to the satellite NG-RAN.
In the case that there are multiple EHPLMNs available, the UE shall not attempt to select a higher priority EHPLMN when an EHPLMN has already been selected. The priorities of EHPLMNs are only applicable when the UE is on a VPLMN and multiple EHPLMNs are available.
The UE shall only make reselection attempts while in idle mode. In case of GPRS terminals, the UE shall only make reselection attempts while in Idle or Stand-by mode. In case of terminals operating E-UTRA and/or NR, the UE shall only make reselection attempts while in Idle or RRC-Inactive mode.
In the case of a UE receiving an eMBMS transport service when in idle mode, the UE may postpone the higher priority PLMN search and any reselection attempt until the eMBMS transport service has finished or been stopped.
The interval between attempts shall be stored in the SIM/USIM.
Only the service provider shall be able to select for which of the previous situations, periodic network selection shall be attempted and to set the interval value.
For UEs supporting only Access Technologies other than the following: NB-IoT, GERAN EC-GSM-IoT and Category M1 [17] of E-UTRAN enhanced-MTC the UE shall interpret the interval value to be between 6 minutes and 8 hours, with a step size of 6 minutes.
For UEs only supporting any of the following, or a combination of, NB-IoT, GERAN EC-GSM-IoT [18], and Category M1[13] of E-UTRAN enhanced-MTC, the UE shall interpret the interval value to be between 2 and 240 hours, with a step size of 2 hours between 2 and 80 hours and a step size of 4 hours between 80 and 240 hours.
For UEs supporting a combination of IoT and non-IoT Access Technologies the UE shall interpret the interval value to determine the timer value as above based on the Access Technology currently in use by the UE.
One interval value shall be designated to indicate that no periodic attempts shall be made.
In the absence of a permitted value in the SIM/USIM, or the SIM/USIM is phase 1 and therefore does not contain the datafield, then a default value of 60 minutes, shall be used by the UE except for those UEs only supporting any of the following, or a combination of: NB-IoT, GERAN EC-GSM-IoT [18], and Category M1 [17] of E-UTRAN enhanced-MTC. For those UEs a default value of 72 hours shall be used.
NOTE 4: Use of values less than 60 minutes may result in excessive UE battery drain.
Periodic network selection based on Operator controlled signal threshold criteria
If the Operator controlled signal threshold per access technology is set on the USIM, the UE shall perform the periodic network selection procedure considering all PLMNs, of higher or lower priority than the current PLMN, in the same order as in clause 3.2.2.2, with the following conditions:
- the UE shall select a higher priority PLMN/access technology combination if the target PLMN’s access technology signal quality is equal to or higher than the Operator controlled signal threshold per access technology;
- the UE shall select a lower priority PLMN/access technology combination only if the RPLMN’s access technology signal quality is lower than the Operator controlled signal threshold per access technology, and the target PLMN’s access technology signal quality is equal or higher than the Operator controlled signal threshold per access technology.
NOTE 5: The UE does not perform the periodic attempts if the RPLMN is a HPLMN or EHPLMN, and the RPLMN’s access technology signal quality is equal or higher than the Operator controlled signal threshold per access technology.
If no PLMN, including the RPLMN, fulfils the Operator controlled signal threshold criteria, the UE shall perform the normal periodic network selection for higher priority PLMNs (as described above), without applying the Operator controlled signal threshold per access technology. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.