Group-Based Channel Status Information Reference Signal (CSI-RS) Transmission

Abstract

Systems, apparatus, methods, and computer-readable media are provided for channel state information (CSI) reference signal (RS) triggering for multiple user equipments (UEs) using a single downlink control information (DCI). In some embodiments, a new radio network temporary identifier (RNTI) may be used to indicate triggering of CSI-RS transmission for multiple UEs. Additionally or alternatively, a new DCI format may be used to support CSI-RS triggering for multiple UEs. The techniques described herein may provide reduced DCI overhead compared to conventional techniques. Other embodiments may be described and claimed.

Description

Technical Field

[0001] Various embodiments may generally relate to the field of wireless communication. For example, some embodiments may relate to techniques for group-based CSI-RS transmission.

Background Art

[0002] New Radio (NR) supports CSI reference signals (RS) for channel measurements for channel state information (CSI) reporting and beam management (BM) reporting. There are three types of CSI-RS transmissions supported in NR: periodic, semi-persistent, and aperiodic. Periodic CSI-RS is configured by radio resource control (RRC) signaling and transmitted periodically by a next generation NodeB (gNB). Semi-persistent CSI-RS is also configured by RRC, but its periodic transmission is activated by media access control (MAC) signaling. Aperiodic CSI-RS is triggered by downlink control information (DCI) and is limited to one or several CSI-RS transmission opportunities. Aperiodic CSI-RS is triggered by uplink (UL) DCI formats 0_1 and 0_2 in a user equipment (UE)-specific manner.

Brief Description of the Drawings

[0003] [Figure 1] Shows resource units for CSI-RS according to various embodiments. [Figure 2] Shows DCI formats for CSI-RS triggering for a group of UEs according to various embodiments. [Figure 3] This shows networks in various embodiments. [Figure 4] A schematic diagram of wireless networks in various embodiments is shown. [Figure 5] This block diagram shows a component, according to several exemplary embodiments, capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and performing one or more of the methods discussed herein. [Figure 6] This specification provides exemplary procedures for carrying out the various embodiments discussed herein. [Figure 7] Other exemplary procedures for carrying out the various embodiments discussed herein are shown below. [Modes for carrying out the invention]

[0004] The following detailed description refers to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, certain details, such as certain structures, architectures, interfaces, and techniques, are described for illustrative purposes only, not limitation, to provide a complete understanding of the various aspects of the various embodiments. However, it will be apparent to those skilled in the art who are interested in this disclosure that various aspects of the various embodiments may be implemented in other embodiments that deviate from these specific details. In certain cases, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary details. For the purposes of this document, the term "A or B" means (A), (B), or (A and B).

[0005] Various embodiments of this specification provide techniques for CSI-RS triggering for multiple UEs using a single DCI. In some embodiments, a novel radio network temporary identifier (RNTI) may be used to indicate the triggering of CSI-RS transmissions for multiple UEs. Alternatively, a novel DCI format supporting CSI-RS triggering for multiple UEs may be used. The techniques discussed herein may offer reduced DCI overhead compared to conventional techniques.

[0006] NR supports CSI-RS to support channel measurements for CSI reporting and beam management (BM) reporting. A CSI-RS resource contains one or more basic units of neighboring elements. For example, a CSI-RS resource may have the size (Y,Z) of neighboring elements, where Y is the number of subcarriers and Z is the number of orthogonal frequency division multiplexing (OFDM) symbols. Table 1 shows the supported combinations of basic units and antenna port (AP) multiplexing for CSI-RS resources. CDM indicates code division multiplexing, FD indicates frequency domain (e.g., FD-CDM), and TD indicates time domain.

[0007] [Table 1] Figure 1 shows the basic unit used to construct a CSI-RS resource. In some embodiments, resource units do not need to be adjacent in the frequency domain. A CSI-RS may occupy N=1, 2, or 4 OFDM symbols. If multiple symbols are used for CSI-RS transmission, the occupied RE is the same for all OFDM symbols used.

[0008] The current NR specification supports three types of CSI-RS transmission: periodic, semi-persistent, and aperiodic. Periodic CSI-RS is configured by RRC signaling and transmitted periodically by gNB. Semi-persistent CSI-RS is also configured by RRC, but its periodic transmission is activated by MAC signaling. Aperiodic CSI-RS is triggered by DCI and is limited to one or more CSI-RS transmission opportunities. Aperiodic CSI-RS is triggered by UL DCI formats 0_1 and 0_2 in a user equipment (UE) specific manner.

[0009] Therefore, the current specification only allows CSI-RS to be triggered in a UE-specific manner and does not support triggering CSI-RS transmissions for multiple UEs.

[0010] Various embodiments of this specification provide techniques for CSI-RS triggering for multiple UEs using a single DCI. In some embodiments, a novel radio network temporary identifier (RNTI) may be used to indicate the triggering of CSI-RS transmissions for multiple UEs. Alternatively, a novel DCI format supporting CSI-RS triggering for multiple UEs may be used. The techniques discussed herein may offer reduced DCI overhead compared to conventional techniques.

[0011] In some embodiments, a new DCI format may be introduced to trigger CSI-RS for multiple UEs. The DCI may provide the UE with information to indicate CSI-RS transmission, information about the component carrier (CC) or group of CCs on which the CSI-RS is transmitted, and / or other information associated with the CSI-RS, such as one or more CSI-RS resources. The new DCI format may support triggering different types of CSI-RS resources, such as CSI-RS having repeated "on" and "off" states (e.g., by the same Tx beam and / or different Tx beams), having trs-Info, or not having corresponding parameters (e.g., for CSI measurements). The new DCI format may also support optional triggering of sounding reference signal (SRS) transmissions associated with the corresponding CSI-RS resources.

