Enhanced activation of preconfigured measurement gaps for wireless communications - Patents.com

Conditionally activated preconfigured measurement gaps in wireless communication systems address inefficiencies in existing standards by dynamically managing MGs, enhancing measurement accuracy and resource utilization through autonomous UE-triggered status updates.

JP2024541783APending Publication Date: 2024-11-13INTEL CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023574788
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2022-01-10
Filing Date
2022-11-07
Publication Date
2024-11-13

AI Technical Summary

Technical Problem

Existing wireless communication standards, such as those defined by the Third Generation Partnership Program (3GPP), face inefficiencies in managing preconfigured measurement gaps (MGs) for wireless devices, leading to suboptimal performance in signal quality measurements due to the always-active nature of these gaps, which can disrupt ongoing transmissions and receptions.

Method used

The implementation of conditionally activated preconfigured measurement gaps, where the UE autonomously checks and updates MG status based on specific triggers like measurement object reconfiguration, secondary cell activation, or BWP switching, allowing for dynamic management of MGs to optimize measurement efficiency without constant disruption.

Benefits of technology

This approach reduces the time required for gap configuration, enhances measurement accuracy, and improves overall communication efficiency by minimizing unnecessary gaps, thereby optimizing resource utilization in wireless devices.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024541783000001_ABST
    Figure 2024541783000001_ABST
Patent Text Reader

Abstract

The present disclosure describes a system, method, and device for activating and deactivating a pre-configured measurement gap in carrier aggregation. A user equipment (UE) device can detect a pre-configured measurement gap configured by a network, detect that the pre-configured measurement gap has been activated or deactivated, and activate or deactivate the measurement gap based on detecting that the pre-configured measurement gap has been activated or deactivated.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED PATENT APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 63 / 277,495, filed November 9, 2021, and U.S. Provisional Application No. 63 / 297,991, filed January 10, 2022, the disclosures of which are incorporated by reference as if set forth in their entireties.

[0002] Technical Field The present disclosure relates generally to systems and methods for wireless communications, and more particularly, to activating pre-configured measurement gaps in wireless communications. [Background technology]

[0003] Wireless devices are becoming widespread and are increasingly using wireless channels. The 3rd Generation Partnership Program (3GPP®) is developing one or more standards for wireless communications. [Brief description of the drawings]

[0004] [Figure 1] FIG. 1 is a network diagram illustrating an exemplary network environment in accordance with one or more exemplary embodiments of the present disclosure. [Diagram 2] 1 illustrates an example process for triggering activation or deactivation of pre-configured measurement gaps using measurement target reconfiguration, in accordance with one or more example embodiments of the present disclosure. [Diagram 3] 1 illustrates an example process for triggering activation or deactivation of a pre-configured measurement gap using secondary cell activation, according to one or more example embodiments of the present disclosure. [Figure 4]1 illustrates an example process for triggering activation or deactivation of a pre-configured measurement gap by adding, releasing, or modifying a primary or secondary cell, according to one or more example embodiments of the present disclosure. [Diagram 5] 1 illustrates an example process for triggering activation or deactivation of a pre-configured measurement gap by triggering a user equipment device to autonomously check a pre-configured measurement gap status, according to one or more example embodiments of the present disclosure. [Figure 6A] 13 is a table of parameters for Case 4-1, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 6B] 13 is a table of parameters for Case 4-2, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 6C] 13 is a table of parameters for Case 4-3, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 6D] 13 is a table of parameters for Case 5-1, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 6E] 13 is a table of parameters for Case 5-2, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 6F] 13 is a table of parameters for Case 5-3, in accordance with one or more exemplary embodiments of the present disclosure. [Figure 7] FIG. 1 illustrates a flow diagram of an example process for triggering activation or deactivation of pre-configured measurement gaps in wireless communications, in accordance with one or more example embodiments of the present disclosure. [Figure 8] 1 illustrates a network in accordance with one or more exemplary embodiments of the present disclosure. [Figure 9] 1 illustrates a schematic diagram of a wireless network in accordance with one or more exemplary embodiments of the present disclosure. [Figure 10] FIG. 1 is a block diagram illustrating components in accordance with one or more exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0005] The following description and drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithmic, and other changes. Portions and features of some embodiments may be included in, or substituted for, portions and features of other embodiments. The embodiments set forth in the claims encompass all available equivalents of those claims.

[0006] A wireless device may operate as defined by a technology standard. For cellular telecommunications, the Third Generation Partnership Program (3GPP) defines communication technologies that include the use of measurement gaps, which refer to a small gap of time during which no transmission or reception occurs. During this small gap, a user equipment device (UE) may perform signal quality measurements (e.g., to a target cell before returning to the current cell). The 3GPP standard makes provision for agreement between the UE and the network to define the measurement gap (MG), including the starting location of the measurement gap (MG), the duration of the MG, the number of MGs, etc. (e.g., established by the MG component of a radio resource control message).

[0007] The preconfigured measurement gap procedure is used by the network to provide measurement gaps for downlink position reference signal (DL-PRS) measurements. The gNB network device can activate / deactivate the preconfigured measurement gaps upon receiving a request from the UE or the location management function (LMF).

[0008] The UE uses the MG to perform measurements on a target carrier frequency (e.g., a target cell) while simultaneously transmitting and / or receiving on a serving cell. The MG may be preconfigured by the network (e.g., gap-assisted) or non-gap-assisted. Measurements may be performed on the SSB of the target cell.

[0009] Previously, a configured MG was always active, but newer pre-configured MGs can be conditionally activated.

[0010] In one or more embodiments of the present disclosure, a UE behavior may be defined for when the network converts from a preconfigured MG to another MG.

[0011] In one or more embodiments, if a pre-configured MG is configured for the UE, a measurement target changed by the RRC may trigger a pre-configured MG status (ON / OFF) change.

[0012] ● Case 1-1 → No need to trigger the UE to autonomously check the pre-MG status. When a measurement object (MO) is reconfigured, the pre-MG may be reconfigured accordingly, and an indication of the pre-MG activation status may be updated accordingly. For UEs that support network signaling based pre-configured MG status indication, further pre-MG status can be checked by network signaling. For UEs that do not support NW signaling based pre-configured MG status indication but rule based supports it, the NW will also activate pre-MG in the UE but will not forward any indication to the UE. The UE does not need to know the pre-MG status autonomously because they are already included in the RRCReconfiguration message 2.

[0013] ● Case 1-2 → Need to trigger the UE to autonomously check pre-MG status when such an event occurs. Alternatively, if there is no update regarding the pre-MG configuration in the MO reconfiguration message, For signaling based, at least such indication table is updated and forwarded to the UE. For the rule base, the UE may need to be triggered to update its knowledge about the prior MG status.

[0014] In one or more embodiments, the pre-configured MG status may be based on the addition / release / change of a PSCell / SCell. If a pre-configured MG is configured for the UE, the addition / release / change of a PSCell / SCell by the RRC may trigger a pre-configured MG status (ON / OFF) change.

[0015] ● Case 2-1 → No need to trigger the UE to autonomously check the pre-MG status. When a PSCell / SCell is added / modified by the RRC, the pre-MG may be reconfigured together, and an indication on the pre-MG activation status may be updated together. For UEs that support network signaling based pre-configured MG status indication, further pre-MG status can be checked by network signaling. For UEs that do not support NW signaling based pre-configured MG status indication but rule based supports it, the NW will also activate pre-MG in the UE but will not forward any indication to the UE. The UE does not need to know the pre-MG status autonomously because they are already included in the RRCReconfiguration message 2.

[0016] ● Case 2-2 → Need to trigger the UE to autonomously check the pre-MG status when such an event occurs. Alternatively, if there is no update regarding the pre-MG configuration in the MO reconfiguration message: For signaling based, at least such indication table is updated and forwarded to the UE. In the rule-based case, the UE needs to be triggered to update its knowledge about the prior MG status.

[0017] In one or more embodiments, SCell activation may be the basis for triggering a pre-configured MG status.

