Dynamic power sharing in communication networks

Abstract

Technologies and techniques for wireless communications in a dual connectivity wireless communications network are disclosed. A first uplink timing value for control information to a first cell group is determined. A second uplink timing value for control information to a second cell group is determined. Transmit power for first and second uplink communications may be determined and allocated. A timing offset value is determined relative to the second timing value and transmitted to the wireless communications network. Scheduling information is received in response to transmitting the timing offset value, and at least one of the first uplink communication or the second uplink communication is transmitted based on the scheduling information.

Description

Technical Field

[0001] The techniques discussed below relate generally to wireless communication networks, and more particularly to techniques for providing improved power sharing under dual connectivity requirements.

[0002] introduction

[0003] In wireless communication systems, such as those specified under the standards for 5G New Radio (NR), access points (e.g., base stations) can communicate with user equipment (UEs) (e.g., smartphones). Dual connectivity is an operating mode in which a UE equipped with multiple receivers and transmitters can be configured to utilize radio resources of two different schedulers located in two radio base stations (eNBs) configured as a primary eNB and a secondary eNB connected via a non-ideal backhaul over an X2 interface. In a 5G NR configuration, a UE can connect to a long term evolution (LTE) base station and a 5G NR base station, each of which can be configured as a primary node or a secondary node. In some configurations, a UE can access LTE and 5G NR simultaneously.

[0004] As the demand for mobile broadband access and communications continues to grow, research and development continues to advance wireless communication technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance mobile communications. Accordingly, the present disclosure addresses technologies and techniques to improve power sharing in a dual connectivity operating environment.

[0005] A brief overview of some examples

[0006] An overview of one or more aspects of the present disclosure is given below to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all conceived features of the present disclosure, and is neither intended to identify the key or decisive elements of all aspects of the present disclosure nor to attempt to define the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a form as a preface to a more detailed description given later.

[0007] In one example, a method for power sharing by scheduled entities in a wireless communication network is disclosed, the method comprising: determining a first timing value for a first uplink communication, the first uplink communication including first control information to a first cell group; determining a second timing value for a second uplink communication, the second uplink communication including second control information to a second cell group; allocating transmit power for the first uplink communication and the second uplink communication; determining a timing offset value relative to the second timing value; transmitting the timing offset value to the wireless communication network; receiving scheduling information in response to transmitting the timing offset value; and transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information.

[0008] In another example, a user equipment (UE) within a wireless communication network is disclosed, the UE comprising a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: determine a first timing value for a first uplink communication, the first uplink communication comprising first control information to a first cell group; determine a second timing value for a second uplink communication, the second uplink communication comprising second control information to a second cell group; allocate transmit power for the first uplink communication and the second uplink communication; determine a timing offset value relative to the second timing value; transmit the timing offset value to the wireless communication network; receive scheduling information in response to transmitting the timing offset value; and transmit at least one of the first uplink communication or the second uplink communication based on the scheduling information.

[0009] In another example, a user equipment (UE) in a wireless communication network is disclosed, the UE comprising: a device for determining a first timing value for a first uplink communication, the first uplink communication including first control information to a first cellular cell group; a device for determining a second timing value for a second uplink communication, the second uplink communication including second control information to a second cellular cell group; a device for allocating transmit power for the first uplink communication and the second uplink communication; a device for determining a timing offset value relative to the second timing value; a device for transmitting the timing offset value to the wireless communication network; a device for receiving scheduling information in response to transmitting the timing offset value; and a device for transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information.

[0010] In another example, a computer-readable medium having instructions stored therein is disclosed, the instructions being executable by one or more processors to determine a first timing value for a first uplink communication, the first uplink communication including first control information to a first cell group; determine a second timing value for a second uplink communication, the second uplink communication including second control information to a second cell group; allocate transmit power for the first and second uplink communications; determine a timing offset value relative to the second timing value; transmit the timing offset value to the wireless communication network; receive scheduling information in response to transmitting the timing offset value; and transmit at least one of the first uplink communication or the second uplink communication based on the scheduling information.

[0011] These and other aspects of the present invention will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features and embodiments of the present invention will be apparent to those of ordinary skill in the art. Although features of the present invention may be discussed below with respect to certain embodiments and drawings, all embodiments of the present invention may include one or more advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments may be discussed below as device, system or method embodiments, it should be appreciated that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a schematic illustration of a wireless communication system according to some aspects;

[0014] Figure 2 is a conceptual illustration of an example radio access network according to some aspects;

[0015] Figure 3 is a diagram illustrating organization of wireless resources in an air interface using orthogonal frequency division multiplexing (OFDM) according to some aspects;

[0016] Figure 4 is a block diagram illustrating a wireless communication system supporting beamforming and / or multiple-input multiple-output (MIMO) communications according to some aspects;

[0017] Figure 5 is a block diagram illustrating a radio protocol architecture for a user plane and a control plane according to some aspects;

[0018] Figure 6is a diagram illustrating dynamic power sharing between a primary cell group (MCG) and a secondary cell group (SCG) from a UE perspective in accordance with some aspects;

[0019] Figure 7 is a diagram illustrating dynamic power sharing between an MCG and an SCG utilizing quantized fixed transmission time values ​​and timing offset values ​​in accordance with some aspects;

[0020] Figure 8 is a diagram illustrating dynamic power sharing between an MCG and an SCG from a network perspective utilizing fixed transmission time values ​​and timing offset values ​​in accordance with some aspects;

[0021] Fig. 9 is a diagram illustrating dynamic power sharing between an MCG and an SCG from a network perspective utilizing a fixed transmission time value and two timing offset values ​​in accordance with some aspects;

[0022] Fig.10 is a diagram illustrating dynamic power sharing between an MCG and an SCG from a network perspective using a fixed transmission time value and two timing offset values ​​in the event that the SCG drops a transmission in accordance with some aspects;

[0023] Fig.11 is a diagram illustrating dynamic power sharing between an MCG and an SCG from a network perspective using a fixed transmission time value and two timing offset values ​​in the event that the MCG drops a transmission in accordance with some aspects;

[0024] Fig.12 is a diagram illustrating dynamic power sharing between MCG and SCG using fixed transmission time values ​​and timing offset values ​​from a network perspective to enable a UE to split power between the MCG and SCG in accordance with some aspects;

[0025] Fig.13 is a block diagram illustrating an example of a hardware implementation of a scheduled entity employing a processing system according to some aspects;

[0026] Fig.14 is a block diagram illustrating an example of a hardware implementation of a scheduling entity employing a processing system according to some aspects; and

[0027] Fig.15 is a flow chart illustrating a process for handling timing offset in a dual connectivity (NR-DC) power sharing configuration according to some aspects.

[0028] Detailed Description

[0029] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0030] Although various aspects and embodiments are described in this application by explanation of some examples, it will be understood by those skilled in the art that additional implementations and use cases can be generated in many different arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, each embodiment and / or use can be generated via an integrated chip embodiment and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not be specifically for each use case or application, the wide applicability of the described innovation may occur. The scope of each implementation can range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed or OEM devices or systems incorporating one or more aspects of the described innovation. In some practical environments, the equipment incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., of various sizes, shapes, and configurations.

[0031] The various concepts presented throughout this disclosure may be implemented across a wide variety of telecommunication systems, network architectures, and communication standards. Figure 1 , various aspects of the present disclosure are explained with reference to a wireless communication system 100 as an illustrative example and not as a limitation. The wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. By means of the wireless communication system 100, the UE 106 may be enabled to perform data communications with an external data network 110, such as, but not limited to, the Internet.

[0032] The RAN 104 may implement any suitable radio access technology (RAT) to provide radio access to the UE 106. As an example, the RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification, commonly referred to as 5G. As another example, the RAN 104 may operate under a mix of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, commonly referred to as LTE. 3GPP refers to this hybrid RAN as the Next Generation RAN, or NG-RAN. In another example, the RAN 104 may operate according to both LTE and 5G NR standards. Of course, many other examples may be utilized within the scope of the present disclosure.

[0033] As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station (BS) is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be referred to as a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a B node (NB), an evolved B node (eNB), a gB node (gNB), or some other suitable terminology by those skilled in the art. In an example where the RAN 104 operates according to both LTE and 5G NR standards, one of the base stations 108 may be an LTE base station, and another may be a 5G NR base station.

[0034] The radio access network 104 is further explained as supporting wireless communications for multiple mobile devices. The mobile device may be referred to as a user equipment (UE) 106 in the 3GPP standard, but may also be referred to as a mobile station (MS), a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal (AT), a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology by those skilled in the art. The UE 106 may be a device that provides access to network services to a user. In an example in which the RAN 104 operates according to both LTE and 5G NR standards, the UE 106 may be an evolved universal terrestrial radio access network-new radio dual connectivity (EN-DC) UE that is capable of simultaneously connecting to an LTE base station and an NR base station to receive data packets from both the LTE base station and the NR base station.

