Preconfigured measurement gap status indication to a user equipment (UE)

Abstract

Various embodiments herein provide techniques for a user equipment (UE). In embodiments, the UE may identify an occurrence of a triggering event associated with a configured pre-configured measurement gap (pre-MG). Further, the UE may check the status of the configured pre-MG based on the occurrence of the triggering event. Further, the UE may change the status of the configured pre-MG based on the occurrence of the triggering event. Other embodiments may be described and / or claimed.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 300,559, filed January 18, 2022.

[0002] Various embodiments may generally relate to the field of wireless communications. For example, some embodiments may relate to preconfigured measurement gaps (MGs) in cellular networks. In particular, some embodiments may relate to providing an indication of the status of a preconfigured MG to a user equipment (UE). [Background technology]

[0003] Various embodiments may relate generally to the field of wireless communications. [Brief description of the drawings]

[0004] BRIEF DESCRIPTION OF THE DRAWINGS The embodiments will be readily understood by the following detailed description taken in conjunction with the accompanying drawings, in which: To facilitate this description, like reference numerals indicate like structural elements, and in which: FIG.

[0005] [Figure 1] 1 is a schematic diagram of a wireless network in accordance with various embodiments. [Diagram 2] 1 is a schematic diagram of a wireless network in accordance with various embodiments. [Diagram 3] 1 is a schematic diagram of components of a wireless network in accordance with various embodiments. [Figure 4] FIG. 1 is a block diagram illustrating components that can read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) according to some exemplary embodiments and perform any one or more of the methods described herein. [Diagram 5] 1 is a schematic diagram of an alternative wireless network in accordance with various embodiments. [Figure 6]1 depicts an example technique in accordance with various embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0006] The following detailed description refers to the accompanying drawings. In different drawings, the same reference numbers may be used to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth, such as certain structures, architectures, interfaces, techniques, etc., to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to one of ordinary skill in the art having the benefit of this disclosure that various aspects of the various embodiments may be implemented in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For purposes of this specification, the phrases "A or B" and "A / B" mean (A), (B), or (A and B).

[0007] The 3rd Generation Partnership Project (3GPP®) has agreed to the following regarding New Radio (NR) MG: Triggering events that can change the activation status of a pre-MG configured in the UE include: - BWP Switching - Add / remove measurement target: FFS - Add / release / change SCell: FFS - Activate / deactivate any Scell:FFS - LPP positioning request: FFS

[0008] Radio Resource Control (RRC) Message Triggering Events The triggering event may be based on RRC signaling. Figure 1 shows an example of how one such condition may be triggered. Specifically, Figure 1 shows how a change in measurement object (MO) may serve as a triggering event. As shown in 101, the UE is initially configured with MO#1, which is included in the UE active BWP indication. In this case, the pre-MG may be off (deactivated) since the UE can perform measurements outside of the MG. In 202, the UE's MO is changed to MO#2, which is outside of the UE's activated BWP. In 103, the pre-MG may need to be activated since the UE may be able to measure MOs (e.g., #MO2) configured only in the MG.

[0009] Based on a triggering event, such as a change in the MO shown in FIG. 1, or some other condition described herein, possible UE behavior may be as follows:

[0010] Case 1 If the newly configured MO cannot be measured by the UE without the MG, the NW may provide an indication of the new legacy MG to the UE (i.e., "reconfigure") at the same time as providing an indication of the MO addition / release / modification. For example, one implementation of a configuration message (e.g., an RRC message) may be as follows (below, the newly introduced elements related to the MG configuration indication are provided in italics): MeasConfig::= SEQUENCE { measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, --Need N(italics) measObjectToAddModList MeasObjectToAddModList (italics) OPTIONAL, --Need N reportConfigToRemoveList ReportConfigToRemoveList OPTIONAL, --Need N reportConfigToAddModList ReportConfigToAddModList OPTIONAL, --Need N measIdToRemoveList MeasIdToRemoveList OPTIONAL, --Need N measIdToAddModList MeasIdToAddModList OPTIONAL, --Need N s-MeasureConfig CHOICE ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range } OPTIONAL, --Need M quantityConfig QuantityConfig OPTIONAL, --Need M measGapConfig MeasGapConfig (italic) OPTIONAL, --Need M(italics) measGapSharingConfig MeasGapSharingConfig OPTIONAL, --Need M ..., [[ interFrequencyConfig-NoGap-r16 ENUMERATED{true} OPTIONAL --Need R ]] } measGapConfig{(italics) Updated to legacy MG that can be activated immediately after configuration (italics) }(italic)

[0011] Case 2 If the newly configured MO cannot be measured by the UE without the MG, the NW may provide the UE with an indication of the pre-configured MG simultaneously with an indication of the MO addition / release / change. - In case of pre-MG with signaling-based (non-)activation status, the NW may update the bandwidth per part (BWP) status indication to the UE in the same RRCReconfiguration information element (IE) used to indicate the pre-MG configuration and changes to the MO. Upon receiving the RRCReconfiguration IE, the terminal can check the pre-MG state. - In case of a pre-MG with rule-based (de)activation status, when the UE receives an RRCReconfiguration IE containing an indication for pre-MG configuration, the UE may be able to autonomously identify the pre-MG status. This identification may be similar to the technique by which the UE can identify the pre-MG initial state when the pre-MG is first configured.

[0012] Case 3 Updates to the MG pre-configuration are not sent in the same RRCReconfiguration IE with the MO change indication. In situations where pre-MG activation or deactivation is signaling-based, this case may result from an incorrect NW implementation, since at least the pre-MG status indication may need to be updated and forwarded to the UE, for example, by an RRC message for pre-MG configuration. In situations where pre-MG activation or deactivation is rule-based, it may be desirable for the UE to check for potential MG status changes if the RRCReconfiguration IE contains an indication for an MO change but not for a pre-MG reconfiguration. In other words, for a UE to support rule-based pre-MG activation, it may be desirable for the UE to autonomously check the pre-MG status when there is any RRCReconfiguration IE related to changes to the MO, primary secondary cell (PSCell), and / or BWP. For example, based on the changes to the MO, PSCell, and / or BWP, the UE may identify that it should check the pre-MG status.

[0013] Exemplary embodiments Thus, to address one or more of Cases 1-3, aspects of various embodiments herein may include one or more of the following:

[0014] - Triggering events for the UE to check the pre-MG status after initial pre-MG configuration may include one or more of the following (note that these are intended as examples of such triggering events, and other embodiments may include additional / alternative triggering events): - BWP switching based on receipt of Downlink Control Information (DCI) and / or timer expiry - Activation or deactivation of one or more SCells (e.g., PSCells)

[0015] The NW may use the RRCReconfiguration IE to update the pre-MG configuration when the RRCReconfiguration IE is sent for one or more of the following example events: Based on receipt of the IE, the UE may be able to identify the pre-MG state based on requirements similar to those used to review the pre-MG initial state when the pre-MG is initially configured. The events for performing such an identification may include one or more of the following: - Add / remove one or more MOs - Adding / releasing / changing PSCell under Carrier Aggregation (CA) - BWP Switching

[0016] System and Implementation 2-5 illustrate various systems, devices and components in which aspects of the disclosed embodiments may be implemented.

[0017] 2 illustrates a network 200 according to various embodiments. Network 200 may operate in a manner compliant with 3GPP technical standards for LTE or 5G / NR systems. However, example embodiments are not limited in this respect and the described embodiments may be applied to other networks that would benefit from the principles described herein, such as future 3GPP systems.

[0018] The network 200 may include a UE 202, where the UE 120 may include any mobile or non-mobile computing device designed to communicate with a RAN 204 over a wireless connection. The UE 202 may be communicatively coupled to the RAN 204 by a Uu interface. The UE 202 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.

[0019] In some embodiments, the network 200 may include multiple UEs directly coupled to each other 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.

[0020] In some embodiments, the UE 202 may further communicate with the AP 206 via an over-the-air connection. The AP 206 may manage a WLAN connection, which may serve to offload some / all network traffic from the RAN 204. The connection between the UE 202 and the AP 206 may conform to any IEEE 802.11 protocol, and the AP 206 may be a Wireless Fidelity (Wi-Fi) router. In some embodiments, the UE 202, the RAN 204, and the AP 206 may utilize cellular-WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve the UE 202 being configured by the RAN 204 to utilize both cellular radio resources and WLAN resources.