[0018] ● Case 3-1: The UE needs to be triggered to autonomously check the pre-MG status when such an event occurs. If a pre-configured MG is configured for the UE, the SCell activation is by the MAC-CE. If the pre-configured MG activation status is known in advance by the UE considering all SCell candidates, the NW and the UE should check the pre-configured MG status when the MAC-CE for SCell activation is received.

[0019] In one or more embodiments, the rules for UE autonomous pre-MG (pre-configured MG) activation / deactivation may be as follows: Trigger events that may change the pre-MG activation status configured for the UE include: ·BWP switching Adding / removing any measurement: FFS Add / release / change SCell: FFS · Activating / deactivating any Scell: FFS.

[0020] In one or more embodiments, the triggering event itself, the following condition triggered by an RRC message, may not be feasible: When several RRC messages are being forwarded to the UE, necessary updates regarding the measurement gap configuration may be forwarded to the UE at the same time, and the advantage of pre-MG in reducing gap configuration time would be diminished.

[0021] In one or more embodiments, if the MO configuration is changed, the pre-MG can be reconfigured together in the IE for the MO (e.g., RRCReconfiguation). A new indication regarding the pre-MG activation status can also be updated. The network also activates the pre-MG.

[0022] In one or more embodiments, in case of a signaling-based trigger, the updated pre-MG status indication may be forwarded to the UE in an RRC message for MG reconfiguration. For a rule-based pre-MG activation status indication, the network may not forward any indication to the UE. However, the UE may not need to autonomously identify the pre-MG status since the status may be included in the RRC Reconfiguration message.

[0023] In one or more embodiments, if there is no update regarding the pre-MG configuration in the MO reconfiguration message, for a signaling-based trigger, at least the indication table may be updated and forwarded to the UE, and for a rule-based trigger, the UE may need to be triggered to update its knowledge about the pre-MG status.

[0024] RRCReconfiguration-IEs::= SEQUENCE{ radioBearerConfig RadioBearerConfig OPTIONAL,--Need M secondaryCellGroup OCTET STRING(CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG measConfig MeasConfig OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfiguration-v1530-IEs OPTIONAL } MeasConfig::= SEQUENCE{ measObjectToRemoveList MeasObjectToRemoveList OPTIONAL, -- Need N measObjectToAddModList MeasObjectToAddModList 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 OPTIONAL, -- Need M preMGActivationStatus measGapSharingConfig MeasGapSharingConfig OPTIONAL, -- Need M ..., [[ interFrequencyConfig-NoGap-r16 ENUMERATED {true} OPTIONAL -- Need R ]] }

[0025] In one or more embodiments, the trigger may be for a single CC with one MO. Typical configuration parameters for the case under this scenario are listed below: PCell@f0, BWP0, 4 candidate BWPs Case 1-1: MO#1, intra-f:@f0, BWP0, SSB / CSI-RS [Table 1] Case 1-2: MO#1, intra-f:@f0, BWP1 (different from UE initial active BWP), SSB / CSI-RS [Table 2]

[0026] In one or more embodiments, for a single CC scenario, a BWP switch may trigger a pre-MG status transition.

[0027] Scenario 2: Single CC, >1 MO: Typical configuration parameters for cases under this scenario are listed below. PCell@f0, BWP0, 4 candidate BWPs Case 2-1 MO#1, intra-f:@f0, BWP0, SSB MO#2, intra-f:@f0, BWP0, SSB [Table 3]

[0028] In one or more embodiments, if multiple MOs are in the same frequency layer (eg, including the BWP), the possible pre-MG status transitions may be the same as in Scenario 1.

[0029] Case 2-2: MO#1, intra-f:@f0, BWP0, SSB MO#2, intra-f, gapped: @f0, BWP1, SSB [Table 4]

[0030] Case 2-3: MO#1, intra-f:@f0, BWP0, SSB MO#2, inter-f, with gap:@f1, BWP1, SSB [Table 5]

[0031] In one or more embodiments, for a single CC with multiple MOs, if all MOs may be included within the UE's activated BWP before or after the UE active BWP switch, the pre-MG (de)activation status may be changed at the time of BWP switch.

[0032] Scenario 3: CA: multiple CCs, single BWP switching occurs on PCell / PSCell / SCell, no SCell activation / deactivation.

[0033] The general configuration parameters for these cases are: PCell@f0, BWP0, SCell@f1, BWP0, 4 candidate BWPs Case 3-1: PCell@f0 and SCell@f1 are activated. MO#1, intra-f:@f0, BWP0, SSB;). [Table 6]

[0034] Case 3-2: MO#1, intra-f:@f0, BWP0, SSB MO#2, intra-f:@f1, BWP0, SSB [Table 7]

[0035] In one or more embodiments, for MO#2, it is on the same frequency layer as the activated BWP of the UE in the other SCell. Since only single BWP switching is allowed, for MO#2, the UE that needs to be on the activated gap can remain in the initial status.

[0036] Case 3-3: PCell@f0 and SCell@f1 are activated MO#1, intra-f:@f0, BWP0, SSB MO#2, intra-f:@f1, BWP1, SSB [Table 8]

[0037] In one or more embodiments, for CA scenarios without SCell activation, if it is possible that the frequency layer of the MO is not included within the activated BWP of the UE on either the PCell or the SCell, the pre-MG status at the time of BWP switching may be changed.

[0038] In one or more embodiments, pre-MG triggering may occur only on multiple CCs with SCell activation / deactivation. The general configuration parameters for those cases are as follows: PCell@f0, BWP0, SCell@f1, BWP0, 4 candidate BWPs

[0039] In one or more embodiments, when SCell activation is triggered by the MAC-CE, the association between the pre-MG and the BWP may be changed, and possible rules for activating the pre-MG may be updated accordingly. Case 4-1: MO#1, intra-f:@f0, BWP0, SSB.

[0040] In one or more embodiments, when only SCell activation occurs (e.g., no BWP switching), after the pre-MG is configured, the pre-MG status may remain unchanged if the MO can be included by either the activated BWP of the PCell or another activated SCell. Case 4-2: MO#1, intra-f:@f0, BWP1, SSB.

[0041] In one or more embodiments, when SCell activation only occurs (e.g., without BWP switching), after the pre-MG is configured, if the MO cannot be contained by either the activated BWP of the PCell or another activated SCell, the activated pre-MG is always required while the SCell is activated.

[0042] In one or more embodiments, if SCell activation occurs after pre-MG is configured and MO cannot be included by the activated BWP of the UE on the SCell to be activated, the pre-MG status may remain unchanged.

[0043] Case 4-3: MO#1, intra-f:@f1, BWP0, SSB.

[0044] In one or more embodiments, if SCell activation occurs after pre-MG is configured, the pre-MG activation status may be changed if the MO is not included in the UE's activated BWP in either the PCell or another SCell to be activated, and is included in the UE's activated BWP in the SCell to be activated.

[0045] In one or more embodiments, there may be multiple CCs with both Scell ​​activation / deactivation and BWP switching (eg, only a single BWP switching has occurred in the PCell).

[0046] The general configuration parameters for all the following cases are: PCell@f0, BWP0, SCell@f1, BWP0, 4 candidate BWPs. Case 5-1 MO#1, intra-f:@f0, BWP0, SSB BWP switching in PCell@f0 Deactivate -> Activate @f1.

[0047] In one or more embodiments, when MO can be included by the UE's activated BWP on the PCC, there may be no impact on the pre-MG status from SCell activation, and there may only be an impact from the activated BWP switching on the PCC.

[0048] Case 5-2: MO#1:intra-f:@f1, BWP0, SSB BWP switching in PCell@f0 Deactivate -> Activate @f1.

[0049] In one or more embodiments, there is an impact on the pre-MG status from SCell activation when the MO may be included by the activated BWP of the UE in the SCC to be activated.

[0050] Case 5-3 MO#1, inter-f(after activation):@f2, BWP0, SSB MO#2:NA Deactivate → Activate @f1 In one or more embodiments, there will be no impact on the pre-MG status from SCell activation when the MO cannot be held as activated or included by the activated BWP of the UE in any PCell / SCell to be activated.

[0051] In one or more embodiments, in the case of CA, impacts from SCell (de)activation and BWP switching can independently trigger pre-MG status changes.

[0052] The above description is for purposes of illustration and is not intended to be limiting. There may be many other examples, configurations, processes, algorithms, etc., some of which are described in more detail below. Example embodiments will now be described with reference to the accompanying drawings.

[0053] FIG. 1 is a network diagram illustrating an example network environment 100, in accordance with one or more exemplary embodiments of the present disclosure.

[0054] The wireless network 100 may include one or more UEs 120 and one or more RANs 102 (e.g., gNBs), which may communicate according to 3GPP communication standards. The UEs 120 may be mobile devices that are non-fixed (e.g., do not have a fixed location) or may be fixed devices.

[0055] In some embodiments, the UE 120 and the RAN 102 may include one or more computer systems similar to those of FIGS.

[0056] One or more exemplary UEs 120 and / or RAN 102 may be operable by one or more users 110. A UE may take on multiple different characteristics, each of which shapes its functionality. For example, a single addressable unit may simultaneously be a portable UE, a quality of service (QoS) UE, a dependent UE, and a hidden UE. The UEs 120 (e.g., 124, 126, or 128) and / or RAN 102 may include any suitable processor-driven device, including, but not limited to, a mobile device or a non-mobile, e.g., static, device. For example, the UE 120 may be a software enabled AP (SoftAP), a personal computer, a wearable wireless device (e.g., a bracelet, a watch, glasses, a ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabook™ computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an Internet of Things (IoT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular telephone functionality with PDA device functionality), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular phone, a PCS device, a PDA device incorporating a wireless communications device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CLOSE) device ...large, CSLL devices, ultra mobile devices (UMD), ultra mobile PCs (UMPCs), mobile internet devices (MIDs), "origami" devices or computing devices, devices supporting dynamically configurable computing (DCC), context aware devices, video devices, audio devices, A / V devices, set top boxes (STBs), Blu-ray disc (BD) players, BD recorders, digital video disc (DVD) players, high definition (HD) DVD players, DVD recorders, HD DVD recorders, personal video recorders (PVRs), broadcast HD receivers, video sources, audio sources, video sinks, audio sinks, stereo tuners, broadcast radio receivers, flat panel displays, personal media players (PMPs), digital video cameras (DVCs), digital audio players, speakers, audio receivers, audio amplifiers, gaming devices, data sources, data sinks, digital still cameras (DSCs), media players, smartphones, televisions, music players, etc. Other devices may be included in this list, including smart devices such as lamps, environmental controls, automotive parts, household parts, appliances, etc.

[0057] As used herein, the term "Internet of Things (IoT) device" is used to refer to any object (e.g., appliance, sensor, etc.) that has an addressable interface (e.g., Internet Protocol (IP) address, Bluetooth® identifier (ID), Near Field Communication (NFC) ID, etc.) and can transmit information to one or more other devices through a wired or wireless connection. An IoT device may have a passive communication interface, such as a Quick Response (QR) code, Radio Frequency Identification (RFID) tag, NFC tag, or an active communication interface, such as a modem, transceiver, transmitter-receiver, etc. An IoT device may have a particular set of attributes (e.g., device state or status, such as whether the IoT device is on or off, open or closed, idle or active, available or busy for task execution, cooling or heating capabilities, environmental monitoring or recording capabilities, light emitting capabilities, sound emitting capabilities, etc.) that may be incorporated into and / or controlled / monitored by a central processing unit (CPU), microprocessor, ASIC, etc., and configured for connection to an IoT network, such as a local ad-hoc network or the Internet. For example, IoT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, lighting fixtures, vacuum cleaners, sprinklers, electric meters, gas meters, etc. IoT devices may also include mobile phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc., so long as the devices are equipped with an addressable communication interface for communicating with an IoT network.Thus, an IoT network may be comprised of a combination of “legacy” Internet-accessible devices (e.g., laptop or desktop computers, mobile phones, etc.) in addition to devices that typically do not have Internet connectivity (e.g., dishwashers).

[0058] The UEs 120 (e.g., UEs 124, 126, 128) and any of the UEs 120 may be configured to communicate with each other wirelessly or wired via one or more communications networks 130 and / or 135. The UEs 120 may also communicate with each other peer-to-peer or directly, with or without the RAN 102. Any of the communications networks 130 and / or 135 may include any one of a combination of different types of suitable communications networks, such as, for example, but not limited to, a broadcast network, a cable network, a public network (e.g., the Internet), a private network, a wireless network, a cellular network, or any other suitable private and / or public network. Additionally, any of the communications networks 130 and / or 135 may have any suitable communication range associated therewith and may include, for example, a cellular network. Additionally, any of communications networks 130 and / or 135 may include any type of medium over which network traffic may be carried, including, but not limited to, coaxial cable, twisted pair wire, optical fiber, hybrid fiber coaxial (HFC) medium, microwave terrestrial transceiver, radio frequency communications medium, white space communications medium, ultra-high frequency communications medium, satellite communications medium, or any combination thereof.

[0059] Any of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antenna compatible with the communications protocol used by the UEs 120 (e.g., UEs 124, 126, and 128) and the RAN 102. Some non-limiting examples of suitable communications antennas include cellular antennas, 3GPP standards compatible antennas, directional antennas, omni-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple input multiple output (MIMO) antennas, omni-directional antennas, quasi-omni-directional antennas, etc. The one or more communications antennas may be communicatively coupled to radio components for transmitting and / or receiving signals, such as communication signals, to and / or from the UEs 120 and / or the RAN 102.

[0060] Any of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform directional transmission and / or directional reception in connection with wirelessly communicating in a wireless network. Any of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform such directional transmission and / or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays, etc.). Each of the multiple antenna arrays may be used for transmission and / or reception in a particular respective direction or range of directions. Any of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform any given directional transmission toward one or more defined transmitting sectors. Any of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may be configured to perform any given directional reception from one or more defined receiving sectors.

