Power prioritization and UE-based timing advance acquisition for PRACH for candidate cells in wireless communications

Abstract

The invention relates to power prioritization and UE-based timing advance acquisition for PRACH for candidate cells in wireless communications. Processes and systems are described for configuration based on timing advance (TA) acquisition of a user equipment (UE) and power prioritization of a physical random access channel (PRACH) in a wireless communication network.

Description

Background Art

[0001] Wireless communication networks provide integrated communication platforms and telecommunication services to wireless user devices. Example telecommunication services include telephone, data (e.g., voice, audio and / or video data), messaging and / or other services. Wireless communication networks have wireless access nodes that exchange wireless signals with wireless user devices using wireless network protocols (such as protocols described in various telecommunication standards promulgated by the Third 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 fifth generation new radio (5G NR). Wireless communication networks use technologies such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming and / or other features to facilitate mobile broadband services. Summary of the invention

[0002] The present application describes a process and system for configuring timing advance (TA) acquisition and power prioritization of a physical random access channel (PRACH) based on a user equipment (UE) in a wireless communication network. A communication network (such as a fifth generation (5G) new radio (NR) network) is configured for mobility robustness when the UE moves within the network. The UE may execute one or more applications in the network or use one or more services that rely on low latency and high reliability performance (e.g., URLLC).

[0003] This specification describes mechanisms and procedures related to L1 / L2 based inter-cell mobility (LTM) for mobility delay reduction. In particular, this specification describes timing advance (TA) management, such as when multiple TAs are configured.

[0004] This specification describes how a UE operates in a power limited scenario for LTM. For example, this specification describes a process of how a UE is configured to partition transmission power for PRACH transmissions in a PDCCH sequence on a candidate cell and for UL transmissions on a serving cell.

[0005] This specification describes a process for implementing UE-based TA acquisition. This specification describes a process for UE-based TA measurement, where the UE is configured to determine the TA based on a receive (Rx) timing difference between a current serving cell and a candidate cell and based on the TA value of the current serving cell.

[0006] According to one aspect of the present disclosure, an example process includes: receiving configuration data at a user equipment (UE) from a wireless communication network, the configuration data specifying one or more prioritization rules for the UE to transmit to a serving cell or a candidate cell in the wireless communication network, the one or more prioritization rules specifying when the UE is scheduled to perform a first transmission including a physical data or control channel and a second transmission including a physical random access channel (PRACH) and the first transmission and the second transmission overlap in time, a transmission priority for the first transmission and the second transmission. The process includes transmitting, by the UE, the first transmission, the second transmission, or both the first transmission and the second transmission according to the one or more prioritization rules.

[0007] In some implementations, the configuration data is transmitted from the communication network as part of a system information block (SIB). In some implementations, the configuration data is transmitted from the communication network as part of a radio resource control (RRC) signaling. In some implementations, the one or more priority rules for the UE are for a L1 / L2 triggered mobility (LTM) scenario of the UE.

[0008] In some implementations, the physical data or control channel comprises a physical uplink shared channel (PUSCH). In some implementations, the physical data or control channel comprises a physical uplink control channel (PUCCH). In some implementations, one or more prioritization rules specify that, for a single frequency, a PRACH transmission to a candidate non-serving cell takes precedence over an overlapping PUSCH transmission to a serving cell on the same frequency.

[0009] In some implementations, one or more prioritization rules specify that: PRACH transmissions on a primary cell have a first priority, contention-based random access (CFRA) PRACH transmissions to one or more candidate non-serving cells have a second priority, PUCCH or PUSCH transmissions on a serving cell have a third priority, a non-periodic sounding reference signal (SRS) on a serving cell has a fourth priority, PRACH transmissions on a secondary serving cell have a fifth priority, and periodic or semi-persistent SRS on a serving cell has a sixth priority. In some implementations, the first transmission overlaps with the second transmission, and wherein the serving cell is in a first frequency, and wherein the candidate cell is in a second frequency. In some implementations, the one or more prioritization rules specify that: when a second transmission using PRACH and a first transmission using PUSCH overlap in the time domain, the second transmission using PRACH takes precedence over the first transmission using PUSCH.

[0010] In some specific implementations, the UE has at least two CFRA PRACH transmissions that overlap in time on two candidate non-serving cells, and one or more prioritization rules specify prioritization for the at least two overlapping CFRA PRACH transmissions based on respective cell identifiers of respective candidate cells associated with each respective CRFA PRACH transmission in the at least two overlapping CFRA PRACH transmissions.

[0011] In some embodiments, the first transmission overlaps with the second transmission in time and frequency, wherein the UE cannot perform uplink transmissions on multiple panels simultaneously (STxMP), and wherein one or more prioritization rules specify that the second transmission including a PRACH transmission has a higher priority than the first transmission, wherein the first transmission includes a PUSCH transmission.

[0012] According to one aspect of the present disclosure, an example process includes receiving, at a user equipment (UE), configuration data specifying a timing advance (TA) acquisition process for the UE in a L1 / L2 triggered mobility (LTM) scenario. The process includes transmitting uplink (UL) data to a target cell, the transmission being based on a TA value determined by the UE based on the TA acquisition process specified by the configuration data.

[0013] In some implementations, the configuration data is received at the UE based on dedicated radio resource control (RRC) signaling. In some implementations, the RRC signaling includes an indicator indicating an on state of the UE or an off state of the UE, wherein the 'on' state is used to enable a TA acquisition process for all candidate non-serving cells, and the 'off' state is used to disable the TA acquisition process for all candidate non-serving cells. In some implementations, the RRC signaling includes an indicator for each candidate cell in a candidate cell set, the indicator indicating an on state or an off state of a UE-based TA acquisition process, wherein a target cell for the LTM operation is a candidate cell in the candidate cell set.

[0014] In some embodiments, configuration data is received at a UE based on a medium access control (MAC) control element (CE), which activates a set of transmission configuration indicator (TCI) states prior to a cell switching operation for a candidate cell, wherein a separate field in the MAC CE enables a TA acquisition process for the candidate cell.

[0015] In some specific implementations, the UE is configured to derive the TA value of the candidate cell based on the TA value of the serving cell and the downlink receive timing difference (RTD) between the serving cell and the candidate cell in response to the MAC-CE activating the TCI state of the candidate cell.

[0016] In some implementations, a cell switch command (CSC) that triggers a cell switch to a candidate non-serving cell enables a TA acquisition procedure for the candidate non-serving cell.

[0017] In some implementations, a medium access control (MAC) control element (CE) is configured to activate or deactivate a TA acquisition procedure based on received signal received power (RSRP) associated with different candidate non-serving cells of a UE. In some implementations, the MAC CE includes a plurality of index fields, each index field being associated with a candidate cell index, and wherein a value of a given index field Ci indicates activation or deactivation of a candidate cell associated with the candidate index of the given index field Ci. In some implementations, the MAC CE has a fixed size.

[0018] According to one aspect of the present disclosure, an example process includes receiving configuration data at a user equipment (UE) that specifies triggering conditions for the UE to update a timing advance (TA) value of a candidate cell for L1 / L2 triggered mobility (LTM) operation. The process includes updating, by the UE and based on the configuration data, the TA value of the candidate cell.

[0019] In some implementations, configuration data is transmitted to the UE based on radio resource control (RRC) signaling, wherein the configuration data specifies a TA update timer, and wherein the UE is configured to update the TA value of the candidate cell when the TA update timer expires.

[0020] In some implementations, a set of timing accuracy requirements are predefined in the specification, and wherein the UE updates the TA value to meet the predefined timing accuracy requirements independent of receiving the configuration data.

[0021] In some implementations, the configuration data is transmitted to the UE based on a downlink control information (DCI) format. In some implementations, the DCI format includes multiple fields for a shared UE, wherein each of the multiple fields specifies a TA update value, and the TA update value indicates whether the shared UE is triggered to update the TA value of the corresponding candidate cell. In some implementations, the field index of the TA update value of the corresponding candidate non-serving cell is configured based on RRC signaling. In some implementations, the TA update value of each corresponding candidate cell is associated based on the order of the fields in the DCI format, wherein the TA values ​​of the multiple fields are assigned to the corresponding candidate cell based on the corresponding cell index of the candidate cell. In some implementations, the DCI format includes multiple fields, wherein each of the multiple fields specifies a corresponding candidate cell index for a corresponding different UE.

[0022] The details of one or more embodiments of these systems and methods are set forth in the following drawings and description. Other features, objects, and advantages of these systems and methods will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 A wireless network according to some implementations is shown.

[0024] Figure 2 An example of a network in which an example UE performs PDCCH-ordered physical random access (PRACH) transmissions is shown.

[0025] Figure 3 An example of a network in which an example UE performs PDCCH-ordered PRACH transmissions is shown.

[0026] Figure 4A An example of a UE-based TA acquisition procedure for a UE based on Radio Resource Control (RRC) signaling is shown.

[0027] Figure 4B An example of a UE-based TA acquisition procedure for a UE based on a MAC CE is shown.

[0028] Figure 4C An example of a UE-based TA acquisition procedure for a UE based on a Cell Switch Command (CSC) is shown.

[0029] Figure 5A An example of a DCI format configured to trigger a TA update procedure is shown.

[0030] Figure 5B An example of a DCI format configured to trigger a TA update procedure is shown.

[0031] Figure 6 An example of a MAC CE configured to activate or deactivate a subset of candidate cells for a UE-based TA acquisition procedure is shown.

[0032] Figure 7 A flowchart of an example method according to some implementations is shown.

[0033] Figure 8 A flowchart of an example method according to some implementations is shown.

[0034] Fig. 9 A flowchart of an example method according to some implementations is shown.

[0035] Fig.10 An example user equipment (UE) is shown according to some implementations.

[0036] Fig.11 An example access node according to some implementations is shown. DETAILED DESCRIPTION

[0037] The present application describes a process and system for configuring timing advance (TA) acquisition and power prioritization of a physical random access channel (PRACH) based on a user equipment (UE) in a wireless communication network. A communication network (such as a fifth generation (5G) new radio (NR) network) is configured for mobility robustness when the UE moves within the network. The UE may execute one or more applications in the network or use one or more services that rely on low latency and high reliability performance (e.g., URLLC).

[0038] In general, PRACH is used to carry random access preambles from UEs to next generation nodes (gNBs), such as base stations. In addition to other parameters, base stations use PRACH transmissions to adjust the uplink timing of UEs. In some implementations, Zadoff chu sequences are used to generate random access preambles. Compared to LTE networks, 5G NR random access preamble configurations support two different sequence lengths with various format configurations used in a wide range of deployment scenarios. For example, 839 long sequences use four preamble formats. The preamble format is used for large cell deployments in FR1 (below 6 GHz range) and uses a subcarrier spacing of 1.25 kilohertz (kHz) or 5 kHz. 139 short sequences use nine preamble formats. These formats are designed for small cell deployments including indoor coverage. These preamble formats are used in FR1 (below 6 GHz) and FR2 millimeter wave (mmwave) ranges. FR1 supports 15 kHz or 30 kHz subcarrier spacing, and FR2 supports 60 kHz or 120 kHz subcarrier spacing.

[0039] In general, PRACH uses the same FFT as the FFT used for data. OFDM baseband signal generation for PRACH is defined in Section 5.3.2 of 3GPP TS 38.211. For beam establishment, different SS block time indices are associated with different RACH time / frequency opportunities. SIB1 provides the "number of SS block time indices per RACH time / frequency opportunity". The SSB time index is associated with the RACH opportunity first in frequency, then in time within a slot, and finally in time between slots. For UE initial access, the reference signals used for beam management are the primary synchronization signal (PSS), the secondary synchronization signal (SSS), and the physical broadcast channel (PBCH) demodulation reference signal (DM-RS). The PBCH DMRS may include synchronization signal blocks (SSBs) for idle mode. In connected mode, the PBCH DMRS may include a channel state information reference signal (CSI-RS) for downlink (DL) transmission and a sounding reference signal (SRS) for uplink (UL) transmission.

[0040] This specification describes mechanisms and procedures related to L1 / L2 based inter-cell mobility (LTM) for mobility latency reduction. Specifically, this specification describes timing advance (TA) management, such as when multiple TAs are configured. PRACH transmissions in a physical downlink control channel (PDCCH) sequence on a candidate cell may overlap with uplink transmissions on a serving cell. This specification describes how to prioritize overlapping transmissions for UEs that cannot transmit simultaneously across multiple panels (STxMP). In this case, instead of intra-frequency transmissions, multiple panels may be used for parallel transmissions by the UE, such that UL data transmissions and PRACH are scheduled to occur in parallel. This specification describes prioritization between overlapping transmissions within a frequency band.

[0041] This specification describes how a UE operates in a power limited scenario for LTM. For example, this specification describes a process for how a UE is configured to partition transmit power for PRACH transmissions in PDCCH order on a candidate cell and for UL transmissions on a serving cell. The UE determines transmission priority between parallel PDCCH and UL transmissions for a serving cell, where the UE does not exceed the transmit power specified by the UE power class.

[0042] This specification describes a procedure for implementing UE-based TA acquisition. This specification describes a procedure for UE-based TA measurement, where the UE is configured to determine the TA based on the receive (Rx) timing difference between the current serving cell and the candidate cell and based on the TA value of the current serving cell. In the LTM context, the UE is moving and the UE updates the TA configuration based on the change in the measured timing difference between the current serving cell and the candidate cell. Corresponding UE capabilities will be introduced to support UE-based TA measurement.

[0043] In order to update the determined TA configuration, the UE consumes memory, bandwidth and power. The UE updates the number of supported cells for which the UE can update the TA configuration based on the memory, bandwidth and power constraints of the UE. The UE is configured to report that the UE supports UE-based TA acquisition and the supported configuration of UE-based TA measurement. Specifically, this specification describes how to enable or configure UE-based TA acquisition for candidate cells in LTM operation. This specification describes how to trigger the UE to perform TA updates for candidate cells for UE-based TA acquisition. This specification describes how to efficiently manage candidate cells to enable UE-based TA acquisition when the UE only supports a limited number of cells for the UE-based TA acquisition procedure. The UE-based TA acquisition process described herein can enable the removal of uplink synchronization procedures in traditional handover steps for LTM.

[0044] Figure 1 A wireless network 100 is shown according to some implementations. The wireless network 100 includes UEs 102 and base stations 104 connected via one or more channels 106A, 106B across an air interface 108. The UEs 102 and base stations 104 communicate using a system that supports control for managing access of the UEs 102 via the base stations 104 to the network.

[0045] In some implementations, the wireless network 100 may be a non-standalone (NSA) network that combines Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the Third Generation Partnership Project (3GPP) technical specifications. For example, the wireless network 100 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. In some other implementations, the wireless network 100 may be a standalone (SA) network that combines only 5G NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)), Institute of Electrical and Electronics Engineers (IEEE) 802.11 technology (e.g., IEEE 802.11a; IEEE 802.11b; IEEE802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future developed IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), etc. Although aspects may be described herein using terms typically associated with 5G NR, aspects of the present disclosure may be applied to other systems, such as 3G, 4G, and / or systems after 5G (e.g., 6G).

