Conditions for determining the number of DL reference timings in single-DCI multi-TRP scenarios with two tas

Abstract

A method includes monitoring, by a user equipment (UE) configured for a first uplink (UL) transmission and a second uplink transmission, a first downlink (DL) reference timing. The UE determines whether a condition indicating that a second downlink reference timing is to be monitored is satisfied, and monitors the second downlink reference timing based upon the condition being satisfied.

Description

CONDITIONS FOR DETERMINING THE NUMBER OF DL REFERENCE TIMINGS IN SINGLE-DCI MULTI-TRP SCENARIOS WITH TWO TASFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for a method and apparatus for recommended bit rate support for extended reality (XR).BACKGROUND

[0002] In a single-downlink control information (DCI) multi-transmission reception point (TRP) case, the TRP (e.g., TRP2) that does not send a physical downlink control channel (PDCCH) to a user equipment (UE) may still send some DL signals (e.g., synchronization signal blocks (SSBs)).SUMMARY

[0003] In an aspect of the present disclosure, a method includes monitoring, by a user equipment (UE) configured for a first uplink (UL) transmission and a second uplink transmission, a first downlink (DL) reference timing. The UE determines whether a condition indicating that a second downlink reference timing is to be monitored is satisfied, and monitors the second downlink reference timing based upon the condition being satisfied.

[0004] In an aspect of the method, the first uplink transmission is associated with a first transmission configuration (TCI) state.

[0005] In an aspect of the method, the first TCI state is associated with a first timing advance group (TAG).

[0006] In an aspect of the method, the second uplink transmission is associate with a second TCI state.

[0007] In an aspect of the method, the second TCI state is associated with a second timing advance group.

[0008] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes no separate UL or no joint DL / UL TCI state configured, activated or indicated at the UE to which a pathloss offset is associated.

[0009] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes no bandwidth part (BWP) or no component carrier (CC) configured with two separate sounding reference signal (SRS) closed loop power control (CLPC) adjustment states.

[0010] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes at least one reference signal (RS) being measured by the UE is from a transmission reception point (TRP) for the second transmission.

[0011] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes at least one RS from one TRP for the second transmission being configured as a path loss RS (PLRS).

[0012] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes at least one configured TCI state is associated with a source DL RS for at least one TRP for the second transmission.

[0013] In an aspect of the method, the at least one configured TCI state is a separate DL or separate UL or joint DL / UL TCI.

[0014] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes at least two separate DL TCI states being configured or activated or indicated with different TAG IDs.

[0015] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving an indication for a PDCCH order PRACH or contention- free random access towards another non-collocated TRP that has a DL transmission.

[0016] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes a list of configured or activated TCI states containing at least one codepoint with two joint DL / UL TCI states that are associated to two TAG IDs containing DL RS signals as quasi co location (QCL-D) sources.

[0017] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes at least one configured or activated or indicated separate UL TCI state having a second TAG ID that contains a DL RS as QCL source.

[0018] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving information indicative of a scenario withoutUL-only node / TRP or indicative that there is no active TRP corresponding to at least one UL-only TRP / node.

[0019] In an aspect of the method, the condition indicating that a second downlink reference timing is to be monitored includes the UE being configured or activated or indicated with no UL or no joint DL / UL TCI state for which the source reference signal corresponds to an UL reference signal.

[0020] In an aspect of the method, the condition indicating that a second downlink reference timing is not to be monitored includes at least one separate UL or joint DL / UL TCI state being configured or activated or indicated at the UE to which a PL offset is associated.

[0021] In an aspect of the method, the condition indicating that a second downlink reference timing is not to be monitored includes all separate DL TCI states being configured or activated or indicated with the same TAG ID.

[0022] In an aspect of the method, the condition indicating that a second downlink reference timing is not to be monitored includes the UE receiving information indicative of a scenario with UL-only node / TRP or indicative that there is at least one active TRP corresponding to at least one UL-only TRP / node.

[0023] In an aspect of the present disclosure, a UE includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform any of the foregoing methods.

[0024] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0025] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Some example embodiments will now be described with reference to the accompanying drawings.

[0027] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0028] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0029] FIG. 3 is a flow diagram of an example method of bit rate support, according to one illustrated aspect of the disclosure;

[0030] FIG. 4 is a flow diagram of an example method of bit rate support in a PL offset case, according to one illustrated aspect of the disclosure;

