Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.2.5…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.8…   16.9…   16.10…   16.12…   16.12.5…   16.12.6…   16.12.6.3   16.12.7   16.13…   16.14…   16.15…   16.18…   16.19…   16.21…   16.21.3…   17…   18…   19   20…   21…   A…   B…   C…   G…

 

C  I-RNTI Reference Profilesp. 252

The I-RNTI provides the new NG-RAN node a reference to the UE context in the old NG-RAN node. How the new NG-RAN node is able to resolve the old NG-RAN ID from the I-RNTI is a matter of proper configuration in the old and new NG-RAN node.
Table C-1 below provides some typical partitioning of a 40bit I-RNTI, assuming the following content:
  • UE specific reference: reference to the UE context within a logical NG-RAN node;
  • NG-RAN node address index: information to identify the NG-RAN node that has allocated the UE specific part;
  • PLMN-specific information: information supporting network sharing deployments, providing an index to the PLMN ID part of the Global NG-RAN node identifier.
Profile ID UE specific reference NG-RAN node address index (e.g., gNB ID, eNB ID) RAT-specific information PLMN-specific information Comment
120 bits (~1 million values)20 bits (~1 million values)N/AN/ANG-RAN node address index may be very well represented by the LSBs of the gNB ID.
This profile may be applicable for any NG-RAN RAT.
220 bits (~1 million values)16 bits (65.000 nodes)N/A4 bits (Max 16 PLMNs)Max number of PLMN IDs broadcast in NR is 12.
This profile may be applicable for any NG-RAN RAT.
324 bits (16 million values)16 bits (65.000 nodes)N/AN/AReduced node address to maximise addressable UE contexts.
This profile may be applicable for any NG-RAN RAT.
Up

D  SPID ranges and mapping of SPID values to cell reselection and inter-RAT/inter frequency handover prioritiesp. 253

The SPID values are defined in Annex I of TS 36.300.
From the SPID reference values, only the SPID=253 also applies for 5GC.

E  NG-RAN Architecture for Radio Access Network Sharing with multiple cell ID broadcastp. 254

Each NG-RAN node serving a cell identified by a Cell Identity associated with either a subset of PLMNs, or a subset of SNPNs, or a subset of PNI-NPNs is connected to another NG-RAN node via a single Xn-C interface instance.
Each Xn-C interface instance is setup and removed individually.
Xn-C interface instances terminating at NG-RAN nodes which share the same physical radio resources may share the same signalling transport resources. If this option is applied:
  • Non-UE associated signalling is associated to an Xn-C interface instance by including an Interface Instance Indication in the XnAP message;
  • Node related, non-UE associated Xn-C interface signalling may provide information destined for multiple logical nodes in a single XnAP procedure instance once the Xn-C interface instance is setup;
  • A UE associated signalling connection is associated to an Xn-C interface instance by allocating values for the corresponding NG-RAN node UE XnAP IDs so that they can be mapped to that Xn-C interface instance.
Up

F (Normative)  Use and structure of the I-RNTI |R17|p. 255

The I-RNTI provides an NG-RAN node with a reference to the UE context and a reference to the NG-RAN node that allocated the UE context.
To support an NG-RAN node in resolving the Local NG-RAN ID of the NG-RAN node that allocated the UE context, the I-RNTI structure is as follows:
  • the first part (starting from the MSB of the I-RNTI) identifies the I-RNTI profile. It is 2 bits long for a Full I-RNTI or 1 bit long for a short I-RNTI, and it indicates the length of a Local NG-RAN Node Identifier of the NG-RAN Node that allocated the I-RNTI;
  • the second part, immediately following the first part, is a Local NG-RAN Node Identifier;
  • the third part, immediately following the second part, identifies the UE context stored in the NG-RAN node that allocated the I-RNTI.
In case a NG-RAN node takes an additional Local NG-RAN Node identifier into use or removes a Local NG-RAN Node identifier currently in use it informs its neighbour NG-RAN nodes about this change.
The I-RNTI profiles for Full I-RNTI are described in Table F-1.
I-RNTI Profile Identity I-RNTI profile value
(binary encoding)
00b00
10b01
20b10
30b11
The I-RNTI profiles for Short I-RNTI are described in Table F-2.
I-RNTI Profile Identity I-RNTI profile value
(binary encoding)
00b0
10b1
Up

Up   Top   ToC