Closed VS open 6g superimposed pilot adaptation

Abstract

A method includes receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission, determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based at least on the configuration information, generating, by the UE, an SIP uplink (UL) transmission based at least on UL pilot power and data power, and transmitting, by the UE, the SIP UL transmission to the network apparatus.

Description

CLOSED VS OPEN 6G SUPERIMPOSED PILOT ADAPTATION FIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for closed vs open 6G superimposed pilot adaptation.BACKGROUND

[0002] A power control procedure manages the transmission power of a user equipment (UE) and gNB to ensure efficient use of the radio spectrum, maintain signal quality, and reduce interference.SUMMARY

[0003] In accordance with aspects of the disclosure, a method includes receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission, determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based at least on the configuration information, generating, by the UE, an SIP uplink (UL) transmission based at least on UL pilot power and data power, and transmitting, by the UE, the SIP UL transmission to the network apparatus.

[0004] In an aspect of the method, the UE may determine the UL pilot power and UL data power for SIP transmission by applying an open loop power control (OLPC) operation.

[0005] In an aspect of the method, the configuration information may include a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

[0006] In an aspect of the method, the set of power control configuration may further include desired received pilot power at each RE, fractional pilot power control factor, and / or normalization pilot power control factor.

[0007] In an aspect of the method, the method may further include receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

[0008] In an aspect of the method, the method may further include obtaining a list of pilot-to-data power ratio.

[0009] In an aspect of the method, the pilot-to-data power ratio may be configured by a network node, or included in a predefined list of the pilot-to-data power ratio.

[0010] In an aspect of the method, the pilot-to-data power ratio may be selected and configured by the UE, or included in a predefined list of the pilot-to-data power ratio.

[0011] In an aspect of the method, the method may further include transmitting a capability indicating support superimposed pilot and data power control.

[0012] In accordance with aspects of the disclosure, a method includes receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission, receiving, by the user equipment (UE), a second message from the network apparatus, the second message including power control command adjusting the pilot power and data power, determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based upon the first configuration information and the second configuration information, generating, by the UE, an SIP uplink (UL) transmission based upon the UL pilot power and data power, and transmitting, by the UE, the SIP UL transmission to the network apparatus.

[0013] In an aspect of the method, the UE may determine the UL pilot power and UL data power for SIP transmission by applying a close loop power control (CLPC) operation.

[0014] In an aspect of the method, the first configuration information may include a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

[0015] In an aspect of the method, the first set of power control configuration may further include desired received pilot power at each RE, fractional pilot power control factor, and / or normalization pilot power control factor.

[0016] In an aspect of the method, the method may further include receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

[0017] In an aspect of the method, the method may further include obtaining a list of pilot-to-data power ratio.

[0018] In an aspect of the method, the pilot-to-data power ratio may be configured by a network node, or included in a predefined list of the pilot-to-data power ratio, using the first configuration information.

[0019] In an aspect of the method, the second configuration information may include a set of adjusting power control parameters for SIP including at least data power control adjustment state.

[0020] In an aspect of the method, the second configuration information may further include pilot power control adjustment state.

[0021] In an aspect of the method, the pilot-to-data power ratio may be adjusted by a network node, or included in a predefined list of the pilot-to-data power ratio, using the second configuration information.

[0022] In an aspect of the method, the pilot-to-data power ratio may be adjusted by the UE, or included in a predefined list of the pilot-to-data power ratio, using the second configuration information.

[0023] In an aspect of the method, the method may further include transmitting a capability indicating support superimposed pilot and data power control.

[0024] In accordance with aspects of the disclosure, a user equipment (UE) includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause the UE at least to perform a method as in any one of the foregoing methods.

[0025] In accordance with aspects of the disclosure, a processor-readable medium stores instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of the foregoing methods.

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

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

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

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

[0030] FIG. 3A is a diagram of an example pilot-based transmission, according to one illustrated aspect of the disclosure;

[0031] FIG. 3B is a diagram of an example superimposed pilots transmission, according to one illustrated aspect of the disclosure;

[0032] FIG. 3C is a diagram of an example pilotless transmission, according to one illustrated aspect of the disclosure;

[0033] FIG. 4 is an example diagram of a scenario with near and far UEs communicating with an SIP transmission scheme, according to one illustrated aspect of the disclosure;

[0034] FIG. 5 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure;

[0035] FIG. 6 is a diagram of an example artificial intelligence machine learning (AIML) pilot to power ratio estimator, according to one illustrated aspect of the disclosure;