[0061] MIMO beamforming in wireless networks may be achieved using RF beamforming and / or digital beamforming. In some embodiments, when performing a given MIMO transmission, the UE 120 and / or the RAN 102 may be configured to use all or a subset of its one or more communication antennas to perform MIMO beamforming.

[0062] Either of the UEs 120 (e.g., UEs 124, 126, 128) and the RAN 102 may include any suitable radio and / or transceiver for transmitting and / or receiving radio frequency (RF) signals in a bandwidth and / or channel corresponding to a communication protocol utilized by either of the UEs 120 and the RAN 102 to communicate with each other. The radio components may include hardware and / or software for modulating and / or demodulating communication signals according to a pre-established transmission protocol. The radio components may further have hardware and / or software instructions for communicating via one or more 3GPP protocols and using the 3GPP bandwidth. The radio components may include any known receiver and baseband suitable for communicating via the communication protocol. The radio components may further include a low noise amplifier (LNA), an additional signal amplifier, an analog-to-digital (A / D) converter, one or more buffers, and a digital baseband.

[0063] 1, in one or more embodiments, one or more of the UEs 120 may exchange frames 140 with the RAN 102. The frames 140 may include RRC messages related to triggering activation of pre-configured MGs, indications of MO changes, addition, release, modification, activation of primary and secondary cells, etc., as described herein.

[0064] It is understood that the above description is for purposes of illustration and is not intended to be limiting.

[0065] FIG. 2 illustrates an example process 200 for triggering pre-configured measurement gap activation or deactivation using measurement object reconfiguration, in accordance with one or more example embodiments of the present disclosure.

[0066] 2, process 200 may include a UE (e.g., of UE 120 in FIG. 1) using measurement object 202 (e.g., neighboring cell 1 transmitting at frequency f), measurement object 204 (e.g., neighboring cell 2 transmitting at frequency f), serving cell 206 (e.g., transmitting at frequency f), UE receive frequency 208 using frequency f, and UE receive frequency 210 using frequency f. Neighboring cell 1 may receive SSBs 212, 214, 216, and 218 (e.g., from RAN 102 in FIG. 1). Neighboring cell 2 may receive SSBs 220, 222, 224, and 226 (e.g., from RAN 102 in FIG. 1). The serving cell 206 may indicate 228 that pre-configured MG 1 has been configured using an RRC reconfiguration in an RRC message to the UE receive frequency 208, which may use an intra-BWP PRB 230. The UE may perform measurements 232 without MG during pre-MG 1 in the serving cell 206. The serving cell 206 may indicate 234 a measurement object reconfiguration to the UE receive frequency 208 (e.g., using an RRC reconfiguration message indicating pre-MG 2). The measurement object reconfiguration may trigger a pre-MG 2 in the serving cell 206 (during which the UE may perform measurements 236 in the UE receive frequency 210) and a subsequent pre-MG (during which the UE may perform measurements 238 in the UE receive frequency 210).

