Measurement reporting for secondary cell activation

Abstract

Methods, systems, and computer readable media are disclosed for performing operations including: receiving an instruction to activate a secondary cell (SCell) from a wireless cellular network; transmitting a layer 3 (L3) measurement report to the wireless cellular network in a physical uplink shared channel (PUSCH) message; and performing the shortened SCell activation process.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 449,905, filed March 3, 2023, the entire contents of which are incorporated herein by reference. Background Technology

[0003] Wireless communication networks provide an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephone, data (e.g., voice, audio, and / or video data), messaging, internet access, and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user equipment using wireless network protocols, such as those described in various telecommunications standards issued by the 3rd Generation Partnership Project (3GPP). Example wireless communication networks include Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal Frequency Division Multiple Access (OFDMA) networks, Long Term Evolution (LTE), and 5G New Radio (5G NR). Wireless communication networks use technologies such as OFDM, Multiple-Input Multiple-Output (MIMO), Advanced Channel Decoding, Massive MIMO, beamforming, and / or other features to facilitate mobile broadband services.

[0004] In its technical specifications, 3GPP defines two frequency ranges for wireless communication: a sub-6 GHz range (e.g., 450 MHz to 6000 MHz), also known as Frequency Range 1 (FR1); and a millimeter wave range (24250 MHz to 52600 MHz), also known as FR2. 3GPP introduced millimeter waves in 5G New Radio (NR) to expand the frequency resources available for wireless communication. Summary of the Invention

[0005] This disclosure describes a solution for avoiding redundant measurements and unnecessary delays during the FR2 secondary cell (SCell) activation process. One aspect of the subject matter described in this specification can be embodied in a method involving: receiving an instruction to activate a secondary cell (SCell) from a radio cellular network; transmitting a Layer 3 (L3) measurement report to the radio cellular network in a Physical Uplink Shared Channel (PUSCH) message; and performing a shortened SCell activation process.

[0006] The previously described embodiments can be implemented using: a method; a non-transitory computer-readable medium storing computer-readable instructions for performing the method; one or more processors of a user equipment (UE) configured to perform the method; a UE including processing circuitry configured to perform the method; and a computer memory interoperably coupled to a hardware processor configured to perform the method or the instructions stored on the non-transitory computer-readable medium. These and other embodiments can optionally include one or more of the following features.

[0007] In some implementations, PUSCH messages are sent using dynamic uplink grant.

[0008] In some implementations, the method also involves transmitting a scheduling request (SR) to the wireless cellular network in response to receiving an instruction to activate the SCell, including an SCell activation tag and a request for dynamic uplink authorization.

[0009] In some implementations, the method also involves determining that a dynamic uplink grant is received from the wireless cellular network within a predetermined period of time from the transmission of the SR; and responsively determining to use the dynamic uplink grant to send a PUSCH message.

[0010] In some implementations, PUSCH messages are sent using the selected uplink grant from among multiple periodic uplink grants.

[0011] In some specific implementations, the selected uplink grant is the first uplink grant that occurs after receiving the instruction to activate SCell among the multiple periodic uplink grants.

[0012] In some specific implementations, the selected uplink grant is any uplink grant that occurs within a predetermined time after receiving the instruction to activate the SCell from among the multiple periodic uplink grants.

[0013] In some specific implementations, the selected uplink grant is the first uplink grant that occurs within a predetermined time after receiving the instruction to activate SCell from among the multiple periodic uplink grants.

[0014] In some implementations, the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as the first step.

[0015] Another aspect of the subject matter described in this specification can be embodied in a method that involves: sending a command to a user equipment (UE) to activate a secondary cell (SCell); receiving a Layer 3 (L3) measurement report from the UE in a Physical Uplink Shared Channel (PUSCH) message; and determining, in response to receiving the L3 measurement report, that the UE is performing a shortened SCell activation procedure.

[0016] The previously described embodiments can be implemented using: a method; a non-transitory computer-readable medium storing computer-readable instructions for performing the method; one or more processors configured to perform the method; a base station including one or more processors configured to cause the base station to perform the method; and a computer memory interoperably coupled to a hardware processor configured to perform the method or the instructions stored on the non-transitory computer-readable medium. These and other embodiments can optionally include one or more of the following features.

[0017] In some specific implementations, the method also involves waiting for a predetermined period of time after transmitting an instruction to receive a scheduling request (SR) from the UE.

[0018] In some specific implementations, the method also involves an enhanced SR that receives requests for SCell activation tags and dynamic uplink authorization during a predetermined time period.

[0019] In some specific implementations, the predetermined time period is the first predetermined time period, and the method also involves transmitting dynamic uplink grants to the UE during a second predetermined time period.

[0020] In some specific implementations, this method also involves assigning higher priority to enhanced SRs than to traditional SRs.

[0021] In some implementations, the PUSCH message is received within one of several periodic uplink grants.

[0022] In some specific implementations, receiving L3 measurement reports in a PUSCH message involves checking L3 measurement reports within a subset of multiple periodic uplink grants received during a predetermined period after sending the instruction to activate the SCell.