[0046] In the wireless network 100, the UE 102 and any other UE in the system can be, for example, any of a laptop computer, a smart phone, a tablet computer, a machine type device (such as a smart meter or a dedicated device for healthcare), an intelligent transportation system, or any other wireless device. In the network 100, the base station 104 provides network connectivity to the UE 102 to a wider network (not shown). The UE 102 connectivity is provided via an air interface 108 in a base station service area provided by the base station 104. In some specific 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 the base station 104 is supported by one or more antennas integrated with the base station 104. The service area can be divided into several sectors associated with one or more specific antennas. Such sectors can be physically associated with one or more fixed antennas, or can be assigned to a physical area with one or more tunable antennas or antenna settings, which can be adjusted in a beamforming process for directing signals to a specific sector.

[0047] UE 102 includes control circuitry 110 coupled to transmission circuitry 112 and reception circuitry 114. Transmission circuitry 112 and reception circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmission circuitry 112 and reception circuitry 114 may be adapted to transmit and receive data, respectively, and may include radio frequency (RF) circuitry and / or front end module (FEM) circuitry.

[0048] In various implementations, aspects of the transmission circuitry 112, reception circuitry 114, and control circuitry 110 may be integrated in various ways to implement the operations described herein. The control circuitry 110 may be adapted or configured to perform various operations, such as various operations related to a UE described elsewhere in this disclosure.