[0067] FIG. 3 illustrates an example process 300 for triggering pre-configured measurement gap activation or deactivation using secondary cell activation, in accordance with one or more example embodiments of the present disclosure.

[0068] 3, process 300 may include a UE (e.g., of UE 120 of FIG. 1) using a measurement object 302 (e.g., neighboring cell 1 transmitting at frequency f1), a serving cell 304 (e.g., a primary cell, transmitting at frequency f0), a frequency 306, a UE receive frequency 308 using the primary cell, frequency f0, and a UE receive frequency 310 using the secondary cell, frequency f1. Neighboring cell 1 may receive SSBs 312, 314, 316, and 318 (e.g., from RAN 102 of FIG. 1). The serving cell 304 may indicate 320 a prior MG 1 configuration to the UE receive frequency 308 using an RRC configuration indicator. The UE receive frequency 308 may use an intra-BWP PRB 322. During pre-MG 1, the UE may measure the measurement object 302 using MG, and the UE may need to measure the secondary cell on the deactivated frequency f1 (e.g., with no gaps and with a longer cycle, such as 640 ms). The serving cell 304 may indicate 324 to the UE reception frequency 308 that the secondary cell has been activated by the MAC CE. The UE may measure the measurement object 302 using gaps during SSB 314 (e.g., pre-MG 2). The serving cell 304 may indicate 326 to the UE reception frequency 308 that the secondary cell has been deactivated by the MAC CE, and the UE may measure the measurement object 302 during SSB 316 (e.g., pre-MG 3).

[0069] FIG. 4 illustrates an example process 400 for triggering preconfigured measurement gap activation or deactivation by adding, releasing, or modifying a primary or secondary cell, in accordance with one or more example embodiments of the present disclosure.

[0070] 4, a UE (e.g., of UE 120 in FIG. 1) may use a serving cell 402 at frequency f0, a UE receive frequency 404 at frequency f0, and a UE receive frequency 406 at frequency f1. The serving cell 402 may indicate a pre-MG 1 configuration using an RRC reconfiguration indication for the UE receive frequency 404. The UE receive frequency 404 may use an intra-BWP PRB 410 and may perform measurements 412 during pre-MG 1 without gaps. The serving cell 402 may indicate 414 a MO reconfiguration using an RRC reconfiguration indicator for pre-MG 2 for the UE receive frequency 404, and during pre-MG 2, the UE may perform measurements 416 and 418 with gaps on the UE receive frequency 406.

[0071] FIG. 5 illustrates an example process 500 for triggering pre-configured measurement gap activation or deactivation by triggering a user equipment device to autonomously check a pre-configured measurement gap status, according to one or more example embodiments of the present disclosure.

[0072] 5, a UE (e.g., of UE 120 in FIG. 1) may use a serving cell 502 at frequency f0, a UE receive frequency 504 at f0, and a UE receive frequency 506 at frequency f1. The serving cell 502 may indicate 508 a pre-MG 1 configuration to the UE receive frequency 504 using an RRC reconfiguration indication. The UE receive frequency 504 may use an intra-BWP PRB 510 and may perform measurements 512 during pre-MG 1 without gaps. The serving cell 502 may indicate 514 a secondary cell activation by the MAC CE to the UE receive frequency 504. As a result, the UE may perform measurements 516 and 518 with gaps during pre-MG 2 on the UE receive frequency 506.

[0073] FIG. 6A is a table 600 of parameters for case 4-1, according to one or more exemplary embodiments of the present disclosure.

[0074] When only SCell activation occurs (e.g., there is no BWP switching), after the pre-MG is configured, the pre-MG status may remain unchanged if the MO may be included by either the activated BWP of the PCell or another activated SCell.

[0075] FIG. 6B is a table 620 of parameters for case 4-2, according to one or more exemplary embodiments of the present disclosure.

[0076] When only SCell activation occurs (e.g., there is no BWP switching), after the pre-MG is configured, if the MO cannot be contained by either the activated BWP of the PCell or the activated SCell, an activated pre-MG is required while the SCell is activated.

[0077] When SCell activation occurs after pre-MG is configured, if the MO cannot be included by the UE's activated BWP on the SCell to be activated, the pre-MG status may remain unchanged.

[0078] FIG. 6C is a table 640 of parameters for case 4-3, according to one or more exemplary embodiments of the present disclosure.

[0079] When SCell activation occurs after pre-MG is configured, the pre-MG activation status may be changed if the MO is not included by the UE's activated BWP in either the activated PCell or other SCell, but is included by the UE's activated BWP in the SCell to be activated.

[0080] FIG. 6D is a table 650 of parameters for case 5-1, according to one or more exemplary embodiments of the present disclosure.

[0081] If the MO can be included by the UE's activated BWP in the PCC, there is no impact on the pre-MG status from the SCell activation, only impact from the activated BWP switch in the PCC.

[0082] FIG. 6E is a table 660 of parameters for case 5-2, according to one or more exemplary embodiments of the present disclosure.

[0083] If the MO can be included by the activated BWP of the UE in the SCC to be activated, there is an impact on the pre-MG status from the SCell activation.

[0084] FIG. 6F is a table 670 of parameters for case 5-3, according to one or more exemplary embodiments of the present disclosure.

[0085] If the MO cannot be included by the activated BWP of the UE in any PCell / SCell that is to be kept as activated or activated, there will be no impact on the pre-MG status from SCell activation.

[0086] In case of CA, the impact from SCell (de)activation and BWP switching can independently trigger pre-MG status changes.

[0087] FIG. 7 illustrates a flow diagram of an example process 700 for triggering activation or deactivation of pre-configured measurement gaps in wireless communications, in accordance with one or more example embodiments of the present disclosure.

[0088] At block 702, a device (eg, UE 120 in FIG. 1, UE 802 in FIG. 8) may detect a pre-configured measurement gap (pre-MG) configured by the network.

[0089] At block 704, the device may detect that the pre-configured measurement gap should be activated or deactivated. Detection may use any of the techniques described herein.

[0090] At block 706, the device may activate or deactivate the preconfigured measurement gap based on detecting that the preconfigured measurement gap should be activated or deactivated.

[0091] These embodiments are not intended to be limiting.

[0092] 8 illustrates a network 800 according to various embodiments. Network 800 may operate in a manner consistent with 3GPP technical specifications 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.

[0093] The network 800 may include a UE 802, which may include any mobile or non-mobile computing device designed to communicate with the RAN 804 via an over-the-air connection. The UE 802 may be communicatively coupled to the RAN 804 by a Uu interface. The UE 802 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 network appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.

[0094] In some embodiments, the network 800 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, the PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

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

[0096] The RAN 804 may include one or more access nodes, e.g., AN 808. The AN 808 may terminate air interface protocols for the UE 802 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this manner, the AN 808 may enable data / voice connectivity between the CN 820 and the UE 802. In some embodiments, the AN 808 may be implemented in a discrete device or as one or more software entities running on a server computer as part of a virtual network, e.g., which may be referred to as a CRAN or a virtual baseband unit pool. The AN 808 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 808 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.

