Method for determining uplink transmission resource of user equipment and information technology field

Abstract

In accordance with an example embodiment of the present invention, there is at least one method and apparatus to perform: receiving a configuration for uplink transmissions on a plurality of carriers or cells, or configuring a user equipment with a configuration for uplink transmissions on a plurality of carriers or cells, determining a subset of carriers or cells for uplink reception within a plurality of carriers or cells scheduling user equipment for uplink transmissions, receiving information for at least one uplink transmission of the user equipment, wherein the information comprises: uplink transmission resources for two or more component carriers or cells, the two or more component carriers or cells being used for at least one uplink transmission; and based on the information, determining a subset of component carriers or cells on which the user equipment transmits, and identifying the transmission for each component carrier to which the transmission resource is allocated.

Description

Technical Field

[0001] The teachings of exemplary embodiments of the present invention relate to a novel method in which, when scheduling a set of UL carriers for uplink (UL) transmission for user equipment, the user equipment and the base station dynamically determine at least one uplink transmission carrier to coordinate UL transmission. Background Technology

[0002] This section is intended to provide background or context for the invention as set forth in the claims. The description herein may include concepts that may be pursued, but are not necessarily concepts that have been previously conceived or pursued. Therefore, unless otherwise stated herein, what is described in this section is not prior art to the specification and claims of this application, and is not acknowledged as prior art by virtue of its inclusion in this section.

[0003] Some abbreviations that may be found in the instruction manual and / or accompanying drawings are defined here as follows: ACK (positive confirmation) CA carrier aggregation CG Configuration License CSI Channel State Information CU Centralized Unit DC Dual Connection DCI Downlink Control Information DL downlink DU Distributed Unit FH Prequel HARQ Hybrid Automatic Repeat Request HSDPA High-Speed ​​Downlink Packet Access LTE Long Term Evolution (4G) NACK (Negative Acknowledgment) NR New Radio (5G) NW Network O-RAN (Open RAN) PCell main cell PDCCH (Physical Downlink Control Channel) PDSCH (Physical Downlink Shared Channel) PHR Power Headroom Report PUCCH (Physical Uplink Control Channel) PUSCH Physical Uplink Shared Channel RAN (Radio Access Network) RU radio unit SCell Auxiliary Community SPS (Semi-Persistent Scheduling) SRB signaling radio bearer Tx transmitter UCI uplink control information UL uplink VoNR New Radio Voice

[0004] In 3G HSDPA, 4G LTE, and 5G NR, basic downlink carrier aggregation schedules data across two or more downlink carriers, while uplink feedback is routed on a single uplink carrier. This requires the processing unit responsible for the primary cell to know what is expected in the feedback from the secondary cell and to route the relevant secondary cell information to the processing unit responsible for the secondary cell with low latency. Similarly, the processing unit of the secondary cell must be able to receive relevant feedback from the processing unit of the primary cell without delay.

[0005] The exemplary embodiments of the present invention have made improvements at least in these operations. Summary of the Invention

[0006] This section contains examples of possible implementations and does not imply any limitations.

[0007] In another exemplary aspect of the invention, there is an apparatus, such as a user equipment side apparatus, comprising: at least one processor; and at least one non-transient memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive a configuration from a user equipment of a communication network; determine, based on the configuration, that uplink transmission of information is required on a subset of carriers or cells; and send at least one uplink transmission to a network node of the communication network, the uplink transmission including: an indication identifying information transmitted on a selected subset of carriers or cells.

[0008] In another example aspect of the invention, there is a method comprising: receiving a configuration by a user equipment of a communication network; determining, based on the configuration, that uplink transmission of information is required on a subset of carriers or cells; and sending at least one uplink transmission to a network node of the communication network, the uplink transmission comprising: an indication identifying information to be transmitted on a selected subset of carriers or cells.

[0009] Another example embodiment is an apparatus and method including the foregoing paragraphs, wherein the determination is based on at least one of the following: maximum allocation, type or configuration authorization of uplink allocation, based on a selected or preferred transmitter, associated with the handover time, maximum allowed power or additional maximum power reduction for each configured uplink in the frequency band, wherein the information includes: decoding information for a component carrier used for at least one uplink transmission, wherein the configuration includes: based on the physical uplink control channel or physical uplink shared channel information to be transmitted simultaneously on the uplink component carrier. The power splitting configuration includes: a set of rules for prioritizing uplink transmission in the event of collisions between physical channels, wherein the prioritization includes: prioritizing U-plane data or C-plane data to be transmitted across component carriers based on available license size and pre-configured rules, wherein the prioritization includes: prioritizing C-plane data over U-plane data to be transmitted across component carriers based on available license size and pre-configured rules, where U-plane refers to user plane data, which is data that an end user is transmitting to a target receiver (e.g., a server, other end users), and C-plane... Control plane data (such as MAC headers or RRC messages) terminated at a radio network or end-user equipment includes at least one of the following: a Media Access Control header or a Radio Resource Control message, wherein the decoded information includes uplink control information, which includes an uplink control information header indicating data included in at least one uplink transmission, wherein the header includes an N-UCI field, which includes a pre-configured identifier and a length field. The N-UCI field is a fixed-size field, which exists together with the Physical Uplink Shared Channel for pre-decoding checks of the Physical Uplink Shared Channel. The N-UCI field also exists together with the Physical Uplink Control Channel for pre-decoding checks of the Physical Uplink Shared Channel. When data is transmitted only through at least one transmission, the N-UCI field exists as an extension of the MAC header, which is used to identify the uplink cell transmitting data on different component carriers, and / or where the configuration is received by the user equipment from a network node in the communication network.

[0010] In another exemplary aspect of the invention, there is an apparatus, such as a network-side apparatus, comprising: at least one processor; and at least one non-transient memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: configure a configuration for uplink transmission on multiple carriers or cells to a user equipment by a network node of a communication network; determine a subset of carriers or cells for uplink reception among the multiple carriers or cells scheduled to the user equipment for uplink transmission; receive information for at least one uplink transmission to the user equipment, wherein the information includes: uplink transmission resources for two or more component carriers or cells for at least one uplink transmission; and based on the information, determine a subset of component carriers or cells on which the user equipment will transmit, and identify the transmission for each component carrier on which transmission resources are allocated.

[0011] In another exemplary aspect of the invention, there is a method comprising: configuring a network node of a communication network to a user equipment for uplink transmission on multiple carriers or cells; determining a subset of carriers or cells for uplink reception among the multiple carriers or cells scheduled to the user equipment for uplink transmission; receiving information for at least one uplink transmission for the user equipment, wherein the information includes: uplink transmission resources for two or more component carriers or cells for at least one uplink transmission; and, based on the information, determining a subset of component carriers or cells on which the user equipment will transmit, and identifying the transmission for each component carrier on which transmission resources are allocated.