[0049] The transmission circuit 112 may perform various operations described in this specification. The transmission circuit 112 may use a plurality of multiplexed uplink physical channels for transmission. The plurality of uplink physical channels may be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. The transmission circuit 112 may be configured to receive block data from the control circuit 110 for transmission across the air interface 108.

[0050] The receiving circuit 114 may perform various operations described in this specification. In addition, the receiving circuit 114 may receive a plurality of multiplexed downlink physical channels from the air interface 108 and relay these physical channels to the control circuit 110. The plurality of downlink physical channels may be multiplexed, for example, according to TDM or FDM and carrier aggregation. The transmitting circuit 112 and the receiving circuit 114 may transmit and receive control data and content data (e.g., messages, images, videos, etc.) structured within data blocks carried by the physical channels, respectively.

[0051] Figure 1 A base station 104 is also shown. In some implementations, the base station 104 may be a 5G radio access network (RAN) or a next-generation RAN, an E-UTRAN, a non-terrestrial cell, or a traditional RAN such as a UTRAN. As used herein, the term "5G RAN" or the like may refer to a base station 104 operating in an NR or 5G wireless network 100, and the term "E-UTRAN" or the like may refer to a base station 104 operating in an LTE or 4G wireless network 100. The UE 102 utilizes connections (or channels) 106A, 106B, each connection comprising a physical communication interface or layer.

[0052] The base station 104 circuitry may include control circuitry 116 coupled to transmission circuitry 118 and reception circuitry 120. The transmission circuitry 118 and reception circuitry 120 may each be coupled to one or more antennas that may be used to enable communication via the air interface 108. The transmission circuitry 118 and reception circuitry 120 may be adapted to transmit and receive data, respectively, to any UE connected to the base station 104. The reception circuitry 120 may receive a plurality of uplink physical channels from one or more UEs including the UE 102.

[0053] exist Figure 1 In the figure, one or more channels 106A, 106B are shown as air interfaces to achieve communication coupling, and may conform to cellular communication protocols, such as UMTS protocols, 3GPP LTE protocols, advanced long term evolution (LTE-A) protocols, LTE-based unlicensed spectrum access (LTE-U), 5G protocols, NR protocols, NR-based unlicensed spectrum access (NR-U) protocols, and / or any other communication protocols. In a specific implementation, the UE 102 may directly exchange communication data via the ProSe interface. The ProSe interface may alternatively be referred to as a sidelink (SL) interface and may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0054] Figure 2 An example of a network 200 in which an example UE performs PRCCH transmissions in a PDCCH order is shown. The example UE 202 may include the previously described Figure 1 The base stations of the serving cell 204 and / or the candidate cell 206 may each include the previously described Figure 1 A base station 104 is depicted. Figure 2The illustrated scenario shows that the serving cell 204 and the candidate cell 206 are using different frequency layers in the frequency domain to receive transmissions. The UE 202 transmits PUSCH transmissions 208 and PRACH transmissions 210 simultaneously but at different frequency layers. The physical uplink shared channel (PUSCH) is used to carry user data and optionally carry uplink control information (UCI). For example, the PUSCH transmission 208 to the serving cell 204 performed by the UE 202 uses a first frequency layer, and the PRACH transmission 210 performed by the UE 202 uses a different second frequency layer. In this example, PUSCH and PRACH are transmitted in parallel (e.g., on a time slot) in a high mobility operation scenario. In this example, the UE 202 prioritizes the PRACH transmissions on the candidate cell 206 over the overlapping PUSCH transmissions on the serving cell 204 to minimize the TA acquisition delay for LTM. As described subsequently, the UE 202 performs power scaling in this context.

[0055] UE 202 is configured to prioritize PUSCH transmissions or PRACH transmissions in a scenario where the total transmission power of UL transmissions across the serving cell and the candidate cells exceeds a threshold maximum transmission power of the UE. The threshold maximum transmission power may be predefined.

[0056] Prioritization of PUSCH and PRACH is defined as described. In a first example, a priority order is predefined (hardcoded) for UE 202. The predefined order ensures that UE 202 allocates power so that the total UE transmit power does not exceed the threshold maximum transmit power of the UE. In some specific implementations, the prioritization is predefined as follows in descending order of priority. The first priority (higher) includes PRACH on the primary cell (PCell). The second priority is contention-based random access (CFRA) PRACH on one or more candidate cells for LTM operation. The third priority includes PUCCH and / or PUSCH transmissions. The fourth priority includes aperiodic sounding reference signal (SRS) transmission. SRS is transmitted at the last symbol of a UL timeslot with a full system frequency band area, and it is transmitted at a specific interval and enables a base station (e.g., a gNB) to perform channel quality estimation based on the SRS from the UE. The fifth priority includes PRACH on a secondary cell (SCell). The sixth (lower) priority includes periodic or semi-persistent SRS transmissions. In some implementations, more than one CFRA PRACH overlaps on a candidate cell, such as candidate cell 206 and other candidate cells. In this case, UE 202 prioritizes the CFRA PRACH on a given candidate cell associated with a smaller candidate cell identifier (ID). Figure 2A network 200 is shown in which a PRACH transmission 210 to a candidate cell 206 takes precedence over a PUSCH transmission 208 to a serving cell 204 .