[0012] For example, Figure 2 shows an exemplary DCI format 100 having multiple bit blocks 102a-c. Each individual block 102a-c may correspond to one or more UEs to trigger a CSI-RS and / or provide corresponding parameters to each of the one or more UEs. For example, blocks 102a-c may include trigger code points to indicate the corresponding set of parameters.

[0013] In one embodiment, the UE may receive configuration information from the gNB and assign the UE to one or more blocks 102a-c of the DCI format 100. Alternatively, the configuration information may indicate one or more CSI-RS parameters associated with a particular block 102a-c.

[0014] In another embodiment, a new RNTI may be introduced to support CSI-RS triggering for multiple UEs. The new RNTI may be configured for a set of multiple UEs using a higher layer (e.g., RRC signaling from gNB to UE). The RNTI may be used with the new DCI described herein and / or with existing DCI formats that enable aperiodic CSI-RS triggering, e.g., DCI formats 0_2, 0_1, or 0_0. The corresponding DCI with the new RNTI may be used with further restrictions on DCI formats without a UL physical uplink shared channel (PUSCH), e.g., UL-SCH indicator = 0. Thus, PUSCH transmissions do not have to be scheduled by the DCI.

[0015] [System and Implementation] Figures 3 to 5 show various systems, devices, and components that can implement embodiments of the disclosed embodiments.

[0016] Figure 3 shows network 300 in various embodiments. Network 300 may operate in a manner consistent with 3GPP® technical specifications for LTE or 5G / NR systems. However, exemplary embodiments are not limited thereto, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0017] Network 300 may include UE302, which may include any mobile or non-mobile computing device designed to communicate with RAN304 via an over-the-air connection. UE302 may also be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-car infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashboard mobile device, mobile data terminal, electronic engine management system, electronic / engine control unit, electronic / engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, IoT device, etc.

[0018] In some embodiments, the network 300 may include multiple UEs directly coupled to one another via a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0019] In some embodiments, UE702 may further communicate with AP306 via a wireless connection. AP306 may manage the WLAN connection, which may serve to offload some / all of the network traffic from RAN304. The connection between UE302 and AP306 may be compatible with any IEEE802.11 protocol, and AP306 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, UE302, RAN304, and AP306 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular WLAN aggregation may include UE302 configured by RAN604 to utilize both cellular radio resources and WLAN resources.

[0020] RAN304 may include one or more access nodes, for example, AN308. AN308 may terminate the air interface protocol for UE302 by providing an access layer protocol, including RRC, PDCP, RLC, MAC, and L1 protocols. Thus, AN308 may enable data / voice connectivity between CN320 and UE302. In some embodiments, AN308 may be implemented as one or more software entities running on a server computer, either in a separate device or as part of a virtual network, which may also be called CRAN or virtual baseband unit pool. AN308 may be referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN308 may also be a macrocell base station or low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0021] In embodiments where RAN304 includes a plurality of ANs, these may be coupled to each other via an X2 interface (when RAN304 is an LTE RAN) or an Xn interface (when RAN304 is a 5G RAN). The X2 / Xn interface may be separated into a control / user plane interface in some embodiments, enabling ANs to communicate information regarding handover, data / context transfer, mobility, load management, interference coordination, etc.

[0022] Each AN of RAN304 may manage one or more cells, cell groups, component carriers, etc. to provide an air interface for UE302 to access the network. UE302 may be simultaneously connected to a plurality of cells provided by the same AN or different ANs of RAN304. For example, UE302 and RAN304 may use carrier aggregation to enable UE302 to connect to a plurality of component carriers corresponding to Pcell or Scell respectively. In a dual connectivity scenario, the first AN may be a master node providing MCG, and the second AN may be a secondary node providing SCG. The first AN / second AN may be any combination of eNB, gNB, ng-eNB, etc.

[0023] RAN304 may provide an air interface on licensed spectrum or unlicensed spectrum. To operate within unlicensed spectrum, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with PCell / Scell. Before accessing the unlicensed spectrum, the node may perform media / carrier sensing operations based on, for example, the listen-before-talk (LBT) protocol.

[0024] In a V2X scenario, UE302 or AN308 may be or may act as an RSU, and the RSU may represent any transport infrastructure entity used for V2X communication. The RSU may be implemented in or within a suitable AN or stationary (or relatively stationary) UE. An RSU implemented in or by a UE may be called a “UE-type RSU,” an eNB may be called an “eNB-type RSU,” a gNB may be called a “gNB-type RSU,” and so on. In one example, the RSU is a computing device coupled with roadside radio frequency circuitry that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry that stores intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. The RSU may provide very low latency communication required for high-speed events such as collision avoidance and traffic warnings. Furthermore, or alternatively, the RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller for providing a traffic signaling controller or a wired connection (e.g., Ethernet®) to a backhaul network.

[0025] In some embodiments, RAN304 may be an LTE RAN310 having an eNB, eNB312, for example. The LTE RAN310 may provide an LTE air interface having the following characteristics: a 15kHz SCS, CP-OFDM waveform for DL ​​and SC-FDMA waveform for UL, turbo code for data and TBCC for control. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and cell search and initial acquisition for coherent demodulation / detection in the UE, as well as CRS for channel quality measurement and channel estimation. The LTE air interface may operate in a bandwidth of less than 6GHz.

[0026] In some embodiments, the RAN304 may be an NG-RAN314 having a gNB, e.g., gNB316, or an ng-eNB, e.g., ng-eNB318. The gNB316 may connect to a 5G-enabled UE using a 5G NR interface. The gNB316 may also connect to a 5G core via an NG interface, the NG interface may include an N2 interface or an N3 interface. The ng-eNB318 may also connect to a 5G core via an NG interface, or it may connect to a UE via an LTE air interface. The gNB316 and ng-eNB318 may connect to each other on an Xn interface.