[0012] Another example embodiment is an apparatus and method including the foregoing paragraphs, wherein the information is based on at least one of: maximum allocation, type of uplink allocation, configuration authorization for user equipment, based on selected or preferred transmission, associated with handover time, maximum allowable power or additional maximum power reduction for each configured uplink in the frequency band at the user equipment, wherein the information includes: decoding information for component carriers used for at least one uplink transmission, wherein the configuration includes: power splitting configuration based on physical uplink control channel or physical uplink shared channel information to be simultaneously transmitted on the uplink component carriers, wherein the configuration includes: for handling collisions between physical channels, A set of rules for prioritizing uplink transmissions, wherein this prioritization includes: prioritizing U-plane data or C-plane data to be transmitted across component carriers based on available license size and pre-configured rules, wherein this prioritization includes: prioritizing C-plane data over U-plane data to be transmitted across component carriers based on available license size and pre-configured rules, wherein the U-plane refers to user plane data, which is data being transmitted by an end user to a target receiver (e.g., a server, other terminal equipment), and the C-plane refers to control plane data (such as using MAC headers or RRC messages) terminated at the radio network or end user equipment, wherein the control plane data includes at least one of the following: Media Access Control header, or Radio Resource Control header. The message is based on uplink control information, which includes an uplink control information header indicating data included in at least one uplink transmission. The header includes an N-UCI field, which comprises a pre-configured identifier and a length field. The N-UCI field is a fixed-size field and exists alongside the physical uplink shared channel for pre-decoding checks. The message is sent only after data has been transmitted through at least one transmission. At that time, the N-UCI field exists as an extension of the MAC header, which is used to identify the uplink cell transmitting data on different component carriers. It identifies the use of uplink scheduling downlink control information sent to the secondary network node of the user equipment and the communication network. It includes at least one of the following dynamically shared with the secondary network node: downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or user power margin or estimated transmission power of the user equipment. It also includes at least one of the following dynamically received from the secondary network node: downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or user power margin or estimated transmission power of the user equipment. It also includes the probability of determining the active uplink set.The method includes determining whether an active uplink of the set belongs to a secondary network node, wherein if an active uplink of the set belongs to a secondary network node, demodulating at least one of a physical uplink control channel or a physical uplink shared channel; decoding uplink control information from uplink fronthaul data of the secondary network node, wherein the decoding is successful, wherein if there is no active uplink of the secondary network node, demodulating at least one of a physical uplink control channel or a physical uplink shared channel; and decoding uplink control information based on uplink fronthaul data, which is based on shared uplink control information or configuration authorization information, and / or wherein other distributed unit data is discarded based on uplink control information indicating data for the secondary network node, which is included in at least one of a physical uplink control channel or a physical uplink shared channel.

[0013] A communication system includes a user equipment-side device and a network-side device that perform the operations described above. Attached Figure Description

[0014] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, wherein like reference numerals are used to denote like or equivalent elements. The drawings are shown to facilitate a better understanding of embodiments of the present disclosure, and are not necessarily drawn to scale. In the drawings:

[0015] Figure 1 An example configuration for carrier aggregation (CA) is shown;

[0016] Figure 2 An example of a centralized random access network (RAN) architecture is shown;

[0017] Figure 3 A flowchart for the main gNB is shown;

[0018] Figure 4 A flowchart for the auxiliary gNB is shown;

[0019] Figure 5 A flowchart for user equipment (UE) is shown;

[0020] Figure 6 A high-level block diagram of various devices used to carry out aspects of the present invention is shown; and

[0021] Figure 7A and Figure 7B Each illustrates a method that can be performed by an apparatus according to an exemplary embodiment of the invention. Detailed Implementation

[0022] In an exemplary embodiment of the present invention, at least one method and apparatus for a novel approach are proposed, wherein when scheduling a set of UL carriers for uplink (UL) transmission for user equipment, the user equipment and the base station dynamically determine at least one uplink transmission carrier to coordinate UL transmission.

[0023] As described above, in 3G HSDPA, 4G LTE, and 5G NR, basic downlink carrier aggregation schedules data across two or more downlink carriers, while uplink feedback is routed on a single uplink carrier. This requires the processing unit responsible for the primary cell to know what is expected in the feedback from the secondary cell and to route the relevant information to the processing unit responsible for the secondary cell with very low latency. Similarly, the processing unit of the secondary cell must be able to receive relevant feedback from the processing unit of the primary cell without delay.

[0024] If uplink (UL) carrier aggregation (CA) is also supported, the location of uplink control information in LTE and NR dynamically depends on what is transmitted in the uplink: UL CA or UL switching (two uplinks): PUSCH only on the main UL: main UCI; Only PUSCH has a secondary UL and a secondary UCI; PUSCH addresses both primary and secondary UL: Primary UCI: o Power priority rules and individual UL operations (UL Tx switching) are added to hybrid UL; PUSCH occurs on the primary UL (only if there is no PUSCH in the uplink: primary UCI).

[0025] The fact that UCI is sometimes on the primary UL and sometimes on the secondary UL further complicates the management of uplink control information in non-monolithic base station architectures.

[0026] In contrast, bidirectional connections assume two unassigned base stations connected to the same UE, with feedback issues resolved by the UE having a dedicated uplink connection to each base station. The problem with this is that the UE needs to support transmissions on both uplinks simultaneously, and it also requires Tx power to be split between the two uplinks, thus reducing the coverage that each uplink can support. In some cases, the UE can be restricted to operating two uplinks simultaneously to avoid intermodulation problems.

[0027] In all the aforementioned scenarios where multiple ULs are involved, better coordination of UL transmissions is needed. In NR, EN-DC usage based on simultaneous UL transmissions over LTE and NR does not employ any power-sharing rules, but relies on hard power splitting between the LTE and NR uplinks. Dynamic power control interaction is difficult to implement within 4G and 5G chipsets. Chipset manufacturers are unwilling to handle this complexity, requiring network vendors to bear the implementation burden.

[0028] Furthermore, for NR capacity expansion in scenarios where DU is not allocated, inter-site CA (two sites send downlink, only one site receives uplink) may be preferred over NR DC. Inter-site CA has also been implemented for LTE, but its adoption is low due to the inherent latency in forwarding data from PCell to SCell, which in some deployments prevents reliance on a single uplink CA (or similar CA) operation that provides uplink feedback for all downlinks.

[0029] However, there is a question of how to support carrier aggregation with a non-monolithic base station architecture without requiring two uplinks, and how to avoid latency issues caused by routing control information between processing units.

[0030] The use of proprietary interfaces between processing units (DU, gNB, base station, cell site) to route UCI received by one processing unit to another processing unit causes latency. In some deployments, this prevents CA (or similar CA) operations that rely on a single uplink to provide uplink feedback for all downlinks.

[0031] The existing technology here is based on a reactive approach that forwards UCI data for the SCell after the SCell has been received by the PCell.

[0032] This results in latency penalties that impact all end-to-end throughput performance, or may render support for CA (or similar CA) operations infeasible. The solution proposed here employs an active or initiating approach to notify the SCell when and where UCI and / or UL data can be sent.

[0033] As described below, the term O-RAN is used, but the concept should be understood more broadly in the case where RU refers to the radio unit connected to DU, which is the BB processing unit.

[0034] Before describing the exemplary embodiments disclosed herein in detail, refer to Figure 6 , Figure 6 Simplified block diagrams illustrating various electronic devices suitable for practicing exemplary embodiments of the present invention.

[0035] Figure 6A block diagram of a possible, non-limiting, exemplary system in which example embodiments can be practiced is shown. Figure 6 In this context, User Equipment (UE) 10 and Wireless Network 1 or as... Figure 6 Network 1, as shown, enables wireless communication. Figure 6 The wireless network 1 or network 1 in the document may include a communication network (such as a mobile network), for example, mobile network 1 or a first mobile network as disclosed herein. This document refers to... Figure 6 Any reference to wireless network 1 in this document can be regarded as a reference to any wireless network disclosed herein. Furthermore, as... Figure 6 The wireless network 1 in the RAN may also include hard-wired features that the communication network may require. The UE is wireless and is typically a mobile device that can access the wireless network. For example, the UE may be a mobile phone (or "cellular" phone) and / or a computer with mobile terminal capabilities. For example, the UE or mobile terminal may also be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device that performs voice signaling and / or data exchange with the RAN.

[0036] UE 10 includes one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected via one or more buses. Each transceiver in the one or more transceivers TRANS 10D includes a receiver and a transmitter. The one or more buses may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cable, or other optical communication device. The one or more transceivers TRANS 10D may optionally be connected to one or more antennas for communicating with NN 12 and NN 13 respectively. The one or more memories MEM 10B include computer program code PROG 10C. UE 10 communicates with NN12 and / or NN 13 via wireless links 11 or 16.