[0021] The RAN 204 may include one or more access nodes, e.g., the AN 208. The AN 208 may terminate the air interface protocols for the UE 202 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 208 may enable data / voice connectivity between the CN 220 and the UE 202. In some embodiments, the AN 208 may be implemented as one or more software entities running on a server computer, in a separate device, or as part of a virtual network, which may be referred to as, for example, a CRAN or a virtual baseband unit pool. The AN 208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 208 may be a macrocell base station, or a low-power base station to provide a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0022] In embodiments where the RAN 204 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2 / Xn interface, which in some embodiments may be separated into a control / user plane interface, may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, and the like.

[0023] The ANs of the RAN 204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 202 with an air interface for network access. The UE 202 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 204. For example, the UE 202 and the RAN 204 may use carrier aggregation to enable the UE 202 to connect with multiple component carriers, each corresponding to a Pcell or an Scell. In a dual connection scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0024] The RAN 204 may provide an air interface via a licensed or unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on carrier aggregation techniques using PCell / SCell. Prior to accessing the unlicensed spectrum, the node may perform a medium / carrier sensing operation, for example, based on a listen-before-talk (LBT) protocol.

[0025] In a V2X scenario, the UE 202 or AN 208 may be or act as an RSU, where an RSU may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by an appropriate 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 so on. In one example, an RSU is a computing device coupled to a radio frequency circuit located at the roadside that provides connectivity support to passing vehicular UEs. The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications necessary for high speed events such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components 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.

[0026] In some embodiments, the RAN 204 may be an LTE RAN 210 having an eNB, e.g., an eNB 212. The LTE RAN 210 may provide an LTE air interface with the following characteristics: SCS 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 collection and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell search and initial collection, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0027] In some embodiments, the RAN 204 may be an NG-RAN 214 having a gNB, e.g., gNB 216, or an ng-eNB, e.g., ng-eNB 218. The gNB 216 may connect with a 5G-capable UE using a 5G NR interface. The gNB 216 may connect with a 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 218 may connect with a UE via an LTE air interface, although it may also connect with the 5G core via an NG interface. The gNB 216 and the ng-eNB 218 may connect with each other via an Xn interface.

[0028] In some embodiments, the NG interface may be divided into two parts: an NG User Plane (NG-U) interface, which carries traffic data between nodes of the NG-RAN 214 and the UPF 248 (e.g., the N3 interface), and an NG Control Plane (NG-C) interface, which is a signaling interface between nodes of the NG-RAN 214 and the AMF 244 (e.g., the N2 interface).

[0029] The NG-RAN 214 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, repetitive, 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 CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and tracking reference signals for time tracking. The 5G-NR air interface may operate on the FR1 band, which includes sub-6 GHz bands, or the FR2 band, which includes bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid that includes PSS / SSS / PBCH.

[0030] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of the SCS. For example, the UE 202 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 202, the SCS of the transmission is also changed. Another example use case of BWPs relates to power savings. In particular, multiple BWPs may be configured for a UE 202 with different amounts of frequency resources (e.g., PRBs) to support data transmissions under different traffic load scenarios. A BWP that includes a smaller number of PR Bs may be used for data transmissions with a small traffic load while enabling power savings at the UE 202 and possibly at the gNB 216. A BWP that includes more PR Bs may be used for scenarios with a higher traffic load. The RAN 204 is communicatively coupled to the CN 220, which includes network elements for providing various functions to support data and telecommunication services to customers / subscribers (e.g., users of UEs 202). The components of the CN 220 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 220 onto physical computation / storage resources in servers, switches, etc. A logical instantiation of the CN 220 may be referred to as a network slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network sub-slice.

[0031] In some embodiments, the CN 220 may be an LTE CN 222, which may also be referred to as an EPC. The LTE CN 222 may include an MME 224, an SGW 226, an SGSN 228, an HSS 230, a PGW 232, and a PCRF 234, which are coupled to each other via interfaces (or "reference points") as shown. The functionality of the elements of the LTE CN 222 may be briefly introduced as follows.

[0032] The MME 224 may implement mobility management functions to track the current location of the UE 202 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0033] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the LTE CN 222. The SGW 226 may be a local mobility anchor point for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0034] The SGSN 228 may track the location of the UE 202 and perform security functions and access control to and from administrative areas. In addition, the SGSN 228 may perform EPC inter-node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME 224, MME selection for handover, etc. The S3 reference point between the MME 224 and the SGSN 228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active state.

[0035] The HSS 230 may include a database for network users, including subscription-related information to support processing of communication sessions of the network entities. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS 230 and the MME 224 may enable transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN 220.

[0036] The PGW 232 may terminate an SGi interface towards a data network (DN) 236, which may include an application / content server 238. The PGW 232 may route data packets between the LTE CN 222 and the data network 236. The PGW 232 may be coupled to the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 232 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. Furthermore, the SGi reference point between the PGW 232 and the data network 236 may be an operator external public, private PDN, or intra-operator packet data network, for example, for the provision of IMS services. The PGW 232 may be coupled to the PCRF 234 via a Gx reference point.

[0037] The PCRF 234 is the policy and charging control element of the LTE CN 222. The PCRF 234 may be communicatively coupled to an application / content server 238 to determine appropriate QoS and charging parameters for a service flow. The PCRF 232 may provision the PCEF (over the Gx reference point) with the appropriate TFT and QCI and associated rules.

[0038] In some embodiments, CN 220 may be a 5 GC 240. 5 GC 240 may include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled together via interfaces (or "reference points") as shown. The functionality of the elements of 5 GC 240 may be briefly introduced as follows.

[0039] The AUSF 242 may store data and process authentication related functionality for authentication of the UE 202. The AUSF 242 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5 GC 240 via reference points as shown, the AUSF 242 may exhibit a Nausf service-based interface.

[0040] The AMF 244 may enable other functions of the 5 GC 240 to communicate with the UE 202 and the RAN 204 and subscribe to notifications about mobility events for the UE 202. The AMF 244 may be responsible for registration management (e.g., for registering the UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 244 may provide transport for SM messages between the UE 202 and the SMF 246 and act as a transparent proxy for routing SM messages. The AMF 244 may also provide transport for SMS messages between the UE 202 and the SMSF. The AMF 244 may interact with the AUSF 242 and the UE 202 and perform various security anchor and context management functions. Additionally, the AMF 244 may be a termination point of the RAN CP interface and may include or be an N2 reference point between the RAN 204 and the AMF 244, and the AMF 244 may be a termination point of NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 244 may also support NAS signaling with the UE 202 over an N3 IWF interface.

[0041] The SMF 246 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 248 and the AN 208), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuring traffic steering in the UPF 248 to route traffic to the appropriate destination, terminating the interface towards the policy control function, controlling policy enforcement, charging, and parts of QoS, lawful interception (for SM events and the interface towards the L1 system), terminating the SM part of NAS messages, downlink data notification, initiating AN specific SM information sent via the AMF 244 to the AN 208 over N2, and determining the SSC mode of the session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connection service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.

[0042] The UPF 248 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnection to the data network 236, and a branching point for supporting multi-homed PDU sessions. The UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF-to-QoS flow mapping), perform transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 248 may include an uplink classifier to support routing of traffic flows to the data network.

[0043] The NSSF 250 may select a set of network slice instances to serve the UE 202. The NSSF 250 may also determine the allowed NSSAI and mapping to the subscribed S-NSSAI, if necessary. The NSSF 250 may also determine the AMF set to be used to serve the UE 202, or a list of candidate AMFs based on appropriate configuration and possibly by querying the NRF 254. The selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 to which the UE 202 is registered, by interacting with the NSSF 250, which may lead to a change of the AMF. The NSSF 250 may interact with the AMF 244 over the N22 reference point and may communicate with another NSSF in the visited network over the N31 reference point (not shown). Additionally, the NSSF 250 may exhibit an Nnssf service-based interface.

[0044] The NEF 252 can securely expose services and capabilities offered by 3 GPP network functions for third parties, internal publication / re-publication, AFs (e.g., AF 260), edge computing or fog computing systems, etc. In such an embodiment, the NEF 252 can authenticate, authorize, or throttle AFs. The NEF 252 can also translate information exchanged with the AF 260 and information exchanged with internal network functions. For example, the NEF 252 can translate between AF service identifiers and internal 5 GC information. The NEF 252 can also receive information from other NFs based on the published capabilities of the other NFs. This information can be stored in the NEF 252 as structured data or in the data storage NF using a standardized interface. The stored information can then be re-published by the NEF 252 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 252 can exhibit Nnef service-based interfaces.