[0035] Within this document, a "mobile" device does not necessarily need to have mobile capabilities and can be stationary. The term mobile device or mobile device refers to a wide variety of devices and technologies. A UE may include several hardware structural components that are sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, for example, corresponding to the "Internet of Things". Additionally, a mobile device may be a car or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-rotor aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. Additionally, the mobile device may be a digital home or smart home device, such as home audio, video and / or multimedia devices, appliances, vending machines, smart lighting devices, home security systems, smart meters, etc. The mobile device may further be a smart energy device, a security device, a solar panel or solar array, municipal infrastructure devices that control power, lighting, water, etc. (e.g., smart grids); industrial automation and enterprise devices; logistics controllers; agricultural equipment; military defense equipment, vehicles, aircraft, ships and weapons, etc. Further, the mobile device may provide networked medical or telemedicine support, i.e., remote health care. Telehealth devices may include telehealth monitoring devices and telehealth supervision devices, whose communications may be given priority treatment or prioritized access over other types of information, for example in the form of prioritized access for critical service data transmission and / or associated QoS for critical service data transmission.

[0036] Wireless communication between RAN 104 and UE 106 may be described as utilizing an air interface. Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (further described below; e.g., base station 108). Another way to describe this scheme may be to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions. According to further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (further described below; e.g., UE 106).

[0037] In some examples, access to the air interface may be scheduled, wherein a scheduling entity (e.g., a base station 108) allocates resources for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE 106 (which may be a scheduled entity) may utilize resources allocated by the scheduling entity 108.

[0038] Base station 108 is not the only entity that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (eg, one or more other UEs).

[0039] like Figure 1 , the scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in the wireless communication network, including downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108. On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information), or other control information from another entity in the wireless communication network, such as the scheduling entity 108.

[0040] Additionally, uplink and / or downlink control information and / or traffic information may be divided into frames, subframes, time slots, and / or symbols in time. As used herein, a symbol may refer to a time unit in which each subcarrier carries one resource element (RE) in an orthogonal frequency division multiplexing (OFDM) waveform. A time slot may carry 7 or 14 OFDM symbols. A subframe may refer to a duration of 1 ms. Multiple subframes or time slots may be grouped together to form a single frame or radio frame. Of course, these definitions are not required, and any appropriate scheme may be utilized to organize the waveform, and the various time divisions of the waveform may have any appropriate duration.

[0041] Generally speaking, base stations 108 may include a backhaul interface for communicating with a backhaul portion 120 of a wireless communication system. Backhaul 120 may provide a link between base stations 108 and core network 102. Additionally, in some examples, a backhaul network may provide interconnections between respective base stations 108. Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, and the like, using any suitable transport network.

[0042] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to a 5G standard (e.g., 5GC). Alternatively or additionally, the core network 102 may be configured according to a 4G Evolved Packet Core (EPC), or any other suitable standard or configuration.

[0043] Now refer to Figure 2 , a schematic illustration of RAN 200 is provided by way of example and not limitation. In some examples, RAN 200 may be similar to that described above and in Figure 1 The geographic area covered by the RAN 200 may be divided into cellular regions (cells) that may be uniquely identified by a user equipment (UE) based on an identity broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cells 208 are illustrated, each of which may include one or more sectors (not shown). A sector is a sub-area of ​​a cell. All sectors within one cell are served by the same base station. A radio link within a sector may be identified by a single logical identification belonging to the sector. In a cell divided into sectors, multiple sectors within a cell may be formed by antenna groups, where each antenna is responsible for communication with UEs in a portion of the cell.

[0044] exist Figure 2, two base stations 210 and 212 are shown in the cellular cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in the cellular cell 206. That is, the base station may have an integrated antenna, or may be connected to the antenna or RRH by a feeder cable. In the illustrated example, the cellular cells 202, 204, and 126 may be referred to as macro cells because the base stations 210, 212, and 214 support cells with large sizes. In addition, the base station 218 is shown in a small cell 208 (e.g., a micro cell, a micro cell, a femto cell, a home base station, a home node B, a home evolved node B, etc.), which may overlap with one or more macro cells. In this example, the cellular cell 208 may be referred to as a small cell because the base station 218 supports a cell with a relatively small size. The cell size setting may be done according to the system design and component constraints.

[0045] It is to be understood that the radio access network 200 may include any number of wireless base stations and cellular cells. In addition, relay nodes may be deployed to extend the size or coverage area of ​​a given cellular cell. Base stations 210, 212, 214, 218 provide wireless access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be similar to those described above and in Figure 1 The same as the base station / scheduling entity 108 illustrated in FIG.

[0046] Within the RAN 200, cells may include UEs that may be in communication with one or more sectors of each cell. In addition, each base station 210, 212, 214, and 218 may be configured to provide a core network 102 (see FIG. 1 ) for all UEs in the corresponding cell. Figure 1 ) access point. For example, UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 via RRH 216; and UE 234 may be in communication with base station 218. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 238, 240, and / or 242 may be in communication with the base stations described above and in Figure 1 The UE / scheduled entity 106 is the same as illustrated in FIG.

[0047] When configured in a dual connectivity environment, the UE may be simultaneously connected to two evolved eNode Bs (eNBs), which may include a master eNB (MeNB) and a secondary eNB (SeNB) operating on different carrier frequencies, wherein at least the master eNB (or "master node") is connected to the core network (e.g., 102). A master cell group (MCG) may be configured as a serving cell group associated with the MeNB, and a secondary cell group (SCG) may be configured as a serving cell group associated with the SeNB. From the perspective of the UE, there are three bearer types for multi-radio access technology (RAT) dual connectivity (MR-DC): a master cell group (MCG) bearer, a secondary cell group (SCG) bearer, and a split bearer. An MCG bearer is a radio bearer served only by a MeNB, while an SCG is a radio bearer served only by a gNB. A split bearer may be configured as a bearer directly connected to a gNB from a serving gateway (SGW), and is characterized by a single flow transmitted from the CN to the PDCP protocol layer located at the gNB. The gNB can then split the traffic and forward the packets to the MeNB Radio Link Control (RLC).

[0048] Dynamic power sharing allows UEs in dual connectivity scenarios to operate in the following manner: after allocating the required transmit power of the MCG (primary cell group), the remainder of the uplink power can be allocated to the SCG (secondary cell group). For dynamic power sharing, the MCG has a higher priority than the SCG for power allocation. The reason is that the control plane signaling will mainly pass through the MCG, so the uplink coverage of the MCG should be guaranteed. With dynamic power sharing, neither LTE nor NR uplink transmissions require a maximum power limit (e.g., 20dBm) because the dual uplinks can dynamically share the power headroom. This scheme provides the potential for optimal power allocation between LTE and NR in a UE-specific manner based on different coverage scenarios. The same techniques and technologies can also be applied to MCG service cells and SCG service cells in dual connectivity (NR-DC) implementations, as described in further detail below.

[0049] In some examples, unmanned aerial vehicle (UAV) 220 (which may be a drone or a quadcopter) may be a mobile network node and may be configured to function as a UE. For example, UAV 220 may operate within cell 202 by communicating with base station 210.

[0050] In the radio access network 200, the ability of a UE to communicate independently of its location while moving is called mobility. The various physical channels between the UE and the radio access network are generally managed by an access and mobility management function (AMF, not illustrated, Figure 1The AMF is established, maintained and released under the control of the core network 102 in the core network, which may include a security context management function (SCMF) that manages the security context of both the control plane and the user plane functionalities and a security anchor function (SEAF) that performs authentication.

[0051] The radio access network 200 may utilize DL-based mobility or UL-based mobility to implement mobility and handover (i.e., the transfer of a UE's connection from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, a UE may monitor various parameters of a signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE may perform a handover or handover from the serving cell to a neighboring (target) cell. For example, a UE 224 (illustrated as a vehicle, but any suitable form of UE may be used) may move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from a neighbor cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 may transmit a report message indicating this condition to its serving base station 210. In response, the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.

[0052] In a network configured for UL-based mobility, the UL reference signal from each UE may be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of these cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within a core network) may determine a serving cell for UE 224. As UE 224 moves in radio access network 200, the network may continue to monitor uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 may handover UE 224 from the serving cell to the neighboring cell with or without notifying UE 224.

[0053] Although the synchronization signal transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone including multiple cells operating on the same frequency and / or having the same timing. The use of zones in a 5G network or other next generation communication network implements an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0054] In various implementations, the air interface in the radio access network 200 may utilize a licensed spectrum, an unlicensed spectrum, or a shared spectrum. A licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulator. An unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. Although some technical rules generally still need to be followed to access the unlicensed spectrum, any operator or device can obtain access. A shared spectrum may fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, a license holder of a portion of a licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, for example, using conditions determined by the appropriate license holder to obtain access.

[0055] In some examples, access to the air interface may be scheduled, where a scheduling entity (e.g., a base station) allocates resources (e.g., time-frequency resources) for communication among some or all devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, a scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communications, a UE or scheduled entity utilizes resources allocated by the scheduling entity.

