Method and apparatus for implementing dual timing advance in wireless communications

Abstract

A wireless communication network provides an integrated communication platform and telecommunications services to wireless user equipment. Example telecommunications services include telephony, data (e.g., voice, audio and / or video data), messaging, and / or other services. A wireless communication network has wireless access nodes that exchange wireless signals with wireless user equipment using a wireless network protocol, such as a protocol 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 fifth generation new radio (5G NR). A wireless communication network facilitates mobile broadband services using techniques such as OFDM, multiple input multiple output (MIMO), advanced channel coding, massive MIMO, beamforming, and / or other features.

Description

Background Technology

[0001] 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, 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. Summary of the Invention

[0002] This disclosure describes methods and systems for latency reduction in user equipment (UE) for inter-cell mobility. According to one aspect of this disclosure, a method includes receiving configuration data at the UE specifying that a random access response (RAR) window begins at a Type 1 Physical Downlink Control Channel (PDCCH) monitoring opportunity (MO), wherein the time interval between Physical Random Access Channel (PRACH) transmissions. The method also includes transmitting PRACH transmissions based on the configuration data.

[0003] In some specific implementations of this method, the length of the RAR window allows for RAR forwarding from the target cell to the serving cell.

[0004] In some specific implementations of this method, the configuration data is provided based on Radio Resource Control (RRC) signaling.

[0005] In some specific implementations of this method, the configuration data specifies the number of symbols for the Type 1 PDCCH Public Search Space (CSS).

[0006] In another aspect of this disclosure, a method includes receiving a Random Access Response (RAR) at a User Equipment (UE), the RAR including configuration data specifying a Timing Advance Group (TAG) identifier (TAG-ID) indicating at least two candidate cells and a corresponding Timing Advance (TA) value for each of the at least two candidate cells. The method additionally includes transmitting uplink data to the at least one candidate cell based on the TA value of the at least one candidate cell indicated by the TAG-ID.

[0007] In some specific implementations, the method includes receiving data at the user equipment (UE) indicating a timing advance group identity (TAG-ID) configured as a timing advance value for applying a random access response (RAR); and receiving data at the UE at a single RAR media access control-control element (MAC-CE) indicating one or more media access control-control elements (MAC-CEs) indicating two or more timing advances (TAs) for two or more candidate cells.

[0008] In some implementations, the method continues to receive data at the User Equipment (UE) indicating a Timing Advance Group Identity (TAG-ID), which is configured as a timing advance value for the application Random Access Response (RAR). In response to receiving the TAG-ID, the method includes receiving data at the UE with the instruction to divide one or more CORESET groups into distinct groups using the TAG-ID associated with each CORESET group in one or more Control Resource Sets (CORESET) groups.

[0009] In another aspect of this disclosure, a method includes receiving at a user equipment (UE) data indicating a timing advance group (TAG) indication that determines a TAG identity (TAG-ID) for applying a timing advance value to a random access response (RAR). The method further includes receiving at the UE data via DCI format 1_0 indicating at least one of a target candidate cell's TAG-ID, physical cell ID, or dedicated logical ID, the DCI format 1_0 having a cyclic redundancy check (CRC) scrambled with a random access radio network temporary identifier (RA-RNTI) or a CRC scrambled with a MsgB-RNTI.

[0010] In some aspects, one method includes receiving at the user equipment (UE) data indicating a timing advance group (TAG) indication that determines a TAG identity (TAG-ID) for applying a timing advance value to a random access response (RAR). The method also includes receiving at the UE data an UL grant field or a temporary C-RNTI field, i.e., data indicating an enhanced RAR MAC configured to indicate at least one of a candidate cell's TAG identity (TAG-ID), a physical cell ID, or a logical ID.

[0011] In another aspect of this disclosure, the method disclosed herein includes transmitting data from a user equipment (UE) instructing the transmission of a physical random access channel (PRACH). Additionally, the method includes, at the UE and in response to the PRACH transmission, receiving a media access control (MAC) control element (CE) including a timing advance (TA) command, the MAC CE further specifying the timing advance group identity (TAG-ID) or physical cell ID of the cell.

[0012] In some specific embodiments of this disclosure, MAC CE is received based on downlink control information (DCI) format 1_0 with cyclic redundancy check (CRC).

[0013] In some implementations, the CRC is scrambled by the Cell Radio Network Temporary Identifier (C-RNTI) during the Random Access Response (RAR) window.

[0014] In some specific implementations, the method continues to receive at the UE data indicating a Media Access Control Protocol Data Unit (MAC PDU) scheduled by DCI format 1_0, wherein the MAC PDU includes an Enhanced Absolute Timing Advance (TA) command associated with a Target Candidate Cell or Target Transmit / Receive Point (TRP) and a Media Access Control-Control Element (MAC-CE).

[0015] In some aspects of this disclosure, a method includes a base station transmitting data indicating an indication via one or more Radio Resource Control (RRC) parameters. This indication has a first set of Physical Random Access Channel (PRACH) resources and a second set of PRACH resources for a User Equipment (UE), the first set of PRACH resources specifying a first Timing Advance (TA) for the UE, and the second set of PRACH resources specifying a second TA for the UE. Furthermore, the method includes the base station obtaining data indicating the Timing Advance (TA) of a Transmit / Receive Point (TRP).

[0016] In some specific implementations, the first group of PRACH resources includes a first synchronization signal block (SSB) group and a second SSB group, wherein the grouping configuration of the SSBs is provided through one or more of the system information block (SIB) messages or radio resource control (RRC) messages.

[0017] In some specific embodiments of this disclosure, the first set of PRACH resources includes a first set of preambles, and the second set of PRACH resources includes a second set of preambles.

[0018] In at least one aspect of this disclosure, a method continues to transmit data by a cell indicating physical radio access channel (PRACH) resources, wherein the PRACH resources comprise a first group and a second group. The method also includes obtaining data by the cell indicating a tracking area (TA) of a transmit / receive point (TRP).