[0097] In embodiments where the RAN 804 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 804 is an LTE RAN) or an Xn interface (if the RAN 804 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.

[0098] Each of the ANs of the RAN 804 may manage one or more cells, cell groups, component carriers, etc., to provide the UE 802 with an air interface for network access. The UE 802 may be simultaneously connected to multiple cells provided by the same or different ANs of the RAN 804. For example, the UE 802 and the RAN 804 may use carrier aggregation that allows the UE 802 to connect with multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity 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.

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

[0100] In a V2X scenario, the UE 802 or AN 808 may be or act as an RSU, which may refer to any transportation infrastructure entity used for V2X communications. The RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be referred to as a "UE type RSU", in the case of an eNB it may be referred to as an "eNB type RSU", in the case of a gNB it may be referred to as a "gNB type RSU", etc. In one example, the RSU is a computing device coupled to radio frequency circuitry located on 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 required for high speed events such as collision avoidance, traffic alerts, etc. 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.

[0101] In some embodiments, the RAN 804 may be an eNB, e.g., an LTE RAN 810 having an eNB 812. The LTE RAN 840 may provide an LTE air interface with the following characteristics: 15 kHz SCS; CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL; turbo codes for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on sub-6 GHz bands.

[0102] In some embodiments, the RAN 804 may be an NG-RAN 814 having a gNB, e.g., gNB 816, or an ng-eNB, e.g., ng-eNB 818. The gNB 816 may connect with a 5G-capable UE using a 5G NR interface. The gNB 816 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 818 may also connect with the 5G core through an NG interface, but may connect with the UE via an LTE air interface. The gNB 816 and the ng-eNB 818 may connect with each other through an Xn interface.

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

[0104] The NG-RAN 814 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.

[0105] In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs may be used for dynamic adaptation of the SCS. For example, a UE 802 may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to the UE 802, 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 802 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP that includes a smaller number of PRBs may be used for data transmissions with a small traffic load while enabling power savings at the UE 802 and possibly at the gNB 816. A BWP that includes a larger number of PRBs may be used for scenarios with a higher traffic load.

[0106] The RAN 804 is communicatively coupled to the CN 820, which includes network elements for providing various functions to customers / subscribers (e.g., users of UEs 802) for supporting data and telecommunication services. The components of the CN 820 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 820 onto physical compute / storage resources in servers, switches, etc. A logical instantiation of the CN 820 may be referred to as a network slice, and a logical instantiation of a portion of the CN 820 may be referred to as a network sub-slice.

[0107] In some embodiments, CN 820 may be an LTE CN 822, sometimes referred to as an EPC. LTE CN 822 may include an MME 824, an SGW 826, an SGSN 828, an HSS 830, a PGW 832, and a PCRF 834 coupled together through interfaces (or "reference points") as shown. The functionality of the elements of LTE CN 822 may be briefly introduced as follows.

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

[0109] The SGW 826 terminates the S1 interface towards the RAN and can route data packets between the RAN and the LTE CN 822. The SGW 826 may be a local mobility anchor point for inter-RAN node handover and may provide an anchor for inter-3GPP mobility. Other roles may include lawful interception, charging, and some policy enforcement.

[0110] The SGSN 828 may track the location of the UE 802 and perform security functions and access control. Additionally, the SGSN 828 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection specified by the MME 824; MME selection for handover, etc. The S3 reference point between the MME 824 and the SGSN 828 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.

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

[0112] The PGW 832 may terminate an SGi interface towards a data network (DN) 836, which may include an application / content server 838. The PGW 832 may route data packets between the LTE CN 822 and the data network 836. The PGW 832 may be coupled to the SGW 826 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 832 may further include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 832 and the data network 836 may be an operator external public, private PDN, or intra-operator packet data network, e.g., for the provision of IMS services. The PGW 832 may be coupled to the PCRF 834 via a Gx reference point.

[0113] The PCRF 834 is the policy and charging control element of the LTE CN 822. The PCRF 834 may be communicatively coupled to an app / content server 838 to determine appropriate QoS and charging parameters for a service flow. The PCRF 832 may provision the PCEF (via the Gx reference point) with the appropriate TFT and associated rules with the QCI.

[0114] In some embodiments, CN 820 may be a 5GC 840. 5GC 840 may include AUSF 842, AMF 844, SMF 846, UPF 848, NSSF 850, NEF 852, NRF 854, PCF 856, UDM 858, AF 860, and LMF 862 coupled together through interfaces (or "reference points") as shown. The functionality of the elements of 5GC 840 may be briefly introduced as follows.

[0115] The AUSF 842 may store data and handle authentication related functions for authentication of the UE 802. The AUSF 842 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 840 through reference points as shown, the AUSF 842 may present a Nausf service-based interface.

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

[0117] The SMF 846 may be responsible for SM (e.g., session establishment, tunnel management between the UPF 848 and the AN 808); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering in the UPF 848 to route traffic to the appropriate destination; termination of the interface to the policy control function; control of policy enforcement, charging, and parts of QoS; lawful interception (for SM events and the interface to the L1 system); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent over the N2 to the AN 808 via the AMF 844; and determination of 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 802 and the data network 836.

[0118] The UPF 848 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnection to the data network 836, and a branching point to support multi-homed PDU sessions. The UPF 848 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 848 may include an uplink classifier to support routing of traffic flows to the data network.

[0119] The NSSF 850 ​​may select a set of network slice instances to serve the UE 802. The NSSF 850 ​​may also determine the allowable NSSAIs and mapping to subscribed S-NSSAIs, if necessary. The NSSF 850 ​​may also determine the AMF set, or a list of candidate AMFs, to be used to serve the UE 802 based on a preferred configuration and possibly by querying the NRF 854. The selection of a set of network slice instances for the UE 802 may be triggered by the AMF 844 to which the UE 802 is registered, by interacting with the NSSF 850, which may result in a change of AMF. The NSSF 850 ​​may interact with the AMF 844 via the N22 reference point and may communicate with another NSSF in a visited network via the N31 reference point (not shown). In addition, the NSSF 850 ​​may exhibit an Nnssf service-based interface.

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

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

[0122] The PCF 856 may provide policy rules to control plane functions that enforce them and may support a unified policy framework to govern network behavior. The PCF 856 may also implement a front end to access subscription information related to policy decisions within the UDRs of the UDM 858. In addition to communicating with functions through reference points as shown, the PCF 856 also exhibits an Npcf service-based interface.

[0123] The UDM 858 can process subscription related information to support network entity processing of communication sessions and can store subscription data of the UE 802. For example, the subscription data can be communicated via the N8 reference point between the UDM 858 and the AMF 844. The UDM 858 can include two parts: an application front end and a UDR. The UDR can store subscription data and policy data for the UDM 858 and the PCF 856, and / or structured data for publishing and application data for the NEF 852 (including PFD for application discovery, application request information for multiple UEs 802). The Nudr service-based interface is represented by the UDR 821 to allow the UDM 858, the PCF 856, and the NEF 852 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 credential handling, 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 credential handling, user identification handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 858 may also exhibit a Nudm service-based interface.

[0124] The AF 860 provides application influence over traffic routing, provides access to the NEF, and can interact with the policy framework for policy control.

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

[0126] Data network 836 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers, including, for example, application / content server 838 .

[0127] FIG. 9 illustrates a schematic of a wireless network 900 in accordance with various embodiments.

[0128] The wireless network 900 may include a UE 902 in wireless communication with an AN 904. The UE 902 and the AN 904 may be similar to and substantially interchangeable with similarly named components described elsewhere herein.

[0129] The UE 902 may be communicatively coupled to the AN 904 via a connection 906. The connection 906 is shown as an air interface for enabling the communicative coupling and may be consistent with a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mm-wave or sub-6 GHz frequencies.

[0130] The UE 902 may include a host platform 908 coupled to a modem platform 910. The host platform 908 may include an application processing circuit 912 that may be coupled to a protocol processing circuit 914 of the modem platform 910. The application processing circuit 912 may execute various applications for the UE 902 to source / sink application data. The application processing circuit 912 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

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

[0132] The modem platform 910 may further include digital baseband circuitry 916 that may implement one or more layer operations that are "lower" layer operations in a network protocol stack performed by the protocol processing circuitry 914. 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 pre-coding / 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.

[0133] The modem platform 910 may further include transmit circuitry 918, receive circuitry 920, RF circuitry 922, and an RF front end (RFFE) 924, which may include or be connected to one or more antenna panels 926. Briefly, the transmit circuitry 918 may include digital-to-analog converters, mixers, intermediate frequency (IF) components, etc.; the receive circuitry 920 may include analog-to-digital converters, mixers, IF components, etc.; the RF circuitry 922 may include low noise amplifiers, power amplifiers, power tracking components, etc.; the RFFE 924 may include filters (e.g., surface / volume acoustic wave filters), switches, antenna tuners, beamforming components (e.g., phased array antenna components), etc. The selection and arrangement of the transmit circuitry 918, receive circuitry 920, RF circuitry 922, RFFE 924, and antenna panel 926 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, etc. In some embodiments, the transmit / receive components may be arranged in multiple parallel transmit / receive chains, may be located on the same or different chips / modules, etc.

[0134] In some embodiments, the protocol processing circuit 914 may include one or more instances of control circuitry (not shown) to provide control functions for the transmitting and receiving components.

[0135] UE reception may be established by and through the antenna panel 926, the RFFE 924, the RF circuitry 922, the receive circuitry 920, the digital baseband circuitry 916, and the protocol processing circuitry 914. In some embodiments, the antenna panel 926 may receive transmissions from the AN 904 by receive beamforming signals received by multiple antennas / antenna elements of one or more of the antenna panels 926.

[0136] UE transmissions may be established by and through protocol processing circuitry 914, digital baseband circuitry 916, transmit circuitry 918, RF circuitry 922, RFFE 924, and antenna panel 926. In some embodiments, the transmit components of the UE 904 may apply spatial filters to data to be transmitted to form transmit beams emitted by antenna elements of the antenna panel 927.

[0137] Similar to the UE 902, the AN 904 may include a host platform 928 coupled to a modem platform 930. The host platform 928 may include an application processing circuit 932 coupled to a protocol processing circuit 934 of the modem platform 930. The modem platform may further include a digital baseband circuit 936, a transmit circuit 938, a receive circuit 940, an RF circuit 942, an RFFE circuit 944, and an antenna panel 946. The components of the AN 904 may be similar to and substantially interchangeable with similarly named components of the UE 902. In addition to performing data transmission / reception as described above, the components of the AN 908 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.

[0138] FIG. 10 is a block diagram illustrating components according to various embodiments. The components may 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. In particular, FIG. 10 illustrates a schematic diagram of hardware resources 1000 including one or more processors (or processor cores) 1010, one or more memory / storage devices 1020, and one or more communication resources 1030, each of which may be communicatively coupled via a bus 1040 or other interface circuitry. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1002 may be executed to provide an execution environment in which one or more network slices / sub-slices utilize the hardware resources 1000.

[0139] Processor 1010 may include, for example, processor 1012 and processor 1014. Processor 1010 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.

[0140] The memory / storage device 1020 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1020 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.

[0141] The communications resources 1030 may include interconnect or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 1004 or one or more databases 1006 or other network elements over the network 1008. For example, the communications resources 1030 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.

[0142] The instructions 1050 may include software, programs, applications, applets, apps, or other executable code for causing the processor 1010 to perform any one or more of the methods described herein. The instructions 1050 may reside completely or partially within at least one of the processor 1010 (e.g., in a cache memory of the processor), the memory / storage device 1020, or any suitable combination thereof. Furthermore, any portion of the instructions 1050 may be transferred to the hardware resources 1000 from any combination of the peripheral device 1004 or the database 1006. Thus, the memory of the processor 1010, the memory / storage device 1020, the peripheral device 1004, and the database 1006 are examples of computer-readable and machine-readable media.

[0143] The following examples relate to further embodiments.

[0144] For one or more embodiments, at least one of the components depicted 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. In another example, 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 in the exemplary section below.

[0145] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described in the specification as "exemplary" should not necessarily be construed as preferred or advantageous over other embodiments. As used herein, the terms "computing device," "user device," "communication station," "station," "handheld device," "mobile device," "wireless device," and "user equipment" (UE) refer to wireless communication devices such as cellular phones, smartphones, tablets, netbooks, wireless terminals, laptop computers, femtocells, high data rate (HDR) subscriber stations, access points, printers, point-of-sale devices, access terminals, or other personal communications system (PCS) devices. The devices may be mobile or fixed.

[0146] As used herein, the term "communicating" is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing an organization of data transmitted by one device and received by another, but only the functionality of one of the devices is required to infringe a claim. Similarly, a two-way exchange of data between two devices (both devices transmit and receive during the exchange) may be described as "communicating" when only the functionality of one of the devices is claimed. The term "communicating" as used herein with respect to wireless communication signals includes transmitting wireless communication signals and / or receiving wireless communication signals. For example, a wireless communication unit capable of communicating wireless communication signals may include a wireless transmitter for transmitting wireless communication signals to at least one other wireless communication unit and / or a wireless communication receiver for receiving wireless communication signals from at least one other wireless communication unit.

[0147] As used herein, unless otherwise specified, the use of ordinal adjectives "first," "second," "third," etc. to describe a common object merely indicates that different instances of a similar object are being referred to, and is not intended to imply that the objects so described must be in a given order, temporally, spatially, in ranking, or in any other manner.

[0148] As used herein, the term "access point" (AP) may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved Node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be referred to as a mobile station, a user equipment (UE), a wireless communication device, or some other similar terminology known in the art. FIELD OF THE DISCLOSURE The embodiments disclosed herein relate generally to wireless networks. Some embodiments may relate to wireless networks that operate according to one of the IEEE 802.11 standards.

[0149] Some embodiments may be used with various devices and systems, such as a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A / V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.

[0150] Some embodiments may be used with one-way and / or two-way wireless communication systems, cellular radiotelephone communication systems, mobile phones, cellular telephones, wireless telephones, personal communication system (PCS) devices, PDA devices incorporating wireless communication devices, mobile or portable global positioning system (GPS) devices, devices incorporating GPS receivers or transceivers or chips, devices incorporating RFID elements or chips, multiple-input multiple-output (MIMO) transceivers or devices, single-input multiple-output (SIMO) transceivers or devices, multiple-input single-output (MISO) transceivers or devices, devices having one or more internal antennas and / or external antennas, digital video broadcast (DVB) devices or systems, multi-standard wireless devices or systems, wired or wireless handheld devices, such as smartphones, Wireless Application Protocol (WAP) devices, and the like.

[0151] Some embodiments may be implemented using one or more wireless communication protocols, such as radio frequency (RF), infrared (IR), frequency division multiplexing (FDM), orthogonal FDM (OFDM), time division multiplexing (TDM), time division multiple access (TDMA), enhanced TDMA (E-TDMA), general packet radio service (GPRS), enhanced GPRS, code division multiple access (CDMA), wideband CDMA (WCDMA), CDMA2000, single carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multitone (DMT), Bl The present invention may be used in conjunction with one or more types of wireless communication signals and / or systems in accordance with Bluetooth, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee, Ultra Wideband (UWB), Global System for Mobile Communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, Fifth Generation (5G) mobile networks, 3GPP, Long Term Evolution (LTE), LTE Advanced, Enhanced Data Rates for GSM Evolution (EDGE), etc. Other embodiments may be used in various other devices, systems, and / or networks.

[0152] Various embodiments are described below.

[0153] Example 1 may include an apparatus for a user equipment device (UE) device for activating and deactivating a pre-configured measurement gap in carrier aggregation, the apparatus having a processing circuit coupled to a storage that stores information associated with the pre-configured measurement gap, the processing circuit configured to: detect a pre-configured measurement gap configured by a network; detect that the pre-configured measurement gap should be activated or deactivated; and activate or deactivate the pre-configured measurement gap based on detecting that the pre-configured measurement gap should be activated or deactivated.

[0154] Example 2 may include the apparatus of example 1, where the processing circuitry is further configured to: detect an addition or removal of a measurement object associated with the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated is based on the detection of the addition or removal of the measurement object.

[0155] Example 3 may include the apparatus of example 2, where the processing circuitry is further configured to: detect a network controlled activation or deactivation indication based on a Radio Resource Control (RRC) measurement gap list from the network, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting the network controlled activation or deactivation indication.

[0156] Example 4 may include the apparatus of example 3, wherein the RRC measurement gap list includes an indication of measurement target change.

[0157] Example 5 may include the apparatus of example 3, wherein the RRC measurement gap list cannot be reconfigured and updated by the network with measurement target changes.

[0158] Example 6 may include the apparatus of example 2, where the processing circuitry is further configured to: autonomously identify a status of the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated is based on the autonomous identification of the status.

[0159] Example 7 may include the apparatus of example 1, where the processing circuitry is further configured to: detect activation or deactivation of a secondary cell, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting the activation or deactivation of the secondary cell.

[0160] Example 8 may include the apparatus of example 7, where the processing circuitry is further configured to: detect that a status of the preconfigured measurement gap should be updated based on whether a frequency layer to be measured is included by a bandwidth portion activated by a primary cell or a secondary cell of the UE, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting that a status of the preconfigured measurement gap should be updated.

[0161] Example 9 may include the apparatus of example 7, wherein the activation or deactivation of the secondary cell is based on a medium access control (MAC) control element.

[0162] Example 10 may include the apparatus of Example 7, wherein the UE is not required to autonomously identify a status of the preconfigured measurement gap.

[0163] Example 11 may include the apparatus of Example 10, wherein the processing circuitry is further configured to: detect, based on an RRC instruction for adding, releasing, or changing a primary cell or a secondary cell, that the network has reconfigured and updated the preconfigured measurement gap status, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting that the network has reconfigured and updated the preconfigured measurement gap status.

[0164] Example 12 may include the apparatus of example 7, wherein the UE is required to autonomously identify a status of the preconfigured measurement gap.

[0165] Example 13 may include the apparatus of Example 12, wherein an RRC indication associated with the preconfigured measurement gap cannot be reconfigured and updated by the network along with a measurement target change.

[0166] A computer-readable storage medium of Example 14 includes instructions that cause a processing circuit of a user equipment device (UE) for activating and deactivating a preconfigured measurement gap in carrier aggregation to perform, upon execution of the instructions by the processing circuit, the following steps: detecting a preconfigured measurement gap configured by a network; detecting that the preconfigured measurement gap should be activated or deactivated; and activating or deactivating the preconfigured measurement gap based on detection that the preconfigured measurement gap should be activated or deactivated.

[0167] Example 15 may include the computer-readable medium of Example 14, wherein execution of the instructions further causes the processing circuit to detect addition or removal of a measurement object associated with the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detection of the addition or removal of the measurement object.

[0168] Example 16 may include the computer-readable medium of Example 15, wherein execution of the instructions further causes the processing circuit to detect a network-controlled activation or deactivation indication based on a radio resource control (RRC) measurement gap list from the network, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detection of the network-controlled activation or deactivation indication.

[0169] Example 17 may include the computer-readable medium of Example 15, wherein execution of the instructions further causes the processing circuit to autonomously identify a status of the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated is based on the autonomous identification of the status.

[0170] Example 18 may include the computer-readable medium of Example 14, wherein execution of the instructions further causes the processing circuit to detect activation or deactivation of a secondary cell, and detecting that the preconfigured measurement gap is activated or deactivated is based on detecting the activation or deactivation of the secondary cell.

[0171] Example 19 may include the apparatus of example 1, wherein the processing circuitry is further configured to detect addition or removal of a measurement object associated with the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting the addition or removal of the measurement object.

[0172] Example 20 may include an apparatus of a network device for activating and deactivating a preconfigured measurement gap in carrier aggregation for a user equipment device, the apparatus comprising a processing circuit coupled to a memory device that stores information associated with the preconfigured measurement gap, the processing circuit configured to: generate an activation or deactivation of the preconfigured measurement gap; and encode radio resource control (RRC) signaling for transmission to the user equipment device indicating the activation or deactivation of the preconfigured measurement gap.

[0173] Example 21 may include a method for activating and deactivating a pre-configured measurement gap in carrier aggregation, the method including: detecting, by a processing circuit of a user equipment device (UE), a pre-configured measurement gap configured by a network; detecting, by the processing circuit, that the pre-configured measurement gap should be activated or deactivated; and activating or deactivating, by the processing circuit, the pre-configured measurement gap based on detection that the pre-configured measurement gap should be activated or deactivated.

[0174] Example 22 may include the method of Example 21, further comprising detecting an addition or removal of a measurement object associated with the preconfigured measurement gap, and detecting that the preconfigured measurement gap should be activated or deactivated based on the detection of the addition or removal of the measurement object.

[0175] Example 23 may include the method of Example 22, further comprising detecting a network-controlled activation or deactivation indication based on a radio resource control (RRC) measurement gap list from the network, and detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting the network-controlled activation or deactivation indication.

[0176] Embodiments according to the present disclosure are disclosed in the appended claims, which are particularly directed to methods, storage media, devices, and computer program products, and any feature recited in one claim category, e.g., a method, may also be claimed in another claim category, e.g., a system. Dependencies or references in the appended claims have been selected for formality reasons only. However, any subject matter resulting from an intentional reference (e.g., multiple references) of any preceding claim may also be claimed. Thus, any combination of the claims and their features may be disclosed and claimed, regardless of the dependencies selected in the appended claims. Subject matter that may be claimed includes not only the combination of features recited in the appended claims, but also any other combination of features in the claims, and each feature recited in the claims may be combined with any other feature or combination of features in the claims. Furthermore, any of the embodiments and features described or depicted in this specification may be claimed in a separate claim and / or in any combination with any of the embodiments or features described or depicted in this specification or with any of the features of the appended claims.

[0177] 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 forms disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0178] Certain aspects of the disclosure have been described above with reference to block diagrams and flow diagrams of systems, methods, apparatus, and / or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, respectively, may be implemented by computer-executable program instructions. Similarly, some blocks of the block diagrams and flow diagrams may not necessarily be performed in the order presented, or may not necessarily be performed at all, according to some implementations.

