Apparatus and methods for uplink beamforming in wireless communication network

Abstract

To provide an uplink beamforming method in a 5G network.SOLUTION: In a mobile communication system, a user equipment (UE) determines configuration parameters associated with a second uplink beam upon receiving a configuration message from a base station (BS) including one or more signal quality indicators associated with configuration parameters of a first uplink beam. The determining is based on: the one or more signal quality indicators associated with the configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam. The UE configures the second uplink beam based on the determined configuration parameters of the second beam and transmits uplink data or control information using the second uplink beam to the BS.SELECTED DRAWING: Figure 17

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 63 / 159,390, filed on March 10, 2021 (the "Provisional Application"), the contents of which are incorporated herein by reference.

[0002] The present invention is directed to 5G, the fifth generation mobile network. It is the new global wireless standard after 1G, 2G, 3G, and 4G networks. 5G enables networks designed to connect machines, objects, and devices. The present invention also relates to uplink beamforming in 5G networks. Summary of the Invention

[0003] In one embodiment, the present invention provides a method of data transmission, comprising the steps of: receiving, by a user equipment (UE), a configuration message from a base station (BS), the configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam; determining, by the UE, configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; and determining, by the UE, configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam. Uplink The method includes a configuration step of configuring the second uplink beam based on the determined configuration parameters for the beam, and a transmission step of the UE transmitting uplink data or control information to a BS using the second uplink beam.

[0004] The configuration parameters are the transmit power control (TPC) signal and phase feedback The determining step may include one or more of the configuration parameters (PF) signals. The determining step may include mapping the configuration parameters to integer values ​​based on one or more look-up tables. The decision step is B.S. and identifying the configuration parameters that maximize a signal-to-noise ratio (SNR) of the second uplink beam at the second uplink beam. The method may also include performing an adaptive tracking scheme to track the configuration parameters of the second uplink beam. The adaptive tracking scheme is based on a gradient descent algorithm. The configuration message may include an identifier for identifying a configuration message, at least one transmit power control (TPC) field, and up to N phase feedback and a PF field, where N is the number of user equipments (UEs) in one group in one cell designated by a base station (BS). The configuration message is transmitted via a downlink control information (DCI) To be received .

[0005] In one embodiment, the present invention provides a method for determining a data transmission scheme, the method including: a first transmission step in which a user equipment (UE) transmits data or control information to a base station (BS) using a first transmission scheme in a first period; a first calculation step in which the UE calculates a first transmission power for transmitting the data or control information to the BS for the first transmission scheme; a second transmission step in which the user equipment (UE) transmits data or control information to the base station (BS) using a second transmission scheme in a second period; a second calculation step in which the UE calculates a second transmission power for transmitting the data or control information to the BS for the second transmission scheme; The The second transmission method The data or the control information is transmitted to the BS according to the calculation The first send Power and The calculation The second send electric power Based on Decide decision The method includes the steps of:

[0006] In one embodiment, the present invention is a method of data transmission comprising a determining step in which a base station (BS) determines configuration parameters of an uplink beam, and a transmitting step in which the BS transmits to a user equipment (UE) a configuration message including one or more signal quality indicators associated with the configuration parameters of the uplink beam. The configuration parameters may include one or more of a signal-to-noise ratio (SNR) and phase information of the uplink beam. The method may further comprise a first calculating step of calculating the signal quality indicator based on the configuration parameters. The signal quality indicators include one or more of a transmit power control (TPC) command and a phase feedback (PF) command.

[0007] Preferably, the configuration message includes an identifier for identifying the configuration message, at least one TPC field, and up to N Phase Feedback (PF) fields, where N is the number of User Equipments (UEs) in a group in a cell identified by the base station (BS). The configuration message is transmitted via Downlink Control Information (DCI).

[0008] In one embodiment, the present invention provides a transceiver for receiving a configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam and for transmitting uplink data or control information using a second uplink beam, the transceiver configured to determine the configuration parameters associated with the second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam, and to transmit uplink data or control information using a second uplink beam. Uplink and a processor for configuring the second uplink beam based on the determined configuration parameters for the beam.

[0009] In one embodiment, the present invention includes a processor for determining configuration parameters of an uplink beam, and a receiver in communication with the processor and associated with the configuration parameters of the uplink beam. and a transceiver for transmitting a configuration message indicative of the selected one or more signal quality indicators.

[0010] In one embodiment, the present invention provides a non-transitory computer readable medium having program code recorded thereon, which when processed by a computer processor, includes steps of: a UE receiving a configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam; a UE determining configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; and a UE determining configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam. Uplink The method includes a configuration step of configuring the second uplink beam based on the determined configuration parameters for the beam, and a transmission step of the UE transmitting uplink data or control information using the second uplink beam.

[0011] In one embodiment, the invention is a non-transitory computer readable medium having program code recorded thereon that, when processed by a computer processor, includes a configuration step, by a base station (BS) configuring configuration parameters of an uplink beam, and a transmission step, by the BS transmitting a configuration message indicating one or more signal quality indicators associated with the configuration parameters of the uplink beam.

[0012] In one embodiment, the present invention includes a method for receiving a configuration message from a base station (BS) indicating one or more signal quality indicators associated with configuration parameters of a first uplink beam. , No.means for determining configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; Uplink A user equipment (UE) is provided that includes a means for configuring the second uplink beam based on the determined configuration parameters for the beam, and a means for transmitting uplink data or control information to the BS using the second uplink beam. [Brief description of the drawings]

[0013] [Figure 1] FIG. 1 illustrates an example of a mobile communication system according to some aspects of various exemplary embodiments of the present disclosure.

[0014] [Figure 2A] FIG. 2 illustrates an example of a user plane radio protocol stack in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 2B] FIG. 2 illustrates an example of a radio protocol stack for a control plane in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0015] [Figure 3A] FIG. 2 illustrates an example of mapping between logical channels and transport channels in the downlink in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 3B] FIG. 2 illustrates an example of a mapping between logical channels and transport channels in the uplink in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0016] [Figure 4A]FIG. 2 illustrates an example of a mapping between transport channels and physical channels in the downlink in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 4B] FIG. 2 illustrates an example of a mapping between transport channels and physical channels in the uplink in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0017] [Diagram 5] FIG. 2 illustrates an example of physical signals in the downlink and uplink in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0018] [Figure 6] FIG. 2 illustrates an example of Radio Resource Control (RRC) states and transitions between different RRC states in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0019] [Figure 7] FIG. 2 illustrates an example of a frame structure and physical resources in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0020] [Figure 8] FIG. 2 illustrates an example of a component carrier configuration in different carrier aggregation scenarios in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0021] [Figure 9] A diagram showing an example of Bandwidth Part configuration and switching in accordance with some aspects of various exemplary embodiments of the present disclosure.

[0022] [Figure 10] FIG. 2 illustrates an example of an uplink beamforming scheme in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0023] [Figure 11] FIG. 2 illustrates an example of a particular uplink beamforming scheme in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0024] [Figure 12] FIG. 2 illustrates an example of components of a user equipment for transmission and / or reception in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0025] [Figure 13] FIG. 2 illustrates an example of components of a base station for transmission and / or reception in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0026] [Figure 14A] FIG. 2 illustrates a first example of a downlink control information (DCI) message in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 14B] FIG. 2 illustrates a first example of a downlink control information (DCI) message in accordance with some aspects of various exemplary embodiments of the present disclosure.

[0027] [Figure 15A] FIG. 2 illustrates a second example of a downlink control information (DCI) message in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 15B] FIG. 2 illustrates a second example of a downlink control information (DCI) message in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0028] [Figure 16A] FIG. 13 illustrates a third example of a downlink control information (DCI) message in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 16B] FIG. 13 illustrates a third example of a downlink control information (DCI) message in accordance with some aspects of various exemplary embodiments of the present disclosure.

[0029] [Figure 17] FIG. 1 is a flow diagram of a beamforming and power control loop method in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0030] [Figure 18A] FIG. 11 is a flow diagram of another beamforming and power control loop method in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 18B] FIG. 11 is a flow diagram of another beamforming and power control loop method in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0031] [Figure 19] FIG. 1 is a flow diagram of a method for beamforming or codebook-based precoding scheme selection in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0032] [Figure 20] FIG. 1 is a flow diagram of a method for selecting a beamforming transmission scheme or a single antenna transmission scheme in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0033] [Figure 21] FIG. 1 is a sequence diagram illustrating a UL beamforming method according to some aspects of various exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0034] 1 illustrates an example of a mobile communication system 100 according to some aspects of various exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by a wireless communication system operator, such as a Mobile Network Operator (MNO), a private network operator, a Multi-System Operator (MSO), an Internet of Things (IOT) network operator, etc., and may provide services such as voice, data (e.g., wireless Internet access), messaging, vehicular communication services such as Vehicle to Everything (V2X) communication services, safety services, mission-critical services, and services in residential, commercial, or industrial environments such as IoT, Industrial IOT (IIOT), etc.