[0019] In another aspect of this disclosure, a processor of a user equipment (UE) is configured to perform operations including: receiving configuration data at the UE specifying that the random access response (RAR) window begins at the first symbol of the earliest Type 1 physical downlink control channel (PDCCH) monitoring moment (MO), wherein the time interval between the physical random access channel (PRACH) transmission and the earlier Type 1 PDCCH MO is at least This includes sending PRACH data based on the configuration data. It also includes monitoring each type 1 PDCCH MO within the RAR window specified by the configuration to perform RAR reception in response to the PRACH transmission.

[0020] Another aspect of this disclosure relates to a processor for a user equipment (UE) configured to perform operations including: receiving a random access response (RAR) at the UE, the RAR including configuration data specifying a timing advance group (TAG) identifier (TAG-ID) indicating at least two candidate cells and a corresponding timing advance (TA) value for the TAG identified by the TAG-ID. These operations include transmitting uplink data to at least one candidate cell among the candidate cells associated with the TAG-ID based on the TA value of the TAG corresponding to the TAG-ID.

[0021] In another aspect, this disclosure describes a processor for a user equipment (UE) configured to perform operations including: receiving at the UE data indicating a timing advance group identity (TAG-ID) of a candidate cell to indicate a timing advance value transmitted over the uplink on the candidate cell. These operations also include receiving at the UE data via DCI format 1_0 indicating at least one of a TAG-ID, a physical cell ID, or a dedicated logical ID of a target candidate cell, the DCI format 1_0 having a cyclic redundancy check (CRC) scrambled by a random access radio network temporary identifier (RA-RNTI) or a CRC scrambled by a MsgB-RNTI, wherein the DCI format 1_0 includes a field indicating the TAG-ID, physical cell ID, or dedicated logical ID of the target candidate cell.

[0022] Another aspect of this disclosure describes a processor for a user equipment (UE) configured to perform operations including: receiving data at the UE indicating a timing advance group (TAG) of a candidate cell to apply a timing advance value for a random access response (RAR). These operations include receiving at the UE an enhanced RAR MAC that reuses a UL grant field or a temporary C-RNTI field to indicate at least one of the candidate cell's TAG identity (TAG-ID), physical cell ID, or logical ID.

[0023] Another aspect of this disclosure describes a processor for a user equipment (UE) configured to perform operations including: transmitting data from the UE instructing a physical random access channel (PRACH) to transmit, and receiving at the UE, and in response to the PRACH, a media access control (MAC) control element (CE) including a timing advance (TA) command, the MAC CE further specifying a timing advance group identity (TAG-ID) or physical cell ID of a candidate cell to apply a TA value indicated by the TA command of the MAC CE.

[0024] At least one aspect of this disclosure describes a processor for a base station configured to perform operations including: transmitting data indicating an indication via one or more Radio Resource Control (RRC) parameters, the indication having a first set of Physical Random Access Channel (PRACH) resources and a second set of PRACH resources for a User Equipment (UE), the first set of PRACH resources being used to obtain a first timing advance (TA) associated with a first TAG-ID for the UE, and the second set of PRACH resources being used to obtain a second TA associated with a second TAG-ID for the UE. These operations include the base station obtaining data indicating a timing advance (TA) for a Transmit / Receive Point (TRP).

[0025] Another aspect of this disclosure describes a processor for a cell configured to perform operations including: transmitting data by the cell indicating a Physical Radio Access Channel (PRACH) resource configuration, wherein the PRACH resources indicated by the configuration include a first set of PRACH resources and a second set of PRACH resources. These operations include obtaining data by the cell indicating a Tracking Area (TA) of a Transmit / Receive Point (TRP).

[0026] In some specific embodiments of this disclosure, a non-transitory computer storage medium is provided with instructions that, when executed by one or more computers, cause the one or more computers to perform any of the methods described above.

[0027] In some specific implementations, a system includes one or more processors and one or more storage devices storing instructions that, when executed by the one or more processors, are operable to cause the one or more processors to perform any of the methods described above.

[0028] 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, the figures, and the claims. Attached Figure Description

[0029] Figure 1 Examples of wireless networks based on some specific implementations are shown.

[0030] Figure 2 A schematic diagram illustrating a user equipment (UE) receiving transmissions from a serving cell is shown. The user equipment (UE) is configured to transmit information to one or more candidate cells.

[0031] Figure 3 Examples are shown in Figure 2 The diagram shows the RAR window received at the UE, which is configured to specify the timing advance group identifier (TAG-ID).

[0032] Figure 4 A schematic diagram of a UE header is shown, which indicates a RAR that is configured to indicate a given TA of an associated candidate cell.

[0033] Figure 5 The diagram shows a UE header with multiple blocks configured to support multiple TAs for more than one candidate cell.

[0034] Figure 6 A schematic diagram illustrating multiple CORESET groups with corresponding TAG-IDs is shown.

[0035] Figure 7 The example shows the UE header of the TA command, which is used to indicate the TAG-ID.

[0036] Figure 8 Examples are shown for use in Figure 2 The process 800 shows the RACH procedure at the UE to obtain one or more TAs.

[0037] Figures 9A to 9B A schematic diagram illustrates a mechanism for enabling two TAs for intra-cell multiple transmit / receive point (mTRP) transmission.

[0038] Figure 10 The flowchart illustrates example methods based on some specific implementations.

[0039] Figure 11 The flowchart illustrates example methods based on some specific implementations.

[0040] Figure 12 The flowchart illustrates example methods based on some specific implementations.

[0041] Figure 13 The flowchart illustrates example methods based on some specific implementations.

[0042] Figure 14 The flowchart illustrates example methods based on some specific implementations.

[0043] Figure 15 The flowchart illustrates example methods based on some specific implementations.

[0044] Figure 16 The flowchart illustrates example methods based on some specific implementations.