[0057] Figure 3 An example of a network 300 in which an example UE 202 performs PRACH transmissions in a PDCCH order is shown. The example UE 302 may include the previously described Figure 1 The base stations of the serving cell 204 and / or the candidate cell 206 may each include the previously described Figure 1 or Figure 2 The base station 104 described. Specifically, Figure 3 An example scenario is shown in which a UE 302 has a scheduled PUSCH transmission 208 toward a serving cell 204 and a PRACH transmission toward a candidate cell 206. In this scenario, the UE 302 cannot perform parallel or simultaneous transmissions of the PSUCH transmission 208 and the PRACH transmission 210, such as on different frequency layers. In this example, the UE 302 is configured to prioritize the PRACH 210 transmission to the candidate cell 206, such as Figure 3 Therefore, UE 302 performs to prioritize PRACH 210 on candidate cell 206 over overlapping PUSCH transmission 208 on serving cell 204. Due to the overlap with PRACH transmission 210, UE 302 discards the overlapping PUSCH symbols.

[0058] Figures 2 to 3 The scenarios in are examples of prioritization rules, but one or more other prioritization rules may be predefined for UE 302. The network selects a configuration based on the deployment scenario. The network indicates the selected rules to UE 302 through one or more mechanisms. For example, the network may signal the prioritization rules using a system information block (SIB). In another example, the network signals the configuration to the UE through a UE-specific RRC signal to operate L1 / L2 triggered mobility (LTM) operation.

[0059] In some implementations, a UE, such as UE 302, cannot perform uplink transmissions on multiple panels simultaneously (STxMP). In an example, UE 302 is configured to prioritize contention-based random access (CFRA) PRACH toward candidate cell 206 and discard at least the overlapping portion of UL transmissions on serving cell 204.

[0060] FIG. 4A to FIG. 4C Each shows an example of a UE-based TA acquisition procedure for a UE. Specifically, FIG. 4A to FIG. 4CEach of the Figures 1 and 2 shows a process for implementing UE-based TA acquisition. For UE-based TA measurement, the UE is configured to determine the TA based on the receive (Rx) timing difference between the current serving cell and the candidate cell and based on the TA value of the current serving cell. As the UE moves through the environment relative to the serving cell or the candidate cell, the UE updates the TA configuration based on the change in the measured timing difference between the current serving cell and the candidate cell.

[0061] The UE updates the number of supported cells for which the UE can update the TA configuration based on the memory, bandwidth and power constraints of the UE. The UE is configured to report that the UE supports UE-based TA acquisition and the supported configuration of UE-based TA measurements. Several examples of the UE and / or the network may determine candidate cells for operation of the UE-based TA acquisition procedure and enable or configure UE-based TA acquisition for the candidate cells in the LTM operation.

[0062] Figure 4A An example of an RRC signaling process 400 for enabling or configuring a UE-based TA acquisition procedure is shown. UE-specific RRC signaling may be provided to enable a UE-based TA acquisition procedure for LTM operation for a given UE. For example, an RRC parameter referred to as UE-based TA may be included in the LTM configuration data.

[0063] The RRC signal 402 specifies UE reconfiguration data. In some implementations, the RRC signaling provides enabling / or disabling (e.g., an on-off indication) of TA acquisition for candidate cells on a per-UE basis. In this example, a given information element (IE) is configured on a per-UE basis as follows. The IE specifies a field {UE-based TA, ENUMERATED {enable / disable}}. In some implementations, when the second field of the IE is set to 'enabled' based on the UE's TA, a UE-based TA acquisition procedure is enabled for all candidate cells to maintain uplink timing advance (UL TA). In another example, an on / off indicator for a UE-based TA acquisition procedure is provided for each candidate cell. This has a larger granularity than a per-UE signal because some candidate cells may be suitable for UE-based TA, while other candidate cells are not suitable for communicating with the UE in LTM. Suitability may be based on the ability of time synchronization between the candidate cell and the serving cell. For example, the suitability of a candidate cell may be based on inter-DL or intra-DL capabilities. For each candidate cell in the LTM, a field UE-based TA is included to indicate whether the UE-based TA acquisition procedure is enabled for the particular identified candidate cell.

[0064] exist Figure 4A In the process 400, the UE is in the time period T RRCReceive RRC signal 402. Then, UE processing,1 The UE then configures the TA acquisition for the specified candidate cell according to the RRC signaling by enabling or disabling it. At step 404, the UE performs a downlink synchronization procedure based on the configuration specified in the RRC signaling at step 402. search Search in the search space and also in T meas During the measurement, measurements of signals from the candidate cells are performed. A measurement report 406 may then be sent based on the measured signals.

[0065] This specification describes how to trigger a UE to perform TA update for candidate cells for UE-based TA acquisition. This specification describes how to efficiently manage candidate cells to enable UE-based TA acquisition when the UE supports only a limited number of cells for the UE-based TA acquisition procedure. The UE-based TA acquisition procedure described herein can enable the removal of uplink synchronization procedures in the traditional handover steps for LTM.

[0066] Figure 4B An example of a UE-based TA acquisition procedure 410 for a UE based on a MAC CE is shown. In some implementations, the initial state is performed Figure 4A 412 is used after the RRC signaling 402 of the UE. The network (e.g., through the base station) can send the MAC CE to the UE to specify which cells are candidate cells eligible for UE-based TA acquisition. In some implementations, the network transmits to the UE in the first instance or initial configuration phase. Figure 4A 414 (e.g., similar to 414). Figure 4A 404) during DL synchronization of the UE. Since the target cell may have been selected, the transmission of the activation signal may initiate DL synchronization for the UE. The number of identified candidate cells is significantly reduced.

[0067] MAC CE 412 changes the DL synchronization process for the UE, such as Figure 4BAs shown. The UE receives a MAC CE that specifies that a UE-based TA acquisition procedure is enabled through TCI state activation data. The UE receives a MAC CE 414 before a cell switching operation for a given candidate cell. In some implementations, the UE receives an indicator, such as a 1-bit UE-based TA indicator 416. When the indicator 416 is set to 'enabled' (e.g., '1') in the MAC-CE 412, the UE starts to derive the TA value of the candidate cell based on the TA value of the serving cell and the DL receive timing difference (RTD) between the serving cell and the target cell. The UE determines the timing difference T Δ 418. UE determines the timing margin T margin 420.