[0045] NRF 254 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 254 also maintains information of available NF instances and their supported services. As used herein, terms such as "instantiate," "instance," and the like, may refer to the creation of an instance, and "instance" may refer to a concrete occurrence of an object that may occur, for example, during the execution of program code. Additionally, NRF 254 may exhibit an Nnrf service-based interface.

[0046] The PCF 256 may provide policy rules to control and enforce plane functions and may also support a unified policy framework for managing network behavior. The PCF 256 may also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 258. As shown, in addition to communicating with functions via reference points, the PCF 256 exhibits an Npcf service-based interface.

[0047] The UDM 258 may process subscription-related information to support processing of communication sessions of the network entities and may store subscription data of the UE 202. For example, the subscription data may be communicated over the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 may include two parts: an application front-end and a UDR. The UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for exposure and application data (including PFD for application discovery, application request information for multiple UEs 202) for the NEF 252. A Nudr service-based interface may be indicated by the UDR 221 to enable the UDM 258, the PCF 256, and the NEF 252 to access a particular set of stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notifications of relevant data changes in the UDR. The UDM may include a UDM-FE responsible for handling credentials, location management, subscription management, etc. Several different front ends may serve the same user in different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credentials processing, user identification processing, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 258 may also present a Nudm service-based interface.

[0048] The AF 260 can provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0049] In some embodiments, the 5 GC 240 may enable edge computing by selecting an operator / third-party service that is geographically close to the point where the UE 202 attaches to the network. This may reduce latency and load on the network. To provide an edge computing implementation, the 5 GC 240 may select a UPF 248 that is close to the UE 202 and perform traffic steering from the UPF 248 to the data network 236 over the N6 interface. This may be based on UE subscription data, UE location, and information given by the AF 260. In this way, the AF 260 may influence the UPF (re)selection and traffic routing. Based on the operator deployment, when the AF 260 is considered to be a trusted entity, the network operator may allow the AF 260 to directly interact with the associated NFs. Additionally, the AF 260 may exhibit a Naf service-based interface.

[0050] Data network 236 may represent various network operator services, Internet access, or third party services, which may be provided by one or more servers, including, for example, application / content server 238 .

[0051] 3 illustrates a schematic of a wireless network 300 in accordance with various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 may be similar to similarly named components described elsewhere herein and may be substantially interchangeable.

[0052] The UE 302 may be communicatively coupled to the AN 304 via a connection 306. The connection 306 is shown as an air interface enabling the communicative coupling and may correspond to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0053] The UE 302 may include a host platform 308 coupled to a modem platform 310. The host platform 308 may include an application processing circuit 312 that may be coupled to a protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 may execute various applications for the UE 302 to source / sink application data. The application processing circuit 312 may further perform one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0054] The protocol processing circuitry 314 may perform one or more of the layer operations to facilitate transmission or reception of data over the connection 306. The layer operations implemented by the protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0055] The modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations that are "lower" layer operations performed by protocol processing circuitry 314 in a network protocol stack. These operations may include PHY operations including, for example, one or more of HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multi-antenna port precoding / decoding that 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.

[0056] The modem platform 310 may further include transmit circuitry 318, receive circuitry 320, RF circuitry 322, and an RF front end (RFFE) 324, which may include or connect to one or more antenna panels 326. Briefly, the transmit circuitry 318 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc., the receive circuitry 320 may include analog-to-digital converters, mixers, IF components, etc., the RF circuitry 322 may include low noise amplifiers, power amplifiers, power tracking components, etc., and the RFFE 324 may include filters (e.g., surface / bulk acoustic wave filters), switches, antenna tuners, beam forming components (e.g., phased array antenna components), etc. The selection and arrangement of the transmit circuitry 318, receive circuitry 320, RF circuitry 322, RFFE 324, and antenna panel 326 components (collectively referred to as “transmit / receive components”) may be specific to the details of a particular implementation, such as, for example, whether communications are TDM or FDM at mmWave or sub-6 GHz frequencies.

[0057] In some embodiments, the protocol processing circuit 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit / receive components.

[0058] UE reception may be established by and through the antenna panel 326, the RFFE 324, the RF circuitry 322, the receive circuitry 320, the digital baseband circuitry 316, and the protocol processing circuitry 314. In some embodiments, the antenna panel 326 may receive transmissions from the AN 304 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 326.

[0059] UE transmissions may be established by and through the protocol processing circuitry 314, the digital baseband circuitry 316, the transmit circuitry 318, the RF circuitry 322, the RFFE 324, and the antenna panel 326. In some embodiments, the transmit components of the UE 304 may apply spatial filters to data to be transmitted to form transmit beams emitted by the antenna elements of the antenna panel 326.

[0060] Similar to the UE 302, the AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled to a protocol processing circuit 334 of the modem platform 330. The modem platform may further include a digital baseband circuit 336, a transmit circuit 338, a receive circuit 340, an RF circuit 342, an RFFE circuit 344, and an antenna panel 346. The components of the AN 304 may be similar to, and substantially interchangeable with, similarly named components of the UE 302. In addition to performing data transmission / reception as described above, the components of the AN 308 may perform various logical functions including RNC functions such as, for example, radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0061] 4 is a block diagram illustrating components that can 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 methods described herein, according to some exemplary embodiments. Specifically, FIG. 4 illustrates a schematic diagram of hardware resources 400 including one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry. In embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 402 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 400.

[0062] Processors 410 may include, for example, processor 412 and processor 414. Processor 410 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 described herein), or any suitable combination thereof.

[0063] The memory / storage 420 may include main memory, disk storage, or any suitable combination thereof. The memory / storage 420 may include any type of volatile, non-volatile, or semi-volatile memory, such as, but not limited to, 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.

[0064] Communications resources 430 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripherals 404 or one or more databases 406 or other network elements over network 408. For example, communications resources 430 may include a wired communications component (e.g., for coupling via USB, Ethernet, etc.), a cellular communications component, an NFC component, a Bluetooth (or Bluetooth Low Energy) component, a Wi-Fi component, and other communications components.