[0056] The base station is not the only entity that can be used as a scheduling entity. That is, in some examples, a UE can be used as a scheduling entity, thereby scheduling resources for one or more scheduled entities (e.g., one or more other UEs). In this example, sidelink or other types of direct link signals can be communicated directly between UEs without having to rely on scheduling or control information from another entity. For example, UE 238 is illustrated as communicating with UEs 240 and 242. In some examples, UE 238 acts as a scheduling entity, while UEs 240 and 242 can act as scheduled entities.

[0057] UE 238, 240 and 242 can communicate via direct links in, for example, massive machine type communication (MTC), device to device (D2D), peer to peer (P2P), vehicle to everything (V2X) and / or mesh networks. In the mesh network example, UE 240 and 242 can optionally communicate directly with each other in addition to communicating with a scheduling entity (e.g., UE 238). In some examples, UE 238 can be a transmitting side link device that reserves resources on a side link carrier for transmission of side link signals to UEs 240 and 242 in a D2D or V2X network. Here, UE 240 and 242 are each receiving side link devices. UE 240 and 242 can then reserve additional resources on the side link carrier for subsequent side link transmissions.

[0058] In some examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​the serving base station 212 can both communicate with the base station 212 using cellular signals and communicate with each other using sidelink signals 227 without relaying the communication through the base station. In this example, the base station 212 or one or both of the UEs 226 and 228 can act as a scheduling entity to schedule the sidelink communication between the UEs 226 and 228. For example, the UEs 226 and 228 can communicate the sidelink signals 227 within a vehicle-to-everything (V2X) network.

[0059] In order to achieve a low block error rate (BLER) for transmissions over the radio access network 200 while still achieving very high data rates, channel coding may be used. That is, wireless communications may generally utilize suitable error-correcting block codes. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. Utilizing this redundancy in the encoded information message may improve the reliability of the message, thereby enabling correction of any bit errors that may occur due to noise.

[0060] In earlier 5G NR specifications, user data is encoded using quasi-cyclic low-density parity check (LDPC) with two different basemaps: one basemap is used for large code blocks and / or high code rates, and the other basemap is used for other cases. Control information and the physical broadcast channel (PBCH) are encoded using polar coding based on nested sequences. For these channels, puncturing, shortening, and repetition are used for rate matching.

[0061] However, it will be appreciated by those skilled in the art that various aspects of the present disclosure may be implemented using any suitable channel code. Various implementations of the base station (e.g., scheduling entity) 108 and the UE (e.g., scheduled entity) 106 may include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to utilize one or more of these channel codes for wireless communication.

[0062] The air interface in the radio access network 200 may utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link in which both endpoints can communicate with each other in two directions. Full-duplex means that both endpoints can communicate with each other at the same time. Half-duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full-duplex channel generally relies on the physical isolation of the transmitter and the receiver, and suitable interference cancellation techniques. Full-duplex simulation is usually implemented for a wireless link by utilizing frequency division duplex (FDD) or time division duplex (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmissions in one direction, and at other times, the channel is dedicated to transmissions in another direction, where the direction can change very quickly, for example, several times per time slot.

[0063] The air interface in the radio access network 200 may further utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224. In addition, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and may be provided using time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource extension multiple access (RSMA), or other appropriate multiple access schemes. In addition, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 may be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0064] Various aspects of the present disclosure will be described with reference to OFDM waveforms, examples of which are shown in Figure 3 Schematically illustrated in FIG. It will be appreciated by those skilled in the art that various aspects of the present disclosure may be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of the present disclosure may focus on OFDM links for clarity, it will be appreciated that the same principles may also be applied to SC-FDMA waveforms.

[0065] Now refer to Figure 3, illustrates an expanded view of an exemplary DL subframe 302 showing an OFDM resource grid. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers.

[0066] Resource grid 304 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, there may be a corresponding multiple number of resource grids 304 available for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex number representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, which number is independent of the parameter design used. In some examples, depending on the parameter design, an RB may include any suitable number of consecutive OFDM symbols in the time domain. Within the present disclosure, it is assumed that a single RB (such as RB 308) corresponds entirely to a single communication direction (transmission or reception for a given device).

[0067] A UE typically utilizes only a subset of the resource grid 304. An RB may be the smallest resource unit that may be allocated to a UE. Thus, the more RBs are scheduled for a UE and the higher the modulation scheme chosen for the air interface, the higher the data rate for the UE.

[0068] In this illustration, RB 308 is shown as occupying less than the entire bandwidth of subframe 302, with some subcarriers illustrated above and below RB 308. In a given implementation, subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308. Furthermore, in this illustration, RB 308 is shown as occupying less than the entire duration of subframe 302, but this is merely one possible example.

[0069] Each 1 ms subframe 302 may include one or more adjacent time slots. Figure 4In the example shown in , a subframe 302 includes four time slots 310. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots with shorter durations (e.g., one or two OFDM symbols). In some cases, these mini-slots may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit.

[0070] The expanded view of one slot 310 illustrates that the slot 310 includes a control region 312 and a data region 314. Generally speaking, the control region 312 may carry a control channel (e.g., PDCCH), while the data region 314 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 3 The simple structure illustrated in is merely exemplary in nature and different slot structures may be utilized and may include one or more of each of the control region and the data region.

[0071] Although not in Figure 3 306, but each RE 308 within an RB 306 may be scheduled to carry one or more physical channels, including a control channel, a shared channel, a data channel, etc. Other REs 306 within an RB 308 may also carry pilot or reference signals, including but not limited to a demodulation reference signal (DMRS), a control reference signal (CRS), a CSI-RS, or a sounding reference signal (SRS). These pilot or reference signals may be used by a receiving device to perform channel estimation on the corresponding channel, which may enable coherent demodulation / detection of the control and / or data channels within the RB 308.

[0072] In DL transmission, a transmitting device (e.g., a scheduling entity) may allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information to one or more scheduled entities, including one or more DL control channels (such as PBCH); physical control format indicator channel (PCFICH); physical hybrid automatic repeat request (HARQ) indicator channel (PHICH); and / or physical downlink control channel (PDCCH), etc. The transmitting device may further allocate one or more REs 306 to carry other DL signals (such as DMRS); phase tracking reference signal (PT-RS); channel state information-reference signal (CSI-RS); primary synchronization signal (PSS); and secondary synchronization signal (SSS).

[0073] The synchronization signals PSS and SSS, and in some examples also the PBCH and PBCH DMRS, may be transmitted in a synchronization signal block (SSB) comprising 4 consecutive OFDM symbols numbered in ascending order from 0 to 3 via a time index. In the frequency domain, the SSB may be extended over 240 contiguous subcarriers, where the subcarriers are numbered in ascending order from 0 to 239 via a frequency index. Of course, the present disclosure is not limited to this particular SSB configuration. Other non-limiting examples within the scope of the present disclosure may utilize more or less than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit the PBCH; and / or may use a different number of symbols and / or non-consecutive symbols for the SSB.

[0074] The PBCH may further include: a master information block (MIB), which includes various system information, together with parameters for decoding a system information block (SIB). The SIB may be, for example, a system information type 1 (SystemInformationType1) (SIB1), which may include various additional system information. Examples of system information may include, but are not limited to: subcarrier spacing, system frame number, cell bar indication, common control resource set (CoreSet) list (e.g., PDCCH CoreSet0 or CoreSet1), common search space list, search space for SIB1, paging search space, random access search space, and uplink configuration information.

[0075] The PCFICH provides information to assist the receiving device in receiving and decoding the PDCCH. The PDCCH carries downlink control information (DCI), including but not limited to power control commands, scheduling information, grants, and / or RE assignments for DL ​​and UL transmissions. The PHICH carries HARQ feedback transmissions, such as acknowledgments (ACKs) or negative acknowledgments (NACKs). HARQ is a well-known technology to those of ordinary skill in the art, where for accuracy, the integrity of the packet transmission may be verified on the receiving side using any suitable integrity check mechanism, such as a checksum or cyclic redundancy check (CRC). If the integrity of the transmission is confirmed, an ACK may be transmitted, and if it is not confirmed, a NACK may be transmitted. In response to the NACK, the transmitting device may send a HARQ retransmission, which may enable catch-up combining, incremental redundancy, and the like.

[0076] In UL transmission, the transmitting device (e.g., the scheduled entity) may use one or more REs 306 to carry UL control information, which includes one or more UL control channels, such as a physical uplink control channel (PUCCH) and / or a random access channel (RACH). For example, RACH may be used in a random access procedure during initial access of the uplink. The UL control information may include various packet types and categories, including pilots, reference signals, and information configured to implement or assist in decoding uplink data transmission. For example, the UL control information may include DMRS or SRS. In some examples, the control information may include a scheduling request (SR), that is, a request for the scheduling entity to schedule uplink transmission. Here, in response to the SR transmitted on the control channel, the scheduling entity may transmit downlink control information, which may schedule resources for uplink packet transmission. The UL control information may also include HARQ feedback, channel state feedback (CSF), or any other suitable UL control information. UL transmissions may be grant-based (i.e., grants delivered using DCI), or grant-less, including Type 1 (e.g., based only on RRC configuration without any L1 signaling) or Type 2 (e.g., based on RRC configuration and L1 signaling for activation / deactivation).