[0068] As part of MAC CE 412, the UE adds the corresponding candidate cells identified in MAC CE 412 to maintain or not maintain UE TA acquisition. On the UE side, since only a relatively small number of candidate cells (e.g., one or two cells) are identified as target cells, power consumption is reduced. The UE maintains TA acquisition only for these identified cells. This second step may be based on (e.g., in Figure 4A The RSRP report measured in the T measurement report 406 is used. Therefore, the MAC CE 412 can specify a small number of target cells for DL ​​synchronization, thereby significantly reducing the power consumption overhead of the UE. For example, assuming that eight candidate cells are configured for measurement and only two of these candidate cells are addressed by the MAC-CE to activate the TCI state, the power consumption of the UE TA measurement is reduced to 2 / 8=25%.

[0069] Figure 4C An example of a UE-based TA acquisition procedure 420 for a UE based on a cell switching command (CSC) is shown. Generally speaking, once only one candidate cell remains as a target cell, the UE performs the procedure 420. For example, the UE may perform the procedure 420 after each of the procedures 400, 410 has been performed. In some implementations, the procedure 420 may be performed independently of either or both of the procedures 400, 410.

[0070] Once a cell switching command (CSC) is triggered, there is a candidate cell for UE-based TA acquisition to maintain the TA value. Figure 4C As shown, CSC 422 is sent by UE at time T cmd 424 received. UE at T processsing,2 426 processes the command. When the UE switches to the new cell identified in the CSC, UE reconfiguration occurs. The UE then uses the updated TCI state at time T first-data428 transmits data, and the data is transmitted by the UE using the indicated beam.

[0071] FIG. 5A to FIG. 5B An example signaling 500 including a DCI format configured to trigger a TA update procedure is shown. Generally speaking, the network triggers the UE to perform a TA update for a candidate cell for UE-based TA acquisition. For the UE-based TA acquisition procedure in LTM, a variety of methods can be considered to determine the time instance for updating the TA associated with the candidate cell. For example, for each candidate cell in LTM, dedicated RRC signaling for the UE from the network configures a TA update timer. When the TA update timer expires, the UE performs a timing difference measurement and updates the TA value of the candidate cell accordingly.

[0072] The network may operate to trigger the UE to perform a TA update for a candidate cell for UE-based TA acquisition based on a predefined scenario. For example, the UE may know in advance a set of timing accuracy requirements for the UE to trigger a TA update. The UE maintains the TA for the candidate cell and meets the predefined TA requirements, so that the network does not need to signal to the UE any specific requirements for maintaining or updating the TA. The UE meets the predefined requirements. For example, a timing error (TE) requirement may be defined in the 3GPP specification such that the UE transmission timing error derived based on the UE-based TA acquisition should be less than ±T e , where the limit value T e Each SCS used for an SSB signal is specified in the specification.

[0073] The network may operate to trigger the UE to perform TA update for candidate cells for UE-based TA acquisition based on a specified DCI format. The DCI format triggers TA update as follows. In a given DCI format 500, as Figure 5A As shown, a set of TA update fields 502a-n are included. These fields include TA Update #1, TA Update #2, ..., TA Update #N, etc. In some specific implementations, the UE is configured by RRC signaling to associate the candidate cells with the corresponding TA update fields 502a-n of the DCI format 500. In some specific implementations, the association between the candidate cells and the TA update fields is implicitly determined based on the candidate cell index, and no additional specifications are required in the RRC signaling. For example, the candidate cell indexes can be arranged in ascending order, where "TA Update #1" is associated with the candidate cell with the smallest index value. Other such implicit associations can be used. In some specific implementations, the size of the new DCI format 500 can be configured by RRC signaling. In this example, the UE can update the TA value for multiple cells for the same UE.

[0074] Figure 5BAn example of a DCI format 510 configured to trigger a TA update procedure is shown. In this example, there are typically a limited number of candidate cells. DCI format 510 is a group-common DCI format that includes the following fields 512a-m: candidate cell index #1, candidate cell index #2, ..., candidate cell index #M. In DCI format 510, a first candidate cell index field 5102a is configured for a first UE (e.g., UE 102, 202, 302, etc.), and different candidate cell index fields (e.g., fields 512b ... 512m) are used for corresponding different UEs. Therefore, many UEs use the same DCI, and each UE can be associated with a specific candidate cell for updating the TA value. In some specific implementations, the size of the new DCI format 510 can be configured by RRC signaling. For DCI formats 500 and 510, the network controls the TA update.

[0075] Figure 6 An example of a MAC CE 600 configured to activate or deactivate a subset of candidate cells for a UE-based TA acquisition procedure is shown. The MAC-CE 600 is configured to dynamically activate or deactivate a subset of candidate cells to perform a UE-based TA acquisition procedure. n The number of may be based on the number of available candidate cells. The UE-based TA acquisition procedure may be based on the L1-RSRP report from the UE.

[0076] The new activation / deactivation MAC-CE consists of the following fields. The first field is C i , which indicates the candidate cell configured with the candidate cell index 'i'. i The fields each indicate the activation / deactivation status of the UE-based TA acquisition procedure for the candidate cell with candidate cell index i. i field, the MAC entity ignores C i field. When C i When the field is set to '1', if the UE-based TA acquisition procedure for the candidate cell configured with the candidate cell index 'i' is in the deactivated state, it is activated, otherwise the C field set to '1' is ignored. i Field. C iThe field is set to '0' to indicate that the UE-based TA acquisition procedure for the candidate cell configured with the candidate cell index 'i' will be deactivated. MAC-CE 600 has a fixed size consisting of 'N' octets. MAC CE 600 is separated from other MAC CEs designated for the cell specified by the logical cell identifier (eLCID). MAC CE 600 is used based on the RSRP report for the UE. The base station can determine which candidate cells are triggered for handover based on the RSRP report of the UE and use MAC CE 600 to update the UE. In the example MAC CE 600, four octets are shown, but other numbers of octets are possible. In some specific implementations, MAC-CE 600 is identified by a MAC PDU subheader with a dedicated eLCID.

[0077] Figure 7 , Figure 8 and Fig. 9 1 and 2 show flowcharts of respective methods 700, 800, and 900 according to some specific implementation examples. For clarity of presentation, the following description generally describes methods 700, 800, and 900 in the context of other figures in this specification. For example, methods 700, 800, and 900 may be implemented by Figure 1 UE 102. It should be understood that methods 700, 800 and 900 can be performed by any suitable system, environment, software, hardware or a combination of systems, environments, software and hardware as appropriate. In some specific implementations, the various steps of methods 700, 800 and 900 can be executed in parallel, in combination, in a loop or in any order.

[0078] Figure 7 An example process 700 is shown. The process 700 includes receiving (702) configuration data at a user equipment (UE) from a wireless communication network, the configuration data specifying one or more prioritization rules for the UE to transmit to a serving cell or a candidate cell in the wireless communication network, the one or more prioritization rules specifying transmission priorities for a first transmission and a second transmission when the UE is scheduled to perform a first transmission on a serving cell including a physical data or control channel and a second transmission on a candidate non-serving cell including a physical random access channel (PRACH) and the first transmission and the second transmission overlap in time. The process 700 includes transmitting (704) by the UE the first transmission, the second transmission, or both the first transmission and the second transmission according to the one or more prioritization rules.

[0079] In some implementations, the configuration data is transmitted from the communication network as part of a system information block (SIB). In some implementations, the configuration data is transmitted from the communication network as part of radio resource control (RRC) signaling. In some implementations, the one or more priority rules for the UE are for a lower layer triggered mobility (LTM) scenario of the UE.

[0080] In some implementations, the physical data or control channel comprises a physical uplink shared channel (PUSCH). In some implementations, the physical data or control channel comprises a physical uplink control channel (PUCCH). In some implementations, one or more prioritization rules specify that, for a single frequency, a PRACH transmission to a candidate non-serving cell takes precedence over an overlapping PUSCH transmission to a serving cell on the same frequency.

[0081] In some implementations, one or more prioritization rules specify that: PRACH transmissions on a primary cell have a first priority, contention-based random access (CFRA) PRACH transmissions to one or more candidate non-serving cells have a second priority, PUCCH or PUSCH transmissions on a serving cell have a third priority, a non-periodic sounding reference signal (SRS) on a serving cell has a fourth priority, PRACH transmissions on a secondary serving cell have a fifth priority, and periodic or semi-persistent SRS on a serving cell has a sixth priority. In some implementations, the first transmission overlaps with the second transmission, and wherein the serving cell is in a first frequency, and wherein the candidate cell is in a second frequency. In some implementations, the one or more prioritization rules specify that: when a second transmission using PRACH and a first transmission using PUSCH overlap in the time domain, the second transmission using PRACH takes precedence over the first transmission using PUSCH.

[0082] In some specific implementations, the UE has at least two CFRA PRACH transmissions that overlap in time on two candidate non-serving cells, and one or more prioritization rules specify prioritization for the at least two overlapping CFRA PRACH transmissions based on respective cell identifiers of respective candidate cells associated with each respective CRFA PRACH transmission in the at least two overlapping CFRA PRACH transmissions.

[0083] In some embodiments, the first transmission overlaps with the second transmission in time and frequency, wherein the UE cannot perform uplink transmissions on multiple panels simultaneously (STxMP), and wherein one or more prioritization rules specify that the second transmission including a PRACH transmission has a higher priority than the first transmission, wherein the first transmission includes a PUSCH transmission.

[0084] Figure 8 An example process 800 is shown. The process 800 includes receiving (802) at a user equipment (UE) configuration data specifying a timing advance (TA) acquisition procedure for the UE in an L1 or L2 triggered mobility (LTM) operation. The process 800 includes transmitting (804) uplink (UL) data to a target cell, the transmission based on a TA value determined by the UE based on the TA acquisition procedure specified by the configuration data.

[0085] In some implementations, the configuration data is received at the UE based on dedicated radio resource control (RRC) signaling. In some implementations, the RRC signaling includes an indicator indicating an on state of the UE or an off state of the UE, wherein the 'on' state is used to enable a TA acquisition process for all candidate non-serving cells, and the 'off' state is used to disable the TA acquisition process for all candidate non-serving cells. In some implementations, the RRC signaling includes an indicator for each candidate cell in a candidate cell set, the indicator indicating an on state or an off state of a UE-based TA acquisition process, wherein a target cell for the LTM operation is a candidate cell in the candidate cell set.

[0086] In some embodiments, configuration data is received at a UE based on a medium access control (MAC) control element (CE), which activates a set of transmission configuration indicator (TCI) states prior to a cell switching operation for a candidate cell, wherein a separate field in the MAC CE enables a TA acquisition process for the candidate cell.

[0087] In some specific implementations, the UE is configured to derive the TA value of the candidate cell based on the TA value of the serving cell and the downlink receive timing difference (RTD) between the serving cell and the candidate cell in response to the MAC-CE activating the TCI state of the candidate cell.

[0088] In some implementations, a cell switch command (CSC) that triggers a cell switch to a candidate non-serving cell enables a TA acquisition procedure for the candidate non-serving cell.

[0089] In some implementations, a medium access control (MAC) control element (CE) is configured to activate or deactivate a TA acquisition procedure based on received signal received power (RSRP) associated with different candidate non-serving cells of a UE. In some implementations, the MAC CE includes a plurality of index fields, each index field being associated with a candidate cell index, and wherein a value of a given index field Ci indicates activation or deactivation of a candidate cell associated with the candidate index of the given index field Ci. In some implementations, the MAC CE has a fixed size.

[0090] Fig. 9 An example process 900 is shown. The process 900 includes receiving (902) configuration data at a user equipment (UE) that specifies triggering conditions for the UE to update a timing advance (TA) value of a candidate cell for L1 / L2 layer triggered mobility (LTM) operation. The process 900 includes updating (904), by the UE and based on the configuration data, the TA value of the candidate cell.

[0091] In some implementations, configuration data is transmitted to the UE based on radio resource control (RRC) signaling, wherein the configuration data specifies a TA update timer, and wherein the UE is configured to update the TA value of the candidate cell when the TA update timer expires.

[0092] In some implementations, a set of timing accuracy requirements are predefined in the specification, and wherein the UE updates the TA value to meet the predefined timing accuracy requirements independent of receiving the configuration data.

[0093] In some implementations, the configuration data is transmitted to the UE based on a downlink control information (DCI) format. In some implementations, the DCI format includes multiple fields for a shared UE, wherein each of the multiple fields specifies a TA update value, and the TA update value indicates whether the shared UE is triggered to update the TA value of the corresponding candidate cell. In some implementations, the field index of the TA update value of the corresponding candidate non-serving cell is configured based on RRC signaling. In some implementations, the TA update value of each corresponding candidate cell is associated based on the order of the fields in the DCI format, wherein the TA values ​​of the multiple fields are assigned to the corresponding candidate cell based on the corresponding cell index of the candidate cell. In some implementations, the DCI format includes multiple fields, wherein each of the multiple fields specifies a corresponding candidate cell index for a corresponding different UE.

[0094] Figure 7 , Figure 8 and Fig. 9 The example methods 700, 800, and 900 shown may be modified or reconfigured to include additional, fewer, or different steps ( Figure 7 , Figure 8 or Fig. 9 ), these steps may be performed in the order shown or in a different order.

[0095] Fig.10 An example UE 1000 is shown according to some implementations. The UE 1000 may be similar to Figure 1 UE 102 and is substantially interchangeable therewith.

[0096] UE 1000 can be any mobile or non-mobile computing device, such as a mobile phone, a computer, a tablet device, an industrial wireless sensor (e.g., a microphone, a pressure sensor, a thermometer, a motion sensor, an accelerometer, an inventory sensor, a voltage / current meter, etc.), a video device (e.g., a camera, a camcorder, etc.), a wearable device (e.g., a smart watch), or a loose IoT device.

[0097] UE 1000 may include a processor 1002, an RF interface circuit 1004, a memory / storage device 1006, a user interface 1008, a sensor 1010, a driving circuit 1012, a power management integrated circuit (PMIC) 1014, one or more antennas 1016, and a battery 1018. The components of UE 1000 may be implemented as an integrated circuit (IC), a portion of an integrated circuit, a discrete electronic device or other module, logical component, hardware, software, firmware, or a combination thereof. Fig.10 The block diagram of UE 1000 is intended to show a high-level view of certain of the components of UE 1000. 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 implementations.

[0098] Components of UE 1000 may be coupled to various other components via one or more interconnects 1020, which may represent any type of interface, input / output, bus (local, system, or extension), transmission line, trace, optical connection, etc. that allows various circuit components (on common or different chips or chipsets) to interact with each other.

[0099] The processor 1002 may include processor circuits such as a baseband processor circuit (BB) 1022A, a central processor unit circuit (CPU) 1022B, and a graphics processor unit circuit (GPU) 1022C. The processor 1002 may include any type of circuit or processor circuit that executes or otherwise operates computer-executable instructions (such as program codes, software modules, or functional processes from the memory / storage device 1006) to cause the UE 1000 to perform operations as described herein.

[0100] In some implementations, the baseband processor circuit 1022A may access the communication protocol stack 1024 in the memory / storage device 1006 to communicate over a 3GPP compatible network. Generally speaking, the baseband processor circuit 1022A may access the communication protocol stack to: perform user plane functions at the physical (PHY) layer, the medium access control (MAC) layer, the radio link control (RLC) layer, the packet data convergence protocol (PDCP) layer, the service data adaptation protocol (SDAP) layer, and the PDU layer; and perform control plane functions at the PHY layer, the MAC layer, the RLC layer, the PDCP layer, the RRC layer, and the non-access layer. In some implementations, the PHY layer operations may be additionally / alternatively performed by components of the RF interface circuit 1004. The baseband processor circuit 1022A may generate or process baseband signals or waveforms that carry information in a 3GPP compatible network. In some implementations, the waveform used for NR can be based on cyclic prefix orthogonal frequency division multiplexing (OFDM) "CP-OFDM" in uplink or downlink, and discrete Fourier transform spread OFDM "DFT-S-OFDM" in uplink.

[0101] The memory / storage 1006 may include one or more non-transitory computer-readable media including instructions (e.g., the communication protocol stack 1024) that may be executed by one or more processors in the processor 1002 to cause the UE 1000 to perform various operations described herein. The memory / storage 1006 includes any type of volatile or non-volatile memory that may be distributed throughout the UE 1000. In some implementations, some of the memory / storage 1006 may be located on the processor 1002 itself (e.g., L1 cache and L2 cache), while other memory / storage 1006 is located external to the processor 1002 but may be accessed via a memory interface. The memory / storage 1006 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.

[0102] The RF interface circuit 1004 may include a transceiver circuit and a radio frequency front end module (RFEM), which allows the UE 1000 to communicate with other devices through a radio access network. The RF interface circuit 1004 may include various elements arranged in a transmission path or a reception path. These elements may include, for example, switches, mixers, amplifiers, filters, synthesizer circuits, control circuits, etc.

[0103] In the receive path, the RFEM may receive the radiated signal from the air interface via antenna 1016 and proceed to filter and amplify the signal (using a low noise amplifier). The signal may be provided to a transceiver's receiver, which down-converts the RF signal to a baseband signal, which is provided to a baseband processor of processor 1002.

[0104] In the transmit path, the transmitter of the transceiver 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 through a power amplifier before the signal is radiated across the air interface via the antenna 1016. In various specific implementations, the RF interface circuit 1004 can be configured to transmit / receive signals in a manner compatible with the NR access technology.

[0105] Antenna 1016 may include one or more antenna elements to convert electrical signals into radio waves to travel through the air and convert received radio waves into electrical signals. These antenna elements may be arranged into one or more antenna panels. Antenna 1016 may have an antenna panel that is omnidirectional, directional, or a combination thereof to achieve beamforming and multi-input, multi-output communications. Antenna 1016 may include a microstrip antenna, a printed antenna manufactured on the surface of one or more printed circuit boards, a patch antenna, a phased array antenna, etc. Antenna 1016 may have one or more panels that are designed for a specific frequency band including a frequency band in FR1 or FR2.

[0106] The user interface 1008 includes various input / output (I / O) devices designed to enable a user to interact with the UE 1000. The user interface 1008 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual device for accepting input, including in particular one or more physical or virtual buttons (e.g., reset button), physical keyboard, keypad, mouse, touch pad, touch screen, microphone, scanner, headset, etc. The output device circuit includes any physical or virtual device for displaying information or otherwise conveying information (such as sensor readings, (multiple) actuator positions or other similar information). The output device circuit may include any number or combination of audio or visual displays, including in particular one or more simple visual output / indicators (e.g., binary state indicators (such as light emitting diodes "LEDs") and multi-character visual outputs) or more complex outputs (such as display devices or touch screens (e.g., liquid crystal displays "LCDs", LED displays, quantum dot displays, projectors, etc.)), where the output of characters, graphics, multimedia objects, etc. is generated or produced by the operation of the UE 1000.

[0107] Sensor 1010 may include a device, module, or subsystem whose purpose is to detect events or changes in its environment and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit including an accelerometer, gyroscope, or magnetometer; a microelectromechanical system or nanoelectromechanical system including a three-axis accelerometer, three-axis gyroscope, or magnetometer; a liquid level sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging sensor; a proximity sensor (e.g., an infrared radiation detector, etc.); a depth sensor; an ambient light sensor; an ultrasonic transceiver; a microphone or other similar audio capture device; and the like.

[0108] The driver circuit 1012 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1000. The driver circuit 1012 may include various drivers to allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the UE 1000. For example, the driver circuit 1012 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface, a sensor driver for obtaining sensor readings of the sensor 1010 and controlling and allowing access to the sensor 1010, a driver for obtaining an actuator position of an electromechanical component or controlling and allowing access to an electromechanical component, 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.

[0109] The PMIC 1014 may manage power provided to various components of the UE 1000. Specifically, with respect to the processor 1002, the PMIC 1014 may control power selection, voltage scaling, battery charging, or DC-DC conversion.

[0110] In some implementations, the PMIC 1014 may control or otherwise be part of various power saving mechanisms of the UE 1000. The battery 1018 may power the UE 1000, but in some examples, the UE 1000 may be mounted in a fixed location and may have a power source coupled to a power grid. The battery 1018 may 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 1018 may be a typical lead-acid automotive battery.

[0111] Fig.11An access node 1100 (e.g., a base station or gNB) is shown according to some implementations. The access node 1100 can be similar to the base station 104 and can be substantially interchangeable therewith. The access node 1100 may include a processor 1102, an RF interface circuit 1104, a core network (CN) interface circuit 1106, a memory / storage device circuit 1108, and one or more antennas 1110.

[0112] Components of access node 1100 may be coupled to various other components via one or more interconnects 1112. Processor 1102, RF interface circuitry 1104, memory / storage circuitry 1108 (including communication protocol stack 1114), antenna 1110, and interconnect 1112 may be similar to those described with respect to Fig.10 Like-named elements are shown and described.For example, processor 1102 may include processor circuits such as baseband processor circuit (BB) 1116A, central processor unit circuit (CPU) 1116B, and graphics processor unit circuit (GPU) 1116C.

[0113] The CN interface circuit 1106 may provide a connection to a core network (e.g., a 5GC using a fifth generation core network (5GC) compatible network interface protocol such as a carrier Ethernet protocol or some other suitable protocol). The network connection may be provided to / from the access node 1100 via optical fiber or wireless backhaul. The CN interface circuit 1106 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 1106 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0114] As used herein, the terms "access node", "access point", etc. may be described as equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial 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. may refer to an access node 1100 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node", etc. may refer to an access node 1100 (e.g., an eNB) operating in an LTE or 4G system. According to various specific implementations, the access node 1100 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

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

