Search is not available for this dataset
doc_id
int64 1
6.72k
β | Section
stringlengths 5
247
β | Content
stringlengths 501
147k
β | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
β |
|---|---|---|---|---|---|---|---|
1,901 | 8.4.2.2.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | For the parameters for non-MBSFN ABS specified in Table 8.4.2-1 and Table 8.4.2.2.4-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.4-2. For the parameters for MBSFN ABS specified in Table 8.4.2-1 and Table 8.4.2.2.4-3, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.4-4. In Tables 8.4.2.2.4-1 and 8.4.2.2.4-3, Cell 1 is the serving cell, and Cell 2 and Cell 3are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 8.4.2.2.4-1: Test Parameters for PDCCH/PCFICH β Non-MBSFN ABS Table 8.4.2.2.4-2: Minimum performance PDCCH/PCFICH β Non-MBSFN ABS Table 8.4.2.2.4-3: Test Parameters for PDCCH/PCFICH β MBSFN ABS Table 8.4.2.2.4-4: Minimum performance PDCCH/PCFICH β MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.4 |
1,902 | 8.51.9 Extended Macro ng-eNodeB ID | The Target Type is Extended Macro ng-eNodeB ID for an EPS to 5GS handover to a target Extended Macro ng-eNodeB. In this case the coding of the Target ID field shall be coded as depicted in Figure 8.51.9-1. Figure 8.51.9-1: Target ID for Type Extended Macro ng-eNodeB Octets 6 to 11 shall be encoded as specified for the Extended Macro eNodeB (see Figure 8.51-4). The 5GS TAC consists of 3 octets. Bit 8 of Octet 12 is the most significant bit and bit 1 of octet 14 the least significant bit. The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.51.9 |
1,903 | 6.1.2.4 Cross-network slice coordination | The 5G system shall support a mechanism to provide time stamps with a common time base at the monitoring API, for services that cross multiple network slices and 5G networks. The 5G system shall provide suitable APIs to coordinate network slices in multiple 5G networks so that the selected communication services of a non-public network can be extended through a PLMN (e.g. the service is supported by a slice in the non-public network and a slice in the PLMN). The 5G system shall provide a mechanism to enable an MNO to operate a hosted non-public network and private slice(s) of its PLMN associated with the hosted non-public network in a combined manner. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.1.2.4 |
1,904 | 6.1.3.1.6 Handling Activate PDP context request for MS configured for dual priority | If a PDP context exists that was created due to a request including a low priority indicator set to "MS is configured for NAS signalling low priority" and the upper layers of the MS request to activate a PDP context with the same APN and the low priority indicator set to "MS is not configured for NAS signalling low priority", when initiating the PDP context activation procedure, the MS shall: - send an ACTIVATE PDP CONTEXT REQUEST message with the same combination of APN, PDP type and PDP address as the existing PDP context to activate a PDP context; NOTE 1: This option relies on the network handling of abnormal cases as specified in subclause .1.5 case c). - send an ACTIVATE PDP CONTEXT REQUEST message with the same combination of APN and PDP type as the existing PDP context but with a different PDP address, or without PDP address, to activate a PDP context; or - send an ACTIVATE PDP CONTEXT REQUEST message with the same APN after the successful deactivation of the existing PDP context. NOTE 2: The above list of options also apply for the case when the existing PDP context was created due to a request including a low priority indicator set to "MS is not configured for NAS signalling low priority" and the new request to activate a PDP context with the same APN contains a low priority indicator set to "MS is configured for NAS signalling low priority". As an alternative the upper layers of the MS can request to activate a PDP context with a different APN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1.6 |
1,905 | 16.18.3 Height-based Reporting for Aerial UE Communication | An Aerial UE can be configured with height-dependent, event-based measurement reporting (i.e., eventH1 and eventH2 as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]). An Aerial UE sends a measurement report when its altitude becomes higher or lower than configured threshold. The UE includes its height and location information in the measurement report if configured to do so by NG-RAN. RSRP/RSRQ measurement results are always reported when height reporting is configured. The Aerial UE can also be configured to trigger measurement reporting only when both a height-dependent condition and a RSRP/RSRQ/SINR-based condition are met (i.e., eventA3H1, eventA3H2, eventA4H1, eventA4H2, eventA5H1 and eventA5H2 in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12], commonly denoted as eventAxHy). For the content of eventAxHy measurement report, the same rules as described above for eventH1 and eventH2 apply. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18.3 |
1,906 | β VarAppLayerIdleConfig | The UE variable VarAppLayerIdleConfig includes the parameters of the application layer measurements stored in the UE while in RRC_IDLE. VarAppLayerIdleConfig UE variable -- ASN1START -- TAG-VARAPPLAYERIDLECONFIG-START VarAppLayerIdleConfig-r18-IEs ::= SEQUENCE { idleInactiveConfigList-r18 SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF VarAppLayerIdle-r18 } VarAppLayerIdle-r18 ::= SEQUENCE { measConfigAppLayerId-r18 MeasConfigAppLayerId-r17, serviceType-r18 ENUMERATED {streaming, mtsi, vr, spare5, spare4, spare3, spare2, spare1}, appLayerIdleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18, appLayerMeasPriority-r18 INTEGER (1..16) OPTIONAL } -- TAG-VARAPPLAYERIDLECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,907 | 5.2.5.3.2 Npcf_PolicyAuthorization_Create service operation | Service operation name: Npcf_PolicyAuthorization_Create Description: Authorize the request and optionally determines and installs SM Policy Control Data according to the information provided by the NF Consumer or provides Port Management Information Container for ports on DS-TT or NW-TT, or User plane node Management Information Container. Inputs, Required: UE (IP or MAC) address, identification of the application session context. Inputs, Optional: GPSI(s) or SUPI(s) if available, Internal Group Identifier, DNN if available, S-NSSAI if available, Media type, Media format, bandwidth requirements, sponsored data connectivity information if applicable, flow description information as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], AF Application Identifier, AF Communication Service Identifier, AF Record Identifier, Flow status, Priority indicator, emergency indicator, ASP Identifier, resource allocation outcome, AF Application Event Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, AF Transaction Id, Early and/or late notifications about UP path management events, temporal validity condition, spatial validity condition, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation, AF indication for simultaneous connectivity over source and target PSA at edge relocation, EAS Correlation indication, Common EAS IP address, Traffic Correlation ID, FQDN(s) as described in clause 5.6.7 in 23.501[ System architecture for the 5G System (5GS) ] [2], Background Data Transfer Reference ID, priority sharing indicator as described in clause 6.1.3.15 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], pre-emption control information as described in clause 6.1.3.15 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Port Management Information Container and related port number, User plane node Management Information Container, TSN AF parameters provided by the TSN AF to the PCF as described in clause 6.1.3.23 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], TSCTSF parameters provided by the TSCTSF to the PCF as described in clause 6.1.3.23a and clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], RT Latency Indication as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), TSC Assistance Container, MPS for Data Transport Service indicator as described in clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], SFC Identifier(s), Metadata, Periodicity as described clauses 6.1.3.22 and 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Protocol Description as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Indication of ECN marking for L4S as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event, Multi-Modal Service ID together with Multi-modal Service Requirements information for each data flow as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], QoS duration, QoS inactivity interval as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE 1: When only one DNAI and corresponding routing profile ID(s) and the Indication for EAS Relocation are available, the presented DNAI is the target DNAI as defined in clause 6.3.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. NOTE 2: A dedicated Notification Target Address for PMIC/UMIC UPF event and Correlation ID for PMIC/UMIC UPF event are provided by the event consumer over Npcf_PolicyAuthorization as the corresponding events are reported by the UPF and not by the PCF. Providing such information indicates that the consumer of the Npcf_PolicyAuthorization (TSN AF, TSCTSF) suppots PMIC/UMIC via Nupf event reporting. Outputs, Required: Success or Failure (reason for failure, e.g. as defined in clauses 6.1.3.16 and clause 6.1.3.10 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). Outputs, Optional: The service information that can be accepted by the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.3.2 |
1,908 | Annex D (normative): Distributed Charging Trigger Function D.1 General | This annex specifies the enhancement to 3GPP charging architecture and framework in which, when required for a specific service, the Charging Trigger Function is split between the UE that supports that service and the network element or service element. As described in clause 4.3.1.1, the CTF consists of the Accounting Metrics Collection (AMC) function block and the Accounting Data Forwarding (ADF) function block. For select services, the CTF (AMC) is located in the UE and the CTF (ADF) is located in the network element or service element reachable by an application layer protocol. The applicability of this distributed CTF architecture is described in each specific middle tier charging TS that utilizes this construct. In the present document the distributed CTF is only available for offline charging. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
1,909 | 5.8.9.11.3 Actions related to reception of the UEInformationRequestSidelink by the UE | The UE shall perform the following actions upon reception of the UEInformationRequestSidelink: 1> if the UE is acting as L2 U2U Relay UE: 2> if the UEInformationRequestSidelink includes the sl-E2E-QoS-ConnectionListPC5: 3> perform QoS split based on the sl-QoS-InfoList for each QoS flow to decide the split PDB value for each PC5 hop; 3> set the contents of UEInformationResponseSidelink message as follows: 4> set sl-SplitQoS-InfoListPC5 to include the split PDB value for each QoS flow on the fisrt PC5 hop between L2 U2U Relay UE and L2 U2U Remote UE; 4> set sl-DestinationIdentityRemoteUE to include the associated destination identity for peer L2 U2U Remote UE if configured by the upper layer; 3> submit the UEInformationResponseSidelink message to lower layers for transmission; NOTE: It is left to Relay UE implementation on how to split the PDB. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.11.3 |
1,910 | 4.16.2 AM Policy Association Modification 4.16.2.0 General | There are three cases considered for AM Policy Association Modification: - Case A: A Policy Control Request Trigger condition is met: the procedure is initiated by the AMF. - Case B: PCF policy decision per local decision or per trigger by other peers of the PCF (i.e. UDR, AF or NWDAF): the procedure is initiated by the PCF. - Case C: AM Policy Association Modification with the old PCF during AMF relocation: the procedure is initiated by the AMF. In the non-roaming case, the PCF may interact with the CHF to make policy decisions, for Access and Mobility related policies, based on spending limits. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.2 |
1,911 | β LogMeasResultListWLAN | The IE LogMeasResultListWLAN covers measured results for WLAN. LogMeasResultListWLAN information element -- ASN1START -- TAG-LOGMEASRESULTLISTWLAN-START LogMeasResultListWLAN-r16 ::= SEQUENCE (SIZE (1..maxWLAN-Id-Report-r16)) OF LogMeasResultWLAN-r16 LogMeasResultWLAN-r16 ::= SEQUENCE { wlan-Identifiers-r16 WLAN-Identifiers-r16, rssiWLAN-r16 WLAN-RSSI-Range-r16 OPTIONAL, rtt-WLAN-r16 WLAN-RTT-r16 OPTIONAL, ... } WLAN-Identifiers-r16 ::= SEQUENCE { ssid-r16 OCTET STRING (SIZE (1..32)) OPTIONAL, bssid-r16 OCTET STRING (SIZE (6)) OPTIONAL, hessid-r16 OCTET STRING (SIZE (6)) OPTIONAL, ... } WLAN-RSSI-Range-r16 ::= INTEGER(0..141) WLAN-RTT-r16 ::= SEQUENCE { rttValue-r16 INTEGER (0..16777215), rttUnits-r16 ENUMERATED { microseconds, hundredsofnanoseconds, tensofnanoseconds, nanoseconds, tenthsofnanoseconds, ...}, rttAccuracy-r16 INTEGER (0..255) OPTIONAL, ... } -- TAG-LOGMEASRESULTLISTWLAN-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,912 | Annex C (normative): Fixed Broadband Access C.1 General | This annex specifies the enhancement to 3GPP charging architecture and framework for supporting the convergent scenario, where a single operator owns both the Fixed Broadband Access network and the Evolved Packet Core (EPC), and the PCEF is located in the Fixed Broadband Access network, as described in TS 23.203[ Policy and charging control architecture ] [72]. This annex describes only the exceptions and additions in respect the main body requirements, therefore, if not explicitly mentioned the main body is applicable. This annex is applicable only for traffic from Fixed subscribers and NSWO traffic from 3GPP UEs. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
1,913 | 8.2.1.2.3A Minimum Requirement 2 Tx Antenna Ports (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements are specified in Table 8.2.1.2.3A-2, with the addition of parameters in Table 8.2.1.2.3A-1. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cells with CRS assistance information. In Table 8.2.1.2.3A-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.1.2.3A-1: Test Parameters for Transmit diversity Performance (FRC) Table 8.2.1.2.3A-2: Minimum Performance Transmit Diversity (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.2.3A |
1,914 | 4.2.8.2.1 Non-roaming Architecture | Figure 4.2.8.2.1-1: Non-roaming architecture for 5G Core Network with untrusted non-3GPP access Figure 4.2.8.2.1-2: Non-roaming architecture for 5G Core Network with trusted non-3GPP access NOTE 1: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 only shows the architecture and the network functions directly connected to non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. NOTE 2: The reference architecture in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 supports service based interfaces for AMF, SMF and other NFs not represented in the figure. NOTE 3: The two N2 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 terminate to a single AMF for a UE which is simultaneously connected to the same 5G Core Network over 3GPP access and non-3GPP access. NOTE 4 The two N3 instances in Figure 4.2.8.2.1-1 and in Figure 4.2.8.2.1-2 may terminate to different UPFs when different PDU Sessions are established over 3GPP access and non-3GPP access. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.2.1 |
1,915 | 6.3.1A.5 Abnormal cases in the UE | The following abnormal case can be identified: a) Collision of UE-requested PDU session release procedure and a service-level authentication and authorization procedure. When the UE receives a SERVICE-LEVEL AUTHENTICATION COMMAND message during the UE-requested PDU session release procedure, and the PDU session indicated in SERVICE-LEVEL AUTHENTICATION COMMAND message is the PDU session that the UE has requested to release, the UE shall ignore the SERVICE-LEVEL AUTHENTICATION COMMAND message and proceed with the UE-requested PDU session release procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1A.5 |
1,916 | T.4 Security of EAS discovery procedure via V-EASDF in roaming Scenario | Annex P of the present document should be followed, with the following additions, to protect the discovery messages between the UE and the V-EASDF which is used as the DNS server for EAS discovery in the roaming case. If the core network is used to configure the security information, the V-SMF is preconfigured with the V-EASDF security information (credentials to authenticate the V-EASDF, supported security mechanisms, port number, etc.) and provides the security information to the UE as follows: - In the case of LBO roaming, the V-SMF provides the V-EASDF security information to the UE via PCO. - In the case of HR with Session Breakout (HR-SBO) roaming scenarios, during the PDU session establishment or modification procedure, the V-SMF provides the V-EASDF security information via Nsmf_PDUSession_Create/ Nsmf_PDUSession_Update to H-SMF when the V-SMF determines to use a V-EASDF for EAS discovery, and the H-SMF provides the V-EASDF security information to UE via PCO if HR SBO is authorized. NOTE: The security information of V-EASDF provided to the UE is only related with the VPLMN parameter. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | T.4 |
1,917 | 11.8.3 Other SGi PtP tunnelling mechanisms | SGi PtP tunnelling mechanisms such as PMIPv6/GRE, L2TP, GTP-C/U, etc, may be used to deliver Non-IP data to AS via SGi. The PtP tunnel is established towards the AS by the P-GW. Depending on the type of protocol employed on the SGi PtP tunnel, the SGi PtP tunnel setup may be done at the time of attach or at the time of first MO datagram being sent by the CIoT UE. The P-GW selects the AS based on the P-GW configuration (eg. per APN, or per PtP tunnel type etc). NOTE: IP address allocation procedures for the UE are not performed by the P-GW. For uplink Non-IP data, the P-GW forwards the received data to the AS over the established SGi PtP tunnel. For downlink Non-IP data, the AS locates the right SGi PtP tunnel for the UE (using information such as UE identifiers in the Non-IP protocol itself, etc) to forward the data. The AS sends the data to P-GW over the established SGi PtP tunnel. The P-GW inturn sends the data to S-GW on the GTP-U tunnel identified by the associated SGi PtP tunnel for delivery to the UE. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.8.3 |
1,918 | 16.1.8 PUCCH cell switching for TDD cells | To reduce the delay for HARQ-ACK feedback for TDD operation with URLLC services, PUCCH cell switching for TDD cells is supported. The UE can be provided in each PUCCH group with a PUCCH switching SCell (PUCCH sSCell) that can be used for PUCCH transmission in addition to PCell / PSCell / PUCCH SCell. The applicable cell for PUCCH transmission to be either on PCell /PSCell / PUCCH SCell or the PUCCH sSCell at a time is either defined by: - a higher layer configured semi-static time-domain pattern of the applicable cell for PUCCH transmission; or - dynamic indication of the cell for PUCCH transmission through a PDCCH scheduling a PUCCH transmission. The PUCCH cell switching is applicable to all UCI types when using the higher layer configured time-domain pattern, but is only applicable to HARQ feedback for the dynamic indication of the cell for PUCCH transmission through a PDCCH scheduling PUCCH. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.8 |
1,919 | 4.7.5.2.1 Combined routing area updating procedure initiation | The combined routing area updating procedure is initiated only by a GPRS MS operating in MS operation modes A or B, if the MS is in state GMM-REGISTERED and MM-IDLE, and if the network operates in network operation mode I: - when a GPRS MS that is IMSI attached for GPRS and non-GPRS services detects a change of the routing area in state GMM-REGISTERED and MM-IDLE, unless the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and is entering a routing area in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs; - when a GPRS MS that is IMSI attached for GPRS services wants to perform an IMSI attach for non-GPRS services; - after termination of a non-GPRS service via non-GPRS channels to update the association if the MS has changed the RA during that non-GPRS service transaction; - after termination of a non-GPRS service via non-GPRS channels to update the association if GPRS services were suspended during the non-GPRS service but no resume is received. See 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] subclause 16.2.1; - after termination of a non-GPRS service via non-GPRS channels to update the association, if the GPRS MS in MS operation mode A performed a normal GPRS attach or a normal routing area updating procedure during the circuit-switched transaction; - after a CM SERVICE REJECT message with cause value #4 is received by the mobile station (see subclause 4.5.1.1); in this case the update type IE shall be set to "Combined RA/LA updating with IMSI attach"; - when a GPRS MS needs to update the network with the new MS Radio Access Capability IE; - when a GPRS MS needs to update the network with a new DRX parameter IE; - in Iu mode, to re-synchronize the PMM mode of MS and network after RRC connection release with cause "Directed signalling connection re-establishment", see subclause 4.7.2.5; - in Iu mode, to re-synchronize the PMM mode of MS and network after inter-system change not due to PS handover from PMM-CONNECTED mode in Iu mode to A/Gb mode or S1 mode, if the MS performed an inter - system change back to Iu mode without sending a ROUTING AREA UPDATE REQUEST message while in A/Gb mode or a TRACKING AREA UPDATE REQUEST message while in S1 mode; - in Iu mode and A/Gb mode, after intersystem change from S1 mode, and the GMM receives an indication of "RRC connection failure" from lower layers due to lower layer failure while in S1 mode. In this case, if the TIN indicates "RAT-related TMSI", the MS shall set the TIN to "GUTI" before initiating the routing area updating procedure; - in A/Gb mode, after intersystem change from S1 mode if the TIN indicates "RAT-related TMSI", but the MS is required to perform routing area updating for IMS voice termination as specified in annex P.4; - when the MS enters GMM-REGISTERED.NORMAL-SERVICE and the TIN indicates "GUTI"; - when the MS supports SRVCC and changes the mobile station classmark 2, mobile station classmark 3 or the supported codecs; - when the MS which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell and timer T3423 has expired, or is in the GERAN or UTRAN cell when timer T3423 expires; - when due to a manual CSG selection the GPRS MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the MS's Allowed CSG list or in the MS's Operator CSG list; - when the MS changes the MS network capability information; - when the UE's usage setting or the voice domain preference for E-UTRAN change in the MS; - when the MS activates mobility management for IMS voice termination as specified in annex P.2 and the TIN indicates "RAT-related TMSI"; - upon reception of a paging indication using P-TMSI, if the timer T3346 is running and the MS is in state GMM-REGISTERED.ATTEMPTING-TO-UPDATE and the RAI of the current cell is same as the stored RAI; - when the MS which is configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell, after intersystem change from S1 mode to Iu or A/Gb mode not due to CS fallback, and the location area of the current cell is different from the location area stored in the MS; - in A/Gb mode, after intersystem change from S1 mode via cell change order procedure not due to CS fallback, if the TIN indicates "RAT-related TMSI"; in this case the MS shall set the TIN to "GUTI" before initiating the combined routing area updating procedure; - in A/Gb mode, after Inter RAT handover from S1 mode or Iu mode; - when the MS needs to request the use of PSM or needs to stop the use of PSM; - when the MS needs to request the use of eDRX or needs to stop the use of eDRX; - when a change in the eDRX usage conditions at the MS requires different extended DRX parameters; - when a change in the PSM usage conditions at the MS requires a different timer T3312 value or different timer T3324 value; or NOTE 1: A change in the PSM or eDRX usage conditions at the MS can include e.g. a change in the MS configuration, a change in requirements from upper layers or the battery running low at the MS. - when the Default_DCN_ID value changes, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]. NOTE 2: The routing area updating procedure is initiated after deleting the DCN-ID list as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. In A/Gb mode, the routing and location area identification are broadcast on the broadcast channel(s). A combined routing area updating procedure shall abort any ongoing GMM procedure. Aborted GMM procedures shall be repeated after the combined routing area updating procedure has been successfully performed. The ROUTING AREA UPDATE REQUEST message shall always be the first message sent from the MS in the new routing area after routing area change. In Iu mode, the routing and location area identification are broadcast on the broadcast channel(s) or sent to the MS via the PS signalling connection. A combined routing area updating procedure shall abort any ongoing GMM procedure. Aborted GMM procedures may be repeated after the combined routing area updating procedure has been successfully performed. The ROUTING AREA UPDATE REQUEST message shall always be the first GMM message sent from the MS in the new routing area after routing area change. To initiate a combined routing area updating procedure the MS sends the message ROUTING AREA UPDATE REQUEST to the network, starts timer T3330 and changes to state GMM-ROUTING-UPDATING-INITIATED and MM LOCATION UPDATING PENDING. The value of the Update type IE in the message shall indicate "combined RA/LA updating" unless explicitly specified otherwise. If for the last attempt to update the registration of the location area a MM specific procedure was performed, the value of the Update type IE in the ROUTING AREA UPDATE REQUEST message shall indicate "combined RA/LA updating with IMSI attach". Furthermore the MS shall include the TMSI status IE if no valid TMSI is available. If the MS has stored a valid LAI and the MS supports EMM combined procedures, the MS shall include it in the Old location area identification IE in the ROUTING AREA UPDATE REQUEST message. If timer T3302 is currently running, the MS shall stop timer T3302. If timer T3311 is currently running, the MS shall stop timer T3311. If the MS has stored a valid TMSI, the MS shall include the TMSI based NRI container IE in the ROUTING AREA UPDATE REQUEST message. A GPRS MS in MS operation modes B that is in an ongoing circuit-switched transaction, shall initiate the combined routing area updating procedure after the circuit-switched transaction has been released, if the MS has changed the RA during the circuit-switched transaction and if the network operates in network operation mode I. A GPRS MS in MS operation mode A shall initiate the combined routing area updating procedure with IMSI attach after the circuit-switched transaction has been released, if a normal GPRS attach or a normal routing area updating procedure was performed during the circuit-switched transaction and provided that the network operates in network operation mode I. A GPRS MS in MS operation mode A shall perform the normal routing area update procedure during an ongoing circuit-switched transaction. If the MS initiates the combined routing area updating procedure for GPRS services and "SMS-only service", the MS shall indicate "SMS only" in the Additional update type IE. In Iu mode, if the MS wishes to prolong the established PS signalling connection after the normal routing area updating procedure (for example, the MS has any CM application request pending), it may set a follow-on request pending indicator on (see subclause 4.7.13). In Iu mode, when a ROUTING AREA UPDATE REQUEST is received by the SGSN over a new PS signalling connection while there is an ongoing PS signalling connection (network is already in mode PMM-CONNECTED) for this MS, the network shall progress the routing area update procedure as normal and release the previous PS signalling connection when the routing area update procedure has been accepted by the network. NOTE 3: The re-establishment of the radio bearers of active PDP contexts is done as described in subclause "Service Request procedure". If the combined routing area updating procedure is initiated due to the reception of the paging indication while T3346 is running, the "follow-on request pending" indication shall be set to 1. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5.2.1 |
1,920 | β FeatureSetUplink | The IE FeatureSetUplink is used to indicate the features that the UE supports on the carriers corresponding to one band entry in a band combination. FeatureSetUplink information element -- ASN1START -- TAG-FEATURESETUPLINK-START FeatureSetUplink ::= SEQUENCE { featureSetListPerUplinkCC SEQUENCE (SIZE (1.. maxNrofServingCells)) OF FeatureSetUplinkPerCC-Id, scalingFactor ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, dummy3 ENUMERATED {supported} OPTIONAL, intraBandFreqSeparationUL FreqSeparationClass OPTIONAL, searchSpaceSharingCA-UL ENUMERATED {supported} OPTIONAL, dummy1 DummyI OPTIONAL, supportedSRS-Resources SRS-Resources OPTIONAL, twoPUCCH-Group ENUMERATED {supported} OPTIONAL, dynamicSwitchSUL ENUMERATED {supported} OPTIONAL, simultaneousTxSUL-NonSUL ENUMERATED {supported} OPTIONAL, pusch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { scs-15kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-30kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-60kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-120kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL } OPTIONAL, dummy2 DummyF OPTIONAL } FeatureSetUplink-v1540 ::= SEQUENCE { zeroSlotOffsetAperiodicSRS ENUMERATED {supported} OPTIONAL, pa-PhaseDiscontinuityImpacts ENUMERATED {supported} OPTIONAL, pusch-SeparationWithGap ENUMERATED {supported} OPTIONAL, pusch-ProcessingType2 SEQUENCE { scs-15kHz ProcessingParameters OPTIONAL, scs-30kHz ProcessingParameters OPTIONAL, scs-60kHz ProcessingParameters OPTIONAL } OPTIONAL, ul-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1610 ::= SEQUENCE { -- R1 11-5: PUsCH repetition Type B pusch-RepetitionTypeB-r16 SEQUENCE { maxNumberPUSCH-Tx-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, hoppingScheme-r16 ENUMERATED {interSlotHopping, interRepetitionHopping, both} } OPTIONAL, -- R1 11-7: UL cancelation scheme for self-carrier ul-CancellationSelfCarrier-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-7a: UL cancelation scheme for cross-carrier ul-CancellationCrossCarrier-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-5c: The maximum number of SRS resources in one SRS resource set with usage set to 'codebook' for Mode 2 ul-FullPwrMode2-MaxSRS-ResInSet-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- R1 22-4a/4b/4c/4d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 1 cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL } OPTIONAL, -- R1 22-3a/3b/3c/3d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 2 cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL } OPTIONAL, supportedSRS-PosResources-r16 SRS-AllPosResources-r16 OPTIONAL, intraFreqDAPS-UL-r16 SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, intraFreqTwoTAGs-DAPS-r16 ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, dummy3 ENUMERATED {short, long} OPTIONAL } OPTIONAL, intraBandFreqSeparationUL-v1620 FreqSeparationClassUL-v1620 OPTIONAL, -- R1 11-3: More than one PUCCH for HARQ-ACK transmission within a slot multiPUCCH-r16 SEQUENCE { sub-SlotConfig-NCP-r16 ENUMERATED {set1, set2} OPTIONAL, sub-SlotConfig-ECP-r16 ENUMERATED {set1, set2} OPTIONAL } OPTIONAL, -- R1 11-3c: 2 PUCCH of format 0 or 2 for a single 7*2-symbol subslot based HARQ-ACK codebook twoPUCCH-Type1-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3d: 2 PUCCH of format 0 or 2 for a single 2*7-symbol subslot based HARQ-ACK codebook twoPUCCH-Type2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3e: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for a single 2*7-symbol HARQ-ACK codebooks twoPUCCH-Type3-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3f: 2 PUCCH transmissions in the same subslot for a single 2*7-symbol HARQ-ACK codebooks which are not covered by 11-3d and -- 11-3e twoPUCCH-Type4-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3g: SR/HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when SR/HARQ-ACK -- are supposed to be sent with different starting symbols in a subslot mux-SR-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, -- R1 11-4c: 2 PUCCH of format 0 or 2 for two HARQ-ACK codebooks with one 7*2-symbol sub-slot based HARQ-ACK codebook twoPUCCH-Type5-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4d: 2 PUCCH of format 0 or 2 in consecutive symbols for two HARQ-ACK codebooks with one 2*7-symbol sub-slot based HARQ-ACK -- codebook twoPUCCH-Type6-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4e: 2 PUCCH of format 0 or 2 for two subslot based HARQ-ACK codebooks twoPUCCH-Type7-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4f: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for HARQ-ACK codebooks with one 2*7-symbol -- subslot based HARQ-ACK codebook twoPUCCH-Type8-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4g: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for two subslot based HARQ-ACK codebooks twoPUCCH-Type9-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4h: 2 PUCCH transmissions in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot which are not covered -- by 11-4c and 11-4e twoPUCCH-Type10-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4i: 2 PUCCH transmissions in the same subslot for two subslot based HARQ-ACK codebooks which are not covered by 11-4d and -- 11-4f twoPUCCH-Type11-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-1: UL intra-UE multiplexing/prioritization of overlapping channel/signals with two priority levels in physical layer ul-IntraUE-Mux-r16 SEQUENCE { pusch-PreparationLowPriority-r16 ENUMERATED {sym0, sym1, sym2}, pusch-PreparationHighPriority-r16 ENUMERATED {sym0, sym1, sym2} } OPTIONAL, -- R1 16-5a: Supported UL full power transmission mode of fullpower ul-FullPwrMode-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-5d: Processing up to X unicast DCI scheduling for UL per scheduled CC crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL } OPTIONAL, -- R1 16-5b: Supported UL full power transmission mode of fullpowerMode1 ul-FullPwrMode1-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-5c-2: Ports configuration for Mode 2 ul-FullPwrMode2-SRSConfig-diffNumSRSPorts-r16 ENUMERATED {p1-2, p1-4, p1-2-4} OPTIONAL, -- R1 16-5c-3: TPMI group for Mode 2 ul-FullPwrMode2-TPMIGroup-r16 SEQUENCE { twoPorts-r16 BIT STRING(SIZE(2)) OPTIONAL, fourPortsNonCoherent-r16 ENUMERATED{g0, g1, g2, g3} OPTIONAL, fourPortsPartialCoherent-r16 ENUMERATED{g0, g1, g2, g3, g4, g5, g6} OPTIONAL } OPTIONAL } FeatureSetUplink-v1630 ::= SEQUENCE { -- R1 22-8: For SRS for CB PUSCH and antenna switching on FR1 with symbol level offset for aperiodic SRS transmission offsetSRS-CB-PUSCH-Ant-Switch-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8a: PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot and constrained timeline for SRS for CB -- PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorSingleOcc-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8b: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) -- of a slot for Case 2 and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithoutGap-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8c: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) -- of a slot for Case 2 with a DCI gap and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithGap-fr1-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, -- R1 22-9: Cancellation of PUCCH, PUSCH or PRACH with a DCI scheduling a PDSCH or CSI-RS or a DCI format 2_0 for SFI partialCancellationPUCCH-PUSCH-PRACH-TX-r16 ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1640 ::= SEQUENCE { -- R1 11-4: Two HARQ-ACK codebooks with up to one sub-slot based HARQ-ACK codebook (i.e. slot-based + slot-based, or slot-based + -- sub-slot based) simultaneously constructed for supporting HARQ-ACK codebooks with different priorities at a UE twoHARQ-ACK-Codebook-type1-r16 SubSlot-Config-r16 OPTIONAL, -- R1 11-4a: Two sub-slot based HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different -- priorities at a UE twoHARQ-ACK-Codebook-type2-r16 SubSlot-Config-r16 OPTIONAL, -- R1 22-8d: All PDCCH monitoring occasion can be any OFDM symbol(s) of a slot for Case 2 with a span gap and constrained timeline -- for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithSpanGap-fr1-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, scs-30kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, scs-60kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL } OPTIONAL } FeatureSetUplink-v16d0 ::= SEQUENCE { pusch-RepetitionTypeB-v16d0 SEQUENCE { maxNumberPUSCH-Tx-Cap1-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, maxNumberPUSCH-Tx-Cap2-r16 ENUMERATED {n2, n3, n4, n7, n8, n12} } OPTIONAL } FeatureSetUplink-v1710 ::= SEQUENCE { -- R1 23-3-1 Multi-TRP PUSCH repetition (type A) -codebook based mTRP-PUSCH-TypeA-CB-r17 ENUMERATED {n1,n2,n4} OPTIONAL, -- R1 23-3-1-2 Multi-TRP PUSCH repetition (type A) - non-codebook based mTRP-PUSCH-RepetitionTypeA-r17 ENUMERATED {n1,n2,n3,n4} OPTIONAL, -- R1 23-3-3 Multi-TRP PUCCH repetition-intra-slot mTRP-PUCCH-IntraSlot-r17 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, -- R1 23-8-4 Maximum 2 SP and 1 periodic SRS sets for antenna switching srs-AntennaSwitching2SP-1Periodic-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-9 Extension of aperiodic SRS configuration for 1T4R, 1T2R and 2T4R srs-ExtensionAperiodicSRS-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-10 1 aperiodic SRS resource set for 1T4R srs-OneAP-SRS-r17 ENUMERATED {supported} OPTIONAL, -- R4 16-8 UE power class per band per band combination ue-PowerClassPerBandPerBC-r17 ENUMERATED {pc1dot5, pc2, pc3} OPTIONAL, -- R4 17-8 UL transmission in FR2 bands within an UL gap when the UL gap is activated tx-Support-UL-GapFR2-r17 ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1720 ::= SEQUENCE { -- R1 25-3: Repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots with configured K = 2, 4, 8 pucch-Repetition-F0-1-2-3-4-RRC-Config-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-3a: Repetitions for PUCCH format 0, 1, 2, 3 and 4 over multiple PUCCH subslots using dynamic repetition indication pucch-Repetition-F0-1-2-3-4-DynamicIndication-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-3b: Inter-subslot frequency hopping for PUCCH repetitions interSubslotFreqHopping-PUCCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-8: Semi-static HARQ-ACK codebook for sub-slot PUCCH semiStaticHARQ-ACK-CodebookSub-SlotPUCCH-r17 ENUMERATED {supported} OPTIONAL, -- R1 25-14: PHY prioritization of overlapping low-priority DG-PUSCH and high-priority CG-PUSCH phy-PrioritizationLowPriorityDG-HighPriorityCG-r17 INTEGER(1..16) OPTIONAL, -- R1 25-15: PHY prioritization of overlapping high-priority DG-PUSCH and low-priority CG-PUSCH phy-PrioritizationHighPriorityDG-LowPriorityCG-r17 SEQUENCE { pusch-PreparationLowPriority-r17 ENUMERATED{sym0, sym1, sym2}, additionalCancellationTime-r17 SEQUENCE { scs-15kHz-r17 ENUMERATED{sym0, sym1, sym2} OPTIONAL, scs-30kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4} OPTIONAL, scs-60kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7, sym8} OPTIONAL, scs-120kHz-r17 ENUMERATED{sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14, sym15, sym16} OPTIONAL }, maxNumberCarriers-r17 INTEGER(1..16) } OPTIONAL, -- R4 17-5 Support of UL DC location(s) report extendedDC-LocationReport-r17 ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1800 ::= SEQUENCE { -- R1 40-3-3-2: Number of delay values tdcpNumberDelayValue-r18 INTEGER (2..4) OPTIONAL, -- R1 40-3-3-4: Phase report phaseReportMoreThanOne-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-6d: 2 symbols front-loaded DMRS (uplink) for Rel.18 enhanced DMRS ports for PUSCH pusch-2SymbolFL-DMRS-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-6e: 2-symbol FL DMRS + one additional 2-symbols DMRS for Rel.18 enhanced DMRS ports for PUSCH pusch-2SymbolFL-DMRS-Addition2Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-6f: 1 symbol FL DMRS and 3 additional DMRS symbols for Rel.18 enhanced DMRS ports for PUSCH pusch-1SymbolFL-DMRS-Addition3Symbol-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-12: Support Rel-18 UL DMRS with single-DCI based M-TRP ul-DMRS-SingleDCI-M-TRP-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-13: Support Rel-18 UL DMRS with M-DCI based M-TRP ul-DMRS-M-DCI-M-TRP-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-5: Maximum 2 SP and 1 periodic SRS sets for 8T8R antenna switching max2SP1SRS8T8R-AntennaSwitch-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-4: Single-DCI based STx2P SFN scheme for PUCCH pucch-SingleDCI-STx2P-SFN-r18 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, -- R4 27-1 TxDiversity for 4Tx txDiversity4Tx-r18 ENUMERATED {supported} OPTIONAL, -- R4 44-1 TxDiversity for 2Tx txDiversity2Tx-r18 ENUMERATED {supported} OPTIONAL } SubSlot-Config-r16 ::= SEQUENCE { sub-SlotConfig-NCP-r16 ENUMERATED {n4,n5,n6,n7} OPTIONAL, sub-SlotConfig-ECP-r16 ENUMERATED {n4,n5,n6} OPTIONAL } SRS-AllPosResources-r16 ::= SEQUENCE { srs-PosResources-r16 SRS-PosResources-r16, srs-PosResourceAP-r16 SRS-PosResourceAP-r16 OPTIONAL, srs-PosResourceSP-r16 SRS-PosResourceSP-r16 OPTIONAL } SRS-PosResources-r16 ::= SEQUENCE { maxNumberSRS-PosResourceSetPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12, n16}, maxNumberSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberSRS-ResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, maxNumberPeriodicSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-PosResourceAP-r16 ::= SEQUENCE { maxNumberAP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberAP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-PosResourceSP-r16 ::= SEQUENCE { maxNumberSP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberSP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-Resources ::= SEQUENCE { maxNumberAperiodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberAperiodicSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberPeriodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberPeriodicSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberSemiPersistentSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberSemiPersistentSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberSRS-Ports-PerResource ENUMERATED {n1, n2, n4} } DummyF ::= SEQUENCE { maxNumberPeriodicCSI-ReportPerBWP INTEGER (1..4), maxNumberAperiodicCSI-ReportPerBWP INTEGER (1..4), maxNumberSemiPersistentCSI-ReportPerBWP INTEGER (0..4), simultaneousCSI-ReportsAllCC INTEGER (5..32) } -- TAG-FEATURESETUPLINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,921 | 5.3.5.15.2 L2 U2N or U2U Remote UE Release | The L2 U2N Relay UE shall: 1> if the release is triggered by reception of the sl-RemoteUE-ToReleaseList: 2> for each SL-DestinationIdentity value included in the sl-RemoteUE-ToReleaseList: 3> if the current UE has a PC5 RRC connection to a L2 U2N Remote UE with SL-DestinationIdentity: 4> indicate upper layers to trigger PC5 unicast link release. The L2 U2U Relay UE shall: 1> if the release is triggered by reception of the sl-U2U-RemoteUE-ToReleaseList: 2> for each SL-DestinationIdentity value included in the sl-U2U-RemoteUE-ToReleaseList: 3> release the configuration associated with the L2 U2U Remote UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.15.2 |
1,922 | 4.3.4 PDU Session Release 4.3.4.1 General | The PDU Session Release procedure is used to release all the resources associated with a PDU Session, including: - The IP address/Prefixes allocated for an IP-based PDU Session; this may include the release of multiple Prefixes in the case of Multi-homing (as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - Any UPF resource (including N3/N9/N19 termination) that was used by the PDU Session. For N19 termination, the UPF resource may be released if all the PDU Sessions associated with the 5G VN group are released. - Any access resource that was used by the PDU Session. The SMF takes care to notify any entity associated with PDU Session: PCF, DN (e.g. when DN authorization has taken place at PDU Session establishment), etc. of a PDU Session Release. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.4 |
1,923 | 5.3.16 Restriction on use of enhanced coverage | In order to deal with use of extensive resources from the network, the operator may prevent specific subscribers from using enhanced coverage (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). When in NB-S1 mode, the UE shall indicate support for restriction on use of enhanced coverage. When in WB-S1 mode, the UE supporting either CE mode A or CE mode B shall indicate support for restriction on use of enhanced coverage. The UE supporting restriction on use of enhanced coverage indicates its support for restriction on use of enhanced coverage in the ATTACH REQUEST and TRACKING AREA UPDATE REQUEST message. If the UE supports restriction on use of enhanced coverage, the MME indicates whether the use of enhanced coverage is restricted or not in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message (see clause 5.5.1.2 and clause 5.5.3.2). If the use of enhanced coverage is restricted, the UE shall not use enhanced coverage in the registered PLMN and in any PLMN which is in the list of equivalent PLMNs. If the UE supports CE mode B and the network determines that - the use of enhanced coverage is not restricted for the UE; or - CE mode B is not restricted for the UE; the applicable NAS timer values shall be calculated by the network as described in clause 4.8. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.16 |
1,924 | 5.7.14.3 Actions related to transmission of UEPositioningAssistanceInfo message | The UE shall set the contents of the UEPositioningAssistanceInfo message as follows: 1> if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with periodicReporting: 2> for all the association changes store ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp; 2> include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message on expiry of each configured period; 2> optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message; 1> else if ue-TxTEG-RequestUL-TDOA-Config in RRCReconfiguration message is configured with oneShot: 2> identify the ue-TxTEG-Association corresponding to each ue-TxTEG-ID with nr-TimeStamp; 2> include the results in ue-TxTEG-AssociationList in the UEPositioningAssistanceInfo message only one time; 2> optionally include one ue-TxTEG-TimingErrorMarginValue for each UEPositioningAssistanceInfo message. The UE shall submit the UEPositioningAssistanceInfo message to lower layers for transmission. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.14.3 |
1,925 | 9.3.1.1.3 FDD (CSI measurements in case two CSI subframe sets are configured and with CRS assistance information) | For the parameters specified in Table 9.3.1.1.3-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.1.3-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least ο‘ % of the time but less than ο’ο % for each sub-band; b) the ratio of the throughput in ABS subframes obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be β₯ ο§; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER in ABS subframes for the indicated transport formats shall be greater than or equal to Ξ΅. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Table 9.3.1.1.3-1 Sub-band test for single antenna transmission (FDD) Table 9.3.1.1.3-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.1.1.3 |
1,926 | 5.5.1.2.6A Initial registration for initiating an emergency PDU session not accepted by the network | If the network cannot accept an initial registration request with 5GS registration type IE set to "initial registration" and for sending a PDU SESSION ESTABLISHMENT REQUEST message with request type set to "initial emergency request", the UE shall perform the procedures as described in subclause 5.5.1.2.5. Then if the UE is in the same selected PLMN or SNPN where the last initial registration request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. b) attempt initial registration for emergency services. If the network cannot accept an initial registration request with 5GS registration type IE set to "initial registration", for establishing an emergency PDU session and the PDU session needs to be established due to handover of an existing PDN connection for emergency bearer services, the UE shall perform the procedures as described in subclause 5.5.1.2.5. Then if the UE is in the same selected PLMN or equivalent PLMN or the same selected SNPN or equivalent SNPN, where the last initial registration request was attempted, the UE shall attempt initial registration for emergency services. If the initial registration request, with 5GS registration type IE set to "initial registration" and for initiating an emergency PDU session, fails due to abnormal case b) in subclause 5.5.1.2.7, the UE shall perform the actions as described in subclause 5.5.1.2.7 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. If the initial registration request, with 5GS registration type IE set to "initial registration" and for initiating an emergency PDU session, fails due to abnormal cases c), d) or e) in subclause 5.5.1.2.7, the UE shall perform the actions as described in subclause 5.5.1.2.7. Then if the UE is in: a) the same selected PLMN or SNPN where the last initial registration request was attempted and the PDU session does not need to be established due to handover of an existing PDN connection for emergency bearer services, the UE shall: - inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers requesting implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] can result in the emergency call being attempted to another IP-CAN. - attempt initial registration for emergency services; or b) the same selected PLMN or equivalent PLMN or the same selected SNPN or equivalent SNPN, where the last initial registration request was attempted and the PDU session needs to be established due to handover of an existing PDN connection for emergency bearer services, attempt initial registration for emergency services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.6A |
1,927 | 13.3.8.2 Client credentials assertion | CCAs shall be JSON Web Tokens as described in RFC 7519 [44] and are secured with digital signatures based on JSON Web Signature (JWS) as described in RFC 7515 [45]. The CCA shall include: - the NF instance ID of the NF Service Consumer (subject); - A timestamp (iat) and an expiration time (exp), and - The NF type of the expected audience (audience), i.e. the type "NRF" and/or the NF type of the NF Service Producer. The NF Service Consumer shall digitally sign the generated CCA based on its private key as described in RFC 7515 [45]. The signed CCA shall include one of the following fields: - the X.509 URL (x5u) to refer to a resource for the X.509 public key certificate or certificate chain used for signing the client authentication assertion, or - the X.509 Certificate Chain (x5c) include the X.509 public key certificate or certificate chain used for signing the client authentication assertion. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.8.2 |
1,928 | 5.9.3.4 Broadcast MRB release | Upon broadcast MRB release for MBS broadcast service, the UE shall: 1> release the PDCP entity, RLC entity as well as the related MAC and physical layer configuration; 1> if the SDAP entity associated with the corresponding mbs-SessionId has no associated MRB: 2> release the SDAP entity, as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.2; 2> indicate the release of the user plane resources for the mbs-SessionId to upper layers. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.3.4 |
1,929 | 7.10 UE assistance information | In MR-DC, the UE can be configured to report MCG specific UE assistance information if the MN is a gNB and/or SCG specific UE assistance information if the SN is a gNB, if it prefers an adjustment on the connected mode DRX parameters, the maximum aggregated bandwidth, the maximum number of secondary component carriers, the maximum number of MIMO layers, whether the UE prefers the SCG to be deactivated, the minimum scheduling offset for cross-slot scheduling cycle length, whether the UE is applying RLM/BFD measurements relaxation for power saving, and/or whether the UE is experiencing IDC problems as described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. In these cases, it is up to the network whether to accommodate the preference or how to use the relaxation status indications or how to solve the IDC problems. SCG specific UE assistance information for power saving or IDC can be configured by the network via SRB1 or SRB3. SCG specific UE assistance information for power saving or IDC is directly transmitted to the SN via SRB3, if SRB3 is configured and the SCG is activated, otherwise UE transmits SCG specific UE assistance information for power saving or IDC in a transparent container to the MN. When network simultaneously configures the UE to perform radio link monitoring on the SCG and beam failure detection on the SCG while the SCG is deactivated, UE assistance information for the relaxation state report of RLM/BFD measurements for SCG is reported over MCG. UE can implicitly indicate a preference for NR SCG release by indicating zero number of carriers and zero aggregated maximum bandwidth in both FR1 and FR2. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 7.10 |
1,930 | 4.7.1.7 Intersystem change between A/Gb mode and Iu mode | For the Iu mode to A/Gb mode and A/Gb mode to Iu mode intersystem change the following cases can be distinguished: a) Intersystem change between cells belonging to different RA's: The procedures executed by the MS depends on the network mode of operation in the old and new RA. If a change of the network operation mode has occurred in the new RA, then the MS shall behave as specified in subclause 4.7.1.6. If no change of the network operation mode has occurred in the new RA, then the MS shall initiate the normal or combined routing area updating procedure depending on the network operation mode in the current RA. b) Intersystem change between cells belonging to the same RA: 1) If the READY timer is running in the MS in A/Gb mode before or after the inter-system change occurs,or the MS is in PMM-CONNECTED mode in Iu mode, before the inter-system change occurs then the MS shall perform a normal or combined routing area updating procedure depending on the network mode of operation in the current RA. 2) If the READY timer is not running in the MS in A/Gb mode before the inter-system change occurs, or the MS is in PMM-IDLE mode in Iu mode before the inter-system change and the READY timer is not running in the MS in A/Gb mode after the intersystem change, then, unless a routing area updating procedure is required according to case c) or case b) 3) below or according to subclause 4.7.5.1 and 4.7.5.2.1, the MS shall not perform a routing area updating procedure until uplink user data or signalling information needs to be sent from the MS to the network. - If the MS is in the same access network(i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling messages, the procedures defined for that access system shall be followed. This shall be sending of an LLC PDU in an A/Gb mode cell or initiating the service request procedure in an Iu mode cell. - If the MS is in a different access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling messages, the normal or combined routing area updating procedure shall be performed depending on the network operation mode in the current RA, before the sending of user data or signalling messages. If the signalling message is a DETACH REQUEST indicating "power off", the routing area updating procedure need not to be performed. - If the periodic routing area update timer expires the MS shall initiate the periodic routing area updating procedure. 3) If the READY timer is not running in the MS in A/Gb mode or the MS is in PMM-IDLE mode in Iu mode, then the MS shall perform a normal or combined routing area updating procedure depending on the network mode of operation in the current RA if the MS is required to perform routing area updating for IMS voice termination as specified in annex P.3. 4) If the READY timer is not running in the network in A/Gb mode or the network is in PMM-IDLE mode in Iu mode, then the network shall page the MS if downlink user data or signalling information needs to be sent from the network to the MS. This shall include both A/Gb mode and Iu mode cells. - If the MS receives the paging indication in the same access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling information, the MS shall send any LLC PDU in a A/Gb mode cell or shall initiate the service request procedure indicating service type "paging response" in an Iu mode cell. - If the MS receives the paging indication in a different access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling information, the MS shall perform a normal or combined routing area updating procedure depending on the network operation mode in the current RA. c) Intersystem handover from A/Gb mode to Iu mode during a CS connection: After the successful completion of the handover from an A/Gb mode cell to an Iu mode cell, an MS which has performed the GPRS suspension procedure in Gb mode (see 3GPP TS 44.018[ None ] [84]) (i.e. an MS in MS operation mode B or an DTM MS in a A/Gb mode cell that does not support DTM) shall perform a normal routing area updating procedure in the Iu mode cell in order to resume the GPRS services in the network, before sending any other signalling messages or user data. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.7 |
1,931 | 5.3.13 Interaction between power saving mode and extended idle mode DRX cycle | The UE can request the use of both PSM and eDRX during an attach or tracking area updating procedure but it is up to the network to decide to enable none, one of them or both (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [11A] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). If the network accepts the use of both PSM (see clause 5.3.11) and eDRX (see clause 5.3.12), the extended DRX parameters IE provided to the UE should allow for multiple paging occasions before the active timer expires. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.13 |
1,932 | 8.83 Node Features | Node Features IE is coded as depicted in Figure 8. 83-1. Figure 8.83-1: Node Features IE The Node Features IE takes the form of a bitmask where each bit set indicates that the corresponding feature is supported. Spare bits shall be ignored by the receiver. The same bitmask is defined for all GTPv2 interfaces. The following table specifies the features defined on GTPv2 interfaces and the interfaces on which they apply. Table 8.83-1: Node Features on GTPv2 interfaces No features have been defined on the following GTPv2 interfaces in this version of the specification: S2a, S2b, S5, S8, S10, S3, S16, Sv, S101, S121, Sm, Sn. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.83 |
1,933 | 8.77 RFSP Index | Index to RAT/Frequency Selection Priority (RFSP Index) is coded as depicted in Figure 8.77-1, and contains a non-transparent copy of the corresponding IE (see clause 8.2.2), "Subscriber Profile ID for RAT/Frequency Priority (SPID)" as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. The SPID is an integer between 1 and 256 and is encoded as an unsigned integer, which requires the two octets specified for the RFSP Index parameter. Figure 8.77-1. RFSP Index | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.77 |
1,934 | 4.22.2.4 MA PDU Session establishment with non-3GPP access connected to EPC and 3GPP access connected to 5GC 4.22.2.4.1 General | This clause applies to the case where, for a PDU Session, multi-access connectivity via both EPC (over non-3GPP access) and 5GC (over 3GPP access) is supported and allowed in the UE and network. In this case, multi-access connectivity using ATSSS via both non-3GPP access to EPC and 3GPP access to 5GC may be provided as described in this clause. For this scenario, the general principles for ATSSS as described in clause 5.32 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] apply, with the additions provided in this clause 4.22.2.3. A Multi-Access PDU Session may be extended with user-plane resources via an associated PDN Connection on non-3GPP access in EPC. This enables a scenario where a MA PDU Session can simultaneously be associated with user-plane resources on non-3GPP access network connected to EPC and 3GPP access connected to 5GC. Such a PDN Connection in EPS would thus be associated with multi-access capability in the UE and PGW-C+SMF. NOTE: To the MME and SGW this is a regular PDN Connection and the support for ATSSS is transparent to MME and SGW. The UE may operate in either single-registration mode or dual-registration mode in 3GPP access. Irrespective of whether the UE operates in single-registration mode or dual-registration mode in 3GPP access, it is assumed that the UE supports simultaneous registrations for 3GPP access in 5GC and non-3GPP access in EPC. The ATSSS rules are provided from the PGW-C+SMF to the UE via SM NAS signalling over 5GC, as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. ATSSS rules may be provided via the EPC. After the establishment of a MA PDU Session and setting up user-plane resources in non-3GPP access in EPC and 3GPP access in 5GC, the UE distributes the uplink traffic across the two access networks as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Similarly, the PDU Session Anchor UPF performs distribution of downlink traffic across the two access networks as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The PMF protocol may be used via any user plane connection, i.e. via non-3GPP access in EPC or 3GPP access in 5GC. The PCF functionality to support ATSSS, as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] applies also in the case of interworking with EPC. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.4 |
1,935 | 6.2.4A.4 A-MPR for CA_NS_04 | If the UE is configured to CA_41C or any uplink inter-band CA configuration containing CA_41C and it receives IE CA_NS_04 the allowed maximum output power reduction applied to transmission on two component carriers for contiguously aggregated signals is specified in Table 6.2.4A.4-1 and Table 6.2.4A.4-1A for UE power class 3 and in Table 6.2.4A.4-2 for UE power class 2. Table 6.2.4A.4-1: Contiguous Allocation A-MPR for CA_NS_04 (power class 3), Bandwidth Class C Table 6.2.4A.4-1A: Contiguous Allocation A-MPR for CA_NS_04 (power class 3), Bandwidth Class D Table 6.2.4A.4-2: Contiguous Allocation A-MPR for CA_NS_04 (power class 2) If the UE is configured to CA_41C or any uplink inter-band CA configuration containing CA_41C and it receives IE CA_NS_04 the allowed maximum output power reduction applied to transmissions on two serving cells assigned to Band 41 with non-contiguous resource allocation is defined as follows for UE power class 3 A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = 11, 0β€ A < 0.05 = -55.0A + 13.75, 0.05β€ A < 0.15 = -4.0A + 6.10, 0.15β€ A < 0.40 = -0.83A + 4.83, 0.40 β€ A β€ 1 Where A = NRB_alloc / NRB_agg. If the UE is configured to CA_41C or any uplink inter-band CA configuration containing CA_41C and it receives IE CA_NS_04 the allowed maximum output power reduction applied to transmissions on two serving cells assigned to Band 41 with non-contiguous resource allocation is defined as follows for UE power class 2 A-MPR = CEIL {MA, 0.5} If the UE is configured to CA_41D or any uplink inter-band CA configuration containing CA_41D and it receives IE CA_NS_04 the allowed maximum output power reduction applied to transmissions on two serving cells assigned to Band 41 with non-contiguous resource allocation is defined as follows for UE power class 3 A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = 11.5, 0β€ A < 0.05 = -55.0A + 14.25, 0.05β€ A < 0.15 = -4.0A + 6.60, 0.15β€ A < 0.40 = -0.833A + 5.333, 0.40 β€ A β€ 1 Where A = NRB_alloc / NRB_agg. Where MA is defined as follows when the lower edge of the aggregated channel bandwidth (Table 5.6A-1) is less than or equal to the lower edge cutoff frequency specified in Table 6.2.4A.4-2 for the corresponding CA bandwidth combination MA = 13.0, 0 β€ A < 0.05 = 15.33 β 46.67A, 0.05 β€ A < 0.20 = -7.0 β 5.0A, 0.20 β€ A < 0.50 = 4.5, 0.50 β€ A β€ 1 And MA is defined as follows when the lower edge of the aggregated channel bandwidth exceeds the lower edge cutoff frequency specified in Table 6.2.4A.4-2 for the corresponding CA bandwidth combination MA = 8.2, 0 β€ A < 0.04 = 9.8 β 40.0A, 0.04 β€ A < 0.075 = 8.0 β 16.0A, 0.075 β€ A < 0.25 = 4.83 β 3.33A, 0.25 β€ A < 0.40 = 3.83 β 0.83A, 0.40 β€ A β€ 1 Where A = NRB_alloc / NRB_agg. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A.4 |
1,936 | D.1 Null ciphering and integrity protection algorithms | The NEA0 algorithm shall be implemented such that it generates a KEYSTREAM of all zeroes (see sub-clause D.2.1). The length of the KEYSTREAM generated shall be equal to the LENGTH input parameter. The generated KEYSTREAM requires no other input parameters but the LENGTH. Apart from this, all processing performed in association with ciphering shall be exactly the same as with any of the ciphering algorithms specified in this Annex. The NIA0 algorithm shall be implemented in such way that it shall generate a 32 bit MAC-I/NAS-MAC and XMAC-I/XNAS-MAC of all zeroes (see sub-clause D.3.1). Replay protection shall not be activated when NIA0 is activated. All processing performed in association with integrity (except for replay protection) shall be exactly the same as with any of the integrity algorithms specified in this annex except that the receiver does not check the received MAC. NOTE 1: The reason for mentioning the replay protection here is that replay protection is associated with integrity. The NIA0 shall not be used for signalling radio bearers (SRBs) except for unauthenticated emergency sessions for unauthenticated UEs in LSM. The NIA0 shall not be used for data radio bearers (DRBs). NOTE 2: A UE with a 2G SIM is considered to be in LSM in NR. NOTE 3: NEA0 and NIA0 provide no security. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | D.1 |
1,937 | 5.4.2 Scenario | A UAS is approaching the no-fly zone around an airport. Other no-fly zones may be around prisons, highway roads, hospitals, road or crime incidents. The initial authorisation to fly did not contain a route which included this path as the UAV is small enough to not require a route in advance to be granted permission to operate. Or the no-fly zone was temporarily created because of a particular incident. The UAS is transmitting accurate positional information, which may be supplemented by the serving MNO, to the UTM. As the UTM notices that the UAV approaches the edge of the no-fly zone, the UTM decides to send warning to the UAV operator (via the UAV controller) with the details of the no-fly zone. If UAV has reached the edge of the no-fly zone the UTM decides to intervene to prevent any further incursion. The UTM determines a route to remove the UAV from the no-fly zone and provides a route modification to the UAS to achieve this correction. Optionally, the details of the no-fly zone are sent to the UAV controller for user information. The route modifications are transmitted to the UAS and are executed by the UAS to correct the position of the UAV. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.4.2 |
1,938 | 9.2.3.2A TDD (With channelMeasRestriction configured) | The following requirements apply to UE Category β₯2. For the parameters specified in table 9.2.3.2A-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 β Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 β 1 and median CQI1 β 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.3.2A-1: PUCCH 1-1 submode 1 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.3.2A |
1,939 | 9.2.1.3 FDD (CSI measurements in case two CSI subframe sets are configured) | The following requirements apply to UE Category β₯1. For the parameters specified in Table 9.2.1.3-1, and using the downlink physical channels specified in tables C.3.2-1 for Cell 1, C.3.3-1 for Cell 2 and C.3.2-2, the reported CQI value according to RC.2 FDD / RC.6 FDD in Table A.4-1 in subframes overlapping with aggressor cell ABS and non-ABS subframes shall be in the range of Β±1 of the reported median more than 90% of the time. If the PDSCH BLER in non-ABS subframes using the transport format indicated by median CQI obtained by reports in CSI subframe sets CCSI,1 is less than or equal to 0.1, the BLER in non-ABS subframes using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER in non-ABS subframes using the transport format indicated by the median CQI is greater than 0.1, the BLER in non-ABS subframes using transport format indicated by (median CQI β 1) shall be less than or equal to 0.1. The value of the median CQI obtained by reports in CSI subframe sets CCSI,0 minus the median CQI obtained by reports in CSI subframe sets CCSI,1 shall be larger than or equal to 2 and less than or equal to 5 in Test 1 and shall be larger than or equal to 0 and less than or equal to 1 in Test 2. Table 9.2.1.3-1: PUCCH 1-0 static test (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.2.1.3 |
1,940 | 7.4.8 UE Activity Notification | A UE Activity Notification message shall be sent on the S3 interface by the SGSN to the associated MME as part of an SGs Non-EPS alert procedure (see 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [22]) when ISR is activated, except under the conditions specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21], to indicate that activity from a UE has been detected. Table 7.4.8-1 specifies the presence requirements and the conditions of the IEs in the message. Table 7.4.8-1: Information Element in UE Activity Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.4.8 |
1,941 | 8.2.3.1.2 Minimum Requirement for TDD PCell | For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.1.2-4 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell with 3DL CCs, the requirements are specified in Table 8.2.3.1.2-5 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell with 4DL CCs, the requirements are specified in Table 8.2.3.1.2-6 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell with 5DL CCs, the requirements are specified in Table 8.2.3.1.2-7 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell with 6DL CCs, the requirements are specified in Table 8.2.3.1.2-8 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell with 7DL CCs, the requirements are specified in Table 8.2.3.1.2-9 based on single carrier requirement specified in Table 8.2.3.1.2-2 and Table 8.2.3.1.2-3, with the addition of the parameters in Table 8.2.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.1.2-1: Test Parameters for CA Table 8.2.3.1.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.2.3.1.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.2.3.1.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.1.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.1.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.1.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.1.2-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.1.2-9: Minimum performance for multiple CA configurations with 7DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.1.2 |
1,942 | 4.3.12.9 Handling of PDN Connections for Emergency Bearer Services | The default and dedicated EPS bearers of a PDN Connection associated with the emergency APN shall be dedicated for IMS emergency sessions and shall not allow any other type of traffic. The emergency bearer contexts shall not be changed to non-emergency bearer contexts and vice versa. The PDN GW shall block any traffic that is not from or to addresses of network entities (e.g. P-CSCF) providing IMS emergency service. Dynamic PCC shall be deployed in order to support IMS emergency sessions, the procedures are as described in TS 23.203[ Policy and charging control architecture ] [6]. If there is already an emergency PDN GW connection, the UE shall not request another emergency PDN Connection. The MME shall reject any additional emergency PDN Connection requests. The UE shall not request any bearer resource modification for the emergency PDN connection. The PDN GW shall reject any UE requested bearer resource modification that is for the emergency PDN Connection. The ARP reserved for emergency bearer service shall only be assigned to EPS bearers associated with an emergency PDN Connection. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.12.9 |
1,943 | F.3 Subscriber identity and key derivation | EAP-AKA' uses the subscriber identity (Identity) as an input to the key derivation when the key derivation function has value 1 ( i.e. MK = PRF'(IK'|CK',"EAP-AKA'"|Identity)). RFC 4187 [21] clause 7 describes that the Identity is taken from the EAP-Response/Identity or EAP-Response/AKA-Identity AT_IDENTITY attribute sent by the peer. This principle is not applied to the 5GS. If the AT_KDF_INPUT parameter contains the prefix "5G:", the AT_KDF parameter has the value 1 and the authentication is not related to fast re-authentication, then the UE shall set as the Identity for key derivation. When the SUPI Type is IMSI, the Identity shall be set to IMSI as defined in clause 2.2 of TS 23.003[ Numbering, addressing and identification ] [19]. When the SUPI type is network specific identifier, the Identity shall be set to Network Access Identifier (NAI) as defined in clause 28.7.2 of TS 23.003[ Numbering, addressing and identification ] [19]. When the SUPI type is GLI, the Identity shall be set to GLI taking format of NAI as defined in clause 28.15.2 of TS 23.003[ Numbering, addressing and identification ] [19]. When the SUPI type is GCI, the Identity shall be set to GLI taking format of NAI as defined in clause 28.16.2 of TS 23.003[ Numbering, addressing and identification ] [19]. This principle applies to all full EAP-AKA' authentications, even if the UE sent SUCI in NAS protocol or if the UE sent SUCI in the respose to the EAP identity requests as described in Table F.2-1 or if no identity was sent because the network performed re-authentication. The only exception is fast re-authentication when the UE follows the key derivation as described in RFC 5448 [12] for fast re-authentication. NOTE 1: The fast re-authentication is not supported in 5GS. NOTE 2: The prefix "5G:" is part of serving network name as specified in clause 6.1.1.4. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | F.3 |
1,944 | 8.51.2 RNC ID | The Target Type is RNC ID for SRNS relocation procedure, handover to UTRAN and RAN Information Relay towards UTRAN or GERAN operating in GERAN Iu mode, and 5G-SRVCC from NG-RAN to UTRAN procedure. In this case the "Target ID" field shall contain a non-transparent copy of the corresponding IEs (see clause 8.2.2) and be encoded as specified in Figure 8.51-1a below. The "Target RNC-ID" part of the "Target ID" parameter is specified in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33] and 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]. NOTE 1: The ASN.1 parameter "Target ID" is forwarded non-transparently in order to maintain backward compatibility. NOTE 2: The preamble of the "Target RNC-ID" (numerical value of e.g. 0x20) shall not be included into octets 6 to (n+4). Also, the optional "iE-Extensions" parameter shall not be included into the GTP IE. Figure 8.51-1a: Target ID for Type RNC ID If only two digits are included in the MNC, then bits 5 to 8 of octet 7 (MNC digit 3) shall be coded as "1111". The location area code (LAC) consists of 2 octets. Bit 8 of octet 9 is the most significant bit and bit 1 of octet 10 is the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. During a 5G-SRVCC Handover, the AMF does not receive the target RAC in the "Target RNC-ID" part of the "Target ID" IE of the Handover Required message (see clause 9.3.1.25 of 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]). The AMF should set the RAC to a default value, e.g. hexadecimal value 'FF'. The MME_SRVCC shall ignore the received RAC value. The RNC-ID consists of 2 octets and contains 12 bits long value (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [7]). Bit 4 of octet 12 is the most significant bit and bit 1 of octet 13 is the least significant bit (bits 8 to 5 of octet 12 are set to 0). The coding of the RNC-ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. The Extended RNC-ID consists of 2 octets and contains 16 bits long value within the range 4096 to 65535. Bit 8 of octet a is the most significant bit and bit 1 of octet (a+1) is the least significant bit. The coding of the Extended RNC-ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. If the optional Extended RNC-ID is included, then the receiver shall ignore the RNC-ID. If the optional Extended RNC-ID is not included, then the length variable 'n' = 8 and the overall length of the IE is 13 octets. Otherwise, 'n' = 10 and the overall length of the IE is 15 octets. NOTE 3: In the "TargetRNC-ID" ASN.1 type definition in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [7] the "RAC" parameter is marked as optional. RAC is however always available at an SGSN/MME when it sends the RAC in e.g. a GTPv2 Forward Relocation Request message. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.51.2 |
1,945 | 17.6.3 STR Command | The STR command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code field set to 275 and the βRβ bit set in the Command Flags field, It is sent by the GGSN to the BM-SC to terminate a DIAMETER session. A DIAMETER session for a multicast MBMS service is terminated when the last MBMS UE context for the MBMS bearer service is deleted. This informs the BM-SC that the GGSN would like to be deleted from the distribution tree of a particular MBMS bearer service (De-registration procedure). A DIAMETER session for an individual UEβs multicast MBMS service authorisation is terminated when the UE has requested to the GGSN to leave the MBMS bearer service. A DIAMETER session for a broadcast MBMS service may be terminated by the GGSN in exceptional cases. The STR command is also used to deactivate a Trace Session previously activated in the BM-SC and to terminate the associated Diameter Session initiated by the AAR that activated the Trace session. The Gmb specific AVP Additonal-MBMS-Trace-Info shall be included in the STR command only in the case of a Trace Session deactivation. For more detailed description of Trace Session activation/deactivation procedures see 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [69]. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format: <ST-Request> ::= < Diameter Header: 275, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Termination-Cause } [ Destination-Host ] * [ Class ] [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] [ Additional-MBMS-Trace-Info ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.6.3 |
1,946 | 6.3.5.1 Absolute power tolerance | Absolute power tolerance is the ability of the UE transmitter to set its initial output power to a specific value for the first sub-frame at the start of a contiguous transmission or non-contiguous transmission with a transmission gap larger than 20ms. This tolerance includes the channel estimation error (the absolute RSRP accuracy requirement specified in subclause 9.1 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] ). In the case of a PRACH transmission, the absolute tolerance is specified for the first preamble. The absolute power tolerance includes the channel estimation error (the absolute RSRP accuracy requirement specified in subclause 9.1 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] ). | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5.1 |
1,947 | Annex B (Informative): Transparent copying of RANAP/S1AP/NGAP IEs into GTP IEs B.1 General | This annex provides details on how a GTPv2 entity transparently copies information received from RANAP or S1AP or NGAP into GTPv2 IE or IE field. RANAP and S1AP ASN.1 encoding details in this annex are informative. The reference specifications are 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33], 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84] respectively. The respective RANAP/S1AP/NGAP Information Elements are transported on the Iu/S1 interface within a "protocol-IE container" which is composed of: - an Information Element Identity (referred to below as "IE-ID"), - an indication how the receiver shall react if the Information Element is not comprehended (referred to below as "criticality"), - and an "open type field" which consists of a length indication ("OT-LI") and the Information Element itself (referred to below as "IE"). RANAP/S1AP/NGAP PDUs and the contained IEs are defined by means of ASN.1, the specified encoding is PER (packed encoding rule), Octet aligned variant: - PER minimises the information sent on the respective interface to the absolute minimum; - Hence, type definitions of fixed length are encoded without any type or length indication, only type definitions of variable length contain a length indication, e.g. - an OCTET STRING with indefinite length would need to contain a length indication (referred to below as "OCT-LI") followed by the actual octets (referred to below as "octets"); - a SEQUENCE neither contains a type, nor a length-indication. Only in case of optional elements it contains a kind of bit string with each position of this bitstring indicating the presence of an OPTIONAL element (an encoded SEQUENCE type is referred to below as "sequence"). | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | Annex |
1,948 | 12.3.8 The interaction with APN congestion control using the PGW Back-Off Time | When detecting that a given APN is congested, the PGW shall either use the PGW Back-Off Time mechanism (see clause 4.3.7.5 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]) or the APN level overload control mechanism (i.e. providing an Overload Control Information IE with an APN-List included) for that APN, but not both together for the same APN, e.g. if the PGW provides an Overload Control Information IE with an APN-List set to "APN1", it shall not reject Create Session Request messages for "APN1" with a PGW Back-Off Time until the Period-Of-Validity of the overload information previously sent has expired. The PGW may however use both mechanisms concurrently for different APNs, e.g. the PGW may reject Create Session Request messages for the"APN2" with a PGW Back-Off Time IE, if the APN2 is also congested and if there is no on-going APN-level overload control mechanism for that APN. When rejecting a Create Session Request due to APN congestion, the PGW shall set the "APN Congestion" cause, regardless of the aforementioned mechanisms. If the MME/S4-SGSN or ePDG/TWAN has one mechanism active for a given APN and PGW, (e.g. an MME has received a PGW Back-Off Time) and if subsequently it receives information for the same APN and PGW for another mechanism, (e.g. the MME receives an Overload Control Info IE with APN-List included for the same APN), then it shall deactivate/stop the earlier mechanism and consider only the information received for the latter mechanism. Different PGWs may use concurrently different mechanisms for the same APN. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.8 |
1,949 | 10.2.2 MR-DC with 5GC | The Secondary Node (SN) Addition procedure is initiated by the MN and is used to establish a UE context at the SN in order to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the initial SCG serving cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). In case of CPA, the Conditional Secondary Node Addition procedure can be used for CPA configuration and CPA execution. This procedure can also be used to support coordination between the MN and the SN for managing the configuration and reporting of QoE measurements and/or RAN visible QoE measurements in NR-DC. Secondary Node Addition Figure 10.2.2-1 shows the SN Addition procedure. Figure 10.2.2-1: SN Addition procedure 1. The MN decides to request the target SN to allocate resources for one or more specific PDU Sessions/QoS Flows, indicating QoS Flows characteristics (QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. In NGEN-DC and NR-DC, the MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. The MN may request the SCG to be activated or deactivated. For MN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides Xn-U UL TNL address information. For SN terminated bearers, the MN provides a list of available DRB IDs. The S-NG-RAN node shall store this information and use it when establishing SN terminated bearers. The SN may reject the request. For SN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the SN decides how to map QoS flows to DRB. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Addition Request message may contain the QMC Coordination Request IE. NOTE 1: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the SN, which may differ from QoS Flow parameters received over NG. NOTE 2: For a specific QoS flow, the MN may request the direct establishment of SCG and/or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer. 2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources. For bearers requiring SCG radio resources the SN triggers UE Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides for the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN within an SN RRC configuration message contained in the SN Addition Request Acknowledge message. If the MN requested the SCG to be deactivated, the SN may keep the SCG activated. If the MN requests the SCG to be activated, the SN shall keep the SCG activated. In case of bearer options that require Xn-U resources between the MN and the SN, the SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. In case of coordination between the MN and the SN on QoE and RAN visible QoE measurement configuration and reporting, the SN Addition Request Acknowledge message may contain the QMC Coordination Response IE. NOTE 3: In case of MN terminated bearers, transmission of user plane data may take place after step 2. NOTE 4: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2. NOTE 5: For MN terminated bearers for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the SN provides a logical channel ID for primary or split secondary path to the MN. For SN terminated bearers for which PDCP duplication with CA is configured in NR MCG side, the SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the SN via an additional MN-initiated SN modification procedure. 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 3. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC configuration message, without modifying it. Within the MN RRC reconfiguration message, the MN can indicate the SCG is deactivated. 4. The UE applies the new configuration and replies to MN with MN RRC reconfiguration complete message, including an SN RRC response message for SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure. 5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the SN RRC response message, if received from the UE. 6. If configured with bearers requiring SCG radio resources and the SCG is not deactivated, the UE performs synchronisation towards the PSCell configured by the SN. The order the UE sends the MN RRC reconfiguration complete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the SN Status Transfer message. 8. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). 9-12. If applicable, the update of the UP path towards the 5GC is performed via a PDU Session Path Update procedure. Conditional Secondary Node Addition Figure 10.2.2-2 shows the Conditional SN Addition procedure. Figure 10.2.2-2: Conditional Secondary Node Addition procedure 1. The MN decides to configure CPA for the UE. The MN requests the candidate SN(s) to allocate resources for one or more specific PDU Sessions/QoS Flows, indicating QoS Flows characteristics (QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info), indicating that the request is for CPA and providing the upper limit for the number of PSCells that can be prepared by the candidate SN. In addition, for bearers requiring SCG radio resources, the MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the candidate cells recommended by MN via the latest measurement results for the candidate SN to choose and configure the SCG cell(s). The MN may request the candidate SN to allocate radio resources for split SRB operation. In NR-DC, the MN always provides all the needed security information to the candidate SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. For MN terminated bearer options that require Xn-U resources between the MN and the candidate SN, the MN provides Xn-U UL TNL address information. For SN terminated bearers, the MN provides a list of available DRB IDs. The candidate SN shall store this information and use it when establishing SN terminated bearers. The candidate SN may reject the addition request. For SN terminated bearer options that require Xn-U resources between the MN and the candidate SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the candidate SN decides how to map QoS flows to DRB. NOTE 6: For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the candidate SN, which may differ from QoS Flow parameters received over NG. NOTE 7: For a specific QoS flow, the MN may request the direct establishment of SCG and/or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer. 2. If the RRM entity in the candidate SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources, and provides the prepared PSCell ID(s) to the MN. For bearers requiring SCG radio resources the candidate SN configures Random Access so that synchronisation of the SN radio resource configuration can be performed at the CPA execution. Fromthe list of cells indicated within the measurement results provided by the MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the MN in an NR RRCReconfiguration** message, contained in the SN Addition Request Acknowledge message. The candidate SN can either accept or reject each of the candidate cells listed within the measurement results indicated by the MN, i.e. it cannot configure any alternative candidates. In case of bearer options that require Xn-U resources between the MN and the candidate SN, the candidate SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the candidate SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided. NOTE 8: For MN terminated bearers for which PDCP duplication with CA is configured in NR SCG side, the MN allocates up to 4 separate Xn-U bearers and the candidate SN provides a logical channel ID for primary or split secondary path to the MN. For SN terminated bearers for which PDCP duplication with CA is configured in NR MCG side, the candidate SN allocates up to 4 separate Xn-U bearers and the MN provides a logical channel ID for primary or split secondary path to the candidate SN via an additional MN-initiated SN modification procedure. NOTE 9: In case of SN terminated bearers, early data forwarding may take place after step 2. For the early data forwarding of SN terminated bearers, the MN forwards the PDCP SDU to the candidate SN. For the early transmission of MN terminated split/SCG bearers, the MN forwards the PDCP PDU to the candidate SN. 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. In case of early data forwarding in CPA, the MN sends the Early Status Transfer message to the candidate SN. 3. The MN sends to the UE an RRCReconfiguration message including the CPA configuration, i.e. a list of RRCReconfiguration* messages and associated execution conditions. Each RRCReconfiguration* message contains the SCG configuration in the RRCReconfiguration** received from the candidate SN in step 2 and possibly an MCG configuration. Besides, the RRCReconfiguration message can also include an updated MCG configuration. e.g. to configure the required conditional measurements. 4. The UE applies the RRCReconfiguration message received in step 3, stores the CPA configuration and replies to the MN with an RRCReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 4a. The UE starts evaluating the execution conditions. If the execution condition of one candidate PSCell is satisfied, the UE applies RRCReconfiguration* message corresponding to the selected candidate PSCell, and sends an MN RRCReconfigurationComplete* message, including an RRCReconfigurationComplete** message for the selected candidate PSCell, and information enabling the MN to identify the SN of the selected candidate PSCell. 5a-5c. The MN informs the SN of the selected candidate PSCell that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the RRCReconfigurationComplete** message. The MN sends the SN Release Request message(s) to cancel CPA in the other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 6. The UE performs synchronisation towards the PSCell indicated in the RRCReconfiguration* message applied in step 4a. The order the UE sends the MN RRCReconfigurationComplete* message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure. 7. If PDCP termination point is changed to the SN for bearers using RLC AM, and when RRC full configuration is not used, the MN sends the SN Status Transfer message. 8. For SN terminated bearers or QoS flows moved from the MN, dependent on the characteristics of the respective bearer or QoS flow, the MN may take actions to minimise service interruption due to activation of MR-DC (Data forwarding). 9-12. If applicable, the update of the UP path towards the 5GC is performed via a PDU Session Path Update procedure. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.2.2 |
1,950 | 6.1.2A.1.1 Interworking with PDN based on IP | During PDP context activation (see subclause 6.1.3.1), the MS can configure an IPv4 address, or obtain an IPv6 interface identifier to be used during the IETF-based IP address allocation after PDP context establishment. The MS can obtain an IPv4 address or an IPv6 prefix via an IETF-based IP address allocation mechanism once the PDP context is established. The following IETF-based IP address/prefix allocation methods are specified for GPRS (the corresponding procedures are specified in 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [130]): a) /64 IPv6 default prefix allocation via IPv6 stateless address autoconfiguration. Optionally, allocation of additional IPv6 prefix(es) with length /64 or shorter via stateful DHCPv6 Prefix Delegation (see IETF RFC 3633 [139]); b) IPv4 address allocation and IPv4 parameter configuration via DHCPv4; Upon deactivation of a default PDP context, the MS shall locally release any IPv4 address or IPv6 prefix allocated to the MS for the corresponding PDN connection. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.2A.1.1 |
1,951 | Annex C (informative): Guidelines and Principles for Compute-Storage Separation | 5G System Architecture allows any NF/NF Service to store and retrieve its unstructured data (e.g. UE contexts) into/from a Storage entity (e.g. UDSF) as stated in clause 4.2.5 in this release of the specification. This clause highlights some assumptions, principles regarding NF/NF services that use this Storage entity for storing unstructured data: 1. It is up to the Network Function implementation to determine whether the Storage entity is used as a Primary Storage (in which case the corresponding context stored within the NF/NF Service is deleted after storage in the Storage entity) or the Storage entity is used as a Secondary Storage (in which case the corresponding context within the NF/NF Service is stored). 2. It is up to the NF/NF Service implementation to determine the trigger (e.g. at the end of Registration procedure, Service Request procedure etc) for storing unstructured data (e.g. UE contexts) in the Storage entity but it is a good practice for NF/NF service to store stable state in the Storage entity. 3. Multiple NF/NF service instances may require to access the same stored data in the Storage entity (e.g. UE context), around the same time, then the resolution the race condition is implementation specific. 4. All NFs within the same NF Set are assumed to have access to the same unstructured data stored within the Storage entity. 5. AMF planned removal with UDSF (clause 5.21.2.2.1) and AMF auto-recovery (with UDSF option in clause 5.21.2.3) assume that a storage entity/UDSF is used either as a primary storage or secondary storage by the AMF for storing UE contexts. 6. It is up to implementation of the Storage entity to make sure that only NFs that are authorized for a certain data record can access this data record. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
1,952 | 6.10.6 Signalling procedure for PDCP COUNT check | SN may request the MN to execute a counter check procedure specified in Clause 6.13 of this specification to verify the value of the PDCP COUNT(s) associated with DRB(s) offloaded to the SN. To accomplish this, the SN shall communicate this request, including the expected values of PDCP COUNT(s) and associated radio bearer identities to the MN over the Xn-C. If the MN receives a RRC counter check response from the UE that contains one or several PDCP COUNT values (possibly associated with both MN and SN), the MN may release the connection or report the difference of the PDCP COUNT values to the serving AMF or O&M server for further traffic analysis, e.g., detecting the attacker. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.6 |
1,953 | 4.4.3.3 PDN GW | The PDN GW is the gateway which terminates the SGi interface towards the PDN. If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously. PDN GW functions include for both the GTP-based and the PMIP-based S5/S8: - Per-user based packet filtering (by e.g. deep packet inspection); - Lawful Interception; - UE IP address allocation; - Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point, based on the QCI, and optionally the ARP priority level, of the associated EPS bearer; - Accounting for inter-operator charging: for home routed roaming, the P-GW shall collect and report the uplink and downlink data volume (per EPS bearer) as received from and sent to the serving node; - UL and DL service level charging as defined in TS 23.203[ Policy and charging control architecture ] [6] (e.g. based on SDFs defined by the PCRF, or based on deep packet inspection defined by local policy); - Interfacing OFCS through according to charging principles and through reference points specified in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [51]. - UL and DL service level gating control as defined in TS 23.203[ Policy and charging control architecture ] [6]; - UL and DL service level rate enforcement as defined in TS 23.203[ Policy and charging control architecture ] [6] (e.g. by rate policing/shaping per SDF); - UL and DL rate enforcement based on APN-AMBR (e.g. by rate policing/shaping per aggregate of traffic of all SDFs of the same APN that are associated with Non-GBR QCIs); - DL rate enforcement based on the accumulated MBRs of the aggregate of SDFs with the same GBR QCI (e.g. by rate policing/shaping); - DHCPv4 (server and client) and DHCPv6 (client and server) functions; - The network does not support PPP bearer type in this version of the specification. Pre-Release 8 PPP functionality of a GGSN may be implemented in the PDN GW; - The PDN GW may support Non-IP data transfer (e.g. with CIoT EPS Optimisations); - The PDN GW (when acting as a combined PDN GW+SMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [83]) may support Ethernet data transfer; - packet screening; - sending of one or more "end marker" to the source SGW immediately after switching the path during SGW change; - PCC related features (e.g. involving PCRF and OCS) as described in TS 23.203[ Policy and charging control architecture ] [6]. Additionally the PDN GW includes the following functions for the GTP-based S5/S8: - UL and DL bearer binding as defined in TS 23.203[ Policy and charging control architecture ] [6]; - UL bearer binding verification as defined in TS 23.203[ Policy and charging control architecture ] [6]; - Functionality as defined in RFC 4861 [32]; - Accounting per UE and bearer. The P-GW provides PDN connectivity to both GERAN/UTRAN only UEs and E-UTRAN capable UEs using any of E-UTRAN, GERAN or UTRAN. The P-GW provides PDN connectivity to E-UTRAN capable UEs using E-UTRAN only over the S5/S8 interface. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.3.3 |
1,954 | β SL-RemoteUE-Config | The IE SL-RemoteUE-Config specifies the configuration information for NR sidelink U2N Remote UE. SL-RemoteUE-Config information element -- ASN1START -- TAG-SL-REMOTEUE-CONFIG-START SL-RemoteUE-Config-r17::= SEQUENCE { threshHighRemote-r17 RSRP-Range OPTIONAL, -- Need R hystMaxRemote-r17 Hysteresis OPTIONAL, -- Cond ThreshHighRemote sl-ReselectionConfig-r17 SL-ReselectionConfig-r17 OPTIONAL -- Need R } SL-ReselectionConfig-r17::= SEQUENCE { sl-RSRP-Thresh-r17 SL-RSRP-Range-r16 OPTIONAL, -- Need R sl-FilterCoefficientRSRP-r17 FilterCoefficient OPTIONAL, -- Need R sl-HystMin-r17 Hysteresis OPTIONAL -- Cond SL-RSRP-Thresh } -- TAG-SL-REMOTEUE-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,955 | 4.4 Functions | The RRC protocol includes the following main functions: - Broadcast of system information: - Including NAS common information; - Information applicable for UEs in RRC_IDLE and RRC_INACTIVE (e.g. cell (re-)selection parameters, neighbouring cell information) and information (also) applicable for UEs in RRC_CONNECTED (e.g. common channel configuration information); - Including ETWS notification, CMAS notification; - Including positioning assistance data. - RRC connection control: - Paging; - Establishment/modification/suspension/resumption/release of RRC connection, including e.g. assignment/modification of UE identity (C-RNTI, fullI-RNTI, etc.), establishment/modification/suspension/resumption/release of SRBs (except for SRB0); - Access barring; - Initial AS security activation, i.e. initial configuration of AS integrity protection (SRBs, DRBs) and AS ciphering (SRBs, DRBs); - RRC connection mobility including e.g. intra-frequency and inter-frequency handover, path switch from a PCell to a target L2 U2N Relay UE or from a L2 U2N Relay UE to a target PCell or from a source L2 U2N Relay UE to a target L2 U2N Relay UE, associated AS security handling, i.e. key/algorithm change, specification of RRC context information transferred between network nodes; - Establishment/modification/suspension/resumption/release of RBs carrying user data (DRBs/MRBs); - Radio configuration control including e.g. assignment/modification of ARQ configuration, HARQ configuration, DRX configuration; - In case of DC, cell management including e.g. change of PSCell, addition/modification/release of SCG cell(s); - In case of CA, cell management including e.g. addition/modification/release of SCell(s); - In case of MP, path management including e.g. addition/modification/release of indirect path; - QoS control including assignment/ modification of semi-persistent scheduling (SPS) configuration and configured grant configuration for DL and UL respectively, assignment/ modification of parameters for UL rate control in the UE, i.e. allocation of a priority and a prioritised bit rate (PBR) for each RB of UE and logical channel of IAB-MT. - Recovery from radio link failure. - Inter-RAT mobility including e.g. AS security activation, transfer of RRC context information; - Measurement configuration and reporting: - Establishment/modification/release of measurement configuration (e.g. intra-frequency, inter-frequency and inter- RAT measurements); - Setup and release of measurement gaps; - Measurement reporting. - Configuration of BAP entity and BH RLC channels for the support of IAB-node. - Configuration of SRAP entity and Uu/PC5 Relay RLC channels for the support of L2 U2N relay. - Other functions including e.g. generic protocol error handling, transfer of dedicated NAS information, transfer of UE radio access capability information. - Support of self-configuration and self-optimisation. - Support of measurement logging and reporting for network performance optimisation, as specified in TS 37.320[ Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2 ] [61]; - Support of transfer of application layer measurement configuration and reporting. - Configuration of side control information for NCR-node. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.4 |
1,956 | 5.3.10.5 ME identity check procedure | The Mobile Equipment Identity Check Procedure permits the operator(s) of the MME and/or the HSS and/or the PDN GW to check the Mobile Equipment's identity (e.g. to check that it has not been stolen, or, to verify that it does not have faults). The ME Identity can be checked by the MME passing it to an Equipment Identity Register (EIR) and then the MME analysing the response from the EIR in order to determine its subsequent actions (e.g. sending an Attach Reject if the EIR indicates that the Mobile Equipment is prohibited). The ME identity check procedure is illustrated in Figure 5.3.10.5-1. Figure 5.3.10.5-1: Identity Check Procedure 1. The MME sends Identity Request (Identity Type) to the UE. The UE responds with Identity Response (Mobile Identity). 2. If the MME is configured to check the IMEI against the EIR, it sends ME Identity Check (ME Identity, IMSI) to EIR. The EIR responds with ME Identity Check Ack (Result). NOTE: The Identity Check Procedure is typically executed as part of the Attach procedure (see clause 5.3.2.1). | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.10.5 |
1,957 | 9.9.3.12A EPS network feature support | The purpose of the EPS network feature support information element is to indicate whether certain features are supported by the network. The EPS network feature support information element is coded as shown in figure 9.9.3.12A.1 and table 9.9.3.12A.1. The EPS network feature support is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets. If the network does not include octet 4 or octet 5 as defined below in the present version of the protocol, then the UE shall interpret this as a receipt of an information element with all bits of octet 4 and 5 coded as zero. Figure 9.9.3.12A.1: EPS network feature support information element Table 9.9.3.12A.1: EPS network feature support information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.12A |
1,958 | 6.5.5 Integrity key selection | There may be one IK for CS connections (IKCS), established between the CS service domain and the user and one IK for PS connections (IKPS) established between the PS service domain and the user. The data integrity of radio bearers for user data is not protected. The signalling radio bearers are used for transfer of signalling data for services delivered by both CS and PS service domains. These signalling radio bearers are data integrity protected by the IK of the service domain for which the most recent security mode negotiation took place. This may require that the integrity key of an (already integrity protected) ongoing signalling connection has to be changed, when a new connection is established with another service domain, or when a security mode negotiation follow a re-authentication during an ongoing connection. This change should be completed by the RNC within five seconds after receiving the security mode command from the VLR/SGSN. NOTE: For the behaviour of the terminal regarding key changes see section 6.4.5. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.5 |
1,959 | 21.5 Alignment of MDT and QoE Measurements | The radio-related measurements may be collected via immediate MDT for all types of supported services for the purpose of QoE analysis. The MCE/TCE performs the correlation of the immediate MDT measurement results and the QoE measurement results collected at the same UE. The following is supported: - Alignment between a signalling-based QoE measurement and a signalling-based MDT measurement. In this case, the signalling-based QoE configuration sent to the gNB includes the NG-RAN Trace ID of the signalling-based MDT measurement. - Alignment between a management-based QoE measurement and a management-based MDT measurement. The UE configured with QoE measurements sends an indication to inform the gNB about the start or the stop of a QoE measurement session of configured QoE measurements. The gNB can activate the MDT measurements that are to be aligned with the QoE measurements performed by the UE upon/after receiving the QoE measurement session start indication from the UE. The gNB may activate the MDT measurements upon/after receiving the MDT activation message from the OAM. The gNB can deactivate the aligned MDT measurements according to an OAM command which may, e.g., be triggered by the session stop indication. The gNB includes time stamp information to the QoE measurement reports to enable the correlation of corresponding measurement results of MDT and QoE at the MCE/TCE. In addition, the gNB includes the MDT session identifiers (Trace Reference and Trace Recording Session Reference) in the corresponding QoE measurement report. 21.6 QoE Measurement Collection in High Mobility Scenarios QoE measurements can be confined to high mobility state of the UE and/or to HSDN cells. 21.7 Support for RAN visible QoE measurements and reporting in NR-DC Either the MN or the SN can generate and send a RAN visible QoE configuration to the UE. The gNB that has initially configured a UE in NR-DC with an RVQoE configuration can modify and release the RAN visible QoE configuration as long as the UE is connected to this gNB. The gNB that configures the encapsulated QoE measurements to UE is referred to as the RAN visible QoE-configuring gNB, and the peer node is referred to as the non-RAN visible QoE-configuring gNB. Upon mobility, the RAN visible QoE-configuring gNB may be changed. The UE may send RAN visible QoE reports to the network using either SRB4 or SRB5. In addition, the gNB that received a RAN visible QoE report can forward the report to the other gNB (the SN or the MN). QoE reports and RAN visible QoE reports pertaining to the same QoE Reference can be sent over the same SRB or they can be sent over different SRBs. The RAN visible QoE-configuring gNB can configure RAN visible QoE measurements at a UE without a priori knowledge about which gNB(s) will provide the bearer(s) for a future application session. During the lifetime of an application session, to ensure that the RAN visible QoE reports are sent to the gNB(s) that provide the bearer(s) which carry the data flow(s) associated with the RAN visible QoE measurement result in a RAN visible QoE report, the gNB receiving the RAN visible QoE reports determines the bearer(s) used to deliver the application session data flow(s) and the associated gNB (s). The determination may be based on the PDU session ID(s) and the QoS flow ID(s) indicated in a received RAN visible QoE report. When the RAN visible QoE-configuring gNB receives a RAN visible QoE measurement report and determines that the non-RAN Visible QoE-configuring gNB provides at least one bearer for the application session, the RAN Visible QoE-configuring gNB indicates that to the non-RAN Visible QoE-configuring gNB. The non-RAN Visible QoE-configuring gNB can then, if needed, indicate to the RAN visible QoE-configuring gNB its preference with respect to the reporting path for the subsequent RAN visible QoE reports and its preferred RAN visible QoE configuration parameters. If a gNB receives a RAN visible QoE report from a UE in NR-DC, and determines that the bearer(s) for the application session data flow(s) is (are) also provided by the other gNB, or only, provided by the other gNB, the gNB that received the RAN visible QoE measurement report may forward the received RAN visible QoE report to the other gNB. The RAN visible QoE reports can be transferred between the MN and the SN via the RRC TRANSFER message. The RAN visible QoE configuration may also be modified or released. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.5 |
1,960 | 5.4.4 Generic UE configuration update procedure 5.4.4.1 General | The purpose of this procedure is to: a) allow the AMF to update the UE configuration for access and mobility management-related parameters decided and provided by the AMF by providing new parameter information within the command; b) request the UE to perform a registration procedure for mobility and periodic registration update towards the network to update access and mobility management-related parameters decided and provided by the AMF (see subclause 5.5.1.3); c) deliver the UAV authorization information to the UE, as described in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]; or d) update the PEIPS assistance information in the UE (see subclause 5.3.25). This procedure is initiated by the network and can only be used when the UE has an established 5GMM context, and the UE is in 5GMM-CONNECTED mode. When the UE is in 5GMM-IDLE mode, the AMF may use the paging or notification procedure to initiate the generic UE configuration update procedure. The AMF can request a confirmation response in order to ensure that the parameter has been updated by the UE. This procedure shall be initiated by the network to assign a new 5G-GUTI to the UE after: a) a successful service request procedure invoked as a response to a paging request from the network and before the: 1) release of the N1 NAS signalling connection; or 2) suspension of the N1 NAS signalling connection due to user plane CIoT 5GS optimization i.e. before the UE and the AMF enter 5GMM-IDLE mode with suspend indication; or b) the AMF receives an indication from the lower layers that it has received the NGAP UE context resume request message as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31] for a UE in 5GMM-IDLE mode with suspend indication and this resumption is a response to a paging request from the network, and before the: 1) release of the N1 NAS signalling connection; or 2) suspension of the N1 NAS signalling connection due to user plane CIoT 5GS optimization i.e. before the UE and the AMF enter 5GMM-IDLE mode with suspend indication. If the service request procedure was triggered due to 5GSM downlink signalling pending, the procedure for assigning a new 5G-GUTI can be initiated by the network after the transport of the 5GSM downlink signalling. The following parameters are supported by the generic UE configuration update procedure without the need to request the UE to perform the registration procedure for mobility and periodic registration update: a) 5G-GUTI; b) TAI list; c) Service area list; d) NITZ information; e) LADN information; e1) Extended LADN information; f) Rejected NSSAI; NOTE: A cause value associated with a rejected S-NSSAI can be included in the Rejected NSSAI IE or in the Extended rejected NSSAI IE and a back-off timer value associated with rejected S-NSSAI(s) can be included in the Extended rejected NSSAI IE. g) void; h) Operator-defined access category definitions; i) SMS indication; j) "CAG information list"; k) UE radio capability ID; l) 5GS registration result; m) Truncated 5G-S-TMSI configuration; n) T3447 value; o) "list of PLMN(s) to be used in disaster condition"; p) disaster roaming wait range; q) disaster return wait range; r) PEIPS assistance information; s) Priority indicator; t) NSAG information; u) RAN timing synchronization; v) Alternative NSSAI; w) Discontinuous coverage maximum time offset x) void; y) Partially rejected NSSAI; and z) On-demand NSSAI. The following parameters can be sent to the UE with or without a request to perform the registration procedure for mobility and periodic registration update: a) Allowed NSSAI; b) Configured NSSAI; c) Network slicing subscription change indication; d) NSSRG information; e) S-NSSAI location validity information; e1) S-NSSAI time validity information; f) feature authorization indication; and g) Partially allowed NSSAI. The following parameters are sent to the UE with a request to perform the registration procedure for mobility and periodic registration update: a) MICO indication; b) UE radio capability ID deletion indication; and c) Additional configuration indication. The following parameters can be included in the Service-level-AA container IE to be sent to the UE without a request to perform the registration procedure for mobility and periodic registration update: a) Service-level device ID; b) Service-level-AA payload type; c) Service-level-AA payload; d) Service-level-AA response; or e) Service-level-AA service status indication. The following parameters are sent over 3GPP access only: a) LADN information; a1) Extended LADN information; b) MICO indication; c) TAI list; d) Service area list; e) "CAG information list"; f) UE radio capability ID; g) UE radio capability ID deletion indication; h) Truncated 5G-S-TMSI configuration; i) Additional configuration indication; j) T3447 value; k) Service-level-AA container; l) NSAG information; and m) RAN timing synchronization. o) S-NSSAI location validity information. The following parameters are managed and sent per access type i.e., independently over 3GPP access or non-3GPP access: a) Allowed NSSAI; b) Rejected NSSAI (when the NSSAI is rejected for the current registration area or is rejected for the maximum number of UEs reached); and c) If the UE is not registered to the same PLMN or SNPN over 3GPP and non-3GPP access: - 5G-GUTI; - NITZ information; - Rejected NSSAI (when the NSSAI is rejected for the current PLMN or SNPN or rejected for the failed or revoked NSSAA); - Configured NSSAI; - NSSRG information; - SMS indication; - 5GS registration result; - PEIPS assistance information; - MPS indicator; - S-NSSAI time validity information; - Alternative NSSAI; and - MCS indicator. If the UE is registered to the same PLMN or SNPN over 3GPP and non-3GPP access, the following parameters are managed commonly and sent over 3GPP access or non-3GPP access: a) 5G-GUTI; b) NITZ information; c) Rejected NSSAI (when the NSSAI is rejected for the current PLMN or SNPN or rejected for the failed or revoked NSSAA); d) Configured NSSAI; e) SMS indication; and f) 5GS registration result; g) "list of PLMN(s) to be used in disaster condition"; h) disaster roaming wait range; i) disaster return wait range; j) PEIPS assistance information; k) NSSRG information; l) MPS indicator; m) S-NSSAI time validity information; and n) MCS indicator. Figure 5.4.4.1.1: Generic UE configuration update procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4 |
1,961 | β MeasObjectCLI | The IE MeasObjectCLI specifies information applicable for SRS-RSRP measurements and/or CLI-RSSI measurements. MeasObjectCLI information element -- ASN1START -- TAG-MEASOBJECTCLI-START MeasObjectCLI-r16 ::= SEQUENCE { cli-ResourceConfig-r16 CLI-ResourceConfig-r16, ... } CLI-ResourceConfig-r16 ::= SEQUENCE { srs-ResourceConfig-r16 SetupRelease { SRS-ResourceListConfigCLI-r16 } OPTIONAL, -- Need M rssi-ResourceConfig-r16 SetupRelease { RSSI-ResourceListConfigCLI-r16 } OPTIONAL -- Need M } SRS-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-SRS-Resources-r16)) OF SRS-ResourceConfigCLI-r16 RSSI-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-RSSI-Resources-r16)) OF RSSI-ResourceConfigCLI-r16 SRS-ResourceConfigCLI-r16 ::= SEQUENCE { srs-Resource-r16 SRS-Resource, srs-SCS-r16 SubcarrierSpacing, refServCellIndex-r16 ServCellIndex OPTIONAL, -- Need S refBWP-r16 BWP-Id, ... } RSSI-ResourceConfigCLI-r16 ::= SEQUENCE { rssi-ResourceId-r16 RSSI-ResourceId-r16, rssi-SCS-r16 SubcarrierSpacing, startPRB-r16 INTEGER (0..2169), nrofPRBs-r16 INTEGER (4..maxNrofPhysicalResourceBlocksPlus1), startPosition-r16 INTEGER (0..13), nrofSymbols-r16 INTEGER (1..14), rssi-PeriodicityAndOffset-r16 RSSI-PeriodicityAndOffset-r16, refServCellIndex-r16 ServCellIndex OPTIONAL, -- Need S ... } RSSI-ResourceId-r16 ::= INTEGER (0.. maxNrofCLI-RSSI-Resources-1-r16) RSSI-PeriodicityAndOffset-r16 ::= CHOICE { sl10 INTEGER(0..9), sl20 INTEGER(0..19), sl40 INTEGER(0..39), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), s1640 INTEGER(0..639), ... } -- TAG-MEASOBJECTCLI-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,962 | 9.11.3.39 Payload container | The purpose of the Payload container information element is to transport one or multiple payloads. If multiple payloads are transported, the associated information of each payload are also transported together with the payload. The Payload container information element is coded as shown in figure 9.11.3.39.1, figure 9.11.3.39.1A, figure 9.11.3.39.1B, figure 9.11.3.39.2, figure 9.11.3.39.3, figure 9.11.3.39.4 and table 9.11.3.39.1. The Payload container information element is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets. Figure 9.11.3.39.1: Payload container information element Figure 9.11.3.39.1A: Payload container contents with Payload container type "Event notification" Figure 9.11.3.39.1B: Even notification indicator n Figure 9.11.3.39.2: Payload container contents with Payload container type "Multiple payloads" Figure 9.11.3.39.3: Payload container entry Figure 9.11.3.39.4: Optional IE Table 9.11.3.39.1: Payload container information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.39 |
1,963 | 8.88 Signalling Priority Indication | The Signalling Priority Indication information element contains signalling priority indications received from the UE for a specific PDN connection. The Signalling Priority Indication information element is coded as shown in figure 8.88-1. Figure 8.88-1: Signalling Priority Indication The following bits within Octet 5 shall indicate: - Bit 8 to 2 β Spare, for future use and set to zero. - Bit 1 β LAPI (Low Access Priority Indication): This bit defines if the UE indicated low access priority when establishing the PDN connection. It shall be encoded as the Low Priority parameter of the Device Properties IE in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. The receiver shall assume the value "0" if the Signalling Priority Indication IE is applicable for a message but not included in that message by the sender. The low access priority indication may be included in charging records. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.88 |
1,964 | 10.3 Uplink Scheduling | In the uplink, the gNB can dynamically allocate resources to UEs via the C-RNTI on PDCCH(s). A UE always monitors the PDCCH(s) in order to find possible grants for uplink transmission when its downlink reception is enabled (activity governed by DRX and cell DTX when configured). When CA is configured, the same C-RNTI applies to all serving cells. The gNB may cancel a PUSCH transmission, or a repetition of a PUSCH transmission, or an SRS transmission of a UE for another UE with a latency-critical transmission. The gNB can configure UEs to monitor cancelled transmission indications using CI-RNTI on a PDCCH. If a UE receives the cancelled transmission indication, the UE shall cancel the PUSCH transmission from the earliest symbol overlapped with the resource or the SRS transmission overlapped with the resource indicated by cancellation (see clause 11.2A of TS 38.213[ NR; Physical layer procedures for control ] [38]). In addition, with Configured Grants, the gNB can allocate uplink resources for the initial HARQ transmissions and HARQ retransmissions to UEs. Two types of configured uplink grants are defined: - With Type 1, RRC directly provides the configured uplink grant (including the periodicity). - With Type 2, RRC defines the periodicity of the configured uplink grant while PDCCH addressed to CS-RNTI can either signal and activate the configured uplink grant, or deactivate it; i.e. a PDCCH addressed to CS-RNTI indicates that the uplink grant can be implicitly reused according to the periodicity defined by RRC, until deactivated. If the UE is not configured with enhanced intra-UE overlapping resources prioritization, the dynamically allocated uplink transmission overrides the configured uplink grant in the same serving cell, if they overlap in time. Otherwise an uplink transmission according to the configured uplink grant is assumed, if activated. If the UE is configured with enhanced intra-UE overlapping resources prioritization, in case a configured uplink grant transmission overlaps in time with dynamically allocated uplink transmission or with another configured uplink grant transmission in the same serving cell, the UE prioritizes the transmission based on the comparison between the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDUs associated with the overlapping resources. Similarly, in case a configured uplink grant transmissions or a dynamically allocated uplink transmission overlaps in time with a scheduling request transmission, the UE prioritizes the transmission based on the comparison between the priority of the logical channel which triggered the scheduling request and the highest priority of the logical channels that have data to be transmitted and which are multiplexed or can be multiplexed in MAC PDU associated with the overlapping resource. In case the MAC PDU associated with a deprioritized transmission has already been generated, the UE keeps it stored to allow the gNB to schedule a retransmission. The UE may also be configured by the gNB to transmit the stored MAC PDU as a new transmission using a subsequent resource of the same configured uplink grant configuration when an explicit retransmission grant is not provided by the gNB. Retransmissions other than repetitions are explicitly allocated via PDCCH(s) or via configuration of a retransmission timer. The UE may be configured with up to 12 active configured uplink grants for a given BWP of a serving cell. When more than one is configured, the network decides which of these configured uplink grants are active at a time (including all of them). Each configured uplink grant can either be of Type 1 or Type 2. For Type 2, activation and deactivation of configured uplink grants are independent among the serving cells. When more than one Type 2 configured grant is configured, each configured grant is activated separately using a DCI command and deactivation of Type 2 configured grants is done using a DCI command, which can either deactivate a single configured grant configuration or multiple configured grant configurations jointly. When SUL is configured, the network should ensure that an active configured uplink grant on SUL does not overlap in time with another active configured uplink grant on the other UL configuration. For both dynamic grant and configured grant, for a transport block, two or more repetitions can be in one slot, or across slot boundary in consecutive available slots with each repetition in one slot. For both dynamic grant and configured grant Type 2, the number of repetitions can be also dynamically indicated in the L1 signalling. The dynamically indicated number of repetitions shall override the RRC configured number of repetitions, if both are present. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.3 |
1,965 | 15.5.2 Support for Mobility Robustness Optimization 15.5.2.1 General | Mobility Robustness Optimisation aims at detecting and enabling correction of following problems: - Connection failure due to intra-system or inter-system mobility; - Inter-system Unnecessary HO (too early inter-system HO from NR to E-UTRAN with no radio link failure); - Inter-system HO ping-pong; - PSCell change failure; - Inter-system voice fallback failure; - Fast MCG recovery failure. MRO provides means to distinguish the above problems from NR coverage related problems and other problems, not related to mobility. For detection of a sub-optimal successful handovers, MRO additionally enables observability of: - Successful HO due to intra-NR mobility; - Successful HO due to inter-RAT mobility. For detection of a sub-optimal successful PSCell addition/change, MRO additionally enables observability of: - Successful PSCell addition/change. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2 |
1,966 | 5.4.1.4 Support of Unavailability Period | During Registration procedure, the UE supporting the Unavailability Period feature provides "Unavailability Period Support" indication as part of 5GMM Core Network Capability in Registration Request message for initial registration and for every mobility registration. The AMF indicates whether the corresponding feature is supported in the AMF by providing the "Unavailability Period Support" indication in Registration Accept message. If the UE and network support Unavailability Period and an event is triggered in the UE that would make the UE unavailable or lose coverage (see clause 5.4.13.1) for a certain period of time, the UE uses Support of Unavailability Period to inform the AMF of the expected unavailability and whether it is due to NR satellite access discontinuous coverage. Use of Support of Unavailability Period for loss of coverage due to NR satellite access discontinuous coverage shall only be used if both UE and the AMF signalled "Unavailability Period Support", see clause 5.4.13.1. If the use of Support of Unavailability Period procedure is not due to NR satellite access discontinuous coverage, the UE may store its MM and SM context in the USIM or Non-Volatile memory in the ME to be able to reuse it after its unavailability period. If the UE can store its contexts the UE may trigger Mobility Registration Update procedure otherwise the UE shall trigger UE-initiated Deregistration procedure. NOTE 1: How and where the UE stores its contexts depends upon the UE implementation and the Unavailability Type. The UE can store some or all of its contexts in the ME or USIM using existing ME or USIM functionality. Before the start of an event that makes the UE unavailable, the UE triggers either Mobility Registration Update or UE initiated Deregistration procedure: a) If the UE initiates Mobility Registration Update procedure: 0) The UE includes an Unavailability Type to describe the cause of unavailability (e.g. the unavailability caused by NR satellite access discontinuous coverage), the Start of the Unavailability Period if known and the Unavailability Period Duration (if known). 1) If the UE did not include a Start of Unavailability Period, the AMF considers implicitly the Start of Unavailability Period to be the time at which it has received the Registration Request message from the UE. If the UE included a Start of Unavailability Period, the Start of Unavailability Period indicates the time at which the UE determines it expects to be unavailable, i.e. time until which the UE determines it is available. 2) The AMF may determine, if not provided by the UE, or update the Unavailability Period Duration and/or the Start of Unavailability Period. If the AMF knows an Unavailability Period Duration and/or the Start of Unavailability Period (e.g. based on the Unavailability Type and other information available to the AMF as described in clause 5.4.13.3), and the UE did not include an Unavailability Period Duration and/or the Start of Unavailability Period or the UE included an Unavailability Period Duration and/or the Start of Unavailability Period different to the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF, the AMF may use either the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF or the Unavailability Period Duration and/or the Start of Unavailability Period from the UE as the Unavailability Period Duration and/or the Start of Unavailability Period. The AMF should include the Unavailability Period Duration and/or the Start of Unavailability Period known to the AMF in the Registration Accept. How the UE treats the AMF provided Unavailability Period Duration and/or the Start of Unavailability Period is up to UE implementation e.g. to help to determine when to return to coverage after a discontinuous coverage period, whether to listen to paging in eDRX, not to initiate any NAS signalling (including Service Request for MO data) within the discontinuous coverage period in case of any UL signalling/data request or the UE may deactivate its Access Stratum functions for NR satellite access in order to optimise power consumption until coverage returns, etc. 3) The AMF indicates to the UE in the Registration Accept whether the UE is not required to perform a Registration procedure when the unavailability period has ended. 4) The AMF may take the Unavailability Period Duration (if available) and Start of Unavailability Period into account when determining Periodic Registration Update timer value. The AMF may provide a Periodic Registration Update time longer than or equal to the combination of the Unavailability Period Duration and Start of Unavailability Period to avoid interfering with the UE dealing with the event that causes the unavailability; 5) The AMF stores the information that the UE is unavailable at the Start of Unavailability Period in UE context, and considers the UE is unreachable (i.e. clear the PPF in AMF) from then until the UE enters CM-CONNECTED state; 6) While the UE is unreachable, all high latency communication solutions (see clause 5.31.8) apply if supported in the network, e.g. extended data buffering, downlink data buffering status report, etc; and 7) If there is "Loss of Connectivity" event subscription for the UE by AF, the AMF at the start of Unavailability Period considers the remaining time in the Unavailability Period (if available) when constructing the "Loss of Connectivity" event report towards the NEF and the remaining time in the Unavailability Period is reported to the respective subscribed AF. b) If the UE initiates UE-initiated Deregistration procedure: 0) The UE includes Unavailability Period Duration (if known). 1) If there is "Loss of Connectivity" event subscription for the UE by AF, the AMF considers the remaining time in the Unavailability Period when constructing the "Loss of Connectivity" event report towards the NEF and the Unavailability Period is reported to the respective subscribed AF; Unless the AMF indicated that the UE is not required to perform a Registration procedure when the unavailability period has ended, then once the event which makes the UE unavailable is completed in the UE, the UE triggers a Registration procedure. If the event which makes the UE unavailable is delayed to a future time or cancelled in the UE or unavailability period deviates from negotiated value, the UE triggers Registration procedure. The UE may also trigger a Registration procedure before the Unavailability Period has started for other reasons. Depending on the UE state, the Registration procedure can be Initial Registration procedure or Mobility Registration Update procedure. While the UE is in 5GS and if the UE determines that an upcoming loss of coverage no longer applies or determines a new Start of Unavailability Period or Unavailability Period Duration related to the upcoming loss of coverage, the UE sends a new Mobility Registration Update Request to the AMF to update the Start of Unavailability Period and/or Unavailability Period Duration. The UE and the AMF re-negotiate unavailability at every Registration procedure, if it is required. If Start of Unavailability Period and/or Unavailability Period Duration is not included in a Registration procedure any pending unavailability configuration stored in the UE context at AMF is discarded. If the UE moves to EPS, the UE performs Attach or Tracking Area update procedure depending on the interworking mechanisms defined in clause 5.17.2. For discontinuous coverage in E-UTRAN satellite access in EPS, the "Unavailability Period" is also supported (see clause 4.13.8.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]). NOTE 2: In this release of specification there is no transfer of "unavailability period" between AMF and MME and vice versa. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.1.4 |
1,967 | 9.9.2.7 NAS security parameters to E-UTRA | The purpose of the NAS security parameters to E-UTRA information element is to provide the UE with parameters that enable the UE to create a mapped EPS security context and take this context into use after inter-system handover to S1 mode. The NAS security parameters to E-UTRA information element is coded as shown in figure 9.9.2.7.1 and table 9.9.2.7.1. The NAS security parameters to E-UTRA is a type 3 information element with a length of 7 octets. The value part of the NAS security parameters to E-UTRA information element is included in specific information elements within some RRC messages sent to the UE; see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]. For these cases the coding of the information element identifier and length information is defined in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]. Figure 9.9.2.7.1: NAS security parameters to E-UTRA information element Table 9.9.2.7.1: NAS security parameters to E-UTRA information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.2.7 |
1,968 | 5.9.3 Permanent Equipment Identifier | A Permanent Equipment Identifier (PEI) is defined for the 3GPP UE accessing the 5G System. The PEI can assume different formats for different UE types and use cases. The UE shall present the PEI to the network together with an indication of the PEI format being used. If the UE supports at least one 3GPP access technology (i.e. NG-RAN, E-UTRAN, UTRAN or GERAN), the UE must be allocated a PEI in the IMEI or IMEISV format. If a UE has registered with a network by using a network subscription and a PEI of the UE, then the UE shall keep the PEI to be used with the network subscription and shall not use that PEI with another network subscription while the UE is in registered state in the network. In the scope of this release, the PEI may be one of the following: - for UEs that support at least one 3GPP access technology, an IMEI or IMEISV, as defined in TS 23.003[ Numbering, addressing and identification ] [19]; - PEI used in the case of W-5GAN access as further specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. - for UEs not supporting any 3GPP access technologies, the IEEE Extended Unique Identifier EUI-64 [113] of the access technology the UE uses to connect to the 5GC. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.3 |
1,969 | 5.7.10.7 Actions for the successful PSCell change or addition report determination | The UE shall for the PSCell: 1> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the timer T304, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG; or 1> if sn-InitiatedPSCellChange is configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync; or 1> if sn-InitiatedPSCellChange is configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the source PSCell before executing the last reconfiguration with sync: 1> if sn-InitiatedPSCellChange is not configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync; or 1> if sn-InitiatedPSCellChange is not configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG and if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured by the PCell before executing the last reconfiguration with sync: 2> clear the information included in VarSuccessPSCell-Report, if any; 2> store the successful PSCell change or addition information in VarSuccessPSCell-Report and determine the content in VarSuccessPSCell-Report as follows: 3> if the UE is not in SNPN access mode, set the plmn-IdentityList to include the list of EPLMNs stored by the UE (i.e., includes the RPLMN); 3> else if the UE is in SNPN access mode, set the snpn-IdentityList to include the list of equivalent SNPNs stored by the UE (i.e., includes the registered SNPN), if available; 3> set the pCellId to the global cell identity and tracking area code, if available, of the PCell; 3> for the source PSCell (if available) in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied: 4> set the sourcePSCellId in sourcePSCellInfo to the global cell identity and tracking area code, of the source PSCell; 4> set the sourcePSCellMeas in sourcePSCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the source PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; 4> set the rsIndexResults in sourceCellMeas to include all the available SSB and CSI-RS measurement quantities of the source PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG; 3> for the target PSCell indicated in the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync: 4> set the targetPSCellID in targetPSCellInfo to the global cell identity and tracking area code, if available, and otherwise to the physical cell identity and carrier frequency of the target PSCell; 4> set the targetPSCellMeas in targetPSCellInfo to include the cell level RSRP, RSRQ and the available SINR, of the target PSCell based on the available SSB and CSI-RS measurements collected up to the moment the UE successfully completed the random access procedure for the SCG; 4> set the rsIndexResults in targetCellMeas to include all the available SSB and CSI-RS measurement quantities of the target PSCell collected up to the moment the UE successfully completed the random access procedure for the SCG; 4> if the last applied RRCReconfiguration message for the SCG including reconfigurationWithSync was included in the stored condRRCReconfig: 5> set the timeSinceCPAC-Reconfig to the time elapsed between the initiation of the execution of conditional reconfiguration for the target PSCell and the reception of the last conditionalReconfiguration for the SCG including the condRRCReconfig of the target PSCell; 3> if the ratio between the value of the elapsed time of the timer T304 and the configured value of the T304 timer, included in the last applied RRCReconfiguration message for the SCG including the reconfigurationWithSync, is greater than thresholdPercentageT304-SCG if included in the successPSCell-Config received before executing the last reconfiguration with sync for the SCG: 4> set t304-cause in spr-Cause to true; 4> set the ra-InformationCommon to include the random-access related information associated to the random access procedure in the target PSCell, as specified in clause 5.7.10.5; 3> if the ratio between the value of the elapsed time of the timer T310 and the configured value of the timer T310, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync for the SCG, is greater than thresholdPercentageT310-SCG included in the successPSCell-Config if configured before executing the last reconfiguration with sync: 4> set t310-cause in spr-Cause to true; 3> if the T312 associated to the measurement identity of the target PSCell was running at the time of initiating the execution of the reconfiguration with sync procedure for the SCG and if the ratio between the value of the elapsed time of the timer T312 and the configured value of the timer T312, configured while the UE was connected to the source PSCell before executing the last reconfiguration with sync, is greater than thresholdPercentageT312-SCG included in the successPSCell-Config if configured before executing the last reconfiguration with sync: 4> set t312-cause in spr-Cause to true; 3> if sn-InitiatedPSCellChange is configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG: 4> consider all measObjectNR configured by the the source PSCell; 3> else: 4> consider all measObjectNR configured by the the PCell; 3> for each of the measObjectNR: 4> if measurements are available for the measObjectNR: 5> if the SS/PBCH block-based measurement quantities are available: 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PCell or target PCell, ordered such that the cell with highest SS/PBCH block RSRP is listed first if SS/PBCH block RSRP measurement results are available, otherwise the cell with highest SS/PBCH block RSRQ is listed first if SS/PBCH block RSRQ measurement results are available, otherwise the cell with highest SS/PBCH block SINR is listed first, based on the available SS/PBCH block based measurements collected up to the moment the UE successfully completed the random access procedure; 6> for each neighbour cell included, include the optional fields that are available (including the CSI-RS based measurement quantities, if available); 5> if the CSI-RS measurement quantities are available for the cells not yet included in measResultListNR in measResultNeighCells: 6> include in the measResultListNR in measResultNeighCells all the available measurement quantities of the best measured cells, other than the source PCell and target PCell, ordered such that the cell with highest CSI-RS RSRP is listed first if CSI-RS RSRP measurement results are available, otherwise the cell with highest CSI-RS RSRQ is listed first if CSI-RS RSRQ measurement results are available, otherwise the cell with highest CSI-RS SINR is listed first, based on the available CSI-RS based measurements collected up to the moment the UE successfully completed the random access procedure; 6> for each neighbour cell included, include the optional fields that are available; 3> for each of the neighbour cells included in measResultNeighCells: 4> if the cell was a candidate target cell included in the condRRCReconfig within the conditionalReconfiguration, in which the last RRCReconfiguration message for the SCG including reconfigurationWithSync was applied: 5> set the choCandidate to true in measResultNR; 3> include sn-InitiatedPSCellChange if sn-InitiatedPSCellChange is included in the RRCReconfiguration including the applied RRCReconfiguration message with reconfigurationWithSync for the SCG; 3> if sn-InitiatedPSCellChange is configured in the RRCReconfiguration including the last applied RRCReconfiguration with reconfigurationWithSync for the SCG: 4> if available, set the locationInfo as in 5.3.3.7 7 according to the otherConfig associated with the source PSCell; 3> else: 4> if available, set the locationInfo as in 5.3.3.7 7 according to the otherConfig associated with the PCell; 1> release successPSCell-Config configured by the source PSCell if available and thresholdPercentageT304 if configured by the target PSCell. The UE may discard the successful PSCell change or addition information, i.e., release the UE variable VarSuccessPSCell-Report, 48 hours after the last successful PSCell change or addition information is added to the VarSuccessPSCell-Report or upon detaching from the network. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.10.7 |
1,970 | 5.6H PMCH bandwidth for LTE based 5G terrestrial broadcast | Requirements in the present document are specified for the bandwidths listed in Table 5.6H-1. Table 5.6H-1: Transmission bandwidth configuration NRB for 5G terrestrial broadcast The LTE based 5G terrestrial broadcast network operates on 6, 7, and 8 MHz channels and the requirements in this specification apply according to configuration by the higher layer parameter pmch-Bandwidth (see TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) in the MBSFN area (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7]). Note: Upon configuration of the PMCH bandwidth, the UE is assumed to configure its baseband filtering to 10 MHz. This assumption is not intended to restrict the UE implementation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.6H |
1,971 | 4.2.11.4a Hierarchical NSACF-based Number of PDU Sessions per network slice availability check and update procedure | Figure 4.2.11.4a-1: Hierarchical NSAC-based number of PDU Sessions per network slice availability check and update procedure For an S-NSSAI subject to counting of the number of PDU sessions, if hierarchical NSACF architecture is deployed in the network the enforcement of maximum number of PDU Session established for an S-NSSAI is performed as follow: 1-2. Same as for steps 1-2 defined in clause 4.2.11.4. 3. The NSACF performs NSAC for the indicated S-NSSAI. If the PDU session ID entry update at the NSACF is possible, e.g. create a new entry associated with the received NSAC request for increase case, the same action as for step 3 defined in clause 4.2.11.4 is executed. Steps 4-8 are skipped. If the PDU session ID entry at the NSACF is not possible, i.e. by admitting the PDU session the local maximum PDU session number is exceeded, the NSACF delegates the request to the Primary NSACF for an updated local maximum PDU sessions from the Primary NSACF. 4. If the Primary NSACF has not been discovered before, the NSACF discovers and selects the Primary NSACF, which manages the global NSAC service area as for clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 5. The NSACF invokes Nnsacf_NSAC_NumOfPDUsUpdate request to the Primary NSACF. The request message includes the S-NSSAI. 6. The Primary NSACF checks the global maximum PDU session number and determines whether to accept or reject the request to update local maximum PDU session number from NSACF. NOTE: When NSACF sends a delegation request to the Primary NSACF, the Primary NSACF either increases local maximum number at NSACF or rejects the NSAC request. 7. The Primary NSACF returns the Nnsacf_NSAC_NumOfPDUsUpdate response. The response includes a new allocated local maximum PDU sessions number or an indication to reject the request to update local maximum PDU session number. 8. If the primary NSACF provides an updated local maximum number, the NSACF replaces the local maximum PDU session number with the received local maximum PDU sessions number value. The same action is executed as for step 3 in clause 4.2.11.4 based on the updated configured value. 9. Same as for step 4 of clause 4.2.11.4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.4a |
1,972 | 5.17.7.2.2 Routing | The source RAN node sends a message to its core network node including the source and destination addresses. MME uses the destination address to route the message to the correct AMF via N26 interface. AMF uses the destination address to route the message to the correct MME via N26 interface. The AMF connected to the destination RAN node decides which RAN node to send the message to, based on the destination address. The MME connected to the destination RAN node decides which RAN node to send the message to, based on the destination address. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.7.2.2 |
1,973 | 6.11A Discovery signal | A discovery signal occasion for a cell consists of a period with a duration of - one to five consecutive subframes for frame structure type 1 - two to five consecutive subframes for frame structure type 2 - 12 OFDM symbols within one non-empty subframe for frame structure type 3 where the UE in the downlink subframes may assume presence of a discovery signal consisting of - cell-specific reference signals on antenna port 0 in all downlink subframes and in DwPTS of all special subframes in the period for frame structure type 1 and 2 - cell specific reference signals on antenna port 0 when higher layer parameters indicate only one configured antenna port for cell specific reference signals for a serving cell using frame structure type 3 - cell specific reference signals on antenna port 0 and antenna port 1 when higher layer parameters indicate at least two configured antenna ports for cell specific reference signals for a serving cell using frame structure type 3 - cell specific reference signals on antenna port 0 and antenna port 1 when higher layer configured parameter presenceAntennaPort1 is signalled to be 1, for a neighbour cell when using frame structure type 3 - primary synchronization signal in the first subframe of the period for frame structure types 1 and 3 or the second subframe of the period for frame structure type 2, - secondary synchronization signal in the first subframe of the period, and - non-zero-power CSI reference signals in zero or more subframes in the period. The configuration of non-zero-power CSI reference signals part of the discovery signal is obtained as described in clause 6.10.5.2 For frame structures 1 and 2 the UE may assume a discovery signal occasion once every dmtc-Periodicity. For frame structure type 3, the UE may assume a discovery signal occasion may occur in any subframe within the discovery signals measurement timing configuration in clause 5.5.2.10 of [9]. For frame structure type 3, simultaneous transmission of a discovery signal and PDSCH/PDCCH/EPDCCH may occur in subframes 0 and 5 only. For frame structure type 3, the UE may assume that a discovery signal occasion occurs in the first subframe containing a primary synchronization signal, secondary synchronization signal and cell-specific reference signals within the discovery measurement timing configuration in clause 5.5.2.10 of [9]. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.11A |
1,974 | 4.1.3.1.2 Substates of state GMM-DEREGISTERED | The GMM-DEREGISTERED state is subdivided into several substates as explained below. The substates pertain to the whole MS (ME alone if no SIM/USIM is inserted, or ME plus SIM/USIM). The selection of the appropriate substate depends on the GPRS update status, see subclause 4.1.3.2, and on the selected cell. 4.1.3.1.2.1 GMM-DEREGISTERED.NORMAL-SERVICE Valid subscriber data is available, a suitable cell has been found and the PLMN or LA is not in the forbidden list. In this state, a request for GPRS attach is performed using the stored temporary mobile subscriber identity for GPRS (P-TMSI), routing area identification (RAI) and GPRS ciphering key sequence number in case of GU1. If the GPRS update status is GU2, the IMSI shall be used to attach for GPRS services. 4.1.3.1.2.2 GMM-DEREGISTERED.LIMITED-SERVICE Valid subscriber data is available, and a cell is selected, which is known not to be able to provide normal service. 4.1.3.1.2.3 GMM-DEREGISTERED.ATTACH-NEEDED Valid subscriber data is available and for some reason a GPRS attach must be performed as soon as possible. This state is usually of no duration, but can last, e.g. due to access class control (see subclause 4.1.1.2.1). 4.1.3.1.2.4 GMM-DEREGISTERED.ATTEMPTING-TO-ATTACH A cell is selected, a previous GPRS attach was rejected or failed due to a missing response from the network. The execution of further attach procedures depends on the GPRS attach attempt counter. No GMM procedure except GPRS attach shall be initiated by the MS in this substate. 4.1.3.1.2.5 GMM-DEREGISTERED.NO-IMSI No valid subscriber data is available (no SIM/USIM, or the SIM/USIM is not considered valid by the ME) and a cell has been selected. 4.1.3.1.2.6 GMM-DEREGISTERED.NO-CELL-AVAILABLE No cell can be selected. This substate is entered after a first intensive search failed (substate PLMN SEARCH). Cells are searched for at a low rhythm. No services are offered. 4.1.3.1.2.7 GMM-DEREGISTERED.PLMN-SEARCH The mobile station is searching for PLMNs. This substate is left either when a cell has been selected (the new substate is NORMAL-SERVICE or LIMITED-SERVICE) or when it has been concluded that no cell is available at the moment (the new substate is NO-CELL-AVAILABLE). 4.1.3.1.2.8 GMM-DEREGISTERED.SUSPENDED (A/Gb mode only) The MS shall enter this substate when entering dedicated mode and the MS limitations make it unable to communicate on GPRS channels. The MS shall leave this substate when leaving dedicated mode. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.3.1.2 |
1,975 | 5.3.5.12a.1.2 IP Address Addition/Modification | The IAB-MT shall: 1> for each iab-IP-AddressIndex value included in the iab-IP-AddressToAddModList that is not part of the current IAB-MT configuration: 2> add the IP address indicated in iab-IP-Address, corresponding to the iab-IP-AddressIndex. 2> if added IP address is iPv4-Address: 3> if iab-IP-Usage is set to f1-C: 4> store the received IPv4 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to f1-U: 4> store the received IPv4 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to non-F1: 4> store the received IPv4 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else: 4> store the received IPv4 address for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 2> else if iPv6-Address is included: 3> if iab-IP-Usage is set to f1-C: 4> store the received IPv6 address for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to f1-U: 4> store the received IPv6 address for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to non-F1: 4> store the received IPv6 address for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else: 4> store the received IPv6 address for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 2> else if iPv6-Prefix is included in iab-IP-AddressToAddModList: 3> if iab-IP-Usage is set to f1-C: 4> store the received IPv6 address prefix for F1-C traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to f1-U: 4> store the received IPv6 address prefix for F1-U traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else if iab-IP-Usage is set to non-F1: 4> store the received IPv6 address prefix for non-F1 traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 3> else: 4> store the received IPv6 address prefix for all traffic together with the IAB-donor-DU BAP address corresponding to the iab-IP-AddressIndex. 1> for each iab-IP-AddressIndex value included in the iab-IP-AddressToAddModList that is part of the current IAB-MT configuration: 2> modify the IP address configuration(s) in accordance with the IAB-IP-AddressConfiguration corresponding to the iab-IP-AddressIndex. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.12a.1.2 |
1,976 | 4.5.3 Purge of subscriber data in AMF | An AMF may, as an implementation option, purge the subscriber data and MM context of a UE after the implicit or explicit Deregistration of the UE. In this case, the AMF shall unsubscribe and deregister from the UDM, where UDM may further do corresponding operation from UDR, by the means of following "Purge of subscriber data in AMF" procedure. Figure 4.5.3-1: Purge of Subscriber Data in AMF 1. After purging the subscriber data and MM context of a deregistered UE, the AMF unsubscribes to changes to subscription data using Nudm_SDM_Unsubscribe request operation (see clause 5.2.3.3.4), for the data the AMF has previously subscribed (see clause 4.2.2.2.2, step 14b). The UDM unsubscribes the AMF from the data indicated. The UDM may unsubscribe to changes to subscription data from UDR by using Nudr_DM_Unsubscribe for the data the UDM has previously subscribed (see clause 4.2.2.2.2, step 14b). 2. The UDM sends a response back using Nudm_SDM_Unsubscribe response operation. 3. The AMF deregisters from UDM using Nudm_UECM_Deregistration request (SUPI, NF ID, Access Type) operation (see clause 5.2.3.2.3). The UDM may update UE context in UDR by Nudr_DM_Update (SUPI, Subscription Data). 4. The UDM sets the UE Purged flag associated with the Access Type and acknowledges with a Nudm_UECM_Deregistration response operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.5.3 |
1,977 | 8.12.1 Standalone IAB integration | A high-level flow chart for SA-based IAB integration is shown in the Figure 8.12.1-1: Figure 8.12.1-1: The integration procedure for IAB-node in SA Phase 1: IAB-MT setup. In this phase, the IAB-MT of the new IAB-node (e.g. IAB-node 2 in Figure 8.12.1-1) connects to the network in the same way as a UE, by performing RRC connection setup procedure with IAB-donor-CU, authentication with the core network, IAB-node 2-related context management, IAB-node 2βs access traffic-related radio bearer configuration at the RAN side (SRBs and optionally DRBs), and, optionally, OAM connectivity establishment by using the IAB-MTβs PDU session. The IAB-node can select the parent node for access based on an over-the-air indication from potential parent node IAB-DU (transmitted in SIB1). To indicate its IAB capability, the IAB-MT includes the IAB-node indication in RRCSetupComplete message, to assist the IAB-donor to select an AMF supporting IAB. NOTE: The signalling flow for UE initial access procedure as shown in Figure 8.1-1/Figure 8.9.1-1 is used for the setup of the IAB-MT. Phase 2-1: BH RLC channel establishment. During the bootstrapping procedure, one default BH RLC channel for non-UP traffic e.g. carrying F1-C traffic/non-F1 traffic to and from the IAB-node 2 in the integration phase, is established. This may require the setup of a new BH RLC channel or modification of an existing BH RLC channel between IAB-node 1 and IAB-donor-DU. The IAB-donor-CU may establish additional (non-default) BH RLC channels. This phase also includes configuring the BAP Address of the IAB-node 2 and default BAP Routing ID for the upstream direction. NOTE: If the OAM connectivity is supported via backhaul IP layer by implementation, one or more BH RLC channels used for OAM traffic can also be established. Phase 2-2: Routing update. In this phase, the BAP sublayer is updated to support routing between the new IAB-node 2 and the IAB-donor-DU. For the downstream direction, the IAB-donor-CU initiates F1AP procedure to configure the IAB-donor-DU with the mapping from IP header field(s) to the BAP Routing ID related to IAB-node 2. The routing tables are updated on all ancestor IAB-nodes (e.g. IAB-node 1 in Figure 8.12.1-1) and on the IAB-donor-DU, with routing entries for the new BAP Routing ID(s). This phase may also include the IP address allocation procedure for IAB-node 2. IAB-node 2 may request one or more IP addresses from the IAB-donor-CU via RRC. The IAB-donor-CU may send the IP address(es) to the IAB-node 2 via RRC. The IAB-donor-CU may obtain the IP address(es) from the IAB-donor-DU via F1-AP or by other means (e.g. OAM, DHCP). IP address allocation procedure may occur at any time after RRC connection has been established. Phase 3: IAB-DU part setup. In this phase, the IAB-DU of IAB-node 2 is configured via OAM. The IAB-DU of IAB-node 2 initiates the TNL establishment, and F1 setup (as defined in clause 8.5) with the IAB-donor-CU using the allocated IP address(es). The IAB-donor-CU discovers collocation of IAB-MT and IAB-DU from the IAB-nodeβs BAP Address included in the F1 SETUP REQUEST message. After the F1 is set up, the IAB-node 2 can start serving the UEs. NOTE: The IAB-DU can discover the IAB-donor-CUβs IP address in the same manner as a non-IAB gNB-DU. NOTE: If the IAB-node establishes NR-DC before the establishment of F1-C connection, the MN decides whether the MN or the SN becomes the F1-terminating IAB-donor. In case it decides that the SN becomes the F1-terminating IAB-donor, it notifies the SN via Xn. The IAB-node can implicitly derive whether the MN or the SN is the F1-terminating IAB-donor, e.g., based on the entity which provides the default BAP configuration. NOTE: For OAM-based IAB-donor selection, if the IAB-node establishes NR-DC before the establishment of F1-C connection, the IAB-node indicates the F1-terminating IAB-donor by signaling its IP address(es) to this IAB-donor via RRC signaling. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.12.1 |
1,978 | 8.117 Paging and Service Information | The Paging and Service Information IE is used to carry per bearer paging and service information. It is coded as shown in Figure 8.117-1. Figure 8.117-1: Paging and Service Information The EBI field in octet 5 shall contain the value indicating the EPS Bearer ID for which the Paging and Service Information is provided. The EBI field shall be encoded as the EBI field in the EPS Bearer ID (EBI) IE type (see clause 8.8). The PPI flag in octet 6 indicates whether the Paging Policy Indication value in octet 'm' shall be present. If PPI is set to '1', then the Paging Policy Indication value shall be present. If PPI is set to '0', then octet 'm' shall not be present. The Paging Policy Indication value, in octet 'm', shall be encoded as the DSCP in TOS (IPv4) or TC (IPv6) information received in the IP payload of the GTP-U packet from the PGW (see IETF RFC 2474 [65]). | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.117 |
1,979 | 6.3.5E.3.1 Minimum requirement | The category M1 and M2 TDD and FD-FDD UEs shall meet the requirements specified in Table 6.3.5E.3.1-0 for aggregate power control over the power range bounded by the minimum output power as defined in subclause 6.3.2, the maximum output power as defined in subclause 6.2.2E, and the requirements for configured transmitted power are specified in subclause 6.2.5. The category M1 and M2 HD-FDD UEs and for continuous uplink transmissions of duration β€ 64 ms, shall meet the requirements specified in Table 6.3.5E.3.1-0 for aggregate power control over the power range bounded by the minimum output power as defined in subclause 6.3.2, the maximum output power as defined in subclause 6.2.2E, and the requirements for configured transmitted power are specified in subclause 6.2.5. Table 6.3.5E.3.1-0: Aggregate power control tolerance The category M1 and M2 HD-FDD UE and for continuous uplink transmissions of duration > 64 ms shall meet the requirements specified in Table 6.3.5E.3.1-1 for aggregate power control over the power range bounded by the minimum output power as defined in subclause 6.3.2 and the maximum output power as defined in subclause 6.2.2E. Table 6.3.5E.3.1-1: Aggregate power control tolerance | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5E.3.1 |
1,980 | W.4.2 Protection of the traffic transmission | The traffic may require some protection depending on the sensitivity of the data being transmitted. For example, it is possible that the data being transmitted is actually protected by the application layer security and hence might not require additional protection. However, the protection in service layer is independent of application layer security. The service protection description in the Service Announcement implies the protection requirement of the traffic transmission in case the security protection is provided in service layer. It may include indications for which security procedures are supported by the network: control-plane procedure or user-plane procedure. If the support for user-plane procedure is indicated then the description should include also an indication of whether GBA or/and AKMA is supported. NOTE: If the security protection in service layer is not required, the service protection description is not present in the Service Announcement. If the UE does not support the network selected MBS security procedure at the service layer, then the UE may obtain the service via individual delivery method. The actual method of protection may vary depending on the type of data being transmitted, e.g. media streaming application or file download. Clause 6.6.2 and clause 6.6.3 in TS 33.246[ 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) ] [102] apply to the protection of streaming data and protection of download data, respectively. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | W.4.2 |
1,981 | β NR-UE-Variables | This ASN.1 segment is the start of the NR UE variable definitions. -- ASN1START -- NR-UE-VARIABLES-START NR-UE-Variables DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS AreaConfiguration-r17, ARFCN-ValueNR, CellIdentity, EUTRA-PhysCellId, maxCEFReport-r17, MeasId, MeasIdToAddModList, MeasIdleCarrierEUTRA-r16, MeasIdleCarrierNR-r16, MeasResultIdleEUTRA-r16, MeasResultIdleNR-r16, MeasObjectToAddModList, MeasConfigAppLayerId-r17, MeasConfigAppLayer-r17, maxNrofAppLayerMeas-r17, AppLayerIdleInactiveConfig-r18, PhysCellId, RNTI-Value, ReportConfigToAddModList, RSRP-Range, SL-MeasId-r16, SL-MeasIdList-r16, SL-MeasObjectList-r16, SL-ReportConfigList-r16, SL-QuantityConfig-r16, Tx-PoolMeasList-r16, QuantityConfig, maxNrofCellMeas, maxNrofMeasId, maxFreqIdle-r16, PhysCellIdUTRA-FDD-r16, ValidityAreaList-r16, CondReconfigToAddModList-r16, ConnEstFailReport-r16, LoggingDuration-r16, LoggingInterval-r16, LogMeasInfoList-r16, LogMeasInfo-r16, RA-Report-r16, RLF-Report-r16, TraceReference-r16, WLAN-Identifiers-r16, WLAN-NameList-r16, BT-NameList-r16, PLMN-Identity, maxNrofRelayMeas-r17, maxPLMN, RA-ReportList-r16, VisitedCellInfoList-r16, AbsoluteTimeInfo-r16, LoggedEventTriggerConfig-r16, LoggedPeriodicalReportConfig-r16, Sensor-NameList-r16, SL-SourceIdentity-r17, SuccessHO-Report-r17, PLMN-IdentityList2-r16, AreaConfiguration-r16, maxNrofSL-MeasId-r16, maxNrofFreqSL-r16, maxNrofCLI-RSSI-Resources-r16, maxNrofCLI-SRS-Resources-r16, RSSI-ResourceId-r16, SRS-ResourceId, VisitedPSCellInfoList-r17, SuccessPSCell-Report-r18, maxNPN-r16, SNPN-ConfigIDList-r18, AreaConfiguration-v1800, NID-r16, LTM-Candidate-r18, LTM-CSI-ResourceConfig-r18, SK-CounterConfiguration-r18, ReferenceConfiguration-r18, maxNrofLTM-Configs-r18, maxNrofLTM-CSI-ResourceConfigurations-r18, maxSecurityCellSet-r18 FROM NR-RRC-Definitions; -- NR-UE-VARIABLES-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,982 | 5.2.7.2.5 Nnrf_NFManagement_NFStatusSubscribe service operation | Service Operation name: Nnrf_NFManagement_NFStatusSubscribe. Description: Consumer can subscribe to be notified of the following: - Newly registered NF along with its NF services. - Updated NF profile. - Deregistered NF. Inputs, Required: callback URI. Inputs, Optional: - PLMN ID of the target NF/NF service, in the case of the subscription to the status of NF/NF service instance(s) in home PLMN from the serving PLMN, or PLMN ID and NID in the case of SNPN (see clause 5.30.2.9.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server. - Validity Time, in case to indicate the time instant after which the subscription becomes invalid. - For updated NF profile subscription, conditions that trigger a notification from NRF. Includes monitored attributes in the NF profile (changes trigger a notification) or unmonitored attributes in the NF profile (changes do not trigger a notification) - The following parameters are mutually exclusive: - NF Type (if NF status of a specific NF type is to be monitored). - NF Instance ID or NF Instance ID list (if NF status of a specific NF instance or a list of NF instance is to be monitored). - NF Service name (if NF status for NF which exposes a given NF service is to be monitored). - NF Set (if NF status of a set of NF Instances belonging to a certain NF Set is to be monitored). - NF Service Set (if the status of a set of NF Service Instances belonging to a certain NF Service Set is to be monitored). - NF Group (if the NF status of NF Instances identified by a NF (UDM, AUSF, PCF, BSF, CHF, HSS or UDR) Group Identity is to be monitored). - SCP Domain (if the status of NF or SCP instances belonging to a certain SCP domain is to be monitored). - For the UPF Management defined in clause 4.17.6: UPF Provisioning Information as defined in that clause. - For AMF, Consumer may include list of GUAMI(s), or AMF Set or AMF Region, or TAIs. - For SMF, Consumer may include list of TAIs. - S-NSSAI(s) and the associated NSI ID(s) (if available). - For NWDAF, Consumer may include: - Analytics ID(s) (possibly per service). - TAI(s). - NF Set ID, NF Type of NF data sources. - Analytics aggregation capability and/or Analytics metadata provisioning capability. - ML Model Accuracy checking capability. - Analytics Accuracy checking capability. - Roaming exchange capability. - For NWDAF containing MTLF, Consumer may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). - For NWDAF containing MTLF with Federated Learning (FL) capability, Consumer may include FL capability type (i.e. FL client, FL server, if available), Time Period of Interest, if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]). Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - For ADRF, Consumer may include: - Data and analytics storage and retrieval capability. - ML model storage and retrieval capability. - For NEF, Consumer may include Event ID(s) provided by AF. - For DCCF, Consumer may include: - TAI(s). - NF type of the NF data sources. - NF Set ID of the NF data sources. - Support for relocation of data subscription. Details about NWDAF discovery and selection are described in clause 6.3.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Outputs, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Validity Time. Outputs, Optional: None. NOTE: Alternatively, other means such as OA&M can also be used to subscribe for NF status. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7.2.5 |
1,983 | 5.4.1 Carrier aggregation | In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities: - A UE with single timing advance capability for CA can simultaneously receive and/or transmit on multiple CCs corresponding to multiple serving cells sharing the same timing advance (multiple serving cells grouped in one TAG); - A UE with multiple timing advance capability for CA can simultaneously receive and/or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped in multiple TAGs). NG-RAN ensures that each TAG contains at least one serving cell; - A non-CA capable UE can receive on a single CC and transmit on a single CC corresponding to one serving cell only (one serving cell in one TAG). CA is supported for both contiguous and non-contiguous CCs. When CA is deployed frame timing and SFN are aligned across cells that can be aggregated, or an offset in multiples of slots between the PCell/PSCell and an SCell is configured to the UE. The maximum number of configured CCs for a UE is 16 for DL and 16 for UL. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.4.1 |
1,984 | 5.2.8.2.9 Nsmf_PDUSession_StatusNotify service operation | Service operation name: Nsmf_PDUSession_StatusNotify. Description: This service operation is used by the SMF to notify its consumers about the status of a PDU Session (e.g. PDU Session is released due to local reasons within the H-SMF, PDU Session handover to a different system or access type, triggering I-SMF reselection for the PDU Session). Input, Required: Status information. Input, Optional: Cause, Small Data Rate Control Status, APN Rate Control Status, target DNAI information. Output, Required: Result Indication. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.9 |
1,985 | 4.9.1 Architecture | A Network-Controlled Repeater node, referred to as NCR-node, is an RF repeater that enables wireless amplifying-and-forwarding functionality in NG-RAN. The NCR-node is capable of receiving and applying side control information from a gNB with additional functionality to support Network-Controlled Repeater. The NCR-node comprises an NCR-MT and an NCR-Fwd. The NCR-MT is an entity supporting a subset of the UE functionality that communicates with the gNB to receive side control information via a control link based on the NR Uu interface. The NCR-Fwd is the function performing amplifying-and-forwarding of signals between gNB and UE via the NCR-Fwd backhaul link and NCR-Fwd access link, respectively. The NCR-Fwd can support multiple beams towards the UE. The behaviour of the NCR-Fwd is controlled according to the side control information received from the gNB. The NCR-node is modelled as depicted in Figure 4.9.1-1. Figure 4.9.1-1: Conceptual model of network-controlled repeater. An NCR-MT establishes SRBs and, optionally, DRB(s) with a gNB. The establishment of DRB(s) can be used to transport OAM traffic. The signal that NCR-Fwd forwards is associated to the cell that the NCR-MT is connected to via the control link. Whether the NCR-Fwd can forward other signals is up to implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.9.1 |
1,986 | 4.4.2.1 Average number of active UEs on the DL per QCI | a) This measurement provides the average number of UEs that have DTCH data queued on the downlink. The measurement is split into subcounters per E-RAB QoS level (QCI). For an eNodeB serving one or more RNs, the measurement refers to the number of active UEs connected directly to the eNodeB, excluding RNs. The measurement is also applicable to RNs. b) SI c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form DRB.UEActiveDl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.2.1 |
1,987 | N.2.2 Redundant transmission on N3/N9 interfaces | If the user data redundancy is fulfilled by means of two duplicated N3 tunnels, the redundant packets will be transferred between UPF and RAN via two independent N3 tunnels, which are associated with a single PDU Session, over different transport layer path to enhance the reliability of service. Figure N.2.2-1: Redundant transmission with two N3 tunnels between the UPF and a single NG-RAN node In order to protect the redundant traffic on the N3 reference point, the current mechanism defined in clause 9.3 of the present document shall be reused. The added path for redundancy shall provide equal level of security compared to single path. In case two N9 tunnels are involved to fulfil the redundancy for one NG-RAN, the security mechanism defined in clause 9.9 shall be used for protecting the redundant data transferring via two N9 tunnels as described above. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | N.2.2 |
1,988 | 4.28.2.1 Control of access stratum time synchronization service without AF request | The control of 5G Access Stratum-based Time Distribution for a UE is performed by the AMF according to parameters retrieved in the Access and Mobility Subscription data. Figure 4.28.2.1-1: Subscription-based control of 5G access stratum-based time distribution 1. The UE performs the registration procedure as described in clause 4.2.2.2.2. The AMF retrieves the Access and Mobility Subscription data including the Access Stratum Time Synchronization Service Authorization. The Access and Mobility Subscription data may further include the Uu time synchronization error budget, one or more periods of start and stop times defining active times, a coverage area, clock quality detail level, and the acceptance criteria for the UE, as described in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. As part of this, the AMF shall, if supported, store the 5G access stratum time distribution indication (enable, disable), the Uu time synchronization error budget, clock quality detail level and clock quality acceptance criteria, and the UE reconnection indication in the UE context in AMF. 2. The AMF performs the control according to the subscription data as follows. If the AMF receives start and stop times then the AMF sends the message to the NG-RAN to enable or disable the 5G access stratum time distribution according to the expiry of start and stop times if the UE is in CM-CONNECTED state. If the UE is in CM-IDLE state when a Start time condition is met, then the AMF pages the UE and provides the 5G access stratum distribution indication to NG-RAN as part of the subsequent service request procedure initiated by the UE in the response to the paging. If the AMF received Time Synchronization Coverage Area information as part of the Access and Mobility Subscription data including the Access Stratum Time Synchronization Service Authorization, the AMF determines if the Coverage Area information shall trigger an activation or deactivation of the access stratum time distribution: - If the UE has moved inside the Coverage Area, then the AMF determines to enable access stratum time distribution for the UE. - If the UE has moved outside the Coverage Area, then the AMF determines to disable access stratum time distribution for the UE. The AMF determines whether the UE moves inside/outside of the Coverage Area specified in the clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] The AMF shall send the UE reconnection indication to the UE updating the UE configuration as defined in clause 4.2.2 or clause 4.2.4.2. 3. The AMF sends N2 message (UE Context Modification Request) to the NG-RAN. The AMF sends the 5G access stratum time distribution indication (enable, disable), the Uu time synchronization error budget, clock quality detail level and clock quality acceptance criteria when they are available, to NG-RAN during mobility registration, AM policy modification, Service Request, N2 Handover and Xn handover as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. The NG-RAN node shall, if supported, store the information in the UE Context. Based on this information, the NG-RAN node provides the 5GS access stratum time to the UE according to the Uu time synchronization error budget as provided by the TSCTSF (if supported by UE and NG-RAN) and NG-RAN provides timing synchronization status reports to the UE (as described in clause 4.15.9.5.2). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.28.2.1 |
1,989 | 5.16.4.7 PCC for Emergency Services | Dynamic PCC is used for UEs establishing emergency service and shall be used to manage IMS emergency sessions when an operator allows IMS emergency sessions. When establishing Emergency Services with a SMF, the PCF provides the SMF with the QoS parameters, including an ARP value reserved for the Emergency Services to prioritize the QoS Flows when performing admission control, as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The PCF rejects an IMS session established via the emergency PDU Session if the AF (i.e. P-CSCF) does not provide an emergency indication to the PCF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.4.7 |
1,990 | β LoggedMeasurementConfiguration | The LoggedMeasurementConfiguration message is used to perform logging of measurement results while in RRC_IDLE or RRC_INACTIVE. It is used to transfer the logged measurement configuration for network performance optimisation. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE LoggedMeasurementConfiguration message -- ASN1START -- TAG-LOGGEDMEASUREMENTCONFIGURATION-START LoggedMeasurementConfiguration-r16 ::= SEQUENCE { criticalExtensions CHOICE { loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } LoggedMeasurementConfiguration-r16-IEs ::= SEQUENCE { traceReference-r16 TraceReference-r16, traceRecordingSessionRef-r16 OCTET STRING (SIZE (2)), tce-Id-r16 OCTET STRING (SIZE (1)), absoluteTimeInfo-r16 AbsoluteTimeInfo-r16, areaConfiguration-r16 AreaConfiguration-r16 OPTIONAL, --Need R plmn-IdentityList-r16 PLMN-IdentityList2-r16 OPTIONAL, --Need R bt-NameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, --Need M wlan-NameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, --Need M sensor-NameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, --Need M loggingDuration-r16 LoggingDuration-r16, reportType CHOICE { periodical LoggedPeriodicalReportConfig-r16, eventTriggered LoggedEventTriggerConfig-r16, ... }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension LoggedMeasurementConfiguration-v1700-IEs OPTIONAL } LoggedMeasurementConfiguration-v1700-IEs ::= SEQUENCE { sigLoggedMeasType-r17 ENUMERATED {true} OPTIONAL, -- Need R earlyMeasIndication-r17 ENUMERATED {true} OPTIONAL, -- Need R areaConfiguration-r17 AreaConfiguration-r17 OPTIONAL, --Need R nonCriticalExtension LoggedMeasurementConfiguration-v1800-IEs OPTIONAL } LoggedMeasurementConfiguration-v1800-IEs ::= SEQUENCE { areaConfiguration-v1800 AreaConfiguration-v1800 OPTIONAL, --Need R nonCriticalExtension SEQUENCE {} OPTIONAL } LoggedPeriodicalReportConfig-r16 ::= SEQUENCE { loggingInterval-r16 LoggingInterval-r16, ... } LoggedEventTriggerConfig-r16 ::= SEQUENCE { eventType-r16 EventType-r16, loggingInterval-r16 LoggingInterval-r16, ... } EventType-r16 ::= CHOICE { outOfCoverage NULL, eventL1 SEQUENCE { l1-Threshold MeasTriggerQuantity, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, ... } -- TAG-LOGGEDMEASUREMENTCONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,991 | 5.2.2.6 Active indication | In the "mobile terminated call confirmed" state or in the "call received" state, the call control entity of the network shall, upon receipt of a CONNECT message: through connect the traffic channel (including the connection of an interworking function, if required), stop timers T310, T303 or T301 (if running); send a CONNECT ACKNOWLEDGE message to its peer entity at the mobile station of the called user; initiate procedures to send a CONNECT message towards the calling user and enter the "active" state. In the "connect request" state, the call control entity of the mobile station shall, upon receipt of a CONNECT ACKNOWLEDGE message: stop timer T313 and enter the "active" state. When timer T313 expires prior to the receipt of a CONNECT ACKNOWLEDGE message, the mobile station shall initiate clearing in accordance with subclause 5.4.3. Figure 5.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Call acceptance and active indication at mobile terminating call establishment | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.2.6 |
1,992 | 5.4.2 UE reachability in CM-CONNECTED | For a UE in CM-CONNECTED state: - the AMF knows the UE location on a serving (R)AN node granularity. - the NG-RAN notifies the AMF when UE becomes unreachable from RAN point of view. UE RAN reachability management is used by RAN for UEs in RRC_INACTIVE state, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. The location of a UE in RRC_INACTIVE state is known by the RAN on a RAN Notification area granularity. A UE in RRC_INACTIVE state is paged in cells of the RAN Notification area that is assigned to the UEs. The RAN Notification area can be a subset of cells configured in UE's Registration Area or all cells configured in the UE's Registration Area. UE in RRC_INACTIVE state performs RAN Notification Area Update when entering a cell that is not part of the RAN Notification area that is assigned to the UE. At transition into RRC_INACTIVE state RAN configures the UE with a periodic RAN Notification Area Update timer value and the timer is restarted in the UE with this initial timer value. After the expiry of the periodic RAN Notification Area Update timer in the UE, the UE in RRC_INACTIVE state performs periodic RAN Notification Area Update, as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. To aid the UE reachability management in the AMF, RAN uses a guard timer with a value longer than the RAN Notification Area Update timer value provided to the UE. Upon the expiry of the periodic RAN Notification Area Update guard timer in RAN, the RAN shall initiate the AN Release procedure as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The RAN may provide the elapsed time since RAN's last contact with the UE to AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.2 |
1,993 | 4.3.33 Support for Multi-USIM UE 4.3.33.1 General | A network and a Multi-USIM UE may support one or more of the following features for Multi-USIM UE operation: - Connection Release, as described in clause 4.3.33.2. - Paging Cause Indication for Voice Service, as described in clause 4.3.33.3. - Reject Paging Request, as described in clause 4.3.33.4. - Paging Timing Collision Control, as described in clause 4.3.33.5. - Paging Restriction, as described in clause 4.3.33.6. In the Attach procedure (as specified in clause 5.3.2.1), or in the Tracking Area Update procedure (as specified clause 5.3.3), when a Multi-USIM UE has more than one USIM active, supports and intends to use one or more Multi-USIM specific features, it indicates to the MME the corresponding Multi-USIM feature(s) are supported. Based on the received indication of supported Multi-USIM features from the UE, the MME shall indicate to the UE the support of the Multi-USIM features based on the Multi-USIM features supported by network and any preference policy by the network, if available. When a UE returns to having only one USIM active from a Multi-USIM UE that previously indicated to the network it supported Multi-USIM feature(s), the UE shall indicate all the Multi-USIM features are not supported to the network for that USIM. The MME shall only indicate the support of Paging Restriction feature together with the support of either Connection Release feature or Reject Paging Request feature. The Multi-USIM UE includes the support of individual features for Connection Release, Paging Cause Indication for Voice Service, Reject Paging Request and Paging Restrictions as specified in clause 5.11.3. The network shall not indicate support for any Multi-USIM feature to the UE as part of the Emergency Attach procedure or as part of Tracking Area Update for Emergency attached UE. A Multi-USIM UE shall use a separate IMEI for each USIM when it registers with the network. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.33 |
1,994 | β EUTRA-PhysCellIdRange | The IE EUTRA-PhysCellIdRange is used to encode either a single or a range of physical cell identities. The range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of EUTRA-PhysCellIdRange, NW may configure overlapping ranges of physical cell identities. EUTRA-PhysCellIdRange information element -- ASN1START -- TAG-EUTRA-PHYSCELLIDRANGE-START EUTRA-PhysCellIdRange ::= SEQUENCE { start EUTRA-PhysCellId, range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504, spare2, spare1} OPTIONAL -- Need N } -- TAG-EUTRA-PHYSCELLIDRANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
1,995 | 6.8.2.2.2 RAN-based notification area update to a new gNB/ng-eNB | When the UE decides to initiate the RANU procedure the UE may initiate the procedure with a new gNB/ng-eNB. In this case, the UE, the target gNB/ng-eNB and the source gNB/ng-eNB follow the detailed procedure as described in clause 6.8.2.1.3 with the following deviations: The target gNB/ng-eNB shall check if it supports the ciphering and integrity algorithms the UE used with the last source cell. If the target gNB/ng-eNB does not support the ciphering and integrity algorithms used in the last source cell or if the target gNB/ng-eNB prefers to use different algorithms than the source gNB/ng-eNB, then the target gNB/ng-eNB shall send an RRCSetup message on SRB0 to the UE in order to proceed with RRC connection establishment as if the UE was in RRC_IDLE (i.e., fallback procedure). If the target gNB/ng-eNB selects the ciphering and integrity protection algorithms which the UE used with the last source cell and the target gNB/ng-eNB decides to send the UE directly back to RRC_INACTIVE state without bringing the UE to RRC_CONNECTED state, the target gNB/ng-eNB shall perform a Path Switch procedure with the AMF to get a fresh {NCC, NH} pair before sending the RRCRelease message to the UE. After the target gNB/ng-eNB receives a fresh {NCC, NH} pair in the Path Switch Acknowledgement message from the AMF, the target gNB/ng-eNB shall set the value of NCC in the RRCRelease message to the NCC value of the received fresh {NCC, NH} pair. After the source gNB/ng-eNB (old gNB/ng-eNB) validates the ResumeMAC-I/shortResumeMAC-I received from the target gNB/ng-eNB (new gNB/ng-eNB) in the RETRIEVE UE CONTEXT REQUEST message, the old gNB/ng-eNB may decide not to relocate the UE context to the new gNB/ng-eNB. In this case, the old gNB/ng-eNB builds the RRCRelease message (MSG4) with a fresh I-RNTI, integrity protect it and encrypt it using the RRC keys that were derived from the new KgNB* similar to RRCResume message (MSG4) protection as specified in clause 6.8.2.1.3. Then, the old gNB/ng-eNB sends the integrity protected and encrypted RRCRelease message to the new gNB/ng-eNB in the RETRIEVE UE CONTEXT FAILURE message. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.2.2 |
1,996 | .1 Downlink Data Notification | A Downlink Data Notification message shall be sent: - on the S11 interface by the SGW to the MME as a part of the network triggered service request procedure; - on the S4 interface by the SGW to the S4-SGSN as part of Paging with no established user plane on S4, SGW triggered paging with S4; - on the S4 interface by the SGW to the S4-SGSN to re-establish all the previous released bearer(s) for a UE, upon receipt of downlink data for a UE in connected mode but without corresponding downlink bearer available; NOTE: This may occur e.g. if the S4-SGSN releases some but not all the bearers of the UE as specified in clause 12.7.2.2 of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. - on S11/S4 interface by SGW to MME/S4-SGSN if the SGW has received an Error Indication (see 3GPP TS 29.281[ General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) ] [13]) from eNodeB/RNC/MME across S1-U/S12/S11-U interface. Respective SGW and MME/S4-SGSN functionality is specified in 3GPP TS 23.007[ Restoration procedures ] [17]. - on the S11/S4 interface by SGW to the MME/S4-SGSN as part of the network triggered service restoration procedure if both the SGW and the MME/S4-SGSN support this optional feature (see 3GPP TS 23.007[ Restoration procedures ] [17]). - on the S11 interface by the SGW to the MME as a part of the Mobile Terminated Data Transport in Control Plane CIoT EPS optimisation with P-GW connectivity. A Downlink Data Notification message may be sent: - on the S4 by the SGW to the S4-SGSN if the SGW has received an Error Indication from S4-SGSN across S4-U interface. Table .1-1 specifies the presence of the IEs in the message. Table .1-1: Information Elements in a Downlink Data Notification Table 7.2.11.1-2: Load Control Information within Downlink Data Notification Table 7.2.11.1-3: Overload Control Information within Downlink Data Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | .1 |
1,997 | 20.3.2 Home network domain name | The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. The MSC Server enhanced for ICS shall derive the home network domain name from the subscriber's IMSI as described in the following steps: 1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. 2. Use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name. 3. Add the label "ics." to the beginning of the domain. An example of a home network domain name is: IMSI in use: 234150999999999; where: - MCC = 234; - MNC = 15; and - MSIN = 0999999999, which gives the home network domain name: ics.mnc015.mcc234.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 20.3.2 |
1,998 | 4.9.2.3.2 The target AMF is not in the PLMN of the N3IWF (i.e. N3IWF in HPLMN) | Figure 4.9.2.3.2-1: Handover of a PDU Session procedure from untrusted non-3GPP access with N3IWF in the HPLMN to 3GPP access (home routed roaming) 1. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. This includes the retrieval of the SMF-IDs corresponding to each of the PDU Sessions. 2. The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.2 (PDU Session Establishment for Home Routed Roaming). In the Nsmf_PDUSession_Create Response the H-SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the V-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) acceptable according to VPLMN policies. 3. The H-SMF executes the release of resources in non-3GPP AN by performing steps 3-12 specified in clause 4.12.7 with the following exceptions: - the H-SMF interfaces the source AMF (in the home PLMN). The H-SMF shall not send the N1 SM Container (PDU Session Release Command) to the UE; - The Npcf_SMPolicyControl_Delete service operation to PCF shall not be performed. - Nsmf_PDUSession_SMContexStatusNotify service operation invoked by the H-SMF to the source AMF indicates the PDU Session is moved to different access. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.2.3.2 |
1,999 | 5.44 Support of Personal IoT network service 5.44.1 General | Personal IoT Network (PIN) provides local connectivity between PIN elements i.e. UEs and/or non-3GPP devices. PIN elements communicate using PIN direct communication, PIN indirect communication and the PIN-DN communication. The management of the PIN direct communication is out of the scope of this specification. For the PIN indirect communication and PIN-DN communication, the data traffic and management traffic pass via a UE acting as PIN element with Gateway Capability (PEGC). With the support of the PEGC registered to 5G network, the PIN Elements have access to the 5G network services and may communicate with other PIN Elements within the PIN or with the DN via 5GC. A PEGC may support multiple PINs. For each PIN, a dedicated DNN/S-NSSAI shall be configured. PIN and PIN elements are managed by specific PIN element with Management Capability (PEMC) with support of an AF, if AF (Application Server and PIN server as specified in TS 23.542[ Application layer support for Personal IoT Network ] [181]) is deployed. A PIN includes at least one PEGC and at least one PEMC. The management of the PIN network (i.e. the management of PIN network creation, deletion and update) and PIN Element (including the management role distribution between PEMC and AF) is out of the scope of this specification. The PEGC is a UE with subscription data related to PIN within the 5GS (i.e. (DNN, S-NSSAI) combination(s) for PIN) and shall register to 5GS as UE in order to support PIN indirect communication and PIN-DN communication via dedicated PDU session. The UE acting as PEMC does not have subscription data related to PIN within the 5GS and behaves as normal UE if it is registered in 5GS. An AF for PIN may be deployed to support the PIN service. The AF for PIN may communicate with PIN elements, including PEMC and PEGC, via application layer for management of the PIN which is transported as user plane data transparently to 5GS and with the 5GC via NEF. The PEMC can manage the PIN via PIN direction communication or PIN indirect communication with the other elements of PIN or via PIN-DN communication with PIN AF which enables the exchange of information with 5GC. The 5GC is enhanced to support the delivery of UE policy related to PIN service for UE acting as PEGC (as specified in clause 5.44.2) and to support the PDU session management for PIN service (as specified in clause 5.44.3). See information in Annex P for the relation between PIN and 5GS. The PINE, PEMC and PEGC application layer functionalities are defined in TS 23.542[ Application layer support for Personal IoT Network ] [181] and are transparent in 5GS. The support of PIN by 5G-RG and FN-RG is not specified. Redundant PDU session for URLLC is not supported in conjunction with PIN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.44 |
2,000 | 6.4.2.3 UE-requested PDU session modification procedure accepted by the network | Upon receipt of a PDU SESSION MODIFICATION REQUEST message, if the SMF accepts the request to modify the PDU session, the SMF shall perform the network-requested PDU session modification procedure as specified in subclause 6.3.2. If the PDU SESSION MODIFICATION REQUEST message contains a Port management information container IE, the SMF shall handle the contents of the Port management information container IE as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.2.3 |
Subsets and Splits