[0036] FIG. 7 is a diagram of an example AIML pilot to power ratio detector / classifier, according to one illustrated aspect of the disclosure; and

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0066] As mentioned above, the power control procedure manages the transmission power of a UE and gNB to ensure efficient use of the radio spectrum, maintain signal quality, and reduce interference. In various embodiments, a mechanism for power control includes one or more of the following elements: Path loss Compensation: This involves adjusting the transmission power based on the path loss between the UE and the base station; Power Offset: This is an additional power adjustment applied to the transmission power; TPC Command: Transmit Power Control (TPC) commands are used to dynamically adjust the transmission power based on real-time measurements and feedback from the network. The command is included in the downlink control information (DCI) format.

[0067] In various embodiments, if the DCI contains two TPC commands and the PUSCH transmissions are on different resources, the UE applies the first TPC command for one resource and the second command for the other resource. In case one TPC command is included, then this is applied to all resources. In various embodiments, the TPC command is a few bits field that maps the command itself to a specific power control value. In various embodiments, the splits the power equally across antenna ports on which the UE transmits PUSCH.

[0068] To ensure accurate channel estimation - paramount to a successful data reception, 5G systems and its precursors rely on the usage of reference signals, also called pilots, which are separate from the data transmission and are ideally orthogonalized among users. This type of approach in various embodiments is referred to as a regular pilot (RP) approach.

[0069] In various embodiments, pilotless transmission may be utilized. In thistransmission scheme, transmitter obtains and uses an irregular (i.e., custom / learned constellation different from QAM) constellation that enables the AI / ML receiver to estimate the channel and the transmitted data. In the pilotless transmission scheme, all the transmission power and resource elements are allocated to data transmission, resulting in higher spectral efficiency than regular pilot (RP) scheme. However, pilotless transmission might require overly complex receiver algorithms with high-order MIMO scenarios, while also making it more challenging to obtain channel state information.

[0070] In various embodiments, superimposed pilot (SIP) transmission is utilized. In this transmission scheme, data is transmitted in all available resource elements (REs), like in pilotless transmission. However, some power in all or some of the REs is also allocated to known pilot components that help channel estimation at the receiver.

[0071] FIG. 3A is a diagram of an example pilot-based transmission, according to one illustrated aspect of the disclosure. As shown in FIG. 3A, data REs and pilot REs are shown per subcarrier and OFDM symbol.

[0072] FIG. 3B is a diagram of an example superimposed pilots transmission, according to one illustrated aspect of the disclosure. As shown in FIG. 3B, data + pilot REs are shown per subcarrier and OFDM symbol.

[0073] FIG. 3C is a diagram of an example pilotless transmission, according to one illustrated aspect of the disclosure. As shown in FIG. 3C, data REs are shown per subcarrier and OFDM symbol.

[0074] Described herein is a power control procedure, in various embodiments, designed for SIP transmission. Successful data reception mainly depends on two factors: a) accuracy of the estimated channel, and b) SNR of the received signal. As in a SIP transmission, the pilot sequences of different UEs are orthogonal, increasing pilot power of a UE results in better channel estimation and consequently data reception of the target UE, without harming channel estimation or data reception of other UEs. In fact, a better channel estimation of a UE results in better interference cancellation in successive interference cancellation and MIMO decoding of all the UEs.

[0075] Accordingly, described herein is a method to consider two power control procedures, one for controlling the 6G UL data channel (e.g., the equivalent of NR PUSCH) transmission, and another for controlling the pilot power in SIP transmission.

[0076] In various embodiments, the PC procedures for both open-loop (OLPC) and closed-loop PC (CLPC) for data and pilot parts of SIP transmission are shown below.

[0077] FIG. 4 is an example diagram 400 of a scenario with near and far UEs communicating with an SIP transmission scheme, according to one illustrated aspect of the disclosure. As shown in FIG. 4, a first UE (UE1) is in communication with a network apparatus (e.g., gNB) engaging in SIP transmission, while a second UE (UE2) is also in communication with a network apparatus engaging in SIP transmission.

[0078] In various embodiments, UE1 is close to the gNB while UE2 is close to the cell edge. In SIP transmission, if these two UEs are co-scheduled over the same resources in SIP transmission, pilot transmission of a UE does not cause problem for pilot or data detection of the other UE. As path loss compensation for UE1 would not require high power transmission, in various embodiments, UE1 has enough power budget for high pilot power transmission. Allocating higher pilot power results in better channel estimation at gNB and consequently, higher throughput for UE1 (while higher pilot transmission by UE1 has no impact on channel estimation or data detection of UE2).