[0023] In some implementations, the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as the first step.

[0024] Details of one or more embodiments of these systems and methods are set forth in the following figures and description. Other features, objects, and advantages of these systems and methods will be apparent from the specification, figures, and claims. Attached Figure Description

[0025] Figure 1 The SCell activation process is illustrated.

[0026] Figure 2 An example of a shortened SCell activation process based on some specific implementations is shown.

[0027] Figure 3 Examples of wireless networks based on some specific implementations are shown.

[0028] Figure 4 The flowchart illustrates example methods based on some specific implementations.

[0029] Figure 5 A flowchart illustrating another example method based on some specific implementations is shown.

[0030] Figure 6 Examples of UEs based on some specific implementations are shown.

[0031] Figure 7 Examples of access nodes based on some specific implementations are shown. Detailed Implementation

[0032] To increase network capacity and data rates, wireless communication networks utilize carrier aggregation, where multiple serving cells are aggregated together to serve a UE. When a wireless communication network uses carrier aggregation, the network configures the UE with a primary cell (PCell) and one or more secondary cells (SCells) (e.g., via Radio Resource Control (RRC) signaling). Once configured, the wireless communication network can dynamically activate or deactivate SCells, possibly using lower-layer signaling such as Media Access Control (MAC) Control Element (CE) commands, in response to changes in network traffic, UE movement, or various other reasons. A SCell can be an FR1 SCell operating on FR1 or an FR2 SCell operating on FR2. Each SCell type can have a different activation procedure. Figure 1 The example illustrates the FR2 SCell activation process introduced in 5G NR.

[0033] Figure 1 An example of activation procedure 100 for activating FR2 SCell is shown. For example... Figure 1As shown, the UE initially receives a SCell activation command from the network (e.g., from a base station). In this example, the SCell activation command is a MAC CE command that specifies the SCell to be activated (also known as the target SCell). Upon receiving the SCell activation command, the UE, during the time period (T... HARQ During this period, the command is acknowledged to the network via Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK). Period T HARQ The duration is defined by the standard (i.e., pre-configured in the UE) or configured by the network. The UE decodes the SCell activation command and initiates the SCell activation operation, which includes: cell synchronization, cell measurement and time / frequency (T / F) tracking, Layer 1 Reference Signal Received Power (L1-RSRP) measurement or beam measurement (BM), L1-RSRP reporting, Transmission Configuration Indicator (TCI) activation for Channel State Information (CSI) reporting and Semi-Persistent Reference Signal (SP-RS) activation, and CSI measurement and reporting.

[0034] Recently, to improve efficiency and ensure consistent operation across various devices, 3GPP has standardized the operations (and resulting delays) performed by the UE and network during SCell activation in various scenarios. In some cases, the operations associated with SCell activation may depend in part on whether the SCell is known to the UE. Specifically, if the SCell is known to the UE, the UE and network can skip certain operations during SCell activation (e.g., cell synchronization, cell measurement and T / F tracking, L1-RSRP measurement or beam measurement, and L1-RSRP reporting), which reduces SCell activation delay. The shortened SCell activation operation... Figure 2 As shown in the image.

[0035] Figure 2 An example of a shortened SCell activation process 200 according to some specific implementations is shown. For example... Figure 2 As shown, compared to the complete SCell activation process 100, cell synchronization, cell measurement and T / F tracking, L1-RSRP measurement or beam measurement, and L1-RSRP reporting are skipped.

[0036] As described in 3GPP TS 38.133 Release 17, Part 8.3.2, for an FR2 SCell to qualify as a known SCell for the UE, the UE must have already transmitted a valid Layer 3 (L3) measurement report (e.g., an RSRP report) before receiving the SCell activation command. Otherwise, the SCell is considered unknown to the UE. However, classifying SCells as known or unknown in this way can lead to inefficiency and redundant measurements. For example, if the UE has measured a SCell but has not yet reported the measurement to the network, the SCell will be considered unknown to the UE. Therefore, when activating the UE, the UE will need to revert to the unknown process (i.e., the full SCell activation process 100), resulting in repeated measurements and longer SCell activation times.

[0037] This disclosure describes solutions for avoiding duplicate measurements and unnecessary delays during the FR2 SCell activation process. In some implementations, the UE is configured to use a shortened SCell activation process instead of the full SCell activation process, provided that the UE can transmit an L3 measurement report to the network after the activation command and before the end of the activation process. The UE can transmit the L3 measurement report using either dynamic uplink (UL) granting or periodic UL granting on the Physical Uplink Shared Channel (PUSCH). In the former case, the UE transmits a scheduling request (SR) to the network to request PUSCH granting, but this is not required in the latter case. This disclosure also describes details of the L3 measurement reporting in both dynamic UL granting and periodic UL granting scenarios.