[0027] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the NG-RAN314 nodes and the UPF348, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN314 nodes and the AMF344.

[0028] NG-RAN314 may provide a 5G-NR air interface having the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repeating, simplex and Reed-Muller code for control, and LDPC for data. The 5G-NR air interface may depend on CSI-RS and PDSCH / PDCCH DMRS, similar to an LTE air interface. The 5G-NR air interface may not use CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for PDSCH phase tracking, and a tracking reference signal for time tracking. The 5G-NR air interface may operate in the FR1 band, which includes the band below 6 GHz, or in the FR2 band, which includes the band from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0029] In some embodiments, a 5G-NR air interface may utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, a UE302 can be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is instructed to the UE302, the SCS of the transmission is also changed accordingly. Another use case example of BWPs relates to power saving. In particular, multiple BWPs can be configured for the UE302 with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. BWPs with fewer PRBs can be used for data transmission under low traffic loads while enabling power savings in the UE302 and, in some cases, the gNB316. BWPs with more PRBs can be used for scenarios with higher traffic loads.

[0030] RAN304 is communicatively coupled to CN320, which includes network elements that provide various functions to support data and telecommunications services to customers / subscribers (e.g., users of UE302). The components of CN320 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functions provided by the network elements of CN320 onto physical computing / storage resources in servers, switches, etc. Logical instantiations of CN320 may be called network slices, and some logical instantiations of CN320 may be called network subslices.

[0031] In some embodiments, CN320 may also be LTE CN322, which may also be called EPC. LTE CN322 may include MME324, SGW326, SGSN328, HSS330, PGW332, and PCRF334 coupled to each other on an interface (or "reference point"), as shown in the figure. The functions of the elements of LTE CN322 can be briefly described below.

[0032] The MME324 may implement mobility management features that track the current location of the UE302 to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0033] The SGW326 may terminate the S1 interface to the RAN and route data packets between the RAN and the LTE CN322. The SGW326 may also be a local mobility anchor point for handover between RAN nodes and may provide an anchor for 3GPP mobility. Other roles may include lawful intercept, billing, and any policy enforcement.

[0034] The SGSN328 may track the location of the UE302 and perform security functions and access control. Furthermore, the SGSN328 may perform EPC node-to-node signaling for mobility between different RAT networks, PDN and S-GW selection specified by the MME324, MME selection for handover, etc. An S3 reference point between the MME324 and the SGSN328 may enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0035] The HSS330 may include a database for network users, containing subscription-related information to support the handling of communication sessions by network entities. The HSS330 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between the HSS330 and the MME324 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to the LTE CN320.

[0036] PGW332 may terminate an SGI interface to a data network (DN) 336, which may include an application / content server 338. PGW332 may route data packets between the LTE CN 322 and the data network 336. PGW332 may be coupled with SGW326 via an S5 reference point to facilitate user plane tunneling and tunnel management. PGW332 may further include nodes (e.g., PCEFs) for policy enforcement and billing data collection. Furthermore, the SGi reference point between PGW332 and the data network 336 may be, for example, an operator-external public, private PDN, or an operator-internal packet data network for provisioning IMS services. PGW332 may be coupled with PCRF334 via a Gx reference point.

[0037] PCRF334 is the policy and billing control element of LTE CN322. PCRF334 may be communicatively coupled to the application / content server 338 to determine appropriate QoS and billing parameters for the service flow. PCRF332 may provision the relevant rules to the PCEF (via the Gx reference point) using appropriate TFT and QCI.

[0038] In some embodiments, CN320 may be 5GC340. 5GC340 may include AUSF342, AMF344, SMF346, UPF348, NSSF350, NEF352, NRF354, PCF356, UDM358, and AF360 coupled to each other on an interface (or "reference point"), as shown in the figure. The functions of the elements of 5GC340 can be briefly described below.

[0039] The AUSF342 may store data for authentication of the UE302 and handle authentication-related functions. The AUSF342 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC340 on the reference point, as shown in the figure, the AUSF342 may present a Nausf service-based interface.

[0040] The AMF344 may enable other functions of the 5GC340 to communicate with the UE302 and RAN304 and subscribe to notifications regarding mobility events related to the UE302. The AMF344 may also perform registration management (e.g., to register the UE302), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF344 may provide transport for SM messages between the UE302 and the SMF346 and may act as a transparent proxy for routing SM messages. The AMF344 may also provide transport for SMS messages between the UE302 and the SMSF. The AMF344 may interact with the AUSF342 and UE302 to perform various security anchor and context management functions. Furthermore, the AMF344 may be the termination point of a RAN CP interface that includes or may be an N2 reference point between the RAN304 and the AMF344, and the AMF344 may also be the termination point of NAS(N1) signaling and may perform NAS encryption and integrity protection. The AMF344 may also support NAS signaling with the UE302 over the N3 IWF interface.

[0041] SMF346 may also perform the following roles: SM (e.g., session establishment between UPF348 and AN308, tunnel management), UE IP address allocation and management (including permission for optional selection), selection and control of UP functions, configuration of traffic steering in UPF348 for routing traffic to appropriate destinations, termination of interfaces toward policy control functions, policy enforcement, control of some aspects of billing and QoS, lawful interception (for SM events and interfaces to LI systems), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information transmitted to AN308 via AMF344 on N2, and determination of the session's SSC mode. SM may also indicate the management of a PDU session, and a PDU session or "session" may indicate a PDU connectivity service that provides or enables the exchange of PDUs between UE302 and the data network 336.

[0042] UPF348 may function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 336, and a branching point to support multi-homed PDU sessions. UPF348 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggers. UPF348 may include an uplink classifier to support routing traffic flows to the data network.