[0035] The mobile communication system 100 can enable various types of applications with different requirements in terms of latency, reliability, throughput, etc. Examples of supported applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB can support stable connections at high peak data rates as well as moderate rates for cell edge users. URLLC can support applications with stringent requirements in terms of latency and reliability and moderate requirements in terms of data rates. Examples of mMTC applications include networks of vast numbers of IoT devices that are sporadically active and transmit small data payloads.

[0036] The mobile communication system 100 may include a Radio Access Network (RAN) portion and a core network portion. In the example shown in FIG. 1, a Next Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 are shown as examples of a RAN and a core network, respectively. Other examples of a RAN and a core network may be implemented without departing from the scope of the present disclosure. Other examples of a RAN include an Evolved Universal Terrestrial RAN (EUTRAN), a Universal Terrestrial RAN ( ... Examples of core networks include the Universal Terrestrial Radio Access (UTRAN), the Evolved Packet Core (EPC), and the UMTS Core Network (UCN). The RAN implements a radio access technology (RAT) and resides between the user equipment (UE) 125 and the core network. Examples of such RATs include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), and the UMTS Core Network (UCN). Evolution(LTE), Universal Mobile Telecom The RAT of the mobile communication system 100 may be NR. The core network exists between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer setup, and application of different quality of service (QoS). The functional layer between the UE 125 and the RAN (e.g., NG-RAN 105) may be referred to as an Access Stratum (AS), and the functional layer between the UE 125 and the core network (e.g., 5GC 110) may be referred to as a Non-access Stratum (NAS).

[0037] The UE 125 may include wireless transmission and reception means for communicating with one or more nodes in a RAN, one or more relay nodes, or one or more other UEs, etc. Examples of a UE include, but are not limited to, a smartphone, a tablet, a laptop, a computer, a wireless transmitting and / or receiving unit in a vehicle, a V2X or vehicle-to-vehicle (V2V) device, a wireless sensor, an IoT device, an IIOT device, etc. Other names may be used for a UE, such as a mobile station (MS), terminal equipment, terminal node, client device, mobile device, etc.

[0038] The RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with the UE 125. Different names may be used for the RAN nodes, for example, depending on the RAT used in the RAN. In a RAN using the UMTS RAT, the RAN node may be referred to as a Node B (NB). In a RAN using the LTE / EUTRA RAT, the RAN node may be referred to as an evolved Node B (eNB). In the example of the mobile communication system 100 shown in FIG. 1, the node of the NG-RAN 105 may be either a next generation Node B (gNB) 115 or a next generation evolved Node B (ng-eNB) 120. In this specification, the terms base station, RAN node, gNB, and ng-eNB may be used interchangeably. The gNB 115 may provide the NR user plane and control plane protocol termination to the UE 125. The ng-eNB 120 may provide the UE 125 with E-UTRA user plane and control plane protocol terminations. The interface between the gNB 115 and the UE 125 or between the ng-eNB 120 and the UE 125 may be referred to as a Uu interface. The Uu interface may be established using a user plane protocol stack and a control plane protocol stack. For the Uu interface, a base station (e.g., a gNB The direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be referred to as the downlink, and the direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) is sometimes called the uplink.

[0039] The gNB 115 and the ng-eNB 120 may be interconnected using an Xn interface. The Xn interface may include an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built on Internet Protocol (IP) transport, and GPRS Tunneling Protocol (GTP) may be used on User Datagram Protocol (UDP) / IP to carry user plane protocol data units (PDUs). Xn-U may provide non-guaranteed delivery of user plane PDUs and may support data forwarding and flow control. The transport network layer of the Xn-C interface may be built on Stream Control Transport Protocol (SCTP) over IP. The application layer signaling protocol may be referred to as Xn Application Protocol (XnAP). The SCTP layer may be used to transport the application layer. The Xn-C interface can provide guaranteed delivery of RAN messages. At the transport IP layer, point-to-point transmission may be used to deliver signaling PDUs. The Xn-C interface can support Xn interface management, UE mobility management including context transfer and RAN paging, and dual connectivity.

[0040] The gNB 115 and ng-eNB 120 support 5GC over the NG interface. 110. More specifically, it may be connected to the Access and Mobility Management Function (AMF) 130 of the 5GC 110 by an NG-C interface and to the User Plane Function (UPF) 135 of the 5GC 110 by an NG-U interface. The transport network layer of the NG-U interface may be built on IP transport and may carry user plane PDUs between the NG-RAN nodes (e.g., gNB 115 or ng-eNB 120) and the UPF 135 using the GTP protocol over UDP / IP. The NG-U may provide unguaranteed delivery of user plane PDUs between the NG-RAN nodes and the UPF. The transport network layer of the NG-C interface may be built on IP transport. SCTP may be added on top of IP for reliable transmission of signaling messages. The application layer signaling protocol may be referred to as NG Application Protocol (NGAP). The SCTP layer may provide guaranteed delivery of application layer messages. Transport IP Layer So , Po An in-to-point transmission may be used to deliver signaling PDUs. The NG-C interface can provide the following functions: NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, configuration transfer, and alert message transmission.

[0041] The gNB 115 or ng-eNB 120 provides the following functions: radio resource management functions such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources (e.g., scheduling) to UEs in both uplink and downlink, IP and Ethernet header compression, data encryption and integrity protection, selection of the AMF at the UE attachment when the routing to the AMF cannot be determined based on information provided by the UE, routing of user plane data to the UPF, routing of control plane information to the AMF, connection setup and release, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (e.g., originating from the AMF), configuration of mobility and scheduling measurements and measurement reports, transport level packet marking in the uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, delivery of NAS messages, radio access network sharing, Dual QoS, and QoS mapping. It may be responsible for one or more of the following: connectivity, close interaction between NR and E-UTRA, and maintaining security and radio configuration for user plane 5G system (5GS) Cellular IoT (CIoT) optimization.

[0042] The AMF 130 provides the following functions: NAS signaling termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including validation of roaming rights, mobility management control (subscription and policy), support for network slicing, Ses The device may be responsible for one or more of the following: Session Management Function (SMF) selection; and 5GS CIoT optimization selection.

[0043] The UPF 135 may be responsible for one or more of the following functions: anchor point for intra / inter-RAT mobility (if applicable); external PDU session point for interconnection to the data network; packet routing and forwarding; packet inspection and application of the user plane part of policy rules; traffic usage reporting; uplink classifier supporting routing of traffic flows to the data network; branching point to support multi-homed PDU sessions; QoS operations for the user plane such as packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (Service Data Flow (SDF) to QoS Flow mapping); and downlink packet buffering and downlink data notification triggering.

[0044] As shown in FIG. 1, the NG-RAN 105 may support a PC5 interface between two UEs 125 (e.g., UE 125A and UE 125B). In the PC5 interface, the direction of communication between two UEs (e.g., from UE 125A to UE 125B or vice versa) is called the sidelink. Sidelink transmission and reception over the PC5 interface is supported when the UE 125 is within the coverage of the NG-RAN 105 and when the UE 125 is out of the coverage of the NG-RAN 105, regardless of which RRC state the UE 125 is in. Support for V2X services over the PC5 interface is provided by NR sidelink communication and / or V2X sidelink communication.

[0045] PC5-S signaling is used for unicast link establishment using direct communication request / accept messages. The UE self-assigns the source Layer-2 ID of the PC5 unicast link, e.g. based on the V2X service type. During the unicast link establishment procedure, the UE sends its own source Layer-2 ID of the PC5 unicast link to a peer UE, e.g. the UE that has received the destination ID from higher layers. The source Layer-2 ID and destination Layer-2 ID pair can uniquely identify a unicast link. The receiving UE verifies that the destination ID belongs to it and accepts the unicast link establishment request from the sending UE. During the PC5 unicast link establishment procedure, the PC5-RRC procedure on the Access Stratum layer is invoked for UE sidelink context establishment as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling allows UE capability exchange and AS layer configuration, e.g. sidelink radio bearer configuration, between a pair of UEs with which a PC5 unicast link is established.

[0046] NR sidelink communication can support one of three types of transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) for a pair of source Layer 2 ID and destination Layer 2 ID in an AS. The unicast transmission mode is characterized by the support of one PC5-RRC connection between peer UEs for the pair, the transmission and reception of control information and user traffic between peer UEs in the sidelink, the support of sidelink HARQ feedback, the support of sidelink transmit power control, the support of RLC acknowledged mode (AM), and the detection of radio link failure for the PC5-RRC connection. The groupcast transmission is characterized by the transmission and reception of user traffic between UEs belonging to a group in the sidelink, and the support of sidelink HARQ feedback. The broadcast transmission is characterized by the transmission and reception of user traffic between UEs in the sidelink.