[0038] Figure 3 A wireless network 300 according to some specific implementation is illustrated. The wireless network 300 includes a UE 302 and a base station 304 connected via one or more channels 306A, 306B across an air interface 308. The UE 302 and the base station 304 communicate using a system that supports control for managing the UE 302's access to the network via the base station 304.

[0039] In some implementations, the wireless network 300 may be a standalone (SA) network incorporating a fifth-generation (5G) new radio (NR) communication standard as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. In other implementations, the wireless network 300 may be a non-standalone (NSA) network incorporating both Long Term Evolution (LTE) and 5G NR communication standards. For example, the wireless network 300 may be an E-UTRA (Evolved Universal Terrestrial Radio Access)-NR Dual Connectivity (EN-DC) network or an NR-EUTRA Dual Connectivity (NE-DC) network. Other types of communication standards are possible, including future 3GPP systems (e.g., sixth-generation (6G) systems), IEEE 802.11 technology, and so on. While this document may use terminology generally associated with 5G NR to describe aspects, the aspects of this disclosure may be applied to other systems, such as 4G and / or systems beyond 5G (e.g., 6G).

[0040] In wireless network 300, UE 302 and any other UE in the system can be, for example, a laptop computer, smartphone, tablet computer, machine-type device such as a smart meter or dedicated device for healthcare, intelligent transportation system, or any other wireless device with or without a user interface. In network 300, base station 304 provides UE 302 with network connectivity to a wider network (not shown). This UE 302 connectivity is provided via air interface 308 within the base station service area provided by base station 304. In some implementations, this wider network can be a wide area network operated by a cellular network provider, or it can be the Internet. Each base station service area associated with base station 304 is supported by antennas integrated with base station 304. The service area is divided into multiple sectors associated with certain antennas. Such sectors may be physically associated with fixed antennas or may be assigned to physical areas with tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a particular sector.

[0041] UE 302 includes control circuitry 310 coupled to transmitting circuitry 312 and receiving circuitry 314. Transmitting circuitry 312 and receiving circuitry 314 may each be coupled to one or more antennas. Control circuitry 310 may include various combinations of dedicated circuitry and baseband circuitry. Transmitting circuitry 312 and receiving circuitry 314 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry or front-end module (FEM) circuitry.

[0042] In various specific implementations, aspects of the transmitting circuit 312, the receiving circuit 314, and the control circuit 310 may be integrated in various ways to achieve the operations described herein. The control circuit 310 may be adapted or configured to perform various operations, such as the UE-related operations described elsewhere in this disclosure.

[0043] Additionally, the transmitting circuit 312 can transmit multiple multiplexed uplink physical channels. These multiple uplink physical channels can be multiplexed according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. The transmitting circuit 312 can be configured to receive block data from the control circuit 310 and transmit it across the air interface 308.

[0044] Additionally, receiving circuitry 314 can receive multiple multiplexed downlink physical channels from air interface 308 and relay these physical channels to control circuitry 310. These multiple downlink physical channels can be multiplexed according to TDM or FDM and carrier aggregation. Transmitting circuitry 312 and receiving circuitry 314 can transmit and receive both structured control data and content data (e.g., messages, images, video, etc.) within data blocks carried by the physical channels.

[0045] Figure 3 Base station 304 is also illustrated. In specific implementations, base station 304 may be an NG radio access network (RAN) or 5G RAN, E-UTRAN, non-terrestrial cell, or traditional RAN (such as UTRAN). As used herein, the term "NG RAN" etc. may refer to base station 304 operating in an NR or 5G wireless network 300, and the term "E-UTRAN" etc. may refer to base station 304 operating in an LTE or 4G wireless network 300. UE 302 utilizes connections (or channels) 306A, 306B, each connection including a physical communication interface or layer.

[0046] The base station 304 circuitry may include control circuitry 316 coupled to transmitting circuitry 318 and receiving circuitry 320. Transmitting circuitry 318 and receiving circuitry 320 may each be coupled to one or more antennas, which may be used for communication via air interface 308. Transmitting circuitry 318 and receiving circuitry 320 may be adapted to transmit and receive data to and from any UE connected to base station 304, respectively. Transmitting circuitry 318 may transmit a downlink physical channel comprising multiple downlink subframes. Receiving circuitry 320 may receive multiple uplink physical channels from various UEs, including UE 302.

[0047] exist Figure 3In this document, one or more channels 306A and 306B are exemplified as air interfaces for communication coupling and may conform to cellular communication protocols such as 3GPP LTE, LTE-A, LTE-U (LTE-U), 5G, NR, NR-U, and / or any other communication protocols discussed herein. In a specific implementation, UE 302 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as the sidelink (SL) interface and may include one or more logical channels, including but not limited to the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0048] In some specific implementations, the wireless network 300 configures UE 302 to use a secondary cell (SCell). In one example, the wireless network 300 configures UE 302 to use carrier aggregation with the primary cell (PCell) and one or more SCells. The SCell can be an FR1 SCell operating on FR1 or an FR2 SCell operating on FR2. Following the above discussion, the activation process for an FR2 SCell depends on whether the SCell is unknown or known to the UE. Also as mentioned above, the complete SCell activation process (such as...) Figure 1 (As shown) is used for unknown SCells, while the shortened SCell activation process (such as...) Figure 2 (As shown) is used for the known SCell.

