Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.401  Word version:  18.5.0

Top   Top   Up   Prev   None
1…   4…   4.2.2…   4.3…   4.3.6…   4.3.8…   4.3.12…   4.3.16…   4.3.20…   4.3.25…   4.4…   4.6…   4.7…   5…   5.1.2…   5.3…   5.3.2…   5.3.3…   5.3.3.2   5.3.3.3…   5.3.4…   5.3.4B…   5.3.5…   5.3.8…   5.3.9…   5.4…   5.4.4…   5.5…   5.5.1.2…   5.5.2…   5.5.2.2…   5.5.2.3…   5.5.2.4…   5.6…   5.7.3…   5.7A…   5.10   5.11…   5.19…   D…   D.3…   D.3.4   D.3.5   D.3.6   D.3.7…   D.3.8…   E   F…   J…   K…   L…   M…

 

M  Functions and procedures over NB-IoT RAT |R13|p. 445

In the case of conflict between the information in this Annex and other information in the main body of the present document, the information in the main body takes precedence.
The following Tables list the functions and procedures that are:
  • Supported or not supported over NB-IoT RAT, including whether for CP CIoT EPS Optimisation only, UP CIoT EPS Optimisation only or both.
  • Optional for the UE and/or network when using NB-IoT RAT.
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
4.3.3IP header compression
RoHC (NAS)
YesCPOptionalOptional
RoHC (AS)
YesUPOptionalOptional
4.3.5Mobility management functionsYesBoth
Inter-RAT idle mode NAS mobility (WB-E_UTRAN, UTRAN, GERAN)
YesBoth
Reachability management
YesBothISR OptionalISR Optional
TA list management (2)
YesBoth
ISR
YesBothOptional
Mobility restrictions
YesBoth
IMS voice over PS session supported indication
NoN/AN/AN/A
Voice domain preference and UE usage setting
NoN/AN/AN/A
Preferred and supported network behaviour
YesBoth
4.3.7.1a.2GTP-C Overload ControlYesCPN/A
4.3.7.4MME control of overloadYesBothN/A
Extended Access Barring
NoN/AN/AN/A
4.3.7.4.2.7Control Plane data specific NAS level congestion controlYesCP
4.3.12IMS emergency sessionNoN/AN/AN/A
4.3.12aSupport of Restricted Local Operator ServiceNoN/AN/AN/A
4.3.13Closed Subscriber GroupNoN/AN/AN/A
4.3.17Support for MTC
Low access priority
YesBothOptional
Non-IP data delivery (NIDD)
YesBoth
NIDD SCEF
YesCPN/A (1)Optional (3)
NIDD SGi
YesBothN/A (1)Optional (3)
4.3.18Multimedia Priority ServiceNoN/AN/AN/A
4.3.22Power Save ModeYesBothOptionalOptional
4.3.27aRestriction of use of Enhanced Coverage for voice centric UENoN/AN/AN/A
4.3.27bRestriction of use of Enhanced Coverage for data centric UENoN/AN/AN/A
4.3.28Restriction of use of Enhanced CoverageYesBothOptional
4.3.293GPP PS Data OffYesBothOptionalOptional
4.7QoS
PDN connection to SCEF
YesCPOptional
Dedicated bearer
NoN/AN/AN/A
GBR bearer
NoN/AN/AN/A
Non-GBR bearer
YesUP
Rate control (Serving PLMN)
YesCPOptional
Rate control (APN)
YesBothOptional
4.7.8Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS OptimisationYesYesN/AOptional
4.10CIoT EPS Optimisation
UP
YesUPOptionalOptional
CP
YesCP
NOTE 1:
Whether the non-IP PDN connection is provided via SCEF or over SGi is transparent to the UE.
NOTE 2:
Required for inter-RAT idle mode mobility.
NOTE 3:
At least one of NIDD SCEF and NIDD SGi is required.
 
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
5.3.1IP address allocation (1)YesBothNot required for NIDD
5.3.2Attach procedureYesBoth
Normal attach
YesBothOptional (2)
Attach without PDN connectivity
YesBothOptional (2)Optional
Emergency attach
NoN/AN/AN/A
SMS transfer without Combined Attach
YesBothOptional
5.3.3TAU procedureYes (3)Both
5.3.4Service request proceduresYesBoth (4)
5.3.4AConnection Suspend procedureYesUP
5.3.4BData transport in CP CIoT EPS OptimisationYesCP
Reliable data delivery with hop-by-hop acknowledgement
YesCPN/AOptional
5.3.5S1 release procedureYes (5)
5.3.5AConnection resume procedureYesUP
5.3.6APDN-GW pause of charging procedureYesBothN/AOptional
5.3.7GUTI reallocation procedureYesBoth
5.3.8Detach procedureYes (6)Both
5.3.10Security functionYesBoth
AS security
YesUP
NAS security
YesBoth
5.3.14UE radio capability match requestNo (7)N/AN/AN/A
NOTE 1:
Incl. attach without PDN connectivity.
NOTE 2:
At least one of Normal attach and Attach without PDN connectivity is required.
NOTE 3:
Incl. inter RAT.
NOTE 4:
Also supported with CP CIoT EPS Optimisation when the UE/MME also support S1-U data transfer or UP CIoT EPS Optimisation.
NOTE 5:
Releases the S11-U bearer in the case of CP CIoT EPS Optimisation. RRC Connection release is used with the UE.
NOTE 6:
ISR aspects optional.
NOTE 7:
IMS Voice not supported over NB-IoT.
 
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
5.4.1Dedicated bearer activationNoN/AN/AN/A
5.4.2Bearer modification with QoS updateYesUPOptionalOptional
5.4.3PDN-GW initiated bearer modification without bearer QoS updateYesUP
5.4.4Bearer deactivationYesUP
5.4.5UE-requested bearer resource modificationYesBothOptional with CP CIoT EPS Optimisation
5.4.7E-UTRAN initiated ERAB modification procedureNo (1)N/AN/AN/A
5.4.8E-UTRAN initiated UE context modification procedureNo (1)N/AN/AN/A
NOTE 1:
Dual connectivity not supported over NB-IoT RAT.
 
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
5.5HandoverNo
5.5.1Intra-E-UTRAN handoverNoN/AN/AN/A
5.5.2Inter RAT handoverNoN/AN/AN/A
5.6Network assisted cell changeNoN/AN/AN/A
 
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
5.8MBMS (3)(3)(3)(3)(3)
5.10Multiple PDN support and PDN activation for UEs supporting Attach without PDN connectivityYes (1)Both
5.11UE capability handlingYesBoth
5.12Warning message deliveryNoN/AN/AN/A
5.13DRX and UE-specific DRX parameter handlingYes (2)Both
5.13aExtended idle mode DRXYesBothOptionalOptional
5.15RAN information management proceduresNoN/AN/AN/A
5.16MME-initiated procedure on UE's CSG membership changeNoN/AN/AN/A
5.17HeNB multicast packet forwarding functionNoN/AN/AN/A
NOTE 1:
Multiple PDN optional.
NOTE 2:
UE-specific DRX not supported in NB-IoT RAT.
NOTE 3:
See Table M-6.
 