[0031] FIG. 5 is a flow diagram of an example method of bit rate support in a number of separate DL states, according to one illustrated aspect of the disclosure; and

[0032] FIG. 6 is a diagram of an example block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node), according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0033] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0034] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0035] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution(LTE), LTE- Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0036] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0037] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0038] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5GNR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0039] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0040] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0041] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0042] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0043] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0044] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en- gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit. In various embodiments, multiple TRPs may be included in each of a cell.

[0045] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DUrelated functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0046] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O- RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0047] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0048] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 6. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0049] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100.As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0050] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0051] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0052] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0053] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SME) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a networkexposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0054] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0055] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0056] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0057] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0058] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0059] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in theproviding of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0060] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0061] As mentioned above, in a single-downlink control information (DCI) multitransmission reception point (TRP) case, the TRP (e.g., TRP2) that does not send a physical downlink control channel (PDCCH) to a user equipment (UE) may still send some DL signals (e.g., synchronization signal blocks (SSBs)). In such a deployment with TRP2 being also capable of DL, the UE may monitor two DL reference timings, one per TRP / timing advance group (TAG). In the case of a TRP2 not being capable of DL, the term UL-only TRP is also used to refer to such TRP2, and in this deployment the UE may monitor just one DL reference timing.

[0062] Accordingly, described herein is a method and apparatus for a single-DCI multi-TRP scenario with two TAs, defining conditions for UE behavior to determine how many DL reference timings the UE has to monitor for setting the uplink (UL) transmission timings.

[0063] In various embodiments, if at least one of the conditions (defined herein) are met, then the UE monitors at least two DL reference timings, one per TAG, and applies, for example, TAI and TA2 to DL reference timing 1 and 2, respectively for setting the UL transmission timings. If none of the conditions are met, then the UE monitors at least one DL reference timing, which will be used for both TAGs and applies TAI and TA2 to such single DL reference timing for setting the UL transmission timings. For example, in an embodiment, the UE needs to check only one condition. In another embodiment, the UE needs to check all the conditions. In another embodiment, the UE needs to check only a subset K of all the conditions.