[0047] For NR sidelink communications, the source Layer-2 ID, destination Layer-2 ID, and PC5 link identifier are used. The source Layer-2 ID is the identifier used in the sidelink communication frame. Send out The Destination Layer 2 ID may be a link layer identity that identifies a device or a group of devices. Is a recipient ofThe source Layer-2 ID may be a link layer identification that identifies the device. In some examples, the source Layer-2 ID and the destination Layer-2 ID may be assigned by a management function in the core network. The source Layer-2 ID can identify the source of the data in the NR sidelink communication. The source Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the LSB portion (8 bits) of the source Layer-2 ID and may be forwarded to the sender's physical layer. This can identify the source of the intended data in the sidelink control information and can be used for packet filtering at the receiver's physical layer. The second bit string may be the MSB portion (16 bits) of the source Layer-2 ID and may be carried in a Media Access Control (MAC) header. This can be used for packet filtering at the receiver's MAC layer. The destination Layer-2 ID can identify the target of the data in the NR sidelink communication. For NR sidelink communication, the destination Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the LSB part (16 bits) of the destination Layer 2 ID and may be forwarded to the sender's physical layer. This may identify the target of the intended data in the sidelink control information and may be used for packet filtering at the receiver's physical layer. The second bit string may be the MSB part (8 bits) of the destination Layer 2 ID and may be carried in the MAC header. This may be used for packet filtering at the receiver's MAC layer. The PC5 link identifier may uniquely identify a PC5 unicast link in the UE for the lifetime of the PC5 unicast link. The PC5 link identifier is used to indicate the PC5 unicast link for which a sidelink Radio Link Failure (RLF) declaration has been made and the PC5-RRC connection has been released.

[0048] 2A and 2B show an example of a user plane and control plane radio protocol stack, respectively, in accordance with some aspects of various exemplary embodiments of the present disclosure. As shown in FIG. 2A, the user plane protocol stack of the Uu interface (between the UE 125 and the gNB 115) includes the Service Data The Layer 1 includes sublayers of Layer 2, such as Layer 1 Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, MAC 204 and MAC 214, and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0049] The PHY 205 and PHY 215 provide transport channels 244 to the MAC 204 and MAC 214 sublayers. The MAC 204 and MAC 214 sublayers provide logical channels 243 to the RLC 203 and RLC 213 sublayers. The RLC 203 and RLC 213 sublayers provide RLC channels 242 to the PDCP 202 and PCP 212 sublayers. The PDCP 202 and PDCP 212 sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. The radio bearers may be classified into two groups: Data Radio Bearers (DRBs) for user plane data and Signaling Radio Bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to the 5GC.

[0050] The main services and functions of the MAC 204 or MAC 214 sublayer are mapping between logical channels and transport channels, MultipleMultiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to different logical channels to / from Transport Blocks (TBs) passed to / from the physical layer on transport channels, reporting of scheduling information, error correction with Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)), priority handling between UEs with dynamic scheduling, priority handling between logical channels of one UE with Logical Channel Prioritization (LCP), priority handling between overlapped resources of one UE, and padding. A single MAC entity may support multiple numerologies, transmission timings, and cells. Mapping restrictions in logical channel prioritization that control which numerologies, cells, and transmission timings a logical channel can use.

[0051] The HARQ function can ensure delivery between peer entities at Layer 1. If the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process can support one TB, and if the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process can support one or multiple TBs.

[0052] The RLC 203 or RLC 213 sublayer can support three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration may be per logical channel independent of the numerology and / or transmission time, and the Automatic Repeat Request (ARQ) may operate with any of the numerologies and / or transmission times for which the logical channel is configured.

[0053] The main services and functions of the RLC 203 or RLC 213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include transport of higher layer PDUs, sequence numbering independent of the PDCP sequence number (UM and AM), error correction through ARQ (AM only), segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), discard of RLC SDUs (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0054] The automatic repeat request in the RLC 203 or RLC 213 sublayer has the following properties: ARQ retransmits RLC SDUs or RLC SDU segments based on an RLC status report. Polling for RLC status reports may be used if required by RLC. The RLC receiver may also trigger an RLC status report after detecting a missing RLC SDU or RLC SDU segment.

[0055] The main services and functions of the PDCP 202 or PDCP 212 sublayer include forwarding of data (user plane or control plane), maintenance of the PDCP sequence number (SN), header compression and decompression using the Robust Header Compression (ROHC) protocol, header compression and decompression using the EHC protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discard, split bearer routing, duplication, reordering and in-order delivery, out-of-order delivery, and duplicate discarding.

[0056] The main services and features of SDAP 201 or SDAP 211 are QoS flow and data radio bearer mapping, and the marking of QoS Flow ID (QFI) on both downlink and uplink packets. A single protocol entity of the SDAP may be configured for each individual PDU session.

[0057] As shown in FIG. 2B, the control plane protocol stack of the Uu interface (between UE 125 and gNB 115) includes the PHY layer (Layer 1), the MAC, RLC and PDCP sublayers of Layer 2, and further the RRC 206 and RRC 216 sublayers, as described above. The main services and functions of the RRC 206 and RRC 216 sublayers on the Uu interface include broadcast of AS and NAS related system information, paging initiated by 5GC or NG-RAN, establishment, maintenance and release of RRC connection between UE and NG-RAN (including adding, modifying and releasing carrier aggregation and adding, modifying and releasing dual connectivity in NR or between E-UTRA and NR), security functions including key management, establishment, configuration, maintenance and release of SRBs and DRBs, mobility functions (including handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, and inter-RAT mobility), QoS management functions, control of UE measurement reports and reports, detection and recovery of radio link failures, and forwarding of NAS messages between NAS and UE. The NAS 207 and NAS 227 layers are control protocols (terminated in the AMF on the network side) that perform functions such as authentication, mobility management, security control, etc.

[0058] 3A and 3B respectively show example mappings between logical channels and transport channels in the downlink and uplink in some aspects of various exemplary embodiments of the present disclosure. Different types of data transfer services may be provided by the MAC. Each logical channel type may be defined by what type of information is transferred. The logical channels may be classified into two groups: control channels and traffic channels. The control channels are used only for transferring control plane information. The broadcast control channel (BCCH) is a downlink channel for broadcasting system control information. The paging control channel (PCCH) is a downlink channel that carries paging messages. The common control channel (CCCH) is a channel for transmitting control information between the UE and the network. This channel may be used for UEs that do not have an RRC connection with the network. The dedicated control channel (DCCH) is a point-to-point bidirectional channel that transmits dedicated control information between the UE and the network and is used by UEs that have an RRC connection. The traffic channel may be used only for transferring user plane information. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to one UE for transferring user information. A DTCH can exist in both the uplink and downlink.

[0059] Downlink transport channel types include the Broadcast Channel (BCH), the Downlink Shared Channel (DL-SCH), and the Paging Channel (PCH). The BCH is characterized by a fixed, predefined transport format and the requirement to be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances. The DL-SCH is characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for discontinuous reception (DRX) of the UE to enable UE power saving. 。P The CH supports Discontinuous Reception (DRX) in the UE to enable UE power saving (DRX cycles are determined by the network and assigned to the UE). The BCH is characterized by the requirement that it be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances, and that it be dynamically mapped onto physical resources that can also be used for traffic / other control channels.

[0060] In the downlink, the following connections exist between logical channels and transport channels: BCCH may be mapped to BCH. BCCH may be mapped to DL-SCH. PCCH may be mapped to PCH. CCCH may be mapped to DL-SCH. DCCH may be mapped to DL-SCH. DTCH may be mapped to DL-SCH.

[0061] Types of uplink transport channels include the uplink shared channel (UL-SCH) and the random access channel (RACH). The UL-SCH is characterized by the possibility of using beamforming, support for dynamic link adaptation by varying transmit power and potentially modulation and coding, support for HARQ, and support for both dynamic and quasi-static resource allocation. The RACH is characterized by limited control information and collision risk.

[0062] In the uplink, the following connections exist between logical channels and transport channels: CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, DTCH may be mapped to UL-SCH.

[0063] 4A and 4B respectively illustrate examples of mapping between transport channels and physical channels in the downlink and uplink in accordance with some aspects of various exemplary embodiments of the present disclosure. The physical channels in the downlink include a physical downlink shared channel (PDSCH), a physical downlink control channel (PDCCH), and a physical broadcast channel (PBCH). The PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. No transport channels are mapped to the PDCCH, but downlink control information (DCI) is transmitted via the PDCCH.

[0064] The physical channels in the uplink include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). The UL-SCH transport channel may be mapped to the PUSCH, and the RACH transport channel may be mapped to the PRACH. No transport channel is mapped to the PUCCH, but uplink control information (UCI) is transmitted via the PUCCH.

[0065] Sidelink Radio Bearers (SLRBs) can be classified into two groups: Sidelink Data Radio Bearers (SL DRBs) for user plane data and Sidelink Signaling Radio Bearers (SL SRBs) for control plane data. Separate SL SRBs using different SCCHs are configured for PC5-RRC and PC5-S signaling, respectively.