[0116] 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". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0117] 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 following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits 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 of the examples shown in the example section below.

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

[0119] Although the above embodiments have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to encompass all such variations and modifications.

[0120] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 the authorized use should be clearly stated to users.

Claims

1. A method, comprising: receiving, at a user equipment (UE), configuration data from a wireless communication network, the configuration data specifying one or more prioritization rules for the UE to transmit to a serving cell or a candidate cell in the wireless communication network, the one or more prioritization rules specifying transmission priorities for the first transmission and the second transmission when the UE is scheduled to perform a first transmission on a serving cell including a physical data or control channel and a second transmission on a candidate non-serving cell including a physical random access channel (PRACH), and the first transmission and the second transmission overlap in time; as well as The first transmission, the second transmission, or both the first transmission and the second transmission are transmitted by the UE according to the one or more prioritization rules.

2. The method of claim 1, wherein the configuration data is transmitted from the communication network as part of a system information block (SIB).

3. The method of claim 1, wherein the configuration data is transmitted from the communication network as part of Radio Resource Control (RRC) signaling. 4 . The method of claim 1 , wherein the one or more prioritization rules for the UE are applied when a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) operation is enabled for the UE.

5. The method of claim 1, wherein the physical data or the control channel comprises a physical uplink shared channel (PUSCH).