[0179] These computer executable program instructions may be loaded onto a special purpose computer or other specific machine, processor, or other programmable data processing apparatus to produce a specific machine, whereby the instructions executing on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in one or more blocks of the flow diagram. These computer program instructions may be stored in a computer readable storage medium or memory that can instruct the computer or other programmable data processing apparatus to function in a particular manner, whereby the instructions stored in the computer readable medium produce an article of manufacture that includes instruction means for implementing one or more functions specified in one or more blocks of the flow diagram. As an example, certain implementations may provide a computer program product having a computer readable storage medium having computer readable program code or program instructions embodied therein, the computer readable program code adapted to be executed to implement one or more functions specified in one or more blocks of the flow diagram. Computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a sequence of operational elements or steps to be executed on the computer or other programmable apparatus to generate a computer-implemented process, such that the instructions executing on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in one or more blocks of the flow diagram.

[0180] Thus, the blocks in the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, can be implemented by a dedicated hardware-based computer system that performs the specified functions, elements, or steps, or combinations of dedicated hardware and computer instructions.

[0181] In particular, conditional language such as "can," "might," "could," or "potential," unless otherwise stated or understood otherwise within the context in which it is used, is intended to generally convey that certain implementations may include certain features, elements, and / or operations, while other implementations do not include those features, elements, and / or operations. Thus, such conditional language is not intended to generally imply that the features, elements, and / or operations are in any way required for one or more implementations, or that one or more implementations necessarily include logic for determining whether those features, elements, and / or operations are included or performed in any particular implementation, with or without user input or prompting.