[0049] In some implementations, UE 302 is configured to use a shortened SCell activation procedure if the UE can transmit an L3 measurement report to the radio network 300 after the SCell activation command and before the activation procedure ends. In some implementations, UE 302 uses either Dynamic UL Grant on PUSCH (DG-PUSCH) or Configured (Periodic) UL Grant on PUSCH (CG-PUSCH) to transmit the L3 measurement report. In some examples, UE 302 is pre-configured to use either DG-PUSCH or CG-PUSCH to communicate the L3 measurement report. In other examples, the radio network 300 configures UE 302 to use either DG-PUSCH or CG-PUSCH to communicate the L3 measurement report.

[0050] In a specific implementation of UE 302 using dynamic UL granting, the UE is configured to send a scheduling request (SR) to the radio network 300 to request PUSCH granting, which allocates resources (e.g., time / frequency resources) for transmitting L3 measurement reports. UE 302 then transmits the L3 measurement reports to the radio network 300 on the resources allocated by the received dynamic UL granting.

[0051] In some implementations, UE 302 is configured to use an enhanced SR to request PUSCH authorization. In these implementations, if UE 302 does not have valid L3 measurement results to report for a SCell, the UE does not transmit the enhanced SR to the radio network 300. Conversely, if UE 302 has valid L3 measurement results to report for a SCell, the UE is configured to transmit the enhanced SR to the radio network 300 to request PUSCH authorization for reporting the L3 measurement results. The enhanced SR includes a SCell activation tag that indicates to the radio network 300 that the SR is requesting resources for reporting L3 measurements for FR2 SCell activation. Once the radio network 300 receives the enhanced SR, the network will respond by processing the enhanced SR with a higher priority than a conventional SR. It should be noted that UE 302 can also use a conventional SR to request PUSCH authorization for L3 measurement reporting. However, the conventional SR does not include an indication that the SR is requesting resources for reporting L3 measurements for FR2 SCell activation.

[0052] In some specific implementations, during the SCell activation process, the wireless network 300 is configured to wait for a predetermined time period T1 from the UE 302 for a SR (which can be a traditional SR or an enhanced SR). After the wireless network 300 transmits an SCell activation command for the target SCell to the UE 302, a timer T1 controlled by the wireless network 300 starts. If the UE 302 does not have a valid L3 measurement result to report for the target SCell, the UE will not transmit the SR to the wireless network 300. However, the UE 302 can still transmit a traditional SR for some other purpose, such as UL traffic on a PCell or primary / secondary cell (PSCell). If the wireless network 300 does not receive an SR from the UE 302 within T1, the network assumes the SCell is unknown to the UE and uses the full SCell activation process. Conversely, if the wireless network 300 receives an SR from the UE 302 within T1, the network assumes the SCell is known to the UE and uses a shortened SCell activation process.

[0053] In some implementations, after the wireless network 300 receives the enhanced SR (e.g., within T1), the network is configured to transmit the requested UL authorization to the UE 302 within a predetermined time period T2, which begins after the UE transmits the SR to the wireless network 302. Specifically, the UE 302 starts a timer set to T2 after transmitting the SR to the wireless network 300. If the UE 302 does not receive the UL authorization before the timer expires, the UE assumes that the wireless network 300 does not expect the UE to accelerate the SCell activation process. Therefore, the UE 302 performs the complete SCell activation process.

[0054] As previously described, UE 302 may transmit a conventional SR to radio network 300 for some other purpose (i.e., not for L3 measurement reporting). In this scenario, radio network 300 may not be able to distinguish whether the SR is for L3 measurement reporting or for other purposes. However, radio network 300 provides UL authorization to UE 302. In one scenario, UE 302 determines that it will not use the UL authorization for L3 measurement reporting, but for other purposes (e.g., UL traffic). In this scenario, to avoid further delays from waiting for the L3 measurement report that will not be transmitted from UE 302, radio network 300 is configured to check the L3 measurement report only on the UL authorization received from UE 302 within a predetermined time period T3, where the timer set to T3 starts after the network provides the UL authorization to the UE. If radio network 300 does not receive an L3 measurement report from UE 302 before timer T3 expires, the network assumes that the SCell is unknown to the UE and uses the full SCell activation procedure.

[0055] As previously described, UE 302 may optionally send L3 measurement reports on periodic UL grants (CG-PUSCH). In these scenarios, UE 302 does not need to send an SR to the network to request PUSCH grants. Instead, the radio network 300 pre-configures periodic PUSCH UL grants to UE 302, and the UE can use these UL grants for UL services and / or for L3 measurement reports.