[0066] FIG. 5 illustrates an example of physical signals in the downlink and uplink in accordance with some aspects of various exemplary embodiments of the present disclosure. Demodulation Reference Signals (DM-RS) may be used in the downlink and uplink and may be used for channel estimation. The DM-RS is a UE-specific reference signal that is transmitted along with a downlink, uplink, or sidelink physical channel to estimate the channel of the physical channel. The PT-RS is used for phase estimation and coherent detection. The phase tracking reference signal (PT-RS) may be used in the downlink and uplink to track the phase and mitigate performance loss due to phase noise. The PT-RS is primarily used to estimate and minimize the impact of common phase error (CPE) on system performance. Due to phase noise characteristics, the PT-RS signal has low density in the frequency domain and high density in the time domain. The PT-RS, in combination with the DM-RS, is transmitted when the network is configured to assume the presence of the PT-RS. The positioning reference signal (PRS) may be used in the downlink for positioning with different positioning techniques. The PRS is used to measure the delay of the downlink transmission by correlating the received signal from the base station with a local replica in the receiver. The channel state information reference signal (CSI-RS) may be used in the downlink. The CSI-RS is used for channel state estimation, reference signal received power (RSRP) measurement for mobility and beam management, time / frequency tracking for demodulation, among others. CSI-RS may be configured specifically for a UE, but multiple users may share the same CSI-RS resources. The UE determines the CSI reports and transmits them in the uplink to the base station using the PUCCH or PUSCH. Primary Synchronization Signals (PSS) and Secondary Synchronization Signals (SSS) are used for radio frame synchronization. PSS and SSS are used for cell search procedures during initial attach or for mobility purposes. Sounding Reference Signals (SRS) may be used in the uplink for uplink channel estimation. Similar to CSI-RS, SRS can serve as a QCL reference for other physical channels so that they can be configured and transmitted in much the same manner as SRS.

[0067] 6 illustrates an example of Radio Resource Control (RRC) states and transitions between different RRC states in accordance with some aspects of various exemplary embodiments of the present disclosure. A UE is in one of three RRC states: an RRC connected state 610, an RRC idle state 620, and an RRC inactive state 630. After powering on, the UE is in the RRC idle state 620, and the UE establishes a connection with the network via an RRC connection establishment procedure using initial access to perform data transfer and / or voice calls. Once the RRC connection is established, the UE is in the RRC connected state 610. The UE can be released from the RRC idle state 620 to the RRC connected state 630 using an RRC connection establishment / release procedure 640. 610 or from the RRC connected state 610 to the RRC idle state 620.

[0068] The RRC inactive state 630 is used to reduce the signaling load and latency caused by frequent transitions from the RRC connected state 610 to the RRC idle state 620 when the UE frequently transmits small data. In the RRC inactive state 630, the AS context is stored by both the UE and the gNB. This results in a faster state transition from the RRC inactive state 630 to the RRC connected state 610. The UE transitions from the RRC inactive state 630 to the RRC connected state 610 or from the RRC connected state 610 to the RRC inactive state 630 using an RRC connection resume / deactivation procedure 660. The UE transitions from the RRC inactive state 630 to the RRC idle state 620 using an RRC connection release procedure 650.

[0069] FIG. 7 illustrates an example of a frame structure and physical resources in some aspects of various exemplary embodiments of the present disclosure. Downlink or uplink transmission is performed by a frame that includes ten 1 ms subframes and has a time length of 10 ms. Each subframe includes 1, 2, 4, ... slots, and the number of slots per subframe depends on the subcarrier spacing of the carrier on which the transmission is performed. The time length of a slot can be 14 symbols with a normal cyclic prefix (CP) or an extended cyclic prefix (CP). In some cases, the number of slots in a subframe is 12 symbols with an extended CP, and in other cases, the number of slots in a subframe is variable in time depending on the subcarrier spacing used, such that the number of slots in a subframe is an integer. Figure 7 shows a resource grid in the time and frequency domain. Each element of the resource grid containing one symbol in time and one subcarrier in frequency is called a resource element (RE). A resource block (RB) may be defined as 12 consecutive subcarriers in the frequency domain.

[0070] In some examples, with non-slot-based scheduling, the transmission of a packet occurs over a portion of a slot, e.g., 2, 4, or 7 OFDM symbols, also called a minislot. Minislots are used for low-latency applications such as URLLC and operation in unlicensed bands. In some embodiments, minislots may also be used for fast flexible scheduling of services (e.g., preemption of URLLC for eMBB).

[0071] FIG. 8 illustrates an example of component carrier configurations in different carrier aggregation scenarios in some aspects of various exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE 125 may receive or transmit simultaneously on one or more CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs in the same band or different bands as illustrated in FIG. 8. The gNB 115 and the UE 125 may communicate using a serving cell. The serving cell is associated with at least one downlink CC (e.g., may be associated with only one downlink CC or may be associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cCell (SCell).

[0072] The UE 125 can adjust the timing of its uplink transmission using an uplink timing control procedure. A timing advance (TA) can be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB 115 can determine a desired timing advance setting and provide it to the UE. The UE 125 can use the provided TA to determine its uplink transmit timing relative to the UE's observed downlink receive timing.

[0073] In the RRC connected state, the gNB 115 is responsible for maintaining the timing advance to keep L1 synchronization. Serving cells with uplinks to which the same timing advance applies and using the same timing reference cell are grouped into a Timing Advance Group (TAG). A TAG contains at least one serving cell with a configured uplink. The mapping of serving cells to TAGs is set by RRC. For a primary TAG, the UE uses the PCell as the timing reference cell, except for shared spectrum channel access where in some cases a SCell may also be used as the timing reference cell. For a secondary TAG, the UE 125 can use any of the activated SCells of this TAG as the timing reference cell and does not have to change this unless necessary.

[0074] Timing advance updates may be signaled from the gNB 115 to the UE 125 via a MAC CE command. Such a command may restart a TAG-specific timer that indicates whether L1 can be synchronized or not; when the timer is running, L1 is considered to be synchronized, otherwise L1 is considered to be out of sync (in this case , uplink transmission occurs only on the PRACH).

[0075] A UE 125 with single timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into one TAG) sharing the same timing advance. A UE 125 with multiple timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells (multiple serving cells grouped into multiple TAGs) with different timing advances. NG-RAN ensures that each TAG contains at least one serving cell. A non-CA capable UE 125 may receive on a single CC and transmit on a single CC corresponding to only a single serving cell (one serving cell in one TAG).

[0076] The multi-carrier property of the physical layer in case of CA may be exposed to the MAC layer, and one HARQ entity may be required per serving cell. When CA is configured, the UE 125 may have one RRC connection with the network. In RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) provides NAS mobility information. Depending on the UE capabilities, the SCell is configured to form a set of serving cells together with the PCell. The set of serving cells configured for a UE includes one PCell and one or more SCells. Reconfiguration, addition, and deletion of SCells may be performed by RRC.

[0077] In a dual connectivity scenario, the UE 125 has two MAC entities, a Master Cell Group (MCG) for communication with a master base station and a Secondary Cell Group (SCG) for communication with a secondary base station, i.e. ,Ma For MCG to communicate with base stations MAC Entity and a MAC entity for the SCG for communication with a secondary base station.

[0078] FIG. 9 illustrates an example of Bandwidth Part configuration and switching in some aspects of various exemplary embodiments of the present disclosure. A UE (e.g., 125) is configured with one or more Bandwidth Parts (BWPs) 910 in a given component carrier. In some examples, one of the one or more Bandwidth Parts can be active at the same time. The active Bandwidth Part defines the UE's operating bandwidth within the operating bandwidth of the cell. For initial access, an initial Bandwidth Part 920 determined from system information is used until the configuration of the UE in the cell is received. For example, in Bandwidth Adaptation (BA) by BWP switching 940, the UE's transmission and reception bandwidth is adjusted because it is not as large as the cell's bandwidth. For example, the width can be ordered to be variable (e.g., shrink during low activity periods to save power), the position can be moved in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing can be ordered to be variable (e.g., to enable different services). First active BWP 930 may be an active BWP upon RRC (re)configuration of a PCell or activation of an SCell.

[0079] For a downlink or uplink BWP in the set of downlink or uplink BWPs, respectively, the UE is provided with the following configuration parameters: subcarrier spacing (SCS), cyclic prefix, number of common RBs and consecutive RBs, index in the set of downlink or uplink BWPs by the respective BWP-Id, a set of BWP common parameters and a set of BWP specific parameters. A BWP is provided with the subcarrier spacing and subcarrier spacing configured for the BWP. Based on the cyclic prefix, the UE is associated with an OFDM numerology. For the serving cell, the UE is provided with a default downlink BWP among the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP is the initial downlink BWP.

[0080] A downlink BWP is associated with a BWP inactivity timer. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is configured, the UE may perform BWP switching to the default BWP. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not configured, the UE may perform BWP switching to the initial downlink BWP.