[0045] Figure 17 Example user equipment (UE) based on some specific implementations are illustrated.

[0046] Figure 18 Example access nodes are shown according to some specific implementations. Detailed Implementation

[0047] This disclosure describes methods and systems for latency reduction in User Equipment (UE) for inter-cell mobility. New mobile services requiring low latency and high reliability performance (e.g., URLLC) are emerging. In current NR designs, Physical Radio Access Channel (PRACH) reception and Random Access Response (RAR) transmission are performed by a single gnodeB (gNB). One aspect of this disclosure describes uplink timing enhancements, specifying methods and systems for: Layer 1 (L1) / Layer 2 (L2) based inter-cell mobility (LTM) with reduced mobility latency, and timing advance management in Radio Layer 1 (RAN1) and Radio Layer 2 (RAN2).

[0048] [Inventor—Red text is background and can be skipped during review.]

[0049] Figure 1 A wireless network 100 according to some specific implementation is illustrated. The wireless network 100 includes a UE 102 and a base station 104 connected via one or more channels 106A, 106B across an air interface 108. The UE 102 and the base station 104 communicate using a system that supports control for managing the UE 102's access to the network via the base station 104.

[0050] In some implementations, Wireless Network 100 may be a non-standalone (NSA) network combining Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards as defined by the 3rd Generation Partnership Project (3GPP) technical specifications. For example, 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, Wireless Network 100 may be a standalone (SA) network combining only 5G NR. In addition, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)), IEEE 802.11 technologies (e.g., IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11ac; or other currently or future IEEE 802.11 technologies), IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.). While this document may use terminology commonly associated with 5G NR to describe the aspects, the aspects of this disclosure can be applied to other systems, such as 3G, 4G, and / or systems beyond 5G (e.g., 6G).

[0051] In wireless network 100, UE 102 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. In network 100, base station 104 provides UE 102 with network connectivity to a wider network (not shown). This UE 102 connectivity is provided via air interface 108 within the base station service area provided by base station 104. 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 104 is supported by one or more antennas integrated with 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 physical areas with one or more tunable antennas or antenna configurations that can be adjusted during beamforming to direct signals to a specific sector.

[0052] UE 102 includes control circuitry 110 coupled to transmitting circuitry 112 and receiving circuitry 114. Transmitting circuitry 112 and receiving circuitry 114 may each be coupled to one or more antennas. Control circuitry 110 may include various combinations of dedicated circuitry and baseband circuitry. Transmitting circuitry 112 and receiving 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.

[0053] In various specific implementations, aspects of the transmitting circuit 112, receiving circuit 114, and control circuit 110 may be integrated in various ways to achieve the operations described herein. Control circuit 110 may be adapted to or configured to perform various operations, such as those UE-related operations described elsewhere in this disclosure. For example, control circuit 110 may perform each of the receiving operations described above with respect to the method, such as receiving configuration data at the user equipment (UE) at which a specified random access response (RAR) window begins at a Type 1 physical downlink control channel (PDCCH) monitoring moment (MO).

[0054] Transmitting circuit 112 can perform various operations described in this specification. For example, transmitting circuit 112 can perform any of the above-described transmission operations, including transmitting uplink data to at least one candidate cell among candidate cells indicated by TAG-ID and based on the TA value of at least one candidate cell. Additionally, transmitting circuit 112 can use multiple multiplexed uplink physical channels for transmission. The multiple uplink physical channels can be multiplexed, for example, according to time division multiplexing (TDM) or frequency division multiplexing (FDM) and carrier aggregation. Transmitting circuit 112 can be configured to receive block data from control circuit 110 for transmission across air interface 108.

[0055] Receiver circuit 114 can perform various operations described in this specification. For example, receiver circuit 114 can perform any of the above-described receiving operations, including receiving a Random Access Response (RAR) at the User Equipment (UE), the RAR including configuration data specifying a Timing Advance Group (TAG) identifier (TAG-ID) indicating at least two candidate cells and a corresponding Timing Advance (TA) value for each of the at least two candidate cells. Additionally, receiver circuit 114 can receive multiple multiplexed downlink physical channels from air interface 108 and relay these physical channels to control circuit 110. The multiple downlink physical channels can be multiplexed, for example, according to TDM or FDM and carrier aggregation. Transmitter circuit 112 and receiver circuit 114 can respectively transmit and receive control data and content data (e.g., messages, images, videos, etc.) structured within data blocks carried by the physical channels.

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

[0057] The base station 104 circuitry may include control circuitry 116 coupled to transmitting circuitry 118 and receiving circuitry 120. Transmitting circuitry 118 and receiving circuitry 120 may each be coupled to one or more antennas, which may be used for communication via air interface 108. Transmitting circuitry 118 and receiving circuitry 120 may be adapted to transmit and receive data to and from any UE connected to base station 104. Receiving circuitry 120 may receive multiple uplink physical channels from one or more UEs, including UE 102.

[0058] exist Figure 1 In this implementation, one or more channels 106A and 106B are exemplified as air interfaces for communication coupling and may conform to cellular communication protocols such as UMTS, 3GPP LTE, LTE-A, LTE-based Unlicensed Spectrum Access (LTE-U), 5G, NR, NR-based Unlicensed Spectrum Access (NR-U), and / or any other communication protocol. In a specific implementation, 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 the Physical Sidelink Control Channel (PSCCH), Physical Sidelink Discovery Channel (PSDCH), and Physical Sidelink Broadcast Channel (PSBCH).

[0059] Figure 2 A schematic diagram illustrating a User Equipment (UE) 200 receiving transmissions from a serving cell is shown. This UE is configured to transmit information to one or more candidate cells. For example, UE 200 receives configuration data specifying a Random Access Response (RAR) window, which advantageously reduces UE power consumption during Type 1 Physical Downlink Control Channel (PDCCH) Monitoring Occasion (MO).