[0056] In some implementations, the wireless network 300 is configured to check UL authorization within a predetermined time period T4, beginning after the network transmits the SCell activation command. If the wireless network 300 does not receive an L3 measurement report from the UE 302 within T4, the network assumes the SCell is unknown to the UE and uses the complete SCell activation procedure. It should be noted that if the UE 302 has no valid L3 measurement results to report, the UE will ignore those UL authorizations used for L3 measurement reporting. However, if the UE 302 has services, the UE can still use those UL authorizations to transmit services.

[0057] In some implementations, UE 302 is configured to report L3 measurements regarding periodic UL grants using one or more of the following options. In the first option, UE 302 is configured to report L3 measurements regarding the most recent UL grant after the SCell activation command. In the second option, UE 302 is configured to report L3 measurements for any UL grant within a predetermined time period T5 after receiving the SCell activation command. In the third option, UE 302 is configured to report L3 measurements regarding the most recent UL grant after the SCell activation command plus a time period X. In one example, X = T. HARQ +3 milliseconds (ms). Therefore, in some examples, the wireless network 300 starts from when it transmits the activation command or from n+Tharq+3ms T4 (where n is the time slot when it transmits the activation command, T...). HARQ This refers to the PHY parsing time, and the 3ms refers to the MAC layer processing time.

[0058] Figure 4 A flowchart illustrating an example method 400 according to some specific implementation is provided. For clarity, the following description generally describes method 400 within the context of the other figures in this specification. For example, method 400 may be derived from... Figure 3 The method is executed by UE 302. It should be understood that method 400 may be executed, for example, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware. In some specific implementations, the various steps of method 400 may be run in parallel, in combination, in cycles, or in any order.

[0059] At 402, method 400 relates to receiving an instruction to activate a secondary cell (SCell) from a wireless cellular network.

[0060] At 404, method 400 relates to transmitting a Layer 3 (L3) measurement report to a wireless cellular network in a Physical Uplink Shared Channel (PUSCH) message.

[0061] At 406, method 400 involves performing a shortened SCell activation procedure.

[0062] In some implementations, PUSCH messages are sent using dynamic uplink grant.

[0063] In some implementations, the method also involves transmitting a scheduling request (SR) to the wireless cellular network in response to receiving an instruction to activate the SCell, including an SCell activation tag and a request for dynamic uplink authorization.

[0064] In some implementations, the method also involves determining that a dynamic uplink grant is received from the wireless cellular network within a predetermined period of time from the transmission of the SR; and responsively determining to use the dynamic uplink grant to send a PUSCH message.

[0065] In some implementations, PUSCH messages are sent using the selected uplink grant from among multiple periodic uplink grants.

[0066] In some specific implementations, the selected uplink grant is the first uplink grant that occurs after receiving the instruction to activate SCell among the multiple periodic uplink grants.

[0067] In some specific implementations, the selected uplink grant is any uplink grant that occurs within a predetermined time after receiving the instruction to activate the SCell from among the multiple periodic uplink grants.

[0068] In some specific implementations, the selected uplink grant is the first uplink grant that occurs within a predetermined time after receiving the instruction to activate SCell from among the multiple periodic uplink grants.

[0069] In some implementations, the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as the first step.

[0070] Figure 5 A flowchart illustrating an example method 500 according to some specific implementation is provided. For clarity, the following description generally describes method 500 within the context of the other figures in this specification. For example, method 500 may be derived from... Figure 3 The method is executed by base station 304. It should be understood that method 500 can be executed, for example, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware. In some specific implementations, the various steps of method 400 can be run in parallel, in combination, in cycles, or in any order.

[0071] At 502, method 500 includes sending an instruction to the user equipment (UE) to activate the secondary cell (SCell).

[0072] At 504, method 500 relates to receiving layer 3 (L3) measurement reports from the UE in a Physical Uplink Shared Channel (PUSCH) message.

[0073] At 506, method 500 relates to determining, in response to receiving an L3 measurement report, that the UE is performing a shortened SCell activation procedure.

[0074] In some specific implementations, the method also involves waiting for a predetermined period of time after transmitting an instruction to receive a scheduling request (SR) from the UE.

[0075] In some specific implementations, the method also involves an enhanced SR that receives requests for SCell activation tags and dynamic uplink authorization during a predetermined time period.

[0076] In some specific implementations, the predetermined time period is the first predetermined time period, and the method also involves transmitting dynamic uplink grants to the UE during a second predetermined time period.

[0077] In some specific implementations, this method also involves assigning higher priority to enhanced SRs than to traditional SRs.

[0078] In some implementations, the PUSCH message is received within one of several periodic uplink grants.

[0079] In some specific implementations, receiving L3 measurement reports in a PUSCH message involves checking L3 measurement reports within a subset of multiple periodic uplink grants received during a predetermined period after sending the instruction to activate the SCell.

[0080] In some implementations, the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as the first step.

[0081] Figure 6 An example of UE 600 according to some specific implementations is shown. UE 600 may be similar to Figure 3 The UE 302 is essentially interchangeable with it.

