Systems and methods for indicating control information to network nodes
Patent Information
- Authority / Receiving Office
- EP · EP
- Patent Type
- Applications
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2023-08-02
- Publication Date
- 2026-06-03
AI Technical Summary
Existing systems face challenges in efficiently indicating control information to multiple network nodes in wireless communication networks, particularly in scenarios where traditional downlink control information (DCI) signaling is not adequately flexible to support group communications.
The proposed solution involves a new format of DCI signaling that allows for the simultaneous indication of control information to a group of network nodes. This is achieved by introducing new radio network temporary identifiers (RNTIs) and modifying the field format of DCI to include beam index fields, time indication fields, and other control parameters that can be shared or specifically allocated to each node.
The new DCI signaling format enhances the flexibility and efficiency of control information transmission, allowing for concurrent management of multiple network nodes with reduced interference and improved network coverage.
Smart Images

Figure CN2023110833_06022025_PF_FP_ABST
Abstract
Description
SYSTEMS AND METHODS FOR INDICATING CONTROL INFORMATION TO NETWORK NODESTECHNICAL FIELD
[0001] The disclosure relates generally to wireless communications, including but not limited to systems and methods for indicating control information to network nodes.BACKGROUND
[0002] Coverage is a fundamental aspect of cellular network deployments. Mobile operators rely on different types of network nodes to offer blanket coverage in their deployments. As a result, new types of network nodes have been considered to increase the flexibility of mobile operators for their network deployments. For example, certain systems or architecture introduce integrated access and backhaul (IAB) , which may be enhanced in certain other systems, as a new type of network node not requiring a wired backhaul. Another type of network node is the RF repeater which simply amplify-and-forward any signal that they receive. RF repeaters have seen a wide range of deployments in 2G, 3G and 4G to supplement the coverage provided by regular full-stack cells.SUMMARY
[0003] The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
[0004] At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. A wireless communication node (e.g., base station (BS) ) can send / provide / transmit a first message in a downlink control information (DCI) to a plurality of network nodes (e.g., smart nodes (SNs) ) , with the first message indicating control information respectively configured / provided for the plurality of network nodes.
[0005] In some implementations, the configured / provided one or more respective ones of beam index fields and configured / provided one or more respective ones of time indication fields in the DCI are configured for each of the network nodes.
[0006] In certain implementations, the configured / provided one or more respective ones of beam index fields for each of the network nodes can be consecutive or non-consecutive. The configured / provided one or more respective ones of time indication fields for each of the network nodes can be consecutive or non-consecutive.
[0007] In some implementations, the time indication fields in the DCI can be shared and used for the plurality of network nodes.
[0008] In certain implementations, each of the network nodes can be configured / provided with one or more respective ones of beam index fields in the DCI. The configured / provided one or more respective ones of beam index fields for each of the network nodes can be consecutive or non-consecutive.
[0009] In certain implementations, each of the time indication field can be associated with one or more of the beam index fields. The associated one or more beam index fields for each time indication field can be used for one or more of the network nodes, respectively.
[0010] In some implementations, the beam index fields in the DCI can be reinterpreted as beam pattern index fields in the DCI. The time indication fields can be shared and used for one or more of the plurality of network nodes.
[0011] In certain implementations, each of the beam pattern index fields can be sequentially associated with a corresponding ones of the time indication fields with one-to-one mapping. Furthermore, in some implementations, a beam pattern list can be configured / provided for each of the plurality of network nodes, The beam pattern list can include one or more beam patterns.
[0012] In some implementations, each of the beam patterns can include one or more beam indexes. The one or more beam indexes in each of the beam patterns can be allocated for one or more of the plurality of network nodes, respectively. In certain implementations, the beam pattern list can be configured / provided to each of the plurality of network nodes via at least one of radio resource control (RRC) , medium access control control element (MAC CE) , or DCI signaling. Furthermore, the first message is sent in a new format of DCI.
[0013] In certain implementations, the DCI can be configured / provided for indicating the control information for the plurality of network nodes through at least one of the following. For example, a new radio network temporary identifier (RNTI) can be configured / provided to scramble the DCI indicating the control information for the plurality of network nodes. Similarly, a legacy RNTI can be configured / provided to scramble the DCI with one or a plurality of values, where one value is configured / provided to scramble the DCI for indicating the control information for a network node, and one or more other values are configured / provided to scramble the DCI indicating the control information for the plurality of network nodes. The DCI indicating the control information for the plurality of network nodes can be configured / provided to be monitored in a common search space. A new dedicated parameter can be configured / provided for the plurality of network nodes to differentiate whether the DCI is configured / provided for indicating the control information for the plurality of network nodes or for a network node.
[0014] In some implementations, the first message can be sent in a format of a new DCI signaling. The new DCI signaling can be scrambled through at least one of following. For example, It can be scrambled using a new RNTI. Furthermore, a legacy RNTI configured / provided to scramble DCI can have a plurality of values, where one value is configured / provided to scramble the DCI indicating the control information for a network node, and one or more other values can be configured / provided to scramble the new DCI signaling indicating the control information for the plurality of network nodes.
[0015] In certain implementations, the format can include or consist of a plurality of blocks, where each of the network nodes can be configured / provided with a respective one of the blocks. Each block can include or consist of at least one of the following: one or more beam indication fields, one or more time resource indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, or one or more polarization indication fields. Furthermore, the relationships between different types of the fields in each of the blocks can be respectively one-to-one mapping or one-to-more mapping.
[0016] In some implementations, the format can include or consist of a plurality of blocks, where each of the network nodes can be configured / provided with respective one or more of the blocks. Each block can further consist of at least one of the following: a beam indication field, a time resource indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field.
[0017] In certain implementations, the format can include or consist of a plurality of blocks and a plurality of time resource indication fields, where each of the network nodes can be configured / provided with a respective one of the blocks. Each block can further consist of at least one of the following: one or more beam indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, or one or more polarization indication fields. Furthermore, a plurality of time resource indication fields can be shared for the plurality of network nodes.
[0018] In some implementations, the relationships between each of the time indication fields and different types of the fields in a corresponding one of the blocks configured / provided for a corresponding one of the network nodes can be respectively one-to-one mapping or one-to-more mapping. Furthermore, the relationships between different types of the fields in each of the blocks can be respectively one-to-one mapping or one-to-more mapping.
[0019] In certain implementations, the format can include or consist of a plurality of blocks and a plurality of time resource indication fields, where each of the network nodes can be configured / provided with respective one or more of the blocks. Each block can include or consist of at least one of the following: a beam indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field. The time resource indication fields can be shared for the plurality of network nodes. The relationship between each of the plurality of time indication fields and respective one or more of the blocks configured / provided for a corresponding one of the network nodes can be one-to-one mapping or one-to-more mapping.
[0020] In some implementations, the format can include at least one of: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, or one or a plurality of polarization indication fields. Each of the network nodes can be configured / provided with one or more respective ones of the beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields. In some implementations, the configured / provided beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields for a corresponding one of the network nodes can be consecutive or non-consecutive. The relationships between different types of the fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping.
[0021] In certain implementations, the format can include at least one of: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, or one or a plurality of polarization indication fields. Each of the network nodes can be configured / provided with one or more respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields. The configured / provided one or more time indication fields in the DCI can be shared by the plurality of network nodes. In some implementations, the configured / provided beam indication fields, frequency indication fields, power indication fields, panel indication fields, and / or polarization indication fields for a corresponding one of the network nodes can be consecutive or non-consecutive. The relationships between each of the time indication fields and the respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping. Similarly, the relationships between different types of the fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping.
[0022] In some implementations, each of the network nodes can be configured / provided with one or more specific parameters to obtain the control information. Each of the plurality of network nodes can be configured / provided to obtain the control information through at least one of the following methods: a new dedicated parameter for the network node, or implicitly known by one or more specific parameters. The network node can know / determine that the first message contains the control information allocated for network node when the one or more specific parameters are configured / provided for the network node.
[0023] In some implementations, the related information can be configured / provided for each of the plurality of network nodes to monitor and / or decode the first message. The related information may include at least one of a logic index representing a corresponding network node or a number of network nodes for which the control information is configured / provided. The related information can be configured / provided to the network node from the wireless communication node via at least one of RRC, MAC CE, or DCI signaling.
[0024] At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. The wireless communication node can send / provide / transmit a second message to one of the network nodes, indicating control information that is configured / provided for the network node. Furthermore, when the control information indicated in the first message and the control information indicated in the second message for the same network node are contradictory, the priorities between the two messages can include at least one of the following: the latest message signaling has the highest priority, the first message has a higher priority than the second message, the second message has a higher priority than the first message, or whichever of the first and second messages includes a priority flag has the highest priority.
[0025] In some implementations, the wireless communication node can indicate control information to a group of SNs according to at least one of the following example configurations or solutions:
[0026] ● Example configuration 1: Reuse the legacy DCI (e.g., the DCI 2_8) to indicate the control information for a group of SNs;
[0027] ● Example configuration 2: Introduce a new DCI signaling to indicate the control information for a group of SNs;
[0028] ● Example configuration 3: Enabling of group signaling and group-related information can be indicated to SN.BRIEF DESCRIPTION OF THE DRAWINGS
[0029] Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader’s understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0030] FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure;
[0031] FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure;
[0032] FIG. 3 illustrates a schematic diagram of an example network, in accordance with some embodiments of the present disclosure;
[0033] FIG. 4 illustrates a schematic diagram of transmission links between BS to SN and SN to UE, in accordance with some embodiments of the present disclosure;
[0034] FIG. 5 illustrates the use of a DCI signaling in which the number of allocated beam index fields is equal to the number of allocated time resource indication fields for each SN, in accordance with some embodiments of the present disclosure;
[0035] FIG. 6 illustrates a sequential association of beam index and time resource indication fields, where each SN is configured / provided with one or more beam index fields and one or more time resource indication fields, in accordance with some embodiments of the present disclosure;
[0036] FIG. 7 illustrates the use of a beam pattern index and a time resource indication field to indicate the control information for a group of SNs, in accordance with some embodiments of the present disclosure;
[0037] FIG. 8 illustrates the field format of a DCI signaling, in accordance with some embodiments of the present disclosure;
[0038] FIG. 9 illustrates a DCI signaling in which the time resource indication fields are common and shared by all SNs in a group, in accordance with some embodiments of the present disclosure; and
[0039] FIG. 10 illustrates a flow diagram of an example method for indicating control information to a group of SNs, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION
[0040] 1. Mobile Communication Technology and Environment
[0041] FIG. 1 illustrates an example wireless communication network, and / or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100. ” Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In FIG. 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
[0042] For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118 / 124 may be further divided into sub-frames 120 / 127 which may include data symbols 122 / 128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and / or wired communications, in accordance with various embodiments of the present solution.
[0043] FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured / provided to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of FIG. 1, as described above.
[0044] System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) . The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
[0045] As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in FIG. 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.
[0046] In accordance with some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
[0047] The UE transceiver 230 and the base station transceiver 210 are configured / provided to communicate via the wireless data communication link 250, and cooperate with a suitably configured / provided RF antenna arrangement 212 / 232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured / provided to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured / provided to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
[0048] In accordance with various embodiments, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some embodiments, the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
[0049] Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.
[0050] The network communication module 218 generally represents the hardware, software, firmware, processing logic, and / or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured / provided to communicate with the base station 202. For example, network communication module 218 may be configured / provided to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured / provided for, ” “configured / provided to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and / or arranged to perform the specified operation or function.
[0051] The Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols. The OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, a sixth layer may be a Non Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.
[0052] Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
[0053] 2. Systems and Methods for Interference Measurement for Network Nodes (e.g., SN)
[0054] In certain systems (e.g., 5G new radio (NR) , Next Generation (NG) systems, 3GPP systems, and / or other systems) , a network-controlled repeater (NCR) can be introduced as an enhancement over conventional RF repeaters with the capability to receive and / or process side control information from the network. Side control information can allow a network-controlled repeater to perform / execute / operate its amplify-and-forward operation in a more efficient manner. Certain benefits can include at least mitigation of unnecessary noise amplification, transmissions and receptions with better spatial directivity, and / or simplified network integration.
[0055] The NCR can be regarded as a stepping stone of a re-configurable intelligent surface (RIS) . A RIS node can adjust the phase and amplitude of the received signal to improve / enhance the coverage (e.g., network communication coverage) . As discussed herein, network nodes, including and not limited to NCR, smart repeater, enhanced RF repeaters, RIS, and / or integrated access and backhaul (IAB) , can be denoted, referred to, or provided as a smart node (SN) (e.g., network node) for simplicity. The SN can refer to one kind of node which can support the controllable amplify-and forward or forward operation of wireless signal. For example, the SN can include, correspond to, or refer to a kind of network node to assist the BS 102 to improve coverage (e.g., avoiding / averting blockage / obstructions, increasing transmission range, etc. ) .
[0056] In certain cases, an SN may maintain multiple links simultaneously, such as a link between the BS 102 and the SN and another link between the SN and the UE 104 to ensure signal forwarding for the BS 102 and the UE 104. However, the forwarded signal from the SN to the UE 104 may interfere with the reception of signal from the BS 102 to the SN, or vice versa (sometimes referred to or denoted as self-interference, self-oscillator, or self-excitation) . Hence, the systems and methods of the technical solution discussed herein can provide or introduce functionalities for measuring the interference (e.g., self-interference) of / on the SN and / or potential actions to be performed by the BS 102 and / or the SN according to the interference measurement result, such as to address, resolve, or minimize interference of signal forwarding.
[0057] FIG. 3 illustrates a schematic diagram of an example network 300. As illustrated in FIG. 3, one or more BSs 102A-B (e.g., BSs 102) can serve one or more UEs 104A-B (e.g., UEs 104) respectively in their cells via the respective one or more SNs 306A-B (e.g., sometimes labeled as SN (s) 306) , such as when there are blockages between the BS (s) 102 and the UE (s) 104.
[0058] FIG. 4 illustrates a schematic diagram 400 of transmission links between BS 102 to SN 306 and SN 306 to UE 104. The SN 306 can include or consist of at least two units or functional parts / components (e.g., sometimes referred to as function entities) , such as the communication unit (CU) (e.g., SN CU) and the forwarding unit (FU) (e.g., SN FU) . The units of the SN 306 can support different functions for communication with at least one of the BS 102 and / or the UE 104. A first unit (or function entity) of the SN 306 may refer to the SN CU and a second unit (or function entity) of the SN 306 may refer to the SN FU or vice versa, in some cases. For example, the SN CU (e.g., first unit) can be a network-controlled repeater (NCR) MT. In another example, the SN FU (e.g., second unit) can be an NCR forwarder / forwarding (Fwd) . The SN CU can act / behave or include features similar to a UE 104, for instance, to receive and decode side control information from the BS 102. The SN CU may be a control unit, controller, mobile terminal (MT) , part of a UE, a third-party IoT device, and so on. The SN FU can carry out the intelligent amplify-and-forward operation using the side control information received by the SN CU. The SN FU may be a radio unit (RU) , a RIS, and so on.
[0059] In some examples, the unit to achieve each functionality (or each functional parts / components) may refer to the separate or dedicated components of SN. In some examples, the unit for each functionality may refer to the different logic parts of same component SN. The interface to enable the information exchange / transition between these two unit can also be supported optionally. In the following parts of the disclosure, for convenience of description, the FIG. 4 is taken as example by assuming the operation between BS and FU, FU and UE, BS and UE” . One of the entity can be replaced by others as described above.
[0060] The transmission links between the BS 102 to SN 306 and the SN 306 to UE 104 as shown in FIG. 4 can be defined / described / provided as follows:
[0061] C1: Control link (C-link) from SN CU to BS;
[0062] C2: Control link (C-link) from BS to SN CU;
[0063] F1: Backhaul link from SN FU to BS;
[0064] F2: Backhaul link from BS to SN FU;
[0065] F3: Access link from UE to SN FU; and
[0066] F4: Access link from SN FU to UE.
[0067] Control link (e.g., sometimes referred to as a communication link) can refer to or mean that the signal from one side will be detected and decoded by the other side, so that the information transmitting in / via the control link can be utilized to control the status of forwarding links (e.g., backhaul links and / or access links, F-link) . Forwarding link can mean that the signal from BS 102 or UE 104 is unknown to SN FU. In this case, the SN FU can amplify and forward signals without decoding them. For example, the F1 and F3 links can correspond to or be associated with the complete uplink (UL) forwarding link (e.g., backhaul link and access link, respectively) from UE 104 to BS 102, in which F1 is the SN FU UL forwarding link. Additionally, the F2 and F4 links can correspond to or be associated with the complete DL forwarding link (e.g., backhaul link and access link, respectively) from BS 102 to UE 104, in which F4 is the SN FU DL forwarding link. The F1 and F2 links can correspond to or be referred to as backhaul links and F3 and F4 links can correspond to or be referred to as access links.
[0068] 3. Systems and Methods for Indicating Control Information to Network Nodes (e.g., SNs)
[0069] As detailed herein, coverage is a critical aspect of cellular network deployments, and mobile operators rely on various network nodes to provide wide-ranging coverage. To increase flexibility, new types of network nodes have been explored. For example, IAB was introduced in Rel-16 and enhanced in Rel-17 as a wireless node that eliminates the need for wired backhaul. As explained above, another type is the RF repeater, which amplifies and forwards received signals. RF repeaters have been extensively used in 2G, 3G, 4G, and 5G systems to supplement the coverage provided by regular full-stack cells. However, the RF repeater operates with only a radio unit.
[0070] In Rel-18, NCR is introduced as an improvement over conventional RF repeaters. The NCR can receive and process side control information from the network. This allows / enables NCRs to amplify the signal only when necessary, which reduces interference and noise. To indicate control information for the NCR, the current specification uses a predefined list of time resources for each aperiodic beam indication in the access link, pre-defined by RRC signaling. Each time resource is defined by specific fields, including starting slot, starting symbol, and duration.
[0071] Nevertheless, there may exist issues that if the BS wants to send / provide / transmit control information to a group of SNs, there may introduce a need that using a signaling to indicate the control information to a group of SNs. Here, the ‘a group of SNs’ means a plurality of SNs. For this purpose, the existing DCI (e.g., the DCI 2_8) , i.e., a unicast signaling that used to indicate the control information for a SN can be enhanced as a group signaling to indicate the control information for a group of SNs, or a new downlink control information (DCI) signaling can be introduced as a group signaling to indicate the control information for a group of SNs. Here, the unicast signaling means the signaling only carries the control information for a SN, and the group signaling means the signaling carries the control information for a plurality of SNs.
[0072] In some implementations, the current DCI 2_8 can be scrambled with the legacy RNTI (i.e., ncr-RNTI) to send / provide / transmit control information to a specific SN. In order to differentiate the DCI 2_8 when it is used to indicate control information to a group of SNs, different RNTI values can be considered to scramble the DCI 2_8. In some configurations, a new RNTI, e.g., ncr-G-RNTI, can be introduced to scramble the DCI 2_8 that is used for signaling to a group of SNs. Each SN can be configured / provided with one or more ncr-G-RNTI values, such as ncr-G-RNTI SEQUENCE (SIZE (1.. maxNrofNCRGroupRNTIs) ) OF RNTI-Value. The maxNrofNCRGroupRNTIs parameter represents the maximum number of ncr-G-RNTI values that can be configured / provided for a SN. This parameter can be pre-defined or configured / provided by the BS. When a SN is configured / provided with multiple ncr-G-RNTI values, it indicates that the SN is configured / provided into multiple groups, and each group has a different ncr-G-RNTI value. The SNs in a same group are configured / provided with the same ncr-G-RNTI value.
[0073] In some implementations, the legacy RNTI, ncr-RNTI, can be reused with enhancements, e.g., ncr-RNTI can be configured / provided with one or more RNTI values. This allows / enables the SN to differentiate the DCI 2_8 for unicast or for a group of SNs. For example, “ncr-RNTI-r18” includes a sequence of RNTI values, with a size ranging from 1 to the maximum number of NCRRNTIs (maxNrofNCRRNTIs) . The maxNrofNCRRNTIs parameter represents the maximum number of ncr-RNTI values that can be configured / provided for a SN. This parameter can be pre-defined or configured / provided by the BS. For example, a pre-defined rule can be defined that the first RNTI value of ncr-RNTI is used to scramble the DCI 2_8 for unicast signaling, while the second and subsequent RNTI values of ncr-RNTI are used to scramble the DCI 2_8 for group signaling for a group of SNs. In this way, the SN can always know / determine whether the DCI 2_8 is intended for it or for a group of SNs, regardless of how many RNTI values are configured / provided for it.
[0074] For example, a pre-defined rule can be defined that the last configured / provided RNTI value of ncr-RNTI is used to scramble the DCI 2_8 for unicast signaling, while the other remaining RNTI values of ncr-RNTI are used to scramble the DCI 2_8 for group signaling for a group of SNs. In this way, the SN can always know / determine whether the DCI 2_8 is intended for it or for a group of SNs.
[0075] In some configurations, the DCI 2_8 can be used for group signaling. In this case, the DCI 2_8 can be monitored in a Common Search Space (CSS) . When an SN receives an RRC configuration that the DCI format 2_8 is configured / provided to be monitored in a CSS, the SN can know / determine that the DCI 2_8 is a group signaling that is used to indicate control information to a group of SNs. However, if the SN receives an RRC configuration that the DCI format 2_8 is configured / provided to be monitored in a USS, the SN can know / determine that the DCI 2_8 is a unicast signaling that only carries the control information for itself.
[0076] In some configurations, a dedicated parameter can be defined by the base station for the user equipment via at least one of the RRC, medium access control (MAC) control element (CE) , or DCI signaling to differentiate whether the DCI 2_8 is used for unicast or group signaling. For example, a dedicated RRC parameter called “EnableGroupSignaling” can be introduced. When this parameter is configured / provided for the SN and set to enabled, it means / indicates / informs that the DCI 2_8 is used for group signaling. Otherwise, it means / indicates / informs that the DCI 2_8 is used for unicast signaling. Another example is a dedicated RRC parameter called “GroupOrUnicast. ” When the value of this parameter is configured / provided as 1, it means / indicates that the DCI 2_8 is used for group signaling. Otherwise, it means / indicates that the DCI 2_8 is used for unicast signaling.
[0077] A new / specific MAC CE signaling can also be used to indicate whether the DCI 2_8 is used for unicast or group signaling. In some implementations, the new / specific MAC CE signaling may include a field to activate or deactivate group signaling function of DCI 2_8. When this MAC CE signaling is used to activate group signaling, the DCI 2_8 is used to indicate the control information for a group of SNs. When this MAC CE signaling is used to deactivate group signaling, the DCI 2_8 is used as a unicast signaling to indicate the control information for a SN. Moreover, a new / specific field can be added to the current DCI 2_8 signaling. This new / specific field can be used to differentiate whether the DCI 2_8 is used for unicast or group signaling. In some examples, when this new / specific field is set to zero, this setting / value means / indicates / informs that the control information contained in DCI 2_8 is used for a SN. Otherwise, the setting / value means / indicates that the control information contained in DCI 2_8 is used for a group of SNs.
[0078] In some implementations, when the DCI 2_8 is used for group signaling, one or more new higher layer parameters is to be configured / provided to enable each SN to know / determine where to obtain the control information that is allocated for it in the DCI 2_8. In this case, whether the DCI 2_8 is used for unicast signaling or group signaling can be implicitly determined by these newly configured / provided higher layer parameters. For example, when the DCI 2_8 is used for group signaling, a new higher layer parameter should be defined for the SN to determine the start position of the allocated beam fields inside the DCI 2_8 payload. When this higher layer parameter is configured / provided to the SN, the SN can know / determine that the detected DCI 2_8 is used for group signaling. Another example is that a new higher layer parameter should be defined for the SN to determine the number of allocated beam fields in the DCI 2_8. When this higher layer parameter is configured / provided to the SN, the SN can know / determine that the detected DCI 2_8 is used for group signaling for a group of SNs.
[0079] The field format of DCI 2_8 can be enhanced when DCI 2_8 is used to indicate the control information for a group of SNs. In the legacy specification, the format of the current DCI 2_8 includes beam index fields and time resource indication fields. The number of beam index fields is equal to the number of time resource indication fields. The number of time resource indication fields is determined by the length of the RRC configured / provided list. The bitwidth of the beam index field is configured / provided by the RRC parameter AperiodicBeamFieldWidth, and the bitwidth of the time resource indication field is determined by max where here I is the number of time domain resources configured / provided by ncr-AperiodicFwdConfig. The N is configured / provided by the RRC parameter numberOfFields.
[0080] In some implementations, the DCI 2_8 can be reinterpreted to indicate the control information for a group of SNs. For example, this can be done by re-interpreting the meaning of (e.g., re-purposing / re-defining) the fields in DCI 2_8. In some configurations, each SN can be configured / provided with one or more beam index fields and one or more time resource indication fields. The allocated beam information fields and time resource indication fields can be consecutive or non-consecutive. The term “consecutive” refers to the fact that the allocated beam information fields and allocated time resource indication fields are continuous, respectively. It does not mean that the information indicated in the corresponding field are “consecutive. ” For example, if an SN is allocated with two consecutive beam index fields, it means / indicates / informs that the SN has been allocated with the beam index field X and beam index field X+1. It does not mean that the information indicated in the two beam index fields must be the beam index Y and beam index Y+1. This definition is consistently applied throughout various scenarios. For each SN, the allocated time indication field is sequentially associated with the allocated beam index fields in one-to-one mapping or one-to-more mapping. And when the allocated time indication field and the allocated beam index fields is one-to-more mapping, and since the total number of beam index fields in the DCI is equal to the total number of beam index fields, it means there may exist a case that some time indication fields in the DCI may not be configured to the SNs. And in this way, these time indication fields can be treated as invalid and not used by SNs.
[0081] For each SN, when the allocated time indication field and the allocated beam index fields is one-to-one mapping, the number of allocated beam index fields can be equal to the number of allocated time resource indication fields. For example, as shown in FIG. 5, each SN can be configured / provided with one or more consecutive beam index fields and one or more consecutive time resource indication fields, respectively. For each SN, the allocated beam index field is sequentially associated with the allocated time resource indication fields with one-to-one mapping, and for each SN, the number of allocated beam index fields is equal to the number of allocated time indication fields. As shown, the group includes three SNs, and the DCI 2_8, which includes six beam index fields and six time resource indication fields, is used for indicating the control information for the three SNs. SN1 is allocated with two beam index fields and two time resource indication fields, SN2 is allocated with one beam index field and one time resource indication field, and SN3 is allocated with three beam index fields and three time resource indication fields.
[0082] However, in some implementations, the allocated beam index fields and time resource indication fields for different SNs can be “non-consecutive. ” The term “non-consecutive” refers to the fact that the allocated beam information fields and allocated time resource indication fields are non-continuous, respectively. For example, as shown in FIG. 5, the group may include three SNs, and the DCI 2_8, which includes six beam index fields and six time resource indication fields, is used for indicating the control information for the three SNs. SN1 is allocated with two beam index fields and two time resource indication fields, SN2 is allocated with one beam index field and one time resource indication field, and SN3 is allocated with three beam index fields and three time resource indication fields.
[0083] As detailed herein, the number of beam index fields in the DCI 2_8 is equal to the number of time resource indication fields. To configure each SN with one or more beam index fields and one or more time resource indication fields, the number of beam index fields and time resource indication fields that allocated for it is to be determined for each SN.
[0084] In some configurations, the legacy RRC parameter numberOfFields can be reused to determine the number of time resource indication fields that are allocated for a SN. In this case, the number of allocated beam index fields is equal to the number of allocated time resource indication fields for a SN. For example, if the DCI 2_8 is used to indicate the control information for a group of SNs, and assuming that the DCI 2_8 has six time resource indication fields in total, and the first three time resource indication fields are allocated for SN1, then the value of the RRC parameter numberOfFields can be configured / provided as three for SN1 by the BS.
[0085] In some configurations, a new higher layer parameter can be used to configure the number of allocated beam index fields in DCI 2_8 for a SN by the BS via the RRC, MAC CE, or DCI signaling. In this case, the number of allocated time indication fields for a SN is equal to the number of allocated beam index fields. The legacy RRC parameter numberOfFields can be used to indicate the total number of time indication fields in DCI 2_8. Therefore, the total number of beam index fields in DCI 2_8 can be equal to the total number of time indication fields in the DCI 2_8. For example, assuming that the DCI 2_8 includes six beam index fields and six time resource indication fields, and that three beam index fields are allocated for SN1, the BS can configure the value of the new parameter as three for SN1, and the value of the current RRC parameter numberOfFields as six for SN1. After receiving the value of the new parameter, SN1 knows / determines that there are three beam index fields and three time resource indication fields that are allocated for it in DCI 2_8.
[0086] In some configurations, a new higher layer parameter can be used by the BS to configure the number of allocated time resource indication fields in DCI 2_8 for a SN via RRC, MAC CE, or DCI signaling. In this case, the number of allocated beam index fields for a SN is equal to the number of allocated time indication fields. The legacy RRC parameter numberOfFields can be used to indicate the total number of time indication fields in DCI 2_8. Therefore, the total number of beam index fields in DCI 2_8 can be equal to the total number of time resource indication fields in DCI 2_8.
[0087] In some configurations, the number of allocated beam index and time resource indication fields for a SN can be implicitly determined. For example, if the BS configures the start position of the first allocated beam index field and the end position of the last allocated beam index field inside the DCI payload to the SN, the SN can implicitly calculate the number of allocated beam index fields. Since the number of time resource indication fields allocated for the SN is equal to the number of allocated beam index fields, the number of allocated time resource indication fields can also be obtained. Similarly, if the BS configures the start position of the first allocated time indication field and the end position of the last allocated time resource indication field inside the DCI payload to the SN, the SN can implicitly calculate the number of allocated time resource indication fields. Since the number of beam index fields allocated for the SN is equal to the number of allocated time resource indication fields, the number of allocated beam index fields can also be obtained.
[0088] In some implementations, to configure each SN with one or more beam index fields and one or more time resource indication fields, the bitwidth of the allocated beam index fields and time indication fields in the DCI 2_8 is to be determined by the SN. In some configurations, the legacy RRC parameter aperiodicBeamFieldWidth can be used to configure the bitwidth of all beam index fields in DCI 2_8. This results in all SNs in the group having the same number of beams that can be used. In some configurations, the current RRC parameter aperiodicBeamFieldWidth can be reinterpreted to represent the bitwidth of beam index fields that are allocated for a specific SN. As a result, the bitwidth of beam index fields that are allocated for different SNs can be different. In some configurations, the bitwidth of the allocated beam index fields can be implicitly obtained by the SN. For example, if the BS configures a list of start positions corresponding to the allocated beam index fields for the SN, the first start position corresponds to the start position of the first allocated beam index field for the SN, the second start position corresponds to the start position of the second allocated beam index field for the SN, and so on. If the allocated beam index fields for a SN are consecutive, the SN can calculate the bitwidth of beam index fields by the difference in bits between two consecutive start positions.
[0089] Furthermore, the bitwidth of the allocated time indication fields can be determined in different ways. In some configurations, the bitwidth is determined by the number of entries of the RRC configured / provided list ncr-AperiodicFwdConfig, as detailed herein. In some configurations, the bitwidth of allocated time resource indication fields can be implicitly obtained by the SN. For example, if the BS configures a list of start positions corresponding to the allocated time indication fields for the SN, the first start position corresponds to the start position of the first allocated time indication field for the SN, the second start position corresponds to the start position of the second allocated time indication field for the SN, and so on. If the allocated time resource indication fields for a SN are consecutive, the SN can calculate the bitwidth of time resource indication fields by the difference in bits between two consecutive start positions.
[0090] Since the DCI 2_8 includes the control information for multiple SNs, each SN is to know / determine where to find the allocated beam index information inside the DCI 2_8 payload. In some configurations, the start position of the first allocated beam index field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, if the allocated beam index fields for the SN in the DCI 2_8 are consecutive, the start position of the first allocated beam index field inside the DCI payload can be configured / provided to the SN by the BS. In this case, the bitwidth of beam index fields allocated for the SN can be configured / provided by the current RRC parameter AperiodicBeamFieldWidth. The number of beam index fields allocated for the SN can be determined as detailed herein. This allows the SN to obtain its own beam information from the DCI 2_8 payload.
[0091] Similarly, in some configurations, the start position of the first allocated beam index field and the end position of the last allocated beam index field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, if the allocated beam index fields for the SN in the DCI 2_8 are consecutive, the BS can configure the start position of the first allocated beam index field and the end position of the last allocated beam index field inside the DCI payload. In this case, the bitwidth of the beam index fields allocated for the SN can be configured / provided using the legacy RRC parameter AperiodicBeamFieldWidth. As a result, there may be no need to explicitly configure the number of beam index fields or time resource indication fields to the SN. The number of beam index fields allocated for the SN can be implicitly calculated, and the number of allocated time resource indication fields is equal to the number of allocated beam index fields.
[0092] In some configurations, the BS can configure a list of start positions to the SN via at least one of RRC, MAC CE, or DCI signaling. The first start position corresponds to the start position of the first allocated beam index field, the second start position corresponds to the start position of the second allocated beam index field, and so on. In this case, the number of beam index fields allocated for the SN can be implicitly obtained / determined from the number of configured / provided start positions in the list. When the allocated beam index fields for the SN are consecutive, the bit width of the beam index fields allocated for the SN can also be implicitly known / determined by the SN.
[0093] In some configurations, each beam field in the DCI 2_8 is numbered sequentially, starting with one for instance. This numbering scheme is referred to as the logic index. The logic index represents the numbering / index of the first allocated beam index field for a specific SN. For example, if there are six beam index fields in the DCI 2_8, including the control information for three SNs, and the first allocated beam index field for SN1 is beam index field 3, then the logic index for SN1 would be three. In order to use this method of configuration, the bit width of all beam index fields should be the same, and the size of the DCI 2_8 should be known by the SN. The number of allocated beam index fields for a SN can be determined, as detailed herein. Once the logic index and the number of allocated beam index fields are known, the SN can obtain the allocated beam information from DCI 2_8.
[0094] In some configurations, a list of logic indices can be configured / provided to the SN. Each logic index represents the numbering / index of an allocated beam index field for the SN. The first logic index represents the numbering / index of the first allocated beam index field for the SN, the second logic index represents the numbering / index of the second allocated beam index field for the SN, and so on. This method of configuration requires that the bitwidth of all beam index fields be the same. The number of allocated beam index fields for the SN can be implicitly known by the SN from the number of entries in the list.
[0095] In some configurations, the position of allocated beam index fields inside the DCI payload can be implicitly known by the SN. This is possible if the logic index that represents the numbering / index of the first allocated time indication field is configured / provided to the SN, and the logic index that represents the numbering / index of the first allocated beam index field is the same as the logic index for the first allocated time resource indication field. In this case, the bitwidth of all beam index fields and the bitwidth of all time resource indication fields should be the same. For example, if there are six beam index fields and six time resource indication fields in the DCI 2_8 that are used for the control information for three SNs, and the first allocated time resource indication field is time resource indication field 3 for the SN1, then the BS can configure the logic index 3 to the SN1 and can also configure to the SN that the number of allocated time indication fields is two. In this way, the SN1 can know / determine that the first allocated beam index field is beam index 3, and the number of allocated beam index fields is two.
[0096] In some configurations, a logic index can be configured / provided to each SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or can be configured / provided to each SN via operations, administration and maintenance (OAM) signaling / protocol. The logic index represents the numbering / index of the first allocated beam index fields and the first allocated time indication fields for the SN in the DCI 2_8. For example, if there are six beam index fields (i.e., beam index field 1, beam index field 2, ..., beam index field 6) and six time indication fields (i.e., time indication 1, time indication 2, ..., time indication 6) in the DCI 2_8 including the control information for three SNs, and the logic index configured / provided to the SN1 is three, then the first allocated beam index field for SN1 is beam index 2, and the first allocated time resource indication field is time resource indication 3.
[0097] In some configurations, a list of logic indices can be configured / provided to each SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or can be configured / provided to each SN via the OAM. The logic indices represent the numbering / index of the first allocated beam index fields and the first allocated time resource indication fields for the SN in the DCI 2_8. The first logic index represents the numbering / index of the first allocated time resource indication field and allocated beam index field for the SN, the second logic index represents the numbering / index of the second allocated time resource indication field and allocated beam index field for the SN, and so on. In this case, the number of allocated beam index fields and time indication fields can be implicitly known by the SN via the number of entries in the list.
[0098] To configure each SN with one or more beam index fields and one or more time resource indication fields, the SN determines the position of the allocated time resource indication fields inside the DCI payload. In some configurations, the start position of the first allocated time indication fields can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, if the allocated time indication resource fields for the SN in the DCI 2_8 are consecutive, the BS can configure the start position of the first allocated time indication field to the SN. In this case, the bitwidth of the time resource indication field is determined by max where I is the number of time domain resources configured / provided by ncr-AperiodicFwdConfig. The number of time resource indication fields allocated for the SN can be determined using the options detailed herein. As a result, the SN can obtain its own time information from the DCI 2_8 payload.
[0099] In some configurations, the start position of the first allocated time resource indication field and the end position of the last allocated time resource indication field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. This is useful in cases where the allocated time indication fields for the SN are consecutive. In this case, the bitwidth of the time resource indication fields allocated for the SN can follow the current specification. Therefore, the number of time indication fields allocated for the SN can be implicitly calculated. Since the number of allocated beam index fields is equal to the number of allocated time indication fields, there is no need to explicitly configure the number of beam index fields or time indication fields to the SN. The existing RRC parameter numberOfFields can be used to indicate the total number of time indication fields in the DCI 2_8, or can also be re-interpreted / re-purposed to indicate the number of time indication fields allocated for the SN in the DCI 2_8. In either case, it may not be necessary for the BS to configure this parameter to the SN.
[0100] In some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The first start position corresponds to the start position of the first allocated time resource indication field, the second start position corresponds to the start position of the second allocated time resource indication field, and so on. In this case, there may be no need to explicitly configure the number of beam index fields or time indication fields to the SN. The number of time indication fields allocated for the SN can be implicitly obtained by the number of configured / provided start positions in the list. Additionally, the number of allocated beam index fields is equal to the number of allocated time resource indication fields. The existing RRC parameter numberOfFields can be used to indicate the total number of time indication fields in the DCI 2_8, and / or can be re-interpreted to indicate the number of time resource indication fields allocated for the SN in the DCI 2_8. In either case, it may not be necessary for the BS to configure this parameter to the SN. If the allocated time indication fields are consecutive, the bitwidth of the time indication fields allocated for the SN can also be calculated implicitly.
[0101] In some configurations, the time resource indication fields in the DCI 2_8 are numbered sequentially, starting from 1 for instance (or any interger value) . For example, the time indication fields may be numbered as time indication field 1, time indication field 2, and so on. This numbering scheme is referred to as the logic index. The logic index represents the numbering / index of the first allocated time resource indication field for a specific SN. For example, if there are six time resource indication fields in the DCI 2_8 including the control information for three SNs, and the first allocated time resource indication field for SN1 is time resource indication field 3, then the logic index 3 can be configured / provided to SN1. In this case, it may be required that the bitwidth of all time resource indication fields and the bitwidth of all beam index fields be the same. Since the number of allocated time resource indication fields for the SN can be known by the SN as detailed herein, the SN can obtain the allocated time resource indication from DCI 2_8.
[0102] In some configurations, a list of logic indices can be configured / provided to the SN. Each logic index represents the numbering / index of an allocated time indication field for the SN. The first logic index represents the numbering / index of the first allocated time indication field for the SN, the second logic index represents the numbering / index of the second allocated time indication field for the SN, and so on. In this case, the bitwidth of all time resource indication fields should be the same. The number of allocated time resource indication fields for the SN can be implicitly known by the SN from the number of entries in the list.
[0103] In some configurations, the SN can implicitly determine the position of allocated time indication fields inside the DCI payload if the BS configures the logic index that represents the numbering / index of the first allocated beam index field to the SN. The logic index that represents the numbering / index of the first allocated time resource indication field can be the same as the logic index for the first allocated beam index field. In this case, it is required that the bitwidth of all beam index fields and the bitwidth of all time resource indication fields be the same. This allows / enables the SN to determine the allocated beam and time resource information from the DCI 2_8. For example, if there are six beam index fields and six time indication fields in the DCI 2_8 that are used for the control information for three SNs, and the first allocated beam index field for SN1 is beam index field 3, then the BS can configure the logic index 3 to SN1 and can configure to the SN that the number of allocated beam index fields is 2. In this way, SN1 can determine that the first allocated time resource indication field is time resource indication 3, and the number of allocated time resource indication fields is two.
[0104] In some configurations, the BS can configure a logic index to each SN via RRC, MAC CE, DCI signaling, or OAM. The logic index represents the numbering / index of the first allocated beam index field and the first allocated time resource indication field for the SN in the DCI 2_8. For example, if there are six beam index fields (e.g., beam index field 1, beam index field 2, ..., beam index field 6) and six time resource indication fields (i.e., time indication 1, time indication 2, ..., time indication 6) in the DCI 2_8, and the logic index configured / provided to the SN1 is three, this configured value means / indicates / informs the first allocated beam index field for SN1 is beam index 2, and the first allocated time resource indication field is time resource indication 3.
[0105] In some configurations, the BS can configure a list of logic indices to each SN via RRC, MAC CE, DCI signaling, or OAM signaling / protocol. The logic indices represent the numbering / index of the first allocated beam index field and the first allocated time resource indication field for the SN in the DCI 2_8. The first logic index represents the numbering / index of the first allocated time resource indication field and allocated beam index field for the SN, the second logic index represents the numbering / index of the second allocated time resource indication field and allocated beam index field for the SN, and so on. In this case, the number of allocated beam index fields and time resource indication fields can be implicitly known by the SN via the number of entries in the list.
[0106] In some implementations, to configure each SN with one or more beam index fields and one or more time resource indication fields, the SN is to determine the size of the received DCI 2_8 before decoding. As detailed herein, since the DCI 2_8 only carries the information for a specific SN, the SN can calculate the size of the DCI 2_8 using the configured / provided RRC parameter. However, when the DCI 2_8 is used to indicate the control information to a group of SNs, the SN cannot calculate the size of the DCI 2_8 since the SN does not know the bitwidth and number of beam index fields that are allocated for other SNs. In this regard, the size of DCI 2_8 can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some configurations, size can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0. In some configurations, the size of DCI 2_8 can be implicitly obtained / calculated by the SN. For example, if the bitwidth of all beam index fields in DCI 2_8 is the same as the bitwidth of all time resource indication fields in DCI 2_8, and this information is known to the SN, then the SN can implicitly calculate the size of DCI 2_8.
[0107] As detailed herein, the DCI 2_8 can be reinterpreted to indicate the control information for a group of SNs. This can be done by re-interpreting the meaning of the fields in DCI 2_8. In some implementations, the timing information for each SN in the same group can be the same and shared by a group of SNs. In this case, the time resource indication fields in the DCI 2_8 can be used and shared by multiple SNs. This means / indicates / informs that the time resource indication field and the beam index field in DCI 2_8 are one-to-more mapped, which means / indicates that one or more beam index fields can be associated with one time resource indication field. In this way, for the fields of DCI 2_8, each SN can be configured / provided with one or more beam index fields and one or more time resource indication fields. The allocated beam information fields and the allocated time indication information can be consecutive or non-consecutive. As detailed herein, the term “consecutive” can refer to the fact that the allocated beam information fields and allocated time resource indication fields are continuous, respectively. It does not mean that the information indicated in the corresponding field should be consecutive. For example, if a SN is allocated with two consecutive beam index fields, this can mean / indicate / inform that the SN has been allocated with beam index field X and beam index field X+1. It does not mean that the indicated information in the two beam index fields should be beam index Y and beam index Y+1. For each SN, the allocated beam index field is sequentially associated with the allocated time resource indication fields. This means / indicates that for each SN, the beam index fields and time resource indication fields are paired up in a one-to-one manner. The number of allocated beam index fields is also equal to the number of allocated time resource indication fields.
[0108] Referring to FIG. 6, depicted is the sequential association of beam index and time resource indication fields, allowing the BS to efficiently convey control information to a group of SNs. As shown, the DCI 2_8 is used to indicate the control information for a group of SNs to cooperatively operate. The timing information for each SN in the same group can be the same and shared by a group of SNs, and each SN can be allocated with one or more consecutive beam index fields. The DCI 2_8 can be structured as a sequence of beam index fields and time resource indication fields, numbered sequentially from 1 to N. The time resource indications in the DCI 2_8 are common and shared for a group of SNs. For the beam index fields in the DCI 2_8, each SN is configured / provided with one or more consecutive beam index fields. For each SN, the allocated beam index fields are sequentially associated with the time resource indication fields with one-to-one mapping. For example, as shown in FIG. 6, the DCI 2_8 includes six time indication fields and six beam index fields, and it is used to indicate the control information for three SNs. The time resource indication fields in the DCI 2_8 are shared by the three SNs. SN 1 is allocated with beam index field 1, which is associated with time resource indication field 1. SN 2 is allocated with beam index fields 2 and 3, which are associated with time resource indication fields 1 and 2, respectively. SN 3 is allocated with beam index fields 4, 5, and 6, which are associated with time resource indication fields 1, 2, and 3, respectively.
[0109] In some implementations, the timing information for each SN in the same group can be the same and shared by a group of SNs. Additionally, the time resource indication field can be applicable to one or more consecutive beam index fields. This indicates that one or more consecutive beam index fields can correspond to one or more SNs, respectively. In this way, the allocated beam index fields for a SN may not be consecutive. For example, as shown in FIG. 6, the DCI 2_8 includes six time resource indication fields and six beam index fields, and it is used to indicate the control information for three SNs. The time resource indication fields in the DCI 2_8 are shared by the three SNs. The time resource indication 1 is associated with the beam index fields 1, 2, and 3, where the beam index field 1 is allocated for SN 1, the beam index field 2 is allocated for SN 2, and the beam index field 3 is allocated for SN 3. The time resource indication 2 is associated with the beam index fields 4, 5, and 6, where the beam index field 4 is allocated for SN 1, the beam index field 5 is allocated for SN 2, and the beam index field 6 is allocated for SN 3. The remaining time resource indication fields 3, 4, 5, and 6 are invalid or not used by a group of SNs, and these time resource indication fields can be ignored by the SNs.
[0110] As detailed herein, all the time resource indication fields are shared by a group of SNs. Therefore, the RRC configured / provided list of time resource information by ncr-AperiodicFwdConfig should be the same for all SNs in the group. The number of time resource indication fields in the DCI 2_8 can also be configured / provided by the RRC signaling numberOfFields, as detailed herein.
[0111] In some implementations, to associate the time resource indication fields in DCI 2_8 with multiple SNs, the number of allocated beam index fields for each SN can be determined. In some configurations, the BS can configure the number of allocated beam index fields in DCI 2_8 to the SN via at least one of RRC, MAC CE, or DCI signaling. Moreover, different SNs can be configured / provided with the same or different numbers of beam index fields. In some configurations, the number of allocated beam index fields can be implicitly determined by the SN.This is done by the BS configuring the start position of the first allocated beam index field and the end position of the last allocated beam index field inside the DCI payload. The bitwidth of beam index fields can be configured / provided to the SN via the current RRC parameter. The SN can then implicitly calculate the number of allocated beam index fields, as detailed herein. Furthermore, in some configurations, if each SN in the group is assigned the same number of allocated beam index fields, this number can be a predefined value known by both the BS and all SNs in the group. In some configurations, the number of allocated beam index fields in the DCI 2_8 for a particular SN can be a predefined value known by both the SN and the BS. Different SNs within the group may have either different or the same predefined values.
[0112] In some implementations, to associate the time resource indication fields in DCI 2_8 with multiple SNs, the bitwidth of the allocated beam information for the SN can be determined. In some configurations, the legacy RRC parameter aperiodicBeamFieldWidth can be used to configure the bitwidth of all beam index fields in DCI 2_8. This indicates that all SNs in the group can have the same number of beams that is to be used. In some configurations, the current RRC parameter aperiodicBeamFieldWidth can be reinterpreted to represent the bitwidth of beam index fields that are allocated for a specific SN. This indicates that the bitwidth of the beam index fields can be different for different SNs. In some configurations, the bitwidth of allocated beam index fields can be implicitly determined by the SN. This can be done by the BS configuring a list of start positions corresponding to the allocated beam index fields to the SN. The start positions are consecutive, and the SN can calculate the bitwidth of beam index fields by the bit difference of two consecutive start positions. Furthermore, in some configurations, the position of the allocated beam information for the SN in the DCI 2_8 can refer to the options, as detailed herein.
[0113] In some implementations, to associate the time resource indication fields in DCI 2_8 with multiple SNs, the position of the time indication fields inside the DCI 2_8 payload is to be determined. In some configurations, the start position of the first time resource indication field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The bitwidth of time resource and the number of time indication fields in the DCI 2_8 can still follow the legacy specification. This indicates that the SN can obtain the time information from the DCI 2_8 payload in the same way as detailed herein.
[0114] In some configurations, the start position of the first time indication field and the end position of the last allocated time indication field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The existing RRC parameter numberOfFields can be reused to indicate the total number of time indication fields in the DCI 2_8. In some implementations, the parameter numberOfFields can be reinterpreted to indicate the number of time indication fields that are valid or are to be used for the SN in the DCI 2_8. Finally, the parameter numberOfFields can be omitted altogether.
[0115] In some configurations, the position of the first time resource indication field inside the DCI payload can be calculated by each SN implicitly. For example, when the legacy RRC parameter aperiodicBeamFieldWidth is used to configure the bitwidth of all beam index fields in the DCI 2_8, this can indicate that all SNs in the group have the same number of beams that can be used. In this case, since the number of beam index fields in the DCI 2_8 is equal to the number of time resource indication fields, the SN can determine the position of time indication fields inside the DCI payload.
[0116] In some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The start positions are consecutive, and the first start position corresponds to the start position of first time resource indication field, the second start position corresponds to the start position of second time resource indication field, and so on. In this case, the number of time resource indication fields in the DCI 2_8 can be implicitly obtained by the number of configured / provided start positions in the list. The existing RRC parameter numberOfFields can be used to indicate the total number of time indication fields in the DCI 2_8. In some implementations, the numberOfFields parameter can be reinterpreted to indicate the number of time indication fields that are valid or may be used for the SN in the DCI 2_8. In some implementations, the parameter numberOfFields can be omitted altogether. Moreover, since the time resource indication fields are consecutive, the bitwidth of time resource indication fields can also be known implicitly by the SN from the list of start positions. In some configurations, the time information is shared by all SNs in a group. In this case, the position of the time information inside the DCI 2_8 payload can be pre-defined and known to all SNs. This can indicate that the time resource indication fields are in a fixed position in DCI 2_8.
[0117] In some implementations, to associate the time resource indication fields in DCI 2_8 with multiple SNs, the bitwidth of the time resource indication fields can be determined. In some configurations, as detailed herein, the bitwidth of time indication fields can be determined by the number of entries of RRC configured / provided list ncr-AperiodicFwdConfig. Moreover, the bitwidth of the time resource indication fields should / may be the same for all SNs in the group. In some configurations, the bitwidth of time resource indication fields can be implicitly obtained by the SN. For example, when a list of start positions corresponding to the time resource indication fields is configured / provided to the SN by the BS, the SN can calculate the bitwidth of time resource indication fields by the bit difference of two consecutive start positions. This is because the time resource indication fields in DCI 2_8 are consecutive.
[0118] In some implementations, the total number of beam index fields in the DCI can be equal to the total number of beam index fields configured / provided for all SNs in the group. Furthermore, the total number of time resource indication fields and the total number of beam index fields can also be the same. In this case, when the DCI 2_8 is used to indicate the control information for a group of SNs, the number of allocated beam index fields for one SN is smaller than the time resource indication fields in the DCI 2_8. For a specific SN, if the SN is allocated with L1 beam index fields, and there are T1 time indication fields in the DCI 2_8 (where T1 > L1) , then the first L1 time resource indication fields are valid for the SN. The remaining T1-L1 time resource indication fields may be invalid for the specific SN.
[0119] In some implementations, to associate the time resource indication fields in DCI 2_8 with multiple SNs, the the size of DCI 2_8 can be determined. In some configurations, the size of DCI 2_8 can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some configurations, the size of DCI 2_8 can be equal to the existing DCI format that is monitored by the SN, such as DCI format 1_0. In some configurations, the bitwidth and the number of beam index fields for each SN in the group can be the same and pre-defined for each SN. Additionally, the bitwidth of time indication fields and the number of time indication fields can be known to the SN, as detailed herein. Once the number of SNs in a group is configured / provided for each SN, the size of DCI 2_8 can be implicitly calculated by the SN.
[0120] In some implementations, the DCI 2_8 can be reinterpreted to indicate the control information for a group of SNs. This can be done by re-interpreting the meaning of the fields in DCI 2_8. The timing information in the DCI 2_8 can be shared by a group of SNs. Additionally, each beam index field can be sequentially associated with a time resource indication field with a one-to-one mapping. Considering that DCI 2_8 can be used to indicate the control information for a group of SNs, a beam pattern list including one or more beam patterns can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each beam pattern in the list has a corresponding index, and each beam pattern can include one or more beam indexes. Each beam index in the beam pattern corresponds to the beam information configured / provided for a SN. In this case, the existing beam index field in the DCI 2_8 can be reinterpreted as the beam pattern index. When the SN receives the DCI 2_8, the SN can obtain / determine the beam pattern index. The SN can then obtain the configured / provided beam information for the SN from the configured / provided beam pattern list. In this case, the field of the DCI 2_8 can include a series of beam pattern indices (Beam pattern index 1, Beam pattern index 2, ..., Beam pattern index N) and time resource indications (Time resource indication 1, Time resource indication 2, ..., Time resource indication N) .
[0121] Referring to FIG. 7, depicted is the use of the beam pattern index and time resource indication field, indicating the control information for the group of SNs. As shown in FIG. 7, the DCI 2_8 can be used to indicate the control information for three SNs. The DCI 2_8 includes three beam fields and three time resource indication fields in this example. Each beam field is sequentially associated with a time resource indication field, such that beam field 1 is associated with time resource indication 1, beam field 2 is associated with time resource indication 2, and beam field 3 is associated with time resource indication 3. The beam field in the DCI 2_8 is used to indicate the beam pattern index. The beam pattern list is configured / provided to the SNs, and for each beam pattern, the first configured / provided beam index information is allocated for SN1, the second configured / provided beam index information is allocated for SN2, and the third configured / provided beam index information is allocated for SN3. Therefore, when SN1 obtains the beam pattern index 2 from the first beam pattern field, it can refer to the list and obtain that the beam information corresponding to time resource indication 1 is the beam index 1. Similarly, SN2 can obtain that the beam information corresponding to time resource indication 1 is the beam index 3, and SN3 can obtain that the beam information corresponding to time resource indication 1 is the beam index 2.
[0122] In some implementations, the beam index field in the DCI 2_8 can be re-interpreted as the beam pattern index. This requires that the beam pattern list be configured / provided to the SN. The beam pattern list can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or it can be configured / provided to the SN and BS via OAM. Each beam pattern in the list can have a corresponding beam pattern index. For each beam pattern, it includes one or more beam index information, where each beam index information is allocated for a SN respectively. The different beam patterns in the list should include the same number of beam index information fields. Since the beam pattern list includes the beam information for different SNs, the configured / provided beam pattern list should be the same for these SNs. Additionally, since the time indications in the DCI 2_8 are shared by these SNs, the RRC configured / provided list of time resources by ncr-AperiodicFwdConfig should be the same for all SNs in the group.
[0123] In some implementations, the beam index field in DCI 2_8 can be re-interpreted as the beam pattern index. It is because the bitwidth of time resource indication fields in the DCI 2_8 and the number of time indication fields can follow the current specification. Additionally, the total number of beam fields in DCI 2_8 is equal to the total number of time resource indication fields. In some implementations, as described herein, the RRC parameter aperiodicBeamFieldWidth can be used to configure the bitwidth of the beam index field. However, if the beam index field is re-interpreted / re-purposed as the beam pattern index, in some configurations, the current RRC parameter aperiodicBeamFieldWidth can be re-interpreted / re-purposed to configure the bitwidth of the beam pattern index field in the DCI 2_8. Similarly, in some configurations, a new higher layer parameter can be used to configure the bitwidth of the beam pattern index field in the DCI 2_8 to the SN by the BS.
[0124] In some implementations, as the beam index field in DCI 2_8 can be re-interpreted as the beam pattern index, the SN is to determine which beam information in the beam pattern is allocated for it. In some configurations, the BS can configure a logic index to the SN to indicate the location or the order of the beam information allocated for it in each beam pattern. For example, there are three SNs, and each beam pattern can include three beam information fields. The BS can configure the logic index 1 to the SN1, which means / indicates / informs that the first beam index information in each beam pattern is configured / provided for SN1. The BS can configure the logic index 2 to the SN2, which indicates that the second beam index information in each beam pattern is configured / provided for SN2. Similarly, the BS can configure the logic index 3 to the SN3 to indicate that the third beam index information in each beam pattern is configured / provided for SN3. In some configurations, the order or location of beam information allocated for each SN in the beam pattern can be pre-defined for each SN and the BS.
[0125] In some implementations, as the beam index field in DCI 2_8 can be re-interpreted as the beam pattern index, the SN is to determine the size of DCI 2_8. In some configurations, when the bitwidth and the number of time indication fields are known by the SN as legacy mechanisms and the bitwidth and number of beam fields can also be determined by the SN, the size of DCI 2_8 can be implicitly calculated by the SN. In some configurations, the size of DCI 2_8 can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some configurations, the size can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0.
[0126] In some embodiments, a new DCI signaling can be introduced to indicate the control information for a group of SNs. In some configurations, a new RNTI, e.g., SN-G-RNTI, can be defined to scramble the new group DCI signaling that is used to indicate the control information for a group of SNs. This new RNTI is configured / provided by the BS to the SN via at least one of RRC, MAC CE, or DCI signaling. Each SN can be configured / provided with one or a plurality of RNTI values for this new type of RNTI. In this case, it indicates that the SN can be configured / provided into many groups. Each group has a different SN-G-RNTI value, and the SNs in a same group are configured / provided with the same SN-G-RNTI value.
[0127] In some configurations, the ncr-RNTI can be reused with enhancements. To enable scrambling of the new DCI signaling, the SN can be configured / provided with one or more plurality of RNTI values for ncr-RNTI. For example, the format “ncr-RNTI-r18” can be defined as SEQUENCE (SIZE (1.. maxNrofNCRRNTIs) ) OF RNTI-Value, where “maxNrofNCRRNTIs” represents the maximum number of ncr-RNTI values that can be configured / provided for a given SN. This value can either be predefined or configured / provided by the BS. The utilization of different RNTI values provides the ability to scramble both DCI 2_8 and the new DCI signaling. For example, a pre-defined rule can be defined where the first RNTI value of ncr-RNTI is used to scramble DCI 2_8 for unicast signaling, while the second and subsequent RNTI values of ncr-RNTI are used to scramble the new DCI signaling for group signaling for a group of SNs. Similarly, if only one RNTI value is configured / provided for ncr-RNTI, this specific RNTI value can be used to scramble both DCI formats. In some configurations, a pre-defined rule can be defined for scrambling DCI signaling. For example, the last configured / provided RNTI value of ncr-RNTI can be used to scramble the DCI 2_8 for unicast signaling, while the other remaining RNTI value of ncr-RNTI can be used to scramble the new DCI signaling for group signaling for a group of SNs. If only one RNTI value is configured / provided for the ncr-RNTI, then this RNTI value can be used to scramble both DCI formats. In some configurations, the ncr-RNTI can be reused. For example, in this case, the ncr-RNTI can be used to scramble the current DCI 2_8 and the new DCI signaling format.
[0128] In the context of deploying a new / specific DCI signaling mechanism to efficiently convey control information to a group of SNs, various crucial aspects of control information and their respective formats are to be thoughtfully considered. Firstly, the beam information is used to indicate the beam for the SN. The format of the beam information can be the logic beam index, where each beam index corresponds to a physical beam of the SN, or corresponds to a specific codebook that can be used to configure the SN. In this way, the related codebook configuration should be known by the SN and BS. Secondly, the time information is used to indicate the time resource associated with the indicated beam information. The BS can configure a list of time resources for each SN via the RRC signaling. Each time resource is defined by {Starting slot defined as the slot offset, starting symbol defined by symbol offset within the slot, duration defined by the number of symbols} . In this way, the time information field in the new DCI signaling is used to indicate a time resource configured / provided in the RRC signaling. Thirdly, the frequency information is used to indicate the frequency resource of the SN. The format of the frequency information can be the logic index, and the logic index can be interpreted as one of a carrier index, a passband index, a Bandwidth Part (BWP) index, or a cell index. Furthermore, the format can consider power information, panel information (if the SNs within the group comprise multiple panels) , and polarization information.
[0129] In the context of enabling the new / specific DCI signaling to accommodate control information for multiple SNs, the information conveyed by the new DCI signaling can include a series of block numbers, denoted as block number 1, block number 2, block number 3, and so forth, up to block number N. Here, a “block” represents a collection of fields or a group of fields containing control information used for a specific SN. This definition is consistently applied throughout various scenarios. Furthermore, each block may include:
[0130] Beam indication 1 through to Beam indication L;
[0131] Time indication 1 through to Time indication T;
[0132] Frequency indication 1 through to Frequency indication F;
[0133] Power indication 1 through to Power indication G;
[0134] Panel indication 1 through to Panel indication H; and
[0135] Polarization indication 1 through to Polarization indication P.
[0136] In some implementations, the SN can determine which block is configured / provided for it when receiving the new DCI. In some configurations, the new DCI signaling includes multiple blocks that are used for different SNs. The start position of the block that is allocated for a specific SN is configured / provided to the SN by the BS via the RRC, MAC CE, or DCI signaling. This allows / enables the SN to know / determine the start position of the block that is configured / provided for it. After receiving the new DCI, the SN can then use the start position to determine which block is configured / provided for it. The bitwidth and number of each field can also be configured / provided and known by the SN. This allows the SN to obtain / determine the control information from the new group DCI signaling. In some configurations, the start position and end position of the block that is allocated for a specific SN in the new DCI format payload should be configured / provided to the SN by the BS via the RRC, MAC CE, or DCI signaling.
[0137] In some implementations, the SN can determine the number of values L, T, F, G, H, and P of each block and the corresponding bitwidths of field. If the block includes the beam indication field, the bitwidth of the beam indication field can be a fixed value that is known by the SN and BS or a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. The number of beam indication fields (L) can be defined through several alternative approaches. In some configurations, L is a fixed value that can be known by the SN and BS. L can be the same for all SNs in a same group, and in some embodiments, L can be different for SNs in a same group. In some configurations, L can be configured / provided to each SN of the group by the BS via at least one of RRC, MAC CE, or DCI signaling. In this way, the block configured / provided to the different SN of the group can have the different number of beam indication fields. In some configurations, the number of beam indication fields L of each block can be determined and equal to the number of time resource indication fields T of the same block. In this case, the beam indication fields and the time resource indication fields of the block can be sequentially associated with one-to-one mapping. In some configurations, L is zero, which means / indicates / informs that the block of new DCI signaling can not include the beam indication field. In this case, the BS or the OAM can pre-configure a fixed beam pattern that can be used by the SN. For example, there are three SNs (e.g., SN1, SN2, SN3) in the group, and for SN1, the BS can pre-configure a fixed beam pattern {beam index1, beam index 2, beam index3} that can be used by the SN1. In this way, the block that is configured / provided for the SN1 of the new DCI signaling includes the time indication, then the SN can use the indicated time resource information and the pre-configured / provided beam information to operate. In some configurations, L can be equal to 1, which means / indicates / informs that common beam information can be used for all time information indicated in the corresponding block.
[0138] In some implementations, if the block includes the time resource indication field, the bitwidth of time resource indication field can be determined by the number of entries of the RRC list of time resource that is configured / provided for the corresponding SN. The number of time resource indication fields (T) can be determined through several alternative approaches. In some configurations, T can be a fixed value and can be known by the SN and BS. T can be the same for all SNs in a same group, and in some embodiments, T can be different for SNs in a same group. In some configurations, T can be configured / provided to each SN of the group by the BS via at least one of RRC, MAC CE or DCI signaling. In this way, the block configured / provided to the different SN of the group can have a different number of time indication fields. In some configurations, the number of time indication fields T of each block can be determined and equal to the number of beam indication fields L of the same block. In this case, the beam indication fields and the time indication fields of the block can be sequentially associated with one-to-one mapping. In some configurations, T can be equal to 1, which means / indicates / informs that a common time information can be used for all beam information indicated in the corresponding block.
[0139] In some implementations, if the block includes the frequency indication field, the bitwidth of frequency indication field can be a fixed value that is known by the SN and BS, or can be a configurable value that is configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number of frequency indication fields (F) can be determined through several alternative approaches. In some configurations, F can be equal to L (L ≠ 0) , in which case a 1-to-1 mapping can be used to associate the indicated beam information and the frequency resource. In some configurations, F can be equal to T (T ≠ 0) , in which case a 1-to-1 mapping can be used to associate the indicated time resource and the frequency resource. In some configurations, F can be equal to 1, which means / indicates / informs that a common frequency bandwidth can be used for the beam and / or time information indicated in the corresponding block. In some configurations, F can be equal to 0, which means / indicates / informs that block does not include the frequency information. The frequency indication can be implicitly determined by BS / OAM with a fixed supported or fixed configured / provided frequency resource, e.g., the system bandwidth. In this case, the bitwidth of this field is 0.
[0140] In some implementations, if the block includes the power indication field, the bitwidth of power indication field can be a fixed value that is known by the SN and BS, or can be a configurable value that is configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number of power indication fields (G) and their bitwidth can be determined through several alternative approaches. In some configurations, G can be equal to L (L ≠ 0) , in which case a 1-to-1 mapping can be used to associate the beam and the power information. In some configurations, G can be equal to T (T ≠ 0) , in which case a 1-to-1 mapping can be used to associate the time and the power information. In some configurations, G can be equal to 1, which means / indicates / informs that the power information can be common for the SN’s forwarding operation. In some configurations, G can be equal to 0, which means / indicates / informs that the power indication is not included in the new DCI signaling.
[0141] In some implementations, if the block includes the panel indication field, the bitwidth of panel indication field can be a fixed value that is known by the SN and BS, or can be a configurable value that is configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number of panel indication fields (H) and their bitwidth can be determined through several alternative approaches. In some configurations, H can be equal to L (L ≠ 0) , in which case a 1-to-1 mapping can be used to associate the beam and the panel information. In some configurations, H can be equal to T (T ≠ 0) , in which case a 1-to-1 mapping can be used to associate the time and the panel information. In some configurations, H can be equal to 1, which means / indicates / informs that the panel information can be common for the SN’s forwarding operation. In some configurations, H can be equal to 0, which means / indicates / informs that the panel indication is not included in the new DCI signaling.
[0142] In some implementations, if the block includes the polarization indication field, the bitwidth of polarization indication field can be a fixed value that is known by the SN and BS, or can be a configurable value that is configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number of polarization indication fields (P) and their bitwidth can be determined through several alternative approaches. In some configurations, P can be equal to L (L ≠ 0) , in which case a 1-to-1 mapping can be used to associate the beam and the polarization information. In some configurations, P can be equal to T (T ≠ 0) , in which case a 1-to-1 mapping can be used to associate the time and the polarization information. In some configurations, P can be equal to 1, which means / indicates / informs that the polarization information can be common for the SN’s forwarding operation. In some configurations, P can be equal to 0, which means / indicates / informs that the polarization indication is not included in the new DCI signaling.
[0143] In some implementations, SN can determine the actual / valid number of beam indication / time indication fields in each block. In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. The invalid index can be pre-defined for the SN and BS or configured / provided for the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The invalid beam index / time index can be common for all SNs in the group, or different for each SN. In this way, when the SN determines that the index of the corresponding field is the pre-defined invalid index, SN can determine that this beam indication field and associated time indication field are invalid. In some configurations, an additional field can be added in the corresponding block to indicate the valid number of time indication fields or the valid number of beam indication fields. In some configurations, the invalid beam indication / time indication can be realized through implementation. For example, when configuring the RRC list of time resources, some time resources can be configured / provided with invalid time information, e.g., the duration of a time resource is 0. Thus, when the SN finds / determines that the time indication field refers to invalid time resource information, SN can determine that the corresponding time indication field and the associated beam information field are invalid.
[0144] In some implementations, SN can determine the size of the new DCI signaling. In some configurations, the BS can explicitly configure the size of the new DCI signaling to the SN via RRC, MAC CE, or DCI signaling. In some configurations, the size can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0. In some configurations, when the number of each type of field and the bitwidth of each type of field are the same for different blocks, the SN can implicitly know / determine the bitwidth of each block. Moreover, when the SN knows the number of blocks in the new DCI signaling or the number of SNs in a group, the SN can implicitly calculate the size of the new DCI signaling. There may be no need to explicitly configure the size of new DCI signaling. For example, there can be three SNs (SN1, SN2, and SN3) used to serve a UE. Moreover, as detailed herein, the new DCI signaling can include three blocks. Each block contains a beam indication field and a time indication field. For SN1, the BS can configure the number of time indication fields to be 2 via RRC signaling. The number of beam indication fields is equal to the number of time indication fields. The BS also configures a list of 64 time resources to SN1 via RRC signaling. Similalry, for SN2, the BS can configure the number of time indication fields to be 2 via RRC signaling. The number of beam indication fields is equal to the number of time indication fields. The BS also configures a list of 32 time resources to SN2 via RRC signaling. For SN3, the BS can configure the number of time indication fields to be 1 via RRC signaling. The number of beam indication fields is equal to the number of time indication fields. The BS also configures a list of 16 time resources to SN3 via RRC signaling.
[0145] Furthermore, since the new DCI signaling includes the control information that can be used by the three SNs, the BS is to indicate to each SN the start bit position of its corresponding block inside the new DCI payload. For example, for SN1, the BS can configure the start position to be 1, which means / indicates / informs that the first bit of the new DCI payload is the start position of the block number 1. For SN2, the BS can configure the start position to be 21, while for SN3, the BS can configure the start position to be 37. In this manner, after receiving the DCI signaling, each SN can correctly determine its own control information from the new DCI signaling.
[0146] In some implementations, the new DCI signaling can transmit information in the form of multiple blocks, denoted as block number 1, block number 2, block number 3, and so on up to block number N. When the SN is configured / provided to monitor this new DCI format, one or more blocks are configured / provided to the SN. Furthermore, each block is defined with at least one of the following fields: Beam indication 1, Time indication 1, Frequency indication 1, Polarization indication 1, Power indication 1, and Panel indication 1.
[0147] In some implementations, SN can determine the start position of a block and the number of blocks for a SN. To determine the start position of allocated blocks for the SN, in some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each start position corresponds to a start position of a block inside the new DCI format payload that is configured / provided for the SN. If the configured / provided list has only one start position, it indicates that only one block is configured / provided for the SN in the new DCI signaling. For example, a list of start positions can be configured / provided to the SN by the BS via the MAC CE signaling. In this case, the number of blocks allocated for the SN can be implicitly obtained / determined by the SN from the entries of the list. In some configurations, the BS can configure the start position of the first block inside the new DCI format payload to an SN via at least one of RRC, MAC CE, or DCI signaling. The BS can also configure the number of blocks to the SN via at least one of RRC, MAC CE, or DCI signaling. In this option, the multiple blocks configured / provided to the SN are consecutive. In some implementations, considering the case that each SN can be configured / provided with one or more consecutively allocated blocks, the BS can configure the start position of the first allocated block and the end position of the last allocated block to the SN via at least one of RRC, MAC CE, or DCI signaling. In this case, the number of blocks allocated for the SN can be implicitly determined by the SN when the bitwidth of each field in the block is configured / provided / known to the SN.
[0148] Furthermore, to determine the number of allocated blocks for an SN, in some configurations, the BS can configure the number of blocks to the corresponding SN via at least one of RRC, MAC CE, or DCI signaling. Similarly, in some configurations, the number of blocks allocated for the SN can be implicitly obtained by the SN. For example, when a list of start positions is configured / provided to the SN by the BS, the number of blocks allocated for the SN can be implicitly obtained by the SN from the entries of the list.
[0149] In some implementations, the SN can determine the bitwidth of each field of the block. The bitwidth of the time resource indication field in each block can determined by the number of entries in the RRC list of time resources that is configured / provided for the corresponding SN. The bitwidths of other fields in the block can be either a fixed value that is known to the SN and BS, or they can be configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling.
[0150] In some implementations, the SN can determine the valid beam or time indications in the allocated blocks. In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. This invalid index can be pre-defined to the SN and BS, or it can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The invalid beam index / time index can be common for all SNs in the group, or it can be different for each SN. In this way, when the SN determines that the index of the corresponding field is the pre-defined invalid index, the SN can determine that the beam indication field and the associated time indication field are invalid.
[0151] In some configurations, the invalid beam indication / time indication can be realized through implementation. For example, when configuring the RRC list of time resources, some time resources can be configured / provided with invalid time information, such as a duration of 0. In this case, when the SN determines that the time indication field refers to an invalid time resource, the SN can determine that the corresponding time indication field and the associated beam information field are invalid. Another example is that, for each SN, one or more allocated blocks can be configured / provided with the same beam information and / or the same time information. For example, the new DCI signaling includes the control information for 3 SNs, and SN1 is allocated with blocks 1, 2, and 3. However, the BS may only want to configure 2 beam information and associated time information for SN1. In this case, blocks 2 and 3 can be configured / provided with the same beam information and the same time information.
[0152] In some implementations, the SN can determine the size of the new DCI signaling. In some configurations, the size of new DCI signaling can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Moreover, in some configurations, the size can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0.
[0153] In some implementations, the new DCI signaling is used to convey control information for the operation of a group of SNs. Given that different SNs within the group may be located in distinct positions and possess varying capabilities, the control information transmitted may differ for each SN. However, as the group of SNs collectively participate in forwarding signals from the BS to a UE or vice versa, there can be cases where the time resource information required for the forwarding operation of different SNs can be the same. The information transmitted by the new DCI signaling may include time indications, such as time indication 1, time indication 2, and so on up to time indication T, as well as blocks numbered from 1 to N. Each SN is configured / provided with one block, and these blocks contain the necessary control information with fields such as Beam indication 1 to L, Frequency indication 1 to F, Power indication 1 to G, Panel indication 1 to H, and Polarization indication 1 to P. Since the time information in the new DCI signaling is the same for a group of SNs, the RRC list that the BS configures for each SN in the group should be the same. The mapping relationship between the time indication fields and the respective types of fields in a block configured / provided for a SN can be one-to-one mapping or one-to-more mapping. The mapping relationship between the different types of respective fields in a block can also be one-to-one mapping or one-to-more mapping.
[0154] In some implementations, the association relationship between the time resource indication fields (T) and beam indication fields (L) in each block may vary. As the time resource indication fields are common for all SNs in the group, the number of time resource indication fields can differ from the number of beam indication fields (L) in each block. When T is greater than L (T > L) , several configurations can be considered to determine the associated time resource indication of the indicated beam information in the block.
[0155] For example, in some configurations, the “bitmap of time indication” field can be added to each block to indicate the associated time information for the corresponding beam indication. The bitwidth of the bitmap of time indication field is equal to T. The first indicated beam information is associated with the time indication i, where i is the index of the codepoint with the first value 1 in the bitmap. The second indicated beam information is associated with the time indication j, where j is the index of the codepoint with the second value 1 in the bitmap, and so on. The number of value 1 in the bitmap should be equal to the number of indicated beam information fields of block. For example, if T = 5, and there are three beam indications in the block number 1, and the bitmap of time indication field is 10101, then the first beam indication of block number 1 is associated with the time indication 1, the second beam indication of block number 1 is associated with the time indication 3, and the third beam indication of block number 1 is associated with the time indication 5.
[0156] In some configurations, for each SN, the indicated beam information can be sequentially associated with the time indication in a one-to-one mapping. The remaining time indications can be treated as invalid for the SN. For example, if T = 5, and there are three beam indications in the block number 1, then these three beam indications can be sequentially associated with time indication 1, time indication 2, time indication 3, respectively. For the case of T = L, it means / indicates / informs that for the SN, the time indications can be sequentially associated with the indicated beam indications in a one-to-one mapping. In the case of T < L, the associated time indication of the indicated beam information in the block can be determined using various configurations. In some configurations, for each SN, the indicated beam information can be sequentially associated with the time indication in a one-to-one mapping. The remaining beam indications can be treated as invalid for the SN. For example, if T = 5 and there are six beam indications in block number 1, then the first five beam indications are sequentially associated with the five time indications, respectively.
[0157] In some implementations, the SN can determine the number of time resource indication fields in the new DCI signaling and its corresponding bitwidth of the time resource indication fields. The number of time resource indication fields can be determined using alternative configurations. For example, in some configurations, T can be a fixed value known by all the SN in the group and BS. In some configurations, T can be configured / provided to each SN of the group by the BS via at least one of RRC, MAC CE, or DCI signaling. The configured / provided value T is the same for all SNs. In some configurations, T can be implicitly obtained by the SN. For example, in an overview, when the BS configures the start position of the first time indication and the end position of the last time indication inside the DCI payload to the SN via at least one of RRC, MAC CE, or DCI signaling, and the SN knows the bitwidth of each time indication field from the configured / provided RRC list of time resources, the number of time indication fields in the DCI can be implicitly calculated by the SN.
[0158] In some implementations, the bitwidth of the time resource indication field can be determined by the number of entries in the RRC list of time resources. In other configurations, the bitwidth of the time resource indication field can be implicitly obtained by the SN. For example, if a list of start positions corresponding to the time indication fields is configured / provided to the SN by the BS, and if the time indication fields are consecutive in the new DCI signaling, the SN can implicitly know / determine the bitwidth of the time indication fields from the difference in bits between two consecutive start positions.
[0159] In some implementations, the SN can determine the position of time indication fields in the new DCI signaling payload. For example, in some configurations, the BS can configure the start position of the first time indication inside the DCI payload to the SN via at least one of RRC, MAC CE, or DCI signaling. In this way, since the number of time indication fields and the bitwidth can be known by the SN as described herein, the SN can obtain the time information from the new DCI signaling payload.
[0160] In some configurations, the BS can configure the start position of the first time indication and the end position of the last time indication inside the DCI payload to the SN via at least one of RRC, MAC CE, or DCI signaling. This requires that the time indication fields in the DCI signaling are consecutive. Since the bitwidth can be known by the SN from the configured / provided RRC list of time resources, and the bitwidth of each time indication field is the same, the number of time indication fields in the DCI can be implicitly calculated by the SN.
[0161] In some configurations, a pre-defined start position of the first time indications inside the DCI payload can be defined for the SNs in the group and BS. This may require that the time indication fields in the DCI signaling are consecutive. For example, the first bit of the DCI payload can be the start position of the first time indications. Since the bitwidth of time indication fields can be known by the SN from the configured / provided RRC list of time resources, and the number of time indication fields can be known by the SN, the SN can implicitly obtain the time information from the new DCI signaling payload.
[0162] In some configurations, the BS can configure a list of start positions to the SN via at least one of RRC, MAC CE, or DCI signaling. Each start position in the list represents the start position of the time indication inside the DCI payload. The first start position in the list represents the start position of the first time indication inside the DCI payload, the second start position in the list represents the start position of the second time indication inside the DCI payload, and so on. In this case, the number of time indication fields and the bitwidth of time indication fields can be implicitly known by the SN. Similarly, as detailed herein, in some implementations, the SN can determine the number of values L, F, G, H, P and their corresponding bitwidth.
[0163] In some implementations, the SN can determine the position of allocated block inside the DCI payload. For example, in some configurations, the BS can configure the start position of the block that is allocated for the SN inside the new DCI format payload to the corresponding SN via RRC, MAC CE, or DCI signaling. In this way, after receiving the new DCI, the SN can implicitly know / determine the start position of the block that is configured / provided for it. Since the bitwidth and number of each field in the block can also be configured / provided and known by the SN, the SN can then obtain the control information from this new group DCI signaling. In some configurations, the BS can configure the start position and the end position of the block that is allocated for the SN inside the new DCI format payload to the corresponding SN via RRC, MAC CE, or DCI signaling. This allows / enables the SN to determine the position of the allocated block inside the DCI payload.
[0164] In some implementations, the SN can determine the size of the new DCI signaling. For example, in some configurations, the size of new DCI signaling can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Furthermore, the size can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0.
[0165] In some implementations, the SN can determine the actual / valid number of beam indications. In some configurations, a new field can be added to the block to indicate the number of valid beam indications or number of valid time indications. The actual number of beam indications can be implemented in several ways. For example, a bitmap field can be introduced to the block to indicate the actual / valid number of beam indications. This field can also be used to indicate the valid beam indications and time indications. For example, if L = 4, T = 5, and there are four beam indications in block number 1, and the bitmap of time indication is 10101, this means / indicates / informs that only the first three beam indications have corresponding time indications. The fourth beam indication in the block is invalid because it does not have an associated time indication. Another way to implement the actual number of beam indications is to configure the RRC list of time resources with invalid time information. For example, the duration of a time resource can be set to 0. If the SN determines that the time indication field refers to an invalid time resource, the SN can determine that the corresponding time indication field and the associated beam information field in the block are invalid.
[0166] In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. This invalid index can be pre-defined for the SN and BS, or it can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The invalid beam index / time index can be common for all SNs in the group, or it can be different for each SN.In this way, when the SN determines that the index of the corresponding field is the pre-defined invalid index, the SN can determine that this beam indication field and associated time indication field are invalid.
[0167] In some implementations, the new DCI signaling can use the same time resource information for all SNs in the group, resulting in the information transmitted by the new DCI signaling to include a series of time indications (time indication 1, time indication 2, ..., time indication T) and a list of block numbers (block number 1, block number 2, block number 3, ..., block number N) . Each SN within the group can be configured / provided with one or more blocks, and each block is defined with at least one of the following fields: Beam indication 1, Frequency indication 1, Polarization indication 1, Power indication 1, and Panel indication 1. The mapping relationship between the plurality of time indication fields and the respective one or more blocks configured / provided for an SN can be a one-to-one mapping or a one-to-more mapping, depending on the specific configuration.
[0168] In some implementations, the association relationship between the time indications and beam indications in all allocated blocks for an SN can vary. As detailed herein, the total number of time resource indication fields (T) may differ from the number of beam indication fields (L) in the allocated blocks for the SN. For each SN, the indicated beam information is sequentially associated with the time indication with a one-to-one mapping. The remaining time indications or remaining beam indications are treated as invalid for the SN. For example, if T = 5 and there are three beam indications in the three blocks allocated for SN1, then the first three beam indications are sequentially associated with the time indications 1, 2, and 3, respectively. The time indications 4 and 5 are invalid for SN1.
[0169] In some implementations, the SN can determine the number of time resource indication fields and their corresponding bitwidth in the new DCI signaling, as well as the position of the time resource indication fields in the DCI signaling payload, the start position of a block and the number of blocks allocated for a SN, and the size of the new DCI signaling, as detailed herein.
[0170] In some implementations, the SN can determine the actual number of beam indications and / or the actual number of time resource indications. For example, in some configurations, the RRC list of time resources can be configured / provided with invalid time information, such as a time resource with a duration of 0. If the SN finds / determines that a time resource indication field refers to an invalid time resource, the SN can determine that the corresponding time resource indication field and the associated beam information field in the block are invalid. In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. This invalid index can be pre-defined for the SN and BS, or it can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The invalid beam index / time index can be common for all SNs in the group, or it can be different for each SN. In this way, when the SN determines that the index of the corresponding field is the pre-defined invalid index, the SN can determine that this beam indication field and associated time indication field are invalid.
[0171] In some implementations, the new DCI signaling can transmit information that includes various fields, such as beam indications (Beam indication 1 to Beam indication Ltotal) , time indications (Time indication 1 to Time indication Ttotal) , frequency indications (Frequency indication 1 to Frequency indication Ftotal) , power indications (Power indication 1 to Power indication Gtotal) , panel indications (Panel indication 1 to Panel indication Htotal) , and polarization indications (Polarization indication 1 to Polarization indication Ptotal) . Each SN is configured / provided with one or more corresponding fields of these types, and the allocation of fields for a SN can be consecutive or non-consecutive, as detailed herein. Additionally, the relationship between different types of fields can be either one-to-one mapping or one-to-more mapping.
[0172] Referring now to FIG. 8, depicted is the field format of the new DCI signaling. As shown, a group of three SNs is configured / provided with six beam index fields, six time resource indication fields, and three frequency information fields. The new DCI signaling can allocate the following fields to the group of SNs. For SN1, it can be allocated two beam index fields, two time resource indication fields, and one frequency information field. Additionally, beam index 1 is associated with time indication 1, beam index 2 is associated with time indication 2, and frequency indication 1 is common for all beam and time information allocated to SN1. Similarly, for SN2, it can be allocated one beam index field, one time resource indication field, and one frequency information field. Additionally, Beam index 3 is associated with time indication 3, and frequency indication 2 is common for all beam and time information allocated to SN2. Furthermore, for SN3, it can be allocated three beam index fields, three time indication fields, and one frequency information field. Additionally, Beam index 4 is associated with time indication 4, beam index 5 is associated with time indication 5, beam index 6 is associated with time indication 6, and frequency indication 3 is common for all beam and time information allocated to SN3.
[0173] To configure each SN with one or more corresponding fields in the new DCI signaling, the SN is to determine the number of allocated fields and their respective bitwidths. In particular, the number of beam indication fields (L) allocated for a SN can be determined through various configurations. For example, in some configurations, L can be a fixed value known by both the SN and the BS, where L can be the same for all SNs within the group or may vary for different SNs in the group. In some configurations, L can be configured / provided to each SN in the group by the BS via at least one of RRC, MAC CE, or DCI signaling. This allows / enables different SNs in the group to have different numbers of beam indication fields. In some configurations, the number of beam indication fields allocated for a SN can be determined and equal to the number of time indication fields allocated for the SN. In this case, the beam indication fields and the time indication fields of the block can be sequentially associated with a one-to-one mapping. In some configurations, L can be zero, which means / indicates / informs that the new DCI signaling does not include the beam indication field that is allocated for the SN. In this case, the BS or OAM functionality can pre-configure a fixed beam pattern that can be used by the SN. For example, there are 3 SNs (e.g., SN1, SN2, SN3) in the group, and for SN1, the BS can pre-configure a fixed beam pattern {beam index1, beam index 2, beam index3} that can be used by the SN1. In this way, the new DCI signaling that is configured / provided for SN1 includes the time indication. The SN can then use the indicated time resource information and the pre-configured / provided beam information to operate. In some configurations, L can be 1, which means / indicates / informs that a common beam information is used for all time information that is indicated and allocated for the SN in the new DCI signaling. In some configurations, L can be implicitly obtained by the SN. For example, if a list of start positions of beam indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated beam fields for the SN can be implicitly obtained from the number of start positions in the list.
[0174] In some implementations, the bitwidth of beam indication field allocated for the SN in the new DCI signaling can be determined through various configurations. For example, in some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions of beam indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of the allocated beam fields for the SN can be implicitly obtained from the number of start positions in the list.
[0175] In some implementations, the number of time resource indication fields (T) in the new DCI signaling can be determined through various configurations. In some configurations, T can be a fixed value that is known by the SN and BS. T can be the same for all SNs in a group, or it can be different for different SNs in a group. In some configurations, T can be configured / provided to each SN in the group by the BS via at least one of RRC, MAC CE, or DCI signaling. This allows different SNs in the group to have different numbers of time indication fields. In some configurations, the number of time indication fields allocated for the SN in the new DCI signaling can be determined and equal to the number of beam indication fields allocated for the SN. In this case, the beam indication fields and the time indication fields allocated for the SN in the new DCI signaling are sequentially associated with a one-to-one mapping. In some configurations, T can be 1, which means / indicates / informs that a common time information is used for all beam information that is allocated for the SN in the new DCI signaling. In some configurations, T can be implicitly obtained by the SN. For example, if a list of start positions of time indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as described in aspect 2 of case 2.5, the number of allocated time fields for the SN can be implicitly obtained from the number of start positions in the list.
[0176] In some implementations, if the new DCI signaling includes the time indication field allocated for a SN, the bitwidth of the allocated time indication field can be determined through various configurations. In some configurations, the bitwidth of the time indication fields allocated for the SN can be determined by the number of entries in the RRC list of time resources that is configured / provided for the corresponding SN. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions of time resource indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of the allocated time fields for the SN can be implicitly obtained from the number of start positions in the list.
[0177] In some implementations, the number of frequency indication fields (F) in the new DCI signaling can be determined through various configurations. In some configurations, F = L (L ≠ 0) , a one-to-one mapping is used to associate the indicated beam information and the frequency resource that is allocated for the SN. In some configurations, F = T (T ≠ 0) , a one-to-one mapping is used to associate the indicated time resource and the frequency resource that is allocated for the SN. In some configurations, F = 1, which means / indicates / informs that a common frequency bandwidth is used for the beam and / or time information that is allocated for the SN in the new DCI. In some configurations, F = 0, which means / indicates that the new DCI signaling does not include the frequency information that is allocated for the SN. The frequency indication can be implicitly determined by the BS / OAM with a fixed supported or fixed configured / provided frequency resource, such as the system bandwidth. In this case, the bitwidth of this field is 0. In some configurations, F can be implicitly obtained by the SN. For example, if a list of start positions of frequency indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated frequency fields for the SN can be implicitly obtained from the number of start positions in the list.
[0178] In some implementations, the bitwidth of the frequency indication field allocated for the SN in the DCI signaling can have several configurations. For example, in some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions of frequency indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herien, the bitwidth of the allocated frequency fields for the SN can be implicitly obtained from the number of start positions in the list.
[0179] In some implementations, the number of power indication fields (G) and its corresponding bitwidth allocated for a SN in the new DCI signaling can have several configurations. In some configurations, G = L (L ≠ 0) , a one-to-one mapping can be used to associate the beam and the power information that is allocated for the SN. In some configurations, G = T (T ≠ 0) , a one-to-one mapping can be used to associate the time and the power information that is allocated for the SN. In some configurations, G = 1, which means / indicates / informs that the power information is common for the beam and / or time information that is allocated for the SN in the new DCI. In some configurations, G = 0, which means / indicates / informs that the new DCI signaling does not include the power information allocated for the SN. In some configurations, G can be implicitly obtained by the SN. For example, if a list of start positions of power indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated power fields for the SN can be implicitly obtained from the number of start positions in the list.
[0180] In some implementations, the bitwidth of the power indication field allocated for the SN in the new DCI signaling can be configured / provided in a variety of ways. In some configurations, the bitwidth of the power indication field can be a fixed value that is known by both the SN and the BS. In some configurations, the bitwidth of the power indication field can be configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth of the power indication field can be implicitly obtained by the SN. For example, when a list of start positions of power indication fields that are allocated to the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of the allocated power fields for the SN can be implicitly obtained.
[0181] In some implementations, the number of panel indication fields (H) and its corresponding bitwidth allocated for a SN in the new DCI signaling can be configured / provided in a variety of ways. For example, in some configurations, H = L (L ≠ 0) , a one-to-one mapping can be used to associate the beam and the panel information that is allocated for the SN. In some configurations, H = T (T ≠ 0) , a one-to-one mapping can be used to associate the time and the panel information that is allocated for the SN. In some configurations, H = 1, which means / indicates / informs that the panel information is common for the beam and / or time information that is allocated for the SN in the new DCI. In some configurations, H = 0, which means / indicates / informs that the new DCI signaling does not include the panel information allocated for the SN. In some configurations, H can be implicitly obtained by the SN. For example, if a list of start positions of panel indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated panel fields for the SN can be implicitly obtained from the number of start positions in the list.
[0182] In some implementations, the bitwidth of the panel indication field allocated for the SN in the new DCI signaling can have several configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions of panel indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of the allocated panel fields for the SN can be implicitly obtained from the number of start positions in the list.
[0183] In some implementations, the number of polarization indication fields (P) and its corresponding bitwidth allocated for a SN in the new DCI signaling can have several configurations. For example, in some configurations, P = L (L ≠ 0) , a one-to-one mapping can be used to associate the beam and the polarization information that is allocated for the SN. In some configurations, P = T (T ≠ 0) , a one-to-one mapping can be used to associate the time and the polarization information that is allocated for the SN. In some configurations, P = 1, which means / indicates / informs that the polarization information is common for the beam and / or time information that is allocated for the SN in the new DCI. In some configurations, P = 0, which means / indicates / informs that the new DCI signaling does not include the polarization information allocated for the SN. In some configurations, P can be implicitly obtained by the SN. For example, if a list of start positions of polarization indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated polarization fields for the SN can be implicitly obtained from the number of start positions in the list.
[0184] In some implementations, the bitwidth of the polarization indication field allocated for the SN in the new DCI signaling can have several configurations. For example, in some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions of polarization indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of the allocated polarization fields for the SN can be implicitly obtained from the number of start positions in the list.
[0185] In some implementations, to configure each SN with one or more corresponding fields, the SN is to determine the position of the allocated fields inside the DCI payload. In particular, for each type of field, the SN can determine the position of the corresponding allocated fields inside the DCI payload through various configurations. For example, in some configurations, the start position of the first allocated field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, for each type of field, when the corresponding allocated fields for each SN are consecutive, the start position of the first allocated field inside the DCI payload can be configured / provided to the SN by the BS. Since the number of corresponding allocated fields and the bitwidth of corresponding fields can be determined by the SN, the SN can determine the corresponding allocated information from the new DCI signaling.
[0186] In some configurations, the start position of the first allocated field and the end position of the last allocated field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, for each type of field, when the corresponding allocated fields for each SN are consecutive, the start position of the first allocated field and the end position of the last allocated field inside the DCI payload can be configured / provided to the SN by the BS. In this case, there msy be no need to configure both the number of fields and the bitwidth of the corresponding field to the SN, since the SN can implicitly obtain these values.
[0187] In some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each start position in the list corresponds to the start position of an allocated field inside the DCI payload. For example, for each type of field, when the corresponding allocated fields for each SN are non-consecutive, a list of start positions can be configured / provided to the SN by the BS. In this case, the number of fields allocated for the SN can be implicitly obtained by the number of configured / provided start positions in the list. Since for each type of field, the allocated fields are consecutively, the bitwidth can also be implicitly obtained by the SN.
[0188] In some implementations, the SN can determine the size of the new DCI signaling. The size of the new DCI signaling can be determined in a variety of ways. In some configurations, the size of the new DCI signaling can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some configurations, the size of the new DCI signaling can be equal to the existing DCI format that is monitored by the SN, such as DCI format 1.0. In some configurations, the size of the DCI can be implicitly calculated if the number of fields and their bitwidth are the same and known for all SNs in the group.
[0189] In some implementations, the SN can determine the actual number of beam indications and / or the actual number of time indications for each SN. This can be determined in a variety of ways.
[0190] In some implementations, the SN can determine the actual number of beam indications and / or the actual number of time resource indications for each SN. This can be determined in a variety of ways. For example, in some configurations, the BS may configure some time resources with invalid time information, such as a time resource with a duration of 0. If the SN determines that the time indication field is referring to an invalid time resource information, then the SN can determine that the corresponding time indication field and the associated beam information field allocated for it are invalid.
[0191] In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. This invalid index can be pre-defined for the SN and BS, or it can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. The invalid beam index / time index can be common for all SNs in the group, or it can be different for each SN.In this way, when the SN determines that the index of the corresponding field is the pre-defined invalid index, the SN knows that the beam indication field and the associated time indication field are invalid.
[0192] In some implementations, in the context of the new DCI signaling, where the time information is common for all SNs in the group, the field format can include various fields, such as time indications (Time indication 1 to Time indication Ttotal) , beam indications (Beam indication 1 to Beam indication Ltotal) , frequency indications (Frequency indication 1 to Frequency indication Ftotal) , power indications (Power indication 1 to Power indication Gtotal) , panel indications (Panel indication 1 to Panel indication Htotal) , and polarization indications (Polarization indication 1 to Polarization indication Ptotal) . In the new DCI signaling, the time indication fields are common and shared by all SNs in the group. For each other type of field, each SN can be allocated with one or more corresponding types of fields. Furthermore, for each type of field, the allocated fields for a SN can be consecutive or non-consecutive. Additionally, the relationship between different types of fields can be either one-to-one mapping or one-to-more mapping.
[0193] Referring now to FIG. 9, depicted is a new / specific DCI signaling format, illustrating the indication of control information to three SNs in a group. As shown, the new / specific DCI signaling includes three time indication fields, six beam index fields, and four frequency indication fields. The time indication 1 is associated with beam index fields 1, 2, and 3, and the time indication 2 is associated with beam index fields 4, 5, and 6. The time indication fields in the DCI 2_8 are shared by the three SNs. As shown in FIG. 9, SN1 has been allocated with the non-consecutive beam index fields 1 and 4 and the frequency indication 1. This means / indicates / informs that the frequency indication 1 is common to all of the allocated beam and time information for SN1. Similarly, SN2 has been allocated with the non-consecutive beam index fields 2 and 5 and the frequency indication 2. This means / indicates / informs that the frequency indication 2 is common to all of the allocated beam and time information for SN2. Moreover, SN3 has been allocated with the non-consecutive beam index fields 3 and 6 and the frequency indication 3. This means / indicates / informs that the frequency indication 3 is common to all of the allocated beam and time information for SN3.
[0194] In some implementations, the SN can determine the number of time resource indication fields (Ttotal) in the new DCI signaling and its corresponding bitwidth. The number of time resource indication fields can be determined through various configurations. In some configurations, Ttotal can be a fixed value that is known by all SNs in the group and the BS. In some configurations, Ttotal can be configured / provided to each SN of the group by the BS via at least one of RRC, MAC CE, or DCI signaling. The configured / provided value of Ttotal is the same for all SNs. In some configurations, Ttotal can be implicitly obtained by the SN. For example, if the start position and end position of the time resource indication fields are configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling, and the bitwidth of each time resource indication field is known by the SN from the configured / provided RRC list of time resources, then the SN can implicitly calculate the number of time resource indication fields in the DCI.
[0195] In some implementations, the bitwidth of time resource indication fields can be determined through various configurations. In some configurations, the bitwidth can be determined by the number of entries in the RRC list of time resources. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, if a list of start positions corresponding to the time indication fields are configured / provided to the SN by the BS, and if the time indication fields are consecutive in the new DCI signaling, then the SN can know / determine the bitwidth of time indication fields from the difference in bits between two consecutive start positions.
[0196] In some implementations, the SN can determine the position of time indication fields in the new DCI signaling payload. In some configurations, the start position of the first time indications inside the DCI payload should be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In this way, since the number of time indication fields and the bitwidth can be known by the SN, as detailed herein, the SN can obtain the time information from the new DCI signaling payload. In some configurations, the start position and end position of the time indication fields are configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In this way, the bitwidth can be known by the SN from the configured / provided RRC list of time resources. Considering that the bitwidth of each time indication field is the same, the number of time indication fields in the DCI can be implicitly calculated by the SN. In some configurations, a pre-defined start position of the first time indications inside the DCI payload can be defined for the SNs in the group and BS. For example, the first bit of the DCI payload can be the start position of the first time indications. In some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each start position in the list represents the start position of the time indication inside the DCI payload. The first start position in the list represents the start position of the first time indication inside the DCI payload, the second start position in the list represents the start position of the second time indication inside the DCI payload, and so on. In this case, the number of time indication fields and the bitwidth of time indication fields can be implicitly known by the SN.
[0197] In some implementations, the number of beam indication fields (L) allocated for a SN can be determined through various configurations. In some configurations, L can be a fixed value that is known by the SN and BS. L can be the same for all SNs in a same group, or it can be different for SNs in a same group. In some configurations, L can be configured / provided to each SN of the group by the BS via at least one of RRC, MAC CE, or DCI signaling. In this way, different SNs of the group can have different numbers of beam indication fields. In some configurations, the number of beam indication fields allocated for a SN is determined and equal to the number of time indication fields allocated for the SN. In this case, the beam indication fields and the time indication fields of the block are sequentially associated with one-to-one mapping. In some configurations, L is zero, which means / indicates / informs that the new DCI signaling does not include the beam indication field that is allocated for the SN. In this case, the BS or the OAM can pre-configure a fixed beam pattern that can be used by the SN. For example, there are three SNs (e.g., SN1, SN2, SN3) in the group, and for SN1, the BS can pre-configure a fixed beam pattern of {beam index 1, beam index 2, beam index 3} that can be used by the SN1. In this way, the new DCI signaling that is configured / provided for SN1 includes the time indication. Then, the SN can use the indicated time resource information and the pre-configured / provided beam information to operate. In some configurations, L is equal to 1, which means / indicates / informs that a common beam information is used for all time information indicated that is allocated for the SN in the new DCI signaling. In some configurations, L can be implicitly obtained by the SN.For example, when a list of start positions of beam indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated beam fields for the SN can be implicitly obtained from the number of start positions in the list.
[0198] In some implementations, the bitwidth of the beam indication field allocated for the SN in the DCI signaling can have various configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, when a list of start positions of beam indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of allocated beam fields for the SN can be implicitly obtained.
[0199] In some implementations, the number of frequency indication fields (F) can be determined through various configurations. In some configurations, F is equal to L (L ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the indicated beam information and the frequency resource that is allocated for the SN. In some configurations, F is equal to T (T ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the indicated time resource and the frequency resource that is allocated for the SN. In some configurations, F is equal to 1. In this case, a common frequency bandwidth is used for the beam and / or time information that is allocated for the SN in the new DCI. In some configurations, F is equal to 0. In this case, the new DCI signaling does not include the frequency information that is allocated for the SN. The frequency indication can be implicitly determined by the BS / OAM with a fixed supported or fixed configured / provided frequency resource, such as the system bandwidth. In this case, the bitwidth of this field is 0. In some configurations, F can be implicitly obtained by the SN. For example, when a list of start positions of frequency indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated frequency fields for the SN can be implicitly obtained from the number of start positions in the list.
[0200] In some implementations, the bitwidth of the frequency indication field allocated for the SN in the DCI signaling can have various configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, when a list of start positions of frequency indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of allocated frequency fields for the SN can be implicitly obtained.
[0201] In some implementations, the number of power indication fields (G) and their bitwidth allocated for a SN can be determined through various configurations. In some configurations, G is equal to L (L ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the beam and the power information that are allocated for the SN. In some configurations, G is equal to T (T ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the time and the power information that are allocated for the SN. In some configurations, G is equal to 1. In this case, the power information is common for the beam and / or time information that are allocated for the SN in the new DCI. In some configurations, G is equal to 0. In this case, the new DCI signaling does not include the power information allocated for the SN. In some configurations, G can be implicitly obtained by the SN. For example, when a list of start positions of power indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated power fields for the SN can be implicitly obtained from the number of start positions in the list.
[0202] In some implementations, the bitwidth of the power indication field allocated for the SN in the DCI signaling can have various configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, when a list of start positions of power indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of allocated power fields for the SN can be implicitly obtained from the number of start positions in the list.
[0203] In some implementations, the number of panel indication fields (H) and their bitwidth allocated for a SN can be determined through various configurations. In some configurations, H is equal to L (L ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the beam and the panel information that are allocated for the SN. In some configurations, H is equal to T (T ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the time and the panel information that are allocated for the SN. In some configurations, H is equal to 1. In this case, the panel information is common for the beam and / or time information that are allocated for the SN in the new / specific DCI. In some configurations, H is equal to 0. In this case, the new / specific DCI signaling does not include the panel information allocated for the SN. In some configurations, H can be implicitly obtained by the SN. For example, when a list of start positions of panel indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated panel fields for the SN can be implicitly obtained from the number of start positions in the list.
[0204] In some implementations, the bitwidth of the panel indication field allocated for the SN in the DCI signaling can have various configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, when a list of start positions of panel indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of allocated panel fields for the SN can be implicitly obtained from the number of start positions in the list.
[0205] In some implementations, the number of polarization indication fields (P) and their bitwidth allocated for a SN can be determined through various configurations. In some configurations, P is equal to L (L ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the beam and the polarization information that are allocated for the SN.In some configurations, P is equal to T (T ≠ 0) . In this case, a 1-to-1 mapping can be used to associate the time and the polarization information that are allocated for the SN. In some configurations, P is equal to 1. In this case, the polarization information is common for the beam and / or time information that are allocated for the SN in the new DCI. In some configurations, P is equal to 0. In this case, the new DCI signaling does not include the polarization information allocated for the SN. In some configurations, P can be implicitly obtained by the SN. For example, when a list of start positions of polarization indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the number of allocated polarization fields for the SN can be implicitly obtained from the number of start positions in the list.
[0206] In some implementations, the bitwidth of the polarization indication field allocated for the SN in the DCI signaling can have various configurations. In some configurations, the bitwidth can be a fixed value that is known by the SN and BS. In some configurations, the bitwidth can be a configurable value that is configured / provided by the BS to each SN via RRC, MAC CE, or DCI signaling. In some configurations, the bitwidth can be implicitly obtained by the SN. For example, when a list of start positions of polarization indication fields that are allocated for the SN can be configured / provided to the SN by the BS, as detailed herein, the bitwidth of allocated polarization fields for the SN can be implicitly obtained from the number of start positions in the list.
[0207] In some implementations, the SN can determine the position of corresponding allocated fields inside the DCI payload for each type of field. In some configurations, the start position of the first allocated field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, for each type of field, when the corresponding allocated fields for each SN are consecutive, the start position of the first allocated field inside the DCI payload can be configured / provided to the SN by the BS. Since the number of corresponding allocated fields and the bitwidth of corresponding fields can be known by the SN, the SN can obtain the corresponding allocated information from the new DCI signaling.
[0208] In some configurations, the start position of the first allocated field and the end position of the last allocated field inside the DCI payload can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For example, for each type of field, the start position of the first allocated field and the end position of the last allocated field inside the DCI payload can be configured / provided to the SN by the BS. When the number of fields is configured / provided to the SN, there may be no need to configure the bitwidth of the corresponding field since it can be implicitly obtained by the SN. When the bitwidth of fields is configured / provided to the SN, there may be no need to configure the number of corresponding fields to the SN since it can be implicitly obtained by the SN. In some configurations, a list of start positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each start position corresponds to the start position of an allocated field inside the DCI payload. In this case, the number of fields allocated for the SN can be implicitly obtained by the number of configured / provided start positions in the list. The bitwidth of each field can also be implicitly obtained by the SN, since the allocated fields for each type of field are consecutive.
[0209] In some implementations, the SN can determine the size of a new / specific DCI signaling through various configurations. In some configurations, the size of new DCI signaling can be explicitly configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some configurations, the size of new DCI signaling can be equal to the existing DCI format that is monitored by the SN, e.g., DCI format 1_0. In some configurations, a special case is that for each type of field, when the number of fields and their bitwidth are the same and known for all SNs in the group, and when the SN can know / determine the number of SNs that the DCI includes the information for, the size of DCI can be implicitly calculated by the SN.
[0210] In some implementations, the SN can determine the actual number of beam indications and / or the actual number of time indications through various configurations. In some configurations, the number of beam indications and / or the number of time indications can be determined by the specific implementation. For example, when configuring the RRC list of time resources, some time resources can be configured / provided with invalid time information, such as a duration of 0. Thus, when the SN finds / determines that the time indication field refers to invalid time resource information, SN can know / determine that the corresponding time indication field and the associated beam information field allocated for it are invalid. In some configurations, a specific beam index or a specific time index can be defined as an invalid index to indicate that the information in the corresponding field is invalid. This invalid index can be pre-defined to the SN and BS, or configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. This invalid beam index / time index can be common for all SNs in the group, or can be different for each SN. In this way, when the SN finds / determines that the index of the corresponding field is the pre-defined invalid index, the SN knows / determines that this beam indication field and associated time indication field are invalid.
[0211] In some implementations, the current DCI 2_8 can be enhanced with new field format to be used for indicating the control information for a group of SNs. The field format methods for the new DCI signaling to indicate the control information for a group of SNs described above can also be applicable to the new field format of reusing the DCI 2_8 signaling to indicate the control information for a group of SNs.
[0212] In some embodiments, the group-related information can be configured / provided to the SN. When considering that the BS can send / provide / transmit group signaling for a group of SNs, several implementations may need to be taken into account. In some implementations, the BS can use group signaling to indicate control information for a group of SNs. To ensure that an SN knows that the monitored group signaling includes control information intended for it, several configurations can be considered. For example, in some configurations, a new dedicated parameter can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. When this parameter is configured / provided, it means / indicates / informs that group signaling is enabled for the SN. The SN should then monitor group signaling and decode it to obtain the control information allocated for it. In some configurations, to enable an SN to obtain control information from group signaling, new group-specific parameters are defined for the SN. In this case, whether group signaling is enabled for the SN can be implicitly indicated by one or more group-specific parameters. For example, as detailed herein, the number of allocated beam index fields in the DCI 2_8 can be configured / provided to the SN. Once this parameter is configured / provided to the SN, it means / indicates / informs that group signaling function is enabled, and the SN should monitor group signaling and decode it to obtain the control information allocated for it.
[0213] In some implementations, group-related information can be informed / provided to SNs. This information can include several configurations. In some configurations, the number of SNs in a group can be either the total number of SNs in the group, or the actual number of SNs in the group that group signaling includes control information for. For example, as detailed herein, the number of SNs in a group can be configured / provided to the SN to help the SN determine the size of the DCI 2_8. Similarly, the BS can determine that SN1, SN2, and SN3 can be grouped together. The BS can use group signaling to indicate the group information to these three SNs. However, group signaling may not always include control information for all three SNs. In this case, the actual number of SNs that group signaling includes control information for can be configured / provided to the SN.
[0214] In some configurations, a logic index can be configured / provided for an SN to represent the index of the SN in the group. This logic index can be used by the SN to obtain the position of allocated beam index fields and the position of allocated time indication fields in the DCI 2_8 message. Furthermore, the logic index can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. In some implementations, the logic index can be configured / provided to the SN and BS via the OAM.
[0215] In some embodiments, the priority between unicast signaling and group signaling for a specific SN can be configured / provided. There may exist a scenario where a SN receives unicast signaling that only includes control information for itself. The SN may also receive group signaling that includes control information for multiple SNs. In this case, if the SN receives conflicting control information from the unicast and group signaling (e.g., the beam information for the same time resource indicated in the two signaling is different) , several configurations can be considered for the priority between the two types of signaling. In some configurations, the SN can follow the indicated control information in the latest received signaling. In some configurations, group signaling is prioritized over unicast signaling. In some configurations, unicast signaling is prioritized over group signaling. In some configurations, the signaling that includes the priority flag has the highest priority. For example, a priority flag can be added to group signaling, and when the SN receives group signaling with the priority flag, it means / indicates / informs that group signaling has the highest priority. In some configurations, both the control information indicated in the two signaling can be operated by the SN. For example, when the beam information for the same time resource indicated in the two signaling is different and the network node can support simultaneous multiple beam operations, the SN can simultaneously forward the signal using two beams.
[0216] Referring now to FIG. 10, which illustrates a flow diagram of a method 1000 for indicating control information to network nodes (e.g., SNs) . The method 1000 may be implemented using any of the components and devices detailed herein in conjunction with FIGS. 1–9. In an overview, the method 1000 may include sending / providing / transmitting a first message indicating control information for a plurality of network nodes (1002) . The method 1000 can also include receiving the control information (1004) .
[0217] At operation (1002) , and in some arrangements, a wireless communication node (e.g., base station (BS) ) can send / provide / transmit a first message in a downlink control information (DCI) to a plurality of network nodes (e.g., smart node (SN) ) , with the first message indicating control information respectively configured / provided for the plurality of network nodes.
[0218] In some configurations, the configured / provided one or more respective ones of beam index fields and configured / provided one or more respective ones of time indication fields in the DCI are configured for each of the network nodes.
[0219] In some configurations, the wireless communication method may include the configured / provided one or more respective ones of beam index fields for each of the network nodes, which can be either consecutive or non-consecutive. Similarly, the configured / provided one or more respective ones of time indication fields for each of the network nodes can be either consecutive or non-consecutive. The term “consecutive” only refers to the fact that the allocated beam information fields and allocated time resource indication fields are continuous, respectively. It does not mean that the information indicated in the corresponding field are or must be “consecutive. ” For example, if an SN is allocated with two consecutive beam index fields, it means / indicates / informs that the SN has been allocated with the beam index field X and beam index field X+1. It does not mean that the information indicated in the two beam index fields are or must be the beam index Y and beam index Y+1.
[0220] In some implementations, the time indication fields in the DCI can be shared and used for the plurality of network nodes. As shown in FIG. 9, the time indication 1 is associated with beam index fields 1, 2, and 3, and the time indication 2 is associated with beam index fields 4, 5, and 6. Moreover, the time indication fields in the DCI are shared by the three SNs.
[0221] In some configurations, each of the network nodes can be configured / provided with one or more respective ones of beam index fields in the DCI. The configured / provided one or more respective ones of beam index fields for each of the network nodes can be consecutive or non-consecutive. In some configurations, each of the time indication field can be associated with one or more of the beam index fields. The associated one or more beam index fields for each time indication field can be used for one or more of the network nodes, respectively.
[0222] In some configurations, the beam index fields in the DCI can be reinterpreted / re-purposes / re-defined as beam pattern index fields in the DCI. The time indication fields can be shared and used for one or more of the plurality of network nodes. In some configurations, each of the beam pattern index fields can be sequentially associated with a corresponding ones of the time indication fields with one-to-one mapping. Furthermore, in some configurations, a beam pattern list can be configured / provided for each of the plurality of network nodes, The beam pattern list can include one or more beam patterns. As detailed herein, the beam pattern list can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or it can be configured / provided to the SN and BS via OAM signaling / protocol.
[0223] In some configurations, each of the beam patterns can include one or more beam indexes. The one or more beam indexes in each of the beam patterns can be allocated for one or more of the plurality of network nodes, respectively. In some implementations, the beam pattern list can be configured / provided to each of the plurality of network nodes via at least one of RRC, MAC CE, or DCI signaling. The first message may be sent in a new / specific format of DCI .
[0224] In some configurations, the DCI can be configured / provided to indicate the control information for the plurality of network nodes through at least one of the following. For example, a new RNTI can be configured / provided to scramble the DCI indicating the control information for the plurality of network nodes. Similarly, a legacy RNTI can be configured / provided to scramble the DCI with one or a plurality of values, where one value is configured / provided to scramble the DCI for indicating the control information for a network node, and one or more other values are configured / provided to scramble the DCI indicating the control information for the plurality of network nodes. The DCI indicating the control information for the plurality of network nodes can be configured / provided to be monitored in a common search space. Furthermore, a new dedicated parameter can be configured / provided for the plurality of network nodes to differentiate whether the DCI is configured / provided for indicating the control information for the plurality of network nodes or for a network node.
[0225] In some configurations, the first message can be sent in a format of a new DCI signaling. The new DCI signaling can be scrambled through at least one of following. For example, it can be scrambled using a new RNTI, e.g., ncr-G-RNTI. Furthermore, a legacy RNTI configured / provided to scramble DCI can have a plurality of values, where one value is configured / provided to scramble the DCI for indicating the control information for a network node, and one or more other values can be configured / provided to scramble the new DCI signaling indicating the control information for the plurality of network nodes. Each SN can be configured / provided with one or more ncr-G-RNTI values, such as ncr-G-RNTI SEQUENCE (SIZE (1.. maxNrofNCRGroupRNTIs) ) OF RNTI-Value. The maxNrofNCRGroupRNTIs parameter represents the maximum number of ncr-G-RNTI values that can be configured / provided for a SN. This parameter can be pre-defined or configured / provided by the BS. When a SN is configured / provided with multiple ncr-G-RNTI values, it indicates that the SN is configured / provided into multiple groups, and each group has a different ncr-G-RNTI value.
[0226] In some configurations, the format can consist of a plurality of blocks, where each of the network nodes can be configured / provided with a respective one of the blocks. Each block can further consist of at least one of the following: one or more beam indication fields, one or more time resource indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, or one or more polarization indication fields. Furthermore, the relationships between different types of the fields in each of the blocks can be respectively one-to-one mapping or one-to-more mapping.
[0227] In some configurations, the format can consist of a plurality of blocks, where each of the network nodes can be configured / provided with respective one or more of the blocks. Each block can further consist of at least one of the following: a beam indication field, a time resource indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field.
[0228] In some configurations, the format can consist of a plurality of blocks and a plurality of time resource indication fields, where each of the network nodes can be configured / provided with a respective one of the blocks. Each block can further consist of at least one of the following: one or more beam indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, or one or more polarization indication fields. Furthermore, a plurality of time resource indication fields can be shared for the plurality of network nodes.
[0229] In some configurations, the relationships between each of the time indication fields and different types of the fields in a corresponding one of the blocks configured / provided for a corresponding one of the network nodes can be respectively one-to-one mapping or one-to-more mapping. Furthermore, the relationships between different types of the fields in each of the blocks can be respectively one-to-one mapping or one-to-more mapping.
[0230] In some configurations, the format can include a plurality of blocks and a plurality of time resource indication fields, where each of the network nodes can be configured / provided with respective one or more of the blocks. Each block can include at least one of the following: a beam indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field. The time resource indication fields can be shared for the plurality of network nodes. Furthermore, the relationship between each of the plurality of time indication fields and respective one or more of the blocks configured / provided for a corresponding one of the network nodes can be one-to-one mapping or one-to-more mapping.
[0231] In some configurations, the format can include at least one of the following: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, or one or a plurality of polarization indication fields. Each of the network nodes can be configured / provided with one or more respective ones of the beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields. In some configurations, the configured / provided beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields for a corresponding one of the network nodes can be consecutive or non-consecutive. The relationships between different types of the fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping.
[0232] In some configurations, the format can include at least one of the following: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, or one or a plurality of polarization indication fields. Each of the network nodes can be configured / provided with one or more respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields. The configured / provided one or more time indication fields in the DCI can be shared by the plurality of network nodes. In some configurations, the configured / provided beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields for a corresponding one of the network nodes can be consecutive or non-consecutive. The relationships between each of the time indication fields and the respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping. Similarly, the relationships between different types of the fields configured / provided for a corresponding one of the plurality of network nodes can be one-to-one mapping or one-to-more mapping.
[0233] In some configurations, each of the network nodes can be configured / provided with one or more specific parameters to obtain the control information. Each of the plurality of network nodes can be configured / provided to obtain the control information through at least one of the following methods: a new dedicated parameter for the network node, or implicitly known by one or more specific parameters. The network node can know / determine that the first message contains the control information allocated for it when the one or more specific parameters are configured / provided for the network node.
[0234] In some configurations, the related information can be configured / provided for each of the plurality of network nodes to monitor and decode the first message. The related information may include at least one of a logic index representing a corresponding network node or a number of network nodes for which the control information is configured / provided. The related information can be configured / provided to the network node from the wireless communication node via at least one of RRC, MAC CE, or DCI signaling.
[0235] At least one aspect is directed to a system, method, apparatus, or a computer-readable medium. The wireless communication method may include the wireless communication node sending / providing / transmitting a second message to one of the network nodes, indicating control information that is being configured / provided for the network node. Furthermore, when the control information indicated in the first message and the control information indicated in the second message for the same network node are contradictory, the priorities between the two messages can include at least one of the following: the latest message signaling being the highest priority, the first message having a higher priority than the second message, the second message having a higher priority than the first message, or whichever of the first and second messages includes a priority flag having the highest priority.
[0236] While various embodiments of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architecture or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or more features of one embodiment can be combined with one or more features of another embodiment described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.
[0237] It is also understood that any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
[0238] Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits and symbols, which may be referenced in the above description, can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0239] A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.
[0240] Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include 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, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and / or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.
[0241] If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
[0242] In this document, the term “module” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
[0243] Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
[0244] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.
Claims
1.A wireless communication method, comprising:sending, by a wireless communication node to a plurality of network nodes, a first message indicating control information respectively configured for the plurality of network nodes.2.The wireless communication method of claim 1, wherein the first message is sent in a DCI.3.The wireless communication method of claim 2,wherein one or more respective ones of beam index fields and one or more respective ones of time indication fields in the DCI are configured for each of the network nodes.4.The wireless communication method of claim 3,wherein the configured one or more respective ones of beam index fields for each of the network nodes is consecutive or non-consecutive; andwherein the configured one or more respective ones of time indication fields for each of the network nodes is consecutive or non-consecutive.5.The wireless communication method of claim 2,wherein time indication fields in the DCI are shared and used for the plurality of network nodes.6.The wireless communication method of claim 5,wherein each of the network nodes is configured with one or more respective ones of beam index fields in the DCI; andwherein the configured one or more respective ones of beam index fields for each of the network nodes is consecutive or non-consecutive.7.The wireless communication method of claim 5,wherein each of the time indication field in the DCI is associated with one or more of the beam index fields; andwherein the associated one or more beam index fields for each time indication field is used for one or more of the network nodes, respectively.8.The wireless communication method of claim 2,wherein beam index fields in the DCI are reinterpreted as beam pattern index fields in the DCI; andwherein the time indication fields are shared and used for one or more of the plurality of network nodes.9.The wireless communication method of claim 8, wherein each of the beam pattern index fields is sequentially associated with a corresponding ones of the time indication fields with one-to-one mapping.10.The wireless communication method of claim 8,wherein a beam pattern list is configured for each of the plurality of network nodes; andwherein the beam pattern list includes one or more beam patterns.11.The wireless communication method of claim 10, wherein each of the beam patterns includes one or more beam indexes, and wherein the one or more beam indexes in each of the beam patterns is allocated for one or more of the plurality of network nodes, respectively.12.The wireless communication method of claim 10, wherein the beam pattern list is configured to each of the plurality of network nodes via at least one of RRC, MAC CE, or DCI signaling.13.The wireless communication method of claim 1, wherein the first message is sent in a new format of DCI.14.The wireless communication method of any of claim 2 or claim 13, wherein the DCI is configured for indicating the control information for the plurality of network nodes through at least one of:a new RNTI configured to scramble the DCI indicating the control information for the plurality of network nodes;a legacy RNTI configured to scramble the DCI has one or a plurality of values, one of the values configured to scramble the DCI for indicating the control information for a network node, and one or more other of the values are configured to scramble the DCI indicating the control information for the plurality of network nodes;the DCI indicating the control information for the plurality of network nodes is configured to be monitored in a common search space;a new dedicated parameter is configured for the plurality of network nodes to differentiate that the DCI is configured for indicating the control information for the plurality of network nodes or for a network node.15.The wireless communication method of claim 1, wherein the first message is sent in a format of a new DCI signaling.16.The wireless communication method of claim 15, wherein the new DCI signaling is scrambled through at least one of:a new RNTI; ora legacy RNTI configured to scramble DCI has a plurality of values, one of the values value configured to scramble the DCI indicating the control information for a network node, and one or more other of the values configured to scramble the new DCI signaling indicating the control information for the plurality of network nodes.17.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of a plurality of blocks, each of the network nodes configured with a respective one of the blocks; andwherein each of the blocks further consists of at least one of:one or more beam indication fields;one or more time resource indication fields;one or more frequency indication fields;one or more power indication fields;one or more panel indication fields; orone or more polarization indication fields.18.The wireless communication method of claim 17, wherein relationships between different types of the fields in each of the blocks are respectively one-to-one mapping or one-to-more mapping.19.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of a plurality of blocks, each of the network nodes configured with respective one or more of the blocks; andwherein each of the blocks further consist of at least one of: a beam indication field, a time resource indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field.20.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of a plurality of blocks and a plurality of time resource indication fields, each of the network nodes configured with a respective one of the blocks; andwherein each of the blocks further consists of at least one of:one or more beam indication fields;one or more frequency indication fields;one or more power indication fields;one or more panel indication fields; orone or more polarization indication fields.21.The wireless communication method of claim 20, wherein a plurality of time resource indication fields are shared for the plurality of network nodes.22.The wireless communication method of claim 20, wherein relationships between each of the time indication fields and different types of the fields in a corresponding one of the blocks configured for a corresponding one of the network nodes are respectively one-to-one mapping or one-to-more mapping.23.The wireless communication method of claim 20, wherein relationships between different types of the fields in each of the blocks are respectively one-to-one mapping or one-to-more mapping.24.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of a plurality of blocks and a plurality of time resource indication fields, each of the network nodes configured with respective one or more of the blocks; andwherein each of the blocks further consist of at least one of: a beam indication field, a frequency indication field, a power indication field, a panel indication field, or a polarization indication field.25.The wireless communication method of claim 24, wherein the time resource indication fields are shared for the plurality of network nodes.26.The wireless communication method of claim 24, wherein a relationship between each of the plurality of time indication fields and respective one or more of the blocks configured for a corresponding one of the network nodes are one-to-one mapping or one-to-more mapping.27.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of at least one of: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, and one or a plurality of polarization indication fields; andwherein each of the network nodes is configured with one or more respective ones of the beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields.28.The wireless communication method of claim 27, wherein the configured beam indication fields, time indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields for a corresponding one of the network nodes are consecutive or non-consecutive.29.The wireless communication method of claim 27, wherein relationships between different types of the fields configured for a corresponding one of the plurality of network nodes is one-to-one mapping or one-to-more mapping.30.The wireless communication method of any of claim 13 or claim 15,wherein the format consists of at least one of: one or a plurality of beam indication fields, one or a plurality of time indication fields, one or a plurality of frequency indication fields, one or a plurality of power indication fields, one or a plurality of panel indication fields, and one or a plurality of polarization indication fields;wherein each of the network nodes is configured with one or more respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields; andwherein the configured one or more time indication fields in the DCI are shared by the plurality of network nodes.31.The wireless communication method of claim 30, wherein the configured beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields for a corresponding one of the network nodes is consecutive or non-consecutive.32.The wireless communication method of claim 30, wherein relationships between each of the time indication fields and the respective ones of the beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields configured for a corresponding one of the plurality of network nodes are one-to-one mapping or one-to-more mapping.33.The wireless communication method of claim 30, wherein relationships between different types of the fields configured for a corresponding one of the plurality of network nodes are one-to-one mapping or one-to-more mapping.34.The wireless communication method of claim 1, wherein each of the network nodes is configured with one or more specific parameters to obtain the control information.35.The wireless communication method of any of claim 1 or claim 34, wherein each of a plurality of network nodes is configured to obtain the control information through at least one of:a new dedicated parameter for the network node;implicitly known by one or more specific parameters, and the network node can know that the first message contains the control information allocated for it when the one or more specific parameters are configured for the network node.36.The wireless communication method of claim 1, wherein related information is configured for each of plurality of network nodes to monitor and decode the first message;wherein the related information comprises at least one of:a logic index representing a corresponding one of the network nodes; ora number of the network nodes for which the control information is configured.37.The wireless communication method of claim 36, wherein the related information is configured to the network node from the wireless communication node via at least one of RRC, MAC CE, or DCI signaling.38.The wireless communication method of claim 1, further comprising:sending, by the wireless communication node to one of the network nodes, a second message indicating control information configured for the network node.39.The wireless communication method of claim 38, wherein when the control information indicated in the first message and the control information indicated in the second message for the same network node are contradictory, priorities between the two messages comprise at least one of:a latest message signaling has a highest priority;the first message has the higher priority that the second message;the second message has the higher priority that the first message; orwhichever of first and second messages includes a priority flag has a highest priority.40.A wireless communication method, comprising:receiving, by at least one network node of a plurality of network nodes, from a wireless communication node, a first message indicating control information respectively configured for the plurality of network nodes;wherein the wireless communication node is communicatively coupled to each of the plurality of network nodes through at least one of: a first forwarding link, a second forwarding link, a first control link, or a second control link, and each of the plurality of network nodes is communicatively coupled to one or more corresponding wireless communication devices through at least one of: a third forwarding link or a fourth forwarding link.41.A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 40.42.A computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 40.