[0037] NN 12 (NR / 5G Node B, evolved NB, or LTE equipment) is related to equipment (such as...) Figure 6The NN 12 provides access to wireless devices (such as UE 10) to the wireless network 1 via one or more networks (NN 13 and UE 10). The NN 12 includes one or more processors DP 12A, one or more memories MEM 12B, and one or more transceivers TRANS 12D interconnected via one or more buses. According to an example embodiment, these TRANS 12Ds may include X2 and / or Xn interfaces for use in performing the example embodiment. Each of the one or more transceivers TRANS 12Ds includes a receiver and a transmitter. The one or more transceivers TRANS 12Ds may optionally be connected to one or more antennas for communicating with UE 10 at least on link 11. One or more memories MEM 12B and computer program code PROG 12C are configured, together with one or more processors DP 12A, to cause the NN 12 to perform one or more of the operations described herein. NN 12 can communicate (e.g., via link 16) with another gNB, or eNB, or device (such as NN 13). Furthermore, link 11, link 16, and / or any other link can be wired, wireless, or both, and can implement, for example, an X2 or Xn interface. Additionally, link 11 and / or link 16 can communicate via other network devices, such as, but not limited to, […]. Figure 6 The NN 12 is an NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 device. It can perform the functions of MME (Mobility Management Entity) or SGW (Serving Gateway), such as user plane functions, and / or access management functions for LTE, as well as similar functions for 5G.

[0038] NN 13 can be used for WiFi or Bluetooth or other wireless devices associated with mobile function devices (such as AMF or SMF). Furthermore, NN 13 may include NR / 5G node B or possible evolved NB, base stations (such as primary or secondary node base stations) (e.g., for NR or LTE LTE), which communicate with devices (such as NN 12 and / or UE 10 and / or Wireless Network 1). NN 13 includes one or more processors DP 13A interconnected via one or more buses, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS 13D. According to an example embodiment, these network interfaces of NN 13 may include X2 and / or Xn interfaces for use in performing the example embodiment. Each transceiver in the one or more transceivers TRANS 13D includes a receiver and a transmitter, which may optionally be connected to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For example, one or more memory MEM 13B and computer program code PROG 13C are configured, together with one or more processors DP 13A, to cause NN 13 to perform one or more of the operations described herein. NN 13 can communicate with another mobility function device and / or eNB (such as NN 12 and UE 10) or any other device, for example, via link 11, or link 16, or another link. Figure 6 Link 16 shown can be used to communicate with NN 12. These links can be wired, wireless, or both, and can implement, for example, an X2 or Xn interface. Furthermore, as mentioned above, links 11 and / or 16 can be connected via other network devices, such as, but not limited to, NCE / MME / SGW devices (such as...). Figure 6 NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14).

[0039] Figure 6 One or more buses of the device can be address, data, or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic or other optical communication devices, wireless channels, etc. For example, one or more transceivers TRANS 12D, TRANS 13D, and / or TRANS 10D can be implemented as remote radio heads (RRHs), while other components of the NN 12 are physically located at a different location from the RRHs, and these devices can include one or more buses, which can be partially implemented as fiber optic cables to connect other components of the NN 12 to the RRHs.

[0040] It should be noted that, although Figure 6Network nodes (such as NN 12 and NN 13) are shown, but any of these nodes can be incorporated into or be incorporated into an eNodeB, eNB, or gNB (such as for LTE and NR), and will still be configured to perform the example implementation.

[0041] Furthermore, it should be noted that the description herein refers to a "cell" performing functions; however, it should be clear that the gNB and / or user equipment and / or mobility management function equipment that form the cell will perform these functions. Additionally, a cell constitutes part of a gNB, and each gNB may have multiple cells.

[0042] Wireless Network 1 or any network that it may represent may include or may not include NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14, which may include (NCE) network control element functions, MME (Mobility Management Entity) / SGW (Serving Gateway) functions, and / or Serving Gateway (SGW), and / or MME (Mobility Management Entity) and / or SGW (Serving Gateway) functions, and / or User Data Management (UDM) functions, and / or PCF (Policy Control) functions, and / or Access and Mobility Management (AMF) functions, and / or Session Management (SMF) functions, and / or Location Management (LMF) functions, and / or Authentication Server (AUSF) functions, and provide connectivity to another network (such as a telephone network and / or a data communication network (e.g., the Internet)), and is configured to perform any 5G and / or NR operations other than or in lieu of other standard operations during the term of this application. NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 can be configured to perform operations in LTE, NR, 5G, and / or any standards-based communication technology performed or discussed within the timeframe of this application, according to example embodiments. Furthermore, it should be noted that operations according to example embodiments, such as those performed by NN 12 and / or NN 13, can also be performed at NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0043] NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 includes one or more processor DP 14A interconnected via one or more buses coupled to link 13 and / or link 16, one or more memory MEM 14B, and one or more network interfaces ((multiple) N / WI / F). According to an example embodiment, these network interfaces may include X2 and / or Xn interfaces for use in performing the example embodiment. One or more memory MEM 14B includes computer program code PROG 14C. The one or more memory MEM 14B and computer program code PROG 14C are configured, together with the one or more processor DP 14A, to cause NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 to perform one or more operations that may be required to support the operation according to the example embodiment.

[0044] It should be noted that NN 12 and / or NN 13 and / or UE 10 can be configured (e.g., based on standard implementations, etc.) to perform Location Management Function (LMF) functionality. LMF functionality can be embodied in any of these network devices or other devices associated with them. Furthermore, at least as described below, LMF (such as...) Figure 6 The MME / SGW / UDM / PCF / AMF / SMF / LMF 14 (LMF) can co-address with UE 10, such as with Figure 6 The NN 12 and / or NN 13 are separated for performing operations according to the example embodiments disclosed herein.

[0045] Wireless Network 1 can implement network virtualization, which is the process of combining hardware and software network resources, as well as network functions, into a single, software-based managed entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as external, combining many networks, or parts of networks, into virtual units, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented to some extent using hardware (such as processors DP 10, DP 12A, DP 13A, and / or DP 14A, and memory MEM 10B, MEM 12B, MEM 13B, and / or MEM 14B), and such virtualized entities produce technical effects.

[0046] Computer-readable storage devices MEM 12B, MEM 13B, and MEM 14B can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Computer-readable storage devices MEM 12B, MEM 13B, and MEM 14B can be components for performing storage functions. As a non-limiting example, processors DP 10, DP 12A, DP 13A, and DP 14A can be of any type suitable for the local technical environment and can include any of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors DP 10, DP 12A, DP 13A, and DP 14A can be components for performing functions such as controlling UE 10, NN 12, NN 13, and other functions described herein.

[0047] Generally, various embodiments of any of these devices may include, but are not limited to: cellular phones (such as smartphones), tablets, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices (such as digital cameras with wireless communication capabilities), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablets with wireless communication capabilities, and portable units or terminals that embed a combination of such functions.

[0048] Furthermore, various embodiments of any of these devices can be used with any other node of this type associated with a UE vehicle, an aerial platform station, or a ground network or any type of drone radio, or a radio in an aircraft or other air vehicle or a vessel traveling on water (such as a ship).

[0049] Figure 1 An example configuration for carrier aggregation (CA) is shown.

[0050] like Figure 1 As shown, according to an exemplary embodiment of the present invention, the uplink of the UE is received in the radio unit (RU) and routed to two processing units, the distributed unit (DU) (see...). Figure 1 ).

