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,801 | 6.41.2.5 UE Discovery, Selection and Access | Subject to operator’s policy and agreement between a 3rd party service provider and operator, the 5G system shall enable a UE to receive and use configuration provided by a 3rd party service provider to discover and access a hosting network and localized services, including the considerations of prior service agreement... | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.5 |
1,802 | 5.2.2.4 Namf_MT service 5.2.2.4.1 General | Service description: It provides a NF the service to request information related to capabilities that make sure UE is reachable to send MT signalling or data to a target UE or toward UEs in a multicast session. The following are the key functionalities of this NF service - paging UE if UE is in IDLE state and respond o... | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.4 |
1,803 | 8.106 Node Number | Node Number shall be coded as depicted in Figure 8.106-1. Figure 8.106-1: Node Number The Node number shall carry an ISDN number. If the Node Number carries the SGSN Number, then the SGSN number shall be coded according to the contents of ISDN-AddressString data type defined in 3GPP TS 29.002[ Mobile Application Part (... | 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.106 |
1,804 | 7B.5 Subscriber privacy for wireline access | The requirements and procedures on the UE related to subscriber privacy in clauses 5.2.5, 6.12 and Annex C are applicable for the 5G-RG. NOTE 1: The requirements and procedures on the UE related to subscriber privacy in clauses 5.2.5, 6.12 and Annex C are not applicable for the FG-RG. NOTE 2: When the SUPI contains a G... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7B.5 |
1,805 | – BWP-UplinkDedicated | The IE BWP-UplinkDedicated is used to configure the dedicated (UE specific) parameters of an uplink BWP. BWP-UplinkDedicated information element -- ASN1START -- TAG-BWP-UPLINKDEDICATED-START BWP-UplinkDedicated ::= SEQUENCE { pucch-Config SetupRelease { PUCCH-Config } OPTIONAL, -- Need M pusch-Config SetupRelease { PUS... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,806 | 5.21.3.4 Reliability of NF Services | When multiple NF Service instances within a NF Service Set are exposed to the NF Service consumer or SCP and the failure of NF Service instance is detected or notified by the NRF, i.e. it is not available anymore, the NF Service consumer or SCP selects another NF Service instance of the same NF Service Set within the N... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.3.4 |
1,807 | 6.5.2A.3.1 Minimum requirement for CA | For intra-band contiguous carrier aggregation bandwidth class B, C and D, the requirements in Table 6.5.2A.3.1-1 and 6.5.2A.3.1-2 apply within the aggregated transmission bandwidth configuration with both component carrier (s) active and one single contiguous PRB allocation of bandwidth at the edge of the aggregated tr... | 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.5.2A.3.1 |
1,808 | – LTM-CSI-ReportConfig | The IE LTM-CSI-ReportConfig is used to configure report on the cell in which the LTM-CSI-ReportConfig is included. LTM-CSI-ReportConfig information element -- ASN1START -- TAG-LTM-CSI-REPORTCONFIG-START LTM-CSI-ReportConfig-r18 ::= SEQUENCE { ltm-CSI-ReportConfigId-r18 LTM-CSI-ReportConfigId-r18, ltm-ResourcesForChanne... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,809 | 4.13.2 Support of RAT types defined in EPC for satellite access | In the case of satellite access with WB-E-UTRAN, NB-IoT or LTE-M, the RAT Types values "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", " WB-E-UTRAN(OTHERSAT)", "NB-IoT(LEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "NB-IoT(OTHERSAT)", "LTE-M(LEO)", "LTE-M(MEO)", "LTE-M(GEO)" and "LTE-M(OTHERSAT)" are used in EPC to dis... | 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.13.2 |
1,810 | 5.3.12A Handling of local emergency numbers received via 3GPP access and non-3GPP access 5.3.12A.1 General | The requirements in subclause 5.3.12 with the clarifications and additional conditions in subclause 5.3.12A apply to a UE supporting: - attach procedures (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) or registration procedures via 3GPP access; and - registratio... | 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.3.12A |
1,811 | D.3.1 Remote control | Some of the interactions within a plant are conducted by automated control applications similar to those described in clause D.2. Here too, sensor output is requested in a cyclic fashion, and actuator commands are sent via the communication network between a controller and the actuator. Furthermore, there is an emergin... | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.3.1 |
1,812 | 9.11.4.24 IP header compression configuration | The purpose of the IP header compression configuration information element is to negotiate ROHC channel setup parameters specified in IETF RFC 5795 [39B] and, optionally, provide additional header compression context setup parameters. The IP header compression configuration information element is coded as shown in figu... | 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.4.24 |
1,813 | 16.10.6.5.1 Service Continuity in RRC_IDLE or RRC_INACTIVE | Mobility procedures for MBS reception allow the UE to start or continue receiving MBS service(s) when changing cells. The gNB may indicate in the MCCH the list of neighbour cells providing the same MBS broadcast service(s) as provided in the serving cell. This allows the UE, e.g., to request unicast reception of the se... | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.5.1 |
1,814 | A.13 KAMF to KAMF' derivation in mobility | Derivation of KAMF' from KAMF during mobility shall use the following input parameters. - FC = 0x72 - P0 = DIRECTION - L0 = length of DIRECTION (i.e. 0x00 0x01) - P1 = COUNT, - L1 = length of COUNT (i.e. 0x00 0x04) The input key KEY shall be KAMF. When KAMF' is derived in handover, DIRECTION shall be 0x01 and COUNT sha... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.13 |
1,815 | .2 Delete Bearer Response | The Delete Bearer Response shall be sent as a response of Delete Bearer Request. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Temporarily rejected due to handover/TAU/RAU procedure in progress". Tab... | 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 | .2 |
1,816 | – RRCReject | The RRCReject message is used to reject an RRC connection establishment or an RRC connection resumption. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: Network to UE RRCReject message -- ASN1START -- TAG-RRCREJECT-START RRCReject ::= SEQUENCE { criticalExtensions CHOICE { rrcReject RRCReject... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,817 | 4.3.4.4 Abnormal cases | The following abnormal cases can be identified: a) Lower layer failure If the establishment of an RR connection is unsuccessful, or the RR connection is lost, the IMSI detach is aborted by the mobile station. b) Access barred because of access class control or EAB The signalling procedure for IMSI detach shall not be s... | 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.3.4.4 |
1,818 | 3.2 Symbols | For the purposes of the present document the following symbols apply: A Interface between an MSC and a BSC. Bea Reference point for the CDR file transfer from the Exposure function API CGF to the BD. Bc Reference point for the CDR file transfer from the Circuit Switched CGF to the BD. Bcp Reference point for the CDR fi... | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 3.2 |
1,819 | 5.7.7.3 Actions related to transmission of ULDedicatedMessageSegment message | The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows: 1> For each new UL DCCH... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.7.3 |
1,820 | 4.4.4.3 Integrity checking of NAS signalling messages in the MME | Except the messages listed below, no NAS signalling messages shall be processed by the receiving EMM entity in the MME or forwarded to the ESM entity, unless the secure exchange of NAS messages has been established for the NAS signalling connection: - EMM messages: - ATTACH REQUEST; - IDENTITY RESPONSE (if requested id... | 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 | 4.4.4.3 |
1,821 | 5.15.3 Applications using the RIM Procedures | The RAN node applications, which use the RIM procedures, are fully transparent for the MME and SGSN. These applications are described in RAN specifications. An example between E-UTRAN and GERAN is the Network Assisted Cell Change described in TS 48.018[ None ] [42], TS 25.413[ UTRAN Iu interface Radio Access Network A... | 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.15.3 |
1,822 | 9.4 Reporting of Precoding Matrix Indicator (PMI) | The minimum performance requirements of PMI reporting are defined based on the precoding gain, expressed as the relative increase in throughput when the transmitter is configured according to the UE reports compared to the case when the transmitter is using random precoding, respectively. When the transmitter uses rand... | 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.4 |
1,823 | 11.8 Non-IP data transfering over SGi 11.8.1 General | When support of Non-IP data is provided at the Gi/SGi interface, different Point-to-Point (PtP) tunneling techniques may be used. When using PtP tunneling by UDP/IP encapsulation subclause 11.8.2 below shall be followed. Other techniques as described in clause 11.8.3 below may be used. The Gi/SGi based Non-IP data deli... | 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 |
1,824 | 4.7.13.3 Service request procedure accepted by the network | If the SERVICE REQUEST message was sent in PMM-IDLE mode, the indication from the lower layers that the security mode control procedure is completed shall be treated as a successful completion of the procedure. The service request attempt counter shall be reset, timer T3317 shall be stopped, and the MS enters GMM-REGIS... | 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.13.3 |
1,825 | 8.11.2.2.4 CE Mode A with CRS interference model | The requirements are specified in Table 8.11.2.2.4-2, with the addition of parameters in Table 8.11.2.2.4-1. In Table 8.11.2.2.4-2, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respective... | 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.11.2.2.4 |
1,826 | 19 Support for NR coverage enhancements | To improve NR uplink coverage for both FR1 and FR2, the following enhancements on PUSCH, PUCCH, PRACH and MSG3 PUSCH are supported: - Enhanced aggregation of multiple slots with TB repetition is supported for both PUSCH transmission with dynamic and configured grant. In addition, counting based on available slots is su... | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 19 |
1,827 | 5.4.5 UE requested bearer resource modification | The UE requested bearer resource modification procedure for an E-UTRAN is depicted in figure 5.4.5-1. The procedure allows the UE to request for a modification of bearer resources (e.g. allocation or release of resources) for one traffic flow aggregate with a specific QoS demand. Alternatively, the procedure allows the... | 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.4.5 |
1,828 | – PUCCH-TPC-CommandConfig | The IE PUCCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI. PUCCH-TPC-CommandConfig information element -- ASN1START -- TAG-PUCCH-TPC-COMMANDCONFIG-START PUCCH-TPC-CommandConfig ::= SEQUENCE { tpc-IndexPCell INTEGER (1..15) OPTIONAL, -- Cond PDCCH-O... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,829 | 5.8.9.9.2 Actions related to transmission of UuMessageTransferSidelink message | The L2 U2N Relay UE initiates the Uu message transfer procedure when at least one of the following conditions is met: 1> upon receiving Paging message related to the connected L2 U2N Remote UE from network (including Paging message within RRCReconfiguration message); 1> upon acquisition of the SIB(s) requested by the c... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.9.2 |
1,830 | 5.5.1.3.4.2 Combined attach successful | The description for attach for EPS services as specified in clause 5.5.1.2.4 shall be followed. In addition, the following description for attach for non-EPS services or "SMS only" applies. The TMSI reallocation may be part of the combined attach procedure. The TMSI allocated is then included in the ATTACH ACCEPT messa... | 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.5.1.3.4.2 |
1,831 | 6.4.1 UE-requested PDU session establishment procedure 6.4.1.1 General | The purpose of the UE-requested PDU session establishment procedure is to establish a new PDU session with a DN, to perform handover of an existing PDU session between 3GPP access and non-3GPP access, to transfer an existing PDN connection in the EPS to the 5GS, to transfer an existing PDN connection in an untrusted no... | 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.1 |
1,832 | 5.21.1.2 NGAP UE-TNLA-binding | While a UE is in CM-Connected state the 5G-AN node shall maintain the same NGAP UE-TNLA-binding (i.e. use the same TNL association and same NGAP association for the UE) unless explicitly changed or released by the AMF. An AMF shall be able to update the NGAP UE-TNLA-binding (i.e. change the TNL association for the UE) ... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.1.2 |
1,833 | B.1 Protection of RRC messages | The following list provides information which messages can be sent (unprotected) prior to AS security activation and which messages can be sent unprotected after AS security activation. Those messages indicated "-" in "P" column should never be sent unprotected by gNB or UE. Further requirements are defined in the proc... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.1 |
1,834 | 6.3 Coordination between SM and GMM for supporting ISR | The MS with its TIN set as "RAT-related TMSI" for which ISR is activated shall change its TIN to "P-TMSI" to locally deactivate ISR and stop the periodic tracking area update timer T3412 or T3423, if running: - upon modification of any PDP context which was activated before the ISR is activated in the MS; - upon deacti... | 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.3 |
1,835 | 8.4.4.1 SN Addition with SCG Activation or Deactivation | Figure 8.4.4.1-1: SCG Activation or Deactivation in SN Addition procedure 1. The MN sends the SN Addition Request message to the SN, indicates the request of SCG activation or deactivation. 2. The SN-CU-CP may send the BEARER CONTEXT SETUP REQUEST message to the SN-CU-UP to setup bearer context and notify the activatio... | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.4.1 |
1,836 | 13.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... | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.2 |
1,837 | J.1 Modified f5* function | This annex shows how the AUTS calculation could be modified in order to avoid keystream re-use during AKA re-synchronisations procedure. The f5* function given in clause 6.3.3 only has RAND as a non-key input and hence if an authentication challenge (RAND, AUTN) is replayed, then the same AK is calculated which is then... | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | J.1 |
1,838 | B.2.1.1 Security procedures | EAP-TLS is a mutual authentication EAP method that can be used by the EAP peer and the EAP server to authenticate each other. It is specified in RFC 5216 [38] and draft-ietf-emu-eap-tls13 [76]. The 3GPP TLS protocol profile related to supported TLS versions and supported TLS cipher suites in 3GPP networks is specified ... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.2.1.1 |
1,839 | 10.5.5.20 Service type | The purpose of the service type information element is to specify the purpose of the Service request procedure. The service type is a type 1 information element. The service type information element is coded as shown in figure 10.5.135/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols... | 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 | 10.5.5.20 |
1,840 | 5.7.1.3 Reception of the DLInformationTransfer by the UE | Upon receiving DLInformationTransfer message, the UE shall: 1> if dedicatedNAS-Message is included: 2> forward dedicatedNAS-Message to upper layers. 1> if referenceTimeInfo is included: 2> calculate the reference time based on the time, referenceSFN and timeInfoType if it is included; 2> calculate the uncertainty of th... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.1.3 |
1,841 | 8.1 UE Initial Access | The signalling flow for UE Initial access is shown in Figure 8.1-1. Figure 8.1-1: UE Initial Access procedure 1. The UE sends an RRCSetupRequest message to the gNB-DU. 2. The gNB-DU includes the RRC message and, if the UE is admitted, the corresponding low layer configuration for the UE in the INITIAL UL RRC MESSAGE TR... | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.1 |
1,842 | 6.1.3.7a Extended MCH Scheduling Information MAC Control Element | The Extended MCH Scheduling Information MAC control element illustrated in Figure 6.1.3.7-2 is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-4. This control element has a variable size. For each MTCH the fields below are included: - LCID: this field indicates the Logical Channel ID of the MTCH... | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.7a |
1,843 | 9.1.1.2 Applicability and test rules for different CA configurations and bandwidth combination sets | The performance requirement for CA CQI tests in Clause 9 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL CCs in Table... | 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.1.1.2 |
1,844 | 5 GTP Header for Control Plane 5.1 General format | Control Plane GTP uses a variable length header. Control Plane GTP header length shall be a multiple of 4 octets. Figure 5.1-1 illustrates the format of the GTPv2-C Header. Figure 5.1-1: General format of GTPv2 Header for Control Plane Where: - if T = 0, TEID field is not present, k = 0, m = 0 and n = 5; - if T = 1, TE... | 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 | 5 |
1,845 | 5.3.3 Connection Management 5.3.3.1 General | Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3 |
1,846 | 8.17.4 IAB Inter-CU Backhaul RLF recovery for single connected IAB-node | The inter-CU backhaul RLF recovery procedure for IAB-nodes in SA mode enables recovery of an IAB-node to another parent node underneath a different IAB-donor-CU, when the IAB-MT of the IAB-node detects backhaul RLF. Figure 8.17.4-1 shows an example of the backhaul RLF recovery procedure for an IAB-node in SA mode. In t... | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.17.4 |
1,847 | 16.14.10 Verification of UE location | For UE location verification based on multi-RTT with single satellite in NTN, at least the following UE and gNB measurements specified in TS 38.215[ NR; Physical layer measurements ] [59] are reported: gNB receive-transmit time difference at the uplink time synchronization reference point, UE receive-transmit time dif... | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.10 |
1,848 | 4.7.5.1.4a Routing area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only) | If the routing area updating request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the MS shall perform the procedures as described in subclause 4.7.5.1.4. Then if the MS is in the same selected PLMN where the last routing area updating was attempted, the MS shall: a) ... | 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.1.4a |
1,849 | 8.13.2 Management based MDT activation 8.13.2.1 General | In Management Based Trace Activation towards a gNB-CU-CP, gNB-CU-UP or a gNB-DU can be fulfilled with the Cell Traffic trace functionality defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The configuration parameters of the Trace Ses... | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2 |
1,850 | 4.4.3 IMSI attach procedure | The IMSI attach procedure is the complement of the IMSI detach procedure (see subclause 4.3.4). It is used to indicate the IMSI as active in the network. In A/Gb mode and GERAN Iu mode, the network indicates whether the IMSI attach/detach procedures are required by using the ATT flag which is broadcast in the L3-RR SYS... | 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.4.3 |
1,851 | 5.6.1.5A Service request procedure for initiating a PDN connection for emergency bearer services not accepted by the network | If the service request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.6.1.5. If the service request for initiating a PDN connection for emergency bearer services fails due to receiving the AUTHENTICATION REJEC... | 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.6.1.5A |
1,852 | 10.5.5.21 Cell Notification | The purpose of the Cell Notification information element is to indicate that the Cell Notification is supported by the network and shall be then used by MS. The Cell Notification information element is coded as shown in figure 10.5.135a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocol... | 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 | 10.5.5.21 |
1,853 | 6.10.3.1 SN Counter maintenance | The MN shall maintain a 16-bit counter, SN Counter, in its AS security context. The SN Counter is used when computing the KSN. The MN maintains the value of the counter SN Counter for a duration of the current 5G AS security context between UE and MN. The UE does not need to maintain the SN Counter after it has compute... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.3.1 |
1,854 | 5.8.5.7 Usage Report generated by UPF | The UPF sends the Usage Report to inform the SMF about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the Usage Report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final Usage Report is sent ... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.5.7 |
1,855 | 4.7.2.8 Handling of timer T3324 (A/Gb mode, Iu mode and S1 mode) | An MS supporting PSM may request the network to assign a value for T3324 by including a requested timer value in: - the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message (in A/Gb mode and Iu mode ); or - the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message (in S1 mode). The value of timer T3324 can be sent by... | 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.2.8 |
1,856 | 7.2.18 Create Indirect Data Forwarding Tunnel Request | The Create Indirect Data Forwarding Tunnel Request message shall be sent on the S11/S4 interface by the MME/SGSN to the SGW as part of the Handover procedures or TAU/RAU procedure with Serving GW change and data forwarding as specified in clause 5.3.3.1A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancemen... | 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.2.18 |
1,857 | – AppLayerMeasParameters | The IE AppLayerMeasParameters is used to convey the capabilities supported by the UE for application layer measurements. AppLayerMeasParameters information element -- ASN1START -- TAG-APPLAYERMEASPARAMETERS-START AppLayerMeasParameters-r17 ::= SEQUENCE { qoe-Streaming-MeasReport-r17 ENUMERATED {supported} OPTIONAL, qoe... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,858 | 5.3.11 Power saving mode | The UE can request the use of power saving mode (PSM) during an attach or tracking area updating procedure (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 Univ... | 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.11 |
1,859 | 4.13.8 Enhanced support of discontinuous network coverage for satellite access 4.13.8.1 General | Basic support for discontinuous coverage is specified in clause 4.3.5.2 and clause 4.3.17.7. The present clause 4.13.8 provides additional optional enhancements to discontinuous coverage: - Mobility management and power saving optimization, see clause 4.13.8.2; and - Coverage availability information provisioning to th... | 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.13.8 |
1,860 | 4.11.2 Handling list of "PLMNs not allowed to operate at the present UE location" | The UE may be rejected with EMM cause #78 in ATTACH REJECT message, TRACKING AREA UPDATE REJECT message or DETACH REQUEST message. The EMM cause #78 is applicable for the UE only when the UE is accessing a PLMN using a satellite E-UTRAN access. For the satellite E-UTRAN access the UE shall store a list of "PLMN not all... | 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 | 4.11.2 |
1,861 | 5.5.4.27 Event A5H1 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3) | The UE shall: 1> consider the entering condition for this event to be satisfied when all of condition A5H1-1 and condition A5H1-2 and condition A5H1-3, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A5H1-4 or condition A5H1-5 or condition A5H1-6, i.e. ... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.27 |
1,862 | 6.3.22 NSACF discovery and selection | The NF consumers shall utilise the NRF to discover NSACF instance(s), including the NSACF acting as Primary NSACF role, unless NSACF information is available by other means, e.g. locally configured in NF consumers. The NSACF selection function in the NSACF NF consumer selects an NSACF instance based on the available NS... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.22 |
1,863 | 8.7.3 FDD (EPDCCH scheduling) | The parameters specified in Table 8.7.3-1 are valid for all FDD tests unless otherwise stated. Table 8.7.3-1: Common test parameters (FDD) The requirements are specified in Table 8.7.3-3, with the addition of the parameters in Table 8.7.3-2 and the downlink physical channel setup according to Annex C.3.2. The test poin... | 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.7.3 |
1,864 | 6.26.2.2 5G LAN-virtual network (5G LAN-VN) | A UE shall be able to select a 5G LAN-VN, that the UE is a member of, for private communication. A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands. The 5G system shall be able to support large numbers of small 5G LAN-VNs. NOTE: Targeting residential deployments translate ... | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2.2 |
1,865 | 13.3.7 Authentication and authorization between SCPs | SCPs shall use one of the following methods as described in 13.1 to mutually authenticate each other before service layer messages can be exchanged on that interface: - If the PLMN uses protection at the transport layer, authentication provided by the transport layer protection solution shall be used for mutual authent... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.7 |
1,866 | 9.3.4.1.1 FDD | For the parameters specified in Table 9.3.4.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.4.1.1-2 and by the following a) the ratio of the throughput obtained when transmitting on a randomly selected subband among the best M subbands report... | 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.4.1.1 |
1,867 | 5.3.2.1 HARQ Entity | There is one HARQ entity at the MAC entity for each Serving Cell which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see clause 5.3.2.2... | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.3.2.1 |
1,868 | 6.10.2 MBSFN reference signals | MBSFN reference signals shall be transmitted in the MBSFN region of MBSFN subframes/slots only when the PMCH is transmitted. MBSFN reference signals are transmitted on antenna port 4. For an MBMS-dedicated carrier configured with a single MBSFN area, and for a PMCH transmitted with 0.37 kHz subcarrier spacing in slot ,... | 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.10.2 |
1,869 | 4.15.6.7a Authorization of service specific parameter provisioning | Figure 4.15.6.7a-1 shows the procedure to authorize the service specific parameter provisioning requests (e.g. for Application guidance for URSP determination as defined in clause 4.15.6.10). Figure 4.15.6.7a-1: Service Specific Authorization for an individual UE or group of UEs 1. The AF initiates the procedure as spe... | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.7a |
1,870 | 5.3.5.5 Cell Group configuration 5.3.5.5.1 General | The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], and for NE-DC, the SCG is configured a... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5 |
1,871 | – BWP-UplinkCommon | The IE BWP-UplinkCommon is used to configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all oth... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,872 | 10.8.1 EN-DC | The Master Node to eNB Change procedure is used to transfer context data from a source MN/SN to a target eNB. Figure 10.8.1-1: Master Node to eNB Change procedure Figure 10.8.1-1 shows an example signalling flow for the Master Node to eNB Change procedure: 1. The source MN starts the MN to eNB Change procedure by initi... | 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.8.1 |
1,873 | 5.8.6.2 Selection and reselection of synchronisation reference | The UE shall for frequency(ies) which have been selected for NR sidelink communication/discovery as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]: 1> if one frequency is selected for NR sidelink communication/discovery: 2> if sl-SyncFreqList is not included in RRCReconfiguration ... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.6.2 |
1,874 | 4.23.6.3 Reporting UP path change to the AF | Figure 4.23.6.3-1 shows procedures related Reporting UP path change to the AF. Figure 4.23.6.3-1: Reporting UP path change to the AF 1a. I-SMF indicates that UP path change may occur for the PDU Session via Nsmf_PDUSession_Update Request as described in clause 4.23.9; the SMF responds to the I-SMF. 2. If early notifica... | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.6.3 |
1,875 | 5.3.1.1 RRC connection control | RRC connection establishment involves the establishment of SRB1. The network completes RRC connection establishment prior to completing the establishment of the NG connection, i.e. prior to receiving the UE context information from the 5GC. Consequently, AS security is not activated during the initial phase of the RRC ... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.1.1 |
1,876 | 16.3a.1 Authentication, Authorization and Accounting procedures | When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN, the P-GW may (depending on the configuration for this APN) send a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If the RADIUS server is also respo... | 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 | 16.3a.1 |
1,877 | 5.3.3.3 Actions related to transmission of RRCSetupRequest message | The UE shall set the contents of RRCSetupRequest message as follows: 1> set the ue-Identity as follows: 2> if upper layers provide a 5G-S-TMSI: 3> set the ue-Identity to ng-5G-S-TMSI-Part1; 2> else: 3> draw a 39-bit random value in the range 0..239-1 and set the ue-Identity to this value; NOTE 1: Upper layers provide t... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.3 |
1,878 | 5.2.2.4 Notification of interworking in connection with mobile terminating call establishment | In this subclause, the term "interworking" is used only in the meaning of interworking with a network other than PLMN or ISDN, not as interworking between PLMN and ISDN since this is the normal case. In this sense, PLMN and ISDN are seen within the same environment, called the PLMN/ISDN environment. During call establi... | 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.4 |
1,879 | 5.8.10.4.3 Event S2 (Serving becomes worse than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition S2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition S2-2, as specified below, is fulfilled; 1> for this NR sidelink measurement, consider the NR sidelink fre... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.4.3 |
1,880 | 4.5.5.3 Distribution of RACH access delay | This measurement provides the distribution of number of the time before UEs in a cell achieve a successful attach. The RACH access delay is the time from when a UE sends its first Random Access Preamble until the UE receives the Random Access Response. CC This measurement is obtained by incrementing the measurement bin... | 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.5.5.3 |
1,881 | 5.1.6 Completion of the Random Access procedure | At completion of the Random Access procedure, the MAC entity shall: - discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any; - flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer. Upon successful completion of the Random Access procedure initiated for DAPS handover, the ... | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.6 |
1,882 | 5.5.2.2 Measurement identity removal | The UE shall: 1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in VarMeasConfig: 2> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> remove the measurement reporting entry for this measId from the VarMeasReportList, if ... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.2 |
1,883 | 5.15.4.1.2 Mapping of S-NSSAIs values in the Allowed NSSAI and in the Requested NSSAI to the S-NSSAIs values used in the HPLMN | For the roaming case, one or more S-NSSAIs in an Allowed NSSAI provided to the UE can have values which are not part of the UE's current Network Slice configuration information for the Serving PLMN. In this case, the network provides the Allowed NSSAI together with the mapping of each S-NSSAI of the Allowed NSSAI to th... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.4.1.2 |
1,884 | 13.4.1.2.2 Service Request Process | The complete service request is two-step process including requesting an access token by NF Service Consumer (Step 1, i.e. 1a or 1b), and then verification of the access token by NF Service Producer (Step 2). Step 1: Access token request Pre-requisite: - The NF Service consumer (OAuth2.0 client) is registered with the ... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.2.2 |
1,885 | 4.8.2.2a Network Triggered Connection Resume in RRC_INACTIVE procedure | The Network Triggered Connection Resume in RRC_INACTIVE procedure is used when the NG-RAN needs to send data (e.g. the N1 NAS PDU and/or downlink user plane PDU) to a UE in the RRC_INACTIVE state. During the procedure, the NG-RAN sends a RAN Paging to the UE in order to trigger the Connection Resume in RRC_INACTIVE pro... | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.2.2a |
1,886 | 8.2.6.18 Payload container | Within a PLMN, this IE shall be included if: a) the UE has one or more stored UE policy sections identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN for the registration procedure for mobility and periodic registration update due to inter-system change from S1 mode to N1 mode of a UE op... | 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 | 8.2.6.18 |
1,887 | 5.3.19 Handling of congestion control for transport of user data via the control plane | The network may activate congestion control for transport of user data via the control plane, as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has indicated support for the control plane CIoT 5GS optimizations and the network decides to activate the congestion control for tr... | 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.3.19 |
1,888 | 4.15.6.9.2 Processing AF requests to influence access and mobility management policies targeting an individual UE | This procedure is used for individual UEs when the request shall be applied independently of conditions related to the application traffic. Depending on the AF deployment (see clause 6.2.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AF may interact with NFs of the Core Network either directl... | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.9.2 |
1,889 | 6.38.2.2 Gateways | The 5G system shall be able to support access to the 5G network and its services via at least one gateway (i.e. PIN Element with Gateway Capability or eRG) for authorised UEs and authorised non-3GPP devices in a PIN or a CPN. The 5G system shall be able to support IP traffic offload to data network for a CPN. NOTE 1: T... | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2.2 |
1,890 | 6.1.3.3.2 Synchronization failure recovery in Home Network | Upon receiving an authentication failure message with synchronisation failure (AUTS) from the UE, the SEAF sends an Nausf_UEAuthentication_Authenticate Request message with a "synchronisation failure indication" to the AUSF and the AUSF sends an Nudm_UEAuthentication_Get Request message to the UDM/ARPF, together with t... | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.3.2 |
1,891 | 5.45 QoS Monitoring 5.45.1 General | QoS monitoring comprises of measurements of QoS monitoring parameters and reports of the measurement result for a QoS Flow and can be enabled based on 3rd party application requests and/or operator policies configured in the PCF. Event Reporting from PCF is specified in clause 6.1.3.18 of TS 23.503[ Policy and charging... | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.45 |
1,892 | 5.5.2.7 Reporting configuration addition/modification | The UE shall: 1> for each reportConfigId included in the received reportConfigToAddModList: 2> if an entry with the matching reportConfigId exists in the reportConfigList within the VarMeasConfig, for this entry: 3> reconfigure the entry with the value received for this reportConfig; 3> for each measId associated with ... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.7 |
1,893 | 9.5.10 Modify PDP context request (MS to network direction) | This message is sent by the MS to the network to request modification of an active PDP context. See table 9.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: modify PDP context request (MS TO network direction) Significance: global Direction: MS to netw... | 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 | 9.5.10 |
1,894 | 16.9.9.2 Channel Access Priority Classes for Sidelink (SL-CAPC) | The SL-CAPC of SL radio bearers and SL MAC CEs are either fixed or (pre)configurable as follows: - Fixed to the highest priority for all SL-SRBs and SL MAC CEs - (Pre)configurable per DRB for all SL-DRBs When choosing the SL-CAPC for a SL-DRB the network takes into account the PQIs of all QoS flows mapped to that SL DR... | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.9.2 |
1,895 | 5.4.6 Power Headroom Reporting | The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission or SRS transmission per activated Serving Cell and also with information about the difference between the nominal ... | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.6 |
1,896 | 5.3.18 Restricted local operator services | Restricted local operator services (RLOS) is an optional feature that enables operators to offer access to restricted local operator services to the unauthenticated UEs in limited service state (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (... | 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.18 |
1,897 | 9.11.3.108 On-demand NSSAI | The purpose of the On-demand NSSAI information element is to provide a list of one or more on-demand S-NSSAIs and the associated slice deregistration inactivity timer value per the on-demand S-NSSAI to the UE. The On-demand NSSAI information element is coded as shown in figure 9.11.3.108.1, figure 9.11.3.108.2, and tab... | 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.108 |
1,898 | 8.3.2.1I Single-layer Spatial Multiplexing (With Enhanced DMRS table configured) | For single-layer transmission on antenna port 7, 8, 11 or 13 upon detection of a PDCCH with DCI format 2C, the requirement is specified in Table 8.3.2.1I-2, with the addition of the parameters in Table 8.3.2.1I-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of the test is to verify rank... | 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.3.2.1I |
1,899 | Annex G (informative): Business to Business (B2B) charging architecture and principles G.2.1 General | In the B2B scenario, the charging architecture may involve two modes of interaction: - Business CHF interaction: the NF (CTF) collects and reports the charging information per business, alternatively it collects and reports the charging information per consumer but for business charging purposes, to the business CHF (i... | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
1,900 | – SL-PSSCH-TxConfigList | The IE SL-PSSCH-TxConfigList indicates PSSCH transmission parameters. When lower layers select parameters from the range indicated in IE SL-PSSCH-TxConfigList, the UE considers both configurations in IE SL-PSSCH-TxConfigList and the CBR-dependent configurations represented in IE SL-CBR-PriorityTxConfigList. Only one IE... | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.