[0082] UE 600 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, pressure sensors, thermometers, motion sensors, accelerometers, stock sensors, voltmeters / ammeters, etc.), video devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0083] UE 600 may include a processor 602, RF interface circuitry 604, memory / storage device 606, user interface 608, sensor 610, drive circuitry 612, power management integrated circuit (PMIC) 614, antenna structure 616, and battery 618. The components of UE 600 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 6The block diagram is intended to show a high-level view of some of the components in the UE 600. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0084] The components of UE 600 can be coupled to various other components via one or more interconnects 620, which can represent any type of interface, input / output, bus (local, system, or extended), transmit line, trace, optical connector, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0085] Processor 602 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 622A, central processing unit circuitry (CPU) 622B, and graphics processing unit circuitry (GPU) 622C. Processor 602 may include one or more processors and any type of circuitry or processor circuitry that execute or otherwise operate computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 606) to cause UE 600 to perform the operations described herein. In some specific embodiments, processor 602 (e.g., using baseband processor circuitry 622A) is configured to perform operations including: interacting with RF interface circuitry 604 to receive instructions to activate a secondary cell (SCell) from a wireless cellular network; transmitting a Layer 3 (L3) measurement report in a Physical Uplink Shared Channel (PUSCH) message via RF interface circuitry 604; and performing a shortened SCell activation process.

[0086] In some implementations, the baseband processor circuit 622A can access the communication protocol stack 624 in the memory / storage device 606 to communicate over a 3GPP-compatible network. Generally, the baseband processor circuit 622A can access the communication protocol stack to perform user plane functions at the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Serving Data Adaptation Protocol (SDAP) layer, and PDU layer; and to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC layer, and non-access strata. In some implementations, PHY layer operations may additionally / optionally be performed by components of the RF interface circuit 604. The baseband processor circuit 622A can generate or process baseband signals or waveforms carrying information in a 3GPP-compatible network. In some specific implementations, the waveform used for NR can be based on Cyclic Prefix Orthogonal Frequency Division Multiplexing (OFDM) "CP-OFDM" in the uplink or downlink, and Discrete Fourier Transform Extended OFDM "DFT-S-OFDM" in the uplink.

[0087] Memory / storage device 606 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 624) that can be executed by one or more processors in processor 602 to cause UE 600 to perform the various operations described herein. Memory / storage device 606 includes any type of volatile or non-volatile memory that can be distributed throughout UE 600. In some specific embodiments, some memory / storage devices in memory / storage device 606 may be located on processor 602 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 606 may be located external to processor 602 but accessible via a memory interface. Memory / storage device 606 may include any suitable volatile or non-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 memory, or any other type of memory device technology.

[0088] RF interface circuitry 604 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 600 to communicate with other devices via a radio access network. RF interface circuitry 604 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0089] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 616, and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal, which is then provided to the baseband processor of processor 602.

[0090] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can amplify the RF signal via a power amplifier before it is radiated across the air interface via antenna 616. In various specific implementations, the RF interface circuitry 604 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0091] Antenna 616 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 616 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output (MIMO) communication. Antenna 616 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 616 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0092] User interface 608 includes various input / output (I / O) devices designed to enable a user to interact with UE 600. User interface 608 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a head-mounted device. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes "LEDs" and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays "LCDs," LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced through the operation of UE 600.

[0093] Sensor 610 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; temperature sensors (e.g., thermistors); pressure sensors; image capture devices (e.g., cameras or lensless apertures); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0094] The driving circuitry 612 may include software and hardware elements that operate to control specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 600. The driving circuitry 612 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 600. For example, the driving circuitry 612 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for obtaining sensor readings from sensor circuitry 610 and controlling and allowing access to sensor circuitry 610; a driver for obtaining actuator positioning of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0095] The PMIC 614 manages the power supplied to various components of the UE 600. Specifically, relative to the processor 602, the PMIC 614 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0096] In some implementations, the PMIC 614 can control various power-saving mechanisms of the UE 600, or otherwise become part of these power-saving mechanisms. The battery 618 can power the UE 600, but in some examples, the UE 600 may be installed in a fixed location and may have a power source coupled to the power grid. The battery 618 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in vehicle-based applications, the battery 618 can be a typical lead-acid automotive battery.

[0097] Figure 7 An access node 700 (e.g., a base station or gNB) according to some specific implementation is illustrated. The access node 700 may be similar to and substantially interchangeable with the base station 304. The access node 700 may include a processor 702, RF interface circuitry 704, core network (CN) interface circuitry 706, memory / storage device circuitry 708, and antenna structure 710.