[0051] When scheduling a UE in the downlink, the DU forwards its downlink scheduling downlink control information (DCI) scheduling message to the UE to other DUs. There is an inherent latency tolerance here, as it takes time for the UE to receive the corresponding PDSCH and begin sending HARQ-ACK. Similarly, when scheduling a UE in the uplink, the uplink scheduling DCI is sent by the scheduling DU to other DUs, and there is a minimum latency from the UE receiving the DCI before the UE can begin sending the corresponding PUSCH. The interfaces used for these exchanges can be high-speed interfaces for inter-vendor CA and for 5G-6G dynamic spectrum sharing in 3GPP.

[0052] Each DU will demodulate the same uplink and extract uplink control information (UCI) consisting of HARQ-ACK and / or CSI reports from the uplink transmission (PUCCH or PUSCH) when needed.

[0053] If this configuration results in a separate uplink being configured, then a decision rule regarding whether to transmit two or only one (and which) uplink is in effect, and the UE dynamically determines its (multiple) uplink transmission carriers based on this decision rule. Due to their knowledge of each other's DCIs, the two DUs can track the dynamics and know on which uplink the expected PUSCH and / or UCI is expected, and what type the expected UCI is on that uplink.

[0054] In this scenario, the UE may determine its UL based, for example, on the maximum received UL grant (DCI or configuration grant), or on the currently selected transmitter and associated handover time, or on the maximum allowed power of each configured UL and AMPR in the frequency band. Regardless of how the UE performs this determination, it is free to select (multiple) ULs, and the expected UL information DU will have to perform at most N assumptions about where the ULs are transmitted, where N is the number of ULs configured for the UE. The value of N can be reduced using some policies / rules from the network to the UE.

[0055] When a UE needs to transmit UL data / control information for more than one UL and selects only one UL for transmission, it can include a new control information field (denoted as N-UCI) within the UL transmission to indicate how each cell should perform decoding of the transmitted UL information. This N-UCI field can be simply a field indicating the expected UL cell based on a pre-configured identifier, and another field with a length in bits / bytes for the payload of that cell.

[0056] N-UCI can be a fixed-size field that is at least one of the following: It always exists alongside PUSCH and is used in a similar manner as UCI-on-PUSCH, allowing this field to be checked before proceeding with PUSCH decoding. MAC header extensions (when used only to determine what data is being sent on the PUSCH); and / or Extend the UCI field on PUCCH if needed.

[0057] This information is used to determine which uplink cell the data received on the transmitted carrier was initially intended to be sent to. This is not clearly known from the network-side DCI, because the UE maps uplink data from its buffers to the scheduled carriers in priority order, but the network does not know in advance which bearer's data ends on the transmitted PUSCH. This, of course, also increases robustness to lost DCI errors. Through this N-UCI field, the UE may, for example, select the larger of two received UL grants for transmission in the same time slot, and then prioritize this information, for which deprecated grants are intended to, for example, prioritize VoNR or SRB data, which may only be configured for PCells without CA or DC.

[0058] Note that the regular UCI on the PUCCH can be deterministically known by the base station, for example, assuming what HARQ-ACK and / or what CSI exist. Furthermore, the UE's priority transmission rules can participate when data is transmitted, although N-UCI may not be needed when there is no data, which can be the case when only the PUCCH is transmitted.

[0059] Note that this solution is applicable to LTE, 5G, and 6G. For LTE, in the absence of progress in uplink selection and the introduction of N-UCI, the framework can be limited to working with existing base stations.

[0060] Figure 2 An example of a centralized random access network (RAN) architecture is shown.

[0061] For example, such as Figure 2 The centralized RAN (C-RAN) architecture described herein is primarily designed for urban areas that typically require capacity expansion. As mentioned above, this solution requires that the RU receiving the UL be routed to at most one DU.

[0062] It can be observed how multiple RUs are remotely deployed and then accessed via a transport network to a centralized location where all DU processes are completed. In these deployments, transports at the C-RAN location are typically handled by a fronthaul gateway (FH GW), which then routes the different input / output streams to the desired locations. Therefore, enabling the above requirement can be a simple configuration change to forward incoming UL data from one RU to more than one endpoint.

[0063] The flowcharts used for the main gNB, auxiliary gNB, and UE are in Figure 2 , Figure 3 , Figure 4 ,as well as Figure 5 The novel steps are described in the text, with the novel steps indicated by double asterisks. Annotation.

[0064] The primary gNB is named this way because, for example, simultaneous UL transmission is not possible if required (see...). Figure 5 If so, then the UE can default all UL transmissions to one of the gNBs.

[0065] Figure 3 A flowchart for the main gNB is shown.

[0066] like Figure 3 As shown in step 10, the UE is configured with at least two DL component carriers, and when there is more than one UL, such as Figure 3 When configured as shown in step 20, the UE can also receive configurations that help determine how to send UL information.

[0067] As in the exemplary embodiments of the present invention Figure 3 As shown in step 20 of the double star, there exists a rule by which the gNB configures the UE using optional uplink conflict resolution, uplink power splitting, and / or preferred uplink.

[0068] like Figure 3 As shown in step 30, there is a UL semi-static configuration that shares a UE with another or other DU.

[0069] This configuration can provide the UE with a set of rules, such as preferred UL for transmission at any time when simultaneous UL transmission is required, or how power splitting is performed depending on the PUCCH / PUSCH information to be transmitted on each UL branch. These rule sets can also include strategies on how to prioritize UL transmission in the event of a conflict between PUSCH and RACH, for example, in

[30] , the DU involved in the CA configuration shares information about the UE's semi-static UL configuration, such as RACH, periodic PUCCH timing, PUCCH configuration, etc.

[0070] As in the exemplary embodiments of the present invention Figure 3 As shown in step 40 of the double star configuration, there is authorization to dynamically share downlink control information of CG / SPS configuration with other distributed units, and / or optionally share user equipment power margin and / or estimated transmission power.

[0071] As in the exemplary embodiments of the present invention Figure 3 As shown in step 50 of the double star configuration, there is a dynamic reception of provided downlink control information (DCI) authorization or CG / SPS configuration from another or auxiliary distributed unit, and optionally, reception of user equipment power margin and / or estimated transmission power.

[0072] like Figure 3 As shown in step 60, there is an attempt to demodulate PUCCH and / or PUSCH, and decode UCI.

[0073] In [steps 40 and / or 50], the DUs involved in the CA configuration dynamically share DCI or configuration authorization or semi-persistent information for configuring the UE with CA. Additionally, the DUs may share information about the UE PHR or estimated transmission power. In

[60] , the primary gNB attempts to demodulate the PUCCH and / or PUSCH and decodes the new N-UCI field. If it encounters multiplexed new N-UCI fields indicating information from different UL branches, it discards data from the other UL branches

[70] .

[0074] As in the exemplary embodiments of the present invention Figure 3 As shown in step 70 of the double asterisk, if it is determined that the uplink control information indicates that the data for another or secondary distributed unit is included in the PUSCH or PUCCH, then the data of that other or secondary distributed unit may be discarded.

[0075] like Figure 3 As shown in step 80, there is a situation where data is sent to the corresponding endpoint (e.g., a higher layer, a scheduler, or a PHY function / service).

[0076] exist Figure 3 In step

[80] , the gNB proceeds to normal operation and forwards the received data to its intended recipient.

[0077] Figure 4 A flowchart for a secondary gNB is described. When the UE cannot transmit on more than one UL, it is also possible to configure all DUs within the CA configuration as secondary gNBs if no single preferred UL is available for transmission. The initial steps of gNB operation in this mode are similar to those of the primary gNB [10-50].

[0078] First, note that... Figure 4Steps 10, 20, 30, 40, and 50 Figure 3 The steps are the same.

