hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.6 Functionality of Serving Network and Home Environment | The following functionality shall be the responsibility of the home environment:
- User Authentication.
- SIM/USIM Issue.
- Billing.
- User Profile/VHE Management.
The following functionality shall be the responsibility of the serving network:
- Radio or other means of access.
- Transport and signalling.
The following functionality may be the responsibility of either the serving network, the home environment or an appropriate combination of both
- Service Control.
- QoS negotiation.
- Mobility management, including roaming.
- Automatic establishment of roaming agreements. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.7 PLMN Architecture | The network is logically divided into a radio access network and a core network, connected via an open interface. From a functional point of view the core network is divided into a Packet Switched CN Domain, IP Multimedia (IM) CN subsystem [27] and a Circuit Switched CN Domain. IM CN subsystem utilises PS CN domain bearer services.
CS CN domain supports bearer independent transport. There is no difference in service offering or UE functionality due to different transport.
A PS only 3GPP core network is possible as defined within the specification for the Evolved Packet System (EPS) [42].
For further information see 3GPP TS 23.221 [20]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.8 Interworking Between PLMN and Wireless LANs | Aspects related to interworking between PLMN and WLAN are captured in TS 22.234 [35]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.9 Network Sharing | Network sharing shall be transparent to the user.
The specifications shall support both the sharing of:
(i) radio access network only;
(ii) radio access network and core network entities connected to radio access network
NOTE: In a normal deployment scenario only one or the other option will be implemented.
It shall be possible to support different mobility management rules, service capabilities and access rights as a function of the home PLMN of the subscribers. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.10 The Evolved Packet System | Evolved Packet System is an evolution of the 3G UMTS characterized by higher-data-rate, lower-latency, packet-optimized system that supports multiple RATs. The Evolved Packet System comprises the Evolved Packet Core together with the evolved radio access network (E-UTRA and E-UTRAN).The service requirements for the Evolved Packet System are specified in TS22.278 [42]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11 User Data Convergence | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.1 Introduction | The UDC concept [45] supports a layered architecture, separating the data from the application logic in the 3GPP system, so that user data is stored in a logically unique repository allowing access from core and service layer entities, named application front-ends. And such unique repository shall be possible to be shared among different PLMNs that have trusted relationships.
Network elements and functionalities should be designed to access profile data remotely and without storing them permanently locally, i.e. the front-ends shall work in a subscriber data-less configuration.
In some cases, services may depend on user data scattered over UDC and other network elements. UDC may support the ability to access necessary network elements to fetch user data on behalf of these services, while minimizing impacts on existing Network Elements in which the data is located.
Applications can subscribe to specific events which will likely occur on specific user data, and those should be notified when those events do appear. The events can be changes on existing user data, addition of user data, and so on.
Third-party applications and non-trusted network elements should only be able to access the user data after proper authentication and authorization taking into account security and privacy requirements, i.e. it should be possible to present different views on the data to the parties which require access, dependent on the authorization. UDC concept is backwards compatible with 3GPP systems, i.e. it does not have an impact on traffic mechanisms, reference points and protocols of existing network elements.
The UDC concept preserves user authentication and authorization of services across domains, ensuring secured users' access to network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.2 Management of user data | Due to the logical centralization of user data, it is necessary for UDC to support the provisioning of the user data, that is, user data manipulation like creation, deletion, reading, modification and other operations. Provisioning shall be possible via an external system, self-care or dynamically via applications offering e.g. user service configuration facilities.
Operations carried out in the framework of UDC shall support the ACID (Atomicity, Consistency, Isolation, and Durability) characteristics. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 4.11.3 User Data Modelling | User Data Modelling refers to the different models that apply to user data convergence: Information Models and Data Models.
An Information Model denotes an abstract, formal representation of entity types, including their properties and relationships, the operations (e.g. read, write…) that can be performed on them, and related rules and constraints. In the information model, entities might have network topology relationship with each other.
In order to accommodate multiple applications and services, existing and new ones, a common baseline information model shall be developed and shall, at minimum, clearly distinguish a number of concepts as entity types:
- Subscriber with relation to several users (e.g. a company and its employees),
- A user attached to different subscriptions (e.g. for a private and a professional service usage)
- A user using multiple devices (e.g. mobiles or fixed)
- Grouping of users to certain categories
- A particular user as member of a certain group
- Service providers' services provided by network operators
- Enterprise services provided by network operators
The baseline information model shall be future proof. It shall not be tied to any specific implementation of the data base or its interfaces. It shall provide flexibility (in its data structure and content), extensibility and multi-application approach.
By extensible, it shall be understood that new applications and/or new service profiles can be added by the operator, if necessary. The flexibility shall permit new data for existing applications to be introduced, or modified.
Data Models are practical implementations of the information model, e.g. Tree-like modelling. The common information model shall allow deriving one or more data models. A reference data model shall be standardized for the message exchange over Ud interface [50], in order to enable multivendor interoperability.
Each application shall only interface the UDC for the data it is dealing with, and not be impacted by other data that UDC stores for other applications. It corresponds to the concept of a data view specific to a given application.
An application can allow access by other applications to data for which it is responsible. This can be done under certain constraint customized by operators.
Access to the UDC data shall be independent of the structure of the data models, i.e. the changes in the data models shall not affect the interface. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5 Evolution | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5.1 Support of 2G services | The 3GPP specifications shall be capable of supporting existing 2G services in a manner which is transparent to the users of these services. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 5.2 Provision and evolution of services | Since a phased approach has been adopted, the same general service principles shall apply to each phase. Support of services from an end user perspective is understood to be an important driver for established mobile users to stay with their existing operator while taking the new services into use. It is therefore important to enable operators to offer continued support of legacy services in future releases. Previous release services shall as a principle also be supported in the following releases.
Networks shall be capable of providing a specified core set of capabilities.
The core set of capabilities should permit home environment to offer a range of distinctive services including those which cannot be implemented on systems based on previous release specifications.
It shall be possible for the home environment to develop services with full roaming capability.
The radio interface should not unnecessarily restrict the development of new services (within physical limitations).
The standard shall provide a mechanism which allows a terminal to be easily upgraded so that it can access new services which are within the physical limitations of the terminal. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 6 Classification of services | In the CS CN domain, the basic services are divided into circuit teleservices (3GPP TS 22.003 [14]) and bearer services (3GPP TS 22.002 [21]) and they can utilise standardised supplementary services (3GPP TS 22.004 [5]).
The PS CN Domain provides IP bearer services. SMS, USSD and UUS can also be considered as bearer services for some applications.
IP multimedia services are the IP based session related services, including voice communications. IP multimedia sessions use IP bearer services provided by the PS CN Domain.
Value added non-call related services include a large variety of different operator specific services/applications. They are usually not specified by 3GPP. The services can be based on fully proprietary protocols or standardised protocols outside 3GPP.
In order to create or modify the above services (both call and non-call related services) operators may utilise toolkits standardised by 3GPP (such as CAMEL or LCS) or external solutions (e.g. Internet mechanisms). Pre-paid is an example of an application created with toolkits that may apply to all of the above services categories.
Figure 1: Service classification |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7 Principles for new service capabilities | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.1 General | 3GPP specifications shall enable the user of a single terminal to establish and maintain several connections simultaneously. It shall efficiently cater for applications which have variable requirements relating to specific QoS parameters (e.g. throughput) whilst meeting other QoS targets. It shall also cater for applications which are able to take adapt to a range of variations in QoS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2 Multimedia | 3GPP specifications shall support development of multimedia services and provide the necessary capabilities.
Multimedia services combine two or more media components (e.g. voice, audio, data, video, pictures, text) within one call. A multimedia service may involve several parties and connections (different parties may provide different media components) and therefore flexibility is required in order to add and delete both resources and parties.
Multimedia services are typically classified as interactive or distribution services.
Interactive services are typically subdivided into conversational, messaging and retrieval services:
Conversational services are real time (no store and forward), usually bi-directional where low end to end delays (< 100 ms) and a high degree of synchronisation between media components (implying low delay variation) are required. Video telephony and video conferencing are typical conversational services."
Messaging services offer user to user communication via store and forward units (mailbox or message handling devices). Messaging services might typically provide combined voice and text, audio and high-resolution images.
Retrieval services enable a user to retrieve information stored in one or many information centres. The start at which an information sequence is sent by an information centre to the user is under control of the user. Each information centre accessed may provide a different media component, e.g. high-resolution images, audio and general archival information.
Distribution services are typically subdivided into those providing user presentation control and those without user presentation control.
Distribution services without user control are broadcast services where information is supplied by a central source and where the user can access the flow of information without any ability to control the start or order of presentation e.g. television or audio broadcast services.
Distribution services with user control are broadcast services where information is broadcast as a repetitive sequence and the ability to access sequence numbering allocated to frames of information enables the user (or the user's terminal) to control the start and order of presentation of information. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.1 Circuit Switched (CS) multimedia calls | CS multimedia call is a Bearer Service which utilises Synchronous Transparent Data service. The following basic requirements shall be supported for CS multimedia calls [24]:
- CS multimedia call shall be based on a 3GPP specific subset of H.324M.
- All call scenarios shall be supported, i.e. Mobile Originating and Mobile Terminating call against Mobile, ISDN and PSTN call party.
- Single and multiple numbering schemes shall be supported.
- Fallback to speech (TS 11 [14]) shall be supported from 3.1kHz Ext. PLMN multimedia bearer, i.e. if setup of the multimedia call fails the call will be set up as a speech call.
- Service change and fallback shall be supported for UDI/RDI multimedia bearer and speech, to allow fallback to a less preferred service if the preferred service is unsupported, and to change the service between speech and multimedia during the call.
- In the case where a CS multimedia call includes speech (e.g. video call) then the following requirements apply:
- A user shall be able to change between a speech and CS multimedia call, when desired.
- When the CS multimedia call is no longer supported, for example due to degraded coverage conditions (including UTRAN to GERAN only transitions), service change shall occur automatically from a CS multimedia call to speech.
- When a CS multimedia call can be supported, for example due to improved coverage conditions (including GERAN only to UTRAN or UTRAN/GERAN transitions), service change back to the CS multimedia call may be initiated by the network.
- Other services than CS multimedia call may exist which utilise the Synchronous Transparent Data service. Service transition to/from speech described for CS multimedia call in this clause shall only apply to CS multimedia call and not Synchronous Transparent Data services in general.
- Different bitrates as specified at 3GPP TS 22.002 [21] shall be supported.
- Supplementary services apply to multimedia calls as for Synchronous Transparent Data service according to 3GPP TS 22.004[5].
- When accepting a multimedia call, the user shall be able to request a service change to speech before the call is answered, such that the multimedia path is never actually connected through to the user's phone.
- The user shall be able to deny a service change to multimedia during the call. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.2 IP multimedia (IM) sessions | IP multimedia services are not the evolution of the circuit switched services but represent a new category of services, mobile terminals, services capabilities, and user expectations. Any new multimedia service, which may have a similar name or functionality to a comparable standardised service, does not necessarily have to have the same look and feel from the user's perspective of the standardised service. Voice communications (IP telephony) is one example of real-time service that would be provided as an IP multimedia application.
The following basic requirements are be supported for IP multimedia [27]:
- IP multimedia session control shall be based on SIP [28].
- All session scenarios shall be supported; i.e. Mobile Originating and Mobile Terminating sessions against Internet/Intranet, CS or IM Mobile, ISDN, PSTN call party.
- MSISDN and SIP URL numbering and addressing schemes shall be supported.
- IP multimedia applications shall as a principle, not be standardised, allowing service provider specific variations.
7.2.3 Multimedia Messaging Service (MMS)
The following basic requirements are be supported for MMS:
- Store-and-forward multimedia messaging service with mobile and non-mobile users [25].
- MMS shall be capable of supporting integration of different types of messaging (e.g. fax, SMS, Multimedia, voicemail, e-mail etc.) in a consistent manner.
- Streamed and batch delivery for both message download from the network to the terminal, and messages upload from the terminal to the network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.4 Real-Time Text Conversation | Real-Time Text (RTT) conversation is a service enabled in 3GPP networks by the Global Text Telephony ( GTT ) [26].
- GTT enables real time, character by character, text conversation to be included in any conversational service, Circuit Switched as well as IP based.
- It is possible to use the text component in a session together with other media components, especially video and voice.
- Interworking with existing text telephony in PSTN as well as emerging forms of standardised text conversation in all networks is within the scope of this feature.
- The text media component can be included initially in the session, or added at any stage during the session.
- The text component is intended for human input and reading, and therefore supports human capabilities in text input speed. The character set support is suitable for the languages the users communicate in.
- GTT specifies limited interoperation with Multimedia Messaging Services including a possibility to divert to messaging in case of call failure and sharing user interface equipment and external UE interfaces. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.2.5 Packet Switched Streaming Service | The following basic requirements are to be supported for streaming:
- The streaming service uses a client / server model which is transparent to the PLMN. The client controls the initiation and execution of the service.
- The streaming service [30] shall use existing standards (codecs and protocols [31]) where these are available.
- The streaming service utilises the PS Domain with the QoS requirements as specified in 3GPP TS 22.105 [1]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.3 Service Management Requirements | 3GPP specifications shall include standardised protocols enabling service management. It shall enable control, creation and subscription of service capabilities and services, and the management of user profiles. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 7.4 Automatic Device Detection | The home environment should be automatically notified when a user, identified by a SIM/USIM, has changed ME and should be informed of the identity of the new ME. This should be applicable to any ME. It should also be possible to achieve Automatic Device Detection for users using any SIM/USIM.
NOTE: The purpose of this is to enable an automatic configuration of terminals by the operator for specific applications/services if so needed. The procedure for such an automatic configuration need not to be standardized by 3GPP.
The notification that a user has changed ME shall be given as early as possible. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 8 Service architecture | In order to provide standardisation of service capabilities a service architecture shown by Figure 2 is envisaged
Figure 2: Service Architecture
A number of bearers shall be provided that can differ in flexibility and offer different capabilities. Bearers may be characterised by parameters such as "throughput", "delay tolerance", "maximum bit error rate", "symmetry" etc. These bearers enable information to be transferred appropriate to the provision of teleservices, multimedia services and end user applications generally, via subnetworks which typically provide different specified qualities of service.
The assignment and release of bearers is provided by the bearer control function. Provision should be made for several bearers to be associated with a call and for bearers to be added to a call and/or to be released from a call following call establishment. The bearers should be independent of radio environments, radio interface technology and fixed wire transmission systems.
Adaptation/Interworking functions are required in order to take account of the differences between the bearers used for the provision of a teleservice/multimedia service/application in the fixed network and the bearers. Adaptation/Interworking functions are required which take account of the discontinuous and/or asymmetrical nature of most teleservices/multimedia services/applications.
The service platform shall provide interfaces (to serving networks and home environments) appropriate to the support, creation and control of supplementary services, teleservices, multimedia services and user applications. The service platform will also provide interfaces enabling subscribers to control supplementary services, teleservices, multimedia services and user applications.
Supplementary service provision and control will be independent of radio operating environment, radio interface technology and fixed wire transmission systems.
As far as possible, the service platform is required to enable new supplementary services, teleservices, multimedia services and/or end user applications to be supported at minimum cost, with minimum disruption of service and within the shortest possible time. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 9 Quality of Service (QoS) | The Quality of Service (QoS) parameters should be identified together with appropriate parameter values which set targets to be reached when designing 3GPP specifications, and which also will serve as guidelines for network design and service provision.
The QoS for call set-up time, as an example, can be defined in terms of a mean value and as a percentage of cases which should not exceed a certain time limit. Further information can be found in 3GPP TS 22.105 [1].
The performance requirements for the All-IP Network can be found in 3GPP TS 22.278 [42].
For UE initiated QoS control OMA device management shall be the primary method for provisioning QoS parameters. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10 Emergency Calls | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1 General requirements | 10.1.0 Introduction
It shall be possible to establish an emergency speech call or GTT [26] call (subject to national requirements). The term 'Emergency call' henceforth refers to speech calls, and GTT Emergency calls if applicable. The term "other media" henceforth refers to media other than speech and GTT. Support of other media types during an emergency call when the IM CN subsystem is used is referred to as 'IMS Multimedia Emergency Session' (MES) and is specified in subclause 10.4.2. Emergency calls will be routed to the emergency services in accordance with national regulations for where the subscriber is located. This may be based upon one or more default emergency call numbers stored in the ME. It shall be allowed to establish an emergency call without the need to dial a dedicated number to avoid the mis-connection in roaming case, such as menu, by use of a 'red button', or a linkage to a car air bag control. Emergency calls shall be supported by the UE without a SIM/USIM/ISIM being present. No other type shall be accepted without a SIM/USIM/ISIM than emergency calls and subject to operator policy and regional regulations, restricted local operator service access.
Emergency calls shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden LA (see 3GPP TS 22.011 [11]), or on a CSG cell without the subscriber being a member of that CSG (see 3GPP TS 22.220 [48]). Such emergency calls shall be accepted by the network if required by local regulation.
The Emergency service is required only if the UE supports voice.
Note 1: It will be left to the national authorities to decide whether the network accepts emergency calls without the SIM/USIM/ISIM.
It shall be possible to initiate emergency calls to different emergency call centres, depending on the type of emergency. The following types of emergency calls shall be possible:
- Police
- Ambulance
- Fire Brigade
- Marine Guard
- Mountain Rescue
- Manually Initiated eCall (MIeC)
- Automatically Initiated eCall (AIeC)
- Spare
When a SIM/USIM is present, subscriber specific emergency call set-up MMI shall be provided. The Home Environment operator shall specify preferred emergency call numbers (e.g. 999 for UK citizens or 110, 118 and 119 for Japanese citizens). These emergency call numbers shall be stored in the SIM/USIM and the ME shall read this and use any entry of these digits to set up an emergency call. It shall be possible to store more than one instance of this field.
Note 2: Release '98 and earlier SIM cards have the capability to store additional emergency call numbers. However in many cases this has not been used.
It shall be possible to tie any emergency call number to any single emergency call type or to any combination of emergency call types. The association between emergency call numbers and emergency call type shall be able to be programmed by the Home Environment operator into the SIM/USIM.
Example:
19 Police (Albania)
100 Police and Fire Brigade (Greek cities)
100 Ambulance and Fire Brigade (Belgium)
112 Police and Ambulance (Italy)
112 General emergency call, all categories (Sweden)
115 Fire Brigade (Italy)
144 Ambulance (Austria)
If the UE does not recognise the emergency call numbers but the serving network recognises the dialled number as an emergency call number used in the country, a normal call set up shall take place over the radio interface and after the serving network has recognised the emergency number the call shall be routed as an emergency call.
The user friendly MMI that specifies the type of emergency call directly (e.g. menu) should be supported for use in any (i.e. home or visited) PLMN to avoid the misconnection in roaming case. This shall be allowed both with and without SIM/USIM being present.
When emergency call establishment is initiated, the emergency call type shall be sent by the UE if it is available.
The serving network may download emergency call numbers to the UE in order to ensure that local emergency call numbers are known to the UE. In case of PLMN, the UE shall regard these emergency numbers as valid in that country only (as identified by the MCC) and shall discard them when a new country is entered.
Note 3: The UE can inform the user if the emergency call type for an emergency number received from the serving network differs from that configured on the USIM/SIM for the same number. How this is implemented is outside the scope of 3GPP and takes into consideration operator policy and regulatory requirements.
If permitted by local regulation, it shall be possible for the user to prevent the sending of his public user identifiers and the location information to the PSAP (i.e. emergency response centre).
Note 4: Operator policies (e.g. requirements for support of emergency communications) may over-ride the user request for suppression.
10.1.0a Emergency calls over WLAN
Emergency calls over WLAN shall be supported as above with the following caveats:
• The UE issues an Emergency session over WLAN access to EPC only when 3GPP access for emergency call is not possible or available (e.g. no 3GPP coverage).
• UEs shall only be able to establish an Emergency session over WLAN when the UE has been provisioned with the WLAN access parameters.
• Service continuity for an Emergency voice call moving from 3GPP access CS domain to WLAN access IMS domain is not supported.
• The level of security should not be less than that which is currently applied to authenticated and unauthenticated CS or IMS emergency calls.
• Emergency call numbers downloaded to the UE over WLAN from untrusted sources shall not be used by the UE.
NOTE 5: TS 23.402 [57] establishes when WLAN is trusted or not.
• Subject to local 3GPP operator policy, the UE may use additional emergency call number(s) received via WLAN access for emergency calls via 3GPP access or WLAN access, while in the country for which the numbers were received.
10.1.1 Identification of emergency numbers
The ME shall identify an emergency number dialled by the end user as a valid emergency number and initiate emergency call establishment if it occurs under one or more of the following conditions. If it occurs outside of the following conditions, the ME should not initiate emergency call establishment but normal call establishment. Emergency number identification takes place before and takes precedence over any other (e.g. supplementary service related) number analysis.
a) 112 and 911 shall always be available. These numbers shall be stored on the ME.
b) Any emergency call number stored on a SIM/USIM when the SIM/USIM is present.
c) 000, 08, 110, 999, 118 and 119 when a SIM/USIM is not present. These numbers shall be stored on the ME.
d) Additional emergency call numbers that may have been downloaded by the serving network when the SIM/USIM is present. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2 Domains priority and selection for UE attempts to emergency call | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2.1 Voice and GTT only | A UE that is connected to a domain in which it is possible for the UE to make non emergency calls using the particular media requested by the user, shall use that domain to attempt an emergency call unless serving network policy (based on regulatory requirements and operator needs) requires the UE, including an unauthenticated UE, to attempt the emergency call on a specific domain first.
If the UE is connected to more than one domain in which it is possible for the UE to make non emergency calls using the particular media requested by the user, the UE shall attempt an emergency call on the same domain it would use to originate a non-emergency call using the same media unless serving network policy (based on regulatory requirements and operator needs) requires the UE, including an unauthenticated UE, to attempt the emergency call on a specific domain first.
In the case where an emergency call attempt by a UE fails, the UE should automatically make a second attempt on the other domain if the UE supports it.
If the user aborts the emergency call setup during the subsequent automatic attempt and immediately tries to set up an emergency call again, then the UE shall immediately attempt in the domain in which the user aborted the emergency call. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.2.2 Other media | The following applies in addition to 10.1.2.1.
If an emergency call attempt that includes a request for both (i) voice and/or GTT and (ii) other media cannot be supported or fails in all connected access types in the PS CN domain, the UE shall attempt the emergency call in the CS domain if available and shall only include the request for voice and/or GTT. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.1.3 Call-Back Requirements | Subject to local/regional regulations the network shall support a call-back from a PSAP.
It shall be possible to supply the user's Directory Number/MSISDN/SIP URI as the CLI to the PSAP to facilitate call-back. The CLI used on call-back shall allow the PSAP to contact the same terminal that originated the emergency call.
If the incoming call can be identified by the core network as a call-back to an emergency call (i.e. coming from a PSAP) then supplementary services at the terminating party shall be handled as described in TS 22.173 [40] for Multimedia Telephony (e.g. Communication Diversion, Communication Hold, Communication Barring).
NOTE: There is no specific callback requirement for CS supplementary services.
A call-back may be attempted for a period of time defined by local regulations after the emergency call release. In case of a UE in limited service state, call-back is not required. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.2 Emergency calls in the CS CN Domain | A CS CN Domain shall support the emergency call teleservice as defined in 3GPP TS 22.003 [14] (TS12).
If a UE supports TS11(Telephony)[14], then it shall also support TS12(Emergency Calls)[14]. It shall be possible to set up emergency calls initiated by an emergency call number. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.3 Emergency Calls in the PS CN Domain | Without the IM CN subsystem, emergency calls are not supported in the PS CN domain. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4 Emergency calls in the IM CN subsystem | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.1 General | The IM CN subsystem shall support IMS emergency calls. It shall be possible to set up emergency calls initiated by an emergency call number.
If a UE supports IMS Multimedia Telephony service with speech media as specified in TS 22.173 [40] via an access network, then it shall also support IMS emergency calls via that access network.
Subject to the regulatory requirement, the IM CN subsystem shall be able to unambiguously identify each emergency service defined in the national numbering plan for the country in which the UE is located.
In accordance with national regulations for where the subscriber is located, if the UE does not recognise a dialled number as an emergency call number but the IM CN where the subscriber is located does recognise the dialled number as an emergency call number (e.g. a number used in the local emergency numbering plan) then the call shall be routed as an emergency call indicating the type of emergency service to the correct PSAP. Subject to operator setting the call may be prioritized.
Note 1: The above does not preclude the network rejecting the call and requesting the UE to setup a new emergency call to the same emergency service.
The serving network may download emergency call numbers and emergency call types, together with a validity indication of this list, for use in the IM CN subsystem so that local emergency call numbers are made known to the UE. Depending on the validity indication, the UE shall regard these emergency numbers and emergency call types as valid in that country (as identified by the MCC) and shall discard them when a new country is entered, or the UE shall regard these emergency numbers and emergency call types as valid in that serving network, which can be a PLMN (as identified by the MCC and MNC) or an NPN, and shall discard them when the UE enters a new PLMN or NPN.
Emergency calls may be initiated using a private numbering plan [49].
Note 2: There can be an overlap between the private numbering plan of a hosted enterprise and the public numbering plan, which makes translation of emergency numbers necessary.
Emergency calls may be initiated by a service when requested by the user.
Note 3: It is not intended to enable automatic setup of emergency calls.
Note 4: Only speech and GTT-IP [47] media are supported, when required per subclause 10.1, for emergency services towards a CS PSAP.
An emergency call shall take precedence over any other services a UE may be engaged in, if required by local regulation.
Emergency calls from an unauthenticated UE (as far as the IM CN is concerned) shall be supported by the IM CN subsystem, if required by local regulation.
Subject to regulatory requirements, when UEs must be authenticated, both the network and the UE shall support the same authentication and security methods that are used for non-emergency sessions. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2 IMS Multimedia Emergency Sessions | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.1 General | For IMS emergency calls towards IP PSAPs, other media types may be supported by the UE and the IMS, subject to regulatory requirements.
The media types that may be supported during an IMS MES include:
- Real time video (simplex, full duplex), synchronized with speech if present;
- Session mode text-based instant messaging;
- File transfer;
- Video clip sharing, picture sharing, audio clip sharing;
- Voice; and
- Real-Time Text .
Note 1: An IMS MES need not contain voice or Real-Time Text .
To avoid interworking issues, a UE and IMS that supports text based instant messaging shall support a common session mode text-based instant messaging protocol.
IMS MES does not include support for legacy store and forward messaging such as the Short Messaging Service (SMS).
Calls from non-human associated devices (e.g. fire alarms) are outside the scope of this specification.
Adding, removing and modifying individual media to/from an IMS MES shall be supported.
An IMS MES is not a subscription service. A UE capable of IMS emergency calls and capable of supporting the other media types should also be able to support initiation of an IMSMES.
An IMS MES from an unauthenticated UE (as far as the IM CN is concerned) shall be supported by the IM CN subsystem, if required by local regulation.
IMS MES shall be supported by UEs that are subject to service restrictions, e.g. for UEs camping on a cell in a forbidden PLMN or in a forbidden LA (see 3GPP TS 22.011 [11]), or on a CSG cell without the subscriber being a member of that CSG (see 3GPP TS 22.220 [48]). Such IMS MES shall be accepted by the network if required by local regulation.
An IMS MES shall support providing the location of the UE, in a manner similar to IMS emergency voice calls.
An IMS UE that supports IMS MES shall identify an emergency number dialled by the end user as a valid emergency number utilizing the same mechanisms as used for IMS emergency voice calls as defined in subclause 10.1.1.
Note 2: This capability supports the general public, including facilitating emergency communications by individuals with disabilities (e.g. persons who are deaf, deaf-blind, hard of hearing, or have a speech disability).
An originating network and UE may support some or all of these other media types, and support of any specific media by an originating network or UE may be subject to regulatory requirements.
Voice call continuity per clause 21 shall be supported when a UE with an active IMS MES with voice and other media moves out of IMS voice coverage and voice call continuity is supported by the UE and network. The remaining media (i.e. voice call) then becomes a CS emergency call e.g. TS12 call for 3GPP systems as defined in 3GPP TS 22.003 [14].
Other media shall be dropped when a UE with an active IMS MES moves out of IMS voice coverage, irrespective of whether or not there is an active voice session. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.2 UE Requirements | When IMS MES are supported by the UE, the following apply:
- An IMS UE that supports IMS MES shall also support IMS emergency voice calls.
- Once a UE is aware that an IMS MES has been initiated, the UE shall be able to (subject to user configuration) avoid drawing unnecessary attention to the user (e.g., playing audible tones or flashing brightly) and should confirm this to the user in as private a manner as is reasonable e.g. using text on the screen or audio if headphones are already connected. UE behaviour in an IMS MES may need to be different relative to the normal configuration.
- The UE should clearly differentiate IMS emergency session-mode text based instant messaging from IMS non-emergency session-mode text based instant messaging on the user display.
- The IMS UE supporting video transfer during an IMS MES should be able to deliver recorded media in a form that allows progressive playback. (It is desirable that all pre-recorded media sent during an emergency session be progressively viewable.)
- When an IP PSAP attempts to add additional media to an existing IMS MES, the user shall be made aware of this. When additional media is requested by the PSAP, the user shall be able to permit or deny it.
- The UE shall provide an indication to the user for each requested media, whether it was successfully or unsuccessfully established.
- Further notifications of added and removed media shall be indicated to the user while the IMS MES is active.
- If none of the media requested by the UE is successfully established, the IMS MES will fail and an IMS MES failure indication shall be provided to the user.
- In handover of an IMS MES where other media is dropped when IMS MES is not supported, the UE shall indicate to the end user that the other media is not supported in this area.
The following requirements for IMS emergency voice calls also apply when an IMS MES is supported by the UE:
- An IMS UE that supports IMS MES shall indicate to the network that the call is an IMS emergency call as is done for an IMS emergency voice call.
- An IMS UE that supports IMS MES shall be able to receive an IMS call-back from a PSAP per clause 10.1.3 with voice, GTT or other media per clause 10.4.2.1.
- An IMS UE that supports MES shall utilize the same trust and security mechanisms for the other media as utilized for an IMS emergency voice call.
- When roaming, a UE shall originate an IMS MES in the serving network in the same manner as for IMS emergency voice calls. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.4.2.3 Originating Network Requirements | When an IMS MES is enabled by the originating network, the following apply:
- Other media shall only be supported in packet-based networks that support IMS emergency voice calls.
- The originating network shall deliver all media to the same IP PSAP throughout the duration of the IMS MES.
- The network shall indicate to the UE, for each requested media, whether it was successfully or unsuccessfully established.
- Further notification of added and removed media shall be provided to the UE while the IMS MES is active.
- If none of the media requested by the UE is successfully established, the IMS MES will fail and an IMS MES failure indication will be provided to the UE.
The following requirements for IMS emergency voice calls also apply when IMS MES is supported by the network:
- Subject to regional regulatory requirements, the network shall be able to authenticate the UE using the same procedures as for IMS emergency voice calls.
- The originating network shall provide the capability to enable an IMS UE supporting IMS MES to obtain local emergency numbers or other emergency address(es) (e.g. destination address) utilizing the same mechanism as used for IMS emergency voice calls.
- An IMS MES shall be provided in the local serving network.
- For an IMS MES, any kind of emergency addressing (e.g. SIP URIs, Tel URIs) and special indications for emergency sessions shall be treated in the same manner as IMS emergency voice calls.
- The originating network should detect all IMS MESs regardless of the UE emergency call indication. According to operator policy, the originating network may either inform the UE to enable re-origination as an IMS MES or support origination of the initial call.
- The originating network shall be responsible for routing the IMS MES towards the appropriate PSAP (e.g., based on emergency service type, location, or policy).
- The network shall be able to provide integrity protection, and/or privacy for other media similar to that provided for IMS emergency voice calls.
- An IMS MES shall utilize the same priority mechanisms as IMS emergency voice calls.
- Detailed log records of the IMS MES shall be generated by the originating network in a similar manner to IMS emergency voice calls and subject to regulatory requirements.
- All media content within the IMS MES shall be carried with an indication of the source, in a similar manner as for IMS emergency voice calls. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.6 Location Availability for Emergency Calls | National regulations may require wireless networks to provide the emergency caller's location. This requirement typically overrides the caller's right to privacy with respect to their location being revealed, but remains in effect only as long as the authorities need to determine the caller's location. The interpretation of the duration of this privacy override may also be different, subject to national regulation. For example, some countries require location to be available from the wireless network only while the call is up, while others may allow PSAP's to unilaterally decide how long the location must be made available.
Therefore, the requirement for providing location availability is to allow the network to support providing a mobile caller's location to the authorities for as long as required by the national regulation in force for that network.
NOTE: See TS 22.071 [44] for location service requirements on emergency calls. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.7 Transfer of data during emergency calls | Emergency calls may be supplemented with emergency related data [1]. Typically this data enables the accurate geographic location of a manually or automatically activated emergency calling device e.g. an in vehicle system (IVS), to be provided to the Public Safety Answering Point (PSAP).
The following requirements apply to UEs designed to be able to perform eCalls and to networks supporting eCall:
- The data may be sent prior to, in parallel with, or at the start of the voice component of an eCall.
- Should the PSAP request additional data then this may be possible during the established eCall.
- The realisation of the transfer of data during an eCall shall minimise changes to the originating and transit networks.
- Both the voice and data components of the eCall shall be routed to the same PSAP or designated emergency call centre.
- The transmission of the data shall be acknowledged and, if necessary, data shall be retransmitted.
- The UE shall indicate at call setup if the emergency call will carry supplementary data, i.e. is an eCall.
UEs designed to be able to perform eCalls and configured to only perform eCalls (eCall only mode) shall comply with the following additional requirements:
• The UE shall not perform mobility management procedures, including registration on a PLMN, except when attempting to initiate and during an eCall, or to initiate a test or reconfiguration of the terminal upon request from the user.
• For UEs that have the ability to be called back by the PSAP, the UE shall be capable to continue mobility management procedures for a limited duration following the termination of the eCall.
- The UE shall contain an USIM application.
- In the case where the user subscribes to other services provided by the PLMN, it shall be possible for the network operator to reconfigure the UE so that it can access the subscribed services.
- It shall be possible for the user of the UE to change network operator/service provider (i.e. to use a different USIM) or for the subscriber to modify the existing subscription used with the UE.
- It shall be possible for the UE upon request from the user to initiate a call to an operator designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services.
Additional national and regional requirements are as specified in Annex A. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.8 Supplementary service interaction during emergency calls | Supplementary services that interrupt or divert the media path between a PSAP and the end device shall be handled as specified in TS 22.173 [40] (e.g. Communication Hold) for Multimedia Telephony. No such Supplementary Services are applicable to CS Emergency Calls (TS12) according to TS 22.004 [5].
10.9 Emergency Calls in a MUSIM UE
A MUSIM UE shall be able to select a USIM to originate an emergency call in the following priority:
- USIM in normal service
- USIM in limited service state
The MUSIM UE shall avoid interruptions of emergency call procedures of one USIM by other services of other USIM.
Subject to regulatory requirements, call-back requirements defined in clause 10.1.3 apply to a MUSIM UE. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.10 Emergency Services over Non-public networks | Subject to local/regional regulations, the 5G system shall support IMS Multimedia Emergency services (see clause10.4) over non-public network (NPN) [59] for NPNs using IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.11 Short Message Service over IMS to emergency centre | EPS and 5GS shall route a Short Message over IMS using the emergency numbers to a local emergency response centre (i.e. PSAP), according to the local regulations.
The Short Message shall be routed to the emergency response centre serving the location where the subscriber is located and replies routed back to the subscriber in accordance with national regulations as specified in 10.1.
The 3GPP system shall support a Short Message to be routed to different emergency response centres, depending on the type of emergency as specified in 10.1.
The Short Message Service to emergency response centre shall be supported without a SIM/USIM/ISIM being present.
Note 1: It will be left to the national authorities to decide whether the network accepts Short Message Service to emergency response centre without the SIM/USIM/ISIM.
The Short Message Service to emergency response centre shall be able to use the same identification methods as for emergency calls, as specified in 10.1.1.
Subject to local/regional regulations Short Message Service to emergency response centre shall support location service as specified in chapter 10.6. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 10.12 Emergency Sessions over Relay UEs | Where the 5G system supports remote UE access to emergency sessions via relay UEs, the following requirements apply:
- Subject to local regulatory requirements, the UE shall first attempt to make an emergency session via any available network. If the UE fails to find a network that allows emergency sessions, the UE shall attempt an emergency session via a relay UE.
- Subject to local regulatory requirements, the 5G system shall route emergency sessions to an appropriate PSAP for the location of the remote UE, which can be in the same country of the remote UE or not. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11 Numbering principles | The following network addressing schemes listed below shall be supported at the relevant domains:
- E.164,
- E.168,
- E.212,
- X.121
- Internet (including e.g. IP address, SIP URI). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1 Number portability | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.1 Requirements for CS CN domain | Some numbering schemes shall be fully independent of the supporting serving network and the home environment, allowing users to transfer this number to another home environment. For further information see 3GPP TS 22.066 [7].
An MSISDN shall be allocated to each new user at the start of a subscription. This number may be allocated from one of several numbering domains. For example:
- home / serving environment numbering scheme;
- national numbering scheme;
- regional numbering scheme;
- global numbering scheme.
A user shall be able to move subscription from one home environment to another without changing the MSISDN provided that the new home environment offers service in the same geographic domain. It is envisaged that home environment s will be able to allocate MSISDNs from each of these domains as required. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.2 Requirements for PS CN domain | None identified. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.1.3 Requirements for IM CN subsystem | It shall be possible to offer number portability for E.164 numbers within IM CN subsystem. For further information see 3GPP TS 22.066 [7]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.2 Evolution path | Since 3GPP specifications aim to be aligned with IMT-2000, a primary goal in numbering is the provision of global user numbering in line with steps taken by the ITU - SG2.
The numbering scheme and network implementation chosen shall allow for international/global evolution. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.3 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.4 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.5 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.6 Private numbering | A user may wish to use private numbers for the purposes of calling frequent numbers. Therefore there is a requirement for the use, by the user, of Private Numbering Plans (PNPs). These schemes may belong to the user himself, to a home environment or a third-party. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7 Numbering schemes | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.1 Multiple numbering scheme | The standards shall support the possibility of allowing the bearer service associated with an MT call to be implicitly defined by the destination MSISDN, for example to use a different MSISDN to establish voice, fax or data. It will be possible for multiple MSISDNs to be associated with a single subscription. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.2 Single numbering scheme | The standards shall support the possibility of allowing MT calls of different bearer types (e.g. voice, fax, data) to be routed to a single MSISDN. It is recognised that the implementation of this may depend on the availability of bearer information associated with an incoming call from the adjoining transit network. In particular the standards will support this possibility in the case of an adjoining ISDN transit network. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.7.3 Additional numbers | The 3GPP system shall support the possibility to assign an additional MSISDN, in addition to the original MSISDN, to a user with a connection to the PS CN domain. If this additional MSISDN is available, it shall be used for correlation of CS and IMS in voice call and service continuity as well as IMS Centralized Service. In this case the original MSISDN may be used for charging and OA&M purposes and forwarded to the PS gateway to other packet data networks. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 11.8 Optimal routing | The implementation of the numbering scheme used shall allow for optimal routing; i.e. routing shall not take place simply on the number dialled.
See 3GPP TS 22.079 [8] for some scenarios for the CS CN domain. Optimal routing for IP services is supported by the All-IP Network [42].
11a Identification Requirements
11a.1 Subscriber Identification
In 3GPP the identity of a subscriber is encoded in a identity module application which is contained on a UICC or on a GSM SIM card. The GSM SIM card is a removable component of the User Equipment; UICC can be removable or also embedded. Three types of identity modules are used in the 3GPP system:
- Universal Subscriber Identity Module (USIM)
- IMS Subscriber Identity Module (ISIM)
- Subscriber Identity Module (SIM) according to GSM
General requirements:
- In the 3GPP system each subscriber shall be uniquely identifiable.
- The serving networks shall be able to authenticate any subscriber that roams onto their network
- If a UE, that is registered on the serving network, contains a GSM SIM card or a UICC containing a identity module application, the serving network shall be able to identify the associated home PLMN.
Note 1: UE support of GSM SIM is optional.
Note 2: See the chapter (USIM, UICC and Terminal) of the present specification for a reference, which GSM phase SIMs need to be supported by the network.
11a.2 Terminal Identification
It is a requirement that the terminal can be uniquely identified by the home environment and serving network. This shall require a terminal identity scheme which uniquely identifies each terminal, see 3GPP TS 22.016[12].
11a.3 Home Environment / Serving Network Identification
Home / serving environments need to route communication to the current location of the user. This shall require a identity scheme which uniquely identifies the serving environment and shall be used for routing purposes.
11a.4 Serving Environment / Mobile Virtual Network Identification
A mobile virtual network operator (MVNO) is a service provider that does not have its own radio access network, but resells wireless services, typically under their own brand name, using the network of a host PLMN operator.
It should be possible to uniquely identify subscribers belonging to a particular MVNO. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 12 Human Factors and user procedures | The User Interface (MMI) from the end-user's point of view should be as flexible as possible while still meeting the general service requirements. In addition, it should be capable of being updated so as to meet new services which are still to be envisaged.
In general, the following principles should be encompassed:
- activation of services should be as simple as possible with minimum input expected from the user;
- feedback, to the user from the various services, should be meaningful;
- any error recovery procedures provided should be simple to understand and execute.
- input from the user and information to the user should be provided in alternative selectable modes in order to match user capabilities, preferences and situation.
However, a detailed specification for the User Interface shall not be defined. In particular given the global nature of the third generation systems, for different regions of the world, different criteria will determine the implementation of the User Interface. Also it is unlikely that there will be a single common handset which will meet all the service requirements and therefore a common User Interface would be impractical.
Given the flexibility of the services, there should be a wide range of User Interface possibilities. These possibilities include simple terminals with a single on/off button through to complex terminals providing support to hearing/visually impaired users.
Control of CS CN Domain supplementary services (3GPP TS 22.004 [5]), may use MMI procedures specified in 3GPP TS 22.030 [6] and existing MMI related UE features (Annex A) may also be used. In particular the following features are highly desirable for uniform UE implementation where appropriate:
- Mapping of numeric keys to European alphabetic keys to ensure compatible mnemonic dialing as defined in 3GPP TS 22.030 [6],
- "+" key function to enable one key international access as defined in Annex A
- Structure of the MMI as described in 3GPP TS 22.030 [6]
- Presentation of IMEI (International Mobile Equipment Identity) as defined in 3GPP TS 22.030 [6]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13 UICC, USIM and Terminal | This clause defines the functional characteristics and requirements of the User Service Identity Module (USIM) and ISIM (IM Services Identity Module). The USIM/ISIM are applications residing on a UICC. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1 The USIM/ISIM and User Profiles | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.1 The USIM | Every USIM shall have a unique identity and shall be associated with one and only one home environment.
It shall be possible for a home environment to uniquely identify a user by the USIM.
The USIM shall be used to provide security features.
For access to services, provided by PS or CS CN domains, a valid USIM shall be required. Optionally, SIM according to GSM phase 2, GSM phase 2+, 3GPP release 99, 3GPP release 4 specifications may be supported.
The USIM shall be able to support SIM Application Toolkit as specified in 3GPP TS 22.038 [3].
The USIM shall reside on a UICC. USIM specific information shall be protected against unauthorised access or alteration.
It shall be possible to update USIM specific information via the radio interface, in a secure manner.
Access to the IMS services shall be possible using the USIM application in the event of no ISIM being present on the UICC. If an ISIM is present on the UICC it shall be used to access the IMS.
It shall be possible to store provisioning parameters on the USIM according to DM specifications [37].
It should be possible to store provisioning parameters on the USIM according to CP specifications [38].
It shall be possible for the network operator to configure the USIM to indicate (through personalisation and OTA) whether provisioning parameters according to DM specifications or provisioning parameters according to CP specifications shall be used.
NOTE: To avoid misoperation of the UE in a mixed provisioning environment e.g. during a transition phase when both CP and DM clients are present in the UE, the CP parameters on the USIM can be read first. If DMinformation is present (provisioned OTA in the CP parameters.), then use DM, otherwise use CP.
Annex A describes a number of features that may optionally be supported by the UE and thus USIM. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.2 User Profiles | It shall be possible for a user to be associated with one or a number of user profiles, which the user can select and activate on a per call basis. The user profile contains information which may be used to personalise services for the user.
It shall be possible for one or more user profiles associated with the same user to be active simultaneously so that the user may make or receive calls associated with different profiles simultaneously. Activation of profiles shall be done in a secure manner, for example with the use of a PIN.
For terminating calls the correct profile shall be indicated by the user address used (e.g. MSISDN, SIP URI), each profile will have at least one unique user address associated with it. For originating calls the user shall be able to choose from the available profiles, the appropriate one for the call. A profile identity will need to be associated with the call for accounting and billing purposes. User profile identities need not be standardised but a standardised means is required for indicating that a particular profile is being used.
Simultaneous use of the same user profile on multiple terminals for the same type of service shall not be allowed.
User profiles associated with different home environments shall not share the same user address. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.3 UICC usage in GERAN only Terminals | In Release 5 and later, terminals supporting only GERAN shall support USIM.
NOTE: It is strongly recommended that manufacturers implement SIM support on GERAN only terminals until the population of SIMs in the market is reduced to a low level. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.1.4 Multiple USIMs per UICC | The standard shall support more than one USIM per UICC even when those USIMs are associated with different home environments. Only one of the USIMs or the SIM shall be active at a given time. While the UE is in idle mode, it shall be possible for the user to select/reselect one USIM application amongst those available on the UICC. At switch on, the Last Active USIM shall be automatically selected. The Last Active USIM shall be stored on the UICC. By default if there is no Last Active USIM defined in the UICC, the user shall be able to select the active USIM amongst those available on the UICC.
The standard must not prevent the coexistence of USIM applications, each associated with different home environments on the same UICC, so long as the security problems which arise from such a coexistence are solved.
13.1.5 The ISIM
Access to the IMS services shall be possible using an ISIM application.
The ISIM shall be sufficient for providing the necessary security features for the IMS and IMS only.
The ISIM shall reside on a UICC. ISIM specific information shall be protected against unauthorised access or alteration.
It shall be possible to update ISIM specific information via the radio interface, in a secure manner.
NOTE: When accessing IMS over GERAN/UTRAN/EUTRAN or I-WLAN using ISIM, a USIM needs also be present to access the rest of the 3GPP system. Alternatively USIM could be used to access IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2 The UICC | Characteristics including physical formats of a UICC are defined in TS 31.101[36].
Access to services via 3GPP system with a single UICC shall be possible.
NOTE 1: The UICC refers to either a physically distinct module, or to an embedded eUICC (e..g as defined in [62], [63]). |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2.1 The UICC and Applications other than the USIM or ISIM | It shall be possible for the UICC to host other applications in addition to the USIM or ISIM, see figure 3. Service providers, subscribers or users may need to establish additional data or processes on the UICC. Each application on an UICC shall reside in its own domain (physical or logical). It shall be possible to manage each application on the card separately. The security and operation of an application in any domain shall not be compromised by an application running in a different domain. Applications may need to use their own security mechanisms which are separate to those specified by 3GPP e.g. electronic commerce applications.
Examples of UICC applications are: USIM, ISIM, off-line user applications like UPT, electronic banking, credit service, etc.
Applications should be able to share some information such as a common address book.
It shall be possible to address applications, which reside on the UICC, via the radio interface.
Figure 3: Example of a Multifunction UICC
13.2.1a UICC applications and IMS
UICC applications may make use of IMS functionalities controlled by ME.
NOTE: This is to allow a UICC application to interact with an Application Server (AS) through IMS. Examples of UICC applications include identity management, banking applications, etc. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.2.2 Fast Access and Retrieval of Data from UICC | An optional "high speed" interface may be provided between the UICC and the ME.
If provided, this interface shall allow fast access and retrieval of data to support functionalities requiring large amounts of data to be transferred to and from the UICC. Examples include:
- on-card web servers
- rapid access to data stored on the UICC, e.g. phone book, PLMN lists or user data
A UICC/ME interface supporting this "high speed" interface shall be backward compatible with the TS 102 221 interface specified in 3GPP TS 31.101 [36]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.3 Terminals and Multiple UICCs | A single terminal may support the use of multiple UICC (e.g. with applications like USIM and/or banking, credit card,...). Only one UICC shall be active at a time to access a PLMN. In case the active UICC contains more than one USIM, the requirements of 13.1.4 shall apply.
If the UICC with the active USIM is removed from the mobile terminal during a call (except for emergency calls), the call shall be terminated immediately. If the UICC with an active ISIM is removed during an IMS session the IMS session shall be terminated. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 13.4 Multiple USIMs | With the growing demand in the consumer market, some commercially deployed UEs support more than one USIM (typically two). With support of MUSIM UEs in the 3GPP system, the system performance and user experiences are expected to be improved.
The 3GPP system shall support ME with multiple USIMs (on the same UICC or on different UICCs) that are registered at the same time.
The 3GPP system shall treat each registration from the USIMs of a MUSIM UE independently. Each registered USIM in a MUSIM UE shall be associated with a dedicated IMEI/PEI. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 14 Types of features of UEs | 3GPP specifications should support a wide variety of user equipment, i.e. setting any limitations on terminals should be avoided as much as possible. For example user equipment like hand-portable phones, personal digital assistants and laptop computers can clearly be seen as likely terminals.
In order not to limit the possible types of user equipment they are not standardised. The UE types could be categorised by their service capabilities rather than by their physical characteristics. Typical examples are speech only UE, narrowband data UE, wideband data UE, data and speech UE, etc.
In order to enhance functionality split and modularity inside the user equipment the interfaces of UE should be identified. Interfaces like UICC-interface, PCMCIA-interface and other PC-interfaces, including software interfaces, should be covered by references to the applicable interface standards.
UEs have to be capable of supporting a wide variety of teleservices, multimedia services and applications provided in PLMN environment. Limitations may exist on UEs capability to support all possible teleservices, multimedia services and information types (speech, narrowband data, wideband data, video, etc.) and therefore functionality to indicate capabilities of a UE shall be specified.
The basic mandatory UE requirements are:
- Support for USIM. Optional support of GSM phase 2, 2+, 3GPP Release 99 and Release 4 SIM cards [34]. Phase 1, 5V SIM cards shall not be supported. Support for the SIM/ISIM is optional for the UE, however, if it is supported, the mandatory requirements for SIM/ISIM shall be supported in the UE;
Note 1: There is no Release 5 specification for the SIM, and therefore references to "SIM" apply to earlier releases.
Note 2: It is strongly recommended that manufacturers implement SIM support on terminals supporting GERAN until the population of SIMs in the market is reduced to a low level.
- Home environment and serving network registration and deregistration;
- Location update;
- Originating or receiving a connection oriented or a connectionless service;
- An unalterable equipment identification; IMEI, see 3GPP TS 22.016 [12];
- Basic identification of the terminal capabilities related to services such as; the support for software downloading, application execution environment/interface, MExE terminal class, supported bearer services.
- Terminals capable for emergency calls shall support emergency call without a SIM/USIM/ISIM.
- Support for the execution of algorithms required for encryption, for CS and PS services. Support for non encrypted mode is required;
- Support for the method of handling automatic calling repeat attempt restrictions as specified in 3GPP TS 22.001 [4];
- At least one capability type shall be standardised for mobile terminals supporting the GERAN,UTRAN and E-UTRAN radio interfaces.
- Under emergency situations, it may be desirable for the operator to prevent UE users from making access attempts (including emergency call attempts) or responding to pages in specified areas of a network, see 3GPP TS 22.011 [11];
- Ciphering Indicator for terminals with a suitable display;
- The ciphering indicator feature allows the UE to detect that the 3GPP radio interface ciphering (user plane) is not switched on and to indicate this to the user. The ciphering indicator feature may be disabled by the home network operator setting data in the SIM/USIM. The default terminal behaviour shall be to take into account the operator setting data in the SIM/USIM. However, terminals with a user interface that can allow it, shall offer the possibility for the user to configure the terminal to ignore the operator setting data in the SIM/USIM. If this feature is not disabled by the SIM/USIM or if the terminal has been configured to ignore the operator setting data in the SIM/USIM, then whenever a user plane connection is in place, which is, or becomes un-enciphered, an indication shall be given to the user. In addition, if this feature is not disabled by the SIM/USIM or if the terminal has been configured to ignore the operator setting data in the SIM/USIM, then additional information may also be provided about the status of the ciphering. Ciphering itself is unaffected by this feature, and the user can choose how to proceed;
- Support for PLMN selection.
- Support for handling of interactions between toolkits concerning the access to UE MMI input/output capabilities;
- Whenever an application (e.g. a SAT/MExE/WAP application) requires the access to the UE MMI input/output capabilities (e.g. display, keyboard,… ), the UE shall grant this access subject to the capabilities of the UE. This shall not cause the termination of any other applications (e.g. WAP browser or MExE/SAT application) which were previously using these UE resources. The UE shall give the user the ability to accept or reject the new application. In the case that the application request is rejected, the access to the UE MMI input/output capabilities is returned to the applications which were previously using these UE resources. If the user decides to continue with the new application, then when this new application is terminated, the access to the UE MMI input/output capabilities shall be returned to the UE to be re-allocated to applications (e.g. the preceding application which was interrupted). Subject to the capabilities of the UE, the user shall have the ability to switch the MMI input/output capabilities between applications.
NOTE: Rejecting a request to access the UE MMI input/output capabilities by an application does not necessarily mean that it is terminated, but only that the access to the UE MMI input/output capabilities are not granted to this application. Handling of rejection (termination, put on hold,…) is the responsibility of the application.
Annex A describes a number of features which may optionally be supported by the UE. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15 Relationship between subscription and service delivery | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.1 Subscription | A subscription describes the commercial relationship between the subscriber and the service provider.
Figure 4: Subscriber, subscription and services relationship
A subscription to a network operator may provide the user with access to one or more domains. A Subscription shall identify the set of services, within particular domains, to which the user has access (see figure 3); each subscription may specify a different set of services. These services may be provided by the CS CN Domain and/or a PS CN Domain and/or an IM CN subsystem. Subscriptions relate to services such as Basic Services (e.g. Teleservices, Bearer services), PS services and IM-Services (IP-based multimedia services), which are typically provided by network operators, and to value added services which typically are provided by network operators and/or other entities that provide services to a subscriber
The subscription identifies:
- the services and related services information that are made available to the subscriber by the service provider;
In addition, a subscription to a network operator may identify:
- the domains to which the user has been granted access by the network operator. In particular, the PS service profile and information on the allowed QoS parameter ranges shall be contained in the subscription.
- the identity of the subscriber within these domains.
NOTE: The identity of a subscriber in the CS CN domain and PS CN domain (e.g. her IMSI) may potentially be different to her identity in the IM CN subsystem
- the radio access systems over which the subscriber may access their services e.g. UTRAN, GERAN, EUTRAN, I-WLAN. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.2 Other concepts associated with services | Provision of services:
An action to make a service available to a subscriber. The provision may be:
• general: where the service is made available to all subscribers (subject to compatibility restrictions enforced) without prior arrangements being made with the service provider;
• pre‑arranged: where the service is made available to an individual subscriber only after the necessary arrangements have been made with the service provider.
Withdrawal:
An action taken by the service provider to remove an available service from a subscriber's access. The withdrawal may be:
• general: where the service is removed from all subscribers provided with the service;
• specific: where the service is removed on an individual basis from subscribers provided with the service.
NOTE: Access to the IM subsystem requires IP connectivity provided, for example, through provision of the PS CN domain. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3 Requirements concerning service delivery | In general, it is a requirement to allow the use of independent services simultaneously (i.e. Basic, PS, IP multimedia and operator specific).
1) The network usage shall be based on the services identified within the subscription, the terminal capabilities and, where applicable, roaming agreements between operators.
2) The Home environment shall be able to decide on the service delivery in a roaming scenario. I.e. it shall control how services are delivered in line with the subscription.
3) If an offered or required service (e.g. voice) could be provided with different technologies within the serving network, the decision on service delivery shall be based on preferences identified in the user profile and serving network capabilities and conditions (e.g. load).
4) If the user profile does not allow an alternative service delivery method and the requested delivery method is not available in the serving network the service shall not be provided to the subscriber. This applies also to data bearer services with defined QoS parameters (or parameter ranges).
Examples:
- A terminating voice call for a subscriber with a dual/multi mode terminal (e.g. UTRAN/GERAN) could be delivered in a hybrid network as IM service or CS voice call (TS11). The delivery decision is based on the preferences of service delivery within the user profile and the network conditions. If there is no preference information of the Home environment available the decision is made only on the network conditions from the serving network.
- A terminating data service (e.g. PS with QoS for real time audio) where the network cannot provide the QoS at call setup. Both the originating and terminating application shall be informed about the possible QoS configuration for that call. The further handling (setup continuation, termination) depends on the decisions of the applications. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3.1 Mobile Originated Voice calls | When a ME capable of offering voice service both on CS and IMS is CS attached and IMS registered MO CS Voice calls (TS11) and MO IMS voice services shall be originated on the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 15.3.2 Mobile Terminated Voice calls | When a ME capable of offering voice service both on CS and IMS, MT CS Voice calls (TS11) and MT IMS voice services shall be delivered over the domain specified by the Home operator policy or users preferences. The Home Operator policy shall have precedence to user preferences. If the call delivery attempt fails in one domain, if specified by operator policy, it should be possible to attempt the delivery in the other domain or the call/communication forwarding supplementary services [41, 40] may be invoked if provisioned.
NOTE 1: The delivery decision will take into account aspects such as IMS registration and CS attachment status.
NOTE 2: When the terminating network knows that the UE is either IMS registered or CS attached in non-3GPP access (e.g. CDMA), the delivery decision will take this into account in order to select the correct domain. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 16 Charging principles | The cost of the call may cover the cost of sending, transporting, delivery and storage. The cost of call related signalling may also be included. Provision shall be made for charging based on time, destination, location, volume, bandwidth, access technology and quality. Charges may also be levied as a result of the use of value-added services.
It shall be possible for information relating to chargeable events to be made available to the home environment at short notice. The requirements shall include:
- Immediately after a chargeable event is completed;
- At regular intervals of time, volume or charge during a chargeable event.
- Delivery of the location of the terminal to the home environment, e.g. cell identification;
Standardised mechanisms of transferring charging information are required to make these requirements possible.
It should be possible for multiple leg calls (e.g. forwarded, conference or roamed) to be charged to each party as if each leg was separately initiated. However, in certain types of call, the originating party may wish/be obliged to pay for other legs (e.g. SMS MO may also pay for the MT leg.).
It shall be possible to charge according to the location (e.g. cell, or zone) and access technology that are being used to access network services.
Provision shall be made for the chargeable party to be changed during the life of the call. There shall be a flexible billing mechanism which may include the use of stored value cards, credit cards or similar devices.
The chargeable party (normally the calling party) shall be provided with an indication of the charges to be levied (e.g. via the called number automatically or the Advice of Charge supplementary service) for the duration of the call (even though the user may change service environment)The user shall be able to make decisions about the acceptable level of accumulated charge dynamically or through their service profile.
If a user is to be charged for accepting a call then their consent should be obtained. This may be done dynamically or through their service profile.
Charging and accounting solutions shall support the shared network architecture so that end users can be appropriately charged for their usage of the shared network, and network sharing partners can be allocated their share of the costs of the shared network resources. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17 Roaming | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17.1 Assumptions | In order to roam, the following applies:
- Mobile terminal can connect to the radio access network.
- Authentication (charging/billing network) must occur in order to get access to services (except for emergency calls).
- The services offered to a roaming subscriber may be restricted by the capabilities of the visited network, and the roaming agreement between the visited and the home environment.
17.2 Principle
Long term evolution of the IM CN subsystem shall not be restricted by the short/mid-term inter-domain roaming requirements. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 17.3 Requirements | Figure 5: Roaming requirements
- The personalised services & capabilities available in a visited network are dependent upon the subscription options in the home environment. This does not preclude the visited network offering additional services, or access to content providers.
- Roaming from this release's home environment to CS (this release or earlier) visited network is required
- Roaming from this release's home environment to IM CN subsystem visited network is required
- Roaming from this release's home environment to PS (this release or earlier) visited network is required
- Roaming from previous releases' home environment (or earlier) to this release CS visited network is required
- Roaming from previous releases' home environment (or earlier) to this release PS visited network is required
NOTE: When an operator allows a subscriber to roam to different domains, the home environment needs to provide subscription data to the visited network . The mapping between service data of the different domains is not standardised; it is determined by the home environment and may be influenced by roaming agreements. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 18 Handover Requirements | Any handover required to maintain an active service while a user is mobile within the coverage area of a given network, shall be seamless from the user's perspective. However handovers that occur between different radio environments may result in a change of the quality of service experienced by the user.
It shall be possible for users to be handed over between different networks subject to appropriate roaming/commercial agreements.
For further information see 3GPP TS 22.129 [9]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 19 Network Selection | Network selection procedures are defined in 3GPP TS 22.011 [11].
Other procedures may be offered by the UE. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 20 Security | Security matters are considered in 3GPP TS 21.133 [15] and 3GPP TS 33.120 [16]. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21 Voice Call Continuity | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.1 General | The 3GPP system shall be able to provide continuity between CS voice services (Teleservice 11[14]) and the full duplex speech component of IMS multimedia telephony service [40] with no negative impact upon the user's experience of the voice service. This functionality is known as voice call continuity. Voice call continuity shall be executed when continuation of a voice service is required based on operator policy across a change in the connection of the UE to the 3GPP system as the user moves from using the CS domain to using IMS and vice versa.
The user experience shall be unaffected by the transition from a CS voice service to a full duplex speech component of IMS multimedia telephony and vice versa, and the user shall experience no disruption in the voice service provided. The voice service is continued with the same ME.
It shall be possible to support Voice call continuity between IMS and the CS domain belonging to different operators; i.e., when the user's IMS services are under the control of the home IMS and the user is roaming in the coverage of the visited CS network.
It shall be possible for an operator to enable or disable Voice call continuity for a given subscriber e.g. based on roaming conditions, terminal capabilities. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2 Support of Supplementary Services | The voice call continuity user's experience shall be such that, to the greatest degree possible, a consistency of service is provided regardless of the underlying communication infrastructure and technology. With regard to supplementary services, the general principle is that CS-based supplementary services only apply whilst a VCC subscriber is in the CS domain and equivalent services over IMS only apply whilst a VCC subscriber is in the IMS domain, although there are exceptions listed below. It is not required to synchronise the supplementary service settings of the CS domain with the related service settings of the IMS (e.g. different forwarding numbers may apply over CS and over IMS).
The following supplementary services apply. The impact on the supplementary services in case the VCC is executed for the calling party, the called party, or both is described below. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.1 Line Identification Services | A user who has subscribed to the CLIP Supplementary Service and receives a call shall also receive the line identity or appropriate IMS information of the calling party.
The identity presentation is not changed for the duration of the call regardless of whether the call undergoes VCC.
If the CLIR Supplementary Service or IMS identity restriction is applicable to the call, then at call setup time the called user shall receive an indication that the identity is not available because of restriction.
The indication is not changed for the duration of the call regardless of whether the call undergoes VCC.
If COLP or a corresponding IMS service is applicable to a call the calling subscriber shall receive the connected line identity or appropriate IMS information at call setup time.
The identity presentation is not changed for the duration of the call regardless of whether the call undergoes VCC.
If the COLR Supplementary Service or IMS identity restriction is applicable to the call, then the calling user shall receive an indication at call setup time that the identity of the connected party is not available because of restriction.
The indication is not changed for the duration of the call regardless of whether the call undergoes VCC. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.2 All Call Forwardings | It shall be possible to perform VCC on a call which was forwarded due to call forwarding supplementary services in the CS or redirecting services in the IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.3 Call Waiting | The functionality of call waiting supplementary service in the CS domain shall not be affected by the user's ability to undergo VCC.
NOTE: Whether the user will continue to receive call waiting notifications in the case their call is continued in the IMS will depend on whether a call waiting service is available in the IMS. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.4 Call Hold | It shall be possible to re-establish a call which has been put on hold before undergoing VCC, after the VCC has been performed. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.5 Multiparty | It shall be possible for any party in a multiparty call to undergo VCC and to stay in the call. It shall be possible to terminate the entire multiparty call when the served mobile subscriber releases even if she is connected via the IMS after undergoing VCC. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.6 All Call Barrings | If a call were to undergo VCC and that would result in the call being barred in the target domain/system, it shall be up to the home operator policy whether the call continues in the target domain/system, the call terminates, or VCC is not executed for the call. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.7 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.8 Void | |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.2.9 All other Supplementary Services | Other supplementary services are not discussed in this section as they do not apply to calls in progress (i.e. they apply to call set up only) or their support and/or the need for standardised implementation has not been identified as critical for VCC in this Release. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.3 Quality of Service | Voice call continuity shall not adversely impact the quality of the voice service experienced by the user. |
e63674806edc16f438f86b5fe12a65a6 | 22.101 | 21.4 Security | Voice call continuity shall not adversely impact the security of the 3GPP system.
Security mechanisms of the 3GPP system shall be reused for voice call continuity. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.