[0064] In accordance with the brief description, FIG. 3 is a flow diagram of an example method 300 of bit rate support, according to one illustrated aspect of the disclosure. In various embodiments, method 300 may be implemented in a UE that is in communication with a networkapparatus, such as a gNB, base station, or other network device. In various embodiments, the UE is configured with a separate downlink (DL) transmission configuration indicator (TCI) state (TCI#1) associated to TAG1 and one separate uplink (UL) TC state (TCI#2) associated to TAG1, and with a separate UL TCI state (TCI#3) associated to TAG2.

[0065] At block 310, the UE monitors a first DL reference signal (RS). In various embodiments, for example, the UE monitors a DL reference timing for TAG1 (e.g., a first TAG).

[0066] At block 320, the UE determines whether or not a condition is satisfied for monitoring a second DL reference signal.

[0067] In various embodiments, the conditions may include any one or more of the following: There is no separate UL or joint DL / UL TCI state configured or activated or indicated at the UE to which a Rel-19 introduced pathloss (PL) offset is associated. In various embodiments, this an implicit way for the UE to know that there is no UL-only TRP serving that UE.There is no bandwidth part (BWP) / component carrier (CC) for which two separate sounding reference signal (SRS) closed loop power control (CLPC) adjustments states are configured, e.g., via RRC, at the UE. In various embodiments, this is an implicit way for the UE to know there is no UL-only TRP serving that UE.At least one RS is measured by the UE from TRP2, for example in a last predefined time window.At least one RS from TRP2 is configured as PL-RS.There is at least one configured TCI state (separate DL or separate UL or joint DL / UL) with a source DL RS from TRP2.At least two separate DL TCI states are configured or activated or indicated with different TAG IDs. In various embodiments, the UE may be receiving data from two TRPs belonging to different TAGs.The UE receives the indication for a PDCCH order physical random access channel (PRACH) or contention-free random access towards another non-collocated TRP that has the DL transmission.The list of configured or activated TCI states contains at least one codepoint with 2 joint DL / UL TCI states (that are associated to the two TAG IDs) containing DL RS signals as QCL-D sources.There is at least one configured or activated or indicated separate UL TCI state with the second TAG ID that contains a DL RS as quasi co-located (QCL) source.The UE receives information indicative of a scenario without UL-only node / TRP or indicative that there is no (active) TRP corresponding to at least one UL-only TRP / node, where such information may be signaled through RRC, MAC control element (CE), or DCI.The UE is configured or activated or indicated with no separate UL or joint DL / UL TCI state for which the source reference signal corresponds to an UL reference signal(s).

[0068] In various embodiments, for intra-cell signaling, dedicated signaling may be utilized, for example in the cell configuration to indicate which SSBs are transmitted by which TRPs in that cell.

[0069] In various embodiments, “symmetric” conditions may be considered. For example, if at least one of such “symmetric” conditions is met, then the UE is required to monitor at least one DL reference timing, otherwise if none is met the UE is required to monitor at least two DL reference timings. For example, symmetric conditions may include any one or more of the following:There is at least one separate UL or joint DL / UL TCI state configured or activated or indicated at the UE to which the Rel-19 introduced PL offset is associated.All the separate DL TCI states are configured or activated or indicated with the same TAG ID.The UE receives information indicative of a scenario with UL-only node / TRP or indicative that there is at least one (active) TRP corresponding to at least one UL-only TRP / node, where such information may be signaled through RRC, MAC CE, or DCI.

[0070] Accordingly, at block 320, if one or more of the above conditions is not met, the method 300 reverts to block 310. However, if one or more of the above conditions is met at block 320, then at block 330, the UE monitors the second downlink reference signal. In various embodiments, the UE monitors a downlink reference timing for TAG2 (e.g., a second TAG). Additionally, the UE continues monitoring the first DL RS.

[0071] The blocks / operations of FIG. 3 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the blocks / operations may include other blocks / operations not illustrated in FIG. 3. In embodiments, the blocks / operations may not include every block / operation illustrated in FIG.3. In embodiments, the blocks / operations may be implemented in a different order than that illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 3.

[0072] FIG. 4 is a flow diagram of an example method 400 of bit rate support in a PL offset case, according to one illustrated aspect of the disclosure. In various embodiments, method 400 may be implemented in a UE that is in communication with a network apparatus, such as a gNB, base station, or other network device.

[0073] At block 410, a serving cell includes two TRPs associated to two different TAGs and a UE is capable of two TAs. For example, the UE is capable of the two TAs feature, and a single cell, (e.g., intra-cell, single-DCI scenario with two TRPs associated to two different TAGs (TAG1 for TRP1 and TAG2 for TRP2)).

[0074] At block 420, the UE is configured with one separate DL TCI state (TCI#1) associated to TAG1 and one separate UL TCI state (TCI#2) associated to TAG1. That is, the UE is initially configured with one separate DL TCI state, TCI#1, for DL transmission from a TRP in TAG1, being TRP1 in this example, and one separate UL TCI state, TCI#2, for UL transmission toward a TRP in TAG1.

[0075] At block 430, the UE is required to monitor at least one DL reference timing for TAG1. For example, as only one UL TCI state is configured, and as a consequence activated / indicated, the UE receives only one timing advance command (TAC), (i.e., TAI), and the UE is required to monitor just one DL reference timing (for TAG1).

[0076] At block 440, the UE is further configured with one separate UL TCI state (TCI#3) associated to TAG2.

[0077] Accordingly, at block 450, the UE determines if there is a PL offset associated with TCI#3.

[0078] If a PL offset is associated with TCI#3, at block 460, the UE determines that the TRP in TAG2 is an uplink only TRP, and the UE is not required to monitor any DL reference timing for TAG2. That is, the UE assesses the UL transmission using TCI#3 as being toward an UL-only TRP in TAG2, which, for example, is TRP2, and the UE does not need to monitor any additional DL reference timing.

[0079] If there is not a PL offset associated with TCI#3, at block 470, the UE determines that the TRP in TAG2 is not an uplink only TRP, and the UE is required to monitor a DL reference timing also for TAG2. That is, the UE assesses the UL transmission using TCI#3 being toward a TRP in TAG2, (e.g., TRP2), which is not UL-only, and the UE is required to monitor an additional DL reference signal for timing for TAG2. In various embodiments, the additional DL reference signal for timing for TAG2 is one of the DL reference signals of one of the separate DL TCI states having the same TAG as the uplink signal.

[0080] The blocks / operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the blocks / operations may include other blocks / operations not illustrated in FIG. 4. In embodiments, the blocks / operations may not include every block / operation illustrated in FIG. 4. In embodiments, the blocks / operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[0081] FIG. 5 is a flow diagram of an example method 500 of bit rate support in a number of separate DL states, according to one illustrated aspect of the disclosure. In various embodiments, method 500 may be implemented in a UE that is in communication with a network apparatus, such as a gNB, base station, or other network device.

[0082] At block 510, a serving cell includes two TRPs associated to two different TAGs and a UE is capable of two TAs. For example, the UE is capable of the two TAs feature, and a single cell, (e.g., intra-cell, single-DCI scenario with two TRPs associated to two different TAGs (TAG1 for TRP1 and TAG2 for TRP2)).

[0083] At block 520, the UE is configured with one separate DL TCI state (TCI#1) associated to TAG1 and one separate UL TCI state (TCI#2) associated to TAG1. That is, the UE is initially configured with one separate DL TCI state, TCI#1, for DL transmission from a TRP in TAG1, being TRP1 in this example, and one separate UL TCI state, TCI#2, for UL transmission toward a TRP in TAG1.

[0084] At block 530, the UE is required to monitor at least one DL reference timing for TAG1. For example, as only one UL TCI state is configured, and as a consequence activated / indicated,the UE receives only one TAC, (i.e., TAI), and the UE is required to monitor just one DL reference timing (for TAG1).

[0085] At block 540, the UE is further configured with one separate UL TCI state (TCI#3) associated to TAG2.

[0086] At block 550, the UE is further configured with one separate DL TCI state (TCI#4) associated to TAG2.

[0087] At block 560, the UE determines if TCI#4 is associated with TAG1.

[0088] If TCI#4 is associated with TAG1, then at block 570, the UE determines that the TRP in TAG2 is an uplink only TRP and the UE is not required to monitor any DL reference timing for TAG2.

[0089] If TCI#4 is not associated with TAG1, then the UE determines that the TRP in TAG2 is not an uplink only TRP, and the UE is required to monitor a DL reference timing also for TAG2.

[0090] The blocks / operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the blocks / operations may include other blocks / operations not illustrated in FIG. 5. In embodiments, the blocks / operations may not include every block / operation illustrated in FIG. 5. In embodiments, the blocks / operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 5.

[0091] In various embodiments, the UE detects the receive time difference between different reference signals. If the UE measures that the time difference exceeds a threshold, the UE identifies that both two TRPs contain DL signals. Once this is identified, the UE groups the list of identified reference signals.

[0092] In other various embodiments, the UE monitors the variation of the receive time for the reference signals. In the case where the reference signals are coming from the same TRP, they will experience the same clock drift and propagation delay variation, and the UE groups the list of reference signals with similar clock drift and propagation delays, and identifies which RS belong to which TRP.

[0093] The following describes operations from the perspective of a UE. From such a perspective, a method includes monitoring, by the UE configured for a first uplink (UL)transmission and a second uplink transmission, a first downlink (DL) reference timing, determining, by the UE, whether a condition indicating that a second downlink reference timing is to be monitored is satisfied, and monitoring, by the UE, the second downlink reference timing based upon the condition being satisfied.

[0094] FIG. 6 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 600, according to one illustrated aspect of the present disclosure. The wireless station 600 may include, for example, one or more (e.g., two as shown in FIG. 6) RF (radio frequency) or wireless transceivers 602A, 602B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 604 to execute instructions or software and control transmission and receptions of signals, and a memory 606 to store data and / or instructions.

[0095] Processor 604 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 604, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 602 (602A or 602B). Processor 604 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 602, for example). Processor 604 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 604 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 604 and transceiver 602 together may be considered as a wireless transmitter / receiver system, for example.

[0096] In addition, referring to FIG. 6, a controller (or processor) 608 may execute software and instructions, and may provide overall control for the station 600, and may provide control for other systems not shown in FIG. 6, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 600, such as, for example, an email program, audio / video applications, a word processor, a Voiceover IP application, or other application or software.

[0097] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 604, or other controller or processor, performing one or more of the functions or tasks described above.

[0098] According to another example embodiment, RF or wireless transceiver(s) 602A / 602B may receive signals or data and / or transmit or send signals or data. Processor 604 (and possibly transceivers 602A / 602B) may control the RF or wireless transceiver 602A or 602B to receive, send, broadcast or transmit signals or data.

[0099] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 600, FIG. 6) including means (e.g., processor 604, RF transceivers 602A and / or 602B, and / or memory 606, in FIG. 6) for carrying out any of the methods; a non- transitory computer-readable storage medium (e.g., memory 606, FIG. 6) comprising instructions stored thereon that, when executed by at least one processor (processor 604, FIG. 6), are configured to cause a computing system (e.g., 600, FIG. 6) to perform any of the example methods; and an apparatus (e.g., 600, FIG. 6) including at least one processor (e.g., processor 604, FIG. 6), and at least one memory (e.g., memory 606, FIG. 6) including computer program code, the at least one memory (606) and the computer program code configured to, with the at least one processor (604), cause the apparatus (e.g., 600) at least to perform any of the example methods.

[0100] Further embodiments of the present disclosure include the following examples.

[0101] Example 1.1. A user equipment (UE), comprising: means for monitoring, by a user equipment (UE) configured for a first uplink (UL) transmission and a second uplink transmission, a first downlink (DL) reference timing; means for determining, by the UE, whether a condition indicating that a second downlink reference timing is to be monitored is satisfied; and means for monitoring, by the UE, the second downlink reference timing based upon the condition being satisfied.

[0102] Example 1.2. The UE of example 1.1, wherein the first uplink transmission is associated with a first transmission configuration (TCI) state.

[0103] Example 1.3. The UE of example 1.2, wherein the first TCI state is associated with a first timing advance group (TAG).

[0104] Example 1.4. The UE of any one of examples 1.1 to 1.3 , wherein the second uplinktransmission is associate with a second TCI state.

[0105] Example 1.5. The UE of claim 1.4, wherein the second TCI state is associated with a second timing advance group.

[0106] Example 1.6. The UE of any one of examples 1.1 to 1.5, wherein the condition indicating that a second downlink reference timing is to be monitored includes no separate UL or no joint DL / UL TCI state configured, activated or indicated at the UE to which a pathloss offset is associated.

[0107] Example 1.7. The UE of any one of examples 1.1 to 1.6, wherein the condition indicating that a second downlink reference timing is to be monitored includes no bandwidth part (BWP) or no component carrier (CC) configured with two separate sounding reference signal (SRS) closed loop power control (CLPC) adjustment states.

[0108] Example 1.8. The UE of any one of examples 1.1 to 1.7, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one reference signal (RS) being measured by the UE is from a transmission reception point (TRP) for the second transmission.

[0109] Example 1.9. The UE of any one of examples 1.1 to 1.8, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one RS from one TRP for the second transmission being configured as a path loss RS (PLRS).

[0110] Example 1.10. The UE of any one of examples 1.1 to 1.9, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one configured TCI state is associated with a source DL RS for at least one TRP for the second transmission.

[0111] Example 1.11. The UE of example 1.10, wherein the at least one configured TCI state is a separate DL or separate UL or joint DL / UL TCI.

[0112] Example 1.12. The UE of any one of examples 1.1 to 1.11, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least two separate DL TCI states being configured or activated or indicated with different TAG IDs.

[0113] Example 1.13. The UE of any one of examples 1.1 to 1.12, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving an indication for a PDCCH order PRACH or contention- free random access towards another noncollocated TRP that has a DL transmission.

[0114] Example 1.14. The UE of any one of examples 1.1 to 1.13, wherein the condition indicating that a second downlink reference timing is to be monitored includes a list of configured or activated TCI states containing at least one codepoint with two joint DL / UL TCI states that are associated to two TAG IDs containing DL RS signals as quasi co location (QCL-D) sources.

[0115] Example 1.15. The UE of any one of examples 1.1 to 1.14, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one configured or activated or indicated separate UL TCI state having a second TAG ID that contains a DL RS as QCL source.

[0116] Example 1.16. The UE of any one of examples 1.1 to 1.15, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving information indicative of a scenario without UL-only node / TRP or indicative that there is no active TRP corresponding to at least one UL-only TRP / node.

[0117] Example 1.17. The UE of any one of examples 1.1 to 1.16, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE being configured or activated or indicated with no UL or no joint DL / UL TCI state for which the source reference signal corresponds to an UL reference signal.

[0118] Example 1.18. The UE of any one of examples 1.1 to 1.17, wherein the condition indicating that a second downlink reference timing is not to be monitored includes at least one separate UL or joint DL / UL TCI state being configured or activated or indicated at the UE to which a PL offset is associated.

[0119] Example 1.19. The UE of any one of examples 1.1 to 1.18, wherein the condition indicating that a second downlink reference timing is not to be monitored includes all separate DL TCI states being configured or activated or indicated with the same TAG ID.

[0120] Example 1.20. The UE of any one of examples 1.1 to 1.19, wherein the condition indicating that a second downlink reference timing is not to be monitored includes the UE receiving information indicative of a scenario with UL-only node / TRP or indicative that there is at least one active TRP corresponding to at least one UL-only TRP / node.

[0121] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed hereinare not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0122] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0123] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[0124] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[0125] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta- languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0126] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosurebe as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising: monitoring, by a user equipment (UE) configured for a first uplink (UL) transmission and a second uplink transmission, a first downlink (DL) reference timing; determining, by the UE, whether a condition indicating that a second downlink reference timing is to be monitored is satisfied; and monitoring, by the UE, the second downlink reference timing based upon the condition being satisfied.

2. The method of claim 1, wherein the first uplink transmission is associated with a first transmission configuration (TCI) state.

3. The method of claim 2, wherein the first TCI state is associated with a first timing advance group (TAG).

4. The method of any one of claims 1 to 3, wherein the second uplink transmission is associate with a second TCI state.

5. The method of claim 4, wherein the second TCI state is associated with a second timing advance group.

6. The method of any one of claims 1 to 5, wherein the condition indicating that a second downlink reference timing is to be monitored includes no separate UL or no joint DL / UL TCI state configured, activated or indicated at the UE to which a pathloss offset is associated.

7. The method of any one of claims 1 to 6, wherein the condition indicating that a second downlink reference timing is to be monitored includes no bandwidth part (BWP) or no component carrier (CC) configured with two separate sounding reference signal (SRS) closed loop power control (CLPC) adjustment states.

228. The method of any one of claims 1 to 7, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one reference signal (RS) being measured by the UE is from a transmission reception point (TRP) for the second transmission.

9. The method of any one of claims 1 to 8, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one RS from one TRP for the second transmission being configured as a path loss RS (PLRS).

10. The method of any one of claims 1 to 9, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one configured TCI state is associated with a source DL RS for at least one TRP for the second transmission.

11. The method of claim 10, wherein the at least one configured TCI state is a separate DL or separate UL or joint DL / UL TCI.

12. The method of any one of claims 1 to 11, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least two separate DL TCI states being configured or activated or indicated with different TAG IDs.

13. The method of any one of claims 1 to 12, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving an indication for a PDCCH order PRACH or contention-free random access towards another non-collocated TRP that has a DL transmission.

14. The method of any one of claims 1 to 13, wherein the condition indicating that a second downlink reference timing is to be monitored includes a list of configured or activated TCI states containing at least one codepoint with two joint DL / UL TCI states that are associated to two TAG IDs containing DL RS signals as quasi co location (QCL-D) sources.

15. The method of any one of claims 1 to 14, wherein the condition indicating that a second downlink reference timing is to be monitored includes at least one configured or activated or indicated separate UL TCI state having a second TAG ID that contains a DL RS as QCL source.

16. The method of any one of claims 1 to 15, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE receiving information indicative of a scenario without UL-only node / TRP or indicative that there is no active TRP corresponding to at least one UL-only TRP / node.

17. The method of any one of claims 1 to 16, wherein the condition indicating that a second downlink reference timing is to be monitored includes the UE being configured or activated or indicated with no UL or no joint DL / UL TCI state for which the source reference signal corresponds to an UL reference signal.

18. The method of any one of claims 1 to 17, wherein the condition indicating that a second downlink reference timing is not to be monitored includes at least one separate UL or joint DL / UL TCI state being configured or activated or indicated at the UE to which a PL offset is associated.

19. The method of any one of claims 1 to 18, wherein the condition indicating that a second downlink reference timing is not to be monitored includes all separate DL TCI states being configured or activated or indicated with the same TAG ID.

20. The method of any one of claims 1 to 19, wherein the condition indicating that a second downlink reference timing is not to be monitored includes the UE receiving information indicative of a scenario with UL-only node / TRP or indicative that there is at least one active TRP corresponding to at least one UL-only TRP / node.

21. A user equipment (UE), comprising: at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform a method as in any one of claims 1 to 20.

22. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1 to 20.25

Images