[0079] FIG. 5 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 5 may correspond to similar components described above in FIGS. 1-2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0080] At operation 501, the UE transmits a message to the gNB that the UE supports SIP transmission and the gNB receives the message.

[0081] At operation 502, the UE transmits a UE capability message to the gNB that the UE supports superimposed pilot and data power control and the gNB receives the capability message.

[0082] In various embodiments, operation 303 may be referred to as an open loop power control (OLPC). At operation 504, the gNB transmits a configure parameters for power control of data part message to the UE and the UE receives the configure parameters for power control of data part message. In various embodiments, the configure parameters for power control of data part message may include a configuration for restraints for pilot vs data power, configuration of parameters for power control of the pilot part, desiredreceive pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor number of scheduled MU-MIMO users.

[0083] At operation 505, the UE applies an enhanced OLPC operation to generate an SIP UL transmission (TX), as will be described in further detail below. Accordingly, at operation 506, the UE transmits an SIP UL signal to the gNB and the gNB receives the SIP UL signal.

[0084] At operation 507, the gNB, in various embodiments, employs machine learning pilot to data power ratio estimation. Accordingly, at operation 508, the gNB performs data detection.

[0085] In various embodiments, operation 509 may be referred to as a closed loop power control (CLPC). At operation 10, the gNB transmits a configure parameters for power control of data part message to the UE and the UE receives the configure parameters for power control of data part message. In various embodiments, the configure parameters for power control of data part message may include a configuration for restraints for pilot vs data power, configuration of parameters for power control of the pilot part, desired receive pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor number of scheduled MU-MIMO users.

[0086] At operation 511, the gNB transmits a TPC for data power control adjustment state message to the UE and the UE receives the TPC for data power control adjustment state message. In various embodiments, the TPC for data power control adjustment state message includes a TPC for pilot power control adjustment state.

[0087] At operation 512, the UE applies an enhanced CLPC operation to generate an SIP UL transmission (TX), as will be described in further detail below. Accordingly, at operation 513, the UE transmits an SIP UL signal to the gNB and the gNB receives the SIP UL signal.

[0088] At operation 514, the gNB, in various embodiments, employs machine learning pilot to data power ratio estimation. Accordingly, at operation 515, the gNB performs data detection.

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

[0090] In various embodiments, a PC method utilized above includes controlling superimposed pilot transmission power independently from data transmission power. So, transmission power of m-th UE, i.e.,in dBm, can be expressed as:= 10log10(10p^ / w+ (1)

[0091] where P^aar|d Ppttot denote the allocated power for data and pilot transmission in dBm, respectively. Therefore, the general constraints for a PC solution can be written as^"’ < PSAX [dBm] Vm (2)C. 2 " PSTP-MAX [dBm] V m (3)PX’. - PSTP-MIN [dBm] V m (4)

[0092] where PSIP? MINar|d ^SIP-MAXdB) are the configured minimum and maximum allowed differences in pilot transmission power compared to the data transmission power for the m-th UE. gNB configures the PS^?MINand Ps^?MAXparameters.