[0065] The instructions 450 may comprise software, programs, applications, applets, apps, or other executable code for causing at least one of the processors 410 to perform any one or more of the methods described herein. The instructions 450 may reside, completely or partially, within at least one of the processors 410 (e.g., within a processor's cache memory), within the memory / storage device 420, or any suitable combination thereof. Additionally, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripherals 404 or database 406. Thus, the memory of the processor 410, the memory / storage device 420, the peripherals 404, and the database 406 are examples of computer-readable and machine-readable media.

[0066] FIG. 5 illustrates a network 500 according to various embodiments. The network 500 may operate in a manner compliant with 3 GPP technical standards or technical reports for 6G systems. In some embodiments, the network 500 may operate simultaneously with the network 200. For example, in some embodiments, the network 500 may share one or more frequency or bandwidth resources with the network 200. As one particular example, a UE (e.g., UE 502) may be configured to operate with both the network 500 and the network 200. Such a configuration may be based on the UE including circuitry configured for communication with the frequency and bandwidth resources of both the networks 200 and 500. In general, some elements of the network 500 may share one or more characteristics with elements of the network 200. For the sake of brevity and clarity, such elements may not be repeated in the description of the network 500.

[0067] The network 500 may include a UE 502, where the UE 120 may include any mobile or non-mobile computing device designed to communicate with a RAN 508 over a wireless connection. The UE 502 may be similar to, for example, the UE 202. The UE 502 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment, an in-vehicle entertainment device, an instrument cluster, a heads-up display device, an on-board diagnostic device, a dash-top mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.

[0068] Although not specifically shown in FIG. 5, in some embodiments, the network 500 may include multiple UEs directly coupled to each other 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. Similarly, although not specifically shown in FIG. 5, the UE 502 may be communicatively coupled to an AP, such as the AP 206, as described with respect to FIG. 2. Additionally, although not specifically shown in FIG. 5, in some embodiments, the RAN 508 may include one or more ANs, such as the AN 208 described with respect to FIG. 2. The RAN 508 and / or the ANs of the RAN 508 may be referred to as base stations (BSs), RAN nodes, or using some other terminology or name.

[0069] The UE 502 and the RAN 508 may be configured to communicate over an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features, such as communication in terahertz (THz) or sub-THz bandwidths, or joint communication and sensing. As used herein, the term "joint communication and sensing" may refer to a system that enables wireless communication as well as radar-based sensing through various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communication in the frequency range of 80 GHz and above. Such frequency ranges may additionally or alternatively be referred to as "millimeter wave" or "mm wave" frequency ranges.

[0070] The RAN 508 may enable communication between the UE 502 and a 6G Core Network (CN) 510. Specifically, the RAN 508 may facilitate transmission and reception of data between the UE 502 and the 6G CN 510. The 6G CN 510 may include various functions, such as an NSSF 250, an NEF 252, an NRF 254, a PCF 256, an UDM 258, an AF 260, an SMF 246, and an AUSF 242. The 6G CN 510 may further include a UPF 248 and a DN 236, as shown in FIG.

[0071] Additionally, the RAN 508 may include various additional functions that are in addition to or in lieu of the functions of legacy cellular networks, such as 4G or 5G networks. Two such functions may include a Compute Control Function (Comp CF) 524 and a Compute Services Function (Comp SF) 536. The Comp CF 524 and the Comp SF 536 may be part of or functions of a computing services plane. The Comp CF 524 may be a control plane function that provides functionality such as management of the Comp SF 536, computing task context creation and management (e.g., create, read, modify, delete), and interaction with the underlying computing infrastructure for computing resource management. The Comp SF 536 may be a user plane function that acts as a gateway that interfaces computing service users (such as UE 502) with the computing nodes behind the Comp SF instance. Some functionality of Comp SF 536 may include parsing computing service data received from users and computing tasks that can be executed by computing nodes, hosting a service mesh ingress gateway or service API gateway, service and billing policy enforcement, performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 536 instance may act as a user plane gateway for a cluster of computing nodes. A Comp CF 524 instance may control one or more Comp SF 536 instances.

[0072] Two other such functions may include a communication control function (Comm CF) 528 and a communication service function (Comm SF) 538, which may be part of the communication service plane. The Comm CF 528 may be a control plane function for managing the Comm SF 538, creating / configuring / releasing communication sessions, and managing communication session context. The Comm SF 538 may be a user plane function for data transport. The Comm CF 528 and the Comm SF 538 may be considered upgrades to the SMF 246 and the UPF 248 described with respect to the 5G system of FIG. 2. The upgrades provided by the Comm CF 528 and the Comm SF 538 may enable service aware transport. For legacy (e.g., 4G or 5G) data transport, the SMF 246 and the UPF 248 may still be used.

[0073] Two other such functions may include a Data Control Function (Data CF) 522 and a Data Service Function (Data SF) 532, which may be part of the data service plane. The Data CF 522 may be a control plane function and may provide functionality such as Data SF 532 management, data service creation / configuration / release, data service context management, etc. The Data SF 532 is a user plane function and may act as a gateway between data service users (such as various functions of the UE 502 and the 6G CN 510) and data service endpoints behind the gateway. Specific functions may include parsing and forwarding data service user data to corresponding data service endpoints, generating charging data, and reporting data service status.

[0074] Another such function may be a service orchestration and chaining function (SOCF) 520, which may discover, orchestrate, and chain up communication / computing / data services provided by functions in the network. Upon receiving a service request from a user, SOCF 520 may interact with one or more of Comp CF 524, Comm CF 528, and Data CF 522 to identify Comp SF 536, Comm SF 538, and Data SF 532 instances, configure service resources, and generate a service chain that may include multiple Comp SF 536, Comm SF 538, and Data SF 532 instances and their associated computing endpoints. Workload processing and data movement may then take place within the generated service chain. SOCF 520 may also be responsible for maintaining, updating, and releasing the created service chain.

[0075] Another such function may be the Service Registration Function (SRF) 514, which may act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 536 and Data SF 532 gateways, as well as services provided by the UE 502. The SRF 514 may be considered a counterpart to the NRF 254, which may act as a registry of network functions.

[0076] Other such functions may include an evolved service communication proxy (eSCP) and a service infrastructure control function (SICF) 526, which may provide a service communication infrastructure for control plane services and user plane services. The eSCP may relate to a service communication proxy (SCP) in 5G with the addition of user plane service communication proxy capabilities. Thus, the eSCP is represented in two parts, eCSP-C 512 and eSCP-U 534, for the control plane service communication proxy and the user plane service communication proxy, respectively. The SICF 526 may control and configure the eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0077] Another such function is the AMF 544. The AMF 544 is similar to 244 but has additional functions. In particular, the AMF 544 may include potential function repartitioning, such as moving message transfer functions from the AMF 544 to the RAN 508.

[0078] Another such function is a service orchestration exposure function (SOEF) 518. The SOEF can be configured to expose service orchestration and chain services to external users, such as applications.

[0079] The UE 502 may include an additional function called a Computing Client Services Function (comp CSF) 504. The comp CSF 504 may have both control plane and user plane functionality and may interact with corresponding network side functions such as the SOCF 520, Comp CF 524, Comp SF 536, Data CF 522, and / or Data SF 532 for service discovery, request / response, computational task workload exchange, etc. The Comp CSF 504 may also interface with the network side functions to determine whether a computing task should be initiated on elements of the UE 502, the RAN 508, and / or the 6G CN 510.

[0080] The UE 502 and / or the Comp CSF 504 may include a service mesh proxy 506. The service mesh proxy 506 may act as a proxy for service-to-service communications in the user plane. The capabilities of the service mesh proxy 506 may include one or more of addressing, security, load balancing, and the like.

[0081] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the exemplary section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, the circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the exemplary section.

[0082] Exemplary Techniques In some embodiments, an electronic device, network, system, chip, or component of FIG. 2-FIG. 5, or other figures herein, or portions or implementations thereof, may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. One such process is illustrated in FIG. 6. The process of FIG. 6 may include or relate to a method performed by a UE, one or more elements of a UE, and / or an electronic device that includes or implements a UE. The process of FIG. 6 may include, at 601, identifying an occurrence of a triggering event related to a configured pre-configured measurement gap (pre-MG), at 602, checking a status of the configured pre-MG based on the occurrence of the triggering event, and at 603, changing a status of the configured pre-MG based on the occurrence of the triggering event.

[0083] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the exemplary section below. For example, the baseband circuitry described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below. As another example, the circuitry associated with a UE, base station, network element, etc. described above in connection with one or more of the preceding figures may be configured to operate according to one or more of the examples described below in the exemplary section.

[0084] Working Example Example 1 may include a method for a UE to autonomously check pre-MG status upon RRC reconfiguration for one or more measurement objects (e.g., addition / removal / adjustment of one or more measurement objects).

[0085] Example 2 may include a method in which the UE autonomously checks the pre-MG status when RRC reconfiguration for a PSCell / SCell adds / removes / adjusts.

[0086] Example 3 may include a method in which the UE autonomously checks the pre-MG state upon RRC reconfiguration for BWP switching.

[0087] Example 4 may include the method of Examples 1, 2, 3, or some other examples herein, where the RRC messages may include the simultaneous measurement gap configuration.

[0088] Example 5 may include the method of example 4 or some other example herein, where these measurement gap configurations may be legacy (rel16) MG configurations.

[0089] Example 6 may include the method of example 4 or any other example herein, where these measurement gap configurations may be pre-configured MG configurations.

[0090] Example 7 may include the method of Example 6 or any other example herein, and for a pre-MG with signaling-based (de)activation, the pre-MG status indication shall be updated by an RRC message for pre-MG configuration and forwarded to the UE.

[0091] Example 8 may include the method of Example 6 or some other example herein, and for a pre-MG using rule-based (de)activation, the UE may autonomously know the pre-MG state based on the same rule to check the pre-MG initial state when configured.

[0092] Example 9 may include a method for a UE, the method comprising: determining a triggering event for checking a status of a preconfigured measurement gap (MG), the triggering event including a bandwidth portion switch and / or activation or deactivation of a secondary cell (SCell).

[0093] Example 10 may include the method of Example 9 or any other example herein, wherein the BWP switching is DCI-based or timer-based. Example 11 may include the method of Examples 9-10 or any other example herein, wherein the status of the pre-configured MG is determined based on an RRC message that adds, deletes, or modifies one or more measurement objects.

[0094] Example 11 may include the method of Examples 9-10 or any other example herein, wherein the status of the pre-configured MG is determined based on an RRC message that adds, deletes, or modifies one or more measurement objects.

[0095] Example 11 includes a method performed by a user equipment (UE), one or more elements, and / or one or more electronic devices including or implementing the UE, the method comprising: identifying an occurrence of a triggering event associated with a configured pre-configured measurement gap (pre-MG); checking a status of the configured pre-MG based on the occurrence of the triggering event; and changing a status of the configured pre-MG based on the occurrence of the triggering event.

[0096] Example 12 includes the method of Example 11 and / or any other example herein, wherein checking the status of the configured pre-MG is based on a technique similar to the technique used to identify the status of the pre-MG during initial configuration of the pre-MG.