[0098] The components of access node 700 can be coupled to various other components via one or more interconnects 712. The processor 702, RF interface circuitry 704, memory / storage device circuitry 708 (including a communication protocol stack 714), antenna structure 710, and interconnects 712 can be similar to those in reference [reference needed]. Figure 6Similar named elements are shown and described. For example, processor 702 may include processor circuitry such as, for example, baseband processor circuitry (BB) 716A, central processing unit circuitry (CPU) 716B, and graphics processing unit circuitry (GPU) 716C. Processor 702 may include one or more processors and any type of circuitry or processor circuitry that execute or otherwise operate computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 708) to cause access node 700 to perform the operations as described herein. In some specific embodiments, processor 702 is configured to perform operations including: interfacing instructions for activating a secondary cell (SCell) with user equipment (UE) via RF interface circuitry 704; receiving a Layer 3 (L3) measurement report from the UE via RF interface circuitry 704 in a Physical Uplink Shared Channel (PUSCH) message; and determining, in response to receiving the L3 measurement report, that the UE is performing a shortened SCell activation procedure.

[0099] The CN interface circuit 706 can provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as Carrier Ethernet or some other suitable protocol). Network connectivity can be provided to / from access node 700 via fiber optic or wireless backhaul. The CN interface circuit 706 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 706 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0100] As used herein, the terms "access node," "access point," etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes can be referred to as BS, gNB, RAN node, eNB, Node B, RSU, TRxP, or TRP, etc., and can include ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node," etc., can refer to an access node 700 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node," etc., can refer to an access node 700 (e.g., an eNB) operating in an LTE or 4G system. Depending on various specific implementations, the access node 700 can be implemented as one or more of the following: dedicated physical equipment such as a macrocell base station, and / or a low-power (LP) base station for providing a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell, such as a femtocell, picocell, or other similar cell.

[0101] In some specific implementations, all or part of the access node 700 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In a V2X scenario, the access node 700 may be a "roadside unit" or act as a "roadside unit". The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. An RSU may be implemented or be implemented by a suitable RAN node or a UE that is camped (or relatively camped), wherein an RSU implemented or be implemented by a UE may be referred to as a "UE-type RSU", an RSU implemented or be implemented by an eNB may be referred to as an "eNB-type RSU", an RSU implemented or be implemented by a gNB may be referred to as a "gNB-type RSU", and so on.

[0102] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0103] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples in the Examples section below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more examples in the Examples section below.

[0104] Example

[0105] Example 1 is a method comprising: receiving an instruction to activate a secondary cell (SCell) from a wireless cellular network; transmitting a Layer 3 (L3) measurement report to the wireless cellular network in a Physical Uplink Shared Channel (PUSCH) message; and performing a shortened SCell activation process.

[0106] Example 2 is based on the method described in Example 1, wherein the PUSCH message is sent using dynamic uplink grant.

[0107] Example 3 is the method according to Example 1, the method further comprising: in response to receiving the instruction to activate the SCell, transmitting a scheduling request (SR) to the wireless cellular network including an SCell activation tag and a request for dynamic uplink authorization.

[0108] Example 4 is the method according to Example 3, the method further comprising: determining that the dynamic uplink grant is received from the wireless cellular network within a predetermined time period from the transmission of the SR; and responsively determining to use the dynamic uplink grant to send the PUSCH message.

[0109] Example 5 is the method according to Example 1, wherein the PUSCH message is sent using a selected uplink grant from a plurality of periodic uplink grants.

[0110] Example 6 is the method according to Example 5, wherein the selected uplink grant is the first uplink grant that occurs after receiving the instruction for activating the SCell among the plurality of periodic uplink grants.

[0111] Example 7 is the method according to Example 5, wherein the selected uplink grant is any uplink grant that occurs within a predetermined time after receiving the instruction for activating the SCell from among the plurality of periodic uplink grants.

[0112] Example 8 is the method according to Example 5, wherein the selected uplink grant is the first uplink grant that occurs within a predetermined time after receiving the instruction for activating the SCell among the plurality of periodic uplink grants.

[0113] Example 9 is the method according to Example 1, wherein the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as a first step.

[0114] Example 10 is a method comprising: sending a user equipment (UE) instruction to activate a secondary cell (SCell); receiving a Layer 3 (L3) measurement report from the UE in a Physical Uplink Shared Channel (PUSCH) message; and determining, in response to receiving the L3 measurement report, that the UE is performing a shortened SCell activation process.

[0115] Example 11 is the method according to Example 10, the method further comprising: waiting for a predetermined period of time after transmitting an instruction to receive a scheduling request (SR) from the UE.

[0116] Example 12 is the method according to Example 11, the method further comprising: receiving an enhanced SR including an SCell activation tag and a request for dynamic uplink authorization during the predetermined time period.

[0117] Example 13 is the method according to Example 12, wherein the predetermined time period is a first predetermined time period, and the method further includes: transmitting the dynamic uplink grant to the UE during a second predetermined time period.

[0118] Example 14 is the method according to Example 12, the method further comprising: assigning a higher priority to the enhanced SR than to the conventional SR.

[0119] Example 15 is the method according to Example 11, wherein the PUSCH message is received in one of a plurality of periodic uplink grants.

[0120] Example 16 is the method according to Example 15, wherein receiving the L3 measurement report in a PUSCH message includes: checking the L3 measurement report in a subset of the plurality of periodic uplink grants received within a predetermined time period after sending the instruction for activating the SCell.