[0079] As in the exemplary embodiments of the present invention Figure 4 As shown in step 55 with the double asterisk, there are additional steps 55, 60, 70, 80, 90 and 100 shown.

[0080] According to such Figure 4 The exemplary embodiments of the present invention shown are as follows: Figure 3 and Figure 4 The differences between them are Figure 4 The step

[55] appears where the gNB must determine all possible ULs where the UE can send them.

[0081] If in Figure 4 At step 55, the gNB determines that there is a high probability that the UE will select its configured UL for UL transmission

[70] , then the active uplink set will be determined, and it will continue to attempt to decode the UL received from its RU via FH.

[0082] As in the exemplary embodiments of the present invention Figure 4 As shown in step 55 of the double asterisk, there exists a determined active uplink or a set of active uplinks.

[0083] Here, the probability of each UL within the active UL set can be determined based, for example, the exchanged PHR information and the expected UL transmission in a given time slot. Using this information, the gNB can predict whether the UE will be able to adopt a synchronous UL. Note, however, that this is only a prediction, as radio conditions can vary, and therefore the UL power requirements for each branch will also vary accordingly, and the gNB PHR may also be slightly outdated.

[0084] As in the exemplary embodiments of the present invention Figure 4 As shown in step 60 of the dual-star system, it is determined whether the active uplink belongs to another or an auxiliary gNB or base station.

[0085] As in the exemplary embodiments of the present invention Figure 4 As shown in step 70 of the double star system, there are identified active uplinks and attempts are made to demodulate PUCCH and / or PUSCH, and decode the UCI from the uplink FH data of the secondary base station.

[0086] As in the exemplary embodiments of the present invention Figure 4 As shown in step 80 of the double asterisk, there is a determination of whether the decoding was successful.

[0087] If decoding fails [for example, in] Figure 4In step 80 of the double asterisk configuration, according to an example embodiment of the present invention, the gNB will attempt to decode the UL of the fronthaul data received from another cell configured with UL within the CA configuration. Figure 4 The double star step 90].

[0088] As in the exemplary embodiments of the present invention Figure 4 As shown in step 90 of the double star symbol, there exists for Figure 4 If decoding fails in step 80, such as Figure 4 As shown in step 90, there is an attempt to demodulate PUCCH and / or PUSCH based on the master base station uplink FH data according to the shared UL DCI / CG information, and decode UCI.

[0089] Then, as in the example embodiments of the present invention Figure 4 As shown in step 100 of the double asterisk, if the UCI indicates that data for other DUs is included in the PUCCH and / or PUSCH, then the other DU data is discarded.

[0090] In this scenario, because DCI and other UL scheduling information are exchanged dynamically, if UL information is sent via the selected UL, the auxiliary gNB knows exactly where the UL information is located. After the UL is determined, the gNB uses the new N-UCI field to select its corresponding data and discards the remaining data [as shown in step 100].

[0091] like Figure 4 As shown in step 110, there is a situation where data is sent to the corresponding endpoint (e.g., a higher layer, a scheduler, or a PHY (function / service)).

[0092] Figure 5 A flowchart for user equipment is described.

[0093] From the UE's perspective ( Figure 5 From this perspective, in Figure 5 In step

[10] , the UE is configured with at least two ULs.

[0094] like Figure 5 As shown in step 10, there is a configuration for receiving at least two uplinks (ULs).

[0095] As in the exemplary embodiments of the present invention Figure 5 As shown in step 20 of the double star, there is a configuration for receiving rules for optional uplink conflict resolution, uplink power allocation, and / or preferred UL.

[0096] UE can receive devices with, for example Figure 5The rule set in step

[20] regarding how to perform power splitting (if it supports simultaneous transmission) based on what it needs to transmit on each UL branch, determines the preferred UL in cases where simultaneous transmission cannot be performed. These rule sets may also include strategies on how to prioritize UL transmissions, for example, in the event of a conflict between PUSCH and RACH.

[0097] exist Figure 5 In step 30, the UE detects the need for simultaneous transmission on more than one UL branch.

[0098] exist Figure 5 In step 40, the UE determines whether it will perform UL transmission on more than one UL tributary or will transmit only on a single UL. This determination can be based on existing technology processes such as the available power on each tributary and the UE's ability to perform simultaneous transmissions. If the UE determines that it does indeed have the capability to transmit on two tributaries, it proceeds according to... Figure 5 The prior art state shown in step 50 is carried out.

[0099] As in the exemplary embodiments of the present invention Figure 5 As shown in step 60 of the double star, there are preferred branches for uplink transmission of information for both ULs, as shown in step 60, based on power limitations for simultaneous transmission or operation in a single transmission chain.

[0100] If the UE determines that it does not have the capability to transmit on both UL branches, then in Figure 5 In step 60, the UE determines the preferred tributary for UL transmission. If the UE is configured for more than two ULs, in this step the UE will determine its preferred tributary for transmission within its capabilities. The selection of this preferred tributary can be based solely on the configuration from the gNB (e.g., Figure 5 Step 20), or it can be based on, for example, the size of the available license, or the currently configured UL, and the transition time for switching ULs.

[0101] As in the exemplary embodiments of the present invention Figure 5 As shown in step 70 of the double asterisk, there are rules that prioritize U-plane and C-plane data to be transmitted on the preferred tributary based on the available license size and pre-configured rules. Note that the U-plane refers to user plane data, i.e., data that the end user is sending to the target receiver (e.g., a server, other end users), while the C-plane refers to control plane data that terminates at the wireless network or end user equipment, such as using MAC headers or RRC messages.

[0102] The control plane is the part of the network that controls how data packets are forwarded; that is, how data is sent from one place to another. For example, the process of creating routing tables is considered part of the control plane. Routers use various protocols to identify network paths, and they store these paths in routing tables.

[0103] Some examples of control plane protocols include routing protocols (such as BGP, OSPF, and IS-IS), network management protocols (SNMP), and application layer protocols (such as HTTP and FTP).

[0104] The data plane (sometimes called the user plane, forwarding plane, carrier plane, or bearer plane), control plane, and management plane, which carry user services, are the three basic components of a telecommunications architecture.

[0105] Then, as in the example embodiments of the present invention Figure 5 As shown in step 80 of the double asterisk, there is a UCI header indicating the data included in each transmission branch.

[0106] In steps 70-80, after the preferred UL is selected, the UE prioritizes the data to be transmitted within the selected license and includes a new N-UCI field to facilitate decoding at different UL cells.

[0107] like Figure 5 As shown in step 90, there is uplink data being sent.

[0108] In addition, Figure 5 Note that in another exemplary embodiment of the invention, UL DCIs are interchanged, and the predetermined UL can be based on, for example, the largest UL TBS size.

[0109] Note that for UEs configured with a single UL, there is no significant impact on the UE side.

[0110] Note that although the above description may be based on a CA scenario, the same exact logic applies to DC deployments.

[0111] Figure 7A and Figure 7B Each illustrates a method that can be performed by an apparatus according to an exemplary embodiment of the invention.

[0112] Figure 7A The diagram illustrates what can be achieved by network devices (such as, but not limited to, user terminals) or user equipment (such as...). Figure 6 The operations performed by UE10 in the example. Figure 7A As shown in step 710, there is a configuration received by a user equipment of the communication network. Figure 7AAs shown in step 720, based on this configuration, it is determined that uplink transmission of information is required on a carrier or a subset of cells. Then, as... Figure 7A As shown in step 730, at least one uplink transmission is sent to a network node of the communication network, the uplink transmission including: an indication of information being transmitted in a selected subset of a carrier or cell.

[0113] According to the example embodiments described in the preceding paragraphs, the determination is based on at least one of the following: maximum allocation, type or configuration authorization of uplink allocation, based on selected or preferred transmitters, associated with handover time, maximum allowed power or additional maximum power reduction for each configured uplink in the frequency band.