[0077] In addition to control information, one or more REs 306 (e.g., within the data region 314) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as on the PDSCH for DL ​​transmissions or on the physical uplink shared channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within the data region 314 may be configured to carry a SIB (e.g., SIB1) that carries system information that may enable access to a given cell.

[0078] These physical channels are generally multiplexed and mapped to transport channels for handling by the medium access control (MAC) layer. The transport channels carry information blocks, which are called transport blocks (TBs). The transport block size (TBS), which may correspond to the number of information bits, may be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0079] Refer to above Figure 1-3 The channels or carriers described in are not necessarily all channels or carriers that can be utilized between the scheduling entity and the scheduled entity, and a person of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those channels or carriers illustrated, such as other traffic, control, and feedback channels.

[0080] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 4 An example of a wireless communication system 400 that supports beamforming and / or MIMO is illustrated. In a MIMO system, a transmitter 402 includes multiple transmit antennas 404 (e.g., N transmit antennas), and a receiver 406 includes multiple receive antennas 408 (e.g., M receive antennas). Thus, there are N×M signal paths 410 from the transmit antennas 404 to the receive antennas 408. Each of the transmitter 402 and the receiver 406 may be implemented, for example, in a scheduling entity, a scheduled entity, or any other suitable wireless communication device.

[0081] The use of such multi-antenna technology enables wireless communication systems to exploit the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to transmit different data streams (also referred to as layers) simultaneously on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the total system capacity, the latter of which is called multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying the data streams by different weights and phase shifts) and then transmitting each spatially precoded stream through multiple transmit antennas on the downlink. The spatially precoded data streams arrive at the UE with different spatial signatures, and these different spatial signatures enable each UE to recover one or more data streams intended for the UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0082] The number of data streams or layers corresponds to the rank of the transmission. In general, the rank of a MIMO system is limited to the lower of the number of transmit or receive antennas 404 or 408. Additionally, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank (and therefore, the number of data streams) assigned to a specific UE on the downlink may be determined based on a rank indicator (RI) transmitted from the UE to the base station. The RI may be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the measured signal to interference and noise ratio (SINR) on each receive antenna. The RI may indicate, for example, the number of layers that can be supported under the current channel conditions. The base station may use the RI together with resource information (e.g., available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0083] In one example, if Figure 4, a rank 2 spatial multiplexing transmission on a 2x2 MIMO antenna configuration will transmit one data stream from each transmit antenna 404. Each data stream arrives at each receive antenna 408 along a different signal path 410. The receiver 406 can then reconstruct the data streams using the signals received from each receive antenna 408.

[0084] Beamforming is a signal processing technique that may be used at a transmitter 402 or a receiver 406 to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitter 402 and the receiver 406. Beamforming may be achieved by combining signals communicated via antennas 404 or 408 (e.g., antenna elements of an antenna array module) so that some of these signals experience constructive interference and other signals experience destructive interference. To create the desired constructive / destructive interference, the transmitter 402 or the receiver 406 may apply an amplitude and / or phase offset to the signal transmitted or received from each of the antennas 404 or 408 associated with the transmitter 402 or the receiver 406.

[0085] In some examples, in order to select a specific beam for communicating with the UE, the base station may transmit a reference signal, such as an SSB or a channel state information reference signal (CSI-RS), on each of a plurality of beams (SSB beams) in a beam sweeping manner. The UE may measure the reference signal received power (RSRP), the reference signal received quality (RSRQ), or the SINR on each beam, and transmit a beam measurement report indicating the RSRP of each measured beam to the base station. The base station may then select a specific beam for communicating with the UE based on the beam measurement report. In other examples, when the channel is reciprocal, the base station may derive a specific beam for communicating with the UE based on uplink measurements of one or more uplink reference signals, such as a sounding reference signal (SRS).

[0086] To gain access to a cell, a UE may perform a random access procedure on a physical random access channel (PRACH). The UE may identify a random access search space including PRACH resources for initiating a RACH procedure from SIB1. For example, the random access procedure may begin after the UE acquires a cell and determines the occurrence of a RACH opportunity (e.g., PRACH resources) after reading the SSB and SIB1. The SSB provides initial system information (SI), while SIB1 (and other SIB blocks) provide the remaining minimum SI (RMSI). For example, the PBCH MIB of the SSB may carry the first part of the SI required by the user equipment (UE) to access the network. The SIBs (e.g., SIB1 and SIB2) may carry the RMSI required for the UE to gain network access.

[0087] RACH procedures can be performed in various scenarios, such as uplink synchronization loss, lack of available PUCCH resources, scheduling request failure, and other use cases. In addition, RACH procedures can be contention-based or contention-free, and can include a 2-step RACH procedure (contention-based or contention-free), a 3-step RACH procedure (contention-free), or a 4-step RACH procedure (contention-based).

[0088] Used for example Figure 1 The radio access network 104 and / or Figure 2 The radio protocol architecture of the illustrated radio access network 200 may take various forms depending on the particular application. Figure 5 Examples of radio protocol architectures for the user plane and the control plane are illustrated.

[0089] like Figure 5 As explained in , the radio protocol architecture for UE and base station includes three layers: Layer 1 (L1), Layer 2 (L2) and Layer 8 (L8). L1 is the lowest layer and implements various physical layer signal processing functions. L1 will be referred to as the physical layer 506 in this article. L2 508 is above the physical layer 506 and is responsible for the link between the UE and the base station above the physical layer 506.

[0090] In the user plane, the L2 layer 508 includes a medium access control (MAC) layer 510, a radio link control (RLC) layer 512, a packet data convergence protocol (PDCP) 514 layer, and a service data adaptation protocol (SDAP) layer 516, which are terminated at the base station on the network side. Although not shown, the UE may have several upper layers above the L2 layer 508, including at least one network layer (e.g., an IP layer and a user data protocol (UDP) layer) and one or more application layers that are terminated at a user plane function (UPF) on the network side.

[0091] The SDAP layer 516 provides mapping between 5G core (5GC) quality of service (QoS) flows and data radio bearers, and performs QoS flow ID marking in both downlink and uplink packets. The PDCP layer 514 provides packet sequence numbering, ordered delivery of packets, retransmission of PDCP protocol data units (PDUs), and delivery of upper layer data packets to the lower layer. PDUs may include, for example, Internet Protocol (IP) packets, Ethernet frames, and other unstructured data (i.e., machine type communications (MTC), hereinafter collectively referred to as "packets"). The PDCP layer 514 also provides header compression of upper layer data packets to reduce radio transmission overhead, security by encrypting data packets, and integrity protection of data packets. The PDCP context may indicate whether PDCP duplication is used for unicast connections.

[0092] The RLC layer 512 provides segmentation and reassembly of upper layer data packets, error correction through automatic repeat request (ARQ), and sequence numbering independent of PDCP sequence numbering. The RLC context may indicate whether to use an acknowledgement mode (e.g., using a reordering timer) or a non-acknowledgement mode for the RLC layer. The MAC layer 510 provides multiplexing between logical channels and transport channels. The MAC layer 510 is also responsible for allocating various radio resources (e.g., resource blocks) in a cellular cell and HARQ operations among UEs. The MAC context may implement, for example, a HARQ feedback scheme, a resource selection algorithm, carrier aggregation, beam failure recovery, or other MAC parameters for unicast connections. The physical layer 506 is responsible for transmitting and receiving data on a physical channel (e.g., within a time slot). The PHY context may indicate a transport format and radio resource configuration (e.g., bandwidth part (BWP), parameter design, etc.) for a unicast connection.

[0093] In the control plane, the radio protocol architecture for the UE and the base station is basically the same for L1 506 and L2 508, except that there is no SDAP layer in the control plane and there is no header compression function for the control plane. The control plane also includes a radio resource control (RRC) layer 518 in L8 and a higher non-access stratum (NAS) layer 520. The RRC layer 518 is responsible for establishing and configuring signaling radio bearers (SRBs) and data radio bearers (DRBs) between the base station and the UE, paging initiated by the 5GC or NG-RAN, and broadcasting of system information related to the access stratum (AS) and non-access stratum (NAS). The RRC layer 518 is further responsible for QoS management, mobility management (e.g., handover, cell selection, inter-RAT mobility), UE measurement and reporting, and security functions. The NAS layer 520 terminates at the AMF in the core network and performs various functions such as authentication, registration management, and connection management.