[0060] Figure 3A schematic diagram of a RAR window 300 received at UE 200 is illustrated, which is configured to specify a timing advance group identifier (TAG-ID). When RAR window 300 is configured for a contention-free random access (CFRA) procedure for a candidate cell (e.g., candidate cell 204 or candidate cell 206), UE 200 attempts to detect DCI format 1_0 once a random access preamble is sent toward the target candidate cell. DCI format 1_0 includes a cyclic redundancy check (CRC) scrambled by a cell radio network temporary identifier (C-RNTI) during the random access response (RAR) window from serving cell 202.

[0061] In some specific implementations, RAR window 300 begins at position 302, which is the first symbol of an earlier CORESET in the Type 1 PDCCH Common Search Channel (CSS) set configured for monitoring, which is at least k B The symbol, millisecond, or time slot 302. In some older systems, the PRACH is received by the target gNB at UE 200, and the corresponding RAR is forwarded to the serving gNB via the backhaul link, which can take tens of milliseconds to complete. In contrast, according to various aspects of this disclosure, k is provided via Radio Resource Control (RRC) signaling. B The number of symbols or time slots 302 is used to account for the backhaul delay caused by RAR / TA forwarding from the target cell (e.g., candidate cells 204, 206) to the serving cell 202. Assuming the periodicity of the Type 1 PDCCH CSS is approximately 20ms, in at least one example, k B =10ms. In response to receiving a PDCCH command from serving cell 202 at UE 200, PRACH is sent to one or more candidate cells 204, 206. Furthermore, the time interval 306 between the reception of PRACH at UE 200 and the next Type 1 PDCCH MO is less than the previous k. B , making k B =5ms. According to this specific implementation, the RAR window begins at position 304 after the PRACH is received, such that the RAR window begins at position 304 at type 1 PDCCH MO 130. The time gap 306 after the PRACH reception at UE 200 is sufficient for RAR forwarding from the target cell to the serving cell 202.

[0062] Advantageously, UE 200 does not need to monitor MO position 180 because the RAR window starts at position 304 at MO position 130. Therefore, UE 200 consumes less power during transmission, thus reducing the overall power requirement of UE 200. Furthermore, configuring UE 200 as described above reduces UE power consumption for Type 1 CSS monitoring because the monitoring timing takes into account backhaul forwarding delays across two gNBs (e.g., candidate cells 204, 206). Another advantage is that one or more parallel RACH procedures can be triggered for different candidate cells to minimize signaling overhead and TA acquisition latency.

[0063] This disclosure describes how to indicate the expected TAG ID and / or candidate cell associated with RAR reception at UE 200. In one example, a UE-specific search space is used instead of specifying a common search space to reduce latency. Advantageously, in the current PDCCH command CFRA process, the RAR is sent by the NW in response to PRACH reception. To date, RAR has only been scheduled in Type 1CSS and cannot be scheduled using a UE-specific search space, which potentially increases RAR scheduling latency. Furthermore, RAR consists of a considerable number of IEs unrelated to LTM (Local Service Manager) operation, such as a 27-bit UL grant and a 16-bit C-RNTI. For LTM designs, minimizing RAR signaling overhead and latency needs to be considered.

[0064] According to other aspects of this disclosure, the timing advance group identity (ID) is used for the TA value of the applied RAR. The RRC signal may indicate the TAG-ID of each of one or more candidate cells 204, 206. In one implementation, a single RACH procedure is maintained at UE 200. If a new random access (RA) procedure is triggered at UE 200, and another random access (RA) procedure is already in progress in the MAC entity, UE 200 determines whether to continue the existing RAR procedure or continue the new RAR procedure. In response, UE 200 assumes that the RAR is associated with the RACH procedure maintained by UE 200.

[0065] Figure 4A schematic diagram of header 400 is illustrated, indicating a RAR configured to indicate a given TA of an associated candidate cell (such as one of candidate cells 204, 206). One or more time slots 402 indicate any of the TAG-ID, physical cell ID, or dedicated logical ID of one of the candidate cells 204, 206. Each TAG-ID, physical cell ID, or dedicated logical ID is transmitted by UE 200 using DCI format 1_0 with a CRC scrambled by RA-RNTI or MsgB-RNTI. UE 200 can utilize the RAR MAC to indicate the TAG-ID or physical cell ID (or logical ID) of the candidate cell by utilizing the “UL Grant” field or the “Temporary C-RNTI” field.

[0066] Figure 5 A UE header 500 with multiple blocks 504 is shown, which are configured to support multiple TAs for more than one candidate cell among candidate cells 204, 206. Each candidate cell among the more than one candidate cell 204, 206 can be in a single RAR MAC PDU. The multiple blocks 504 can have 1 to N blocks 502, where 'N' is a real number, an integer, and is indicated by the MAC-CE subheader. Each block 502 within the multiple blocks 504 includes a logical ID 506 and a TA value 508. The logical ID 506 can be either a configuration ID or a TAG-ID associated with one of the candidate cells 204, 206. As described above, and as... Figure 2 As shown, in response to the PDCCH command received at UE 200, candidate cells 204 and 206 are triggered by PRACH transmission.

[0067] Figure 6 A schematic diagram illustrating multiple CORESET groups 600 with corresponding TAG-ID 506 is shown. In some implementations, Radio Resource Control (RRC) signaling can be used to divide CORESETs into unique groups 602. Each group 602 can be associated with a logical ID 506. Therefore, in some implementations, each group 602 and its corresponding CORESET are associated with a given TAG-ID, such as... Figure 6 As shown. If UE 200 receives a Radio Access Response (RAR) Physical Downlink Shared Channel (PDSCH) scheduled by a CORESET with a CORESET group index value, UE 200 assumes that the TAG-ID associated with that CORESET group index has been updated by the scheduled RAR.

