3GPP TS 22.368 V10.5.
0 (2011-06)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 10)
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
Keywords
Service, requirement, machine
3GPP Postal address
3GPP support office address
650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2011, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark of ETSI registered for the benefit of its members 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners LTE is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners GSM and the GSM logo are registered and owned by the GSM Association
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
Contents
Foreword............................................................................................................................................................. 5 1 2 3
3.1 3.2
Scope ........................................................................................................................................................ 6 References ................................................................................................................................................ 6 Definitions and abbreviations................................................................................................................... 6
Definitions ......................................................................................................................................................... 6 Abbreviations ..................................................................................................................................................... 7
4 5
5.1 5.1.1 5.1.2 5.1.3 5.2
Overview of system optimisations for machine-type communications ................................................... 8 MTC communication aspects ................................................................................................................... 8
MTC communication scenarios ......................................................................................................................... 8 Introduction .................................................................................................................................................. 8 MTC devices communicating with one or more MTC servers .................................................................... 8 MTC devices communicating with each other ............................................................................................. 9 (void) ............................................................................................................................................................... 10
6 7
7.1 7.1.1 7.1.2 7.1.3 7.1.4 7.1.5 7.1.6 7.1.7 7.2. 7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.11 7.2.12 7.2.13 7.2.14
(void) ...................................................................................................................................................... 10 Service requirements .............................................................................................................................. 10
Common service requirements ........................................................................................................................ 10 General ....................................................................................................................................................... 10 (void) .......................................................................................................................................................... 10 (void) .......................................................................................................................................................... 10 Identifiers ................................................................................................................................................... 10 Charging requirements ............................................................................................................................... 11 Security requirements ................................................................................................................................. 11 Remote MTC device management ............................................................................................................. 11 Specific service requirements MTC Features ............................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11 (void) .......................................................................................................................................................... 11
Annex A (informative): Annex B (informative): Annex C (informative):
Use cases ......................................................................................................... 12 Examples of MTC applications .................................................................... 16 Change history ............................................................................................... 17
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
1
-
Scope
identify and specify general requirements for machine type communications; identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications; specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.
The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will:
References
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] [2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". 3GPP TS 22.011: " Service accessibility".
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
3
3.1
Definitions and abbreviations
Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. MTC Device: A MTC Device is a UE equipped for Machine Type Communication, which communicates through a PLMN with MTC Server(s) and/or other MTC Device(s). NOTE: A MTC Device might also communicate locally (wirelessly, possibly through a PAN, or hardwired) with other entities which provide the MTC Device raw data for processing and communication to the MTC Server(s) and/or other MTC Device(s). Local communication between MTC Device(s) and other entities is out of scope of this technical specification.
MTC Server: A MTC Server is a server , which communicates to the PLMN itself, and to MTC Devices through the PLMN. The MTC Server also has an interface which can be accessed by the MTC User. The MTC Server performs services for the MTC User. MTC User: A MTC User uses the service provided by the MTC Server. MTC Subscriber: A MTC Subscriber is a legal entity having a contractual relationship with the network operator to provide service to one or more MTC Devices. NOTE: Typically a M2M service provider is the party holding subscriptions in order to provide connectivity between MTC Devices and the MTC Server. In practise certain roles can collapse, e.g. the network operator acts as the same time as Service Provider.
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
3.2
Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. NIMTC MNO MTC Network Improvements for Machine Type Communications Mobile Network Operator Machine-Type Communications
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
Overview of system optimisations for machine-type communications
Machine type communication is a form of data communication which involves one or more entities that do not necessarily need human interaction. A service optimised for machine type communications differs from a service optimised for Human to Human communications. Machine type communications is different to current mobile network communication services as it involves: a) different market scenarios, b) data communications, c) lower costs and effort, d) a potentially very large number of communicating terminals with, e) to a large extent, little traffic per terminal. For the purpose of the present document, the term MTC is used for the purpose to describe use-cases and illustrate the diverse characteristics of machine type communication services. The informative annex A gives an overview of MTC use-cases which also illustrate different overload scenarios which will require overload control functions to prevent overload and to differentiate between services offered to different subscribers with different service requirements. In particular, certain MTC services and MTC applications, as exemplified in annex B, are more tolerant and can accept a lower level of performance requirements for its communication services. However some MTC services will have similar service requirements as current mobile network communication services.
5
5.1
5.1.1
MTC communication aspects
MTC communication scenarios
Introduction
For MTC communication the following communication scenarios can be identified: a) MTC Devices communicating with one or more MTC Server b) MTC Devices communicating with each other
5.1.2
MTC devices communicating with one or more MTC servers
The network operator provides network connectivity to MTC Server(s). This applies to MTC Server(s) controlled by the network operator (refer to figure 5-1) or to MTC Server(s) not controlled by the network operator (refer to figure 5-2.)
3GPP
Release 10
3GPP TS 22.368 V10.5.0 (2011-06)
Operator domain
MTC Server
API
MTC User
MTC Device MTC Device MTC Device MTC Device
Figure 5-1: Communication scenario with MTC devices communicating with MTC server. MTC server is located in the operator domain.
Operator domain
MTC Device MTC Device MTC Device MTC Device
MTC Server/ MTC User
Figure 5-2: Communication scenario with MTC devices communicating with MTC server. MTC server is located outside the operator domain.
5.1.3
MTC devices communicating with each other
The communication scenario where the MTC Devices communicate directly without intermediate MTC Server (refer to figure 5-3) is not considered in this release of the specification.
MTC Device MTC Device MTC Device MTC Device
Operator domain A
Operator domain B
MTC Device MTC Device MTC Device MTC Device
Figure 5-3: MTC Devices communicating directly with each other without intermediate MTC server.
3GPP
Release 10
10
3GPP TS 22.368 V10.5.0 (2011-06)
5.2
(void)
6 7
7.1
7.1.1
-
(void) Service requirements
Common service requirements
General
The following are MTC common service requirements: The network shall provide a mechanism to reduce peaks in the data and signalling traffic resulting from very large numbers of MTC Devices (almost) simultaneously attempting data and/or signalling interactions. The network shall provide a mechanism to restrict downlink data and signalling when the network is overloaded. The network shall provide a mechanism to restrict access towards a specific APN when the network is overloaded. A MTC Device may support the Extended Access Barring (EAB) mechanism defined in TS 22.011 [x] A MTC Device supporting the EAB mechanism shall be able to be configured for EAB by the HPLMN. The HPLMN shall be able to configure EAB on a MTC Device that supports it. Once configured, and upon reception of broadcasted EAB information, the MTC Device shall adhere to the defined EAB mechanisms. Note: The decision of whether a MTC Device is configured for EAB is out of 3GPP scope. In general, MTC Devices considered more tolerant to access restrictions are well suited to be configured for EAB.
The system shall provide mechanisms to efficiently maintain connectivity for a large number of MTC Devices. The network operator shall be able to reduce the frequency of mobility management procedures. Configuration parameters which are provided in the USIM shall take precedence over parameters provided in the MTC Device if both exist.
7.1.2 7.1.3 7.1.4
-
(void) (void) Identifiers
The requirements for MTC related to identifiers include the following: The system shall be able to uniquely identify the ME. The system shall be able to uniquely identify the MTC Subscriber. The two requirements above also apply to human-to-human communications. However, for MachineType Communication identifiers will have to be able to cater for a number of identifiers at least two orders of magnitude higher than for human-to-human communications.
NOTE:
3GPP
Release 10
11
3GPP TS 22.368 V10.5.0 (2011-06)
The system shall provide mechanisms for the network operator to efficiently manage numbers and identifiers related to MTC Subscribers.
7.1.5
Charging requirements
No MTC specific charging requirements have been identified in this release.
7.1.6
-
Security requirements
The security requirements for MTC include the following: MTC optimizations shall not degrade security compared to non-MTC communications
7.1.7
Remote MTC device management
The management of MTC Devices should be provided by existing mechanisms (e.g. OMA DM)
7.2.
7.2.1 7.2.2 7.2.3 7.2.4 7.2.5 7.2.6 7.2.7 7.2.8 7.2.9 7.2.10 7.2.11 7.2.12 7.2.13 7.2.14
Specific service requirements MTC Features
(void) (void) (void) (void) (void) (void) (void) (void) (void) (void) (void) (void) (void) (void)
3GPP
Release 10
12
3GPP TS 22.368 V10.5.0 (2011-06)
Annex A (informative): Use cases
Addressing from a centralized entity Use Case Metering devices are typically monitored and controlled by a centralized entity outside or inside the network operator system. Due to the need for centralized control, the centralized entity will inform or poll the metering device when it needs measurement information rather than the metering device autonomously sending measurements. Depending on the nature of the metering application, low latency responses are sometimes required (metering for high pressure pipelines for example). To accomplish this, the centralized entity will need to inform the metering device when it needs a measurement. Typically due to the limitation of IPv4 address space, the metering terminal is behind a NAT (Network Address Translator) where it is not assigned a routable IPv4 address. Theft /Vandalism Vulnerable MTC Application Use Case In contrast to the traditional H2H devices, which are carefully held and protected by a person, MTC Devices are often located in remote areas and ideally are untouched after installation for many years. The remote locales make these devices more susceptible to tampering by unauthorised persons. The tampering of the MTC Device is often accompanied by damage to the metering device. The network has security mechanisms for protection for this type of activity which may not be effective for MTC Devices. The network can not prevent it but can detect it as early as possible in order to deactivate the MEs service and the related USIM. In addition, often theft/vandalism vulnerable MTC Devices are stationary after initial installation and activation. The stationality of the MTC Device can be utilized to improve the detection of theft. If a known stationary devices moves, it can be concluded that the MTC Device has been stolen and thus the account deactivated. Time Controlled MTC Application Use Case For some MTC applications the actual time at which communication takes place is less important, but low communication costs are extremely important. A network operator can offer low communication fees for this type of applications by allowing communication to take place during low traffic time periods only. Possibly the network operator may want to dynamically adjust these time periods based on the actual network traffic load at a specific time. Radio Network Congestion Use Case Radio network congestion because of mass concurrent data transmission takes place in some MTC applications. One of the typical applications is the bridge monitoring with a mass of sensors. When a train passes through the bridge, all the sensors transmit the monitoring data almost simultaneously. The same thing happens in hydrology monitoring during the time of heavy rain and in building monitoring when intruders break in. The network should be optimized to enable a mass of MTC Devices in a particular area to transmit data almost simultaneously. Core Network Congestion Use Case With many MTC applications, a large number of MTC Devices is affiliated with a single MTC User. These MTC Devices together are part of a MTC Group. The MTC User associated with the MTC Group owns a MTC Server which is connected to the PS network of a mobile network operator via an Access Point Name (APN) using the Gi interface. The MTC Devices in the MTC Group communicate with this MTC Server. Typically, the MTC Devices in the MTC Group are scattered over the network in such a way that the data simultaneously sent by the MTC Devices in any particular cell is limited and will not cause a radio network overload. Despite this, when a high number of MTC Devices are sending/receiving data simultaneously, data congestion may occur in the mobile core network or on the link between mobile core network and MTC Server where the data traffic related to MTC Group is aggregated. Preferably, a network operator and the MTC User have means to enforce a maximum rate for the data sent/received by the MTC Group.
3GPP
Release 10
13
3GPP TS 22.368 V10.5.0 (2011-06)
Figure A-1: Congestion in mobile core network and on the link between mobile core network and MTC Server
Signalling Network Congestion Use Case Congestion in the signalling network is caused by a high number of MTC Devices trying almost simultaneously: (1) to attach to the network or (2) to activate/modify/deactivate a connection. In a 3GPP system supporting MTC applications such an overload of the network can be caused by e.g. many mobile payment terminals that become active on a national holiday or by high numbers of metering devices becoming active almost simultaneously after a period of power outage. Also some MTC applications generate recurring data transmissions at precisely synchronous time intervals (e.g. precisely every hour or half hour). Preferably, the 3GPP system provides means to the network operator and MTC User to spread the resulting peaks in the signalling traffic.
Large number of vending machines
SGSN
Radius GW MTC Server
HSS
MME
Figure A-2: Signalling network congestion.
Access Control with billing plan Use Case In some configurations, it may be necessary to restrict the access of a UICC that is dedicated to be used only with machine type modules associated with a specific billing plan. It should be possible to associate a list of UICC to a list of terminal identity such as IMEISV so that if the UICC is used in an other terminal type, the access will be refused. See the following configuration:
3GPP
Release 10
14
3GPP TS 22.368 V10.5.0 (2011-06)
Machine type module
USIM
Ubiquitous plan
Accepted
SGSN GGSN
Notification of IMEISV (machine type module)
others
USIM
Ubiquitous plan
Denied
SGSN
GGSN
Handset or cart type
Notification of IMEISV (handset or cart type)
Figure A-3: Access Control with billing plan
Extra Low Power Consumption Use Case For high mobility case, tracking MTC devices such as animal tracking MTC devices in natural world with high mobility require extra low power consumption because it is almost impossible to replace the battery or recharge the battery for animal tracking MTC device. Compared to the tracking devices installed in the cars and trucks because cars and trucks could generate electricity by themselves, extra low power consumption for these MTC devices is required. For cargo tracking, the cargo with a tracking MTC device could move very fast such as on a train or lorry and could stand still such as in the dock before loading or unloading. It is not desired to either change its battery or replace battery during the transport period, so extra low power consumption MTC devices are also required. For prisoner tracking MTC devices are already used by police, prisoners will not cooperate with police and would wish the MTC devices have flat batteries; therefore, extra low power consumption feature is required for these MTC devices. For the tracking MTC devices of elder people who have memory problem, children or pets, even the batteries of these MTC devices could be replaced or charged, however, considering the worst scenario if they are missing, it requires the MTC devices with extra low power consumption and long working time in order to find them. For low mobility case, the gas meter MTC devices must be battery powered. Extra low power consumption for gas MTC devices is much more critical than electricity meters. Extra Low Power Consumption with Time Controlled MTC Devices Use Case Time Controlled MTC Devices which send or receive data only at certain pre-defined periods may be operated in one or more modes that minimize power consumption. An MTC Device may be operated in a mode where it is expected to receive non-periodic messages (e.g., emergency messages or notifications of altered access period as with the MTC Feature Time Controlled outside the time controlled periods. The MTC Device should minimize power consumption while in a mode to support this. If the application requires the MTC Device to send or receive data within pre-defined periods and receive non-periodic messages outside these periods, operation at the lowest possible power consumption level to extend battery life should be achieved. Location Specific MTC Devices Trigger Use Case
3GPP
Release 10
15
3GPP TS 22.368 V10.5.0 (2011-06)
MTC Devices are generally programmed to autonomously set up a connection to report an event. However, in some implementations it is required that MTC Devices are triggered by the M2M application e.g. by sending them a SMS. In the future millions of this type of MTC Devices will be deployed, while it may be desirable from a M2M application perspective to poll only a sub-set of the MTC Devices in a specific area. For example, during a storm a water authority wants to get status information of dike sensors in a specific area. It is then required that only sensors in that specific area are triggered. As for several M2M applications the MTC Devices are at fixed locations, which are well known by the M2M application owner, it is a waste of network resources to store the location information of these MTC devices in the network. Also scalability issues will come in play if millions of terminals need to be polled in a relative short time. A more efficient and scalable polling mechanism is required to trigger M2M devices based on location information provided by the application or user, to subsequently set up a data or other type of connection e.g. a SMS, PDP context to the network. End-to-end security for roaming MTC devices An MTC Application communicates with a large number of MTC Devices that are located globally and may or may not be mobile. Examples of such devices are mobile navigation systems and payment terminals. Connectivity for the MTC Devices is provided by a single network operator that uses its roaming agreements to connect MTC Devices that are not within range of its own network. From the perspective of the operator of the MTC application its MTC Server and the domain of its network operator are part of a trusted domain. However, the domain of the roaming operator are not seen as part of the trusted domain, as is depicted in the figure below.
trusted domain
Operator Operator domain domain
MTC Server
Operator Operator domain domain
Operator Operator domain domain
Operator Operator domain domain
MTC Device
MTC Device
MTC Device
MTC Device
Figure A-4: End-to-end security for roaming MTC devices The operator of the MTC application therefore requires end-to-end security for messages exchanged between MTC application and MTC Devices. The network operator does not have control over the security features in the domain of the roaming operators. Furthermore, for efficiency reasons the roaming operators may decide on a local breakout to for instance the Internet for MTC traffic in which case the information partly travels over the Internet. The network operator needs to satisfy the MTC application owners end-to-end security requirement without relying on network security alone.
3GPP
Release 10
16
3GPP TS 22.368 V10.5.0 (2011-06)
Annex B (informative): Examples of MTC applications
Some examples of machine-type communication applications are listed in the following table. This list is not exhaustive and is intended to be indicative of the scope of machine-type communication applications.
Service Area Security MTC applications Surveillance systems Backup for landline Control of physical access (e.g. to buildings) Car/driver security Fleet Management Order Management Pay as you drive Asset Tracking Navigation Traffic information Road tolling Road traffic optimisation/steering Point of sales Vending machines Gaming machines Monitoring vital signs Supporting the aged or handicapped Web Access Telemedicine points Remote diagnostics Sensors Lighting Pumps Valves Elevator control Vending machine control Vehicle diagnostics Power Gas Water Heating Grid control Industrial metering Digital photo frame Digital camera eBook
Tracking & Tracing
Payment
Health
Remote Maintenance/Control
Metering
Consumer Devices
3GPP
Release 10
17
3GPP TS 22.368 V10.5.0 (2011-06)
Annex C (informative): Change history
TSG SA# SA Doc. SP-47 SP-47 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SP-48 SA1 Doc Spec 22.220 22.220 22.368 22.368 22.368 22.368 22.368 CR 0001 0003 0005 0006 0009 0010 0011 0013 0014 0015 0017 Rev Rel 2 2 1 1 3 2 1 Cat Subject/Comment Raised from v1.2.2 to v.2.0.0 for approval Raised from v.2.0.0 to v.10.0.0 after approval of SA#47 Deletion of section 5.2 Clarification of PAM CR to TS22.368 Clarification of Location Specific Trigger CR to TS22.368 Clarification of Infrequent Transmission Clarification of Requirements for Time Controlled MTC Feature Clarification and completion of PAM requirements Clarification of local network in Time Controlled Correction of missing changes to clause 7.2.2 Correction of terminology Clarification of "may" in clause 7.2.2 Correction of MTC User shall in 7.2.8 Simplification of Mobile Originated Only feature Simplification of Infrequent Mobile Terminated feature Clarification of MTC Monitoring feature Clarification of Group Based MTC Features Clarification of subscription Clarification on MTC Server relationship to network operator Clarification of Location Specific Trigger MTC Group Features definition clarification MTC Infrequent Transmission clarification MTC Secure Connection MTC Time Controlled clarification Alignment with Stage 2 NIMTC Terminology Clarification of data delay in case of Overload LTE logo changed into LTE Advanced logo SA2 Alignment for MTC Time Tolerant Feature MTC charging requirements in Rel-10 Clarification of EAB Removal of Rel-10 MTC Charging requirements Deletion of requirement on MTC USIM for Release 10 Correction of NIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM Old 1.2.2 2.0.0 New 2.0.0 WI NIMTC SP-100192 -
10.0.0 NIMTC
SP-100400 S1-101157 SP-100400 S1-101158 SP-100400 S1-101138 SP-100400 S1-101139 SP-100400 S1-101159
Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F
10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC 10.0.0 10.1.0 NIMTC
SP-100435 S1-101143r 22.368 SP-100400 S1-101142 SP-100400 S1-101077 SP-100400 S1-101078 SP-100400 S1-101080 SP-100400 S1-101083 22.368 22.368 22.368 22.368 22.368
SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-49 SP-50 SP-50 SP-50 -
SP-100579 S1-102258 SP-100579 S1-102259 SP-100579 S1-102260 SP-100579 S1-102264 SP-100579 S1-102280 SP-100579 S1-102281 SP-100579 S1-102282 SP-100579 S1-102287 SP-100579 S1-102288 SP-100579 S1-102289 SP-100579 SP-100861 SP-100798 SP-100798 S1-102290 S1-103226 S1-103312 S1-103311
22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368 22.368
0023 0024 0025 0029 0038 0018 0027 0034 0035 0036 0037 0046 0049 0051
1 1 1 1 2 2 2 1 1 1 2 2 2 2
Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 Rel-10 Rel-10 Rel-10 F F F B
10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 NIMTC 10.1.0 10.2.0 10.2.0 10.2.0 10.2.0 10.3.0 10.3.0 10.3.0 NIMTC NIMTC NIMTC NIMTC
10.3.0 10.3.1 -
SP-51 SP-51 SP-51 SP-52 SP-52 SP-52
SP-110162 S1-110364 SP-110162 S1-110374 SP-110162 S1-110410 SP-110370 S1-111306 SP-110370 S1-111309 SP-110370 S1-111372
22.368 22.368 22.368 22.368 22.368 22.368
0064 0067 0070 0074 0093 0090
1 1 1 1 2
Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F Rel-10 F
10.3.1 10.4.0 NIMTC 10.3.1 10.4.0 NIMTC 10.3.1 10.4.0 NIMTC 10.4.0 10.5.0 NIMTC 10.4.0 10.5.0 NIMTC 10.4.0 10.5.0 NIMTC
3GPP