[0121] Example 17 is the method according to Example 10, wherein the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as a first step.

[0122] Example 18 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of the device, cause the device to perform one or more elements of the method or any other method or process described herein, as described or associated with any of Examples 1 to 17.

[0123] Example 19 may include an apparatus comprising logic components, modules, and / or circuitry (e.g., processing circuitry) for performing one or more elements of the methods described or associated with any of Examples 1 to 17 or any other methods or processes described herein.

[0124] Example 20 may include a method, technique, or process, or a part or component thereof, as described or associated with any of Examples 1 to 17.

[0125] Example 21 may include an apparatus comprising one or more processors configured to perform a method, technique, or process, or a portion thereof, as described or associated with any one of Examples 1 to 17.

[0126] Example 22 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process, or a portion thereof, as described or associated with any one of Examples 1 to 17. The operation or action performed by the instructions executed by the processing element may include the method according to any one of Examples 1 to 17.

[0127] Example 23 may include methods for communicating in a wireless network as shown and described herein.

[0128] Example 24 may include a system for providing wireless communication as shown and described herein. Operations or actions performed by said system may include methods as described in any one of Examples 1 to 17.

[0129] Example 25 may include a device for providing wireless communication as shown and described herein. Operations or actions performed by said device may include methods as described in any one of Examples 1 to 17.

[0130] Example 26 may include a base station configured to perform the method as described in any one of Examples 10 to 17.

[0131] Example 27 may include user equipment configured to perform the method as described in any one of Examples 1 to 9.

[0132] Unless otherwise expressly stated, any of the embodiments described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0133] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

[0134] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

Claims

1. One or more processors, said processors being configured to perform operations including: Receive instructions to activate secondary cells (SCells) from the wireless cellular network via interface circuitry; The interface circuit transmits a Layer 3 (L3) measurement report to the wireless cellular network in a Physical Uplink Shared Channel (PUSCH) message; and Perform a shortened SCell activation process.

2. The processor of claim 1 or more, wherein the PUSCH message is sent using dynamic uplink grant.

3. The processor according to claim 1, wherein the operation further comprises: In response to receiving the instruction to activate the SCell, a scheduling request (SR) including an SCell activation tag and a request for dynamic uplink authorization is transmitted to the wireless cellular network via the interface circuit.

4. The operation further includes: (The first part of the text is missing, but can be omitted.) Determine that the dynamic uplink grant is received from the wireless cellular network within a predetermined period of time starting from the transmission of the SR; as well as In response, it is determined that the dynamic uplink grant will be used to send the PUSCH message.

5. The processor of claim 1, wherein the PUSCH message is sent using a selected uplink grant from a plurality of periodic uplink grants.

6. The processor of claim 5, wherein the selected uplink grant is the first uplink grant of the plurality of periodic uplink grants that occurs after receiving the instruction for activating the SCell.

7. The processor of claim 5, wherein the selected uplink grant is any uplink grant that occurs within a predetermined time after receiving the instruction for activating the SCell from the plurality of periodic uplink grants.

8. The processor of claim 5, wherein the selected uplink grant is a first uplink grant that occurs within a predetermined time after receiving the instruction for activating the SCell among the plurality of periodic uplink grants.

9. The processor of claim 1, wherein the shortened SCell activation process includes performing a Send Configuration Indicator (TCI) activation as a first step.

10. One or more processors, said processors being configured to perform operations including: Send a command to activate the secondary cell (SCell) to the user equipment (UE) via the interface circuit; Measurements are reported from the UE's Receive Layer 3 (L3) via the interface circuit in the Physical Uplink Shared Channel (PUSCH) message; and In response to receiving the L3 measurement report, it is determined that the UE is performing a shortened SCell activation process.

11. The one or more processors according to claim 10, wherein the operation further comprises: After transmitting the instruction to receive a scheduling request (SR) from the UE, wait for a predetermined period of time.

12. The operation further comprises: An enhanced SR is received during the predetermined time period, including a SCell activation tag and a request for dynamic uplink authorization.

13. The processor of claim 12, wherein the predetermined time period is a first predetermined time period, and the operation further comprises: The dynamic uplink authorization is transmitted to the UE via the interface circuit during the second predetermined time period.

14. The operation further comprises: The enhanced SR is assigned a higher priority than the traditional SR.

15. The processor of claim 11, wherein the PUSCH message is received in one of a plurality of periodic uplink grants.

16. The processor of claim 15, wherein receiving the L3 measurement report in a PUSCH message comprises: The L3 measurement report is checked within a subset of the multiple periodic uplink grants received during a predetermined period after the instruction to activate the SCell is sent.

17. The processor of claim 10, wherein the shortened SCell activation process includes performing a transmit configuration indicator (TCI) activation as a first step.

18. A method for performing the operation according to any one of claims 1 to 17.

19. A user equipment comprising one or more processors according to any one of claims 1 to 9.

20. A base station comprising one or more processors according to any one of claims 10 to 17.

Images