Clause Clause title Support
NB-IoT RAT CP/UP/Both UE NW
4.5.14.3Reliable Data ServiceYesCPOptionalOptional
4.5.15,
5.14
Support of Packet Flow Description management via SCEFYesBothN/AOptional
4.5.16MSISDN-less MO-SMS via T4YesBothOptionalOptional
4.5.18MBMS user service for UEs using power saving functionsYesBothOptionalOptional
4.5.19Enhancements to Location Services for CIoTYesBothOptionalOptional
NOTE:
This table lists MTC/CIoT-related items in TS 23.682 not otherwise specified in the present specification.
 
Up

N  Satellite coverage availability information |R18|p. 449

The protocol and format of satellite coverage availability information to be provisioned to the UE via a PDN connection or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where:
  • these indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available);
  • locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal);
  • coverage availability times may occur at fixed periodic intervals; and
  • coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs.
If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE.
In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server):
  • Serving PLMN ID (if not already known or implied).
  • One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types).
  • List of supported satellite frequency bands (if not implied by the particular RAT Types).
  • Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point).
  • Type of Array (e.g. rectangular or hexagonal).
  • Minimum elevation angle.
Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations:
Satellite coverage availability information at a given grid point = <N> <Binary 0 or 1><Duration 1> <Binary 0 or 1><Duration 2> . . . . <Binary 0 or 1><Duration N>
The above would be concatenated for all of the grid points to produce the satellite coverage availability information.
When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format.
Up

$  Change historyp. 450


Up   Top