[0097] Example 13 includes the method of any of Examples 11-12 and / or any other examples herein, wherein the triggering event is related to bandwidth portion (BWP) switching.

[0098] Example 14 includes the method of any of Examples 11-13 and / or any other examples herein, wherein the triggering event is related to activation or deactivation of a secondary cell (SCell).

[0099] Example 15 includes the method of Example 14 and / or any other example herein, wherein the SCell is a Primary SCell (PSCell).

[0100] Example 16 includes the method of any of Examples 11-15 and / or any other example herein, wherein the triggering event is related to adding or removing a measurement object (MO).

[0101] Example 17 includes the method of any of Examples 11-16 and / or any other examples herein, wherein identifying the triggering event is based on identifying receipt of a radio resource control (RRC) message.

[0102] Example 18 includes the method of example 17 and / or any other example herein, wherein the RRC message is an RRCReconfiguration information element (IE).

[0103] Example 19 includes the method of any of Examples 11-18 and / or any other example herein, further comprising configuring a pre-MG to generate a configured pre-MG based on one or more rules.

[0104] Example Z01 may include an apparatus comprising means for performing one or more elements of the method described or related to any of Examples 1-18, or any other method or process described herein.

[0105] Example Z02 may include one or more non-transitory computer-readable media containing instructions that, upon execution by one or more processors of the electronic device, cause the electronic device to perform one or more elements of a method described or related to any of Examples 1-18, or any other method or process described herein.

[0106] Example Z03 may include an apparatus having logic, modules, or circuitry for performing one or more elements of the method described or related to any of Examples 1-18, or any other method or process described herein.

[0107] Example Z04 may include any method, technique, or process described or related to any of Examples 1-18, or any portion or part thereof.

[0108] Example Z05 may include an apparatus with one or more processors and one or more computer-readable media containing instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described or related to any of Examples 1-18, or a portion thereof.

[0109] Example Z06 may include a signal described or related to any of Examples 1-18, or a portion or part thereof.

[0110] Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1-18, or a portion or part thereof, or others described in this disclosure.

[0111] Example Z08 may include a signal encoded with data described or related to any of Examples 1-18, or a portion or part thereof, or in any other manner described in this disclosure.

[0112] Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message described or related to any of Examples 1-18, or a portion or part thereof, or a signal described otherwise in this disclosure.

[0113] Example Z10 may include an electromagnetic signal carrying computer-readable instructions, where execution of the computer-readable instructions by one or more processors causes the one or more processors to perform a method, technique, or process, or portion thereof, described in or related to any of Examples 1-18.

[0114] Example Z11 may include a computing program including instructions, the execution of which by a processing element causes the processing element to perform a method, technique, or process described or related to any of Examples 1-18 or a portion thereof.

[0115] Example Z12 may include signals in a wireless network as illustrated and described herein.

[0116] Example Z13 may include a method of communicating in a wireless network as shown and described herein.

[0117] Example Z14 may include a system for providing wireless communication as illustrated and described herein.

[0118] Example Z15 may include a device for providing wireless communications as illustrated and described herein.

[0119] Any of the above examples may be combined with any other example (or combination of examples) unless otherwise specified. The above description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the 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.