[0043] The NSSF350 may select a set of network slice instances to serve the UE302. The NSSF350 may also determine the mapping to the authorized NSSAI and the joined S-NSSAI, if necessary. The NSSF350 may also determine the set of AMFs to be used to serve the UE302, or, based on the appropriate configuration, may determine a list of candidate AMFs by querying the NRF354. The selection of a set of network slice instances for the UE302 may be triggered by the AMF344 to which the UE302 is registered by interacting with the NSSF350, which may result in a change of AMF. The NSSF350 may interact with the AMF344 via the N22 reference point, or communicate with another NSSF in the visited network via the N31 reference point (not shown). Furthermore, the NSSF350 may present an Nnssf service-based interface.

[0044] NEF352 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, AFs (e.g., AF360), edge computing, or fog computing systems. In such embodiments, NEF352 may authenticate, authorize, or throttle AFs. NEF352 may also translate information exchanged with AF360 and information exchanged with internal network functions. For example, NEF352 may translate between AF service identifiers and internal 5GC information. NEF352 may also receive information from other NFs based on the exposed capabilities of other NFs. This information may be stored in NEF352 as structured data, or in a data storage NF using a standardized interface. The stored information can then be re-exposed by NEF352 to other NFs and AFs, or used for other purposes such as analysis. Furthermore, NEF352 may present an Nnef service-based interface.

[0045] The NRF354 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to the NF instances. The NRF354 also maintains information about available NF instances and the services they support. As used herein, terms such as “instantiate” and “instantiate” may refer to the creation of an instance, and “instance” may refer to the specific occurrence of an object that may occur, for example, during the execution of program code. Furthermore, the NRF354 may present an Nnrf service-based interface.

[0046] The PCF356 may provide policy rules to control plane functions to enforce policy rules, and may also support a unified policy framework for managing network behavior. The PCF356 may also implement a front-end to access subscription information related to policy decisions in the UDR of the UDM358. In addition to communicating with functions on a reference point as shown in the diagram, the PCF356 presents an Npcf service-based interface.

[0047] UDM358 may process join-related information to support the handling of communication sessions by network entities and may store join data for UE302. For example, join data may be communicated via an N8 reference point between UDM358 and AMF344. UDM358 may include two parts: an application frontend and a UDR. The UDR may store join data and policy data for UDM358 and PCF356, and / or structured data for NEF352, including public and application data (including a PFD for application discovery and application request information for multiple UE302s). A Nudr service-based interface may be presented by UDR321, allowing UDM358, PCF356 and NEF352 to access specific sets of stored data, read notifications of relevant data changes in the UDR, update (e.g., add, modify), delete, and join. The UDM may include a UDM-FE, which is responsible for credential processing, location management, join management, etc. Several different frontends may serve the same user in different transactions. The UDM-FE accesses the enrollment information stored in the UDR and performs authentication certificate processing, user identification processing, access permission, enrollment / mobility management, and enrollment management. In addition to communicating with other NFs on a reference point as shown in the diagram, the UDM358 may present a Nudm service-based interface.

[0048] AF360 may provide application influence on traffic routing, provide access to NEF, and interact with a policy framework for policy control.

[0049] In some embodiments, 5GC340 may enable edge computing by selecting an operator / third-party service that is geographically close to where the UE302 is attached to the network. This may reduce latency and load on the network. To provide an implementation of edge computing, 5GC340 may select a UPF348 that is close to the UE302 and perform traffic steering from the UPF348 to the data network 336 via the N6 interface. This may be based on UE join data, UE location, and information provided by AF360. Thus, AF360 may influence UPF (re)selection and traffic routing. When AF360 is considered a trusted entity based on the operator's placement, the network operator may allow AF360 to interact directly with the relevant NF. Furthermore, AF360 may present a NAF service-based interface.

[0050] The data network 336 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, including, for example, an application / content server 338.

[0051] Figure 4 schematically shows the wireless network 400 in various embodiments. The wireless network 400 may include a UE402 that wirelessly communicates with AN404. The UE402 and AN404 are similar to components of similar names described elsewhere in this specification and may be substantially interchangeable.

[0052] UE402 may be communicatively coupled to AN404 via connection 406. Connection 406 is shown as an air interface to enable communication coupling and can be compatible with cellular communication protocols such as mmWave or LTE or 5G NR protocols operating at frequencies below 6 GHz.

[0053] UE402 may include a host platform 408 coupled with a modem platform 410. The host platform 408 may include an application processing circuit 412, which may be coupled with a protocol processing circuit 414 of the modem platform 410. The application processing circuit 412 may run various applications for UE402 that source / sink application data. The application processing circuit 412 may further implement one or more layer operations for sending / receiving application data to a data network. These layer operations may include transport (e.g., UDP) and internet (e.g., IP) operations.

[0054] The protocol processing circuit 414 may implement one or more layer operations to facilitate the transmission or reception of data over connection 406. The layer operations implemented by the protocol processing circuit 414 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0055] The modem platform 410 may further include a digital baseband circuit 416 that can implement one or more layer operations that lie "below" the layer operations performed by the protocol processing circuit 414 in the network protocol stack. These operations may include PHY operations such as, for example, HARQ-ACK functionality, scrambling / descrambling, coding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bitmetric determination, multi-antenna port precoding / decoding (which may include one or more of space-time coding, space-frequency coding, or spatial coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and one or more other related functions.

[0056] The modem platform 410 may further include a transmitting circuit 418, a receiving circuit 420, an RF circuit 422, and an RF front end (RFFE) 424, which may include or be connected to one or more antenna panels 426. In short, the transmitting circuit 418 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receiving circuit 420 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 422 may include a low-noise amplifier, a power amplifier, a power tracking component, etc.; and the RFFE 424 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phase array antenna component), etc. The selection and arrangement of the components of the transmitting circuit 418, receiving circuit 420, RF circuit 422, RFFE 424, and antenna panel 426 (collectively referred to as the "transmitting / receiving components") may be specific to the details of the implementation, such as whether the communication is TDM or FDM, or whether the frequency is mmWave or below 6 GHz. In some embodiments, the transmitting / receiving components may be arranged in multiple parallel transmitting / receiving chains, or they may be arranged on the same or different chips / modules, etc.