[0068] Figure 7A header 700 for a TA command indicating a TAG-ID is illustrated. In some examples, the TA command may be MAC-CE. According to various aspects of this disclosure, a CFRA procedure is introduced for two TAs in multiple downlink control information (mDCI) multiple transmit / receive point (mTRP) transmission. Header 700 specifies the 'R' field 702 for the TAG-ID or logical ID for candidate cells 204, 206. The TA command MAC-CE is identified by a MAC subheader with a dedicated extended logical channel ID (eLCID), which is a hard-coded specification. The eLCID has a fixed size, for example, two octets.

[0069] Figure 8 A procedure 800 for obtaining one or more TAs at UE 200 is illustrated. Procedure 800 provides a generally enhanced CFRA procedure for obtaining the TA of a target TRP / cell. Procedure 800 includes at least two operations. In a first operation, in response to a PRACH transmission from the UE to the target gNb, the UE generates a signal to detect a DCI format 1_0 with a CRC scrambled by a C-RNTI during a RAR window controlled by the NW. In a second operation, a MAC PDU scheduled by DCI format 1_0 includes a TA command MAC-CE associated with the target candidate cell or target TRP. In some implementations, the TA command MAC-CE can be received via the serving gNb. In one implementation, if only one RACH procedure is maintained, the TA command MAC-CE is used, and the TA command MAC-CE is therefore scheduled by a C-RNTI received at the UE from the serving gNb from any search space. In some specific implementations, the UE can be UE 200, the serving gNb can be serving cell 202, and the target gNb can be either candidate cell 204 or 206, such as... Figure 2 As shown.

[0070] Figures 9A to 9BA schematic diagram illustrating a mechanism for enabling two TAs for intra-cell multiple transmit / receive point (mTRP) transmission is provided. According to certain aspects of this disclosure, for an intra-cell multiple transmit / receive point (mTRP) scenario, the disclosed subject matter supports a contention-based RACH (CBRA) procedure to obtain the TA for the second TRP. In a first embodiment, the SSBs indicated by ssb-PositionsInBurst can be divided into two distinct groups, for example, Synchronization Signal Block (SSB) group 1 and SSB group 2. SSB group configuration can be provided via SIB information or UE-specific RRC messages. For the intra-cell CBRA procedure, UE 200 selects the PRACH resource associated with an SSB in SSB group 'k', which is different from an SSB group that includes SSBs associated with an active TCI state. In the first embodiment, Figure 9A As depicted, the four SSBs are divided into two groups, with group 1 comprising SSBs {1, 6} and group 2 comprising SSBs {2, 8}. The SSB groups are based on information provided by the SIB or dedicated RRC signaling.

[0071] In the second implementation, PRACH resources can be divided into two groups, for example, Group 1 and Group 2. In some implementations, a parameter, such as 'sizeofRA-Group1', can be introduced for each PRACH resource timing (RO). For example, each preamble in Group 1 includes a range of preamble 0, i.e., preamble 0 to a specified size, for example, the parameter 'sizeofRA-Group1'. The remaining preambles are associated with Group 2. The UE is explicitly configured by an RRC that specifies which PRACH group (e.g., Group 1 or Group 2) is used for the CBRA procedure to obtain the second TA. In some implementations, there can be a total of 20 preambles in the RO. For example, in the second implementation, these 20 preambles are divided into two groups (e.g., Group 1, Group 2), and sizeofRA-Group1 is set to '12'. Therefore, Group 1 will include preambles {0~11}, and the remaining preambles are in Group 2.

[0072] Figure 10 A flowchart illustrating an example method 1000 according to some specific implementation is provided. For clarity, the following description generally describes method 1000 within the context of other figures in this specification. For example, method 1000 may be derived from... Figure 2 UE 200 execution.

[0073] Figure 11 A flowchart illustrating an example method 1100 according to some specific implementation is shown. For clarity, the following description generally describes method 1000 within the context of the other figures in this specification. For example, method 1100 may be derived from... Figure 2 The method is executed by UE 200. Method 1100 includes operations 1102, 1104, 1106, and 1108. In some specific implementations, the method continues at operation 1106 to receive data at the user equipment (UE) indicating a timing advance group identity (TAG-ID), which is configured as a timing advance value for applying a random access response (RAR). At operation 1108, method 1100 may continue at operation 1108 to receive data at the UE at a single RAR media access control-control element indicating one or more media access control-control elements (MAC-CE), which indicate two or more timing advances (TAs) for two or more candidate cells. Alternatively, at operation 1108, method 1100 may continue to receive data at the UE in response to receiving a TAG-ID, which includes instructions to divide one or more CORESET groups into distinct groups using a TAG-ID associated with each CORESET group in one or more control resource sets (CORESET) groups.

[0074] Figure 12 A flowchart illustrating an example method 1200 according to some specific implementation is provided. For clarity, the following description generally describes method 1000 within the context of the other figures in this specification. For example, method 1200, including operations 1202 and 1204, can be described by… Figure 2 UE 200 execution.

[0075] Figure 13 A flowchart illustrating an example method 1300 according to some specific implementation is shown. For clarity, the following description generally describes method 1000 within the context of other figures in this specification. For example, method 1300, including operations 1302 and 1304, can be described by… Figure 2 UE 200 execution.

[0076] Figure 14 A flowchart illustrating an example method 1400 according to some specific implementation is shown. For clarity, the following description generally describes method 1000 within the context of the other figures in this specification. For example, method 1400 may be derived from... Figure 2 The UE 200 performs the procedure. Method 1400 may include operations 1402, 1404, 1406, 1408, and 1410. In some specific implementations of method 1400 (e.g., operation 1406), the MAC CE is received based on downlink control information (DCI) format 1_0 with cyclic redundancy check (CRC).