[0120] Abbreviation Unless used differently herein, the terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR 21.905 v16.0.0(2019-06). For purposes of this specification, the following abbreviations may apply to the examples and embodiments discussed herein: 3GPP Third Generation Partnership Project 4G Fourth Generation 5G Fifth Generation 5GC 5G Core network AC Application Client ACK Acknowledgement ACID Application Client Identification AF Application Function AM Acknowledged Mode Acknowledged Mode AMBR Aggregate Maximum Bit Rate AMF Access and Mobility Management Function AN Access Network ANR Automatic Neighbour Relation AP Application Protocol, Antenna Port, Access Point API Application Programming Interface APN Access Point Name Access Point Name ARP Allocation and Retention Priority ARQ Automatic Repeat Request Automatic repeat request AS Access Stratum Access layer ASP Application Service Provider Application Service Provider ASN.1 Abstract Syntax Notation One AUSF Authentication Server Function Authentication server function AWGN Additive White Gaussian Noise BAP Backhaul Adaptation Protocol BCH Broadcast Channel BER Bit Error Ratio Bit Error Rate BFD Beam Failure Detection BLER Block Error Rate BPSK Binary Phase Shift Keying Two-state phase shift keying BRAS Broadband Remote Access Server Broadband Remote Access Server BSS Business Support System BS Base Station BSR Buffer Status Report BW Bandwidth BWP Bandwidth Part C-RNTI Cell Radio Network Temporary Identity Cell Radio Network Temporary Identity CA Carrier Aggregation, Certification Authority CAPEX CAPital EXpenditure Capital Expenditure CBRA Contention Based Random Access CC Component Carrier, Country Code, Cryptographic Checksum CCA Clear Channel Assessment CCE Control Channel Element CCCH Common Control Channel CE Coverage Enhancement CDM Content Delivery Network CDMA Code-Division Multiple Access CFRA Contention Free Random Access Contention Free Random Access CG Cell Group CGF Charging Gateway Function CHF Charging Function CI Cell Identity CID Cell-ID Cell ID (e.g. positioning method) CIM Common Information Model CIR Carrier to Interference Ratio CK Cipher Key CM Connection Management, Conditional Mandatory CMAS Commercial Mobile Alert Service CMD Command CMS Cloud Management System Cloud Management System CO Conditional Optional CoMP Coordinated Multi-Point CORESET Control Resource Set Control resource set COTS Commercial Off-The-Shelf CP Control Plane, Cyclic Prefix, Connection Point CPD Connection Point Descriptor CPE Customer Premise Equipment CPICH Common Pilot Channel CQI Channel Quality Indicator CPU CSI processing unit CSI processing unit, Central Processing Unit C / R Command / Response field bit CRAN Cloud Radio Access Network Cloud Radio Access Network, Cloud RAN CRB Common Resource Block CRC Cyclic Redundancy Check Cyclic Redundancy Check CRI Channel-State Information Resource Indicator, CSI-RS Resource Indicator C-RNTI Cell RNTI Cell RNTI CS Circuit Switched CSAR Cloud Service Archive Cloud Service Archive CSI Channel-State Information CSI-IM CSI Interference Measurement CSI Interference Measurement CSI-RS CSI Reference Signal CSI reference signal CSI-RSRP CSI reference signal received power CSI reference signal received power CSI-RSRQ CSI reference signal received quality CSI reference signal received quality CSI-SINR CSI signal-to-noise and interference ratio CSMA Carrier Sense Multiple Access CSMA / CA CSMA with collision avoidance CSS Common Search Space, Cell-specific Search Space CTF Charging Trigger Function CTS Clear-to-Send Clear to send CW Codeword CWS Contention Window Size D2D Device-to-Device DC Dual Connectivity, Direct Current DCI Downlink Control Information DF Deployment Flavour DL Downlink DMTF Distributed Management Task Force DPDK Data Plane Development Kit DM-RS, DMRS Demodulation Reference Signal DN Data network DNN Data Network Name Data Network Name DNAI Data Network Access Identifier DRB Data Radio Bearer DRS Discovery Reference Signal DRX Discontinuous Reception DSL Domain Specific Language, Digital Subscriber Line DSLAM DSL Access Multiplexer DSL Access Multiplexer DwPTS Downlink Pilot Time Slot Downlink pilot time slot E-LAN ​​Ethernet Local Area Network E2E End-to-End ECCA extended clear channel assessment, extended CCA ECCE Enhanced Control Channel Element, Enhanced CCE ED Energy Detection EDGE Enhanced Datarates for GSM Evolution EAS Edge Application Server Edge Application Server EASID Edge Application Server Identification Edge Application Server Identification ECS Edge Configuration Server Edge Configuration Server ECSP Edge Computing Service Provider Edge Computing Service Provider EDN Edge Data Network EEC Edge Enabler Client Edge Enabler Client EECID Edge Enabler Client Identification EES Edge Enabler Server Edge Enabler Server EESID Edge Enabler Server Identification Edge Enabler Server Identification EHE Edge Hosting Environment Edge Hosting Environment EGMF Exposure Governance tableManagement Function EGPRS Enhanced GPRS Enhanced GPRS EIR Equipment Identity Register eLAA enhanced Licensed Assisted Access, enhanced LAA EM, Element Manager eMBB Enhanced Mobile Broadband EMS Element Management System eNB evolved NodeB Evolved NodeB, E-UTRAN NodeB EN-DC E-UTRA-NR Dual Connectivity EPC Evolved Packet Core EPDCCH enhanced PDCCH, enhanced Physical Downlink Control Channel EPRE Energy per resource element EPS Evolved Packet System EREG enhanced resource element groups ETSI European Telecommunications Standards Institute ETWS Earthquake and Tsunami Warning System eUICC embedded UICC embedded Universal Integrated Circuit Card E-UTRA Evolved UTRA Evolved UTRA E-UTRAN Evolved UTRAN EV2X Improved V2X F1AP F1 Application Protocol F1 Application Protocol F1-C F1 Control plane interface F1-U F1 User plane interface F1 User plane interface FACCH Fast Associated Control CHannel FACCH / F Fast Associated Control Channel / Full rate FACCH / H Fast Associated Control Channel / Half rate FACH Forward Access Channel FAUSCH Fast Uplink Signalling Channel FB Functional Block FBI Feedback Information FCC Federal Communications Commission FCCH Frequency Correction CHannel FDD Frequency Division Duplex FDM Frequency Division Multiplex FDMA Frequency Division Multiple Access FE Front End FEC Forward Error Correction FFS For Further Study FFT Fast Fourier Transformation feLAA further enhanced Licensed Assisted Access, further enhanced LAA FN Frame Number FPGA Field-Programmable Gate Array FR Frequency Range FQDN Fully Qualified Domain Name G-RNTI GERAN Radio Network Temporary Identity GERAN Radio Network Temporary Identity GERAN GSM EDGE RAN GSM EDGE RAN, GSM EDGE Radio Access Network GSM EDGE radio access network GGSN Gateway GPRS Support Node GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (English: Global Navigation Satellite System) gNB Next Generation NodeB Next Generation NodeB gNB-CU gNB-centralized unit gNB centralized unit, Next Generation NodeB centralized unit, Next Generation NodeB centralized unit gNB-DU gNB-distributed unit gNB distributed unit, Next Generation NodeB distributed unit Next Generation NodeB distributed unit GNSS Global Navigation Satellite System GPRS General Packet Radio Service GSM Global System for Mobile Communications Global System for Mobile Communications, Groupe Sp´ecial Mobile GSM Association GTP GPRS Tunneling Protocol GTP-U GPRS Tunnelling Protocol for User Plane GPRS Tunneling Protocol for User Plane GTS Go To Sleep Signal Sleep transition signal (WUS related) GUMMEI Globally Unique MME Identifier Globally Unique MME Identifier GUTI Globally Unique Temporary UE Identity Globally Unique Temporary UE Identity HARQ Hybrid ARQ Hybrid Automatic Repeat Request HANDO Handover HFN HyperFrame Number HyperFrame Number HHO Hard Handover HLR Home Location Register HN Home Network HO Handover HPLMN Home Public Land Mobile Network HSDPA High Speed ​​Downlink Packet Access HSN Hopping Sequence Number Hopping sequence number HSPA High Speed ​​Packet Access HSS Home Subscriber Server Home Subscriber Server HSUPA High Speed ​​Uplink Packet Access HTTP Hyper Text Transfer Protocol HTTPS Hyper Text Transfer Protocol Secure (https is http / 1.1 over SSL, i.e. port 443) I-Block Information Block ICCID Integrated Circuit Card Identification IAB Integrated Access and Backhaul ICIC Inter-Cell Interference Coordination ID Identity, identifier IDFT Inverse Discrete Fourier Transform IE Information element IBE In-Band Emission IEEE Institute of Electrical and Electronics Engineers IEI Information Element Identifier IEIDL Information Element Identifier Data Length IETF Internet Engineering Task Force IF Infrastructure IM Interference Measurement, Intermodulation, IP Multimedia IMC IMS Credentials IMS Credentials IMEI International Mobile Equipment Identity IMGI International mobile group identity IMPI IP Multimedia Private Identity IP Multimedia Private Identity IMPU IP Multimedia PUblic identity IP Multimedia Public Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IoT Internet of Things IP Internet Protocol Ipsec IP Security, Internet Protocol Security IP-CAN IP-Connectivity Access Network IP Connectivity Access Network IP-M IP Multicast IP Multicast IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IR Infrared IS In Sync IRP Integration Reference Point ISDN Integrated Services Digital Network ISIM IM Services Identity Module ISO International Organisation for Standardisation ISP Internet Service Provider IWF Interworking-Function I-WLAN Interworking WLAN Constraint length of the convolutional code, USIM Individual key kB Kilobyte (1000 bytes) kbps kilo-bits per second Kc Ciphering key Ki Individual subscriber authentication key KPI Key Performance Indicator KQI Key Quality Indicator KSI Key Set Identifier ksps kilo-symbols per second KVM Kernel Virtual Machine L1 Layer 1 (physical layer) L1-RSRP Layer 1 reference signal received power L2 Layer 2 (data link layer) L3 Layer 3 (network layer) LAA Licensed Assisted Access LAN Local Area Network LADN Local Area Data Network Local Area Data Network LBT Listen Before Talk LCM LifeCycle Management LCR Low Chip Rate LCS Location Services LCID Logical Channel ID Logical Channel ID LI Layer Indicator LLC Logical Link Control, Low Layer Compatibility LPLMN Local PLMN LPP LTE Positioning Protocol LSB Least Significant Bit LTE Long Term Evolution LWA LTE-WLAN aggregation LTE-WLAN aggregation LWIP LTE / WLAN Radio Level Integration with IPsec Tunnel LTE Long Term Evolution M2M Machine-to-Machine MAC Medium Access Control (context of protocol layering) MAC Message authentication code (security / encryption context) MAC-A MAC used for authentication and key agreement (TSG T WG3 context) MAC-I MAC used for data integrity of signalling messages (TSG T WG3 context) MANO Management and Orchestration Management, Operation and Orchestration MBMS Multimedia Broadcast and Multicast Service MBSFN Multimedia Broadcast multicast service Single Frequency Network MCC Mobile Country Code MCG Master Cell Group MCOT Maximum Channel Occupancy Time MCS Modulation and coding scheme MDAF Management Data Analytics Function MDAS Management Data Analytics Service Management Data Analytics Service MDT Minimization of Drive Tests ME Mobile Equipment MeNB master eNB MER Message Error Ratio Message Error Ratio MGL Measurement Gap Length MGRP Measurement Gap Repetition Period Measurement Gap Repetition Period MIB Master Information Block, Management Information Base MIMO Multiple Input Multiple Output MLC Mobile Location Centre MM Mobility Management Mobility Management MME Mobility Management Entity MN Master Node MNO Mobile Network Operator MO Measurement Object, Mobile Originated MPBCH MTC Physical Broadcast CHannel MPDCCH MTC Physical Downlink Control CHannel MPDSCH MTC Physical Downlink Shared CHannel MPRACH MTC Physical Random Access CHannel MPUSCH MTC Physical Uplink Shared Channel MPLS MultiProtocol Label Switching MS Mobile Station Mobile station MSB Most Significant Bit MSC Mobile Switching Centre Mobile Switching Centre MSI Minimum System Information, MCH Scheduling Information MSID Mobile Station Identifier MSIN Mobile Station Identification Number MSISDN Mobile Subscriber ISDN Number MT Mobile Terminated Mobile Termination MTC Machine-Type Communications mMTC massive MTC, massive Machine-Type Communications Mechanical Large-scale Machine-based Communication MU-MIMO Multi User MIMO MWUS MTC wake-up signal MTC wake-up signal, MTC WUS MTC WUS NACK Negative Acknowledgement NAI Network Access Identifier NAS Non-Access Stratum Non-Access Stratum layer NCT Network Connectivity Topology Network Connectivity Topology NC-JT Non-Coherent Joint Transmission NEC Network Capability Exposure NE-DC NR-E-UTRA Dual Connectivity NEF Network Exposure Function NF Network Function NFP Network Forwarding Path NFPD Network Forwarding Path Descriptor NFV Network Functions Virtualization NFVI NFV Infrastructure NFV Infrastructure NFVO NFV Orchestrator NFV Orchestrator NG Next Generation Next Generation, Next Gen NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity NG-RAN E-UTRA-NR Dual Connectivity NM Network Manager NMS Network Management System N-PoP Network Point of Presence NMIB, N-MIB Narrowband MIB NPBCH Narrowband Physical Broadcast CHannel NPDCCH Narrowband Physical Downlink Control CHannel NPDSCH Narrowband Physical Downlink Shared CHannel NPRACH Narrowband Physical Random Access CHannel NPUSCH Narrowband Physical Uplink Shared CHannel NPSS Narrowband Primary Synchronization Signal NSSS Narrowband Secondary Synchronization Signal NR New Radio, Neighbour Relation NRF NF Repository Function NRS Narrowband Reference Signal NS Network Service NSA Non-Standalone operation mode NSD Network Service Descriptor NSR Network Service Record NSSAI Network Slice Selection Assistance Information S-NNSAI Single-NSSAI NSSF Network Slice Selection Function NW Network NWUS Narrowband wake-up signal, Narrowband WUS NZP Non-Zero Power O&M Operation and Maintenance ODU2 Optical channel Data Unit - type 2 OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OOB Out-of-band OOS Out of Sync OPEX OPerating EXpense OSI Other System Information Other system information OSS Operations Support System OTA over-the-air PAPR Peak-to-Average Power Ratio Peak-to-Average Power Ratio PAR Peak to Average Ratio PBCH Physical Broadcast Channel PC Power Control, Personal Computer PCC Primary Component Carrier Primary CC PCell Primary Cell Main cell PCI Physical Cell ID Physical Cell Identity PCEF Policy and Charging Enforcement Function PCF Policy Control Function PCRF Policy Control and Charging Rules Function Policy control and charging rules function PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layer PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDN Packet Data Network, Public Data Network PDSCH Physical Downlink Shared Channel Physical Downlink Shared Channel PDU Protocol Data Unit PEI Permanent Equipment Identifiers PFD Packet Flow Description P-GW PDN Gateway PHICH Physical hybrid-ARQ indicator channel PHY Physical layer PLMN Public Land Mobile Network PIN Personal Identification Number PM Performance Measurement Performance measurement PMI Precoding Matrix Indicator PNF Physical Network Function PNFD Physical Network Function Descriptor PNFR Physical Network Function Record POC PTT over Cellular PTT over Cellular PP, PTP Point-to-Point PPP Point-to-Point Protocol PRACH Physical RACH Physical RACH PRB Physical resource block PRG Physical resource block group ProSe Proximity Services, Proximity-Based Services PRS Positioning Reference Signal PRR Packet Reception Radio PS Packet Services PSBCH Physical Sidelink Broadcast Channel PSDCH Physical Sidelink Downlink Channel PSCCH Physical Sidelink Control Channel PSSCH Physical Sidelink Shared Channel PSCell Primary SCell Primary SCell PSS Primary Synchronization Signal Primary synchronization signal PSTN Public Switched Telephone Network PT-RS Phase-tracking reference signal Phase-tracking reference signal PTT Push-to-Talk PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel Physical Uplink Shared Channel QAM Quadrature Amplitude Modulation QCI QoS class of identifier QoS class of identifier QCL Quasi co-location QFI QoS Flow ID QoS Flow Identifier QoS Quality of Service QPSK Quadrature (Quaternary) Phase Shift Keying QZSS Quasi-Zenith Satellite System RA-RNTI Random Access RNTI Random Access RNTI RAB Radio Access Bearer, Random Access Burst RACH Random Access Channel RADIUS Remote Authentication Dial In User Service RAN Radio Access Network RAND RANDom number Random number (used for authentication) RAR Random Access Response RAT Radio Access Technology RAU Routing Area Update RB Resource block, Radio Bearer RBG Resource block group REG Resource Element Group Release REQ REQuest request RF Radio Frequency RI Rank Indicator RIV Resource indicator value RL Radio Link RLC Radio Link Control Radio Link Control layer RLC AM RLC Acknowledged Mode RLC UM RLC Unacknowledged Mode RLC Unacknowledged Mode RLF Radio Link Failure Radio Link Failure RLM Radio Link Monitoring RLM-RS Reference Signal for RLM Reference signal for RLM RM Registration Management RMC Reference Measurement Channel RMSI Remaining MSI, Remaining Minimum System Information RN Relay Node RNC Radio Network Controller RNL Radio Network Layer RNTI Radio Network Temporary Identifier ROHC RObust Header Compression RRC Radio Resource Control Radio resource control, Radio Resource Control layer Radio Resource Control Layer RRM Radio Resource Management Radio resource management RS Reference Signal Reference signal RSRP Reference Signal Received Power RSRQ Reference Signal Received Quality RSSI Received Signal Strength Indicator RSU Road Side Unit RSTD Reference Signal Time Difference RTP Real Time Protocol RTS Ready-To-Send Ready to send RTT Round Trip Time Rx Reception, Receiving Receiver S1AP S1 Application Protocol S1-MME S1 for the control plane S1-U S1 for the user plane S-GW Serving Gateway S-RNTI SRNC Radio Network Temporary Identity SRNC Radio Network Temporary Identity S-TMSI SAE Temporary Mobile Station Identifier SAE Temporary Mobile Station Identifier SA Standalone operation mode SAE System Architecture Evolution SAP Service Access Point SAPD Service Access Point Descriptor SAPI Service Access Point Identifier SCC Secondary Component Carrier, Secondary CC SCell Secondary Cell Secondary Cell SCEF Service Capability Exposure Function SC-FDMA Single Carrier Frequency Division Multiple Access SCG Secondary Cell Group SCM Security Context Management SCS Subcarrier Spacing SCTP Stream Control Transmission Protocol SDAP Service Data Adaptation Protocol Service Data Adaptation Protocol layer SDL Supplementary Downlink SDNF Structured Data Storage Network Function SDP Session Description Protocol SDSF Structured Data Storage Function SDU Service Data Unit SEAF Security Anchor Function SeNB secondary eNB SEPP Security Edge Protection Proxy SFI Slot format indication SFTD Space-Frequency Time Diversity, SFN and frame timing difference SFN System Frame Number SgNB Secondary gNB SGSN Serving GPRS Support Node S-GW Serving Gateway SI System Information SI-RNTI System Information RNTI System Information RNTI SIB System Information Block SIM Subscriber Identity Module SIP Session Initiated Protocol SiP System in Package SL Sidelink SLA Service Level Agreement SM Session Management SMF Session Management Function SMS Short Message Service SMSF SMS Function SMTC SSB-based Measurement Timing Configuration SN Secondary Node, Sequence Number SoC System on Chip SON Self-Organizing Network SpCell Special Cell Special Cell SP-CSI-RNTI Semi-Persistent CSI RNTI SPS Semi-Persistent Scheduling SQN Sequence number SR Scheduling Request SRB Signalling Radio Bearer SRS Sounding Reference Signal Detection reference signal SS Synchronization Signal Synchronization signal SSB Synchronization Signal Block SSID Service Set Identifier SS / PBCH Block SS / PBCH Block SSBRI SS / PBCH Block Resource Indicator SS / PBCH Block Resource Indicator, Syncheronization Signal Block Resource Indicator SSC Session and Service Continuity SS-RSRP Synchronization Signal based Reference Signal Received Power SS-RSRQ Synchronization Signal based Reference Signal Received Quality SS-SINR Synchronization Signal based Signal to Noise and Interference Ratio Synchronization Signal based Signal to Noise and Interference Ratio SSS Secondary Synchronization Signal SSSG Search Space Set Group SSSIF Search Space Set Indicator SST Slice / Service Types SU-MIMO Single User MIMO SUL Supplementary Uplink TA Timing Advance, Tracking Area TAC Tracking Area Code TAG Timing Advance Group TAI Tracking Area Identity TAU Tracking Area Update TB Transport Block TBS Transport Block Size TBD To Be Defined TCI Transmission Configuration Indicator TCP Transmission Communication Protocol TDD Time Division Duplex TDRA Time Domain Resource Allocation TDM Time Division Multiplexing TDMA Time Division Multiple Access TE Terminal Equipment TEID Tunnel End Point Identifier TFT Traffic Flow Template TMSI Temporary Mobile Subscriber Identity TNL Transport Network Layer TPC Transmit Power Control TPMI Transmitted Precoding Matrix Indicator TR Technical Report Technical Report TRP, TRxP Transmission Reception Point TRS Tracking Reference Signal TRx Transceiver TS Technical Specifications, Technical Standard TTI Transmission Time Interval Tx Transmission, Transmitting, Transmitter U-RNTI UTRAN Radio Network Temporary Identity UTRAN Radio Network Temporary Identity UART Universal Asynchronous Receiver and Transmitter Universal Asynchronous Receiver and Transmitter UCI Uplink Control Information UE User Equipment UDM Unified Data Management UDP User Datagram Protocol UDSF Unstructured Data Storage Network Function UICC Universal Integrated Circuit Card UL Uplink UM Unacknowledged Mode UML Unified Modelling Language UMTS Universal Mobile Telecommunications System UP User Plane UPF User Plane Function URI Uniform Resource Identifier URL Uniform Resource Locator URLLC Ultra-Reliable and Low Latency USB Universal Serial Bus USIM Universal Subscriber Identity Module USS UE-specific search space UTRA UMTS Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network UwPTS Uplink Pilot Time Slot V2I Vehicle-to-Infrastruction V2P Vehicle-to-Pedestrian V2V Vehicle-to-Vehicle V2X Vehicle-to-everything VIM Virtualized Infrastructure Manager VL Virtual Link Virtual Link, VLAN Virtual LAN, Virtual Local Area Network VM Virtual Machine VNF Virtualized Network Function VNFFG VNF Forwarding Graph VNFFGD VNF Forwarding Graph Descriptor VNFM VNF Manager VNF Manager VoIP Voice-over-IP, Voice-over-Internet Protocol Voice over IP, Voice over Internet Protocol VPLMN Visited Public Land Mobile Network VPN Virtual Private Network VRB Virtual Resource Block WiMAX Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network WMAN Wireless Metropolitan Area Network WPAN Wireless Personal Area Network X2-C X2-Control plane X2 control plane X2-U X2-User plane X2 User plane XML eXtensible Markup Language XRES EXpected user RESponse Expected user response XOR eXclusive OR exclusive OR ZC Zadoff-Chu ZP Zero Po Zero Power