[0114] According to the example embodiment described in the preceding paragraphs, the information includes: decoding information for a component carrier used for at least one uplink transmission.

[0115] According to the example embodiment described in the preceding paragraphs, the configuration includes: a power splitting configuration based on physical uplink control channel or physical uplink shared channel information to be transmitted simultaneously on uplink component carriers.

[0116] According to the example embodiment described in the preceding paragraphs, the configuration includes a set of rules for prioritizing uplink transmissions in the event of a conflict between physical channels.

[0117] According to the example embodiment described in the preceding paragraphs, the prioritization includes prioritizing u-plane data or c-plane data to be transmitted across component carriers based on the available license size and pre-configured rules.

[0118] According to the example embodiment described in the preceding paragraphs, the prioritization includes: based on the available license size and pre-configured rules, c-plane data is given priority over u-plane data to be transmitted across component carriers.

[0119] According to the example embodiments described in the preceding paragraphs, where the u-plane refers to user plane data, which is data that an end user is sending to a target receiver (e.g., a server, another end user), and the c-plane refers to control plane data that terminates at the radio network or end user equipment, such as using MAC headers or RRC messages.

[0120] According to the example embodiments described in the preceding paragraphs, the control plane data includes at least one of the following: a media access control header or a radio resource control message.

[0121] According to the example embodiment described in the preceding paragraphs, the decoded information includes uplink control information, which includes an uplink control information header indicating data included in each uplink transmission in at least one uplink transmission.

[0122] According to the example embodiment described in the paragraphs above, the header includes an N-UCI field.

[0123] According to the example embodiment described in the above paragraphs, the N-UCI field includes a pre-configured identifier and a length field.

[0124] According to the example embodiment described in the paragraphs above, the N-UCI field is a fixed-size field.

[0125] According to the example embodiment described in the preceding paragraphs, the N-UCI field exists together with the physical uplink shared channel for use in checking prior to decoding the physical uplink shared channel.

[0126] According to the example embodiment described in the preceding paragraphs, the N-UCI field exists together with the physical uplink control channel for use in checking prior to decoding of the physical uplink shared channel.

[0127] According to the example embodiment described in the paragraphs above, the N-UCI field exists as an extension of the MAC header when only data is sent via at least one transmission.

[0128] According to the example embodiment described in the preceding paragraphs, the header is used to identify the uplink cell that transmits data on different component carriers.

[0129] According to the example embodiment described in the preceding paragraphs, the configuration is received by the user equipment from a network node of the communication network.

[0130] A stored procedure code (such as) Figure 6 Non-transient computer-readable media (such as PROG 10C) Figure 6 (MEM 10B in the example), the program code is generated by at least one processor (such as...) Figure 6 The DP 10A in the above section is executed to perform at least the operations described in the paragraphs above.

[0131] According to embodiments of this disclosure as described above, there exists an apparatus comprising: a user equipment (such as a communication network) for use with a communication network. Figure 6 UE 10 in the middle receives the configured components (such as Figure 6One or more transceivers 10D; MEM 10B; PROG 10C; and DP 10A); components used to determine, based on this configuration, the uplink transmissions of information that need to be performed on a subset of the carrier or cell (such as... Figure 6 One or more transceivers 10D; MEM 10B; PROG 10C; and DP 10A); and components for sending at least one uplink transmission to network nodes of the communication network (such as... Figure 6 The uplink transmission includes one or more transceivers 10D, MEM 10B, PROG 10C, and DP 10A, which identify information being transmitted in a selected subset of a carrier or cell.

[0132] In an example aspect of this disclosure according to the foregoing paragraphs, the components for at least receiving, determining, and transmitting include: components encoded with a computer program [such as...]. Figure 6 Non-transient computer-readable media [such as PROG 10C] Figure 6 [MEM10B in the image], the computer program can be generated by at least one processor [such as...] Figure 6 Execute DP 10A in [the context of the command].

[0133] Figure 4 Figure B illustrates a network that can be constructed by network nodes (such as, but not limited to, ...). Figure 6 The operations performed by gNB or eNB, NN 12 or NN 13 in the Nylon. For example... Figure 7B As shown in step 750, there is a configuration provided by a network node of the communication network to the user equipment for uplink transmission on multiple carriers or cells. Figure 7B As shown in step 755, within a plurality of carriers or cells scheduled to the user equipment for uplink transmission, a subset of carriers or cells for uplink reception is determined. Figure 7B As shown in step 760, there is information received regarding at least one uplink transmission for the user equipment. Figure 7B As shown in step 770, the information includes: uplink transmission resources for two or more component carriers or cells, where the two or more component carriers or cells are used for at least one uplink transmission. Then as... Figure 7B As shown in step 780, based on this information, a subset of component carriers or cells on which the user equipment transmits is determined, and the transmission is identified for each component carrier on which transmission resources are allocated.

[0134] According to the example embodiments described in the preceding paragraphs, the information is based on at least one of the following: maximum allocation, type of uplink allocation, configuration authorization for user equipment, selected or preferred transmission, and, in association with handover time, maximum allowable power or additional maximum power reduction for each configured uplink in the frequency band at the user equipment.

[0135] According to the example embodiment described in the preceding paragraphs, the information includes: decoding information for a component carrier used for at least one uplink transmission.

[0136] According to the example embodiment described in the preceding paragraphs, the configuration includes: a power splitting configuration based on physical uplink control channel or physical uplink shared channel information to be transmitted simultaneously on uplink component carriers.

[0137] According to the example embodiment described in the preceding paragraphs, the configuration includes a set of rules for prioritizing uplink transmissions in the event of a conflict between physical channels.

[0138] According to the example embodiment described in the preceding paragraphs, the prioritization includes prioritizing u-plane data or c-plane data to be transmitted across component carriers based on the available license size and pre-configured rules.

[0139] According to the example embodiment described in the preceding paragraphs, the prioritization includes: based on the available license size and pre-configured rules, c-plane data is given priority over u-plane data to be transmitted across component carriers.

[0140] According to the example embodiments described in the preceding paragraphs, where the u-plane refers to user plane data, which is data that an end user is sending to a target receiver (e.g., a server, another end user), and the c-plane refers to control plane data that terminates at the radio network or end user equipment, such as using MAC headers or RRC messages.

[0141] According to the example embodiments described in the preceding paragraphs, the control plane data includes at least one of the following: a media access control header or a radio resource control message.

[0142] According to the example embodiment described in the preceding paragraphs, the information is based on uplink control information, which includes an uplink control information header that indicates data included in each uplink transmission in at least one uplink transmission.

[0143] According to the example embodiment described in the paragraphs above, the header includes an N-UCI field.

[0144] According to the example embodiment described in the above paragraphs, the N-UCI field includes a pre-configured identifier and a length field.

[0145] According to the example embodiment described in the paragraphs above, the N-UCI field is a fixed-size field.

[0146] According to the example embodiment described in the preceding paragraphs, the N-UCI field exists together with the physical uplink shared channel for use in checking prior to decoding the physical uplink shared channel.

[0147] According to the example embodiment described in the preceding paragraphs, the N-UCI field exists together with the physical uplink control channel for use in checking prior to decoding of the physical uplink shared channel.

[0148] According to the example embodiment described in the paragraphs above, the N-UCI field exists as an extension of the MAC header when only data is sent via at least one transmission.

[0149] According to the example embodiment described in the preceding paragraphs, the header is used to identify the uplink cell that transmits data on different component carriers.

[0150] According to the example embodiments described in the preceding paragraphs, uplink scheduling downlink control information is identified using secondary network nodes sent to the user equipment and the communication network.

[0151] According to the example embodiments described in the preceding paragraphs, at least one of the following is dynamically shared with the secondary network nodes: downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or user power margin or estimated transmission power of user equipment.

[0152] According to the example embodiments described in the preceding paragraphs, at least one of the following is dynamically received from the secondary network node: downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or user power margin or estimated transmission power of user equipment.

[0153] According to the example embodiment described in the above paragraphs, there is a probability of determining a set of active uplinks; and whether the active uplinks of the set belong to secondary network nodes.

[0154] According to the example embodiments described in the preceding paragraphs, there is at least one of demodulating a physical uplink control channel or a physical uplink shared channel based on the existence of an active uplink belonging to a secondary network node; and decoding uplink control information from uplink fronthaul data of the secondary network node.

[0155] According to the example embodiment described in the above paragraphs, there is a process for determining whether decoding was successful.

[0156] According to the example embodiments described in the preceding paragraphs, there is at least one of demodulating the physical uplink control channel or the physical uplink shared channel based on the absence of an active uplink belonging to a secondary network node; and decoding uplink control information based on uplink fronthaul data, which is based on shared uplink control information or configuration authorization information.

[0157] According to the example embodiments described in the preceding paragraphs, there exists a method for discarding other distributed unit data based on uplink control information indicating data for secondary network nodes, wherein the uplink control information is included in at least one of a physical uplink control channel or a physical uplink shared channel.

[0158] A stored procedure code (such as) Figure 6 Non-transient computer-readable media (such as PROG 12C and / or PROG 13C) Figure 6 (MEM 12B and / or MEM 13B in the example), the program code is handled by at least one processor (such as... Figure 6 DP 12A and / or DP 13A in the above section are executed to perform at least the operations described in the paragraphs above.

[0159] According to the example embodiments described in the preceding paragraphs, there exists an apparatus comprising: a means for communication networks (such as...) Figure 6 Network nodes in network 1) (such as Figure 6 NN 12 and / or NN 13) are components that configure the user equipment for uplink transmission on multiple carriers or cells (such as NN 12 and / or NN 13). Figure 6 One or more transceivers 12D and / or 13D; MEM 12B and / or MEM 13B; PROG 12C and / or PROG 13C; and DP 12A and / or DP 13A, are used by network nodes (such as...) Figure 6 NN 12 and / or NN 13) are components that determine a subset of carriers or cells for uplink reception within a plurality of carriers or cells scheduled to user equipment for uplink transmission. Figure 6 One or more transceivers 12D and / or 13D; MEM 12B and / or MEM 13B; PROG 12C and / or PROG 13C; and DP 12A and / or DP13A); components for receiving information transmitted to at least one uplink for a user equipment (such as... Figure 6One or more transceivers 12D and / or 13D; MEM 12B and / or MEM 13B; PROG 12C and / or PROG 13C; and DP 12A and / or DP 13A), wherein the information includes: uplink transmission resources for two or more component carriers or cells, two or more component carriers or cells for at least one uplink transmission; and for determining, based on the information, a subset of component carriers or cells on which the user equipment will transmit, and identifying the component of the transmission (e.g., ...) for each component carrier on which the transmission resources are allocated. Figure 6 One or more transceivers 12D and / or 13D; MEM 12B and / or MEM 13B; PROG12C and / or PROG 13C; and DP 12A and / or DP 13A.