6. The method of claim 1, wherein the physical data or the control channel comprises a physical uplink control channel (PUCCH).

7. The method of claim 1, wherein the one or more prioritization rules specify: For a single frequency, a PRACH transmission to the candidate non-serving cell takes precedence over an overlapping PUSCH transmission to the serving cell on the same frequency.

8. A method according to claim 1, wherein the one or more prioritization rules specify that: PRACH transmission on the primary cell has a first priority, contention-based random access (CFRA) PRACH transmission to one or more candidate non-serving cells has a second priority, PUCCH or PUSCH transmission on the serving cell has a third priority, a non-periodic sounding reference signal (SRS) on the serving cell has a fourth priority, PRACH transmission on the secondary serving cell has a fifth priority, and periodic or semi-persistent SRS on the serving cell has a sixth priority.

9. The method of claim 1, wherein the first transmission overlaps with the second transmission, and wherein the serving cell is in a first frequency, and wherein the candidate cell is in a second frequency.

10. The method of claim 9, wherein the one or more prioritization rules specify that when the second transmission using the PRACH and the first transmission using the PUSCH overlap in the time domain, the second transmission using the PRACH takes precedence over the first transmission using the PUSCH.

11. The method of claim 1 , wherein the UE has at least two CFRA PRACH transmissions that overlap in time on two candidate non-serving cells, and wherein the one or more prioritization rules specify prioritization for the at least two overlapping CFRA PRACH transmissions based on respective cell identifiers of respective candidate cells associated with each respective CRFA PRACH transmission of the at least two overlapping CFRA PRACH transmissions.