[0093] In an embodiment for OLPC in SIP transmission, considering a PUSCH transmission, the m-th UE determines the data and pilot transmission power P^aC^ 0 and Pp™ot(i, 0 in PUSCH transmission occasion as:p(.ni) VIA X ( i PsiP-MINrdata (0 = min [dBm]Po.data + 101og10(2" ■ M™SCH(0) + adata■ PL + ATF(i)nfrn) _p(m)rdatarSIP-MINPpUot (0 =min[dBm],^0-Piiot + lOlogio (2" ■ M™SCH(0) + a. pilot ' " I" Ypilot ^users

[0094] where Po.data andadataarethe desired received data power at each RE and fractional data power control factor, respectively. In addition, Po.piiot,apiiot, and Ypilot denote the desired received pilot power at each RE, fractional pilot power control factor, and normalization pilot power control factor, respectively. Nusersis the number of scheduled MU-MIMO users. In various embodiments, the above parameters are configured by the gNB.

[0095] The received signal at the RX at resource element (m, n) may be written as:Y(a,b) = y y H^(a, b, Pj) | J jSdata<-M^(q, b, ■ data ^{a, b, p^ u=l: Nuserspj X+ pPilot<'u^a, b,pj) ■ pilot ^(a.b.pj}

[0096] For each user and antenna port, the receiver can estimate the scaled version of the relevant channel as (a, b, p^ H^ua, b, Pj using the orthogonalityproperty of pilot ^(a, b, P]. Note, for recovering the data transmitted by each userdata ^ua, b), the receiver needs to obtain Jpdata^u\a, b, p^ H^u\a, b, Pj.Therefore, the receiver needs to know or estimate pdata^ (^a, b, p ) / J ppiiot^ £?)p.^ for such purpose.

[0097] As the ratio of pilot-to-data power transmission is not fixed (depending on the experienced PL by a UE), gNB is not certain of the selected ratio by the UE. Therefore, gNB should estimate the considered ratio by each UE. FIG. 6 is a diagram of an exampleartificial intelligence machine learning (AIML) pilot to power ratio estimator, according to one illustrated aspect of the disclosure. As shown in FIG. 6, a received signal is input into a remove CP operation, which outputs to a M-point DFT operation 602. The operation 602 outputs to a subcarrier de-mapping operation 603, which outputs to a channel estimator using SIP operation 604 and pilot- to-data power ratio estimator 605. The estimator 605 also receives input from the channel estimator using SIP operation and outputs an estimated ratio.

[0098] In various embodiments, the estimation block is a Convolutional Neural Network (CNN) using convolutional layers for extracting features from the received signal, followed by dense layers for estimation of the pilot-to-data ratio. Note that assistance information such as estimated power control parameters, number of users, and SNR of the received signal can be concatenated with the extracted features and fed as input to the dense layers for the estimation block.

[0099] FIG. 7 is a diagram of an example AIML pilot to power ratio detector / classifier, according to one illustrated aspect of the disclosure. As shown in FIG. 7, a received signal is input into a remove CP operation, which outputs to a M-point DFT operation 702. The operation 702 outputs to a subcarrier de-mapping operation 703, which outputs to a channel estimator using SIP operation 704 and pilot-to-data power ratio estimator 705. The estimator 705 also receives input from the channel estimator using SIP operation and outputs estimated ratios.

[0100] To ease the detection of considered pilot-to-data power ratio at UEs, a list 7? = { i, p2,..., pz} of possible pilot-to-data power ratios can be standardized or be configured by gNB. This list can be shared in linear scale or in dB. The UE, based on the experienced path loss and the power budget, decides independently on the proper pilot power transmission, which aligns with one of the configured pilot-to-data power ratios. Note, here ^SIP-MINand ^sm-MAXe minimum and maximum ratios in list 7?.p(.m) VIA X ( i ) PsiP-MINrdata (0 = min [dBm]Po.data + 101og10(2" ■ M™SCH(0) + adata■ PL + ATF(0 I pWJ _ nWrdatarSIP-MIN [dBm] Po-piiot + 101og10(2^ M™SCH• pilot ■ PI + v TtpiiotN "users ) I _ p(m) sp. _ p(m)..p.PsiP-Cand— rdata WrSIP-Cand| UD |

[0101] Psip-Seiected:UE compares the calculated PsjjCandwith the configured power-to-data ratios, and selects the closest ratio in the shared list 3? to Psj Cand [While satisfying constraints ( 1 )-(4)J. Then, the pilot power is computed as:PpUot & =P^ta & ~ Psff-Selected [dBml

[0102] Machine learning based detectors can be used to detect the ratios considered by the UEs as shown in FIG. 7.

[0103] In a CLPC in SIP transmission embodiment, Considering a PUSCH transmission, the m-th UE determines the data and pilot transmission power Pd™ta(i, 0 and P^otCi, 0 in PUSCH transmission occasion i and PUSCH power control adjustment state with index I as:Pc MA X ( I ) PsiP-MINPdata <i’ 0 =min[dBm]Po.data + 101og10(2" ■ M™SCH(0) + adata■ PL + ATF(0 + fdata(i, Z)p(m) > pfrn) n(m)rdatarSIP-MINrpilot (Z, Z) = min [dBm]+ 101og10(2" ■ + apilot■ PL + ypilotNusersT fpi / otG’ 0where Po.data,adata- and ^dataarethe desired received data power at each RE, fractional data power control factor, and data power control adjustment state controlled by TPC, respectively. In addition, P0-Piiot,piiot, Y pilot, and fdatadenote the desired received pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor, and pilot power control adjustment state controlled by pilot TPC, respectively. Nusersis the number of scheduled MU-MIMO users. All the above parameters are configured by the gNB. Note, pilot TPC can be used in absolute or accumulated settings for determining fpuot.

[0104] In a CLPC in SIP transmission with list of acceptable pilot-to-data power ratios embodiment, to simplify controlling of a UE pilot power, a list JI = { i, 2< ■■■•Pz} °f possible pilot-to-data power ratios can be standardized or be configured by gNB. So, gNB can directly configure a specific pilot-to-data power ratio by sharing the corresponding index, so p sip-configurededenotes the configured pilot-to-data ratioby gNB. Note, here Ps^?MINand Ps^?MAXarethe minimum and maximum ratios in list

[0105] Considering a PUSCH transmission, the m-th UE determines the data and pilot transmission power PaataC^' 0and Pptiot^’ 'nPUSCH transmission occasion i and PUSCH power control adjustment state with index I as:PcMAX ( i ) PsiP-MINpdata & o = min [dBm]^O_data + 101og10■ MRBSCH(I)) + adata■ PL + ATF(0 + fdata(i, Z) p pilott (i, ’ Z)J= Pdda™ta (i, > Z) ■> - p r S(? IpP-rCon rfigure dd(vhZ)J[LdBm]Jwhere Po.data,adata- and ^dataarethe desired received data power at each RE, fractional data power control factor, and data power control adjustment state controlled by TPC, respectively. In addition, Ps^-configuredCh Z) G J? denotes the configured pilot-to-data power ratio by pilot TPC, respectively.

[0106] The following describes operations from the perspective of a network apparatus. From such a perspective, a method may include: receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission; determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based at least on the configuration information; generating, by the UE, an SIP uplink (UL) transmission based at least on UL pilot power and data power; and transmitting, by the UE, the SIP UL transmission to the network apparatus.

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

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

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

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

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

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

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

[0114] Example 1.1 A user equipment (UE), comprising:means for receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission;means for determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based at least on the configuration information;means for generating, by the UE, an SIP uplink (UL) transmission based at least on UL pilot power and data power; andmeans for transmitting, by the UE, the SIP UL transmission to the network apparatus.

[0115] Example 1.2. The UE of Example 1.1, wherein the UE determines the UL pilot power and UL data power for SIP transmission by applying an open loop power control (OLPC) operation.

[0116] Example 1.3. The UE of any of Examples 1.1 or 1.2, wherein the configuration information includes a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

[0117] Example 1.4. The UE of any of Examples 1.1 to 1.3, wherein the set of power control configuration further comprises at least one of: desired received pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor.

[0118] Example 1.5. The UE of any of Examples 1.1 to 1.4, further comprising:means for receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

[0119] Example 1.6. The UE of any of Examples 1.1 to 1.5, further comprising:means for obtaining a list of pilot- to-data power ratio.

[0120] Example 1.7. The UE of Example 1.6, wherein the pilot-to-data power ratio is configured by a network node, or included in a predefined list of the pilot-to-data power ratio.

[0121] Example 1.8. The UE of Example 1.6, wherein the pilot-to-data power ratio is selected and configured by the UE, or included in a predefined list of the pilot-to-data power ratio.

[0122] Example 1.9. The UE of any of Examples 1.1 to 1.8, further comprising transmitting a capability indicating support superimposed pilot and data power control.

[0123] Example 1.10. A UE, comprising:means for receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission;means for receiving, by the user equipment (UE), a second message from the network apparatus, the second message including power control command adjusting the pilot power and data power;means for determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based upon the first configuration information and the second configuration information;means for generating, by the UE, an SIP uplink (UL) transmission based upon the UL pilot power and data power; andmeans for transmitting, by the UE, the SIP UL transmission to the network apparatus.

[0124] Example 1.11. The UE of Examples 1.10, wherein the UE determinesthe UL pilot power and UL data power for SIP transmission by applying a close loop power control (CLPC) operation.

[0125] Example 1.12. The UE of any of Examples 1.10 or 1.11, wherein the first configuration information includes a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

[0126] Example 1.13. The UE of any of Examples 1.10 to 1.12, wherein the first set of power control configuration further comprises at least one of: desired received pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor.

[0127] Example 1.14. The UE of any of Examples 1.10 to 1.13, further comprising:means for receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

[0128] Example 1.15. The UE of any of Examples 1.10 to 1.14, further comprising:means for obtaining a list of pilot- to-data power ratio.

[0129] Example 1.16. The UE of Examples 1.12, wherein the pilot-to-data power ratio is configured by a network node, or included in a predefined list of the pilot-to-data power ratio, using the first configuration information.

[0130] Example 1.17. The UE of any of Examples 1.10 or 1.11, wherein the second configuration information includes a set of adjusting power control parameters for SIP including at least data power control adjustment state.

[0131] Example 1.18. The UE of any of Examples 1.10 or 1.11 or 1.17, wherein the second configuration information further comprises pilot power control adjustment state.

[0132] Example 1.19. The UE of any of Examples 1.10 or 1.11 or 1.17 to 1.18, wherein the pilot-to-data power ratio is adjusted by a network node, or included in a predefined list of the pilot-to-data power ratio, using the second configuration information.

[0133] Example 1.20. The UE of any of Examples 1.10 or 1.11 or 1.17 to 1.18, wherein the pilot-to-data power ratio is adjusted by the UE, or included in a predefinedlist of the pilot-to-data power ratio, using the second configuration information.

[0134] Example 1.21. The UE of any of Examples 1.10 to 1.20, further comprising:means for transmitting a capability indicating support superimposed pilot and data power control.

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

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

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

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

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

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

Claims

WHAT IS CLAIMED IS:

1. A method, comprising:receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission;determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based at least on the configuration information;generating, by the UE, an SIP uplink (UL) transmission based at least on UL pilot power and data power; andtransmitting, by the UE, the SIP UL transmission to the network apparatus.

2. The method of claim 1, wherein the UE determines the UL pilot power and UL data power for SIP transmission by applying an open loop power control (OLPC) operation.

3. The method as in any of claims 1 or 2, wherein the configuration information includes a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

4. The method as in any one of claims 1 to 3, wherein the set of power control configuration further comprises at least one of: desired received pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor.

5. The method as in any one of claims 1 to 4, further comprising receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

6. The method as in any one of claims 1 to 5, further comprising obtaining a list of pilot- to-data power ratio.

7. The method of claim 6, wherein the pilot-to-data power ratio is configured by a network node, or included in a predefined list of the pilot-to-data power ratio.

8. The method of claim 6, wherein the pilot-to-data power ratio is selected and configured by the UE, or included in a predefined list of the pilot-to-data power ratio.

9. The method as in any one of claims 1 to 8, further comprising transmitting a capability indicating support superimposed pilot and data power control.

10. A method, comprising:receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for superimposed pilot (SIP) transmission including a configuration for pilot power transmission and data power transmission;receiving, by the user equipment (UE), a second message from the network apparatus, the second message including power control command adjusting the pilot power and data power;determining, by the UE, the uplink (UL) pilot power and UL data power for SIP transmission based upon the first configuration information and the second configuration information;generating, by the UE, an SIP uplink (UL) transmission based upon the UL pilot power and data power; andtransmitting, by the UE, the SIP UL transmission to the network apparatus.

11. The method of claim 10, wherein the UE determines the UL pilot power and UL data power for SIP transmission by applying a close loop power control (CLPC) operation.

12. The method as in any one of claims 10 or 11, wherein the first configuration information includes a set of power control configuration for SIP including at least a number of scheduled users on a resource set.

13. The method as in any one of claims 10 to 12, wherein the first set of power control configuration further comprises at least one of: desired received pilot power at each RE, fractional pilot power control factor, normalization pilot power control factor.

14. The method as in any one of claims 10 to 13, further comprising receiving a minimum and / or maximum allowed differences in pilot transmission power compared to the data transmission power for the user device.

15. The method as in any one of claims 10 to 14, further comprising obtaining a list of pilot- to-data power ratio.

16. The method of claim 12, wherein the pilot- to-data power ratio is configured by a network node, or included in a predefined list of the pilot-to-data power ratio, using the first configuration information.

17. The method as in any one of claims 10 or 11, wherein the second configuration information includes a set of adjusting power control parameters for SIP including at least data power control adjustment state.

18. The method as in any one of claims 10 or 11 or 17, wherein the second configuration information further comprises pilot power control adjustment state.

19. The method as in any one of claims 10 or 11 or 17 to 18, wherein the pilot-to-data power ratio is adjusted by a network node, or included in a predefined list of the pilot-to-data power ratio, using the second configuration information.

20. The method as in any one of claims 10 or 11 or 17 to 18, wherein the pilot-to-data power ratio is adjusted by the UE, or included in a predefined list of the pilot-to-data power ratio, using the second configuration information.

21. The method as in any one of claims 10 to 20, further comprising transmitting a capability indicating support superimposed pilot and data power control.

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

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

Images