[0121] Terminology For purposes of this specification, the following terms and definitions are applicable to the examples and embodiments discussed herein. The term "circuitry" as used herein may refer to, be a part of, or include hardware components, such as electronic circuits, logic circuits, processors (shared, distributed, or groups), and / or memories (shared, distributed, or groups), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high capacity PLDs (HCPLDs), structured ASICs, programmable SoCs), digital signal processors (DSPs), etc., configured to provide the described functionality. In some embodiments, a circuitry may execute one or more software or firmware programs that provide at least a portion of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements with program code used to perform the functions of the program code (or a combination of circuits used in an electrical or electronic system). In such 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 may refer to, be part of, or include circuitry capable of sequentially and automatically performing a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The processing circuitry may include one or more processing cores for executing instructions, and one or more memory structures for storing 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 manipulating computer-executable instructions, such as program code, software modules, and / or functional processes. The processing circuitry may include additional hardware accelerators, which may be microprocessors, programmable processing devices, and 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 with "processor circuitry" and may be referred to as "processor circuitry". As used herein, the term "interface circuitry" may refer to, be part of, or include 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, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or the like. As used herein, the term "user equipment" or "UE" refers to a device with wireless 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 with and may be referred to as a client, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio device, reconfigurable wireless device, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface. The term "network element" as used herein refers to a physical or virtualized device and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or may be 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. As used herein, the term "computer system" refers to any type of interconnected electronic device or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to each other. Additionally, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computational and / or network resources. As used herein, the terms "appliance," "computer appliance," and the like refer to a computing device or system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image implemented by a hypervisor-equipped device that virtualizes or emulates a computing appliance or is otherwise dedicated to providing specific computing resources. The term "resource" as used herein refers to a physical or virtual device, a physical or virtual component in a computing environment, and / or a physical or virtual component in a particular device, such as a computer device, a mechanical device, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, networks, databases and applications, workload units, and / or whatsoever. A "hardware resource" may refer to computational, storage, and / or network resources provided by a physical hardware element. A "virtualized resource" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resource" or "communication resource" may refer to a resource that is accessible by a computer device / system via a communication network. The term "system resource" may refer to any type of shared entity for providing services and may include computational and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects or services accessible through a server, where such a system resource may reside on a single host or on multiple hosts and be clearly identifiable. The term "channel" as used herein refers to any transmission medium, tangible or intangible, used to communicate data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier", and / or any other similar term that describes a path or medium over which data is communicated. Furthermore, the term "link" as used herein refers to a connection between two devices through a RAT for sending and receiving information. As used herein, the terms "instantiate," "instantiation," and the like refer to the creation of an instance. An "instance" may also refer to a concrete manifestation of an object that may occur, for example, during the execution of program code. The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" can mean that two or more elements are in direct physical or electrical contact with each other, can mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or can mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" can mean that two or more elements are in direct contact with each other. The term "communicatively coupled" can mean that two or more elements may be in contact with each other by any communication means, including through a wired or other interconnect connection, through a wireless communication channel or link, and / or the like. The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element or the data element that contains the contents. The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration. The term "SSB" refers to SS / PBCH block. The term "primary cell" refers to an MCG cell operating on a primary frequency on which a UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure. The term "primary SCG cell" refers to an SCG cell that performs random access when the UE performs a synchronized reconfiguration procedure for DC operation. The term "secondary cell" refers to a cell that provides additional radio resources in addition to the special cell for a UE configured by CA. The term "secondary cell group" refers to a subset of serving cells that includes a PSCell and zero or more secondary cells for a UE configured by a DC. The term "serving cell" refers to a primary cell for an RRC_CONNECTED UE that is not configured by CA / DC, and there is only one serving cell that constitutes the primary cell. The term "serving cell" or "serving cells" refers to the set of cells including the special cell and all secondary cells established by CA / for an RRC_CONNECTED UE. The term "special cell" refers to a PCell or an SCGnoPSell of an MCG for DC operation, otherwise the term "special cell" refers to a PCell.