[0077] In another embodiment of method 1400, during the Random Access Response (RAR) window, the CRC is scrambled using the Cell Radio Network Temporary Identifier (C-RNTI) (e.g., operation 1408). In yet another embodiment, method 1400 may continue to receive data at the UE indicating a Media Access Control Protocol Data Unit (MAC PDU) scheduled by DCI format 1_0 (e.g., operation 1410), where the MAC PDU includes an Enhanced Absolute Timing Advance (TA) command associated with the Target Candidate Cell or Target Transmit / Receive Point (TRP), and a Media Access Control-Control Element (MAC-CE).

[0078] Figure 15 A flowchart illustrating an example method 1500 according to some specific implementation is shown. For clarity, the following description generally describes method 1000 within the context of other figures in this specification. For example, method 1500, including operations 1502 and 1504, can be described by… Figure 2 The serving cell 202 or candidate cells 204, 206 shown are executed. In some embodiments of method 1500, the first set of PRACH resources includes a first synchronization signal block (SSB) group and a second SSB group, wherein the packet configuration of the SSBs is provided by one or more of System Information Block (SIB) information or Radio Resource Control (RRC) messages. In another embodiment of method 1500, the first set of PRACH resources includes a first preamble, and wherein the second set of PRACH resources includes a second preamble.

[0079] Figure 16 A flowchart illustrating an example method 1600 according to some specific implementation is shown. For clarity, the following description generally describes method 1600 within the context of other figures in this specification. For example, method 1600, including operations 1602 and 1604, can be described by… Figure 2 The serving cell 202 or candidate cells 204 and 206 shown are executed.

[0080] It should be understood that each of methods 1000 to 1600 can be performed individually or in combination, for example, by any suitable system, environment, software, hardware, or combination of system, environment, software, and hardware, as appropriate. In some specific implementations, the various steps of method 1000 can be run in parallel, in combination, in cycles, or in any order.

[0081] [Inventor—The red part is background and can be skipped.]

[0082] Figure 17 Example UE 1700 is illustrated according to some specific implementations. UE 1700 may be similar to Figure 1The UE 102 is essentially interchangeable with it.

[0083] UE 1700 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.

[0084] UE 1700 may include a processor 1702, RF interface circuitry 1704, memory / storage device 1706, user interface 1708, sensor 1710, drive circuitry 1712, power management integrated circuit (PMIC) 1714, one or more antennas 1716, and battery 1718. Components of UE 1700 may be implemented as integrated circuits (ICs), portions of such integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 17 The block diagram is intended to show a high-level view of some of the components of the UE 1700. 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.

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

[0086] Processor 1702 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 1722A, central processing unit circuitry (CPU) 1722B, and graphics processing unit circuitry (GPU) 1722C. Processor 1702 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional procedures from memory / storage device 1706) to cause UE 1700 to perform the operations described herein.

[0087] In some implementations, the baseband processor circuit 1722A can access the communication protocol stack 1724 in the memory / storage device 1706 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1722A 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 1704. The baseband processor circuit 1722A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant 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.

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

[0089] RF interface circuitry 1704 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 1700 to communicate with other devices via a radio access network. RF interface circuitry 1704 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.

[0090] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna 1716 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 1702.

[0091] 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 1716. In various specific implementations, the RF interface circuitry 1704 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0092] Antenna 1716 may include one or more antenna elements to convert electrical signals into radio waves for travel 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 1716 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output (MIMO) communication. Antenna 1716 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1716 may have one or more panels designed for a specific frequency band including the frequency bands in FR1 or FR2.

[0093] User interface 1708 includes various input / output (I / O) devices designed to enable users to interact with UE 1700. User interface 1708 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, keypad, mouse, touchpad, touchscreen, microphone, scanner, or headset, etc. 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 1700.

[0094] Sensor 1710 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information (sensor data) about the detected events 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 aperture devices); 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; etc.

[0095] The driving circuitry 1712 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the UE 1700. The driving circuitry 1712 may include individual 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 1700. For example, the driving circuitry 1712 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 acquiring sensor readings of sensor 1710 and controlling and allowing access to sensor 1710, an actuator positioning for acquiring electromechanical components or a driver for 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.

[0096] The PMIC 1714 manages the power supplied to various components of the UE 1700. Specifically, relative to the processor 1702, the PMIC 1714 controls power source selection, voltage scaling, battery charging, or DC-DC conversion.

[0097] In some implementations, the PMIC 1714 can control various power-saving mechanisms of the UE 1700, or otherwise become part of these power-saving mechanisms. The battery 1718 can power the UE 1700, but in some examples, the UE 1700 can be installed and deployed in a fixed location and may have a power source coupled to the grid. The battery 1718 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 1718 can be a typical lead-acid automotive battery.

[0098] Figure 18An example access node 1800 (e.g., a base station or gNB) is illustrated according to some specific implementations. Access node 1800 may be similar to and substantially interchangeable with base station 104. Access node 1800 may include processor 1802, RF interface circuitry 1804, core network (CN) interface circuitry 1806, memory / storage device circuitry 1808, and one or more antennas 1810.

[0099] Components of access node 1800 can be coupled to various other components via one or more interconnects 1812. Processor 1802, RF interface circuitry 1804, memory / storage device circuitry 1808 (including communication protocol stack 1814), antenna 1810, and interconnects 1812 can be similar to those relative to... Figure 17 Similar named components are shown and described. For example, processor 1802 may include processor circuitry such as, for example, baseband processor circuitry (BB) 1816A, central processing unit circuitry (CPU) 1816B, and graphics processing unit circuitry (GPU) 1816C.

[0100] The CN interface circuit 1806 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 1800 via fiber optic or wireless backhaul. The CN interface circuit 1806 may include one or more dedicated processors or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1806 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0101] 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, NodeB, 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 1800 (e.g., a gNB) operating in an NR or 5G system, and the terms "E-UTRAN node," etc., can refer to an access node 1800 (e.g., an eNB) operating in an LTE or 4G system. Depending on various specific implementations, the access node 1800 can be implemented as one or more of the following: dedicated physical equipment such as a macro cell 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 macro cell, such as a femtocell, picocell, or other similar cell.