[0057] In some embodiments, the protocol processing circuit 414 may include one or more instances of a control circuit (not shown) for providing control functions to the transmit / receive components. UE reception may be established by and through the antenna panel 426, RFFE 424, RF circuit 422, receiving circuit 420, digital baseband circuit 416, and protocol processing circuit 414. In some embodiments, the antenna panel 426 may receive transmissions from AN404 by received beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 426.

[0058] UE transmission may be established by and through the protocol processing circuit 414, the digital baseband circuit 416, the transmit circuit 418, the RF circuit 422, the RFFE 424, and the antenna panel 426. In some embodiments, the transmit component of UE 404 may apply a spatial filter to the transmitted data to form a transmit beam radiated by the antenna elements of the antenna panel 426. Similar to UE402, AN404 may include a host platform 428 coupled to a modem platform 430. The host platform 428 may include an application processing circuit 432 coupled to the protocol processing circuit 434 of the modem platform 430. The modem platform may further include a digital baseband circuit 436, a transmit circuit 438, a receive circuit 440, an RF circuit 442, an RFFE circuit 444, and an antenna panel 446. The components of AN404 may be similar to the components of the same name in UE402 and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN408 may perform various logical functions, including RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0059] Figure 5 is a block diagram showing components, according to several exemplary embodiments, that can read instructions from a machine-readable or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and perform one or more of the methods discussed herein. Specifically, Figure 5 shows a schematic diagram of hardware resources 500 including one or more processors (or processor cores) 510, one or more memory / storage devices 520, and one or more communication resources 530, each of which may be communicatively coupled via a bus 540 or other interface circuitry. In embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 502 may be run to provide an execution environment for one or more network slices / subslice for utilizing the hardware resources 500.

[0060] The processor 510 may include, for example, processors 512 and 514. The processor 510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), other processors (including those discussed herein), or any appropriate combination thereof.