[0182] Many modifications and other implementations of the disclosures set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. It is to be understood, therefore, that the disclosure is not to be limited to the particular implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0183] For purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0184] The term "circuitry" as used herein refers to, is a part of, or includes hardware components, such as electronic circuits, logic circuits, processors (shared, dedicated, or group) and / or memories (shared, dedicated, or group), application specific integrated circuits (ASICs), field programmable devices (FPDs) (e.g., field programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high performance PLDs (HCPLDs), constructed ASICs, or 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 to provide at least some of the described functionality. The term "circuitry" may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with program code used to perform the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

[0185] The term "processor circuitry" as used herein refers to, is a part of, or includes circuitry capable of sequentially and automatically performing a series 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 operating computer-executable instructions, such as program code, software modules, and / or functional processes. The processing circuitry may include more 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."

[0186] As used herein, the term "interface circuitry" refers to, is a part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and / or the like.

[0187] The term "user equipment" or "UE" as used herein refers to a device having wireless communication capabilities and may represent 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 client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio unit, reconfigurable radio unit, 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.

[0188] The term "network element" as used herein refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communications 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 others.

[0189] As used herein, the term "computer system" refers to any type of interconnected electronic device, computing 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 computing devices and / or multiple computing systems that are communicatively coupled to each other and configured to share computing and / or networking resources.

[0190] As used herein, the terms "appliance," "computer appliance," and the like refer to a computing device or system having program code (e.g., software or firmware) specifically designed to provide particular 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 particular computing resources.

[0191] The term "resources" as used herein refers to physical or virtual devices, components, and / or components within a particular device in a computing environment, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, etc. "Hardware resources" may refer to computational, storage, and / or network resources provided by a physical hardware element(s). "Virtualized resources" may refer to computational, storage, and / or network resources provided by a virtualization infrastructure to an application, device, system, etc. The term "network resources" or "communication resources" may refer to resources accessible by a computer device / system over a communication network. The term "system resources" may refer to any type of shared entity for providing services and may include computing and / or network resources. A system resource may be viewed as a set of coherent functions, network data objects, or services that reside on a single host or on multiple hosts and are accessible through a clearly identifiable server.

[0192] The term "channel" as used herein refers to any transmission medium, either 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 terminology indicating a path or medium over which data is communicated. Additionally, the term "link" as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

[0193] 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 occurrence of an object that may occur, for example, during the execution of program code.

[0194] The terms "coupled" and "communicatively coupled," along with their derivatives, are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by a means of communication, such as through a wire or other interconnection, through a wireless communication channel or link, or the like.

[0195] 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.

[0196] Unless used differently herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0 (2019-06) and / or any other 3GPP standards. For purposes of this document, the following abbreviations (shown in Table 9) may apply to the embodiments and embodiments discussed herein.

[0197] Table 9: Abbreviations 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 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 stratum 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 ECSP Edge Computing Service Provider Edge Computing Service Provider EDN Edge Data Network 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 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 management, 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 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

Claims

1. 16. An apparatus for a user equipment device (UE) device for activating and deactivating pre-configured measurement gaps in carrier aggregation, the apparatus comprising: A processing circuit coupled to a memory device that stores information associated with the preconfigured measurement gaps, the processing circuit comprising: Detecting a preconfigured measurement gap configured by the network; Detecting that the preconfigured measurement gap should be activated or deactivated; configured to activate or deactivate the preconfigured measurement gap based on detection that the preconfigured measurement gap should be activated or deactivated. Device.

2. The processing circuitry: further configured to detect addition or removal of a measurement object associated with the preconfigured measurement gap; detecting that the preconfigured measurement gap should be activated or deactivated is based on the detection of the addition or removal of the measurement object.

2. The apparatus of claim 1.

3. The processing circuitry: and further configured to detect a network-controlled activation or deactivation indication based on a Radio Resource Control (RRC) measurement gap list from the network; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting the network-controlled activation or deactivation indication.

3. The apparatus of claim 2.

4. The apparatus of claim 3 , wherein the RRC measurement gap list includes an indication of a measurement target change.

5. The apparatus of claim 3 , wherein the RRC measurement gap list cannot be reconfigured and updated by the network with measurement target changes.

6. The processing circuitry: and further configured to autonomously identify a status of the preconfigured measurement gap. detecting that the preconfigured measurement gap should be activated or deactivated is based on an autonomous identification of the status.

3. The apparatus of claim 2.

7. The processing circuitry: further configured to detect activation or deactivation of the secondary cell; detecting that the preconfigured measurement gap should be activated or deactivated based on detecting activation or deactivation of the secondary cell.

2. The apparatus of claim 1.

8. The processing circuitry: and detecting that a status of the preconfigured measurement gap should be updated based on whether a frequency layer to be measured is included by a bandwidth portion activated by a primary cell or a secondary cell of the UE; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting that a status of the preconfigured measurement gap should be updated.

8. The apparatus of claim 7.

9. The apparatus of claim 7 , wherein the activation or deactivation of the secondary cell is based on a Medium Access Control (MAC) control element.

10. The apparatus of claim 7 , wherein the UE is not required to autonomously identify a status of the preconfigured measurement gap.

11. The processing circuitry: and detecting that the network has reconfigured and updated the preconfigured measurement gap status based on an RRC instruction for adding, releasing, or changing a primary or secondary cell; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting that the network has reconfigured and updated the preconfigured measurement gap status.

11. The apparatus of claim 10.

12. The apparatus of claim 7 , wherein the UE is required to autonomously identify a status of the preconfigured measurement gap.

13. The apparatus of claim 12 , wherein an RRC indication associated with the preconfigured measurement gap cannot be reconfigured and updated by the network with measurement target changes.

14. 1. A computer-readable storage medium having instructions having instructions for causing a processing circuit of a user equipment device (UE) for activating and deactivating pre-configured measurement gaps in carrier aggregation, the instructions, upon execution by the processing circuit, to: detecting a preconfigured measurement gap configured by the network; detecting that the preconfigured measurement gap should be activated or deactivated; and activating or deactivating the preconfigured measurement gap based on detection that the preconfigured measurement gap should be activated or deactivated. Computer-readable medium.

15. Execution of the instructions further causes the processing circuitry to: detecting an addition or removal of a measurement object associated with the preconfigured measurement gap; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting an addition or removal of the measurement object.

15. The computer-readable medium of claim 14.

16. Execution of the instructions further causes the processing circuitry to: Detecting a network-controlled activation or deactivation indication based on a Radio Resource Control (RRC) measurement gap list from the network; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting an indication of the network-controlled activation or deactivation.

16. The computer readable medium of claim 15.

17. Execution of the instructions further causes the processing circuitry to: autonomously identifying a status of the preconfigured measurement gap; detecting that the preconfigured measurement gap should be activated or deactivated is based on an autonomous identification of the status.

16. The computer readable medium of claim 15.

18. Execution of the instructions further causes the processing circuitry to: Detecting activation or deactivation of a secondary cell; detecting that the preconfigured measurement gap is activated or deactivated based on detecting activation or deactivation of the secondary cell.

15. The computer-readable medium of claim 14.

19. The processing circuitry: further configured to detect addition or removal of a measurement object associated with the preconfigured measurement gap; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting an addition or removal of the measurement object.

2. The apparatus of claim 1.

20. An apparatus for a network device for activating and deactivating a pre-configured measurement gap in carrier aggregation for a user equipment device, the apparatus comprising: a processing circuit coupled to a memory device that stores information associated with the pre-configured measurement gap, the processing circuit comprising: Generate an activation or deactivation of a preconfigured measurement gap; and configured to encode, for transmission to the user equipment device, radio resource control (RRC) signaling indicating activation or deactivation of the preconfigured measurement gap. Device.

21. 1. A method for activating and deactivating pre-configured measurement gaps in carrier aggregation, the method comprising: detecting, by a processing circuit of a user equipment device (UE), a preconfigured measurement gap configured by the network; detecting, by the processing circuitry, that the preconfigured measurement gap should be activated or deactivated; and activating or deactivating the preconfigured measurement gap based on detection, by the processing circuitry, that the preconfigured measurement gap should be activated or deactivated. method.

22. detecting an addition or removal of a measurement object associated with the preconfigured measurement gap; detecting that the preconfigured measurement gap should be activated or deactivated is based on the detection of the addition or removal of the measurement object.

22. The method of claim 21.

23. detecting a network-controlled activation or deactivation indication based on a Radio Resource Control (RRC) measurement gap list from the network; detecting that the preconfigured measurement gap should be activated or deactivated is based on detecting an indication of the network-controlled activation or deactivation.

22. The method of claim 21.

24. A computer readable storage medium having instructions for carrying out the method of any one of claims 21 to 23.

25. Apparatus configured to carry out the method of any one of claims 21 to 23.

Citation Information

Patent Citations

  • Method and Devices for a Communication System

    US20120263054A1

  • Methods of Sending Feedback Signaling Under Carrier Specific Measurement Gaps in Multi-Carrier

    US20150124728A1