[0102] In some specific implementations, all or part of the access node 1800 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 1800 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 stationed (or relatively stationed) therein, 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.

[0103] 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 USC § 172(f) for that component.

[0104] For one or more embodiments, at least one component 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 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 embodiments described in the Embodiments section below.

[0105] A system (e.g., a base station, a device including one or more baseband processors, etc.) may be configured to perform a specific operation or action by means of software, firmware, hardware, or a combination thereof installed on the system that causes the system to perform actions in operation. The operation or action performed by the system may include the method according to any one of embodiments 1 to 6.

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

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

[0108] As described above, one aspect of this technology may involve collecting and using data that is available from specific and lawful sources to allow interaction with a second device for data transfer. This disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other personal information.

[0109] This disclosure recognizes that the use of such personal information data in the present invention can benefit users. For example, personal information data can be used to provide secure data transfer between a first device and a second device. Personal information data can also be used to identify accounts associated with users from service providers to complete data transfers.

[0110] This disclosure anticipates that entities responsible for collecting, analyzing, disclosing, transferring, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, it is expected that such entities will implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or governmental requirements for protecting user privacy. Such information regarding the use of personal data should be highlighted and easily accessible to users, and should be updated as data collection and / or use change. Users' personal information should be collected only for lawful use. Furthermore, such collection / sharing should only occur after receiving user consent or other lawful grounds provided for in applicable law. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to personal information data comply with their privacy policies and procedures. Furthermore, such entities may be subject to third-party assessments to demonstrate their compliance with widely accepted privacy policies and privacy measures. Moreover, policies and practices should be tailored to the specific types of personal information data collected and / or accessed, and made applicable to applicable laws and standards, including jurisdiction-specific considerations applicable to applying higher standards. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0111] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, the technology of this invention can be configured to allow users to opt-in or opt-out to participate in the collection of personal information data during or at any time after registering for the service. For example, users can opt-in or opt-out to information associated with a user account stored on and / or shared by the user device. In addition to providing opt-in and opt-out options, this disclosure also contemplates providing notifications related to access to or use of personal information. For example, users can be notified when downloading an application that their personal information data will be accessed, and then reminded again before the personal information data is accessed by the application. In some instances, users can be notified when a device accesses information associated with a user's account and / or when a data transfer of information associated with that user's account is initiated and shared with another device.

[0112] Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by restricting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods (such as differentiated privacy).

[0113] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not become inoperable due to the absence of all or part of such personal information data. For example, content can be selected and delivered to the user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that can be used for content delivery services.

Claims

1. A method comprising: Receiving, at a user equipment (UE), configuration data specifying that a random access response (RAR) window starts at a first symbol of an earliest Type 1 physical downlink control channel (PDCCH) monitoring occasion (MO), wherein a time gap between a physical random access channel (PRACH) transmission and the earlier Type 1 PDCCH MO is at least one symbol or slot or millisecond; transmitting the PRACH transmission based on the configuration data; and monitoring each Type 1 PDCCH MO within the RAR window specified by the configuration for RAR reception in response to the PRACH transmission.

2. The method of claim 1, wherein a gap of length of one symbol or slot or millisecond between a PRACH transmission and an associated RAR window is determined based on a RAR forwarding latency from a target candidate cell to a serving cell. 1 3. The method of claim 1, wherein the configuration data is provided based on radio resource control (RRC) signaling.

4. The method of claim 1, wherein the configuration data specifies a gap of a length of a number of symbols or slots or milliseconds between the PRACH transmission and an earliest Type 1 PDCCH common search space (CSS) within the RAR window.

1. A method for wireless communications by a user equipment (UE), comprising: receiving a configuration of a physical random access channel (PRACH) transmission and a random access response (RAR) window; and transmitting a PRACH transmission in the PRACH transmission configuration, wherein the PRACH transmission is associated with a gap of a length of a number of symbols or slots or milliseconds between the PRACH transmission and an earliest Type 1 P​ 5. A method comprising: receiving, at a user equipment (UE), a random access response (RAR) comprising configuration data specifying timing advance group (TAG) identifiers (TAG-IDs) indicating at least two candidate cells and respective timing advance (TA) values for the TAGs identified by the TAG-IDs; transmitting, based on the TA value for the TAG corresponding to the TAG-ID, uplink data to at least one of the candidate cells associated with the TAG-ID.

6. The method of claim 5, comprising: receiving, at the user equipment (UE), data indicating timing advance group identities (TAG-IDs) of candidate cells to indicate timing advance values for uplink transmissions on the candidate cells; and receiving, at the UE, data indicating one or more medium access control-control elements (MAC-CEs) in a single RAR protocol data unit (PDU), wherein each MAC-CE indicates a timing advance (TA) and an associated TAG-ID.

7. The method of claim 5, comprising: receiving, at the user equipment (UE), data indicating timing advance group identities (TAG-IDs) of candidate cells to indicate timing advance values for uplink transmissions on the candidate cells; and receiving, at the UE, data having instructions to partition one or more control resource sets (CORESETs) into different groups; and receiving, at the user equipment (UE), data indicating associations between TAG-IDs and CORESET groups; and receiving a RAR PDU scheduled by a downlink control information (DCI) format from a CORESET; and determining a TAG-ID associated with the TA value in a RAR PDU based on the CORESET group of the CORESET in which the DCI is detected.

8. A method comprising: receiving, at a user equipment (UE), data indicating timing advance group identities (TAG-IDs) of candidate cells to indicate timing advance values for uplink transmissions on the candidate cells; and receiving, at a user equipment (UE), data indicating at least one of a timing advance group (TAG) or a physical cell ID or a logical ID of a candidate cell to apply a timing advance value of a random access response (RAR); and receiving, at the UE, an enhanced RAR MAC reusing a UL grant field or a temporary C-RNTI field to indicate at least one of a TAG identity (TAG-ID) or a physical cell ID or a logical ID of a candidate cell.