[0061] The memory / storage device 520 may include main memory, disk storage, or any appropriate combination thereof. The memory / storage device 520 may include, but is not limited to, any type of volatile, non-volatile, and semi-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0062] The communication resource 530 may include interconnects or network interface controllers, components, or other suitable devices for communicating with one or more peripheral devices 504 or one or more databases 506 or other network elements via the network 508. For example, the communication resource 530 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[0063] Instruction 550 may include other executable code causing at least one of the following to perform one or more of the methods discussed herein: software, programs, applications, applets, apps, or processor 510. Instruction 550 may reside entirely or partially in at least one of the following: processor 510 (e.g., the processor's cache memory), memory / storage device 520, or any suitable combination thereof. Furthermore, any part of instruction 550 may be transferred to hardware resource 500 from either peripheral device 504 or database 506. Thus, the memory of processor 510, memory / storage device 520, peripheral device 504, and database 506 are examples of computer-readable and machine-readable media.

[0064] [Example procedure] In some embodiments, electronic devices, networks, systems, chips, or components, or parts thereof, or implementations thereof, shown in Figures 3 to 5 or some other drawings herein, may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein. For example, Figure 6 shows process 600 according to some embodiments. Process 600 may be performed by a UE or part thereof.

[0065] In 602, process 600 may include receiving configuration information from gNB for DCI to trigger aperiodic CSI-RS for multiple UEs. In 604, process 600 may further include receiving DCI. In 606, process 600 may further include receiving aperiodic CSI-RS based on DCI and configuration information.

[0066] In some embodiments, the DCI may include a block of bits for triggering each aperiodic CSI-RS for each group of one or more UEs. The configuration information may indicate one or more of the block of bits to which the UEs are assigned. Alternatively, the DCI may include an RNTI for triggering aperiodic CSI-RS for multiple UEs. The configuration information may constitute the RNTI.

[0067] Figure 7 shows another process 700 according to various embodiments, which may include, in 702, encoding a DCI to trigger one or more aperiodic CSI-RS for multiple UEs for transmission to multiple UEs. In 704, the process 700 may further include encoding one or more aperiodic CSI-RS for transmission based on the DCI.

[0068] In some embodiments, the gNB may transmit configuration information about the DCI to multiple UEs. In some embodiments, the DCI may include a block of bits for triggering each aperiodic CSI-RS for each group of one or more UEs. The configuration information may indicate one or more of the blocks of bits to which the UEs are assigned. Alternatively, the DCI may include an RNTI for triggering aperiodic CSI-RS for multiple UEs. The configuration information may constitute the RNTI.

[0069] In one or more embodiments, at least one of the components described in one or more of the preceding drawings may be configured to perform one or more operations, techniques, processes and / or methods as described in the following exemplary sections. For example, the baseband circuit described above in relation to one or more of the preceding drawings may be configured to operate according to one or more of the examples described below. In another example, a circuit associated with a UE, base station, network element, etc., described above in relation to one or more of the preceding drawings may be configured to operate according to one or more of the examples described below.

[0070] [example] Example 1 may include one or more non-transitory computer-readable media (NTCRM) that, when executed by one or more processors, cause user equipment (UEs) to receive configuration information for downlink control information (DCI) to trigger aperiodic channel state information (CSI) reference signals (RS) for multiple UEs from next-generation node B (gNB), receive the DCI, and receive aperiodic CSI-RS based on the DCI and configuration information.

[0071] Example 2 may include one or more NTCRMs of Example 1, where the aperiodic CSI-RS is the first aperiodic CSI-RS, the DCI includes a block of multiple bits to trigger each aperiodic CSI-RS, including the first aperiodic CSI-RS, and the configuration information indicates the first block of the block of multiple bits to which the UE is assigned.

[0072] Example 3 may include one or more NTCRMs from Example 2, where the first block shows the triggered CSI-RS resources associated with the first non-periodic CSI-RS.

[0073] Example 4 may include one or more NTCRMs from Example 3, where the triggered CSI-RS resource is a set of CSI-RS resources for CSI-RS iteration or tracking reference signal information (trs-info).

[0074] Example 5 may include one or more NTCRMs from Example 2, where the first block represents a component carrier on which the first non-periodic CSI-RS is transmitted.

[0075] Example 6 may include one or more NTCRMs of Example 2, wherein the first block further includes information for a sounding reference signal (SRS) associated with a first CSI-RS, and the instruction, when executed, causes the UE to further encode the SRS for transmission based on the information.

[0076] Example 7 may include one or more NTCRMs from Examples 1-6, where the configuration information constitutes a Radio Network Temporary Identifier (RNTI) used to trigger aperiodic CSI-RS for multiple UEs.

[0077] Example 8 may include one or more NTCRMs from Example 7, where the DCI has DCI format 0_1 ​​or DCI format 0_2.

[0078] Example 9 may include one or more NTCRMs from Example 7, where DCI includes an Uplink (UL) Shared Channel (SCH) indicator indicating that physical uplink shared channel (PUSCH) transmissions are not scheduled by DCI.

[0079] Example 10 may include one or more non-temporary computer-readable media (NTCRM) that store instructions, when executed by one or more processors, to cause a next-generation node B (gNB) to encode downlink control information (DCI) to trigger one or more aperiodic channel state information (CSI) reference signals (RS) for multiple UEs for transmission to multiple UEs, and to encode one or more aperiodic CSI-RS for transmission based on the DCI.

[0080] Example 11 may include one or more NTCRMs from Example 10, where one or more aperiodic CSI-RSs are multiple aperiodic CSI-RSs, and the DCI includes a block of multiple bits to trigger each aperiodic CSI-RS.

[0081] Example 12 may include one or more NTCRMs from Example 11, and when the instruction is executed, it causes the gNB to further encode configuration information for assigning multiple UEs to each block of a block of multiple bits for transmission to multiple UEs.

[0082] Example 13 may include one or more NTCRMs from Example 11, where each individual block of the multi-bit block represents at least one of the CSI-RS resources or component carriers associated with each aperiodic CSI-RS.

[0083] Example 14 may include one or more NTCRMs from Example 13, where each block includes a CSI-RS resource, and the CSI-RS resource is a set of CSI-RS resources for CSI-RS iteration or tracking reference signal information (trs-info).

[0084] Example 15 may include one or more NTCRMs from Example 11, where one or more blocks of bits contain information for a sounding reference signal (SRS) associated with the corresponding nonperiodic CSI-RS.

[0085] Example 16 may include one or more NTCRMs from any of Examples 10–15, where the DCI includes a Radio Network Temporary Identifier (RNTI) used to trigger aperiodic CSI-RS for multiple UEs.

[0086] Example 17 may include one or more NTCRMs from Example 16, where the DCI has DCI format 0_1 ​​or DCI format 0_2.

[0087] Example 18 may include one or more NTCRMs from Example 16, where the DCI includes an Uplink (UL) Shared Channel (SCH) indicator indicating that a physical uplink shared channel (PUSCH) transmission is not scheduled by the DCI.

[0088] Example 19 may include a device implemented in a user device (UE), which is configuration information for downlink control information (DCI) containing a plurality of bit blocks for triggering each aperiodic channel state information (CSI) reference signal (RS) for each group of one or more UEs from a next-generation node B (gNB), and includes a processor circuit for receiving configuration information indicating a first block of the plurality of bit blocks to which a UE has been assigned, receiving a DCI for triggering a first aperiodic CSI-RS, and receiving a first aperiodic CSI-RS based on the first block of the DCI. The processor circuit may further include memory for storing identifiers of the first block.

[0089] Example 20 may include the apparatus of Example 19, wherein the first block represents at least one CSI-RS resource or component carrier associated with the first non-periodic CSI-RS.

[0090] Example 21 may include the apparatus of Example 19, wherein the first block further includes information for a sounding reference signal (SRS) associated with a first CSI-RS, and the processor circuit further encodes the SRS for transmission based on the information.

[0091] Example 22 may include any of the devices in Examples 19-21, wherein the configuration information constitutes a Radio Network Temporary Identifier (RNTI) used to trigger a first non-periodic CSI-RS for multiple UEs among multiple UEs.

[0092] Example 23 may include an apparatus that includes means for performing one or more elements of any of the methods described or related to Examples 1 to 22, or any other method or process described herein.

[0093] Example 24 may include one or more non-temporary computer-readable media containing instructions that cause an electronic device to perform one or more elements of any of the methods or processes described herein, or any other methods or processes described herein, when one or more processors of the electronic device execute instructions.

[0094] Example 25 may include an apparatus that includes logic, modules, or circuits for performing one or more elements of any of the methods described in or related to Examples 1 to 22, or any other method or process described herein.

[0095] Example 26 may include methods, techniques, or processes described or related to any or part of Examples 1-22.

[0096] Example 27 may include a device comprising one or more processors and one or more computer-readable media containing instructions that, when executed by one or more processors, cause one or more processors to execute methods, techniques, or processes described in or related to any or part of Examples 1 to 22.

[0097] Example 28 may include signals described or related to any of Examples 1 to 22, or parts or portions thereof.

[0098] Example 29 may include datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in or related to any of Examples 1-22, or parts thereof, or described in this disclosure.

[0099] Example 30 may include signals encoded with data described in or related to any of Examples 1-22, or parts thereof, or described in this disclosure.

[0100] Example 31 may include signals encoded in any or part of Examples 1-22, or in any part thereof, or in any part thereof, such as datagrams, packets, frames, segments, protocol data units (PDUs), or messages described in this disclosure.

[0101] Example 32 may include electromagnetic signals that carry computer-readable instructions, and the execution of computer-readable instructions by one or more processors causes one or more processors to execute methods, techniques, or processes described in or related to any or part of Examples 1 to 22.

[0102] Example 33 may include a computer program containing instructions, and the execution of the program by the processing element causes the processing element to execute any or part of the methods, techniques, or processes described or related to those described in Examples 1 to 22.

[0103] Example 34 may include signals in a wireless network as illustrated and described herein.

[0104] Example 35 may include a method of communication in a wireless network as illustrated and described herein.

[0105] Example 36 may include a system for providing wireless communication as illustrated and described herein.

[0106] Example 37 may include a device for providing wireless communication as illustrated and described herein.

[0107] Any of the above examples may be combined with any other example (or combination of examples) unless expressly specified otherwise. The above descriptions of one or more implementations are illustrative and explanatory, but are not intended to be exhaustive or to limit the scope of embodiments to the exact form disclosed. Modifications and changes are possible in light of the above teachings or can be obtained from the implementation of various embodiments.

[0108] [term] Unless otherwise used herein, terms, definitions, and abbreviations may be consistent with those defined in 3GPP TR21.905 v16.0.0 (2019-06). For the purposes of this document, the following abbreviations may apply to the examples and embodiments discussed herein.

[0109] For the purposes of this document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

[0110] As used herein, the term “circuit” refers to, is part of, or includes hardware components configured to provide the functions described, such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) and / or memory (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable SoCs), digital signal processors (DSPs), etc. In some embodiments, the circuit may run one or more software or firmware programs to provide at least some of the functions described. The term “circuit” may also refer to a combination of one or more hardware elements (or combinations of circuits used in an electrical or electronic system) and program code used to perform the functions of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0111] As used herein, the term “processor circuit” refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations, or of recording, storing, and / or transferring digital data. A processing circuit may include one or more processing cores for executing instructions and one or more memory structures for storing program and data information. The term “processor circuit” may also refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions such as program code, software modules, and / or functional processes. A processing circuit may also include more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. One or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. The terms “application circuit” and / or “baseband circuit” may be considered synonymous with “processor circuit” and may also be referred to as “processor circuit.”