[0094] Figure 6 is a diagram 600 illustrating dynamic power sharing between a primary cell group (MCG) and a secondary cell group (SCG) from the perspective of a UE in accordance with some aspects. Under the NR-DC architecture, the NG-RAN may be configured to support NR-NR dual connectivity (NR-DC), where the UE is connected to one gNB acting as a primary node (MN) and another gNB acting as a secondary node (SN). The primary gNB may be connected to the core network (5GC) via an NG interface and to the secondary gNB via an Xn interface. The secondary gNB may be connected to the 5GC via an NG-U interface. In addition, NR-DC may also be used when the UE is connected to two gNB-DUs (one serving the MCG and the other serving the SCG), connected to the same gNB-CU, acting as both a MN and a SN.

[0095] exist Figure 6 In the example of FIG. 1 , an MCG control channel 602 and an SCG control channel 604 are shown, wherein an MCG uplink DCI (UL DCI) 606 is scheduled for transmission on an MCG PUSCH 608, and an SCG UL DCI 610 is scheduled for transmission on an SCG PUSCH 612, wherein the transmission of the UL DCI occurs at T 0 As shown in the figure. In order to calculate the 0 The UE (eg, 106) may check the transmit power of the SCG UL transmission at the time T 0 -T 偏移 previously received PDCCH(s) triggering overlapping MCG UL transmission, and if such PDCCH(s) are detected, the UE sets its transmit power in the SCG (pwr_SCG) such that pwr_SCG ≤ min{P SCG ,P total –MCG tx power}, where P SCG is the maximum SCG power for transmission, P total is the configured maximum transmit power, and MCG tx power is the actual transmit power of the MCG. Otherwise, the UE sets its transmit power to pwr_SCG ≤ P total .

[0096] For the time T 0 The UE can use the timing T to start the SCG transmission. 0 –T 偏移 After the offset T 偏移 To perform a multi-step process, the UE can first calculate the 0 =The sum power of the MCG transmission(s) overlapped by the SCG transmission(s) at the start, and then using the power available for the SCG transmission(s) identified in the calculation step to calculate the power available for the SCG transmission(s) at time T 0 The power is allocated between the SCG transmissions similar to uplink carrier aggregation (UL-CA) at the beginning. As shown in the figure, at T 0 -T 偏移 Previously, the network could schedule the possible 0 MCG UL overlaps with SCG PUSCH, while in T 0 –T 偏移 After that, the network does not schedule at time T 0 MCG UL overlapped with SCG PUSCH. In some examples, inter-cell group and power exchange can be configured as unidirectional (e.g., MCG to SCG). For SCG UL transmission, the maximum power is within the deadline (T 0 -T偏移 ) should not be affected after. Thus, during the SCG UL intermediate period, there will be no need to update the SCG maximum power. In some examples, the uplink carrier aggregation (UL-CA) prioritization rules in each cellular cell group (MCG, SCG) can be reused.