10. A method comprising: sending, from a user equipment (UE), data indicating a physical random access channel (PRACH) transmission; and receiving, at the UE and in response to the PRACH transmission, a medium access control (MAC) control element (CE) including a timing advance (TA) command, the MAC CE further specifying a TAG identity (TAG-ID) or a physical cell ID of a candidate cell to apply a TA value indicated by the TA command of the MAC-CE.

11. The method of claim 10, wherein the MAC CE is scheduled by a downlink control information (DCI) format 1 0 with a cyclic redundancy check (CRC).

12. The method of claim 11, wherein CRC bits of DCI format 1 0 are scrambled by a cell radio network temporary identifier (C-RNTI) during a random access response (RAR) window.

13. The method of claim 10, comprising: receiving, at the UE, data indicating a medium access control protocol data unit (MAC PDU) scheduled by a DCI format 1 0, wherein the MAC PDU includes an enhanced absolute timing advance (TA) command medium access control-control element (MAC-CE) including an information field indicating the TAG-ID or a logical ID associated with a target candidate cell or a target transmission / reception point (TRP).

14. A method comprising: ​ ​ transmitting, by a base station, data indicating an indication having a first set of physical random access channel (PRACH) resources for a user equipment (UE) and a second set of PRACH resources, the first set of PRACH resources for obtaining a first timing advance (TA) associated with a first TAG-ID for the UE and the second set of PRACH resources for obtaining a second TA associated with a second TAG-ID for the UE; and obtaining, by the base station, data indicating a timing advance (TA) of a transmission / reception point (TRP).

15. The method of claim 14, wherein the first set of PRACH resources is associated with a first synchronization signal block (SSB) group and a second set of PRACH resources is associated with a second SSB group, wherein SSB grouping configuration is provided by one or more of system information block (SIB) information or radio resource control (RRC) messages.

16. The method of claim 14, wherein the first set of PRACH resources comprises a first set of preambles and wherein the second set of PRACH resources comprises a second set of preambles.

17. A method comprising: transmitting, by a cell, data indicating a physical random access channel (PRACH) resource configuration, wherein the PRACH resources indicated by the configuration comprise a first set of PRACH resources and a second set of PRACH resources; and obtaining, by the cell, data indicating a tracking area (TA) of a transmission / reception point (TRP).

18. 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 method of any of claims 1-17.

19. A system comprising one or more processors and one or more storage devices having stored thereon instructions that, when executed by the one or more processors, are operable to cause the one or more processors to perform the method of any of claims 1-17.

20. A processor of a user equipment (UE), the processor configured to perform operations comprising: Receiving configuration data at the user equipment (UE) that specifies that a random access response (RAR) window starts at a first symbol of an earliest Type 1 physical downlink control channel (PDCCH) monitoring occasion (MO), where a time gap between a physical random access channel (PRACH) transmission and an earlier Type 1 PDCCH MO is at least one symbol or slot or millisecond; transmitting the PRACH transmission based on the configuration data; and monitoring each type 1 PDCCH MO within the RAR window specified by the configuration for RAR reception in response to the PRACH transmission.

21. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving, at the user equipment (UE), a random access response (RAR), the RAR comprising configuration data specifying timing advance group (TAG) identifiers (TAG-IDs) indicating at least two candidate cells and respective timing advance (TA) values of the TAGs identified by the TAG-IDs; transmit uplink data to at least one of the candidate cells associated with the TAG-ID based on the TA value of the TAG corresponding to the TAG-ID.

22. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving, at the user equipment (UE), data indicating a timing advance group identity (TAG-ID) of a candidate cell to indicate a timing advance value for uplink transmissions on the candidate cell; and receiving, at the UE, data indicating at least one of a TAG-ID, a physical cell ID, or a dedicated logical ID of a target candidate cell via a DCI format 1 0 with a cyclic redundancy check (CRC) scrambled by a random access radio network temporary identifier (RA-RNTI) or with the CRC scrambled by a MsgB-RNTI, wherein the DCI format 1 0 includes one field indicating the TAG-ID or the physical cell ID or the dedicated logical ID of the target candidate cell.

23. A processor of a user equipment (UE), the processor configured to perform operations comprising: receiving, at the user equipment (UE), data indicating a timing advance group (TAG) of a candidate cell to apply a timing advance value for a random access response (RAR); and receiving, at the UE, an enhanced RAR MAC reusing a UL grant field or a temporary C-RNTI field to indicate at least one of a TAG identity (TAG-ID) or a physical cell ID or a logical ID of a candidate cell.

24. A processor of a user equipment (UE), the processor configured to perform operations comprising: transmitting, from the user equipment (UE), data indicating a physical random access channel (PRACH) transmission; and receiving, at the UE and in response to the PRACH transmission, a medium access control (MAC) control element (CE) including a timing advance (TA) command, the MAC CE further specifying a timing advance group identity (TAG-ID) or a physical cell ID of a candidate cell to apply a TA value indicated by the TA command of the MAC-CE.

25. A processor of a base station, the processor configured to perform operations comprising: transmitting, by a base station, data indicating an indication by one or more radio resource control (RRC) parameters, the indication having a first set of physical random access channel (PRACH) resources for a user equipment (UE) and a second set of PRACH resources, the first set of PRACH resources for obtaining a first timing advance (TA) associated with a first TAG-ID for the UE and the second set of PRACH resources for obtaining a second TA associated with a second TAG-ID for the UE; and obtaining, by the base station, data indicating a timing advance (TA) of a transmission / reception point (TRP).

26. A processor of a cell, the processor configured to perform operations comprising: transmit, by the cell, data indicating a physical radio access channel (PRACH) resource configuration, wherein the PRACH resources indicated by the configuration include a first set of PRACH resources and a second set of PRACH resources; and obtain, by the cell, data indicating a tracking area (TA) of a transmission / reception point (TRP).

Images