[0112] As used herein, the term "interface circuit" refers to, a part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" may also refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0113] As used herein, the terms “User Equipment” or “UE” may refer to a device having wireless communication capabilities, or may describe a remote user of network resources in a communication network. The terms “User Equipment” or “UE” may be considered synonymous with, or referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the terms “User Equipment” or “UE” may include any type of wireless / wired device, or any computing device including a wireless communication interface.

[0114] As used herein, the term “network element” refers to physical or virtualized devices and / or infrastructure used to provide wired or wireless network services. The term “network element” may be considered synonymous with networked computers, networking hardware, network devices, network nodes, routers, switches, hubs, bridges, wireless network controllers, RAN devices, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc.

[0115] As used herein, the term “computer system” refers to any type of interconnected electronic devices, computer devices, or components thereof. Furthermore, the terms “computer system” and / or “system” may refer to various components of a computer that are interconnected in a communicative manner. Additionally, the terms “computer system” and / or “system” may refer to multiple computer devices and / or multiple computing systems that are interconnected in a communicative manner and configured to share computing and / or network resources.

[0116] As used herein, terms such as “appliance” and “computer appliance” refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide a particular computing resource. A “virtual appliance” is a virtual machine image implemented by a hypervisor-based device that virtualizes or emulates a computer appliance or otherwise dedicates itself to providing a particular computing resource.

[0117] As used herein, the term “resource” refers to physical or virtual devices, physical or virtual components within a computing environment, and / or physical or virtual components within a particular device, such as computer devices, mechanical devices, memory space, processor / CPU time, processor / CPU usage, processor and accelerator load, hardware time or usage, power, I / O operations, ports or network sockets, channel / link allocation, throughput, memory usage, storage, networks, databases and applications, workload units, etc. “Hardware resources” may refer to compute, storage, and / or network resources provided by physical hardware elements. “Virtualization resources” may refer to compute, storage, and / or network resources provided to applications, devices, systems, etc., by a virtualization infrastructure. The terms “network resources” or “communication resources” may refer to resources accessible by computer devices / systems via a communication network. The term “system resources” may refer to any kind of shared entity providing services, and may include compute and / or network resources. System resources may also be considered as a set of consistent functions, network data objects, or services accessible through a server, such system resources residing on a single host or multiple hosts and clearly identifiable.

[0118] As used herein, the term "channel" refers to a tangible or intangible transmission medium used to communicate data or data streams. The term "channel" may also be synonymous with and / or equivalent to other similar terms that indicate a path or medium through which data is communicated, such as "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or other similar terms. Furthermore, as used herein, the term "link" refers to a connection between two devices via a RAT for the purpose of sending and receiving information.