[0081] 10 illustrates an example of a UL beamforming configuration 1000 according to some aspects of various exemplary embodiments of the present disclosure. 1005 The UE 1005 may use a beamforming scheme for UL transmission of data and control information. The beamformed data is transmitted on the PUSCH and the beamformed control information is transmitted on the PUCCH. As shown, the UE 1005 may use a beamforming scheme to direct an antenna beam 1014 to the gNB 1009, rather than spreading the signal in all directions from its antenna. The UE 1005 may use an antenna array to direct the radiation pattern 1014 to the gNB 1009. By directing the beam 1014 in a particular direction, the beamforming scheme of the configuration 1000 allows the UE 1005 to deliver a higher quality signal to the gNB 1009, increasing data rates and reducing latency without increasing the transmit power of the UE 1005. Additionally, the beamforming scheme may reduce interference from other users in the same cell or neighboring cells.

[0082] In some embodiments, the gNB 1009 may transmit control information via a downlink control information (DCI) message 1019. The gNB 1009 may transmit the DCI 1019 via a PDSCH. The DCI may include scheduling assignments for the PUSCH and PUCCH. For example, the DCI 1019 may include frequency and time domain resource allocations, HARQ feedback, transmit power control (TPC) commands, modulation and coding schemes, antenna ports, etc. In some embodiments, the UE 1005 may use the information signals in the DCI message 1019 to estimate and update beamforming weights as described in Figures 11-12. In some other embodiments, the gNB 1009 may transmit beamforming commands via the DCI message 1019, and the UE 1005 may use the information signals in the DCI message 1019 to estimate and update beamforming weights as described in Figures 11-12.

[0083] 11 illustrates an embodiment of a UL beamforming configuration 1100 according to some aspects of various exemplary embodiments of the present disclosure. The UE 1005 includes an antenna array with m+1 transmit antennas 1114. In the configuration 1100, the UE 1005 applies a beamforming scheme to the transmission of a signal at the antenna before transmitting to the gNB. In the beamforming scheme 1100, the transmit signal is multiplied by a beamforming vector.

number

[0084] The beamforming module 1107 calculates the beamforming vector W based on the information received from the DCI message 1019. The beamforming vector W is calculated such that the received signals from the antennas 1114 are coherently added to the receiving antennas at the gNB 1009. In some embodiments, the beamforming module 1107 estimates the beamforming vector W at the beginning of each time frame and can use it for the entire time frame length. In some other embodiments, the beamforming module 1107 may update the beamforming vector W in response to dynamic wireless propagation channel variations during the time frame length. The power amplifier (PA) 1111 converts a low power radio frequency signal (RF) to a higher power signal to drive the antenna 1114.

[0085] The DCI message 1019 may include a TPC command informing the UE 1005 to increase or decrease the transmit power to achieve a target SNR at the gNB 1009. In some embodiments, the UE 1005 may use the TPC command to calculate the beamforming vector W and select the transmit power. The calculation of the beamforming vector and the selection of the transmit power may be performed jointly or independently. In some implementations, the phases φi,i=1,...,m may be calculated by a code descending gradient algorithm.

number

[0086] where φi(n), i=1,...,m is the beamforming phase φi at time n, tpc(n) is the TPC command at time n, Δφ is the phase update step, and sgn(x) is the sign of x. Table 1 shows an example of the mapping between TPC commands and tpc(n).

[0087] In some embodiments, the transmit power is updated as follows:

number

[0088] Here, Pmax is the maximum power that the UE 1005 can transmit. [Table 1]

[0089] In some embodiments, the DCI message 1019 may include both beamforming commands and TPC commands independently. The beamforming commands provide feedback regarding the application and calculation of the UL beamforming vector. The UE 1005 may use the beamforming commands to calculate the beamforming vector W and select the transmit power. The calculation of the beamforming vector and the selection of the transmit power may be performed independently. In some implementations, the phases φi,i=1,...,m may be calculated by a descending gradient algorithm.

number

[0090] where F(n) is the phase feedback at time n and μ is a constant. The calculated phase φi(n) is mapped to the interval [-π,π]. For example, a 2-bit phase feedback is shown in Table 2. [Table 2]

[0091] FIG. 12 illustrates a user equipment (UE) for transmitting and / or receiving in accordance with some aspects of various exemplary embodiments of the present disclosure. 1005 12 shows an example of components of a user equipment. 1005 The user equipment may be 1005The antenna 1210 may be used to transmit or receive electromagnetic signals. The antenna 1210 may include one or more antenna elements and may enable different input / output antenna configurations including a Multiple-Input Multiple Output (MIMO) configuration, a Multiple-Input Single-Output (MISO) configuration, and a Single-Input Multiple-Output (SIMO) configuration. In some embodiments, the antenna 1210 may enable a massive MIMO configuration having tens or hundreds of antenna elements. The antenna 1210 may enable other multi-antenna techniques such as beamforming. In some examples, the UE 1005 Ability or UE 1005 Depending on the type of UE (e.g. low complexity UE), 1005 may only support a single antenna.

[0092] The transceiver 1220 can communicate bidirectionally over the wireless links described herein via the antenna 1210. For example, the transceiver 1220 may represent a wireless transceiver in a UE and communicate bidirectionally with a wireless transceiver in a base station, or vice versa. The transceiver 1220 can include a modem that modulates packets, provides the modulated packets to the antenna 1210 for transmission, and demodulates packets received from the antenna 1210.

[0093] The memory 1230 may include RAM and ROM. The memory 1230 may include computer readable computer executable code that includes instructions that, when executed, cause the processor to perform various functions described herein. 1235 In some examples, the memory 1230 may include a Basic Input / Output System (BIOS) that may control basic hardware or software operations such as interaction with peripheral components or devices, among other things.