[0160] In an example aspect of this disclosure according to the foregoing paragraphs, the components for at least receiving, determining, and transmitting include: components encoded with a computer program [such as...]. Figure 6 Non-transient computer-readable media [such as PROG 12C and / or PROG 13C] Figure 6 [MEM 12B and / or MEM 13B in the above], the computer program can be generated by at least one processor [such as MEM 12B and / or MEM 13B in the above], Figure 6 Execute DP 12A and / or DP 13A in [the following].

[0161] Advantages of exemplary embodiments of the present invention include: • Enables inter-site CA to achieve better performance than existing technology solutions; • The impact on existing deployments is minimal, consisting mainly of configuration changes; • Removes complexity from the UE and is not extremely complex for implementing the NW-side form; and • Supports a single frame for UEs with different UL capabilities (single UL, synchronous UL, dynamic power sharing, etc.).

[0162] Furthermore, according to exemplary embodiments of the present invention, there exists a circuit system for performing operations as disclosed herein according to exemplary embodiments of the present invention. This circuit system may include any type of circuit system, including content encoding circuit systems, content decoding circuit systems, processing circuit systems, image generation circuit systems, data analysis circuit systems, etc. Furthermore, this circuit system may include discrete circuit systems, application-specific integrated circuit systems (ASICs), and / or field-programmable gate array circuit systems (FPGAs), etc., as well as processors specifically configured by software to perform corresponding functions, or dual-core processors having software and corresponding digital signal processors, etc. Additionally, necessary inputs to and necessary outputs from the circuit system, functions performed by the circuit system, and interconnections (possibly via inputs and outputs) between the circuit system and other components that may include other circuit systems are provided to perform exemplary embodiments of the present invention as described herein.

[0163] According to exemplary embodiments of the invention disclosed in this application, the provided "circuit system" may include at least one or more, or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits having software / firmware; and (ii) Any portion of the hardware processor(s) having software (including the digital signal processor(s)), software, and the memory(s) thereof, which work together to enable a device (such as a mobile phone or server) to perform various functions (such as functions or operations according to exemplary embodiments of the invention disclosed herein); and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0164] According to exemplary embodiments of the present invention, there exists a sufficient circuit system for performing novel operations according to at least the exemplary embodiments of the invention disclosed herein, whereby "circuit system" may be used herein to refer to at least the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuit systems); and (b) A combination of circuitry and software (and / or firmware), such as (if applicable): (i) a combination of (multiple) processors or (ii) (multiple) processors / software (including (multiple) digital signal processors), software, and a portion of (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and (c) A circuit, such as (multiple) microprocessors or a portion thereof, that requires software or firmware to operate even if the software or firmware is not physically present.

[0165] This definition of "circuit system" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit system" will also cover only the implementation of a processor (or processors) or a portion of a processor and its (or their) accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or application processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other network devices.

[0166] Generally, various embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, although the invention is not limited thereto. While aspects of the invention may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is well understood that, by way of non-limiting example, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or combinations thereof.

[0167] Embodiments of the present invention can be practiced in various components, such as integrated circuit modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs that are to be etched and formed on a semiconductor substrate.

[0168] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as being more preferred or advantageous than other embodiments. All embodiments described in this detailed description are exemplary embodiments provided to enable those skilled in the art to make or use the invention, and are not intended to limit the scope of the invention as defined by the claims.

[0169] The foregoing description has provided a complete and informative description of the inventors’ current understanding of the best methods and apparatus for carrying out the invention, through exemplary and non-limiting embodiments. However, various modifications and adjustments will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of the exemplary embodiments of the invention will still fall within the scope of the invention.

[0170] It should be noted that the terms “connection,” “coupling,” or any variation thereof mean any direct or indirect connection or coupling between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are “connected” or “coupled” together. The coupling or connection between elements can be physical, logical, or a combination thereof. As used herein, two elements may be “connected” or “coupled” together by the use of one or more wires, cables, and / or printed electrical connections, and by the use of electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) region, as are several non-limiting and non-exhaustive examples.

[0171] Furthermore, some features of the preferred embodiments of the invention can be used advantageously without the need for corresponding use of other features. Therefore, the foregoing description should be considered merely as an illustration of the principles of the invention, and not as a limitation thereof.

Claims

1. An apparatus comprising: At least one processor; as well as At least one non-transient memory stores instructions that, when executed by the at least one processor, cause the device to at least: Configuration is received by the user equipment of the communication network; Based on the configuration, it is determined that uplink transmission of information is required on a subset of carriers or cells; as well as Send at least one uplink transmission to a network node of the communication network, the uplink transmission including: an indication identifying the information being transmitted in a selected subset of the carrier or cell.