[0119] As used herein, terms such as "instantiate" and "instantiate" refer to the creation of an instance. An "instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0120] The terms “joined” and “communicatively joined” are used herein together with their derivatives. The term “joined” may mean that two or more elements are in direct physical or electrical contact with each other, that two or more elements are indirectly in contact with each other but still cooperate or interact with each other, and / or that one or more other elements are joined or connected between elements said to be joined together. The term “directly joined” may mean that two or more elements are in direct contact with each other. The term “communicatively joined” may mean that two or more elements are in contact with each other by means of communication, including through wired or other interconnection connections, through wireless communication channels or links, etc.

[0121] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains content.

[0122] The term "SMTC" refers to an SSB-based measurement timing configuration, which is comprised of an SSB-MeasurementTimingConfiguration.

[0123] The term "SSB" refers to the SS / PBCH block.

[0124] The term "primary cell" refers to the MCG cell operating at the primary frequency from which the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

[0125] The term "primary SCG cell" refers to the SCG cell that the UE performs random access to when executing a reconfiguration procedure that involves synchronization for DC operation.

[0126] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured in CA.

[0127] The term "secondary cell group" refers to a subset of serving cells in a UE composed of DCs, including PSCells and zero or more secondary cells.

[0128] The term "serving cell" refers to the primary cell for an RRC_CONNECTED UE that is not configured with CA / DC, and there is only one serving cell that constitutes the primary cell.

[0129] The term "serving cell" refers to a set of cells that includes special cells and all secondary cells for UEs of RRC_CONNECTED configured in CA / .

[0130] The term "special cell" refers to the PC cell of an MCG or the PSCell of an SCG in the case of DC operation; otherwise, the term "special cell" refers to a P cell.

Claims

1. When executed by one or more processors, the user device (UE) will receive The next-generation node B (gNB) receives configuration information for downlink control information (DCI) to trigger aperiodic channel state information (CSI) reference signals (RS) for multiple UEs. The DCI is received, Includes an instruction to receive the non-periodic CSI-RS based on the DCI and the configuration information, The DCI is a program having DCI format 0_1 ​​or DCI format 0_2.

2. The program according to claim 1, wherein the aperiodic CSI-RS is a first aperiodic CSI-RS, the DCI includes a plurality of bit blocks for triggering each aperiodic CSI-RS including the first aperiodic CSI-RS, and the configuration information indicates a first block among the plurality of bit blocks to which the UE is assigned.

3. The program according to claim 2, wherein the first block indicates a triggered CSI-RS resource associated with the first non-periodic CSI-RS.

4. The program according to claim 3, wherein the triggered CSI-RS resource is a set of CSI-RS resources for CSI-RS iteration or tracking reference signal information (trs-info).

5. The program according to claim 2, wherein the first block indicates a component carrier on which the first non-periodic CSI-RS is transmitted.

6. The program according to claim 2, wherein the first block further includes information for a sounding reference signal (SRS) associated with the first non-periodic CSI-RS, and the instruction, when executed, causes the UE to further encode the SRS for transmission based on the information.

7. The program according to claim 1, wherein the configuration information constitutes a radio network temporary identifier (RNTI) used to trigger the aperiodic CSI-RS for the plurality of UEs.

8. When executed by one or more processors, it will be transferred to the next-generation node B (gNB). For transmission to multiple user devices (UEs), downlink control information (DCI) is encoded to trigger one or more non-periodic channel status information (CSI) reference signals (RS) for the multiple UEs. Includes instructions for encoding one or more aperiodic CSI-RS for transmission based on the DCI, The DCI is a program having DCI format 0_1 ​​or DCI format 0_2.

9. The program according to claim 8, wherein the one or more aperiodic CSI-RSs are a plurality of aperiodic CSI-RSs, and the DCI includes a plurality of bit blocks for triggering each aperiodic CSI-RS.

10. The program according to claim 9, wherein, when the instruction is executed, the gNB further encodes configuration information for assigning the plurality of UEs to each block of the plurality of bit blocks for transmission to the plurality of UEs.

11. The program according to claim 9, wherein each individual block of the plurality of bits represents at least one of the CSI-RS resources or component carriers associated with each aperiodic CSI-RS.

12. The program according to claim 11, wherein each of the blocks includes the CSI-RS resources, and the CSI-RS resources are a set of CSI-RS resources for CSI-RS iteration or tracking reference signal information (trs-info).

13. The program according to claim 9, wherein one or more of the blocks of bits include information for a sounding reference signal (SRS) associated with a corresponding non-periodic CSI-RS.

14. The program according to claim 8, wherein the DCI includes a radio network temporary identifier (RNTI) used to trigger the aperiodic CSI-RS for the plurality of UEs.

15. A device implemented in a user equipment (UE), Configuration information for downlink control information (DCI) including a block of multiple bits for triggering each aperiodic channel state information (CSI) reference signal (RS) for each group of one or more UEs, and configuration information indicating a first block to which the UE is assigned is received from the next-generation node B (gNB). The DCI is received to trigger the first non-periodic CSI-RS, A processor circuit for receiving the first non-periodic CSI-RS based on the first block of the DCI, A memory for storing the identifier of the first block and Includes, The DCI is a device having DCI format 0_1 ​​or DCI format 0_2.

16. The apparatus according to claim 15, wherein the first block represents at least one CSI-RS resource or component carrier associated with the first non-periodic CSI-RS.

17. The apparatus according to claim 15, wherein the first block further includes information for a sounding reference signal (SRS) associated with the first non-periodic CSI-RS, and the processor circuit further encodes the SRS for transmission based on the information.

18. The apparatus according to any one of claims 15 to 17, wherein the configuration information constitutes a radio network temporary identifier (RNTI) used to trigger the first non-periodic CSI-RS for a plurality of the plurality of UEs.

19. One or more non-temporary computer-readable storage media storing the program described in any one of claims 1 to 7.

20. One or more non-temporary computer-readable storage media storing the program described in any one of claims 8 to 14.

Images