[0097] Generally speaking, T 偏移 should be long enough to handle the cascaded multi-step process described above (i.e., power allocation cannot be performed until the sum of the powers is calculated). This is necessary to ensure that 0 The SCG transmission started and used for the 0 The minimum UE processing time for any of the MCG transmissions that overlap with the starting SCG transmission is necessary. As a property of dual connectivity, at each MCG scheduling opportunity, the master node (e.g., MgNB) may not know how the secondary node (e.g., SgNB) exactly schedules uplink transmissions to UEs on the SCG cell. Therefore, the master node can assume a "worst case" of all possible minimum UE processing times for the SCG, which means that the master node cannot schedule the uplink transmissions to UEs on the SCG cell at time T. 0 The MCG uplink transmission overlapping with the SCG transmission is scheduled before the maximum possible UE processing time among all possible UE processing times of the SCG transmission starting. As a simplified example, if at time T 0 The SCG transmission started can be PUSCH without aperiodic CSI (A-CSI) or PUSCH with A-CSI, then the scheduling is the same as at time T 0 The MCG DCI of the MCG uplink transmission overlapped by the SCG transmission started cannot be transmitted within T 0 -max{T proc,2 , T proc,CSI =T 0 -T proc,CSI After that, T proc,2 is the PUSCH preparation time of the PUSCH scheduled by the PDCCH using the associated PUSCH timing capability, and T proc,CSI is the CSI processing time. Under such configuration, the UE will be able to use T shorter than the maximum possible UE processing time for SCG transmission. 偏移 to handle dynamic power sharing.

[0098] In some examples, the master node (e.g., MgNB) may be configured to determine the exact minimum UE processing time for MCG uplink transmissions. However, the actual UE processing time specified for a CG may depend on various dynamic factors, such as DCI indications and uplink control information (UCI) multiplexing. For UE PUSCH preparation procedure time, if the PUSCH allocation for a transport block includes a time slot offset K, the UE PUSCH preparation procedure time may be determined by the time slot offset K. 2 The first uplink symbol of the scheduling DCI defined by the start and length indicator SLIV and including the effect of the timing advance is no earlier than the symbol L 2 , where L 2 is defined as the number of cyclic prefixes that expire after the reception of the last symbol of the PDCCH carrying the DCI scheduling the PUSCH is completed.

[0099] T proc，2 =max((N 2 +d 2，1 )(2048+144)·κ2 -μ ·T c , d 2，2 )

[0100] The UE may transmit the transport block if the next uplink symbol starting with N 2 represents the PUSCH preparation time symbol based on μ (e.g., 0, 1, 2, etc.) for UE processing capabilities 1 and 2, respectively, where μ corresponds to the maximum T proc，2 (μ DL , μ UL ), where μ DL corresponds to the subcarrier spacing of the downlink for transmitting the PDCCH carrying the DCI scheduling the PUSCH, and μ UL corresponds to the subcarrier spacing of the uplink channel to be used to transmit the PUSCH, and κ is a representation of T S / T C A constant in time units (e.g., 64). If the first symbol of a PUSCH allocation includes only DM-RS, then d 2，1 =0, otherwise d 2，1 =1. If the UE is configured with multiple active component carriers, the first uplink symbol in the PUSCH allocation further includes the effect of the timing difference between the component carriers. If the scheduling DCI triggers the switching of the BWP, then d 2，2 Equal to the switching time, otherwise d 2，2 = 0. If the PUSCH indicated by the DCI overlaps with one or more PUCCH channels, the transport block is multiplexed, otherwise the transport block is transmitted on the PUSCH indicated by the DCI.

[0101] When UE is at time T 0 When there is UCI feedback at the beginning of the transmission, the minimum processing time can be calculated by the processing time T proc，CSI , or Based on these dynamic factors, T 偏移 Configuring it to be variable may require the UE to dynamically adjust the processing timeline (e.g., for calculating the time corresponding to the time T 0 =(t) / (c) = (t) / (d) = (t) / (e) = (t) / (f ... 偏移 should not be shorter than the time T used with 0 The maximum possible UE processing time among all possible UE processing times of MCG transmissions overlapped by the starting SCG transmission. In general, T 偏移 Should not be less than in represents the maximum possible minimum UE processing time among some or all possible UE processing times for MCG transmissions overlapping with SCG transmissions starting at time T0, and Represents the maximum possible minimum UE processing time among some or all possible UE processing times for SCG transmission starting at time T0.

[0102] For dynamic power sharing, the master node may need to know the T of the SCG used by the UE. 偏移 If T 偏移 is unavailable, the master node can assume that T 偏移 is the maximum possible value. In order to determine T 偏移 The master node may use inter-node messaging to decode the SCG RRC configuration to identify the T used by the UE. 偏移 The SCG RRC configuration used by the master node may include proc,CSI , and / or RRC parameters. However, in some operating environments, the master node may not be configured to decode the UE SCG RRC configuration received by the secondary node of the SCG. In the case where the SCG RRC reconfiguration is transmitted to the master node via an inter-node RRC message, the master node will typically place the RRC message in a container and forward it to the UE via the MCG RRC reconfiguration.

[0103] To solve this problem, T can be used in some examples that do not depend on the RRC configuration. offset In one example, a fixed duration value (e.g., 1.5 ms, 4 ms, etc.) may be used. However, in order to use a fixed duration value for T 偏移 , the selected value(s) should be such that it is consistent with T proc,CSI , and / or For example, if the UE reports its fixed T 偏移 value capability, and the fixed T 偏移 Value has a ratio of T proc,CSI , and / or If the duration of any of the above is longer, the UL DCI can be transmitted on the PUSCH. 偏移 The value has a shorter duration, the UE shall ensure that the DCI in the MCG is within the time T 0 -T 偏移 Can be correctly handled independent of any RRC configuration.

[0104] Figure 7 is a diagram 700 illustrating dynamic power sharing between an MCG and an SCG utilizing quantized fixed transmission time values ​​and timing offset values ​​in accordance with some aspects. Figure 6 , Figure 7 The example of FIG. 1 shows an EN-DC operating environment, wherein an MCG control channel 702 and an SCG control channel 704 are shown, each including a plurality of time slots 706, 712 for each respective control channel. The example shows an MCG UL DCI 706 scheduled for transmission on an MCG PUSCH 710 and an SCG UL DCI 714 scheduled for transmission on an SCG PUSCH 716, wherein the transmission of the UL DCI occurs at T 0 As shown in the figure.

[0105] In some examples, T 偏移 The value of T can be configured to have different T values ​​for different frequency bands (e.g., FR1, FR2) with different frequency ranges and data rate capabilities. 偏移 As an example, T 偏移 The candidate values ​​may be configured as {2ms, 4ms} for FR1 and {1ms, 3ms} for FR2. During operation, the UE may select one value (e.g., 4ms) for FR1 and another value (e.g., 1ms) for FR2 for transmitting UL DCI. The UE may report the selected (preferred) initial value for each FR via UE capability signaling. In one example, for a given band combination, if the UE supports NR-DC and both the MCG cell(s) and the SCG cell(s) are in FR1, the UE reports the T value for FR1. 偏移 In another example, if the UE supports NR-DC and both the MCG cell(s) and the SCG cell(s) are in FR2, the UE reports the T for FR2.偏移 In a further example, if the UE does not support NR-DC when both the MCG cell(s) and the SCG cell(s) are in FR1 or FR2, but supports NR-DC when the MCG cell(s) are in FR1 or FR2, respectively, and the SCG cell(s) are in FR2 or FR1, respectively, the UE does not report the NR-DC for T 偏移 No value is determined because the cells do not share power in the same frequency range.

[0106] In another example, instead of using a fixed time value (e.g., 2 ms) as described above, the UE may measure an index such as a sample index, a symbol index, a slot index, or a subframe index. Based on these measurements, the UE may then use T according to OFDM symbol values ​​instead of fixed time values. 偏移 Thus, for example, T 偏移 The value may be determined as a configured number of symbols (e.g., 28 symbols) for a given subcarrier spacing (SCS) (e.g., 15 kHz). 偏移 The symbol number may be set to reference the SCS, such as 15kHz or 30kHz for FR1 and 60kHz or 120kHz for FR2. In some examples, the SCS selection may be fixed and not configurable through higher level signaling.

[0107] exist Figure 7 In the example, fixed T 偏移 The value is selected by the UE (e.g., 1.5 ms) (as discussed above), which in turn determines T 0 -T 偏移 Here, T 0 -T 偏移 The value may occur in the middle of a time slot (706). The UE may be configured to 0 -T 偏移 The value is quantized to a timing boundary, such as a time slot boundary, and T 0 -T 偏移 The value extends to the boundary itself. In this configuration, if T 0 -T 偏移 If the value is between the boundaries of a slot (e.g., in the middle of a slot), it will be assumed that the DCI does not exist in that slot.

[0108] Figure 8 is an explanation of using a fixed transmission time value (T) from a network perspective according to some aspects. 0 ) and timing offset value (T 偏移(值1) ) is a diagram 800 showing dynamic power sharing between MCG and SCG. Figure 6 For example, Figure 8The example of FIG. 1 illustrates an EN-DC operating environment, wherein an MCG control channel 802 and an SCG control channel 804 are shown, each including a plurality of time slots 806, 812 for each respective control channel. The example shows an MCG UL DCI 810 scheduled for transmission on an MCG PUSCH 808 and an SCG UL DCI 816 scheduled for transmission on an SCG PUSCH 814, wherein the transmission of the UL DCI occurs at T 0 As shown in the figure.

[0109] In this example, the network can consider two T 偏移 Value, where the first T 偏移 The value can be a network-based value (T 偏移(值1) ), and the second value may be a value based on the UE (T 偏移(值2) The network-based value may be, for example, a fixed value (eg, 1.5 ms), while the UE-based value may be, for example, the UL processing time (eg, T proc ). During operation, if T 0 -T 偏移(值1) Earlier than T 0 -T 偏移(值2) , then the network can be not in T 0 -T 偏移(值1) Then the MCG DCI is transmitted as shown in the figure. 0 -T 偏移(值2) Earlier than T 0 -T 偏移(值1) , then the network can be 0 -T 偏移(值2) After that, the MCG DCI is transmitted. In this case, the UE may perform several operations with respect to scheduling DCI transmission. In the first option, the UE may discard the MCG DCI at time T. 0 In the second option, the UE may discard the MCG transmission that overlaps with the SCG transmission. In the third option, the UE may select either or both of the first option and / or the second option according to the UE implementation. Figure 9-11 Further discussion of these configurations is provided.

[0110] Fig. 9 is an explanation of using a fixed transmission time value (T) from a network perspective according to some aspects. 0 ) and two timing offset values ​​(T 偏移(值1) , T 偏移(值2) )Diagram 900 of dynamic power sharing between MCG and SCG. Fig. 9 An example similar to Figure 8906, 912 for each respective control channel. The example shows an MCG UL DCI 908 scheduled for transmission on an MCG PUSCH 910 and an SCG UL DCI 914 scheduled for transmission on an SCG PUSCH 916, wherein the transmission of the UL DCI occurs at T 0 As shown in the figure.

[0111] In this example, you can see that the T 偏移(值2) Compared with T for SCG 偏移(值1) As discussed above, T 偏移(值1) can be a network-based value (e.g., 1.5 ms), while T 偏移(值2) It can be based on the value of the UE (for example, T proc ). During operation, the UE may need to calculate the SCG uplink power, which may occur when the UE is powered by T 偏移(值2) However, as can be seen in the figure, SCG DCI 914 occurs during T 偏移(值1) After that. Nevertheless, since MCG DCI 908 occurred at T 偏移(值1) Before, therefore, the DCI is not needed, and thus at T 偏移(值1) It was not received afterwards.

[0112] Accordingly, when the UE is in T 0 -T 偏移(值1) When the MCG DCI 908 is received previously, the MCG side of the UE does not know whether there are any SCG transmissions overlapping with the MCG DCI 908. As a result, the UE can calculate the MCG transmit power. 0 When the SCG UL transmission of SCG DCI 914 is started, the UE can determine the SCG DCI 914 based on the SCG DCI 914 and the MCG DCI transmitted by T 0 -T 偏移(值2) The calculated MCG transmit power is used to calculate the SCG transmit power.

[0113] Fig.10 is a diagram 1000 illustrating dynamic power sharing between an MCG and an SCG from a network perspective utilizing a fixed transmission time value and two timing offset values ​​in the event that the SCG drops a transmission in accordance with some aspects. Fig.10 An example similar to Fig. 91002 and SCG control channels 1004 each including a plurality of time slots 1006, 1012 for each respective control channel. The example shows MCG UL DCI 1008 scheduled for transmission on MCG PUSCH 1010 and SCG UL DCI 1014 scheduled for transmission on SCG PUSCH 1016, wherein the transmission of the UL DCI occurs at T 0 In this example, it can be seen that the T 偏移(值1) Compared with the T 偏移(值2) occurs earlier in time. Similarly, T 偏移(值1) can be a network-based value (e.g., 1.5 ms), while T 偏移(值2) It can be based on the value of the UE (for example, T proc ). However, as can be seen in the figure, MCG DCI 1008 occurs at T 偏移(值2) After that. In this case, the network can be 0 -T 偏移(值2) and T 0 -T 偏移(值1) MCG DCI is transmitted during the time period between.

[0114] At UE 0 -T 偏移(值2) and T 0 -T 偏移(值1) In case of receiving MCG DCI between time T, the UE may then discard 0 The UE will not have enough time to calculate the transmit power for the SCG uplink transmission (as it occurs at T 偏移(值2) This configuration may be advantageous if there is enough time to discard (cancel) the SCG UL transmission when the UE knows the MCG DCI (1008). In this example, the MCG will have T 偏移(值1) and SCGDCI 1014 to notify the SCG to discard the transmission.

[0115] Accordingly, when the UE is in T 0 -T 偏移(值2) and T 0 -T 偏移(值1) When the UE receives the MCG DCI 1008 between the scheduled and the MCG, the MCG side of the UE does not know whether there is any SCG transmission overlapping with the MCG. In this way, the UE calculates the MCG transmit power. Later, when the UE receives the MCG DCI 1008 scheduled at time T 0 When the SCG UL transmission of SCG DCI 1014 starts, the UE can identify the SCG DCI 1014 in T0 -T 偏移(值2) There is MCG DCI 1008 after that and MCG DCI 1008 is in overlapping scheduling. To avoid potential violation of the maximum available power configuration, the SCG side of the UE may discard the MCG DCI 1008 at time T. 0 The SCG transmission starts as shown in the figure.

[0116] Fig.11 is an explanation of using a fixed transmission time value (T) from a network perspective according to some aspects. 0 ) and two timing offset values ​​(T 偏移(值1) , T 偏移(值2) ) Diagram 1100 of dynamic power sharing between the MCG and SCG in the event that the MCG drops a transmission. Fig.11 An example similar to Fig.10 1, wherein an MCG control channel 1102 and an SCG control channel 1104 are shown each including a plurality of time slots 1106, 1112 for each respective control channel. The example shows an MCG UL DCI 1108 scheduled for transmission on an MCGPUSCH 1110 and an SCG ULDCI 1114 scheduled for transmission on an SCG PUSCH 1116, wherein the transmission of the UL DCI occurs at T 0 In this example, it can be seen that the T 偏移(值1) Compared with the T 偏移(值2) occurs earlier in time. Similarly, T 偏移(值1) can be a network-based value (e.g., 1.5 ms), while T 偏移(值2) It can be based on the value of the UE (for example, T proc ).and Fig.11 In contrast to the example of MCG DCI 1008, it is still in T 偏移(值2) After that, SCG DCI 1114 偏移(值2) In this case, the network can 0 -T 偏移(值2) and T 0 -T 偏移(值1) However, since the MCG side of the UE knows that there is a 0 Scheduled SCG UL transmission, so the UE can discard the MCG transmission overlapping with the SCG transmission (shown as "X" in the figure).

[0117] Accordingly, when the UE is in T 0 -T 偏移(值2) and T 0 -T 偏移(值1)When receiving MCG DCI 1108 between the time T and the time T, if the MCG side of the UE knows that there is an SCG transmission overlapping with the MCG, the UE may discard the MCG transmission 1110. 0 When the UE receives the SCG DCI 1114 of the SCG UL transmission at the beginning, the UE can recognize that there is a DCI of the MCG transmission that is scheduled to overlap with the SCG UL transmission. To avoid potential violation of the maximum available power configuration, the SCG side of the UE can discard the DCI at time T 0 MCG transmission.

[0118] exist Fig.11 In the example of FIG. 1 , it may be possible to multiplex T depending on whether the UL transmission includes CSI, whether the UL transmission is a response to a semi-persistent scheduling (SPS) release, or whether the UL transmission performs UCI multiplexing on a PUSCH on a cell group. 偏移(值2) Set to T for MCG or T for SCG proc,CSI , and / or In other words, T 偏移(值2) It can be set according to the actual UL processing time. In another example, T 偏移(值2) Can be set to T for MCG and T for SCG proc,CSI , and / or One of the following, where T 偏移(值2) It is determined based on the maximum possible UL processing time among the possible UL processing times.

[0119] Fig.12 is an explanation of using a fixed transmission time value (T) from a network perspective according to some aspects. 1 ) and timing offset value (T 偏移 ) Dynamic power sharing is performed between MCG and SCG so that the UE splits power between MCG and SCG 1200. Similar to other examples, Fig.12 The example of FIG. 1 shows an EN-DC operating environment, wherein an MCG control channel 1202 and an SCG control channel 1204 are shown, each including a plurality of time slots 1206, 1212 for each respective control channel. The example shows an MCG UL DCI 1208 scheduled for transmission on an MCG PUSCH 1210 and an SCG UL DCI 1214 scheduled for transmission on an SCG PUSCH 1216, wherein the transmission of the UL DCI occurs at T 1 as shown in the figure.

[0120] In this example, T 偏移 can be a fixed value, and T1 -T 偏移 It can be based on the MCG transmission start time T 1 To determine, MCG transmission start time T 1 Based on the MCG UL transmission time (1210) and may not correspond to the SCG UL transmission time (1216). For SCG UL transmission, the maximum sum power for SCG = min{P SCG ,P total -MCG transmit power}, and the MCG transmit power is based on the MCG DCI (1208) through T 1 -T 偏移 To calculate. At time T 1 -T 偏移 Afterwards, the network can be configured not to schedule 1 The MCG UL overlaps with the SCG PUSCH 1216. However, at time T 1 -T 偏移 Previously, the network may be configured to schedule MCG UL overlapping with SCG PUSCH. In some examples, inter-cell group and power exchange may be configured to be unidirectional (e.g., MCG to SCG). For SCG UL transmissions, the maximum power is set at the deadline (T 1 -T 偏移 ) will not be affected, which means that the SCG maximum power does not need to be updated during the middle of the SCG UL. In some examples, the UL-CA prioritization rules can be reused in each cellular cell group. In some examples, the UE can 偏移 The value of is reported as capability.

[0121] Fig.13 1 is a block diagram illustrating an example of a hardware implementation of a scheduled entity (UE) 1300 employing a processing system 1314 according to some aspects. For example, the scheduled entity 1300 may be such as Figure 1 and / or a user equipment (UE) as illustrated in any one or more of 2.

[0122] The scheduled entity 1300 may be implemented with a processing system 1314 (or "processing device") including one or more processors 1304. Examples of processors 1304 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. In various examples, the scheduled entity 1300 may be configured to perform any one or more of the functions described herein, including but not limited to power measurement, power sharing, UL timing, and offset timing. That is, the processor 1304 as utilized in the scheduled entity 1300 may be used to implement any one or more of the processes and procedures described herein.

[0123] In this example, the processing system 1314 may be implemented with a bus architecture generally represented by bus 1302. Depending on the specific application and overall design constraints of the processing system 1314, the bus 1302 may include any number of interconnecting buses and bridges. The bus 1302 communicatively couples various circuits including one or more processors (generally represented by processor 1304), memory 1305, and computer-readable media (generally represented by computer-readable media 1306). The bus 1302 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further. The bus interface 1308 provides an interface between the bus 1302 and the transceiver 1310. The transceiver 1310 provides a communication interface or device for communicating with various other equipment over a transmission medium. Depending on the characteristics of the equipment, a user interface 1312 (e.g., a keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 1312 is optional and may be omitted in some examples.

[0124] In some aspects of the present disclosure, the processor 1304 may include a timing 1320 configured to implement, for example, the UL timing and timing offset procedures described herein, such as those described above. Figure 6-12 The power sharing circuit system 1322 may be configured, for example, for power measurement and / or power sharing, such as those described herein, and the above Figure 6-12 The technology described in .

[0125] The processor 1304 is responsible for managing the bus 1302 and general processing, including the execution of software stored on the computer-readable medium 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described below for any particular device. The computer-readable medium 1306 and the memory 1305 may also be used to store data manipulated by the processor 1304 when executing the software.

[0126] One or more processors 1304 in the processing system 1314 may execute software. Software should be broadly construed to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. The software may reside on a computer-readable medium 1306. The computer-readable medium 1306 may be a non-transitory computer-readable medium. As examples, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes), optical disks (e.g., compact disks (CDs) or digital versatile disks (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key-type drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. Computer-readable medium 1306 may reside in processing system 1314, external to processing system 1314, or distributed across multiple entities including processing system 1314. Computer-readable medium 1306 may be implemented in a computer program product. As an example, a computer program product may include a computer-readable medium in packaging materials. Those skilled in the art will recognize how to best implement the described functionality presented throughout this disclosure depending on the specific application and the overall design constraints imposed on the overall system.

[0127] In one or more examples, the computer-readable storage medium 1306 may include timing instructions 1324 configured for various functions, including but not limited to uplink timing and / or offset timing associated with the functionality of the timing processor 1320. The computer-readable storage medium 1306 may also include power sharing instructions 1326 configured for various functions, including but not limited to power measurement and power sharing associated with the functionality of the power sharing circuitry 1322.

[0128] Of course, in the above examples, the circuit system included in the processor 1314 is provided only as an example, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1306, or in Figure 1-2 and Figure 4 Any other suitable apparatus or device described in any of the foregoing and utilizing, for example, the processes and / or algorithms described herein.

[0129] Fig.14 14 is a block diagram illustrating an example of a hardware implementation of a scheduling entity 1400 employing a processing system according to some aspects. The scheduling entity 1400 is shown as employing a processing system 1414. For example, the scheduling entity 1400 may be such as Figure 1 and 2 A base station (such as an eNB, a gNB) is illustrated in any one or more of the foregoing.

[0130] The scheduling entity 1400 can be similar to the above combination Fig.13 The processing system 1414 of the processing system 1314 discussed is implemented and includes one or more processors 1404, which can be used to implement any one or more of the processes and procedures described herein. In this example, the processing system 1414 can be implemented with a bus architecture generally represented by the bus 1402. Depending on the specific application and overall design constraints of the processing system 1414, the bus 1402 may include any number of interconnecting buses and bridges. The bus 1402 communicatively couples various circuits including one or more processors (generally represented by the processor 1404), a memory 1405, and a computer-readable medium (generally represented by the computer-readable medium 1406). The bus 1402 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described. The bus interface 1408 provides an interface between the bus 1402 and the transceiver 1410. The transceiver 1410 provides a communication interface or device for communicating with various other equipment through a transmission medium (such as air). Depending on the characteristics of the equipment, a user interface 1412 (such as a keypad, display, speaker, microphone, joystick, touch screen) may also be provided. Of course, such a user interface 1412 is optional and may be omitted in some examples.

[0131] The processor 1404 is responsible for managing the bus 1402 and general processing, including the execution of software stored on the computer-readable medium 1406 or the memory 1405. The software, when executed by the processor 1404, causes the processing system 1414 to perform the various functions described herein for any particular device. The computer-readable medium 1406 and the memory 1405 may also be used to store data manipulated by the processor 1404 when executing the software. One or more processors 1404 in the processing system may execute the software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. The software may reside on a computer-readable medium 1406, which may be similar to a processor 1404. Fig.13 Computer readable media 1306 described in.

[0132] In some aspects of the present disclosure, the processor 1404 may include circuitry configured for various functions. For example, the processor 1404 may include a random access circuitry 1420 configured to implement, for example, the initial access and RACH procedures described herein, such as those described above. Figure 6-10 The CSI / CQI circuitry 1122 may be configured, for example, to implement CSI / CQI reporting processing and signaling, such as those described herein, and the above Figure 6-10 The technology described in .

[0133] In one or more examples, the computer-readable storage medium 1406 may include random access instructions 1424 configured for various functions, including but not limited to initial access and RACH processing associated with the functionality of the random access processor 1420. The computer-readable storage medium 1406 may also include CSI / CQI instructions 1426, which are configured for various functions, including but not limited to CSI / CQI report processing and signaling associated with the functionality of the CSI / CQI circuit system 1422.

[0134] Of course, in the above examples, the circuit system included in the processor 1414 is provided only as an example, and other means for performing the described functions may be included in various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1406, or in Figure 1-2 and Figure 4 Any other suitable apparatus or device described in any of the foregoing and utilizing, for example, the processes and / or algorithms described herein.

[0135] Fig.15 1 is a flow chart illustrating a process 1500 for handling timing offset in an NR-DC power sharing configuration according to some aspects. At block 1502, a scheduled entity (e.g., a UE) may determine a first timing value for a first uplink communication including first control information (e.g., MCGDCI) to a first cell group (e.g., MCG). At block 1504, the UE may determine a second timing value (T 0 ), the second uplink communication includes second control information (e.g., SCG DCI) to a second cell group (e.g., SCG). At block 1506, the UE allocates transmit power for the first and second uplink communications, and at block 1508 determines a transmit power relative to a second timing value (T 0 -T 偏移 ) timing offset value (T 偏移 ). At block 1510, the UE transmits the timing offset value to the wireless communication network, and receives scheduling information (e.g., UCI) in response to transmitting the timing offset value at block 1512. At block 1514, the UE may transmit at least one of the first uplink communication (MCG DCI) or the second uplink communication (SCG DCI) based on the scheduling information.

[0136] Several aspects of wireless communication networks have been presented with reference to exemplary implementations. As those skilled in the art will readily appreciate, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures and communication standards.

[0137] As an example, various aspects may be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile (GSM). Various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.

[0138] Within the present disclosure, the wording "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior or superior to other aspects of the present disclosure. Likewise, the term "aspect" does not require that all aspects of the present disclosure include the features, advantages, or modes of operation discussed. The term "coupled" is used herein to refer to a direct or indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, objects A and C may still be considered to be coupled to each other - even if they are not in direct physical contact with each other. For example, a first object may be coupled to a second object, even if the first object never directly contacts the second object physically. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electronic devices and conductors and software implementations of information and instructions, which, when connected and configured, enable the functions described in the present disclosure to be performed without limitation on the type of electronic circuits, which, when executed by a processor, enable the functions described in the present disclosure to be performed.

[0139] Figure 1-15 One or more of the components, steps, features, and / or functions described herein may be rearranged and / or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figure 1 , 2 , 4, 13 and 14, the devices, apparatuses and / or components illustrated may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and / or embedded in hardware.

[0140] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. Based on design preferences, it will be understood that the specific order or hierarchy of steps in these methods can be rearranged. The attached method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented unless specifically stated herein.

[0141] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the universal principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" - unless specifically stated, but intended to mean "one or more". Unless specifically stated otherwise, the term "some / some" refers to one or more. The phrase "at least one of" a list of items refers to any combination of these items, including a single member. As an example, "at least one of a, b or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. The elements of the various aspects described throughout this disclosure are all structurally and functionally equivalent solutions currently or hereafter known to those of ordinary skill in the art, and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims.

Claims

1. A method for power sharing by a scheduled entity in a wireless communication network, the method comprising: determining a first timing value for a first uplink communication, the first uplink communication comprising first control information to a first cell cluster; determining a second timing value for a second uplink communication including second control information to a second group of cells; allocating transmit power for the first uplink communication and the second uplink communication; determining a timing offset value relative to the second timing value; transmitting the timing offset value to the wireless communication network; receiving scheduling information in response to transmitting the timing offset value; as well as transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information; Wherein the method further comprises: determining a second timing offset value relative to the first timing value; determining whether the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value; transmitting only the first uplink communication if the timing offset value relative to the second timing value is not earlier in time than the second timing offset value relative to the first timing value; and The second uplink communication is only transmitted if the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value.

2. The method of claim 1, wherein the timing offset value comprises a fixed value. The method of claim 2 , wherein the fixed value comprises a time period.

4. The method of claim 2, wherein the fixed value comprises a number of transmission symbols.

5. The method of claim 4, further comprising: One of a sample index, a symbol index, a slot index, or a subframe index is measured to determine the number of transmission symbols.

6. The method of claim 1, wherein the timing offset value is determined based on uplink processing time measurements.

7. The method of claim 1, wherein the first cell cluster operates using a first frequency band and the second cell cluster operates using a second frequency band.

8. The method of claim 7, wherein the timing offset value comprises one or more first fixed values ​​associated with the first frequency band, and one or more second fixed values ​​associated with the second frequency band.

9. The method of claim 1, wherein the first control information comprises downlink control information (DCI).

10. The method of claim 1, wherein the scheduling information comprises receiving uplink control information (UPI).

11. A user equipment UE in a wireless communication network, comprising: Transceiver; Memory; as well as a processor communicatively coupled to the transceiver and the memory, wherein the processor and the memory are configured to: determining a first timing value for a first uplink communication, the first uplink communication comprising first control information to a first cell cluster; determining a second timing value for a second uplink communication including second control information to a second group of cells; allocating transmit power for the first uplink communication and the second uplink communication; determining a timing offset value relative to the second timing value; transmitting the timing offset value to the wireless communication network; receiving scheduling information in response to transmitting the timing offset value; as well as transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information; Wherein the processor and the memory are further configured to: determining a second timing offset value relative to the first timing value; determining whether the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value; transmitting only the first uplink communication if the timing offset value relative to the second timing value is not earlier in time than the second timing offset value relative to the first timing value; as well as The second uplink communication is only transmitted if the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value.

12. The UE of claim 11, wherein the timing offset value comprises a fixed value. The UE of claim 12 , wherein the fixed value comprises a time period. The UE of claim 12 , wherein the fixed value comprises a number of transmission symbols.

15. The UE of claim 14, further comprising: One of a sample index, a symbol index, a slot index, or a subframe index is measured to determine the number of transmission symbols.

16. The UE of claim 14, wherein the timing offset value is determined based on uplink processing time measurements.

17. The UE of claim 11, wherein the first cell group operates using a first frequency band and the second cell group operates using a second frequency band.

18. The UE of claim 17, wherein the timing offset value comprises one or more first fixed values ​​associated with the first frequency band, and one or more second fixed values ​​associated with the second frequency band.

19. The UE of claim 11, wherein the first control information comprises downlink control information (DCI).

20. The UE of claim 11, wherein the scheduling information comprises receiving uplink control information (UPI).

21. A user equipment UE in a wireless communication network, comprising: means for determining a first timing value for a first uplink communication, the first uplink communication comprising first control information to a first cell cluster; means for determining a second timing value for a second uplink communication, the second uplink communication comprising second control information to a second group of cells; means for allocating transmit power for said first uplink communication and said second uplink communication; means for determining a timing offset value relative to said second timing value; means for transmitting the timing offset value to the wireless communication network; means for receiving scheduling information in response to transmitting the timing offset value; as well as means for transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information; The user equipment UE further comprises: means for determining a second timing offset value relative to said first timing value; means for determining whether said timing offset value relative to said second timing value is earlier in time than said second timing offset value relative to said first timing value; means for transmitting only the first uplink communication if the timing offset value relative to the second timing value is not earlier in time than the second timing offset value relative to the first timing value; and Means for transmitting only the second uplink communication if the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value.

22. A computer readable medium having stored therein instructions executable by one or more processors to: determining a first timing value for a first uplink communication, the first uplink communication comprising first control information to a first cell cluster; determining a second timing value for a second uplink communication including second control information to a second group of cells; allocating transmit power for the first uplink communication and the second uplink communication; determining a timing offset value relative to the second timing value; transmitting the timing offset value to a wireless communication network; receiving scheduling information in response to transmitting the timing offset value; as well as transmitting at least one of the first uplink communication or the second uplink communication based on the scheduling information; Wherein the instructions are further executable by the one or more processors to: determining a second timing offset value relative to the first timing value; determining whether the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value; transmitting only the first uplink communication if the timing offset value relative to the second timing value is not earlier in time than the second timing offset value relative to the first timing value; as well as The second uplink communication is only transmitted if the timing offset value relative to the second timing value is earlier in time than the second timing offset value relative to the first timing value.

Images