12. The method of claim 1 , wherein the first transmission overlaps with the second transmission in time and frequency, wherein the UE cannot perform uplink transmissions on multiple panels simultaneously (STxMP), and wherein the one or more prioritization rules specify that the second transmission comprising a PRACH transmission has a higher priority than the first transmission, wherein the first transmission comprises a PUSCH transmission.

13. A method comprising: receiving, at a user equipment (UE), configuration data specifying a timing advance (TA) acquisition procedure for the UE in a L1 / L2 triggered mobility (LTM) scenario; as well as Uplink (UL) data is transmitted to a target cell, the transmission being based on a TA value determined by the UE based on the TA acquisition procedure specified by the configuration data.

14. The method of claim 13, wherein the configuration data is received at the UE based on dedicated radio resource control (RRC) signaling.

15. The method according to claim 14, wherein the RRC signaling includes an indicator indicating an on state of the UE or an off state of the UE, wherein the on state is used to enable the TA acquisition process for all candidate non-serving cells, and the off state is used to disable the TA acquisition process for all the candidate non-serving cells.

16. The method according to claim 14, wherein the RRC signaling includes an indicator for each candidate cell in a candidate cell set, the indicator indicating an on state or an off state of the TA acquisition process, wherein the target cell of the LTM operation is a candidate cell in the candidate cell set.

17. The method of claim 13, wherein the configuration data is received at the UE based on a medium access control (MAC) control element (CE), the MAC CE activating a set of transmission configuration indicator (TCI) states prior to a cell switching operation for a candidate cell, wherein a separate field in the MAC CE enables the TA acquisition procedure for the candidate cell.

18. The method of claim 17, wherein the UE is configured to derive the TA value of the candidate cell based on the TA value of the serving cell and a downlink receive timing difference (RTD) between the serving cell and the candidate cell in response to the MAC CE activating the TCI state of the candidate cell.

19. The method of claim 13, wherein a cell handover command (CSC) triggering a cell handover to a candidate non-serving cell enables the TA acquisition procedure for the candidate non-serving cell.

20. A method comprising: receiving configuration data at a user equipment (UE), the configuration data specifying triggering conditions for the UE to update a timing advance (TA) value of a candidate cell for L1 / L2 triggered mobility (LTM) operation; as well as The TA value of the candidate cell is updated by the UE and based on the configuration data.

21. The method of claim 20, wherein the configuration data is transmitted to the UE based on radio resource control (RRC) signaling, wherein the configuration data specifies a TA update timer, and wherein the UE is configured to update the TA value of the candidate cell when the TA update timer expires.

22. The method of claim 20, wherein a set of timing accuracy requirements are predefined in a specification, and wherein the UE updates the TA value to meet the predefined timing accuracy requirements independently of receiving the configuration data.

23. The method of claim 20, wherein the configuration data is transmitted to the UE based on a downlink control information (DCI) format.

24. The method of claim 23, wherein the DCI format comprises a plurality of fields for a common UE, wherein each of the plurality of fields specifies a TA update value indicating whether the common UE is triggered to update the TA value of a corresponding candidate cell.

25. The method according to claim 24, wherein a field index of the TA update value of the corresponding candidate non-serving cell is configured based on RRC signaling.

26. The method of claim 24, wherein the TA update value for each corresponding candidate cell is associated based on an order of the fields in the DCI format, wherein the TA values ​​of the plurality of fields are assigned to respective candidate cells based on respective cell indexes of the candidate cells.

27. The method of claim 23, wherein the DCI format comprises a plurality of fields, wherein each of the plurality of fields specifies a corresponding candidate cell index for a respective different UE.

28. The method of claim 12, wherein a medium access control (MAC) control element (CE) is configured to activate or deactivate a TA acquisition procedure based on received signal received power (RSRP) associated with different candidate non-serving cells of the UE.

29. The method of claim 28, wherein the MAC CE comprises a plurality of index fields, each index field being associated with a candidate cell index, and wherein a given index field C i The value indicates the pair with the given index field C i Activation or deactivation of the candidate cell associated with the candidate index.

30. The method of claim 28, wherein the MAC CE has a fixed size.

31. A system, comprising one or more computers and one or more storage devices, wherein the one or more storage devices store operable instructions, which, when executed by the one or more computers, cause the one or more computers to perform the operations of any one of the methods according to claims 1 to 30.

32. A non-transitory computer storage medium encoded with instructions that, when executed by one or more computers, cause the one or more computers to perform the operations of any of the methods of claims 1 to 30.

33. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving, at a user equipment (UE), configuration data from a wireless communication network, the configuration data specifying one or more prioritization rules for the UE to transmit to a serving cell or a candidate cell in the wireless communication network, the one or more prioritization rules specifying transmission priorities for the first transmission and the second transmission when the UE is scheduled to perform a first transmission on a serving cell including a physical data or control channel and a second transmission on a candidate non-serving cell including a physical random access channel (PRACH), and the first transmission and the second transmission overlap in time; and The first transmission, the second transmission, or both the first transmission and the second transmission are transmitted by the UE according to the one or more prioritization rules.

34. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving, at a user equipment (UE), configuration data specifying a timing advance (TA) acquisition procedure for the UE in a L1 / L2 triggered mobility (LTM) scenario; and Uplink (UL) data is transmitted to a target cell, the transmission being based on a TA value determined by the UE based on the TA acquisition procedure specified by the configuration data.

35. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving configuration data at a user equipment (UE), the configuration data specifying triggering conditions for the UE to update a timing advance (TA) value of a candidate cell for L1 / L2 triggered mobility (LTM) operation; and The TA value of the candidate cell is updated by the UE and based on the configuration data.

Images