2. The apparatus of claim 1, wherein the determination is based on at least one of the following: maximum allocation, type or configuration authorization of uplink allocation, based on selected or preferred transmitter, maximum allowed power or additional maximum power reduction for each configured uplink in the frequency band associated with the handover time.

3. The apparatus according to claim 1, wherein the information includes: Decode information for component carriers used in the at least one uplink transmission.

4. The apparatus of claim 3, wherein the configuration includes: Power splitting configuration based on the physical uplink control channel or physical uplink shared channel information to be transmitted simultaneously on the uplink component carrier.

5. The apparatus of claim 3, wherein the configuration includes: A set of rules used to prioritize uplink transmissions in the event of conflicts between physical channels.

6. The apparatus of claim 5, wherein the prioritization comprises: Based on the available license size and pre-configured rules, priority is given to the u-plane data or c-plane data to be transmitted across the component carriers.

7. The apparatus of claim 6, wherein the u-plane refers to user plane data, the user plane data being transmitted by an end user to the target receiver, the target receiver including at least one of a server or other end user, and wherein the c-plane refers to control plane data terminated at the radio network or the end user equipment, wherein the control plane data includes at least one of: a media access control header, or a radio resource control message.

8. The apparatus of claim 3, wherein the decoding information includes uplink control information, the uplink control information including an uplink control information header, the uplink control information header indicating data included in each uplink transmission in the at least one uplink transmission.

9. The apparatus of claim 8, wherein the header includes an N-UCI field.

10. The apparatus of claim 9, wherein the N-UCI field comprises: Pre-configured identifier and length fields.

11. The apparatus of claim 9, wherein the N-UCI field is a fixed-size field.

12. The apparatus of claim 9, wherein the N-UCI field is present together with the physical uplink shared channel for use in checking prior to decoding the physical uplink shared channel.

13. The apparatus of claim 8, wherein the N-UCI field is present together with the physical uplink control channel for use in checking prior to decoding of the physical uplink shared channel.

14. The apparatus of claim 9, wherein when only data is transmitted via the at least one transmission, the N-UCI field exists as an extension of the MAC header.

15. The apparatus of claim 8, wherein the header is used to determine the uplink cell on which data is transmitted on different component carriers.

16. The apparatus of claim 1, wherein the configuration is received by the user equipment from a network node of the communication network.

17. A method comprising: Configuration is received by the user equipment of the communication network; Based on the configuration, it is determined that uplink transmission of information is required on a subset of carriers or cells; as well as Send at least one uplink transmission to a network node of the communication network, the uplink transmission including: an indication identifying the information being transmitted in a selected subset of the carrier or cell.

18. An apparatus comprising: At least one processor; as well as At least one non-transient memory stores instructions that, when executed by the at least one processor, cause the device to at least: The network nodes of the communication network configure the user equipment for uplink transmission on multiple carriers or cells; Within the plurality of carriers or cells scheduled to the user equipment for uplink transmission, a subset of carriers or cells for uplink reception is determined. Receive information for at least one uplink transmission to a user equipment, wherein the information includes: uplink transmission resources for two or more component carriers or cells for the at least one uplink transmission; as well as Based on the information, the transmission is identified for each component carrier allocated to the transmission resources.

19. The apparatus of claim 18, wherein the determination is based on at least one of: maximum allocation, type of uplink allocation, configuration authorization for the user equipment, selected or preferred transmission, and, in association with handover time, maximum allowed power or additional maximum power reduction for each configured uplink in the frequency band at the user equipment.

20. The apparatus of claim 18, wherein the information includes: Decode information for component carriers used in the at least one uplink transmission.

21. The apparatus of claim 20, wherein the configuration includes: Power splitting configuration based on the physical uplink control channel or physical uplink shared channel information to be transmitted simultaneously on the uplink component carrier.

22. The apparatus of claim 21, wherein the configuration includes: A set of rules used to prioritize uplink transmissions in the event of conflicts between physical channels.

23. The apparatus of claim 22, wherein the prioritization comprises: Based on the available license size and pre-configured rules, priority is given to the u-plane data or c-plane data to be transmitted across the component carriers.

24. The apparatus of claim 23, wherein the u-plane refers to user plane data, the user plane data being transmitted by an end user to the target receiver, the target receiver including at least one of a server or other end user, and wherein the c-plane refers to control plane data terminated at the radio network or the end user equipment, wherein the control plane data includes at least one of: a media access control header, or a radio resource control message.

25. The apparatus of claim 18, wherein the information is based on uplink control information, the uplink control information including an uplink control information header, the uplink control information header indicating data included in each uplink transmission in the at least one uplink transmission.

26. The apparatus of claim 24, wherein the header includes an N-UCI field.

27. The apparatus of claim 25, wherein the N-UCI field comprises: Pre-configured identifier and length fields.

28. The apparatus of claim 25, wherein the N-UCI field is a fixed-size field.

29. The apparatus of claim 25, wherein the N-UCI field is present together with the physical uplink shared channel or uplink control information on the physical uplink shared channel for use in checking prior to decoding the physical uplink shared channel.

30. The apparatus of claim 25, wherein when only data is transmitted via the at least one transmission, the N-UCI field exists as an extension of the MAC header.

31. The apparatus of claim 24, wherein the header is used to determine the uplink cell on which data is transmitted on different component carriers.

32. The apparatus of claim 18, wherein the identifier uses uplink scheduling and downlink control information sent to the user equipment and the secondary network nodes of the communication network.

33. The apparatus of claim 16, wherein the identifier uses downlink scheduling and downlink control information sent to the user equipment and the secondary network nodes of the communication network.

34. The apparatus of claim 32, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Dynamically share at least one of the following with the auxiliary network nodes: Downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or User power margin or estimated transmission power of the user equipment.

35. The apparatus of claim 33, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Dynamically receive at least one of the following from the auxiliary network nodes: Downlink control information authorization or configuration authorization semi-persistent scheduling configuration, or User power margin or estimated transmission power of the user equipment.

36. The apparatus of claim 33, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Determine the probability of the active uplink set; and Determine whether the active uplink of the set belongs to the secondary network node.

37. The apparatus of claim 35, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Based on the existence of an active uplink belonging to the auxiliary network node, demodulate at least one of the physical uplink control channel or the physical uplink shared channel; Decode the uplink control information from the uplink fronthaul data of the auxiliary network node.

38. The apparatus of claim 36, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Determine whether the decoding was successful.

39. The apparatus of claim 38, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Based on the absence of an active uplink belonging to the auxiliary network node, demodulate at least one of the physical uplink control channel or the physical uplink shared channel; Based on the uplink fronthaul data, the uplink control information is decoded, wherein the uplink fronthaul data is based on shared uplink control information or configuration authorization information.

40. The apparatus of claim 39, wherein the at least one non-transient memory stores instructions, the instructions being executed by the at least one processor, such that the apparatus: Other distributed unit data is discarded based on uplink control information indicating data for the secondary network node, wherein the uplink control information is included in at least one of a physical uplink control channel or a physical uplink shared channel.

41. A method comprising: The network nodes of the communication network configure the user equipment for uplink transmission on multiple carriers or cells; Within the plurality of carriers or cells scheduled to the user equipment for uplink transmission, a subset of carriers or cells for uplink reception is determined. Receive information for at least one uplink transmission to a user equipment, wherein the information includes uplink transmission resources for two or more component carriers or cells used for the at least one uplink transmission; and Based on the information, a subset of component carriers or cells on which the user equipment transmits is determined, and the transmission is identified for each component carrier on which transmission resources are allocated.

Images