MARTINEZ TARRADELL MARTA (US)
GUO YI (CN)
PALAT SUDEEP (GB)
YIU CANDY (US)
ZHANG YUJIAN (CN)
ALI ANSAB (US)
HEO YOUN HYOUNG (US)
| US20200305202A1 | 2020-09-24 | |||
| US20210112590A1 | 2021-04-15 |
HUAWEI, HISILICON: "RACH indication and partitioning", 3GPP DRAFT; R2-2108210, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic Meeting; 20210809 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034692
APPLE: "Cross-WI RACH Design", 3GPP DRAFT; R2-2107575, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20210809 - 20210827, 6 August 2021 (2021-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052034224
| CLAIMS What is claimed is: 1. One or more computer-readable media storing instructions that, when executed by one or more processors, configure a user equipment (UE) to: receive, from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. 2. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on a reference signal received power (RSRP) threshold. 3. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on whether the UE is a reduced capability (RedCap) UE. 4. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on a slice group determined by an upper layer. 5. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on applicability of small data transmission (SDT) to the UE. 6. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on an availability of RACH resources for a cell. 7. The one or more computer-readable media of claim 1, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. 8. The one or more computer-readable media of claim 7, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single feature or a highest aggregated priority for a combination of features. 9. The one or more computer-readable media of claim 1, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. 10. The one or more computer-readable media of any of claims 1-9, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. 11. An apparatus of a user equipment (UE) comprising: memory to store random access channel (RACH) configuration information included in an information element (IE) received in a message from an a next-generation NodeB (gNB), the RACH configuration information comprising a list of RACH features or feature combinations supported by a network; and processing circuitry, coupled with the memory, to: retrieve the RACH configuration information from the memory; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. 12. The apparatus of claim 11, wherein the set of RACH resources is selected based further on one or more of: a reference signal received power (RSRP) threshold, whether the UE is a reduced capability (RedCap) UE, a slice group determined by an upper layer, applicability of small data transmission (SDT) to the UE, and an availability of RACH resources for a cell. 13. The apparatus of claim 11, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. 14. The apparatus of claim 13, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single feature or a highest aggregated priority for a combination of features. 15. The apparatus of claim 11, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. 16. The apparatus of and of claims 11-15, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. 17. One or more computer-readable media storing instructions that, when executed by one or more processors, configure a user equipment (UE) to: receive, from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE, wherein the set of RACH resources is selected based on one or more of: one or more of: a reference signal received power (RSRP) threshold, whether the UE is a reduced capability (RedCap) UE, a slice group determined by an upper layer, applicability of small data transmission (SDT) to the UE, and an availability of RACH resources for a cell. 18. The one or more computer-readable media of claim 17, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. 19. The one or more computer-readable media of claim 18, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single resource or highest aggregated priority for a combination of features. 20. The one or more computer-readable media of claim 17, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. 21. The one or more computer-readable media of any of claims 17-20, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. |
In summary, Figure 4 illustrates an example of a flow of a random access procedure with the update on the selection of the PRACH configuration/resource. In this example, the UE selects the PRACH configuration/resources corresponding to the feature combination depending on the options described in Step 3. Detailed solution for Problem 3: Assuming that the combination of 2-step RA and CE are excluded and also fallback to Msg1 only occur once, the only features that can fallback are SDT, slicing and RedCap. Option 1: Set a fix rules for fallback to Msg1 in the specification common for all feature combination. For example, fallback to Msg1 only to the 4-step RACH resources corresponding to the feature combination selected (if configured); otherwise no fallback (as per legacy). Another example, fallback to Msg1 to the 4-step RACH resources corresponding to the feature combination selected (if configured); if not configured, fallback to Msg1 of the common 4-step RACH resources of the BWP (this can also initiate a restart of the RACH procedure) Option 2: Set further fallback feature combination rules if the fallback to the feature combination specific 4-step RACH is not available (e.g. it is not configured). In this option, if the fallback to the feature combination specific 4-step RACH is available, the fallback to Msg1 will occur on the feature combination specific 4-step RACH. If the fallback to the feature combination specific 4-step RACH is not available, instead of always restarting the RACH procedure on common 4-step RACH or fallback to Msg1 of 4-step RACH, the network will provide the fallback to Msg1 option (e.g. network provides as part of the configuration in the feature combination specific 2-step RACH an additional parameter indicating the feature combination specific 4-step RACH possible. For example, the UE initiates the 2-step RACH for SDT, Slicing and RedCap. But cell only configure 4-step RACH for SDT + RedCap or slicing + RedCap or common 4-step RACH. The network can indicate with additional signalling whether the UE can fallback to SDT+RedCap or Slicing+RedCap or common 4-step RACH. Alternatively, the UE can use the PRACH configuration/resource provided by the cell corresponding to the feature combination that are considered valid by the UE in Step 2 in ‘Detailed solution for Problem 2' and are for 4-step RACH and use Step 3 in ‘Detailed solution for Problem 2' to decide on which PRACH configuration/resource corresponding to 4-step RACH can be used for the fallback. Option 3: Leave the decision up to UE implementation on which 4-step RACH resources that are valid as per Step 2 in Detailed solution for Problem 2 to fallback to. SYSTEMS AND IMPLEMENTATIONS Figures 5-7 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments. Figure 5 illustrates a network 500 in accordance with various embodiments. The network 500 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like. The network 500 may include a UE 502, which may include any mobile or non-mobile computing device designed to communicate with a RAN 504 via an over-the-air connection. The UE 502 may be communicatively coupled with the RAN 504 by a Uu interface. The UE 502 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc. In some embodiments, the network 500 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. In some embodiments, the UE 502 may additionally communicate with an AP 506 via an over-the-air connection. The AP 506 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 504. The connection between the UE 502 and the AP 506 may be consistent with any IEEE 802.11 protocol, wherein the AP 506 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 502, RAN 504, and AP 506 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 502 being configured by the RAN 504 to utilize both cellular radio resources and WLAN resources. The RAN 504 may include one or more access nodes, for example, AN 508. AN 508 may terminate air-interface protocols for the UE 502 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 508 may enable data/voice connectivity between CN 520 and the UE 502. In some embodiments, the AN 508 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 508 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 508 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells. In embodiments in which the RAN 504 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 504 is an LTE RAN) or an Xn interface (if the RAN 504 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc. The ANs of the RAN 504 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 502 with an air interface for network access. The UE 502 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 504. For example, the UE 502 and RAN 504 may use carrier aggregation to allow the UE 502 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc. The RAN 504 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol. In V2X scenarios the UE 502 or AN 508 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network. In some embodiments, the RAN 504 may be an LTE RAN 510 with eNBs, for example, eNB 512. The LTE RAN 510 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands. In some embodiments, the RAN 504 may be an NG-RAN 514 with gNBs, for example, gNB 516, or ng-eNBs, for example, ng-eNB 518. The gNB 516 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 516 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 518 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 516 and the ng-eNB 518 may connect with each other over an Xn interface. In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 514 and a UPF 548 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN514 and an AMF 544 (e.g., N2 interface). The NG-RAN 514 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 502 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 502, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 502 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 502 and in some cases at the gNB 516. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load. The RAN 504 is communicatively coupled to CN 520 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 502). The components of the CN 520 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 520 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 520 may be referred to as a network slice, and a logical instantiation of a portion of the CN 520 may be referred to as a network sub-slice. In some embodiments, the CN 520 may be an LTE CN 522, which may also be referred to as an EPC. The LTE CN 522 may include MME 524, SGW 526, SGSN 528, HSS 530, PGW 532, and PCRF 534 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 522 may be briefly introduced as follows. The MME 524 may implement mobility management functions to track a current location of the UE 502 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc. The SGW 526 may terminate an S1 interface toward the RAN and route data packets between the RAN and the LTE CN 522. The SGW 526 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The SGSN 528 may track a location of the UE 502 and perform security functions and access control. In addition, the SGSN 528 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 524; MME selection for handovers; etc. The S3 reference point between the MME 524 and the SGSN 528 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states. The HSS 530 may include a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The HSS 530 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 530 and the MME 524 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 520. The PGW 532 may terminate an SGi interface toward a data network (DN) 536 that may include an application/content server 538. The PGW 532 may route data packets between the LTE CN 522 and the data network 536. The PGW 532 may be coupled with the SGW 526 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 532 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 532 and the data network 536 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 532 may be coupled with a PCRF 534 via a Gx reference point. The PCRF 534 is the policy and charging control element of the LTE CN 522. The PCRF 534 may be communicatively coupled to the app/content server 538 to determine appropriate QoS and charging parameters for service flows. The PCRF 532 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI. In some embodiments, the CN 520 may be a 5GC 540. The 5GC 540 may include an AUSF 542, AMF 544, SMF 546, UPF 548, NSSF 550, NEF 552, NRF 554, PCF 556, UDM 558, and AF 560 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 540 may be briefly introduced as follows. The AUSF 542 may store data for authentication of UE 502 and handle authentication- related functionality. The AUSF 542 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 540 over reference points as shown, the AUSF 542 may exhibit an Nausf service-based interface. The AMF 544 may allow other functions of the 5GC 540 to communicate with the UE 502 and the RAN 504 and to subscribe to notifications about mobility events with respect to the UE 502. The AMF 544 may be responsible for registration management (for example, for registering UE 502), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 544 may provide transport for SM messages between the UE 502 and the SMF 546, and act as a transparent proxy for routing SM messages. AMF 544 may also provide transport for SMS messages between UE 502 and an SMSF. AMF 544 may interact with the AUSF 542 and the UE 502 to perform various security anchor and context management functions. Furthermore, AMF 544 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 504 and the AMF 544; and the AMF 544 may be a termination point of NAS (N1) signaling, and perform NAS ciphering and integrity protection. AMF 544 may also support NAS signaling with the UE 502 over an N3 IWF interface. The SMF 546 may be responsible for SM (for example, session establishment, tunnel management between UPF 548 and AN 508); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 548 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 544 over N2 to AN 508; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 502 and the data network 536. The UPF 548 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 536, and a branching point to support multi-homed PDU session. The UPF 548 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 548 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 550 may select a set of network slice instances serving the UE 502. The NSSF 550 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 550 may also determine the AMF set to be used to serve the UE 502, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 554. The selection of a set of network slice instances for the UE 502 may be triggered by the AMF 544 with which the UE 502 is registered by interacting with the NSSF 550, which may lead to a change of AMF. The NSSF 550 may interact with the AMF 544 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 550 may exhibit an Nnssf service-based interface. The NEF 552 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 560), edge computing or fog computing systems, etc. In such embodiments, the NEF 552 may authenticate, authorize, or throttle the AFs. NEF 552 may also translate information exchanged with the AF 560 and information exchanged with internal network functions. For example, the NEF 552 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 552 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 552 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 552 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 552 may exhibit an Nnef service-based interface. The NRF 554 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 554 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 554 may exhibit the Nnrf service-based interface. The PCF 556 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 556 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 558. In addition to communicating with functions over reference points as shown, the PCF 556 exhibit an Npcf service-based interface. The UDM 558 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 502. For examp'le, subscription data may be communicated via an N8 reference point between the UDM 558 and the AMF 544. The UDM 558 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 558 and the PCF 556, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 502) for the NEF 552. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 558, PCF 556, and NEF 552 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 558 may exhibit the Nudm service-based interface. The AF 560 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control. In some embodiments, the 5GC 540 may enable edge computing by selecting operator/3 rd party services to be geographically close to a point that the UE 502 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 540 may select a UPF 548 close to the UE 502 and execute traffic steering from the UPF 548 to data network 536 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 560. In this way, the AF 560 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 560 is considered to be a trusted entity, the network operator may permit AF 560 to interact directly with relevant NFs. Additionally, the AF 560 may exhibit an Naf service-based interface. The data network 536 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 538. Figure 6 schematically illustrates a wireless network 600 in accordance with various embodiments. The wireless network 600 may include a UE 602 in wireless communication with an AN 604. The UE 602 and AN 604 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 602 may be communicatively coupled with the AN 604 via connection 606. The connection 606 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies. The UE 602 may include a host platform 608 coupled with a modem platform 610. The host platform 608 may include application processing circuitry 612, which may be coupled with protocol processing circuitry 614 of the modem platform 610. The application processing circuitry 612 may run various applications for the UE 602 that source/sink application data. The application processing circuitry 612 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations The protocol processing circuitry 614 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 606. The layer operations implemented by the protocol processing circuitry 614 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 610 may further include digital baseband circuitry 616 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 614 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions. The modem platform 610 may further include transmit circuitry 618, receive circuitry 620, RF circuitry 622, and RF front end (RFFE) 624, which may include or connect to one or more antenna panels 626. Briefly, the transmit circuitry 618 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 620 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 622 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 624 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 618, receive circuitry 620, RF circuitry 622, RFFE 624, and antenna panels 626 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc. In some embodiments, the protocol processing circuitry 614 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components. A UE reception may be established by and via the antenna panels 626, RFFE 624, RF circuitry 622, receive circuitry 620, digital baseband circuitry 616, and protocol processing circuitry 614. In some embodiments, the antenna panels 626 may receive a transmission from the AN 604 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 626. A UE transmission may be established by and via the protocol processing circuitry 614, digital baseband circuitry 616, transmit circuitry 618, RF circuitry 622, RFFE 624, and antenna panels 626. In some embodiments, the transmit components of the UE 604 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 626. Similar to the UE 602, the AN 604 may include a host platform 628 coupled with a modem platform 630. The host platform 628 may include application processing circuitry 632 coupled with protocol processing circuitry 634 of the modem platform 630. The modem platform may further include digital baseband circuitry 636, transmit circuitry 638, receive circuitry 640, RF circuitry 642, RFFE circuitry 644, and antenna panels 646. The components of the AN 604 may be similar to and substantially interchangeable with like-named components of the UE 602. In addition to performing data transmission/reception as described above, the components of the AN 608 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling. Figure 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more memory/storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700. The processors 710 may include, for example, a processor 712 and a processor 714. The processors 710 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof. The memory/storage devices 720 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 720 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 730 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 or other network elements via a network 708. For example, the communication resources 730 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components. Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 710 to perform any one or more of the methodologies discussed herein. The instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within the processor's cache memory), the memory/storage devices 720, or any suitable combination thereof. Furthermore, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 or the databases 706. Accordingly, the memory of processors 710, the memory/storage devices 720, the peripheral devices 704, and the databases 706 are examples of computer-readable and machine-readable media. EXAMPLE PROCEDURES In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 5-7, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 8. In this example, process 800 includes, at 805, receiving, by a user equipment (UE) from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network. The process further includes, at 810, selecting a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. Another such process is depicted in Figure 9. In this example, process 900 includes, at 905, retrieving, from a memory, random access channel (RACH) configuration information included in an information element (IE) received in a message from an a next-generation NodeB (gNB), the RACH configuration information comprising a list of RACH features or feature combinations supported by a network. The process further includes, at 910, selecting a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. Another such process is depicted in Figure 10. In this example, process 1000 includes, at 1005, receiving, from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network. The process further includes, at 1010, selecting a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE, wherein the set of RACH resources is selected based on one or more of: one or more of: a reference signal received power (RSRP) threshold (e.g., corresponding to whether Msg3 repetition is needed for a coverage enhancement (CovEnh) UE), whether the UE is a reduced capability (RedCap) UE, a slice group determined by an upper layer, applicability of small data transmission (SDT) to the UE, and an availability of RACH resources for a cell. For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. EXAMPLES Example 1 may include a method of using the physical random access channel (PRACH) to identify multiple features and/or combinations of features. Example 2 may include the method of example 1 or some other example herein, further comprising receiving the feature specific and combination of features specific PRACH configuration/resources signalled by the network. Example 3 may include the method of examples 1 and 2 or some other example herein, further comprising determining the feature specific and combination of feature specific PRACH configuration/resources possible by the UE Example 4 may include the method of example 3 or some other example herein, wherein determines the feature specific and combination of feature specific PRACH configuration/resources signalled by the network that are subset of the feature specific and combination of feature specific PRACH configuration/resources possible by the UE Example 5 may include the UE of example 4 or some other example herein, wherein the UE determines the PRACH configuration/resources from the subset of the feature specific and combination of feature specific PRACH configuration/resources possible by the UE Example 6 may include the method of example 5 or some other example herein, wherein the UE selects the PRACH configuration/resources from the subset of the feature specific and combination of feature specific PRACH configuration/resources possible by the UE based on UE implementation Example 7 may include the method of example 5 or some other example herein, wherein the UE selects the legacy common PRACH configuration/resources configured in the BWP if no PRACH configuration/resources signalled by the network correspond to the feature combination possible/supported by the UE Example 8 may include the method of example 5 or some other example herein, wherein the UE selects the PRACH configuration/resources corresponding to feature combination based on the maximum number of features matching between the feature combination supported by the cell and the feature combination possible by the UE. Example 9 may include the method of example 5 or some other example herein, wherein the UE selects the PRACH configuration/resources corresponding to feature combination supported by the cell with the highest priority Example 10 may include the UE of example 5 or some other example herein, wherein selects the PRACH configuration/resources corresponding to feature combination using the selection schemes in examples 7, 8 and 9. Example 11 may include the method of example 1 or some other example herein, wherein the network signals the feature specific and combination of features specific PRACH configuration/resources. Example 12 may include the method of example 1 or some other example herein, wherein upon retransmitting PRACH for a certain number of times, the UE performs selection of PRACH configuration/resources corresponding to feature or combinations of features for the fallback from 4-step RACH to 2-step RACH. Example 13 may include the method of example 12 or some other example herein, wherein the UE performs the fallback based a set of fix rules for fallback to Msg1 in the specification common for all feature combination. Example 14 may include the method of example 12 or some other example herein, wherein the UE performs the fallback based on further fallback feature combination rules if the fallback to the feature combination specific 4-step RACH is not available. Example 15 may include the method of example 13 or some other example herein, wherein the UE performs the fallback based on network providing the fallback options for a particular 2-step RACH PRACH configuration/resources Example 16 may include the method of example 13 or some other example herein, wherein the UE performs the fallback based on the PRACH configuration/resource provided by the cell corresponding to the feature combinations that are determined as in example 4 and select the PRACH configuration/resource based on examples 5, 6,7,8 and 10. Example 17 may include the method of example 13 or some other example herein, wherein the UE performs the fallback based on UE implementation. Example X1 includes one or more computer-readable media storing instructions that, when executed by one or more processors, configure a user equipment (UE) to: receive, from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. Example X2 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on a reference signal received power (RSRP) threshold. Example X3 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on whether the UE is a reduced capability (RedCap) UE. Example X4 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on a slice group determined by an upper layer. Example X5 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on applicability of small data transmission (SDT) to the UE. Example X6 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on an availability of RACH resources for a cell. Example X7 includes the one or more computer-readable media of example X1 or some other example herein, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. Example X8 includes the one or more computer-readable media of example X7 or some other example herein, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single feature or a highest aggregated priority for a combination of features. Example X9 includes the one or more computer-readable media of example X1 or some other example herein, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. Example X10 includes the one or more computer-readable media of any of examples X1- X9 or some other example herein, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. Example X11 includes an apparatus of a user equipment (UE) comprising: memory to store random access channel (RACH) configuration information included in an information element (IE) received in a message from an a next-generation NodeB (gNB), the RACH configuration information comprising a list of RACH features or feature combinations supported by a network; and processing circuitry, coupled with the memory, to: retrieve the RACH configuration information from the memory; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE. Example X12 includes the apparatus of example X11 or some other example herein, wherein the set of RACH resources is selected based further on one or more of: a reference signal received power (RSRP) threshold, whether the UE is a reduced capability (RedCap) UE, a slice group determined by an upper layer, applicability of small data transmission (SDT) to the UE, and an availability of RACH resources for a cell. Example X13 includes the apparatus of example X11 or some other example herein, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. Example X14 includes the apparatus of example X13 or some other example herein, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single feature or a highest aggregated priority for a combination of features. Example X15 includes the apparatus of example X11 or some other example herein, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. Example X16 includes the apparatus of any of examples X11-X15 or some other example herein, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. Example X17 includes one or more computer-readable media storing instructions that, when executed by one or more processors, configure a user equipment (UE) to: receive, from a next-generation NodeB (gNB), a message containing an information element (IE) that includes random access channel (RACH) configuration information comprising a list of RACH features or feature combinations supported by a network; and select a set of RACH resources for a RACH procedure based on the RACH configuration information and RACH features or feature combinations supported by the UE, wherein the set of RACH resources is selected based on one or more of: one or more of: a reference signal received power (RSRP) threshold, whether the UE is a reduced capability (RedCap) UE, a slice group determined by an upper layer, applicability of small data transmission (SDT) to the UE, and an availability of RACH resources for a cell. Example X18 includes the one or more computer-readable media of example X17 or some other example herein, wherein the set of RACH resources is selected based further on a predefined prioritization associated with a feature. Example X19 includes the one or more computer-readable media of example X18 or some other example herein, wherein based on the predefined prioritization, the set of RACH resources is selected based on a highest assigned priority for a single resource or highest aggregated priority for a combination of features. Example X20 includes the one or more computer-readable media of example X17 or some other example herein, wherein the IE includes configuration parameters for a feature associated with one or more of: an MsgA transmission; coverage enhancement (CovEnh); slicing; SDT; RedCap; and a RACH preamble. Example X21 includes the one or more computer-readable media of any of examples X17-X20 or some other example herein, wherein the message comprising the IE is received from the gNB via radio resource control (RRC) signaling. Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X21, or any other method or process described herein. Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-X21, or any other method or process described herein. Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X21, or any other method or process described herein. Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X21, or portions or parts thereof. Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof. Example Z06 may include a signal as described in or related to any of examples 1- X21, or portions or parts thereof. Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure. Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure. Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X21, or portions or parts thereof, or otherwise described in the present disclosure. Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof. Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X21, or portions thereof. Example Z12 may include a signal in a wireless network as shown and described herein. Example Z13 may include a method of communicating in a wireless network as shown and described herein. Example Z14 may include a system for providing wireless communication as shown and described herein. Example Z15 may include a device for providing wireless communication as shown and described herein. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments. Abbreviations Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 v16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.
3GPP Third Generation AP Application BRAS Broadband Partnership 35 Protocol, Antenna Remote Access Project Port, Access Point Server 4G Fourth API Application 70 BSS Business 5 Generation Programming Interface Support System 5G Fifth Generation APN Access Point BS Base Station 5GC 5G Core network 40 Name BSR Buffer Status AC ARP Allocation and Report Application Retention Priority 75 BW Bandwidth 10 Client ARQ Automatic BWP Bandwidth Part ACR Application Repeat Request C-RNTI Cell Context Relocation 45 AS Access Stratum Radio Network ACK ASP Temporary Acknowledgeme Application Service 80 Identity 15 nt Provider CA Carrier ACID Aggregation, Application 50 ASN.1 Abstract Syntax Certification Client Identification Notation One Authority AF Application AUSF Authentication 85 CAPEX CAPital 20 Function Server Function EXpenditure AM Acknowledged AWGN Additive CBRA Contention Mode 55 White Gaussian Based Random AMBR Aggregate Noise Access Maximum Bit Rate BAP Backhaul 90 CC Component 25 AMF Access and Adaptation Protocol Carrier, Country Mobility BCH Broadcast Code, Cryptographic Management 60 Channel Checksum Function BER Bit Error Ratio CCA Clear Channel AN Access Network BFD Beam 95 Assessment 30 ANR Automatic Failure Detection CCE Control Channel Neighbour Relation BLER Block Error Rate Element AOA Angle of 65 BPSK Binary Phase CCCH Common Arrival Shift Keying Control Channel 100 CE Coverage Enhancement CDM Content Delivery CoMP Coordinated Resource Network Multi-Point Indicator CDMA Code- CORESET Control C-RNTI Cell Division Multiple Resource Set RNTI 5 Access 40 COTS Commercial Off- 75 CS Circuit Switched CDR Charging Data The-Shelf CSCF call Request CP Control Plane, session control function CDR Charging Data Cyclic Prefix, CSAR Cloud Service Response Connection Archive 10 CFRA Contention Free 45 Point 80 CSI Channel-State Random Access CPD Connection Information CG Cell Group Point Descriptor CSI-IM CSI CGF Charging CPE Customer Interference Gateway Function Premise Measurement 15 CHF Charging 50 Equipment 85 CSI-RS CSI Function CPICH Common Pilot Reference Signal CI Cell Identity Channel CSI-RSRP CSI CID Cell-ID (e.g., CQI Channel Quality reference signal positioning method) Indicator received power 20 CIM Common 55 CPU CSI processing 90 CSI-RSRQ CSI Information Model unit, Central reference signal CIR Carrier to Processing Unit received quality Interference Ratio C/R CSI-SINR CSI CK Cipher Key Command/Respo signal-to-noise and 25 CM Connection 60 nse field bit 95 interference ratio Management, CRAN Cloud Radio CSMA Carrier Sense Conditional Access Network, Multiple Access Mandatory Cloud RAN CSMA/CA CSMA CMAS Commercial CRB Common with collision 30 Mobile Alert Service 65 Resource Block 100 avoidance CMD Command CRC Cyclic CSS Common Search CMS Cloud Redundancy Check Space, Cell- specific Management System CRI Channel-State Search Space CO Conditional Information Resource CTF Charging 35 Optional 70 Indicator, CSI-RS 105 Trigger Function CTS Clear-to-Send DSL Domain Specific 70 ECSP Edge CW Codeword Language. Digital Computing Service CWS Contention Subscriber Line Provider Window Size DSLAM DSL EDN Edge 5 D2D Device-to- 40 Access Multiplexer Data Network Device DwPTS 75 EEC Edge DC Dual Downlink Pilot Enabler Client Connectivity, Direct Time Slot EECID Edge Current E-LAN Ethernet Enabler Client 10 DCI Downlink 45 Local Area Network Identification Control E2E End-to-End 80 EES Edge Information EAS Edge Enabler Server DF Deployment Application Server EESID Edge Flavour ECCA extended clear Enabler Server 15 DL Downlink 50 channel Identification DMTF Distributed assessment, 85 EHE Edge Management Task extended CCA Hosting Environment Force ECCE Enhanced EGMF Exposure DPDK Data Plane Control Channel Governance 20 Development Kit 55 Element, Management DM-RS, DMRS Enhanced CCE 90 Function Demodulation ED Energy EGPRS Enhanced Reference Signal Detection GPRS DN Data network EDGE Enhanced EIR Equipment 25 DNN Data Network 60 Datarates for GSM Identity Register Name Evolution (GSM 95 eLAA enhanced DNAI Data Network Evolution) Licensed Assisted Access Identifier EAS Edge Access, Application Server enhanced LAA 30 DRB Data Radio 65 EASID Edge EM Element Bearer Application Server 100 Manager DRS Discovery Identification eMBB Enhanced Reference Signal ECS Edge Mobile DRX Discontinuous Configuration Server Broadband 35 Reception EMS Element E-UTRAN Evolved FDM Frequency Management System UTRAN Division Multiplex eNB evolved NodeB, EV2X Enhanced V2X FDMA Frequency E-UTRAN Node B F1AP F1 Application Division Multiple 5 EN-DC E- 40 Protocol 75 Access UTRA-NR Dual F1-C F1 Control plane FE Front End Connectivity interface FEC Forward Error EPC Evolved Packet F1-U F1 User plane Correction Core interface FFS For Further 10 EPDCCH enhanced 45 FACCH Fast 80 Study PDCCH, enhanced Associated Control FFT Fast Fourier Physical CHannel Transformation Downlink Control FACCH/F Fast feLAA further enhanced Cannel Associated Control Licensed Assisted 15 EPRE Energy per 50 Channel/Full 85 Access, further resource element rate enhanced LAA EPS Evolved Packet FACCH/H Fast FN Frame Number System Associated Control FPGA Field- EREG enhanced REG, Channel/Half Programmable Gate 20 enhanced resource 55 rate 90 Array element groups FACH Forward Access FR Frequency ETSI European Channel Range Telecommunicat FAUSCH Fast FQDN Fully Qualified ions Standards Uplink Signalling Domain Name 25 Institute 60 Channel 95 G-RNTI GERAN ETWS Earthquake and FB Functional Block Radio Network Tsunami Warning FBI Feedback Temporary System Information Identity eUICC embedded FCC Federal GERAN 30 UICC, embedded 65 Communications 100 GSM EDGE Universal Commission RAN, GSM EDGE Integrated Circuit FCCH Frequency Radio Access Card Correction CHannel Network E-UTRA Evolved FDD Frequency GGSN Gateway GPRS 35 UTRA 70 Division Duplex 105 Support Node GLONASS 35 GTP-U GPRS 70 HSUPA High GLObal'naya Tunnelling Protocol Speed Uplink Packet NAvigatsionnay for User Plane Access a Sputnikovaya GTS Go To Sleep HTTP Hyper Text 5 Sistema (Engl.: Signal (related to Transfer Protocol Global Navigation 40 WUS) 75 HTTPS Hyper Satellite System) GUMMEI Globally Text Transfer Protocol gNB Next Generation Unique MME Identifier Secure (https is NodeB GUTI Globally Unique http/1.1 over10 gNB-CU gNB- Temporary UE SSL, i.e. port 443) centralized unit, Next 45 Identity 80 I-Block Generation HARQ Hybrid ARQ, Information NodeB Hybrid Block centralized unit Automatic ICCID Integrated15 gNB-DU gNB- Repeat Request Circuit Card distributed unit, Next 50 HANDO Handover 85 Identification Generation HFN HyperFrame IAB Integrated NodeB Number Access and Backhaul distributed unit HHO Hard Handover ICIC Inter-Cell 20 GNSS Global HLR Home Location Interference Navigation Satellite 55 Register 90 Coordination System HN Home Network ID Identity, GPRS General Packet HO Handover identifier Radio Service HPLMN Home IDFT Inverse Discrete 25 GPSI Generic Public Land Mobile Fourier Public Subscription 60 Network 95 Transform Identifier HSDPA High IE Information GSM Global System Speed Downlink element for Mobile Packet Access IBE In-Band30 Communications HSN Hopping Emission , Groupe Spécial 65 Sequence Number 100 IEEE Institute of Mobile HSPA High Speed Electrical and GTP GPRS Tunneling Packet Access Electronics Protocol HSS Home Engineers Subscriber Server IEI Information Ipsec IP Security, 70 kB Kilobyte (1000 Element Identifier Internet Protocol bytes) IEIDL Information Security kbps kilo-bits per Element Identifier IP-CAN IP- second 5 Data Length 40 Connectivity Access Kc Ciphering key IETF Internet Network 75 Ki Individual Engineering Task IP-M IP Multicast subscriber Force IPv4 Internet Protocol authentication IF Infrastructure Version 4 key 10 IIOT Industrial 45 IPv6 Internet Protocol KPI Key Internet of Things Version 6 80 Performance Indicator IM Interference IR Infrared KQI Key Quality Measurement, IS In Sync Indicator Intermodulation, IRP Integration KSI Key Set 15 IP Multimedia 50 Reference Point Identifier IMC IMS Credentials ISDN Integrated 85 ksps kilo-symbols per IMEI International Services Digital second Mobile Network KVM Kernel Virtual Equipment ISIM IM Services Machine 20 Identity 55 Identity Module L1 Layer 1 IMGI International ISO International 90 (physical layer) mobile group identity Organisation for L1-RSRP Layer 1 IMPI IP Multimedia Standardisation reference signal Private Identity ISP Internet Service received power 25 IMPU IP Multimedia 60 Provider L2 Layer 2 (data PUblic identity IWF Interworking- 95 link layer) IMS IP Multimedia Function L3 Layer 3 (network Subsystem I-WLAN layer) IMSI International Interworking LAA Licensed 30 Mobile 65 WLAN Assisted Access Subscriber Constraint length 100 LAN Local Area Identity of the convolutional Network IoT Internet of code, USIM LADN Local Things Individual key Area Data Network 35 IP Internet Protocol LBT Listen Before MAC Medium Access 70 MCOT Maximum Talk Control (protocol Channel LCM LifeCycle layering context) Occupancy Time Management MAC Message MCS Modulation and 5 LCR Low Chip Rate 40 authentication code coding scheme LCS Location (security/encryption 75 MDAF Management Services context) Data Analytics LCID Logical MAC-A MAC Function Channel ID used for MDAS Management 10 LI Layer Indicator 45 authentication Data Analytics LLC Logical Link and key 80 Service Control, Low Layer agreement (TSG MDT Minimization of Compatibility T WG3 context) Drive Tests LMF Location MAC-I MAC used for ME Mobile 15 Management Function 50 data integrity of Equipment LOS Line of signalling messages 85 MeNB master eNB Sight (TSG T WG3 context) MER Message Error LPLMN Local MANO Ratio PLMN Management and MGL Measurement 20 LPP LTE Positioning 55 Orchestration Gap Length Protocol MBMS 90 MGRP Measurement LSB Least Significant Multimedia Gap Repetition Bit Broadcast and Multicast Period LTE Long Term Service MIB Master 25 Evolution 60 MBSFN Information Block, LWA LTE-WLAN Multimedia 95 Management aggregation Broadcast multicast Information Base LWIP LTE/WLAN service Single MIMO Multiple Input Radio Level Frequency Multiple Output 30 Integration with 65 Network MLC Mobile Location IPsec Tunnel MCC Mobile Country 100 Centre LTE Long Term Code MM Mobility Evolution MCG Master Cell Management M2M Machine-to- Group MME Mobility 35 Machine Management Entity MN Master Node MSIN Mobile Station NE-DC NR-E- MNO Mobile Identification 70 UTRA Dual Network Operator Number Connectivity MO Measurement MSISDN Mobile NEF Network 5 Object, Mobile 40 Subscriber ISDN Exposure Function Originated Number NF Network MPBCH MTC MT Mobile 75 Function Physical Broadcast Terminated, Mobile NFP Network CHannel Termination Forwarding Path 10 MPDCCH MTC 45 MTC Machine-Type NFPD Network Physical Downlink Communications Forwarding Path Control CHannel mMTC massive MTC, 80 Descriptor MPDSCH MTC massive Machine- NFV Network Physical Downlink Type Communications Functions 15 Shared CHannel 50 MU-MIMO Multi Virtualization MPRACH MTC User MIMO NFVI NFV Physical Random MWUS MTC 85 Infrastructure Access CHannel wake-up signal, MTC NFVO NFV MPUSCH MTC WUS Orchestrator 20 Physical Uplink Shared 55 NACK Negative NG Next Generation, Channel Acknowledgement Next Gen MPLS MultiProtocol NAI Network Access 90 NGEN-DC NG-RAN Label Switching Identifier E-UTRA-NR Dual MS Mobile Station NAS Non-Access Connectivity 25 MSB Most Significant 60 Stratum, Non- Access NM Network Bit Stratum layer Manager MSC Mobile NCT Network 95 NMS Network Switching Centre Connectivity Topology Management System MSI Minimum NC-JT Non- N-PoP Network Point of 30 System 65 Coherent Joint Presence Information, Transmission NMIB, N-MIB MCH Scheduling NEC Network 100 Narrowband MIB Information Capability Exposure NPBCH MSID Mobile Station Narrowband 35 Identifier Physical Broadcast NSA Non-Standalone 70 OSI Other System CHannel operation mode Information NPDCCH NSD Network Service OSS Operations Narrowband Descriptor Support System 5 Physical 40 NSR Network Service OTA over-the-air Downlink Record 75 PAPR Peak-to-Average Control CHannel NSSAI Network Slice Power Ratio NPDSCH Selection PAR Peak to Average Narrowband Assistance Ratio 10 Physical 45 Information PBCH Physical Downlink S-NNSAI Single- 80 Broadcast Channel Shared CHannel NSSAI PC Power Control, NPRACH NSSF Network Slice Personal Narrowband Selection Function Computer 15 Physical Random 50 NW Network PCC Primary Access CHannel NWUS Narrowband 85 Component Carrier, NPUSCH wake-up signal, Primary CC Narrowband Narrowband WUS P-CSCF Proxy Physical Uplink NZP Non-Zero Power CSCF 20 Shared CHannel 55 O&M Operation and PCell Primary Cell NPSS Narrowband Maintenance 90 PCI Physical Cell ID, Primary ODU2 Optical channel Physical Cell Synchronization Data Unit - type 2 Identity Signal OFDM Orthogonal PCEF Policy and 25 NSSS Narrowband 60 Frequency Division Charging Secondary Multiplexing 95 Enforcement Synchronization OFDMA Function Signal Orthogonal PCF Policy Control NR New Radio, Frequency Division Function 30 Neighbour Relation 65 Multiple Access PCRF Policy Control NRF NF Repository OOB Out-of-band 100 and Charging Rules Function OOS Out of Sync Function NRS Narrowband OPEX OPerating PDCP Packet Data Reference Signal EXpense Convergence Protocol, 35 NS Network Service Packet Data Convergence PNFD Physical 70 PSCCH Physical Protocol layer Network Function Sidelink Control PDCCH Physical Descriptor Channel Downlink Control PNFR Physical PSSCH Physical 5 Channel 40 Network Function Sidelink Shared PDCP Packet Data Record 75 Channel Convergence Protocol POC PTT over PSCell Primary SCell PDN Packet Data Cellular PSS Primary Network, Public PP, PTP Point-to- Synchronization 10 Data Network 45 Point Signal PDSCH Physical PPP Point-to-Point 80 PSTN Public Switched Downlink Shared Protocol Telephone Network Channel PRACH Physical PT-RS Phase-tracking PDU Protocol Data RACH reference signal 15 Unit 50 PRB Physical PTT Push-to-Talk PEI Permanent resource block 85 PUCCH Physical Equipment PRG Physical Uplink Control Identifiers resource block Channel PFD Packet Flow group PUSCH Physical 20 Description 55 ProSe Proximity Uplink Shared P-GW PDN Gateway Services, 90 Channel PHICH Physical Proximity-Based QAM Quadrature hybrid-ARQ indicator Service Amplitude channel PRS Positioning Modulation 25 PHY Physical layer 60 Reference Signal QCI QoS class of PLMN Public Land PRR Packet 95 identifier Mobile Network Reception Radio QCL Quasi co- PIN Personal PS Packet Services location Identification Number PSBCH Physical QFI QoS Flow ID, 30 PM Performance 65 Sidelink Broadcast QoS Flow Identifier Measurement Channel 100 QoS Quality of PMI Precoding PSDCH Physical Service Matrix Indicator Sidelink Downlink QPSK Quadrature PNF Physical Channel (Quaternary) Phase 35 Network Function Shift Keying QZSS Quasi-Zenith RL Radio Link 70 RRC Radio Resource Satellite System RLC Radio Link Control, Radio RA-RNTI Random Control, Radio Resource Control Access RNTI Link Control layer 5 RAB Radio Access 40 layer RRM Radio Resource Bearer, Random RLC AM RLC 75 Management Access Burst Acknowledged Mode RS Reference Signal RACH Random Access RLC UM RLC RSRP Reference Signal Channel Unacknowledged Mode Received Power 10 RADIUS Remote 45 RLF Radio Link RSRQ Reference Signal Authentication Dial In Failure 80 Received Quality User Service RLM Radio Link RSSI Received Signal RAN Radio Access Monitoring Strength Indicator Network RLM-RS RSU Road Side Unit 15 RAND RANDom 50 Reference Signal RSTD Reference Signal number (used for for RLM 85 Time difference authentication) RM Registration RTP Real Time RAR Random Access Management Protocol Response RMC Reference RTS Ready-To-Send 20 RAT Radio Access 55 Measurement Channel RTT Round Trip Technology RMSI Remaining MSI, 90 Time RAU Routing Area Remaining Rx Reception, Update Minimum Receiving, Receiver RB Resource block, System S1AP S1 Application 25 Radio Bearer 60 Information Protocol RBG Resource block RN Relay Node 95 S1-MME S1 for the group RNC Radio Network control plane REG Resource Controller S1-U S1 for the user Element Group RNL Radio Network plane 30 Rel Release 65 Layer S-CSCF serving REQ REQuest RNTI Radio Network 100 CSCF RF Radio Frequency Temporary Identifier S-GW Serving Gateway RI Rank Indicator ROHC RObust Header S-RNTI SRNC RIV Resource Compression Radio Network 35 indicator value Temporary SDAP Service Data SI System Identity Adaptation Protocol, Information S-TMSI SAE Service Data SI-RNTI System Temporary Mobile Adaptation Information RNTI 5 Station Identifier 40 Protocol layer 75 SIB System SA Standalone SDL Supplementary Information Block operation mode Downlink SIM Subscriber SAE System SDNF Structured Data Identity Module Architecture Evolution Storage Network SIP Session Initiated 10 SAP Service Access 45 Function 80 Protocol Point SDP Session SiP System in SAPD Service Access Description Protocol Package Point Descriptor SDSF Structured Data SL Sidelink SAPI Service Access Storage Function SLA Service Level 15 Point Identifier 50 SDT Small Data 85 Agreement SCC Secondary Transmission SM Session Component Carrier, SDU Service Data Management Secondary CC Unit SMF Session SCell Secondary Cell SEAF Security Anchor Management Function 20 SCEF Service 55 Function 90 SMS Short Message Capability Exposure SeNB secondary eNB Service Function SEPP Security Edge SMSF SMS Function SC-FDMA Single Protection Proxy SMTC SSB-based Carrier Frequency SFI Slot format Measurement Timing 25 Division 60 indication 95 Configuration Multiple Access SFTD Space-Frequency SN Secondary Node, SCG Secondary Cell Time Diversity, SFN Sequence Number Group and frame timing SoC System on Chip SCM Security Context difference SON Self-Organizing 30 Management 65 SFN System Frame 100 Network SCS Subcarrier Number SpCell Special Cell Spacing SgNB Secondary gNB SP-CSI-RNTISemi- SCTP Stream Control SGSN Serving GPRS Persistent CSI RNTI Transmission Support Node SPS Semi-Persistent 35 Protocol 70 S-GW Serving Gateway 105 Scheduling SQN Sequence Signal based Signal to TCP Transmission number Noise and Interference 70 Communication SR Scheduling Ratio Protocol Request SSS Secondary TDD Time Division 5 SRB Signalling Radio 40 Synchronization Duplex Bearer Signal TDM Time Division SRS Sounding SSSG Search Space Set 75 Multiplexing Reference Signal Group TDMA Time Division SS Synchronization SSSIF Search Space Set Multiple Access 10 Signal 45 Indicator TE Terminal SSB Synchronization SST Slice/Service Equipment Signal Block Types 80 TEID Tunnel End SSID Service Set SU-MIMO Single Point Identifier Identifier User MIMO TFT Traffic Flow 15 SS/PBCH Block 50 SUL Supplementary Template SSBRI SS/PBCH Block Uplink TMSI Temporary Resource Indicator, TA Timing 85 Mobile Synchronization Advance, Tracking Subscriber Signal Block Area Identity 20 Resource Indicator 55 TAC Tracking Area TNL Transport SSC Session and Code Network Layer Service TAG Timing Advance 90 TPC Transmit Power Continuity Group Control SS-RSRP TAI Tracking TPMI Transmitted 25 Synchronization 60 Area Identity Precoding Matrix Signal based TAU Tracking Area Indicator Reference Signal Update 95 TR Technical Report Received Power TB Transport Block TRP, TRxP SS-RSRQ TBS Transport Block Transmission 30 Synchronization 65 Size Reception Point Signal based TBD To Be Defined TRS Tracking Reference Signal TCI Transmission 100 Reference Signal Received Quality Configuration Indicator TRx Transceiver SS-SINR TS Technical 35 Synchronization Specifications, Technical 35 UMTS Universal 70 V2X Vehicle-to- Standard Mobile everything TTI Transmission Telecommunicat VIM Virtualized Time Interval ions System Infrastructure Manager 5 Tx Transmission, UP User Plane VL Virtual Link, Transmitting, 40 UPF User Plane 75 VLAN Virtual LAN, Transmitter Function Virtual Local Area U-RNTI UTRAN URI Uniform Network Radio Network Resource Identifier VM Virtual Machine 10 Temporary URL Uniform VNF Virtualized Identity 45 Resource Locator 80 Network Function UART Universal URLLC Ultra- VNFFG VNF Asynchronous Reliable and Low Forwarding Graph Receiver and Latency VNFFGD VNF 15 Transmitter USB Universal Serial Forwarding Graph UCI Uplink Control 50 Bus 85 Descriptor Information USIM Universal VNFM VNF Manager UE User Equipment Subscriber Identity VoIP Voice-over-IP, UDM Unified Data Module Voice-over- Internet 20 Management USS UE-specific Protocol UDP User Datagram 55 search space 90 VPLMN Visited Protocol UTRA UMTS Public Land Mobile UDSF Unstructured Terrestrial Radio Network Data Storage Network Access VPN Virtual Private 25 Function UTRAN Universal Network UICC Universal 60 Terrestrial Radio 95 VRB Virtual Resource Integrated Circuit Access Network Block Card UwPTS Uplink WiMAX UL Uplink Pilot Time Slot Worldwide30 UM V2I Vehicle-to- Interoperability Unacknowledge 65 Infrastruction 100 for Microwave d Mode V2P Vehicle-to- Access UML Unified Pedestrian WLANWireless Local Modelling Language V2V Vehicle-to- Area Network Vehicle WMAN Wireless Metropolitan Area Network WPAN Wireless 5 Personal Area Network X2-C X2-Control plane X2-U X2-User plane XML eXtensible 10 Markup Language XRES EXpected user RESponse XOR eXclusive OR ZC Zadoff-Chu 15 ZP Zero Power
Terminology For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein. The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer- executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.” The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface. The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like. The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources. The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource. The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable. The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information. The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code. The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content. The term “SMTC” refers to an SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation. The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA. The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/. The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.
Next Patent: METHOD FOR MANUFACTURING A BUNK FOR A VEHICLE