Claims

1. 1. An apparatus for use in a user equipment (UE), comprising: a memory for storing information relating to a configured pre-configured measurement gap (pre-MG); Identifying the occurrence of a triggering event associated with the configured pre-MG; Checking the status of the configured pre-MG based on the occurrence of the triggering event; Changing the status of the configured pre-MG based on the occurrence of the triggering event. one or more processors configured to An apparatus comprising:

2. The apparatus of claim 1 , wherein checking the status of the configured pre-MG is based on techniques similar to those used to identify the status of a pre-MG during initial configuration of the pre-MG.

3. The apparatus of claim 1 , wherein the triggering event is related to bandwidth portion (BWP) switching.

4. The apparatus of claim 1 , wherein the triggering event is related to activation or deactivation of a secondary cell (SCell).

5. The apparatus of claim 4 , wherein the SCell is a Primary SCell (PSCell).

6. The apparatus of claim 1 , wherein the triggering event is related to adding or removing a measurement object (MO).

7. The apparatus of claim 1 , wherein identifying the triggering event is based on identifying receipt of a Radio Resource Control (RRC) message.

8. The apparatus of claim 7 , wherein the RRC message is an RRCReconfiguration information element (IE).

9. When executed by the one or more processors, the method includes: Identifying the occurrence of a triggering event related to a configured pre-configured measurement gap (pre-MG); Checking the status of the configured pre-MG based on the occurrence of the triggering event; Changing the status of the configured pre-MG based on the occurrence of the triggering event. One or more non-transitory computer readable media (NTCRM) containing instructions.

10. 10. The one or more NTCRMs of claim 9, wherein checking the status of the configured pre-MG is based on techniques similar to those used to identify the status of the pre-MG during initial configuration of the pre-MG.

11. The one or more NTCRMs of claim 9 , wherein the triggering event is related to bandwidth portion (BWP) switching.

12. The one or more NTCRMs of claim 9 , wherein the triggering event is related to activation or deactivation of a secondary cell (SCell).

13. The one or more NTCRMs of claim 12 , wherein the SCell is a Primary SCell (PSCell).

14. The one or more NTCRMs of claim 9 , wherein the triggering event is related to adding or removing a measurement object (MO).

15. 10. The one or more NTCRMs of claim 9, wherein identifying the triggering event is based on identifying receipt of a Radio Resource Control (RRC) message.

16. The one or more NTCRMs of claim 15, wherein the RRC message is an RRCReconfiguration information element (IE).

17. A user equipment (UE), one or more processors; When executed by the one or more processors, the method includes: configuring a pre-configured measurement gap (pre-MG) based on one or more rules to generate a configured pre-MG; Identifying the occurrence of a triggering event related to the configured pre-MG; Checking the status of the configured pre-MG based on the occurrence of the triggering event; Changing the status of the configured pre-MG based on the occurrence of the triggering event. one or more non-transitory computer-readable media containing instructions; A UE comprising:

18. The UE of claim 17, wherein checking the status of the configured pre-MG is based on techniques similar to those used to identify the status of a pre-MG during initial configuration of the pre-MG.

19. The UE of claim 17, wherein the triggering event is related to bandwidth portion (BWP) switching.

20. The UE of claim 17, wherein the triggering event is related to activation or deactivation of a secondary cell (SCell).

Images