[0094] The processor 1240 may include a hardware device having processing capabilities (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, the processor 1240 may be configured to operate the memory using a memory controller. In other examples, the memory controller may be incorporated into the processor 1240. The processor 1240 may include a UE 1005 The processor 1200 is configured to execute computer-readable instructions stored in a memory (eg, memory 1230) to cause the processor 1200 to perform various functions.

[0095] Central processing unit (CPU) 1250 may perform basic arithmetic, logical, control, and input / output (I / O) operations specified by computer instructions in memory 1230. 1005 The user equipment (UE) may include additional peripheral components such as a graphics processing unit (GPU) 1260 and a global positioning system (GPS) 1270. The GPU 1260 is 1005 The GPS 1270 is a dedicated circuit for rapid manipulation and modification of the memory 1230 to accelerate the processing performance of the GPS 1270. 1005 The mobile phone may be used to enable location-based services or other services based on the geographic location of the mobile phone.

[0096] The beamforming module 1207 may be implemented as hardware, software, or other The beamforming module 1207 may be implemented via a combination of the above. For example, the beamforming module 1207 may be implemented as instruction code 1235, stored in the memory 1230, and executed by the processor 1240, or may be implemented as a circuit. The beamforming module 1207 is used to perform various aspects and functions related to the present disclosure. For example, the beamforming module 1207 is configured to manage beamforming functions including calculation and application of beamforming vectors, transmit power control, processing beamforming and power control feedback from the gNB, and reporting beamforming information to the gNB. In some examples, the beamforming module 1207 may perform a set of physical layer / medium access control procedures to obtain and maintain a set of beam pair correspondences, e.g., beams used at the BS-side transmission / reception points (TRPs) paired with beams used at the UE. The beam pair correspondences are used for downlink and uplink transmission and reception. The beam management procedures may include the beam management procedure for ... FormingThe process may include one or more of vector calculation and application, beamforming and power control command reception, beam sweeping process, beam measurement process, beam reporting process, beam determination process, beam maintenance process, and beam recovery process. For example, the beamforming vector may be calculated at the beginning of a time frame for a low-varying wireless channel and tracked during a time frame for a fast-varying wireless channel. The power control command and the beamforming command are received via the PDCCH, and the UE decodes the PDCCH to execute the command. The beam sweeping process is used to cover a spatial region with transmitted and / or received beams during a time interval in a predetermined manner. The beam measurement process is used by the TRP or UE to measure characteristics of a received beamforming (BF) signal. The beam reporting process is used by the UE to report information of the BF signal based on the beam measurement. The beam determination process is used by the TRP or UE to select Tx / Rx beams. The beam maintenance process may be used by the TRP or UE to maintain candidate beams by tracking or refining the beams to adapt to channel changes due to UE movement or disturbance. The beam recovery process is used by the UE to identify a new candidate beam after detecting a beam failure and subsequently indicate a TRP of a beam recovery request with information indicating the new candidate beam.

[0097] In some examples, beam management may be performed in the UL and / or DL ​​directions. If good channel reciprocity is available (e.g., in a time division duplex (TDD) system), beam management in one direction may be based on another direction, e.g., UL beam management may be performed well based on the results of DL beam management. In some examples, beam correspondence may be used based on the uplink-downlink reciprocity of the beamformed channel, e.g., the UL Tx / Rx beams may be determined based on beam measurements of the DL beamformed reference signal (RS).

[0098] In some examples, group-based beam management may be used to manage beams on a group-by-group basis rather than on a beam-by-beam basis, e.g., considering that beams sharing similar channel characteristics may be placed in the same beam group. Beam management procedures may include beam sweeping, beam measurement, beam reporting (e.g., grouping-based beam reporting), beam determination, beam maintenance (e.g., group-based beam maintenance), and beam failure recovery.

[0099] FIG. 13 illustrates a gNB for transmission and / or reception in accordance with some aspects of various exemplary embodiments of the present disclosure. 1009 13 shows an example of components of a gNB. 1009 It may be within the gNB 1009 The antenna 1310 may be used to transmit or receive electromagnetic signals. The antenna 1310 may include one or more antenna elements, M The antennas 1310 may enable different input / output antenna configurations, including multiple-input multiple output (MIMO), multiple-input single-output (MISO), and single-input multiple-output (SIMO) configurations. In some embodiments, the antennas 1310 may enable massive MIMO configurations with tens or hundreds of antenna elements. The antennas 1310 may enable other multi-antenna techniques, such as beamforming. In some examples, the gNB 1009 Depending on the capabilities of gNB 1009 may only support a single antenna.

[0100] The transceiver 1320 can communicate bidirectionally over wireless links as described herein via the antenna 1310. For example, the transceiver 1320 may represent a wireless transceiver in a UE and may communicate bidirectionally with a wireless transceiver in a base station, or vice versa. The transceiver 1320 can include a modem for modulating packets, providing the modulated packets to the antenna 1310 for transmission, and demodulating packets received from the antenna 1310.

[0101] The memory 1330 may include RAM and ROM. The memory 1330 may include computer readable computer executable code that includes instructions that, when executed, cause the processor to perform various functions described herein. 1335 In some examples, the memory 1330 may include a Basic Input / Output System (BIOS) that may control basic hardware or software operations such as interaction with peripheral components or devices, among other things.

[0102] The processor 1340 may include a hardware device having processing capabilities (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some examples, the processor 1340 may be configured to operate the memory using a memory controller. In other examples, the memory controller may be incorporated into the processor 1340. The processor 1340 may be configured to control the gNB 1009 The processor 1300 is configured to execute computer-readable instructions stored in a memory (eg, memory 1330) to cause the processor 1300 to perform various functions.

[0103] A central processing unit (CPU) 1350 may perform basic arithmetic, logical, control, and input / output (I / O) operations specified by computer instructions in memory 1330 .

[0104] 14A illustrates an example of a downlink control information (DCI) message structure 1400 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1400 (e.g., DCI message format 0_1, 0_0, 1_0) is used by a gNB to transmit beamforming and TPC commands to UEs in a cell. As shown, the DCI message 1400 includes the following: (i) DCI identifier 1403 indicates DCI format 0_1 / 0_0 / 1_0. (ii) The DCI field 1407 includes information for scheduling the PUSCH in one cell. (iii) Transmit Power Control (TPC) / Phase Feedback (PF) field 1411 is 2 bits in length and is used to instruct the UE to increase or decrease its transmit power.

[0105] DCI format 0_0 / 0_1 is used to schedule PUSCH. , DCI format 1_0 is used to schedule PDSCH in one cell. DCI message 1400 is used to schedule group-common PDCCH or UE-specific PDCCH. PDCCHIn some examples, if the UE does not receive the DCI format 1400 via the group-common PDCCH, the UE may receive the DCI format 1400 via the UE-specific PDCCH in the slot. The gNB may inform the UE via RRC signaling whether to decode the group-common PDCCH or the UE-specific PDCCH. In some examples where the group-common PDCCH is transmitted, the UE may decide whether to decode the common group PDCCH. Furthermore, if the UE is monitoring the common group PDCCH, the UE may process the detected UE-specific PDCCH regardless of whether the group-common PDCCH is received or not.

[0106] In some examples, when the UE decodes the DCI message 1400, the UE can map the TPC command to a tpc value obtained from a lookup table (e.g., Table 1), can execute a beamforming control loop to calculate or track the beamforming phase (e.g., Equation (1)), and can execute a TPC loop to adjust the transmit power. force( For example, Equation (2)) may be selected or updated. The order of the beamforming control loop and the TPC loop may be interchangeable. In some implementations, Equations (1) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating the values ​​of Equations (1) and (2) and storing them in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each relevant scenario.

[0107] 14B illustrates an example of a downlink control information (DCI) message structure 1450 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1450 (e.g., DCI message format 0_1, 0_0, 1_0) is used by a gNB to transmit beamforming and TPC commands to UEs in a cell. As shown, the DCI message 1450 may include the following: (i) DCI identifier 1403 indicates DCI format 0_1 / 0_0 / 1_0 (ii) The DCI field 1407 includes information for scheduling the PUSCH in one cell. (iii) Transmit Power Control (TPC) Field 1461 contains two bits that are used to instruct the UE to increase or decrease its transmit power. (iv) Phase Feedback (PF) field 1463 includes 2 bits that are used to indicate the UE beamforming phase update command.

[0108] DCI format 0_0 / 0_1 may be used to schedule a PUSCH, and DCI format 1_0 may be used to schedule a PDSCH in one cell. The DCI message 1450 may be used to schedule a group-common PDCCH or a UE-specific PDCCH. PDCCH In some examples, if the UE does not receive the DCI format 1450 via the group-common PDCCH, the UE may receive the DCI format 1450 via the UE-specific PDCCH in the slot. The gNB may inform the UE via RRC signaling whether to decode the group-common PDCCH or the UE-specific PDCCH. In some examples where the group-common PDCCH is transmitted, the UE may decide whether to decode the common group PDCCH. Furthermore, when the UE is monitoring the common group PDCCH, the UE may determine whether to decode the group-common PDCCH. A detected UE-specific PDCCH can be processed regardless of whether a general PDCCH is received or not.

[0109] In some examples, upon decoding the DCI message 1450, the UE may map the PF command to an F(n) value obtained from a lookup table (e.g., Table 2), may execute a beamforming control loop to calculate or track the beamforming phase (e.g., Equation (3)), and may execute a TPC loop to adjust the transmit power. Power The order of the beamforming control loop and the TPC loop may be interchangeable. In some implementations, equations (3) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating the values ​​of equations (3) and (2) and storing them in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each relevant scenario.

[0110] 15A illustrates an example of a downlink control information (DCI) message structure 1500 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1500 (e.g., DCI message format 2_0) is used by a gNB to transmit beamforming and TPC commands to a group of UEs in a cell. As shown, the DCI message 1500 may include the following: (i) DCI identifier 1503 indicates DCI format 2_0. (ii) The DCI field 1507 contains information for signaling and scheduling a group of UEs in a cell. (iii) Transmit Power Control (TPC) / Phase Feedback (PF) field 1511a-1511n is 2 bits in length and is used to instruct the UEs in the group to increase or decrease their transmit power.

[0111] The DCI field 1507 is used to inform a group of UEs of the slot format, the available RB set, the channel occupation time (COT) duration, and the search space group switching. DCI format 2_0 is scrambled by the identifier SFI-RNTI and its size is configured by RRC signaling. TPC / PF field 1511a-1511n The beamforming vectors and transmit powers for the UEs in the group are Power 4 shows the TPC / PF commands to calculate and track.

[0112] In some examples, when a UE decodes the DCI message 1500, it can map the n TPC commands to n tpc values ​​obtained from a lookup table (e.g., Table 1), and for each UE in the group, it can perform a beamforming control loop to calculate or track the beamforming phase (e.g., Equation (1)), and perform a TPC loop to adjust the transmit power. Power The beamforming control loop and the TPC loop order may be selected or updated (e.g., Equation (2)). The beamforming control loop and the TPC loop order are interchangeable. In some implementations, Equations (1) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating the values ​​of Equations (1) and (2) and storing them in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each relevant scenario.

[0113] 15B illustrates an example of a downlink control information (DCI) message structure 1550 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1550 (e.g., DCI message format 2_0) is used by a gNB to transmit beamforming and TPC commands to a group of UEs. As shown, the DCI message 1550 may include the following: (i) DCI identifier 1553 indicates DCI format 2_0. (ii) DCI field 1557 contains information for signaling and scheduling a group of UEs in a cell. (iii) TPC fields 1561a-1561n each contain two bits that are used to instruct the UE to increase or decrease its transmit power. (iv) Each of the PF fields 1563a-1563n includes two bits that are used to indicate a UE beamforming phase update command.

[0114] The DCI field 1557 is used to inform a group of UEs of the slot format, the available RB set, the channel occupation time (COT) duration, and the search space group switching. The DCI format 2_0 is scrambled by the identifier SFI-RNTI and its size can be configured by RRC signaling. The TPC fields 1561a to 1561n are used to inform a group of UEs of the slot format, the available RB set, the channel occupation time (COT) duration, and the search space group switching. Your For TPC command PF fields 1563a-1563n may indicate PFs for calculating and tracking beamforming vectors for UEs in the group. command It can be shown that

[0115] In some examples, upon decoding the DCI message 1550, the UE may map the n TPC and n PF commands to n tpc values ​​obtained from a lookup table (e.g., Table 1), and for each UE in the group, may perform a beamforming control loop to calculate or track the beamforming phase (e.g., Equation (1)), and may perform a TPC loop to calculate or track the transmit power. Power The beamforming control loop and the TPC loop order may be selected or updated (e.g., Equation (2)). The beamforming control loop and the TPC loop order are interchangeable. In some implementations, Equations (1) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating the values ​​of Equations (1) and (2) and storing them in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each relevant scenario.

[0116] 16A illustrates an example of a downlink control information (DCI) message structure 1600 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1600 (e.g., DCI message format 2_7) may be used by a gNB to transmit beamforming and TPC commands to a group of UEs in a cell. As shown, the DCI message 1600 may include the following: (i) DCI identifier 1603 indicates DCI format 2_7. (ii) Transmit Power Control (TPC) / Phase Feedback (PF) fields 1611a-1611n are two bits in length and are used to instruct UEs in a group to increase or decrease their transmit power.

[0117] DCI format 2_7 is reserved and can be configured for a group of UEs to transmit TPC and PF commands. The size of DCI format 2_7 can be configured by RRC signaling. TPC / PF fields 1611a-1611n specify the beamforming vectors and transmit powers for the UEs in the group. Power 4 shows the TPC / PF commands to calculate and track.

[0118] In some examples, upon decoding the DCI message 1600, the UE may map the n TPC commands to n tpc values ​​obtained from a lookup table (e.g., Table 1). For each UE in the group, a beamforming control loop may be performed to calculate or track the beamforming phase (e.g., Equation (1)) and the transmit power. Power A TPC loop may be performed to select or update (e.g., Equation (2)). The beamforming control loop and TPC loop orders are interchangeable. In some implementations, Equations (1) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating and storing the values ​​of Equations (1) and (2) in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each associated scenario.

[0119] 15B illustrates an example of a downlink control information (DCI) message structure 1650 in accordance with some aspects of various exemplary embodiments of the present disclosure. The DCI message 1650 (e.g., DCI message format 2_7) is used by a gNB to transmit PF and TPC commands to a group of UEs. As shown, the DCI message 1650 may include the following: (i) DCI identifier 1653 indicates DCI format 2_7. (ii) TPC fields 1661a-1661n each contain two bits that are used to instruct the UE to increase or decrease its transmit power. (iii) PF fields 1663a-1663n, each field containing 2 bits used to indicate a UE beamforming phase update command.

[0120] The TPC fields 1611a to 1611n are used to control the transmission power. Master PF fields 1663a-1663n indicate commands for calculating and tracking beamforming vectors for UEs in the group.

[0121] In some examples, upon decoding the DCI message 1650, the UE may map the n TPC and n PF commands to n tpc values ​​obtained from a lookup table (e.g., Table 1), and for each UE in the group, may perform a beamforming control loop to calculate or track the beamforming phase (e.g., Equation (1)), and may perform a TPC loop to calculate or track the transmit power. Power The beamforming control loop and the TPC loop order may be selected or updated (e.g., Equation (2)). The beamforming control loop and the TPC loop order are interchangeable. In some implementations, Equations (1) and (2) may be pre-calculated and stored in a look-up table in memory. By pre-calculating the values ​​of Equations (1) and (2) and storing them in memory, processing delays can be significantly reduced. For example, the UE may pre-calculate beamforming phases for different propagation environments such as channel delay profile, Doppler spread, distance from gNB, modulation and coding scheme (MCS), store the beamforming phases in a look-up table, and accordingly select the corresponding phases for transmitting signals in each relevant scenario.

[0122] 17 is a flow diagram of a UL beamforming and power control method according to some aspects of various exemplary embodiments of the present disclosure. The method 1700 is described with reference to the gNB 1009 and UE 1005 described in FIGS. 10-13.

[0123] Steps 1702 In this case, the UE receives a DCI message indicating a TPC command from the gNB. For example, the DCI message may be in DCI message formats 0_0, 0_1, 1_0, 2_0, and 2_7, with reference to Figures 13 to 16. The DCI message may also include other information including scheduling information for the UE.

[0124] In step 1704, the UE decodes the DCI message, recovers the transmitted bits, and identifies the DCI field.

[0125] In step 1706, the UE determines the TPC command from the DCI message. Once the UE determines the TPC command, the UE maps the TPC command to a tpc value as previously described (eg, Table 1, Table 2).

[0126] In step 1710, the UE uses tpc to perform a phase tracking loop. For example, the UE may use Equation 1 or 3 to calculate and track the beamforming vectors.

[0127] In step 1714, the UE performs a power control loop using tpc. Power To select and adjust, Equation 2 can be used.

[0128] 18A and 18B show flow diagrams of a UL beamforming method 1800 and a power control method 1850, respectively, in accordance with some aspects of various exemplary embodiments of the present disclosure. It is understood that the method 1800 may be performed independently of the method 1850. The methods 1800 and 1850 may be implemented in conjunction with the gNB beamforming method described in FIGS. 10-13. 1009 and the UE 1005.

[0129] In step 1802, the UE receives a DCI message indicating a PF command from the gNB. For example, the DCI message may be DCI message format 0_0, 0_1, 1_0, 2_0, and 2_7, referring to Figures 13 to 16. The DCI message may also include other information including scheduling information for the UE.

[0130] In step 1806, the UE decodes the DCI message, recovers the transmitted bits, and identifies the DCI field.

[0131] In step 1810, the UE determines the PF command from the DCI message. Once the UE determines the PF command, the UE maps the PF command to a tpc value as previously described (eg, Table 1, Table 2).

[0132] Finally, the UE uses tpc to perform a phase tracking loop, per step 1814. For example, the UE may use Equation 1 or 3 to calculate and track the beamforming vectors.

[0133] In step 1852, the UE receives a DCI message from the gNB indicating the TPC command. For example, the DCI message may be DCI message format 0_0, 0_1, 1_0, 2_0, and 2_7, with reference to Figures 13 to 16. The DCI message may also include other information including scheduling information for the UE.

[0134] In step 1856, the UE decodes the DCI message, recovers the transmitted bits, and identifies the DCI field.

[0135] In step 1860, the UE determines the TPC command from the DCI message. TPC Once the command is determined, the UE maps the TPC command to the tpc value as described above. (e.g., Table 1, Table 2).

[0136] Finally, the UE uses tpc to perform a transmit power control loop, per step 1864. For example, the UE may use Equation 2 to select and adjust the transmit power.

[0137] 19 is a flow diagram of a method for selecting a beamforming or codebook-based precoding scheme for an UL transmission according to some aspects of various exemplary embodiments of the present disclosure. The method 1900 is described with reference to the gNB 1009 and the UE 1005 described in FIGS. 10-13.

[0138] In step 1902, the UE uses codebook-based precoding over a period T1 and calculates a transmit power per symbol P1. In the codebook-based precoding scheme, the UE selects a precoder from a set of predefined precoders for UL transmission of data and control signaling. For example, 3GPP TS38.211V16.3.0(2020-09) - 3rd Generation Partnership Project, Technical Specification Group Radio Access Network, NR, "Physical channels and modulation (Release 16)", which is incorporated herein by reference in its entirety, describes codebook-based precoding techniques for UL transmission in 5G-NR systems.

[0139] In step 1906, the UE uses UL beamforming for time period T1 and calculates a per-symbol transmit power P2.

[0140] In step 1910, the UE determines whether UL beamforming or codebook-based precoding can provide a higher power gain. If codebook-based precoding can provide a higher power gain, the UE proceeds to step 1914. If UL beamforming can provide a higher gain, the UE proceeds to step 1922.

[0141] In step 1914, the UE During period T2, A codebook-based precoding scheme is used for UL transmission of data and / or control signaling, and the transmit power per symbol is P1 Calculate.

[0142] In step 1918, the UE switches to short-term T1 (e.g., T1≦T2) UL beamforming and calculates per-symbol transmit power P2. The UE then proceeds to step 1910 and decides whether to use beamforming or codebook-based transmission.

[0143] In step 1922, the UE During period T2, Uses UL beamforming for UL transmission of data or control signaling, with transmit power per symbol P2 Calculate.

[0144] In step 1926, the UE switches to codebook-based precoding for a short period T1 (e.g., T1≦T2) and selects a per-symbol transmit power P1 The UE then proceeds to step 1910 and decides whether to use beamforming or codebook based transmission.

[0145] FIG. 20 illustrates a method for selecting a beamforming or single antenna scheme for UL transmission according to some aspects of various exemplary embodiments of the present disclosure. 10 to 13. The method 2000 will be described with reference to the gNB 1009 and the UE 1005 shown in FIG.

[0146] In step 2002, the UE determines a beamforming gain G. The beamforming gains for different propagation environments are pre-calculated and stored in the UE memory. From the beamforming gain G, the UE determines the beamforming gain G to achieve a target SNR required at the gNB for error-free decoding of the transmitted signal. Transmission power required for P B and and, Required transmit power for single antenna system P S and, can be calculated (e.g., P B =P S / G).

[0147] In step 2006, the UE calculates the RF power consumption due to beamforming and single antenna transmission. For example, the transmission power consumption of the architecture of FIG. RF The circuit power consumption and power amplifier power P of each RF chain are shown as PA Includes: RF is a constant power regardless of the transmission power P, and P PA depends on the transmission power. P PA , P PA = P / η, where η is the power amplifier efficiency. As a result, the total power consumption of a UE with m + 1 antennas employing a beamforming scheme can be calculated as follows:

number

[0148] P RF and ηis stored in the UE memory, and P TOT is accessed when it is necessary to compute

[0149] In step 2012, the UE calculates the total power consumption P1 of the UL beamforming scheme with m+1 antennas. For example, the UE can calculate P1 using equation (4).

[0150] In step 2016, the UE calculates the total power consumption P2 of the single antenna transmission scheme. For example, the UE calculates P2 using the formula (5) can be used.

number

[0151] In step 2010, the UE determines whether to use beamforming or single antenna transmission based on the difference between the total power consumption ΔP=P2-P1. If ΔP>0, the UE performs step 2024 If ΔP<0, the UE proceeds to step 2020 Proceed to.

[0152] In step 2020, the UE uses a single antenna scheme for transmitting data and control signals to the gNB.

[0153] In step 2024, the UE uses a UL beamforming scheme for transmitting data and control signals to the gNB.

[0154] FIG. 21 is a sequence diagram illustrating a UL beamforming method according to some aspects of some exemplary embodiments of the present disclosure described above in FIGS. 17 to 20. In FIG.

[0155] The exemplary blocks and modules described in this disclosure with respect to various exemplary embodiments may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general purpose processors include, but are not limited to, a microprocessor, any conventional processor, controller, microcontroller, or state machine. In some examples, a processor may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0156] The functions described in this disclosure may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or codes may be stored or transmitted to a computer-readable medium to implement the functions. Other examples for implementing the functions disclosed herein are also within the scope of this disclosure. Implementation of the functions may be via physically co-located or distributed elements (e.g., at various locations), including being distributed such that some of the functions are implemented in different physical locations.

[0157] Computer-readable media includes, but is not limited to, non-transitory computer storage media. Non-transitory storage media may be accessed by general-purpose or special-purpose computers. Examples of non-transitory storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage, and the like. Non-transitory media may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by general-purpose or special-purpose computers or general-purpose or special-purpose processors. In some examples, the software / program code may be transmitted from a remote source (e.g., a website, a server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, microwave, and the like. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, and the like, are within the definition of media. Combinations of the above examples are also within the scope of computer-readable media.

[0158] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items can begin with a phrase such as "at least one" or "one or more." For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A and B and C). Also, as used in this disclosure, the phrase "based on" preceding a list of conditions should not be interpreted as "based only on" the set of conditions, but rather as "based at least in part on" the set of conditions. For example, a result described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure.

[0159] As used herein, the terms "comprise", "include" or "contain" may be used interchangeably, have the same meaning, and should be construed as inclusive and open-ended. The terms "comprise", "include" or "contain" may be used before a list of elements to indicate that at least all of the listed elements in the list are present, but other elements not in the list may also be present. For example, if A contains B and C, then both {B,C} and {B,C,D} are within the scope of A.

[0160] The present disclosure describes exemplary configurations in connection with the accompanying drawings, which do not represent all examples that may be implemented or all configurations within the scope of the present disclosure. The term "exemplary" should not be interpreted as "preferred" or "advantageous compared to other examples," but rather as "an example, instance, or example." By reading this disclosure, including the description of the embodiments and drawings, those skilled in the art will understand that the technology disclosed herein may be implemented using alternative embodiments. Those skilled in the art will understand that the embodiments, or specific features of the embodiments described herein, may be combined to arrive at yet other embodiments for implementing the technology described in the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. A method of data transmission, comprising: a receiving step of receiving, by a user equipment (UE), from a base station (BS), a configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam; a determining step in which the UE determines configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; a configuring step of the UE configuring the second uplink beam based on the determined configuration parameters of the second beam; A method comprising: a transmitting step in which the UE transmits uplink data or control information to the BS using the second uplink beam.

2. The configuration parameters are: A transmit power control (TPC) signal; A phase information (PF) signal.

3. the determining step includes mapping the configuration parameters to integer values ​​based on one or more lookup tables. The method of claim 1.

4. The determining step identifies the configuration parameters that maximize a signal-to-noise ratio (SNR) of the second uplink beam in the gNB. The method of claim 1.

5. and performing an adaptive tracking scheme to track the configuration parameters of the second uplink beam. The method according to claim 4.

6. The adaptive tracking method is based on a gradient descent algorithm. The method according to claim 5.

7. The configuration message comprises: an identifier for identifying a configuration message; at least one transmit power control (TPC) field; and up to N phase information (PF) fields, where N is the number of user equipments (UEs) in a group in a cell identified by the base station (BS). The method of claim 1.

8. The method of claim 1 , comprising receiving the configuration message via downlink control information (DCI).

9. A method for determining a data transmission method, comprising the steps of: a first transmission step in which a user equipment (UE) transmits data or control information to a base station (BS) using a first transmission scheme during a first time period; a first calculation step of calculating a first transmission power for transmitting the data or the control information to the BS in the first transmission scheme by the UE; The user equipment (UE) transmits to the base station (BS) using a second transmission scheme during a second period. a second transmitting step of transmitting data or control information; a second calculation step of calculating a second transmission power for transmitting the data or the control information to the BS in the second transmission scheme by the UE; determining the calculated first power and the calculated second power according to the first transmission scheme or the second transmission scheme.

10. 1. A method of data transmission, comprising: A determining step in which the base station (BS) determines configuration parameters of an uplink beam; a transmitting step of the BS transmitting a configuration message to a user equipment (UE) including one or more signal quality indicators associated with the configuration parameters of the uplink beam; The method includes:

11. The configuration parameters are: Signal-to-noise ratio (SNR); and Phase information of the uplink beam; including one or more of The method of claim 10.

12. a first calculation step of calculating the signal quality indicator based on the configuration parameters. The method of claim 10.

13. The signal quality indicator is Transmit power control (TPC) commands; A phase feedback (PF) command; including one or more of The method of claim 10.

14. The configuration message comprises: an identifier for identifying the configuration message; At least one TPC field; and and up to N phase feedback (PF) fields, where N is the number of user equipments (UEs) in a group in a cell identified by the base station (BS). The method of claim 10.

15. The configuration message is transmitted via Downlink Control Information (DCI). The method of claim 10.

16. receiving a configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam; Transmitting uplink data or control information using the second uplink beam; A transceiver; a processor in communication with the transceiver, determining the configuration parameters associated with the second uplink beam based on the one or more signal quality indicators associated with the configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; Decide, configuring the second uplink beam based on the determined configuration parameters of the second beam. A processor; A user equipment (UE) including:

17. a processor for determining configuration parameters of an uplink beam; a transceiver in communication with the processor for transmitting a configuration message indicating one or more signal quality indicators associated with the configuration parameters of an uplink beam; A base station including:

18. When processed by a computer processor, a receiving step of receiving, by the UE, a configuration message including one or more signal quality indicators associated with configuration parameters of a first uplink beam; a determining step in which the UE determines configuration parameters associated with a second uplink beam based on the one or more signal quality indicators associated with configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; a configuration step of the UE configuring the second uplink beam based on the determined configuration parameters of the second uplink beam; a transmitting step of the UE transmitting uplink data or control information using the second uplink beam; A non-transitory computer readable medium having program code recorded thereon,

19. When processed by a computer processor, A configuration step in which a base station (BS) configures parameters of an uplink beam; a transmitting step of the BS transmitting a configuration message indicating one or more signal quality indicators associated with the configuration parameters of the uplink beam; A non-transitory computer readable medium having program code recorded thereon,

20. means for receiving a configuration message from a base station (BS) indicating one or more signal quality indicators associated with configuration parameters of a first uplink beam; receiving, from the UE, configuration parameters associated with a second uplink beam; means for determining based on the one or more signal quality indicators associated with configuration parameters of the first uplink beam and the configuration parameters of the first uplink beam; means for configuring the second uplink beam based on the determined configuration parameters of the second beam; and means for transmitting uplink data or control information to the BS using the second uplink beam.

Images