System and method for indicating control information to network node

Abstract

Systems and methods are provided for indicating control information to a network node. The wireless communication node may send a first message to the network node in a legacy format of DCI 28. The wireless communication node may be communicatively coupled with a network node. Further, the network node may receive control information from the wireless communication node.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems and methods for instructing control information to network nodes. Background Technology

[0002] Coverage is a fundamental aspect of cellular network deployment. Mobile operators rely on different types of network nodes to provide comprehensive coverage in their deployments. Therefore, new types of network nodes have been considered to increase the flexibility of mobile operators in their network deployments. For example, some systems or architectures introduce integrated access and backhaul (IAB), a new type of network node that does not require wired backhaul and may be enhanced in some other systems. Another type of network node is the radio frequency (RF) repeater, which simply amplifies and forwards any signals it receives. RF repeaters have been widely deployed in 2G, 3G, and 4G to supplement the coverage provided by conventional full-stack cells. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues raised in the prior art and provide additional features that will become apparent from the following detailed description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and are not limiting, and that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure, as will be apparent to those skilled in the art who read this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication node (e.g., a base station (BS)) may send / provide / transmit a first message in downlink control information (DCI) to multiple network nodes (e.g., smart nodes (SN)), wherein the first message indicates control information configured / provided for each of the multiple network nodes respectively.

[0005] In some implementations, one or more corresponding beam index fields and one or more corresponding time indication fields configured / provided in the DCI are configured for each of the multiple network nodes.

[0006] In some implementations, one or more corresponding beam index fields configured / provided for each of the multiple network nodes can be continuous or non-continuous. Similarly, one or more corresponding time indication fields configured / provided for each of the multiple network nodes can be continuous or non-continuous.

[0007] In some implementations, multiple time indication fields in the DCI can be shared and used by multiple network nodes.

[0008] In some implementations, each of the multiple network nodes can be configured / provided with one or more corresponding beam index fields in the DCI. These one or more corresponding beam index fields configured / provided for each of the multiple network nodes can be consecutive or non-consecutive.

[0009] In some implementations, each time indication field may be associated with one or more beam index fields. The one or more beam index fields associated with each time indication field may be used for one or more of the plurality of network nodes.

[0010] In some implementations, the multiple beam index fields in the DCI can be reinterpreted as multiple beam pattern index fields in the DCI. Multiple time indication fields can be shared and used by one or more of the multiple network nodes.

[0011] In some implementations, each of the plurality of beam pattern index fields can be sequentially associated with a corresponding time indication field among the plurality of time indication fields in a one-to-one mapping manner. Furthermore, in some implementations, a beam pattern list can be configured / provided to each of the plurality of network nodes, and the beam pattern list may include one or more beam patterns.

[0012] In some implementations, each of the plurality of beam patterns may include one or more beam indices. The one or more beam indices in each of the plurality of beam patterns may be assigned to one or more network nodes among the plurality of network nodes. In some implementations, the beam pattern list may be configured / provided to each of the plurality of network nodes via at least one of radio resource control (RRC), medium access control element (MAC CE), or DCI signaling. Furthermore, the first message is transmitted in a new DCI format.

[0013] In some implementations, the DCI can be configured / provided to indicate control information for the plurality of network nodes using at least one of the following: For example, a new radio network temporary identifier (RNTI) can be configured / provided to scramble the DCI indicating control information for the plurality of network nodes. Similarly, a conventional RNTI can be configured / provided to scramble the DCI using one or more values, one of which is configured / provided to scramble the DCI indicating control information for one network node, and one or more other values ​​are configured / provided to scramble the DCI indicating control information for the plurality of network nodes. The DCI indicating control information for the plurality of network nodes can be configured / provided for monitoring in a common search space. New dedicated parameters can be configured / provided to the plurality of network nodes to distinguish whether the DCI is configured / provided to indicate control information for the plurality of network nodes or control information for one network node.

[0014] In some implementations, the first message may be sent in a new DCI signaling format. The new DCI signaling may be scrambled using at least one of the following methods. For example, scrambling may be performed using a new RNTI. Furthermore, a conventional RNTI configured / provided for scrambling the DCI may have multiple values, one of which is configured / provided for scrambling the DCI indicating control information for a network node, and one or more other values ​​may be configured / provided for scrambling the new DCI signaling indicating control information for the plurality of network nodes.

[0015] In some implementations, the format may include or consist of multiple blocks, wherein each of the plurality of network nodes may be configured / provided with a corresponding block among the plurality of blocks. Each block may 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 fields in each of the plurality of blocks may be either one-to-one mappings or one-to-many mappings.

[0016] In some implementations, the format may include or consist of multiple blocks, wherein each network node may be configured / provided with one or more of the multiple blocks. Each block may further include 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 some implementations, the format may include or consist of multiple blocks and multiple time resource indication fields, wherein each of the multiple network nodes may be configured / provided with a corresponding block among the multiple blocks. Each block may further include 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, the multiple time resource indication fields may be shared by the multiple network nodes.

[0018] In some implementations, the relationship between each of the plurality of time indication fields and a field of a different type in a corresponding block of the plurality of blocks configured / provided for the corresponding network node among the plurality of network nodes can be a one-to-one mapping or a one-to-many mapping, respectively. Furthermore, the relationship between different types of fields in each of the plurality of blocks can be a one-to-one mapping or a one-to-many mapping, respectively.

[0019] In some implementations, the format may include or consist of multiple blocks and multiple time resource indication fields, wherein each of the multiple network nodes may be configured / provided with one or more corresponding blocks among the multiple blocks. Each block may 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 multiple time resource indication fields may be shared by the multiple network nodes. The relationship between each of the multiple time indication fields and the corresponding one or more blocks among the multiple blocks configured / provided for the corresponding network node among the multiple network nodes may be a one-to-one mapping or a one-to-many mapping.

[0020] In some implementations, the format may include at least one of the following: one or more beam indication fields, one or more time 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. Each of the plurality of network nodes may be configured / provided with corresponding one or more beam indication fields, one or more time indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields. In some implementations, the plurality of beam indication fields, the plurality of time indication fields, the plurality of frequency indication fields, the plurality of power indication fields, the plurality of panel indication fields, and the plurality of polarization indication fields configured / provided for corresponding network nodes in the plurality of network nodes may be continuous or non-continuous. The relationship between different types of fields configured / provided for corresponding network nodes in the plurality of network nodes may be a one-to-one mapping or a one-to-many mapping.

[0021] In some implementations, the format may include at least one of the following: one or more beam indication fields, one or more time 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. Each of the plurality of network nodes may be configured / provided with corresponding one or more beam indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields. The one or more time indication fields configured / provided in the DCI may be shared by the plurality of network nodes. In some implementations, the plurality of beam indication fields, frequency indication fields, power indication fields, panel indication fields, and / or polarization indication fields configured / provided for corresponding network nodes in the plurality of network nodes may be continuous or non-continuous. The relationship between each of the plurality of time indication fields and the corresponding beam indication field, frequency indication field, power indication field, panel indication field, and polarization indication field configured / provided for the corresponding network node in the plurality of network nodes may be a one-to-one mapping or a one-to-many mapping. Similarly, the relationship between different types of fields configured / provided for corresponding network nodes among the multiple network nodes can be a one-to-one mapping or a one-to-many mapping.

[0022] In some implementations, each of the plurality of network nodes may be configured / provided with one or more specific parameters for obtaining the control information. Each of the plurality of network nodes may be configured / provided to obtain the control information through at least one of the following methods: new dedicated parameters for the network node, or implicit knowledge through one or more specific parameters. When the one or more specific parameters are configured / provided to the network node, the network node can know / determine that the first message includes control information allocated to the network node.

[0023] In some implementations, relevant information can be configured / provided to each of the plurality of network nodes to monitor and / or decode the first message. The relevant information may include at least one of the following: a logical index representing the corresponding network node, or the number of the plurality of network nodes configured / provided with the control information. The relevant information can be configured / provided from the wireless communication node to the network node via at least one of the following: RRC, MAC CE, or DCI signaling.

[0024] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A wireless communication node can send / provide / transmit a second message to one of a plurality of network nodes, the second message indicating control information configured / provided for said network node. Furthermore, when the control information indicated in the first message contradicts the control information indicated in the second message for the same network node, the priority between the first message and the second message 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 the message including a priority flag in both the first message and the second message has the highest priority.

[0025] In some implementations, the wireless communication node may indicate control information to a set of SNs according to at least one of the following example configurations or schemes.

[0026] Example Configuration 1: Reuse traditional DCI (e.g., DCI 2_8) to indicate control information for a set of SNs;

[0027] Example Configuration 2: Introducing new DCI signaling to indicate control information for a set of SNs; Example configuration 3: Enabling group signaling and group-related information can be indicated to the SN. Attached Figure Description

[0028] Various exemplary embodiments of the present technical solution are described in detail below with reference to the accompanying drawings. The drawings are for illustrative purposes only and depict only exemplary embodiments of the present technical solution to facilitate the reader's understanding. Therefore, the drawings should not be considered to limit the breadth, scope, or applicability of the present technical solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0029] Figure 1 An example cellular communication network that can implement the techniques disclosed herein, according to embodiments of the present disclosure, is shown; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 A schematic diagram of an example network according to some embodiments of the present disclosure is shown; Figure 4 A schematic diagram of the transmission links from BS to SN and from SN to UE according to some embodiments of the present disclosure is shown; Figure 5 The use of DCI signaling according to some embodiments of the present disclosure is illustrated, in which the number of beam index fields allocated for each SN is equal to the number of time resource indication fields allocated; Figure 6 The sequential association of beam index fields and time resource indication fields according to some embodiments of the present disclosure is illustrated, wherein each SN is configured / provided with one or more beam index fields and one or more time resource indication fields; Figure 7 This illustrates the use of beam pattern index and time resource indication fields to indicate control information for a set of SNs according to some embodiments of this disclosure; Figure 8 The field formats of DCI signaling according to some embodiments of this disclosure are shown; Figure 9 The present disclosure illustrates DCI signaling according to some embodiments thereof, in which the time resource indication field is public and shared by all SNs in a set of SNs; and Figure 10 A flowchart is shown of an example method for instructing control information to a set of SNs according to an embodiment of the present disclosure. Detailed Implementation

[0030] 1. Mobile communication technology and environment Figure 1An example wireless communication network and / or system 100 that can implement the techniques disclosed herein is illustrated according to embodiments of this disclosure. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also called a wireless communication node) and a user equipment 104 (hereinafter referred to as "UE 104"; also called a wireless communication device), which can communicate with each other via a communication link 110 (e.g., a wireless communication channel) and a group of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are located within the respective geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station that operates within its allocated bandwidth to provide appropriate radio coverage for its target users.

[0031] For example, BS 102 can operate within the allocated channel transmission bandwidth to provide appropriate coverage for UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes" that can generally practice the methods disclosed herein. According to various embodiments of this technical solution, such communication nodes are capable of wireless and / or wired communication.

[0032] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA (Orthogonal Frequency Division Multiplexing / Orthogonal Frequency Division Multiple Access) signals) according to some embodiments of the present technical solution is shown. System 200 may include components and elements configured / provided to support known or conventional operating features, which do not need to be described in detail herein. In one illustrative embodiment, system 200 can be used in the above-described... Figure 1 In a wireless communication environment (e.g., wireless communication environment 100), data symbols are communicated (e.g., transmitted and received).

[0033] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and user equipment 204 (hereinafter referred to as "UE 204"). 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 to and interconnected with each other as needed via a data communication bus 220. 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 to and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0034] As will be understood by those skilled in the art, System 200, in addition to Figure 2 In addition to the modules shown herein, any number of other modules may be included. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in the embodiments disclosed herein can 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, the various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend on the specific application and design constraints imposed on the overall system. Those skilled in the art can implement such functionality appropriately for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.

[0035] According to some embodiments, UE transceiver 230 may be referred to herein as "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred to herein as "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each including circuitry coupled to antenna 212. A downlink duplex switch may alternately couple the downlink transmitter or receiver to downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 to receive transmissions on the radio transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be time-coordinated so that the downlink receiver is coupled to the downlink antenna 212, so that transmissions on the wireless transmission link 250 can be received simultaneously when the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, tight time synchronization is achieved through a minimum guard time between changes in duplex direction.

[0036] UE transceiver 230 and base transceiver 210 are configured / provided to communicate via wireless data communication link 250 and cooperate with appropriately configured / provided RF antenna arrangements 212 / 232 capable of supporting specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured / provided to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited in application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured / provided to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0037] According to various embodiments, BS 202 may be, for example, an evolved node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented as various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented as a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, 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 way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0038] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly implemented in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can be implemented as RAM (Random Access Memory), flash memory, ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), registers, hard disks, removable disks, CD-ROMs (Compact Disk Read-Only Memory), or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230, respectively, so that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions 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 processor modules 210 and 230, respectively.

[0039] Network communication module 218 typically refers to the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base station transceiver 210 and other network components and communication nodes configured / provided to communicate with base station 202. For example, network communication module 218 may be configured / provided to support Internet or WiMAX (Worldwide Interoperability for Microwave Access) traffic. In a typical deployment, network communication module 218 provides, but is not limited to, an 802.3 Ethernet interface, enabling base station transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured / provided for,” “configured / provided as,” and their variations, used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform that specified operation or function.

[0040] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communications used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to its upper and lower layers. The OSI model also defines logical networks and efficiently describes computer packet transmission 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, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is other layers.

[0041] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to create and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0042] 2. Systems and methods for measuring interference in network nodes (e.g., SNs). In certain systems (e.g., 5G New Radio (NR), Next Generation (NG) systems, 3GPP systems, and / or other systems), network-controlled repeaters (NCRs) can be introduced as an enhancement to traditional radio frequency repeaters, possessing the ability to receive and / or process sideline control information from the network. This sideline control information allows the NCR to perform its amplification and forwarding operations more efficiently. Some benefits may include at least reduced unwanted noise amplification, better spatial directivity in transmission and reception, and / or simplified network integration.

[0043] NCRs can be viewed as stepping stones to reconfigurable intelligent surfaces (RIS). RIS nodes can adjust the phase and amplitude of received signals to improve / enhance coverage (e.g., network communication coverage). For the sake of brevity, as discussed herein, network nodes (including but not limited to NCRs, intelligent repeaters, enhanced radio repeaters, RIS, and / or integrated access and backhaul (IAB)) can be represented, referred to, or provided as intelligent nodes (SNs) (e.g., network nodes). An SN can refer to a node capable of supporting controlled amplification and forwarding operations or forwarding operations of wireless signals. For example, an SN can include, correspond to, or refer to a network node used to assist BS 102 in improving coverage (e.g., avoiding obstructions / obstacles, increasing transmission range, etc.).

[0044] In some cases, the SN can maintain multiple links simultaneously, such as one link between BS 102 and the SN, and another link between the SN and UE 104, to ensure signal forwarding for both BS 102 and UE 104. However, forwarded signals from the SN to UE 104 may interfere with signal reception from BS 102 to the SN, and vice versa (sometimes referred to as self-interference, self-oscillation, or self-excitation). Therefore, the systems and methods of the technical solutions discussed herein can provide or introduce the following functions: measuring interference on the SN (e.g., self-interference) and / or potential operations to be performed by BS 102 and / or the SN based on the interference measurement results, such as handling, resolving, or minimizing interference in signal forwarding.

[0045] Figure 3 A schematic diagram of example network 300 is shown. (As shown) Figure 3 As shown, for example, when there is an obstruction between BS 102 and UE 104, one or more BS 102A and BS 102B (e.g., BS 102) can serve one or more UE 104A and UE 104B (e.g., UE 104) in their cells via one or more of their respective SN306A and SN 306B (e.g., sometimes labeled SN 306).

[0046] Figure 4A schematic diagram 400 illustrates the transmission links between BS 102 and SN 306, and between SN 306 and UE 104. SN 306 may include at least two units or functional parts / components (e.g., sometimes referred to as functional entities) (e.g., a communication unit (CU) (e.g., SN CU) and a forwarding unit (FU) (e.g., SN FU)), or be composed of them. The units of SN 306 may support different functions for communication with at least one of BS 102 and / or UE 104. In some cases, the first unit (or functional entity) of SN 306 may refer to SN CU, while the second unit (or functional entity) of SN 306 may refer to SN FU, and vice versa. For example, SN CU (e.g., the first unit) may be a Network Control Repeater (NCR) MT. In another example, SN FU (e.g., the second unit) may be an NCR forwarder / forwarding (Fwd). The SN CU may exhibit / perform or include features similar to UE 104, such as receiving and decoding sideline control information from BS 102. The SN CU may be a control unit, controller, mobile terminal (MT), part of the UE, or a third-party IoT device, etc. The SN FU may use the sideline control information received by the SN CU to perform intelligent amplification and forwarding operations. The SN FU may be a radio unit (RU) or RIS, etc.

[0047] In some examples, the unit used to implement each function (or each functional part / component) may refer to a separate component or a dedicated component of the SN. In some examples, the unit used for each function may refer to different logical portions of the same component of the SN. Optionally, an interface for enabling information exchange / transmission between these two units may also be supported. In the following sections of this disclosure, for ease of description, Figure 4 As an example, this assumes operations between BS and FU, FU and UE, and BS and UE. As mentioned above, one of these entities can be replaced by another.

[0048] It can be defined / described / provided as follows: Figure 4 The transmission links shown are between BS 102 and SN 306, and between SN 306 and UE 104: C1: Control link from SN CU to BS (C-link); C2: Control link from BS to SN CU (C-link); F1: Backhaul link from SN FU to BS; F2: Backhaul link from BS to SN FU; F3: Access link from UE to SN FU; and F4: Access link from SN FU to UE.

[0049] A control link (e.g., sometimes referred to as a communication link) can refer to or represent a signal from one side that is detected and decoded by the other side, such that information transmitted on / through the control link can be used to control the state of a forwarding link (e.g., a backhaul link and / or an access link, an F link). A forwarding link can represent a signal from BS 102 or UE 104 that is unknown to the SN FU. In this case, the SN FU can amplify and forward the signal without decoding it. For example, links F1 and F3 can correspond to or be associated with a complete uplink (UL) forwarding link from UE 104 to BS 102 (e.g., a backhaul link and an access link, respectively), where F1 is an SN FU UL forwarding link. Similarly, links F2 and F4 can correspond to or be associated with a complete downlink (DL) forwarding link from BS 102 to UE 104 (e.g., a backhaul link and an access link, respectively), where F4 is an SN FU DL forwarding link. Links F1 and F2 can be referred to as backhaul links, and links F3 and F4 can be referred to as access links.

[0050] 3. Systems and methods for instructing control information to network nodes (e.g., SNs). As detailed in this article, coverage is a critical aspect of cellular network deployment, and mobile operators rely on various network nodes to provide broad coverage. To increase flexibility, new types of network nodes have been explored. For example, the IAB (Infrastructure Access Node) was introduced in Rel-16 and enhanced in Rel-17 as a radio node that eliminates the need for wired backhaul. As mentioned above, another type is the RF repeater, which amplifies and forwards received signals. RF repeaters have been widely used in 2G, 3G, 4G, and 5G systems to supplement the coverage provided by conventional full-stack cells. However, RF repeaters operate solely through radio units.

[0051] In Rel-18, NCR was introduced as an improvement over traditional RF repeaters. The NCR can receive and process side-link control information from the network. This allows / makes the NCR amplify the signal only when necessary, thereby reducing interference and noise. To indicate control information for the NCR, the current specification uses a predefined list of time resources for each non-periodic beam indication in the access link; this list is predefined via RRC signaling. Each time resource is defined by a specific field, which includes the start timeslot, start symbol, and duration.

[0052] However, a problem may arise whereby if the BS wants to send / provide / transmit control information to a group of SNs, it may introduce the need to use signaling to indicate control information to the group of SNs. Here, "a group of SNs" means multiple SNs. To address this, existing DCI (e.g., DCI 2_8), i.e., unicast signaling used to indicate control information for SNs, can be enhanced to group signaling to indicate control information for a group of SNs, or a new downlink control information (DCI) signaling can be introduced as group signaling to indicate control information for a group of SNs. Here, unicast signaling indicates that the signaling carries control information for only one SN, while group signaling indicates that the signaling carries control information for multiple SNs.

[0053] In some implementations, the current DCI 2_8 can be scrambled using a traditional RNTI (i.e., ncr-RNTI) to send / provide / transmit control information to a specific SN. To distinguish DCI 2_8 when it is used to indicate control information to a group of SNs, different RNTI values ​​can be used to scramble DCI 2_8. In some configurations, new RNTIs (e.g., ncr-G-RNTI) can be introduced to scramble DCI 2_8 used for signaling transmission to a group of SNs. Each SN can be configured / provided with one or more ncr-G-RNTI values, for example, 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 an SN. This parameter can be predefined or configured / provided by the BS. When an SN is configured / provided with multiple ncr-G-RNTI values, this means that the SN is configured / provided to multiple groups, and each group has a different ncr-G-RNTI value. SNs in the same group are configured / provided with the same ncr-G-RNTI value.

[0054] In some implementations, the traditional RNTI (ncr-RNTI) can be multiplexed through enhancements. For example, anncr-RNTI can be configured / provided with one or more RNTI values. This allows / makes the SN able to distinguish between DCI 2_8 for unicast and for a group of SNs. For example, "ncr-RNTI-r18" includes a sequence of RNTI values ​​ranging from 1 to a maximum number of NCRNTIs (maxNrofNCRRNTIs). The maxNrofNCRRNTIs parameter represents the maximum number of anncr-RNTI values ​​that can be configured / provided for the SN. This parameter can be predefined or configured / provided by the BS. For example, a predefined rule can be defined whereby the first RNTI value of anncr-RNTI is used to scramble DCI 2_8 for unicast signaling, while the second and subsequent RNTI values ​​of anncr-RNTI are used to scramble DCI 2_8 for group signaling for a group of SNs. In this way, the SN can always know / determine whether DCI 2_8 is used for the SN itself or for a group of SNs, regardless of how many RNTI values ​​are configured / provided for the SN.

[0055] For example, predefined rules can be defined such that the last configured / provided RNTI value of ncr-RNTI is used to scramble DCI 2_8 for unicast signaling, while the remaining RNTI values ​​of ncr-RNTI are used to scramble DCI2_8 for group signaling of a group of SNs. In this way, the SN can always know / determine whether DCI 2_8 is used for itself or for a group of SNs.

[0056] In some configurations, DCI 2_8 can be used for group signaling. In this case, DCI 2_8 can be monitored in the Common Search Space (CSS). When the SN receives an RRC configuration indicating that DCI format 2_8 is configured / provided for monitoring in the CSS, the SN can know / determine that DCI 2_8 is group signaling used to indicate control information to a group of SNs. However, if the SN receives an RRC configuration indicating that DCI format 2_8 is configured / provided for monitoring in the USS (User-Specific Search Space), then the SN can know / determine that DCI 2_8 is unicast signaling carrying only its own control information.

[0057] In some configurations, the base station can define dedicated parameters for the user equipment (UE) through at least one of RRC, Media Access Control (MAC) control elements (CE), or DCI signaling to distinguish whether 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 and set to enabled for the SN, it indicates / indicates / notifies that DCI 2_8 is used for group signaling. Otherwise, it indicates / indicates / notifies that 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 indicates / indicates that DCI 2_8 is used for group signaling. Otherwise, it indicates / indicates that DCI 2_8 is used for unicast signaling.

[0058] New / specific MAC CE signaling can also be used to indicate whether DCI 2_8 is used for unicast or group signaling. In some implementations, new / specific MAC CE signaling may include a field for activating or deactivating the group signaling functionality of DCI 2_8. When the MAC CE signaling is used to activate group signaling, DCI 2_8 is used to indicate control information to a group of SNs. When the MAC CE signaling is used to deactivate group signaling, DCI 2_8 is used as unicast signaling to indicate control information to SNs. Furthermore, new / specific fields can be added to the current DCI 2_8 signaling. These new / specific fields can be used to distinguish whether DCI 2_8 is used for unicast or group signaling. In some examples, when the new / specific field is set to zero, the setting / value indicates / indicates / notifies that the control information contained in DCI 2_8 is used for a single SN. Otherwise, the setting / value indicates / indicates that the control information contained in DCI 2_8 is used for a group of SNs.

[0059] In some implementations, when DCI 2_8 is used for group signaling, one or more new higher-layer parameters need to be configured / provided to enable each SN to know / determine the acquisition location of the control information assigned to it within DCI 2_8. In this case, whether DCI 2_8 is used for unicast signaling or group signaling can be implicitly determined through these newly configured / provided higher-layer parameters. For example, when DCI 2_8 is used for group signaling, a new higher-layer parameter should be defined for the SN to determine the starting position of the beamfields assigned within 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 beamfields assigned in 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 of a group of SNs.

[0060] When DCI 2_8 is used to indicate control information for a set of SNs, the field format of DCI 2_8 can be enhanced. In the traditional specification, the current DCI 2_8 format includes a beam index field and a time resource indicator field. The number of beam index fields is equal to the number of time resource indicator fields. The number of time resource indicator fields is determined by the length of the list configured / provided by the RRC. The bit width of the beam index field is determined by the RRC parameters. AperiodicBeamFieldWidth Configure / provide, and the bit width of the time resource indicator field is determined by max. It is confirmed that, among them, It is by ncr-AperiodicFwdConfig The number of time-domain resources configured / provided. N is determined by the RRC parameter. numberOfFields Configuration / provided.

[0061] In some implementations, DCI 2_8 can be reinterpreted as indicating control information for a set of SNs. This can be achieved, for example, by reinterpreting (e.g., reusing / redefining) the meaning of 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 assigned beam information fields and time resource indication fields can be consecutive or non-consecutive. The term "consecutive" refers to the fact that the assigned beam information fields and the assigned time resource indication fields are consecutive. This does not mean that the information indicated in the corresponding fields is "consecutive." For example, if an SN is assigned two consecutive beam index fields, this indicates / indicates / notifies that the SN has been assigned beam index field X and beam index field X+1. This does not mean that the information indicated in the two beam index fields must be beam index Y and beam index Y+1. This definition applies consistently across various scenarios. For each SN, the assigned time indication fields are sequentially associated with the assigned beam index fields in a one-to-one or one-to-many mapping. Furthermore, when the assigned time indication field and the assigned beam index field have a one-to-many mapping, and since the total number of beam index fields in the DCI equals the total number of beam index fields, it is possible that some time indication fields in the DCI may not be configured for the SN. In this case, these time indication fields can be considered invalid and not used by the SN.

[0062] For each SN, when the allocated time indicator field and the allocated beam index field are mapped one-to-one, the number of allocated beam index fields can be equal to the number of allocated time resource indicator fields. For example, as Figure 5As shown, each SN can be configured / provided with one or more consecutive beam index fields and one or more consecutive time resource indication fields. For each SN, the assigned beam index fields are sequentially associated with the assigned time resource indication fields in a one-to-one mapping, and the number of assigned beam index fields equals the number of assigned time indication fields for each SN. As shown, this group includes three SNs, and DCI 2_8 includes six beam index fields and six time resource indication fields to indicate control information for these three SNs. SN1 is assigned two beam index fields and two time resource indication fields, SN2 is assigned one beam index field and one time resource indication field, and SN3 is assigned three beam index fields and three time resource indication fields.

[0063] However, in some implementations, the beam index fields and time resource indicator fields allocated for different SNs can be "non-contiguous." The term "non-contiguous" means that the allocated beam information fields are non-contiguous, and the allocated time resource indicator fields are non-contiguous. For example, as... Figure 5 As shown, the group can include three SNs, and DCI 2_8 includes six beam index fields and six time resource indication fields to indicate control information for these three SNs. SN1 is assigned two beam index fields and two time resource indication fields, SN2 is assigned one beam index field and one time resource indication field, and SN3 is assigned three beam index fields and three time resource indication fields.

[0064] As described in detail in this document, the number of beam index fields in DCI 2_8 is equal to the number of time resource indication fields. In order to configure each SN with one or more beam index fields and one or more time resource indication fields, it is necessary to determine the number of beam index fields and time resource indication fields to be assigned to that SN for each SN.

[0065] In some configurations, traditional RRC parameters can be reused. numberOfFields This determines the number of time resource indication fields allocated to the SN. In this case, the number of beam index fields allocated to the SN is equal to the number of time resource indication fields allocated to the SN. For example, if DCI 2_8 is used to indicate control information for a set of SNs, and assuming DCI2_8 has a total of six time resource indication fields, and the first three time resource indication fields are allocated to SN1, then the BS can use the RRC parameters... numberOfFields The value is configured / provided as three for SN1.

[0066] In some configurations, the BS can use new higher-layer parameters via RRC, MAC CE, or DCI signaling to configure the number of beam index fields allocated in DCI 2_8 for the SN. In this case, the number of time indication fields allocated to the SN is equal to the number of beam index fields allocated. Traditional RRC parameters numberOfFields This can be used to indicate the total number of time indicator 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 indicator fields in DCI 2_8. For example, assuming DCI 2_8 includes six beam index fields and six time resource indicator fields, and three beam index fields are assigned to SN1, then the BS can configure the value of the new parameter to three for SN1 and set the current RRC parameter... numberOfFields The value is configured to be six for SN1. Upon receiving the value of the new parameter, SN1 knows / determines that three beam index fields and three time resource indication fields have been assigned to it in DCI 2_8.

[0067] In some configurations, the BS can use new higher-layer parameters via RRC, MAC CE, or DCI signaling to configure the number of time resource indication fields allocated in DCI 2_8 for the SN. In this case, the number of beam index fields allocated to the SN is equal to the number of time indication fields allocated. Traditional RRC parameters numberOfFields This 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.

[0068] In some configurations, the number of beam index fields and time resource indication fields allocated to the 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 within 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 to 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 base station configures the start position of the first allocated time indicator field and the end position of the last allocated time resource indication field within 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 to the SN is equal to the number of allocated time resource indication fields, the number of allocated beam index fields can also be obtained.

[0069] In some implementations, to configure one or more beam index fields and one or more time resource indication fields for each SN, the bit width of the beam index field and time indication field allocated in DCI 2_8 will be determined by the SN. In some configurations, traditional RRC parameters... aperiodicBeamFieldWidth This can be used to configure the bit width of all beam index fields in DCI 2_8. This results in all SNs within a group having the same number of available beams. In some configurations, the current RRC parameters... aperiodicBeamFieldWidth This can be reinterpreted as representing the bit width of the beam index field assigned to a specific SN. Therefore, the bit width of the beam index field assigned to different SNs can be different. In some configurations, the bit width of the assigned beam index field can be implicitly obtained by the SN. For example, if the base station configures a list of start positions corresponding to the beam index fields assigned to SNs, then the first start position corresponds to the start position of the first beam index field assigned to that SN, the second start position corresponds to the start position of the second beam index field assigned to that SN, and so on. If the beam index fields assigned to a SN are consecutive, the SN can calculate the bit width of the beam index field using the bit difference between two consecutive start positions.

[0070] Furthermore, the bit width of the allocated time indication field can be determined in different ways. In some configurations, this bit width is determined by a list provided by the RRC configuration. ncr-AperiodicFwdConfig The number of entries (as described in detail herein) is determined. In some configurations, the bit width of the allocated time resource indication field can be implicitly obtained by the SN. For example, if the base station is configured with a list of starting positions corresponding to the time indication fields allocated to the SN, then the first starting position corresponds to the starting position of the first time indication field allocated to that SN, the second starting position corresponds to the starting position of the second time indication field allocated to that SN, and so on. If the time resource indication fields allocated to the SN are consecutive, then the SN can calculate the bit width of the time resource indication field by the bit difference between two consecutive starting positions.

[0071] Because DCI 2_8 includes control information for multiple SNs, each SN needs to know / determine where to find the assigned beam index information within the DCI 2_8 payload. In some configurations, the starting position of the first assigned beam index field within 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 beam index fields assigned to the SN in DCI 2_8 are consecutive, the starting position of the first assigned beam index field within the DCI payload can be configured / provided to the SN by the BS. In this case, the bit width of the beam index field assigned to the SN can be determined by the current RRC parameters. AperiodicBeamFieldWidthConfiguration / Providement. The number of beam index fields assigned to the SN can be determined as described in detail in this document. This allows the SN to obtain its own beam information from the DCI 2_8 payload.

[0072] Similarly, in some configurations, the start position of the first assigned beam index field and the end position of the last assigned beam index field within 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 beam index fields assigned to the SN in DCI 2_8 are consecutive, the BS can configure the start position of the first assigned beam index field and the end position of the last assigned beam index field within the DCI payload. In this case, the bit width of the beam index fields assigned to the SN can use conventional RRC parameters. AperiodicBeamFieldWidth This is configured / provided. Therefore, it may not be necessary to explicitly configure the number of beam index fields or time resource indication fields to the SN. The number of beam index fields allocated to 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.

[0073] 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 assigned beam index field, the second start position corresponds to the start position of the second assigned beam index field, and so on. In this case, the number of beam index fields assigned to the SN can be implicitly obtained / determined from the number of start positions configured / provided in the list. When the beam index fields assigned to the SN are consecutive, the bit width of the beam index fields assigned to the SN can also be implicitly known / determined by the SN.

[0074] In some configurations, each beam field in DCI 2_8 is sequentially numbered, for example, starting from 1. This numbering scheme involves a logical index. This logical index represents the number / index of the first assigned beam index field for a specific SN. For example, if there are six beam index fields in DCI 2_8, including control information for three SNs, and the first assigned beam index field for SN1 is beam index field 3, then the logical index for SN1 will be three. For this configuration method to work, all beam index fields should have the same bit width, and the size of DCI 2_8 should be known to the SN. As described in detail herein, the number of assigned beam index fields for a SN can be determined. Once the logical index and the number of assigned beam index fields are known, the SN can obtain the assigned beam information from DCI 2_8.

[0075] In some configurations, a list of logical indices can be configured / provided to the SN. Each logical index represents the number / index of the beam index field assigned to the SN. The first logical index represents the number / index of the first beam index field assigned to the SN, the second logical index represents the number / index of the second beam index field assigned to the SN, and so on. This configuration method requires that all beam index fields have the same bit width. The number of beam index fields assigned to the SN can be implicitly known to the SN from the number of entries in the list.

[0076] In some configurations, the location of beam index fields allocated within the DCI payload can be implicitly known by the SN. This is possible if the logical index representing the number / index of the first allocated time indicator field is configured / provided to the SN, and the logical index representing the number / index of the first allocated beam index field is the same as the logical index of the first allocated time resource indicator field. In this case, the bit width of all beam index fields and the bit width of all time resource indicator fields should be the same. For example, if there are six beam index fields and six time resource indicator fields in DCI 2_8, these fields are used for control information for three SNs, and the first allocated time resource indicator field for SN1 is time resource indicator field 3, then the BS can configure logical index 3 for SN1, and can also configure the number of allocated time indicator fields for that SN to be two. In this way, SN1 can know / determine that the first allocated beam index field is beam index 3, and that the number of allocated beam index fields is two.

[0077] In some configurations, logical indexes can be configured / provided to each SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or via operations, administration, and maintenance (OAM) signaling / protocols. A logical index represents the number / index of the first assigned beam index field and the first assigned time indication field for a SN in DCI 2_8. For example, if DCI 2_8, which includes control information for three SNs, has 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), and the logical index configured / provided to SN1 is three, then the first assigned beam index field for SN1 is beam index 2, and the first assigned time resource indication field is time resource indication 3.

[0078] In some configurations, the logical index list can be configured / provided to each SN by the BS via at least one of RRC, MAC CE, or DCI signaling, or it can be configured / provided to each SN via OAM. A logical index represents the number / index of the first assigned beam index field and the first assigned time resource indication field for the SN in DCI 2_8. A first logical index represents the number / index of the first assigned time resource indication field and the assigned beam index field for the SN, a second logical index represents the number / index of the second assigned time resource indication field and the assigned beam index field for the SN, and so on. In this case, the number of assigned beam index fields and time indication fields can be implicitly known to the SN through the number of entries in the list.

[0079] To configure each SN with one or more beam index fields and one or more time resource indication fields, the SN determines the location of the allocated time resource indication fields within the DCI payload. In some configurations, the starting position of the first allocated time indication field 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 time indication resource fields allocated to the SN in DCI 2_8 are consecutive, the BS can configure the starting position of the first allocated time indication field to the SN. In this case, the bit width of the time resource indication field is determined by max... It is confirmed that, among them, It is by ncr-AperiodicFwdConfig The number of time-domain resources configured / provided. The number of time resource indication fields allocated to the SN can be determined using the options described in detail in this document. Therefore, the SN can obtain its own time information from the DCI 2_8 payload.

[0080] In some configurations, the start position of the first allocated time resource indicator field and the end position of the last allocated time resource indicator field within 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 when the time indicator fields allocated to the SN are consecutive. In this case, the bit width of the time resource indicator fields allocated to the SN can follow current specifications. Therefore, the number of time indicator fields allocated to the SN can be implicitly calculated. Since the number of allocated beam index fields is equal to the number of allocated time indicator fields, it is not necessary to explicitly configure the number of beam index fields or time indicator fields to the SN. Existing RRC parameters numberOfFieldsIt can be used to indicate the total number of time indication fields in DCI 2_8, or it can be reinterpreted / reused to indicate the number of time indication fields assigned to the SN in DCI 2_8. In either case, the BS may not need to configure this parameter to the SN.

[0081] In some configurations, the BS can configure / provide 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 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, it may not be necessary to explicitly configure the number of beam index fields or time indication fields to the SN. The number of time indication fields allocated to the SN can be implicitly obtained from the number of start positions configured / provided in the list. Furthermore, the number of allocated beam index fields is equal to the number of allocated time resource indication fields. Existing RRC parameters numberOfFields This parameter can be used to indicate the total number of time indication fields in DCI2_8, and / or can be reinterpreted as indicating the number of time resource indication fields allocated to the SN in DCI 2_8. In either case, the BS may not need to configure this parameter to the SN. If the allocated time indication fields are consecutive, the bit width of the time indication fields allocated to the SN can also be implicitly calculated.

[0082] In some configurations, the time resource indication fields in DCI 2_8 are numbered sequentially, for example, starting from 1 (or any integer value). For example, time indication fields can be numbered as Time Indicator Field 1, Time Indicator Field 2, and so on. This numbering scheme involves logical indexes. A logical index represents the number / index of the first allocated time resource indication field for a specific SN. For example, if there are six time resource indication fields in DCI 2_8, including control information for three SNs, and the first allocated time resource indication field for SN1 is Time Resource Indicator Field 3, then logical index 3 can be configured / provided to SN1. In this case, it may be required that the bit width of all time resource indication fields and the bit width of all beam index fields be the same. Since the SN can know the number of time resource indication fields allocated to it, as detailed herein, the SN can obtain the allocated time resource indications from DCI 2_8.

[0083] In some configurations, a list of logical indexes can be configured / provided to the SN. Each logical index represents the number / index of the time indicator field allocated to the SN. The first logical index represents the number / index of the first time indicator field allocated to the SN, the second logical index represents the number / index of the second time indicator field allocated to the SN, and so on. In this case, all time resource indicator fields should have the same bit width. The SN can implicitly know the number of time resource indicator fields allocated to the SN from the number of entries in the list.

[0084] In some configurations, if the BS configures the SN with a logical index representing the number / index of the first allocated beam index field, the SN can implicitly determine the location of the allocated time indicator field within the DCI payload. The logical index representing the number / index of the first allocated time resource indicator field can be the same as the logical index of the first allocated beam index field. In this case, the bit width of all beam index fields and the bit width of all time resource indicator fields are required to be the same. This allows / makes the SN able to determine the allocated beam information and time resource information from DCI 2_8. For example, if there are six beam index fields and six time indicator fields in DCI 2_8 used for control information for three SNs, and the first allocated beam index field for SN1 is beam index field 3, then the BS can configure logical index 3 for SN1, and can configure the number of allocated beam index fields for that SN to be 2. In this way, SN1 can determine that the first allocated time resource indicator field is time resource indicator 3, and the number of allocated time resource indicator fields is two.

[0085] In some configurations, the BS can configure a logical index for each SN via RRC, MAC CE, DCI signaling, or OAM. This logical index represents the number / index of the first assigned beam index field and the first assigned time resource indication field for the SN in DCI 2_8. For example, if there are six beam index fields (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), and the logical index configured / provided for SN1 is three, then the configured value indicates / indicates / notifies that the first assigned beam index field for SN1 is beam index 2, and the first assigned time resource indication field is time resource indication 3.

[0086] In some configurations, the BS can configure a logical index list for each SN via RRC, MAC CE, DCI signaling, or OAM signaling / protocol. These logical indices represent the number / index of the first assigned beam index field and the first assigned time resource indication field for the SN in DCI 2_8. The first logical index represents the number / index of the first assigned time resource indication field and the assigned beam index field for the SN, the second logical index represents the number / index of the second assigned time resource indication field and the assigned beam index field for the SN, and so on. In this case, the SN implicitly knows the number of assigned beam index fields and time resource indication fields by the number of entries in the list.

[0087] In some implementations, to configure one or more beam index fields and one or more time resource indication fields for the SN, the SN needs to determine the size of the received DCI 2_8 before decoding. As mentioned earlier, if the DCI 2_8 only carries information specific to a particular SN, the SN can use the configured / provided RRC parameters to calculate the size of the DCI 2_8. However, when the DCI 2_8 is used to indicate control information to a group of SNs, the SN cannot calculate the size of the DCI 2_8 because it does not know the bit width and number of beam index fields allocated to other SNs. In this regard, the BS can explicitly configure / provide the size of the DCI 2_8 to the SN via at least one of RRC, MAC CE, or DCI signaling. In some configurations, this size can be the same as the existing DCI format monitored by the SN (e.g., DCI format 1_0). In some configurations, the size of the DCI 2_8 can be implicitly obtained / calculated by the SN. For example, if the bit width of all beam index fields in DCI 2_8 is the same as the bit width of all time resource indication fields in DCI 2_8, and the SN knows this information, then the SN can implicitly calculate the size of DCI 2_8.

[0088] As described in detail herein, DCI 2_8 can be reinterpreted as a means of indicating control information to a group of SNs. This can be achieved by reinterpreting the meaning of the fields in DCI 2_8. In some implementations, the timing information of each SN within the same group can be identical and shared by the group of SNs. In this case, the timing resource indication field in DCI 2_8 can be used and shared by multiple SNs. This indicates / indicates / notifies that the timing resource indication field in DCI 2_8 is mapped to the beam index field in a one-to-many manner, meaning / indicating that one or more beam index fields can be associated with a timing resource indication field. In this way, for each field of DCI 2_8, each SN can be configured / provided with one or more beam index fields and one or more timing resource indication fields. The assigned beam information fields and the assigned timing indication information can be continuous or non-continuous. As described in detail herein, the term "continuous" means that the assigned beam information fields and the assigned timing resource indication fields are continuous. This does not mean that the information indicated in the corresponding fields should be continuous. For example, if a SN is assigned two consecutive beam index fields, this indicates / indicates / notifies that the SN has been assigned beam index field X and beam index field X+1. This does not mean that the information indicated in the two beam index fields should be beam index Y and beam index Y+1. For each SN, the assigned beam index fields are sequentially associated with the assigned time resource indication fields. This means / indicates that for each SN, beam index fields and time resource indication fields are paired one-to-one. The number of assigned beam index fields is also equal to the number of assigned time resource indication fields.

[0089] refer to Figure 6 This describes the sequential association between beam index fields and time resource indication fields, allowing the BS to efficiently transmit control information to a group of SNs. As shown in the figure, DCI 2_8 is used to indicate control information for a group of SNs operating in a cooperative manner. The timing information for each SN in the same group can be identical and shared by the group of SNs, and each SN can be assigned one or more consecutive beam index fields. DCI 2_8 can be constructed as a sequence of beam index fields and time resource indication fields numbered sequentially from 1 to N. The time resource indication in DCI 2_8 is common and shared across the group of SNs. For the beam index fields in DCI 2_8, each SN is configured with one or more consecutive beam index fields. For each SN, the assigned beam index fields and time resource indication fields are sequentially associated in a one-to-one mapping. For example, as shown... Figure 6As shown, DCI 2_8 includes six time resource indication fields and six beam index fields, and DCI 2_8 is used to indicate control information for three SNs. The time resource indication fields in DCI 2_8 are shared by the three SNs. SN 1 is assigned beam index field 1, which is associated with time resource indication field 1. SN 2 is assigned beam index fields 2 and 3, which are associated with time resource indication fields 1 and 2, respectively. SN 3 is assigned beam index fields 4, 5, and 6, which are associated with time resource indication fields 1, 2, and 3, respectively.

[0090] In some implementations, the timing information for each SN in the same group can be identical and shared by the group of SNs. Furthermore, the timing resource indication field can be applied to one or more consecutive beam index fields. This indicates that one or more consecutive beam index fields can each correspond to one or more SNs. In this way, the beam index fields assigned to SNs can be non-consecutive. For example, as... Figure 6 As shown, DCI 2_8 includes six time resource indication fields and six beam index fields, and DCI 2_8 is used to indicate control information for three SNs. The time resource indication fields in DCI 2_8 are shared by these three SNs. Time resource indication 1 is associated with beam index fields 1, 2, and 3, where beam index field 1 is assigned to SN1, beam index field 2 is assigned to SN2, and beam index field 3 is assigned to SN3. Time resource indication 2 is associated with beam index fields 4, 5, and 6, where beam index field 4 is assigned to SN1, beam index field 5 is assigned to SN2, and beam index field 6 is assigned to SN3. The remaining time resource indication fields 3, 4, 5, and 6 are invalid or not used by this set of SNs, and these time resource indication fields can be ignored by these SNs.

[0091] As described in detail in this article, all time resource indication fields are shared by a set of SNs. Therefore, through ncr- AperiodicFwdConfig The list of time resource information configured / provided by RRC should be identical for all SNs in the group. The number of time resource indication fields in DCI 2_8 can also be determined via RRC signaling as described in detail herein. numberOfFields Configuration / Provide.

[0092] In some implementations, to associate the Time Resource Indication field in DCI 2_8 with multiple SNs, the number of beam index fields allocated for each SN can be determined. In some configurations, the BS can configure the number of beam index fields allocated in DCI 2_8 to the SN via at least one of RRC, MAC CE, or DCI signaling. Furthermore, 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 achieved 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 within the DCI payload. The bit width of the beam index fields can be configured / provided to the SN via the current RRC parameters. Then, as described in detail herein, the SN can implicitly calculate the number of allocated beam index fields. Furthermore, in some configurations, if each SN in the group is allocated the same number of allocated beam index fields, this number can be a predefined value known to the BS and all SNs in the group. In some configurations, the number of beam index fields assigned to a specific SN in DCI 2_8 can be a predefined value known to both the SN and the BS. Different SNs within the same group can have different or the same predefined values.

[0093] In some implementations, to associate the Time Resource Indication field in DCI 2_8 with multiple SNs, the bit width of the beam information allocated to each SN can be determined. In some configurations, traditional RRC parameters... aperiodicBeamFieldWidth This can be used to configure the bit width of all beam index fields in DCI 2_8. This indicates that all SNs in the group can have the same number of beams available for use. In some configurations, the current RRC parameter... aperiodicBeamFieldWidth This can be reinterpreted as representing the bit width of the beam index field assigned to a specific SN. This indicates that the bit width of the beam index field can differ for different SNs. In some configurations, the bit width of the assigned beam index field can be implicitly determined by the SN. This can be done by the base station configuring a list of start positions corresponding to the assigned beam index field to the SN. These start positions are consecutive, and the SN can determine the bit width of the beam index field by calculating the bit difference between two consecutive start positions. Furthermore, in some configurations, the position of the beam information assigned to the SN in DCI 2_8 can refer to options as described in detail herein.

[0094] In some implementations, to associate the time resource indication field in DCI 2_8 with multiple SNs, it is necessary to determine the position of the time indication field within the DCI 2_8 payload. In some configurations, the starting position of the first time resource indication field within the DCI payload can be configured / provided to the SN by the base station via at least one of RRC, MAC CE, or DCI signaling. The bit width of the time resource in DCI 2_8 and the number of time indication fields can still follow traditional specifications. This indicates that the SN can obtain time information from the DCI 2_8 payload in the same manner as described in detail herein.

[0095] In some configurations, the start position of the first time indication field and the end position of the last allocated time indication field within the DCI payload can be configured / provided to the SN by the base station via at least one of RRC, MAC CE, or DCI signaling. Existing RRC parameters can be reused. numberOfFields This indicates the total number of time indication fields in DCI 2_8. In some implementations, the parameter... numberOfFields This can be reinterpreted as indicating the number of time indication fields in DCI 2_8 that are valid or pending for the SN. Finally, the parameter numberOfFields It can also be omitted entirely.

[0096] In some configurations, the position of the first Time Resource Indicator field within the DCI payload can be implicitly calculated by each SN. For example, when using traditional RRC parameters... aperiodicBeamFieldWidth When configuring the bit width of all beam index fields in DCI 2_8, this indicates that all SNs within a group have the same number of available beams. In this case, since the number of beam index fields in DCI 2_8 is equal to the number of time resource indication fields, the SN can determine the location of the time indication fields within the DCI payload.

[0097] In some configurations, the BS can configure / provide a list of start positions to the SN via at least one of RRC, MAC CE, or DCI signaling. These start positions are consecutive, with the first start position corresponding to the start position of the first Time Resource Indication field, the second start position corresponding to the start position of the second Time Resource Indication field, and so on. In this case, the number of Time Resource Indication fields in DCI 2_8 can be implicitly obtained from the number of start positions configured / provided through the list. Existing RRC parameters numberOfFields This can be used to indicate the total number of time indication fields in DCI 2_8. In some implementations, numberOfFields The parameter can be reinterpreted as indicating the number of time indication fields in DCI 2_8 that are valid for or available for that SN. In some implementations, the parameter... numberOfFields It can be completely omitted. Furthermore, since the time resource indicator field is continuous, its bit width can be implicitly known by the SN from the start position list. In some configurations, time information is shared by all SNs within a group. In this case, the position of the time information within the DCI 2_8 payload can be predefined and known to all SNs. This can indicate that the time resource indicator field is at a fixed position in DCI 2_8.

[0098] In some implementations, the bit width of the time resource indicator field can be determined in order to associate the time resource indicator field in DCI 2_8 with multiple SNs. In some configurations, as described in detail herein, the bit width of the time indicator field can be determined from a list provided by the RRC configuration. ncr-AperiodicFwdConfig The number of entries determines the bit width. Furthermore, the bit width of the time resource indicator field should / can be the same for all SNs within the group. In some configurations, the bit width of the time resource indicator field can be implicitly obtained by the SN. For example, when the BS configures / provides the SN with a list of starting positions corresponding to the time resource indicator field, the SN can calculate the bit width of the time resource indicator field by calculating the bit difference between two consecutive starting positions. This is because the time resource indicator fields in DCI 2_8 are consecutive.

[0099] 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 using DCI 2_8 to indicate control information for a group of SNs, the number of beam index fields allocated to the SN is less than the number of time resource indication fields in DCI 2_8. For a specific SN, if the SN is allocated L1 beam index fields and there are T1 time indication fields in DCI 2_8 (where T1 > L1), then the first L1 time resource indication fields are valid for that SN. The remaining T1–L1 time resource indication fields may be invalid for that specific SN.

[0100] In some implementations, the size of DCI 2_8 can be determined to associate the Time Resource Indication field in DCI 2_8 with multiple SNs. In some configurations, the size of DCI 2_8 can be explicitly configured / provided to the SNs by the base station 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 size of the existing DCI format monitored by the SN (e.g., DCI format 1_0). In some configurations, the bit width and number of beam index fields for each SN in the group can be the same and predefined. Furthermore, as described in detail herein, the bit width and number of time indication fields are known to the SNs. Once the number of SNs in the group is configured / provided for each SN, the size of DCI 2_8 can be implicitly calculated for that SN.

[0101] In some implementations, DCI 2_8 can be reinterpreted as indicating control information for a group of SNs. This can be done by reinterpreting the meaning of the fields in DCI 2_8. Timing information in DCI 2_8 can be shared by a group of SNs. Furthermore, each beam index field can be sequentially associated with a time resource indication field in a one-to-one mapping. Considering that DCI 2_8 can be used to indicate control information for a group of SNs, the BS can configure / provide a beam pattern list, including one or more beam patterns, to the SN 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 indices. Each beam index in the beam pattern corresponds to the beam information configured / provided for that SN. In this case, the existing beam index fields in DCI 2_8 can be reinterpreted as beam pattern indices. When the SN receives DCI 2_8, the SN can obtain / determine the beam pattern indices. The SN can then obtain the beam information configured / provided for that SN from the configured / provided beam pattern list. In this case, the fields of DCI 2_8 may include a series of beam pattern indices (beam pattern index 1, beam pattern index 2, ..., beam pattern index N) and time resource indicators (time resource indicator 1, time resource indicator 2, ..., time resource indicator N).

[0102] refer to Figure 7 This describes the use of beam pattern index and time resource indicator fields to indicate control information for this group of SNs. For example... Figure 7As shown, DCI 2_8 can be used to indicate control information for three SNs. In this example, DCI 2_8 includes three beam fields and three time resource indication fields. 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 fields in DCI 2_8 are used to indicate beam pattern indices. A list of beam patterns is configured / provided to the SNs, and for each beam pattern, the first configured / provided beam index information is assigned to SN1, the second configured / provided beam index information is assigned to SN2, and the third configured / provided beam index information is assigned to SN3. Therefore, when SN1 obtains beam pattern index 2 from the first beam pattern field, it can refer to the list and obtain the beam information corresponding to time resource indication 1, which is beam index 1. Similarly, SN2 can obtain beam information corresponding to time resource indication 1 as beam index 3, and SN3 can obtain beam information corresponding to time resource indication 1 as beam index 2.

[0103] In some implementations, the beam index field in DCI 2_8 can be reinterpreted as a beam pattern index. This requires configuring / providing the beam pattern list 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 via OAM to both the SN and the BS. 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 assigned to a separate SN. Different beam patterns in the list should include the same number of beam index information fields. Since the beam pattern list includes beam information for different SNs, the configured / provided beam pattern list should be the same for these SNs. Furthermore, since the time indication in DCI 2_8 is shared by these SNs, through ncr- AperiodicFwdConfig The list of time resources configured / provided by RRC should be the same for all SNs in the group.

[0104] In some implementations, the beam index field in DCI 2_8 can be reinterpreted as a beam pattern index. This is because the bit width and number of time indicator fields in DCI 2_8 can conform to the current specification. Furthermore, the total number of beam fields in DCI 2_8 equals the total number of time indicator fields. In some implementations, as described herein, the RRC parameters... aperiodicBeamFieldWidth This can be used to configure the bit width of the beam index field. However, if the beam index field is reinterpreted as / reused as a beam pattern index, in some configurations, the current RRC parameter... aperiodicBeamFieldWidthThis can be reinterpreted / reused as the bit width of the beam pattern index field in the DCI 2_8 configuration. Similarly, in some configurations, the bit width of the beam pattern index field in the DCI 2_8 can be configured by the BS to the SN using new higher-layer parameters.

[0105] In some implementations, since the beam index field in DCI 2_8 can be reinterpreted as a beam pattern index, the SN needs to determine which beam information in the beam pattern is assigned to that SN. In some configurations, the BS can configure logical indexes for the SNs to indicate the position or order of the beam information assigned to them in each beam pattern. For example, there are three SNs, and each beam pattern may include three beam information fields. The BS can configure logical index 1 for SN1, which indicates / indicates / notifies the configuration / providalization of the first beam index information in each beam pattern for SN1. The base station can configure logical index 2 for SN2, which indicates the configuration / providalization of the second beam index information in each beam pattern for SN2. Similarly, the base station can configure logical index 3 for SN3 to indicate the configuration / providalization of the third beam index information in each beam pattern for SN3. In some configurations, the order or position of the beam information assigned to each SN in the beam pattern can be predefined for each SN and BS.

[0106] In some implementations, the SN needs to determine the size of DCI 2_8 because the beam index field in DCI 2_8 can be reinterpreted as a beam pattern index. In some configurations, the size of DCI 2_8 can be implicitly calculated by the SN when the SN knows the bit width and number of the time indication field through conventional mechanisms, and the bit width and number of the beam field can also be determined by the SN. In some configurations, the size of DCI 2_8 can be explicitly configured / provided to the SN by the BS through at least one of RRC, MAC CE, or DCI signaling. In some configurations, this size can be equal to the existing DCI format monitored by the SN, such as DCI format 1_0.

[0107] In some embodiments, new DCI signaling may be introduced to indicate control information for a group of SNs. In some configurations, a new RNTI (e.g., SN-G-RNTI) may be defined to scramble the new group DCI signaling used to indicate control information for a group of SNs. This new RNTI is configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. For this new RNTI, one or more RNTI values ​​may be configured / provided for each SN. In this case, this indicates that SNs can be configured / provided to multiple groups. Each group has a different SN-G-RNTI value, and each SN in the same group is configured / provided with the same SN-G-RNTI value.

[0108] In some configurations, ncr-RNTI can be reused after enhancement. To enable scrambling of new DCI signaling, one or more RNTI values ​​for ncr-RNTI can be configured / provided for the SN. 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 be predefined or configured / provided by the BS. Utilization of different RNTI values ​​provides the ability to scramble DCI 2_8 and new DCI signaling. For example, predefined rules 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 new DCI signaling for group signaling of a set of SNs. Similarly, if only one RNTI value is configured / provided for ncr-RNTI, that specific RNTI value can be used to scramble both DCI formats. In some configurations, predefined rules for scrambling DCI signaling can be defined. For example, the last configured / provided RNTI value for ncr-RNTI can be used to scramble DCI 2_8 for unicast signaling, while the remaining RNTI values ​​for ncr-RNTI can be used to scramble new DCI signaling for group signaling of a set of SNs. If only one RNTI value is configured / provided for ncr-RNTI, that RNTI value can be used to scramble both DCI formats. In some configurations, ncr-RNTI can be reused. For example, in this case, ncr-RNTI can be used to scramble both the current DCI 2_8 and new DCI signaling formats.

[0109] In deploying new / specific DCI signaling mechanisms to efficiently transmit control information to a set of SNs, it is necessary to comprehensively consider various key aspects of the control information and their corresponding formats. First, beam information is used to indicate the beams for the SN. The format of beam information can be a logical beam index, where each beam index corresponds to a physical beam of the SN, or to a specific codebook that can be used to configure the SN. Thus, the relevant codebook configuration should be known to both the SN and the BS. Second, time information is used to indicate the time resources associated with the indicated beam information. The BS can configure a list of time resources for each SN via RRC signaling. Each time resource is defined by the following: {the starting time slot defined as the time slot offset, the starting symbol defined by the symbol offset within the time slot, and the duration defined by the number of symbols}. Thus, the time information field in the new DCI signaling is used to indicate the time resources configured / provided in the RRC signaling. Third, frequency information is used to indicate the frequency resources for the SN. The format of frequency information can be a logical index, and this logical index can be interpreted as a carrier index, passband index, bandwidth part (BWP) index, or cell index. In addition, the format can take into account power information, panel information (if the SN in the group includes multiple panels), and polarization information.

[0110] In the context of enabling new / specific DCI signaling to accommodate control information for multiple SNs, the information conveyed by the new DCI signaling may include a series of block numbers, denoted as block number 1, block number 2, and block number 3, up to block number N. Here, a "block" represents a set of fields or a group of fields containing control information for a specific SN. This definition applies consistently across various scenarios. Furthermore, each block may include:

[0111] Beam indicator 1 to beam indicator L; Time indicator 1 to time indicator T; Frequency indicators 1 to frequency indicators F; Power indication 1 to power indication G; Panel indicators 1 to panel indicator H; and Polarization indicator 1 to polarization indicator P.

[0112] In some implementations, when a new DCI is received, the SN can determine which block is configured / provided for it. In some configurations, the new DCI signaling includes multiple blocks for different SNs. The start position of the block allocated to a specific SN is configured / provided to that SN by the BS via RRC, MAC CE, or DCI signaling. This allows / makes the SN aware of / determines the start position of the block configured / provided for it. After receiving the new DCI, the SN can then use this start position to determine which block is configured / provided for it. The bit width and number of each field can also be configured / provided and known to the SN. This allows the SN to obtain / determine control information from the new group DCI signaling. In some configurations, the start and end positions of the blocks allocated to a specific SN in the new DCI format payload should be configured / provided to that SN by the BS via RRC, MAC CE, or DCI signaling.

[0113] In some implementations, the SN can determine the number of values ​​L, T, F, G, H, and P for each block, as well as the bit width of the corresponding fields. If the block includes a beam indication field, the bit width of the beam indication field can be a fixed value known to both the SN and the BS, or a configurable value that can be configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. The number of beam indication fields (L) can be defined using several alternative methods. In some configurations, L is a fixed value known to both the SN and the BS. L can be the same for all SNs in the same group, and in some embodiments, L can be different for each SN in the same group. In some configurations, L can be configured / provided by the BS to each SN in the group via at least one of RRC, MAC CE, or DCI signaling. Thus, blocks configured / provided to different SNs in the group can have different numbers of beam indication fields. In some configurations, the number L of beam indication fields for each block can be determined to be equal to and equal to the number T of time resource indication fields in the same block. In this case, the beam indication fields and time resource indication fields of the block can be sequentially associated in a one-to-one mapping. In some configurations, L is zero, indicating that the block indicating / notifying a new DCI signaling may not include a beam indication field. In this case, the BS or OAM can pre-configure a fixed beam pattern that can be used by the SN. For example, there are three SNs in the group (e.g., SN1, SN2, SN3), and for SN1, the BS can pre-configure a fixed beam pattern {beam index 1, beam index 2, beam index 3} that can be used by SN1. Thus, the block configured / provided for SN1 in the new DCI signaling includes a time indication, which the SN can then use to operate with the indicated time resource information and the pre-configured / provided beam information. In some configurations, L can be equal to 1, indicating / notifying that common beam information can be used for all time information indicated in the corresponding block.

[0114] In some implementations, if a block includes a time resource indication field, the bit width of the time resource indication field can be determined by the number of entries in the RRC time resource list configured / provided for the corresponding SN. The number (T) of time resource indication fields can be determined using several alternative methods. In some configurations, T can be a fixed value and can be known by both the SN and the BS. T can be the same for all SNs in the same group, and in some embodiments, T can be different for SNs within the same group. In some configurations, T can be configured / provided by the BS for each SN in the group via at least one of RRC, MAC CE, or DCI signaling. Thus, blocks configured / provided for different SNs in the group can have different numbers of time indication fields. In some configurations, the number T of time indication fields per block can be determined to be equal to the number L of beam indication fields in the same block. In this case, the beam indication fields and time indication fields of a block can be sequentially associated in a one-to-one mapping. In some configurations, T can be equal to 1, which indicates / indicates / notifies that common time information can be used for all beam information indicated in the corresponding block.

[0115] In some implementations, if a block includes a frequency indication field, the bit width of the frequency indication field can be a fixed value known to both the SN and the BS, or it can be a configurable value configured / provided to the SN by the BS via RRC, MAC CE, or DCI signaling. The number (F) of frequency indication fields can be determined using several alternative methods. In some configurations, F can be equal to L (L≠0), in which case a one-to-one mapping can be used to associate the indicated beam information and frequency resources. In some configurations, F can be equal to T (T≠0), in which case a one-to-one mapping can be used to associate the indicated time resources and frequency resources. In some configurations, F can be equal to 1, which indicates / indicates / notifies that common frequency bandwidth is available for the beam information and / or time information indicated in the corresponding block. In some configurations, F can be equal to 0, which indicates / indicates / notifies that the block does not include frequency information. The frequency indication can be implicitly determined by the BS / OAM through fixed supported or fixed configured / provided frequency resources (e.g., system bandwidth). In this case, the bit width of the field is 0.

[0116] In some implementations, if the block includes a power indication field, the bit width of the power indication field can be a fixed value known to both the SN and BS, or it can be a configurable value configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number (G) of power indication fields and their bit width can be determined using several alternative methods. In some configurations, G can be equal to L (L≠0), in which case a one-to-one mapping can be used to associate beam information with power information. In some configurations, G can be equal to T (T≠0), in which case a one-to-one mapping can be used to associate time information with power information. In some configurations, G can be equal to 1, which indicates / indicates / notifies that the power information can be common to the SN's forwarding operations. In some configurations, G can be equal to 0, which indicates / indicates / notifies that the new DCI signaling does not include a power indication.

[0117] In some implementations, if the block includes a panel indication field, the bit width of the panel indication field can be a fixed value known to both the SN and BS, or it can be a configurable value configured / provided by the BS to the SN via RRC, MAC CE, or DCI signaling. The number (H) of panel indication fields and their bit width can be determined using several alternative methods. In some configurations, H can be equal to L (L ≠ 0), in which case a one-to-one mapping can be used to associate beam information with panel information. In some configurations, H can be equal to T (T ≠ 0), in which case a one-to-one mapping can be used to associate time information with panel information. In some configurations, H can be equal to 1, indicating / indicating / notifying that the panel information can be shared with the SN for forwarding operations. In some configurations, H can be equal to 0, indicating / indicating / notifying that the new DCI signaling does not include a panel indication.

[0118] In some implementations, if the block includes a polarization indication field, the bit width of the polarization indication field can be a fixed value known to both the SN and BS, or it can be a configurable value configured / provided to the SN by the BS via RRC, MAC CE, or DCI signaling. The number (P) of polarization indication fields and their bit width can be determined using several alternative methods. In some configurations, P can be equal to L (L≠0), in which case a one-to-one mapping can be used to associate beam information with polarization information. In some configurations, P can be equal to T (T≠0), in which case a one-to-one mapping can be used to associate time information with polarization information. In some configurations, P can be equal to 1, indicating / indicating / notifying that the polarization information can be common to the SN's forwarding operations. In some configurations, P can be equal to 0, indicating / indicating / notifying that the new DCI signaling does not include a polarization indication.

[0119] In some implementations, the 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. This invalid index can be predefined for both the SN and the BS, or configured / provided by the BS for the SN via at least one of RRC, MAC CE, or DCI signaling. This invalid beam indication / time index can be common to all SNs within the group, or it can be different for each SN. Thus, when the SN determines that the index of the corresponding field is a predefined invalid index, the SN can determine that the beam indication field and the associated time indication field are invalid. In some configurations, an additional field can be added to the corresponding block to indicate the valid number of time indication fields or the valid number of beam indication fields. In some configurations, invalid beam indication / time indication can be achieved through implementation methods. For example, when configuring the RRC list of time resources, some time resources with invalid time information can be configured / provided, for example, a time resource with a duration of 0. Therefore, when the SN discovers / determines that the time indication field involves invalid time resource information, the SN can determine that the corresponding time indication field and the associated beam information field are invalid.

[0120] In some implementations, the 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 monitored by the SN, such as DCI format 1_0. In some configurations, the SN can implicitly know / determine the bit width of each block when the number of fields of each type and the bit width of each type of field are the same for different blocks. Furthermore, the SN can implicitly calculate the size of the new DCI signaling when it knows the number of blocks in the new DCI signaling or the number of SNs in a group. The size of the new DCI signaling can be configured without explicit configuration. For example, there can be three SNs (SN1, SN2, and SN3) serving the UE. Furthermore, as mentioned earlier, 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 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 for SN1 via RRC signaling. Similarly, for SN2, the BS can configure the number of time indication fields to 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 for SN2 via RRC signaling. For SN3, the BS can configure the number of time indication fields to 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 for SN3 via RRC signaling.

[0121]

[0122] Furthermore, since the new DCI signaling includes control information usable by the three SNs, the BS needs to indicate to each SN the starting bit position of its corresponding block within the new DCI payload. For example, for SN1, the BS can configure the starting position to 1, which indicates / indicates / notifies that the first bit of the new DCI payload is the starting position of block number 1. For SN2, the BS can configure the starting position to 21, and for SN3, the BS can configure the starting position to 37. In this way, upon receiving the DCI signaling, each SN can correctly determine its own control information from the new DCI signaling.

[0123] In some implementations, the new DCI signaling can be transmitted in multiple blocks (represented as block number 1, block number 2, block number 3, etc., 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 to have 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.

[0124] In some implementations, the SN can determine the starting position and number of blocks allocated to the SN. To determine the starting position of the blocks allocated to the SN, in some configurations, a list of starting positions can be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Each starting position corresponds to the starting position of a block within the new DCI-formatted payload configured / provided for the SN. If the configured / provided list contains only one starting position, it indicates that only one block is configured / provided to the SN in the new DCI signaling. For example, the starting position list can be configured / provided to the SN by the BS via MAC CE signaling. In this case, the number of blocks allocated to the SN can be implicitly obtained / determined by the SN from the entries in the list. In some configurations, the BS can configure the starting position of the first block within the new DCI-formatted payload to the 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 contiguous. In some implementations, considering 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 to the SN can be implicitly determined by the SN when the bit width of each field in the block is configured / provided to the SN or is known to the SN.

[0125] Furthermore, to determine the number of blocks allocated to the 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 to the SN can be implicitly obtained by the SN. For example, when the BS configures / provides a list of starting positions to the SN, the number of blocks allocated to the SN can be implicitly obtained by the SN from the entries in the list.

[0126] In some implementations, the SN can determine the bit width of each field in the block. The bit width of the time resource indication field in each block can be determined by the number of entries in the RRC list of time resources configured / provided for the corresponding SN. The bit widths of other fields in the block can be fixed values ​​known to both the SN and the BS, or can be configured / provided to the SN by the BS via RRC, MAC CE, or DCI signaling.

[0127] In some implementations, the SN can determine the validity of the beam indication or time indication within the allocated 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. This invalid index can be predefined 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 to all SNs within the group, or it can be different for each SN. Thus, when the SN determines that the index of the corresponding field is a predefined invalid index, the SN can determine that the beam indication field and the associated time indication field are invalid.

[0128] In some configurations, invalid beam indications / time indications can be implemented in various ways. For example, when configuring the RRC list of time resources, invalid time information, such as a duration of 0, can be configured / provided for some time resources. 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, the same beam information and / or the same time information can be configured / provided for one or more allocated blocks. For example, new DCI signaling includes control information for three SNs, with SN1 allocated blocks 1, 2, and 3. However, the BS may only want to configure two 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.

[0129] In some implementations, the SN can determine the size of the new DCI signaling. 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. Furthermore, in some configurations, this size can be equal to the size of the existing DCI format monitored by the SN, such as DCI format 1_0.

[0130] In some implementations, the new DCI signaling is used to transmit control information for the operation of a group of SNs. Considering that different SNs within the group may be located in different places and have different capabilities, the transmitted control information may differ for each SN. However, since the group of SNs jointly participates in forwarding signals from the BS to the UE or from the UE to the BS, there may be situations where different SNs require the same time resource information for their forwarding operations. The information transmitted by the new DCI signaling may include time indicators, such as time indicator 1, time indicator 2, up to time indicator T, and blocks numbered from 1 to N. Each SN is configured / provided with one block, and these blocks contain the necessary control information, including fields such as beam indicators 1 to L, frequency indicators 1 to F, power indicators 1 to G, panel indicators 1 to H, and polarization indicators 1 to P. Since the time information in the new DCI signaling is the same for the group of SNs, the RRC list configured by the BS for each SN in the group should be identical. The mapping between the time indicator field and the corresponding type of field in the blocks configured / provided for the SN can be a one-to-one mapping or a one-to-many mapping. The mapping relationship between corresponding fields of different types in a block can be either a one-to-one mapping or a one-to-many mapping.

[0131] In some implementations, the association between the time resource indication field (T) and the beam indication field (L) in each block may vary. Since the time resource indication field is common to all SNs in the group, the number of time resource indication fields may differ from the number (L) of beam indication fields in each block. When T is greater than L (T > L), several configurations can be considered to determine the associated time resource indications for the beam information indicated in the block.

[0132] For example, in some configurations, a "Time Indicator Bitmap" field can be added to each block to indicate the associated time information for the corresponding beam indicator. The bit width of the Time Indicator Bitmap field is equal to T. The beam information for the first indicator is associated with time indicator i, where i is the index of the first code point with a value of 1 in the bitmap. The beam information for the second indicator is associated with time indicator j, where j is the index of the second code point with a value of 1 in the bitmap, and so on. The number of values ​​of 1 in the bitmap should equal the number of beam information fields in the block. For example, if T = 5, and there are three beam indicators in block number 1, and the bitmap of the time indicator field is 10101, then the first beam indicator of block number 1 is associated with time indicator 1, the second beam indicator of block number 1 is associated with time indicator 3, and the third beam indicator of block number 1 is associated with time indicator 5.

[0133] In some configurations, for each SN, the indicated beam information can be associated with time indicators in a sequential, one-to-one mapping. Remaining time indicators can be considered invalid for that SN. For example, if T=5 and there are three beam indicators in block number 1, these three beam indicators can be associated with time indicator 1, time indicator 2, and time indicator 3 in sequence, respectively. For T=L, this means / indicates / notifies that for that SN, time indicators can be associated with indicated beam indicators in a sequential, one-to-one mapping. In the case of T<L, various configurations can be used to determine the associated time indicators for the indicated beam information in the block. In some configurations, for each SN, the indicated beam information can be associated with time indicators in a sequential, one-to-one mapping. Remaining beam indicators can be considered invalid for that SN. For example, if T=5 and there are six beam indicators in block number 1, the first five beam indicators are associated with the five time indicators in sequence, respectively.

[0134] In some implementations, the SN can determine the number of time resource indication fields and their corresponding bit widths in a new DCI signaling. 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 to all SNs and BSs within the group. In some configurations, T can be configured / provided by the BS to each SN within the group 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 short, when the BS configures the start position of the first time indication and the end position of the last time indication within the DCI payload to the SN via at least one of RRC, MAC CE, or DCI signaling, and the SN knows the bit width 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.

[0135] In some implementations, the bit width of the time resource indication field can be determined by the number of entries in the RRC list of the time resource. In other configurations, the bit width of the time resource indication field can be implicitly obtained by the SN. For example, if the BS configures / provides the SN with a list of start positions corresponding to the time indication field, and if the time indication field is consecutive in the new DCI signaling, the SN can implicitly know / determine the bit width of the time indication field based on the bit difference between two consecutive start positions.

[0136] In some implementations, the SN can determine the location of the time indication field in the new DCI signaling payload. For example, in some configurations, the BS can configure the starting position of the first time indication within the DCI payload to the SN via at least one of RRC, MAC CE, or DCI signaling. Thus, since the number and bit width of the time indication field can be known by the SN as described herein, the SN can obtain time information from the new DCI signaling payload.

[0137] In some configurations, the BS can configure the start position of the first time indication and the end position of the last time indication within 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 be consecutive. Since the bit width can be known by the SN from the RRC list of configured / provided time resources, and each time indication field has the same bit width, the number of time indication fields in the DCI can be implicitly calculated by the SN.

[0138] In some configurations, a predefined start position for the first time indication in the DCI payload can be defined for the SN and BS within the group. This may require that the time indication fields in the DCI signaling be consecutive. For example, the first bit of the DCI payload could be the start position of the first time indication. Since the bit width of the time indication field can be known by the SN from the RRC list of the configured / provided time resources, and the number of time indication fields can be known by the SN, the SN can implicitly obtain time information from the new DCI signaling payload.

[0139] 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 a time indication within the DCI payload. The first start position in the list represents the start position of the first time indication within the DCI payload, the second start position in the list represents the start position of the second time indication within the DCI payload, and so on. In this case, the SN can implicitly know the number of time indication fields and the bit width of the time indication fields. Similarly, as described in detail herein, in some implementations, the SN can determine the number of values ​​L, F, G, H, P and their corresponding bit widths.

[0140] In some implementations, the SN can determine the location of the allocated block within the DCI payload. For example, in some configurations, the BS can configure the starting position of the block allocated to the SN within the new DCI format payload via RRC, MAC CE, or DCI signaling. Thus, upon receiving the new DCI, the SN can implicitly know / determine the starting position of the block configured / provided for it. Since the bit width and number of each field in the block can also be configured / provided and known to the SN, the SN can obtain control information from the new group DCI signaling. In some configurations, the BS can configure the start and end positions of the block allocated to the SN within the new DCI format payload via RRC, MAC CE, or DCI signaling. This allows / makes the SN able to determine the location of the allocated block within the DCI payload.

[0141] In some implementations, the SN can determine the size of the new DCI signaling. For example, 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. Furthermore, this size can be equal to the size of the existing DCI format monitored by the SN, such as DCI format 1_0.

[0142] In some implementations, the SN can determine the actual / valid number of beam indicators. In some configurations, a new field can be added to the block to indicate the valid number of beam indicators or the valid number of time indicators. The actual number of beam indicators can be implemented in several ways. For example, a bitmap field can be introduced into the block to indicate the actual / valid number of beam indicators. This field can also be used to indicate valid beam indicators and time indicators. For example, if L=4, T=5, and there are four beam indicators in block number 1, and the bitmap for the time indicator is 10101, this means that only the first three beam indicators have corresponding time indicators. The fourth beam indicator in the block is invalid because it has no associated time indicator. Another way to implement the actual number of beam indicators 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 indicator field refers to an invalid time resource, the SN can determine that the corresponding time indicator field and the associated beam information field in the block are invalid.

[0143] 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 predefined for both the SN and the BS, or it can be configured / provided to the SN by the BS via at least one of RRC, MACCE, or DCI signaling. The invalid beam index / time index can be common to all SNs in the group, or it can be different for each SN. Thus, when the SN determines that the index of the corresponding field is a predefined invalid index, the SN can determine that the beam indication field and the associated time indication field are invalid.

[0144] In some implementations, the new DCI signaling can use the same time resource information for all SNs in the group, such that the information transmitted via the new DCI signaling includes a series of time indicators (time indicator 1, time indicator 2, ..., time indicator T) and a list of block numbers (block number 1, block number 2, block number 3, ..., block number N). Each SN in the group can be configured / provided with one or more blocks, and each block is defined to have at least one of the following fields: beam indicator 1, frequency indicator 1, polarization indicator 1, power indicator 1, and panel indicator 1. The mapping between the multiple time indicator fields configured / provided for the SN and the corresponding one or more blocks can be a one-to-one mapping or a one-to-many mapping, depending on the specific configuration.

[0145] In some implementations, the association between time indicators and beam indicators across all allocated blocks for a SN can vary. As detailed in this document, the total number (T) of time resource indicator fields in allocated blocks for a SN may differ from the number (L) of beam indicator fields. For each SN, the indicated beam information is associated with time indicators in a sequential, one-to-one mapping. Remaining time indicators or remaining beam indicators are considered invalid for the SN. For example, if T = 5 and there are three beam indicators in the three blocks allocated to SN1, the first three beam indicators are associated with time indicators 1, 2, and 3 in sequence, respectively. Time indicators 4 and 5 are invalid for SN1.

[0146] In some implementations, the SN can determine the number of time resource indication fields and their corresponding bit width in the new DCI signaling, the position of the time resource indication fields in the DCI signaling payload, the starting position of the block and the number of blocks allocated to the SN, and the size of the new DCI signaling, as described in detail in this document.

[0147] 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 time resources with a duration of 0. If the SN finds / determines that a time resource indication field refers to an invalid time resource, then 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 predefined for both the SN and the 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 to all SNs in the group, or it can be different for each SN. Thus, when the SN determines that the index of the corresponding field is a predefined invalid index, the SN can determine that the beam indication field and the associated time indication field are invalid.

[0148] In some implementations, the new DCI signaling can transmit information including various fields, such as beam indication (beam indication 1 to beam indication L). total Time indication (time indication 1 to time indication T) total ), frequency indication (frequency indication 1 to frequency indication F) total Power indication (Power Indicator 1 to Power Indicator G) total ), Panel indicators (panel indicator 1 to panel indicator H) total ) and polarization indicators (polarization indicator 1 to polarization indicator P) total Each SN is configured / provided with one or more corresponding fields of these types, and the fields assigned to the SN can be continuous or non-contiguous, as described in detail herein. Furthermore, the relationship between fields of different types can be a one-to-one mapping or a one-to-many mapping.

[0149] Now for reference Figure 8The diagram describes 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 assign the following fields to this group of SNs. For SN1, it can be assigned two beam index fields, two time resource indication fields, and one frequency information field. Furthermore, beam index 1 is associated with time indication 1, beam index 2 is associated with time indication 2, and frequency indication 1 is common to all beam and time information assigned to SN1. Similarly, for SN2, it can be assigned one beam index field, one time resource indication field, and one frequency information field. Furthermore, beam index 3 is associated with time indication 3, and frequency indication 2 is common to all beam and time information assigned to SN2. Further, for SN3, it can be assigned three beam index fields, three time indication fields, and one frequency information field. Furthermore, beam index 4 is associated with time indicator 4, beam index 5 is associated with time indicator 5, beam index 6 is associated with time indicator 6, and frequency indicator 3 is common to all beam information and time information assigned to SN3.

[0150] To configure one or more corresponding fields for each SN in the new DCI signaling, the SN needs to determine the number of fields to be allocated and their corresponding bit widths. Specifically, the number (L) of beam indication fields allocated to the SN can be determined through various configurations. For example, in some configurations, L can be a fixed value known to both the SN and the BS, where L can be the same for all SNs within the group, or can vary for different SNs within the group. In some configurations, L can be configured / provided by the BS to each SN in the group via at least one of RRC, MAC CE, or DCI signaling. This allows / makes different SNs in the group to have different numbers of beam indication fields. In some configurations, the number of beam indication fields allocated to the SN can be determined to be equal to the number of time indication fields allocated to that SN. In this case, the beam indication fields and time indication fields of the block can be associated sequentially in a one-to-one mapping. In some configurations, L can be zero, which indicates / indicates / notifies that the new DCI signaling does not include beam indication fields allocated to the SN. In this case, the BS or OAM function can pre-configure a fixed beam pattern that can be used by the SN. For example, if there are three SNs in a group (e.g., SN1, SN2, SN3), for SN1, the BS can pre-configure a fixed beam pattern {beam index 1, beam index 2, beam index 3} that can be used by SN1. Thus, new DCI signaling configured / provided for SN1 includes a time indication. The SN can then operate using the indicated time resource information and the pre-configured / provided beam information. In some configurations, L can be 1, which indicates / indicates / notifies that common beam information is used to indicate and allocate all time information for that SN in new DCI signaling. In some configurations, L can be implicitly obtained by the SN. For example, if a list of starting positions for beam indication fields allocated to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of beam fields allocated to the SN can be implicitly obtained from the number of starting positions in that list.

[0151] In some implementations, the bit width of the beam indication field assigned to the SN in the new DCI signaling can be determined through various configurations. For example, in some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of start positions for the beam indication field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, then the bit width of the beam field assigned to the SN can be implicitly obtained from the number of start positions in that list.

[0152] In some implementations, the number (T) of time resource indication fields in the new DCI signaling can be determined through various configurations. In some configurations, T can be a fixed value known to both the SN and the base station. T can be the same for all SNs in the group, or it can be different for different SNs in the group. In some configurations, T can be configured / provided by the BS to each SN in the group 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 to the SN in the new DCI signaling can be determined to be equal to the number of beam indication fields allocated to the SN. In this case, the beam indication fields and time indication fields allocated to the SN in the new DCI signaling are associated sequentially in a one-to-one mapping. In some configurations, T can be 1, which indicates / indicates / notifies the use of common time information for all beam information allocated to the SN in the new DCI signaling. In some configurations, T can be implicitly obtained by the SN. For example, if the list of starting positions for the time indication fields assigned to the SN can be configured / provided to the SN by the BS, as described in aspect 2 of case 2.5, then the number of time fields assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0153] In some implementations, if the new DCI signaling includes a time indication field allocated to the SN, the bit width of that allocated time indication field can be determined through various configurations. In some configurations, the bit width of the time indication field allocated to the SN can be determined by the number of entries in the RRC list of time-domain resources configured / provided for the corresponding SN. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of starting positions for the time resource indication field allocated to the SN can be configured / provided to the SN by the BS, as described in detail herein, the bit width of the time-domain field allocated to the SN can be implicitly obtained from the number of starting positions in the list.

[0154] In some implementations, the number (F) of the frequency indication field in the new DCI signaling can be determined through various configurations. In some configurations, F = L (L ≠ 0), using a one-to-one mapping to associate the indicated beam information with the frequency domain resources allocated to the SN. In some configurations, F = T (T ≠ 0), using a one-to-one mapping to associate the indicated time resources with the frequency resources allocated to the SN. In some configurations, F = 1, which indicates / indicates / notifies the use of a common frequency bandwidth for the beam information and / or time information allocated to the SN in the new DCI. In some configurations, F = 0, which indicates / indicates that the new DCI signaling does not include frequency information allocated to the SN. The frequency indication can be implicitly determined by the BS / OAM through fixed supported or fixed configured / provided frequency resources (e.g., system bandwidth). In this case, the bit width of the field is 0. In some configurations, F can be implicitly obtained by the SN. For example, if the list of starting positions for the frequency indication fields assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of frequency fields assigned to the SN can be implicitly obtained from the number of starting positions in the list.

[0155] In some implementations, the bit width of the frequency indication field assigned to the SN in DCI signaling can have several configurations. For example, in some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of starting positions for the frequency indication field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the bit width of the frequency field assigned to the SN can be implicitly obtained from the number of starting positions in the list.

[0156] In some implementations, the number (G) of power indication fields assigned to the SN in the new DCI signaling and its corresponding bit width can have several configurations. In some configurations, G = L (L ≠ 0), and a one-to-one mapping can be used to associate beam information and power information assigned to the SN. In some configurations, G = T (T ≠ 0), and a one-to-one mapping can be used to associate time information and power information assigned to the SN. In some configurations, G = 1, which indicates / indicates / notifies that in the new DCI, power information is common to the beam information and / or time information assigned to the SN. In some configurations, G = 0, which indicates / indicates / notifies that the new DCI signaling does not include power information assigned to the SN. In some configurations, G can be implicitly obtained by the SN. For example, if the BS can configure / provide the SN with a list of starting positions for power indication fields assigned to that SN, as described in detail herein, the number of power fields assigned to that SN can be implicitly obtained from the number of starting positions in that list.

[0157] In some implementations, the bit width of the power indication field assigned to the SN in new DCI signaling can be configured / provided in various ways. In some configurations, the bit width of the power indication field can be a fixed value known to both the SN and the BS. In some configurations, the bit width of the power indication field can be configured / provided to each SN by the BS via RRC signaling, MAC CE, or DCI signaling. In some configurations, the bit width of the power indication field can be implicitly obtained by the SN. For example, when the BS can configure / provide to the SN a list of starting positions for the power indication field assigned to that SN, as described in detail herein, the bit width of the power field assigned to that SN can be implicitly obtained.

[0158] In some implementations, the number (H) of panel indication fields assigned to the SN in the new DCI signaling and its corresponding bit width can be configured / provided in various ways. For example, in some configurations, H = L (L ≠ 0), a one-to-one mapping can be used to associate beam information and panel information assigned to the SN. In some configurations, H = T (T ≠ 0), a one-to-one mapping can be used to associate time information and panel information assigned to the SN. In some configurations, H = 1, which indicates / indicates / notifies that in the new DCI, panel information is common to the beam information and / or time information assigned to the SN. In some configurations, H = 0, which indicates / indicates / notifies that the new DCI signaling does not include panel information assigned to the SN. In some configurations, H can be implicitly obtained by the SN. For example, if the BS can configure / provide the SN with a list of starting positions for panel indication fields assigned to that SN, as described in detail herein, the number of panel fields assigned to that SN can be implicitly obtained from the number of starting positions in that list.

[0159] In some implementations, the bit width of the panel indication field assigned to the SN in new DCI signaling can have several configurations. In some configurations, the bit width can be a fixed value known to both the SN and the base station. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the base station via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of starting positions for the panel indication field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, then the bit width of the panel field assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0160] In some implementations, the number (P) of polarization indication fields assigned to the SN in the new DCI signaling and their corresponding bit width can be configured in several ways. For example, in some configurations, if P = L (L ≠ 0), a one-to-one mapping can be used to associate the beam information and polarization information assigned to the SN. In some configurations, if P = T (T ≠ 0), a one-to-one mapping can be used to associate the time information and polarization information assigned to the SN. In some configurations, if P = 1, this indicates / indicates / notifies that the polarization information is common to the beam information and / or time information assigned to the SN in the new DCI. In some configurations, if P = 0, this indicates / indicates / notifies that the new DCI signaling does not include the polarization information assigned to the SN. In some configurations, P can be implicitly obtained by the SN. For example, if the list of starting positions of the polarization indication fields assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of polarization fields assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0161] In some implementations, the bit width of the polarization indicator field assigned to the SN in new DCI signaling can be configured in several ways. For example, in some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of starting positions for the polarization indicator field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, then the bit width of the polarization field assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0162] In some implementations, in order to configure each SN with one or more corresponding fields, the SN needs to determine the position of the assigned field within the DCI payload. Specifically, for each type of field, the SN can determine the position of the corresponding assigned field within the DCI payload through various configurations. For example, in some configurations, the starting position of the first assigned field within 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 assigned fields for each SN are consecutive, the starting position of the first assigned field within the DCI payload can be configured / provided to the SN by the BS. Since the number of corresponding assigned fields and the bit width of the corresponding fields can be determined by the SN, the SN can determine the corresponding assignment information from new DCI signaling.

[0163] In some configurations, the start position of the first assigned field and the end position of the last assigned field within the DCI payload can be configured / provided to the SN by the base station via at least one of RRC, MAC CE, or DCI signaling. For example, for each type of field, when the corresponding assigned fields for each SN are consecutive, the start position of the first assigned field and the end position of the last assigned field within the DCI payload can be configured / provided to the SN by the base station. In this case, it may not be necessary to configure both the number of fields and the bit width of the corresponding fields to the SN, as the SN can implicitly obtain these values.

[0164] In some configurations, the BS can configure / provide 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 corresponds to the start position of a field allocated within the DCI payload. For example, for each type of field, when the corresponding allocated fields for each SN are non-contiguous, the list of start positions can be configured / provided by the BS to the SN. In this case, the number of fields allocated to the SN can be implicitly obtained from the number of start positions configured / provided in the list. Since the allocated fields are contiguous for each type of field, the bit width can also be implicitly obtained by the SN.

[0165] 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 various ways. In some configurations, the size of the new DCI signaling can be explicitly configured / provided to the SN by the base station via at least one of RRC, MAC CE, or DCI signaling. In some configurations, the size of the new DCI signaling can be the same as the existing DCI format monitored by the SN (e.g., DCI format 1.0). In some configurations, the size of the DCI can be implicitly calculated if the number of fields and their bit widths are the same and known for all SNs within the group.

[0166] 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 various ways.

[0167] In some implementations, for each SN, the SN can determine the actual number of beam indications and / or the actual number of time resource indications. This can be determined in various ways. For example, in some configurations, the BS can configure some time resources to have invalid time information, such as time resources with a duration of 0. If the SN determines that the time indication field refers to invalid time resource information, then the SN can determine that the corresponding time indication field and the associated beam information field assigned to it are invalid.

[0168] 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 predefined for both the SN and the BS, or it can be 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 to all SNs within the group, or it can be different for each SN. Thus, when the SN determines that the index of the corresponding field is a predefined invalid index, the SN knows that the beam indication field and the associated time indication field are invalid.

[0169] In some implementations, within the context of new DCI signaling, the time information is common to all SNs within the group, and this field format can include various fields, such as: time indication (time indication 1 to time indication T). total Beam indication (beam indication 1 to beam indication L) total ), frequency indication (frequency indication 1 to frequency indication F) total Power indication (Power Indicator 1 to Power Indicator G) total ), Panel indicators (panel indicator 1 to panel indicator H) total ) and polarization indicators (polarization indicator 1 to polarization indicator P) total In this new DCI signaling, the time indication field is public and shared by all SNs within the group. For each other field type, each SN can be assigned one or more fields of the corresponding type. Furthermore, for each field type, the fields assigned to SNs can be consecutive or non-consecutive. Additionally, the relationship between different types of fields can be a one-to-one mapping or a one-to-many mapping.

[0170] Now for reference Figure 9 This describes a new / specific DCI signaling format, illustrating the indication of control information to three SNs within a group. As shown in the figure, this new / specific DCI signaling includes three time indication fields, six beam index fields, and four frequency indication fields. Time indication 1 is associated with beam index fields 1, 2, and 3, and time indication 2 is associated with beam index fields 4, 5, and 6. The time indication fields in DCI 2_8 are shared by these three SNs. Figure 9As shown, SN1 is assigned discontinuous beam index fields 1 and 4, and frequency indicator 1. This indicates that frequency indicator 1 is common to all beam and time information assigned to SN1. Similarly, SN2 is assigned discontinuous beam index fields 2 and 5, and frequency indicator 2. This indicates that frequency indicator 2 is common to all beam and time information assigned to SN2. Furthermore, SN3 is assigned discontinuous beam index fields 3 and 6, and frequency indicator 3. This indicates that frequency indicator 3 is common to all beam and time information assigned to SN3.

[0171] In some implementations, the SN can determine the number of time resource indication fields (T) in the new DCI signaling. total The number of time resource indicator fields and their corresponding bit widths can be determined through various configurations. In some configurations, T... total It can be a fixed value, known to all SNs and BSs within the group. In some configurations, T... total The BS can configure / provide to each SN in the group via at least one of RRC, MACCE, or DCI signaling. T is configured / provided for all SNs. total The values ​​are the same. In some configurations, T total This can be implicitly obtained by the SN. For example, if the start and end positions 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 bit width of each time resource indication field is known by the SN from the RRC list of the configured / provided time resources, then the SN can implicitly calculate the number of time resource indication fields in the DCI.

[0172] In some implementations, the bit width of the time resource indication field can be determined through various configurations. In some configurations, the bit width can be determined by the number of entries in the RRC list of the time resource. In some configurations, the bit width can be implicitly obtained by the SN. For example, if the list of start positions corresponding to the time indication field is configured / provided to the SN by the BS, and if the time indication field is consecutive in new DCI signaling, the SN can know / determine the bit width of the time indication field based on the bit difference between two consecutive start positions.

[0173] In some implementations, the SN can determine the position of the time indication fields in the new DCI signaling payload. In some configurations, the start position of the first time indication within the DCI payload should be configured / provided to the SN by the BS via at least one of RRC, MAC CE, or DCI signaling. Thus, since the number and bit width of the time indication fields can be known to the SN, as described in detail herein, the SN can obtain time information from the new DCI signaling payload. In some configurations, the start and end positions 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. Thus, the SN can know the bit width from the RRC list of the configured / provided time resources. Considering that each time indication field has the same bit width, the SN can implicitly calculate the number of time indication fields in the DCI. In some configurations, a predefined start position for the first time indication in the DCI payload can be defined for both the SN and BS within the group. For example, the first bit of the DCI payload could be the start position of the first time indication. In some configurations, the BS can configure / provide a list of start positions to the SN via at least one of RRC, MAC CE, or DCI signaling. Each starting position in the list represents the starting position of the time indication within the DCI payload. The first starting position in the list represents the starting position of the first time indication within the DCI payload, the second starting position in the list represents the starting position of the second time indication within the DCI payload, and so on. In this case, the SN can implicitly know the number of time indication fields and the bit width of the time indication fields.

[0174] In some implementations, the number (L) of beam indication fields assigned to a SN can be determined through various configurations. In some configurations, L can be a fixed value known to both the SN and the BS. L can be the same for all SNs within the same group, or it can be different for SNs within the same group. In some configurations, L can be configured / provided by the BS to each SN in the group via at least one of RRC, MAC CE, or DCI signaling. In this way, different SNs within the group can have different numbers of beam indication fields. In some configurations, the number of beam indication fields assigned to a SN is determined to be equal to the number of time indication fields assigned to that SN. In this case, the beam indication fields and time indication fields of a block are associated sequentially in a one-to-one mapping. In some configurations, L is zero, which indicates / indicates / notifies that new DCI signaling does not include beam indication fields assigned to the SN. In this case, the BS or OAM can pre-configure a fixed beam pattern that can be used by the SN. For example, there are three SNs in the group (e.g., SN1, SN2, SN3), and for SN1, the BS can pre-configure a fixed beam pattern {beam index 1, beam index 2, beam index 3} that can be used by SN1. Thus, new DCI signaling configured / provided for SN1 includes a time indication. The SN can then operate using the indicated time resource information and the pre-configured / provided beam information. In some configurations, L equals 1, which indicates / indicates / notifies the use of common beam information for all time information allocated to the SN in new DCI signaling. In some configurations, L can be implicitly obtained by the SN. For example, when the list of starting positions for beam indication fields allocated to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of beam fields allocated to the SN can be implicitly obtained from the number of starting positions in the list.

[0175] In some implementations, the bit width of the beam indication field assigned to the SN in DCI signaling can have various configurations. In some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, when the list of starting positions for the beam indication field assigned to the SN can be configured / provided to the SN by the BS, the bit width of the beam field assigned to the SN can be implicitly obtained, as described in detail herein.

[0176] In some implementations, the number (F) of frequency indication fields can be determined through various configurations. In some configurations, F equals L (L≠0). In this case, a one-to-one mapping can be used to associate the indicated beam information with the frequency resources allocated to the SN. In some configurations, F equals T (T≠0). In this case, a one-to-one mapping can be used to associate the indicated time resources with the frequency resources allocated to the SN. In some configurations, F equals 1. In this case, the common frequency bandwidth is used for the beam information and / or time information allocated to the SN in the new DCI. In some configurations, F equals 0. In this case, the new DCI signaling does not include the frequency information allocated to the SN. The frequency indication can be implicitly determined by the BS / OAM through fixed-supported or fixed-configuration / provided frequency domain resources (e.g., system bandwidth). In this case, the bit width of the field is 0. In some configurations, F can be implicitly obtained by the SN. For example, when the list of starting positions for the frequency indication fields allocated to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of frequency fields allocated to the SN can be implicitly obtained from the number of starting positions in the list.

[0177] In some implementations, the bit width of the frequency indication field assigned to the SN in DCI signaling can have various configurations. In some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, when the list of starting positions for the frequency indication field assigned to the SN can be configured / provided to the SN by the BS, the bit width of the frequency field assigned to the SN can be implicitly obtained, as described in detail herein.

[0178] In some implementations, the number (G) of power indication fields assigned to the SN and their bit width can be determined through various configurations. In some configurations, G equals L (L≠0). In this case, a one-to-one mapping can be used to associate the beam information and power information assigned to the SN. In some configurations, G equals T (T≠0). In this case, a one-to-one mapping can be used to associate the time information and power information assigned to the SN. In some configurations, G equals 1. In this case, the power information is common to the beam information and / or time information assigned to the SN in the new DCI. In some configurations, G equals 0. In this case, the new DCI signaling does not include the power information assigned to the SN. In some configurations, G can be implicitly obtained by the SN. For example, when the list of starting positions for power indication fields assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the number of power fields assigned to the SN can be implicitly obtained from the number of starting positions in the list.

[0179] In some implementations, the bit width of the power indication field assigned to the SN in DCI signaling can have various configurations. In some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, when the list of starting positions for the power indication field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the bit width of the power field assigned to the SN can be implicitly obtained from the number of starting positions in the list.

[0180] In some implementations, the number (H) of panel indication fields assigned to the SN and their bit width can be determined through various configurations. In some configurations, H equals L (L≠0). In this case, a one-to-one mapping can be used to associate the beam information and panel information assigned to the SN. In some configurations, H equals T (T≠0). In this case, a one-to-one mapping can be used to associate the time information and panel information assigned to the SN. In some configurations, H equals 1. In this case, the panel information is common to the beam information and / or time information assigned to the SN in the new / specific DCI. In some configurations, H equals 0. In this case, the new / specific DCI signaling does not include the panel information assigned to the SN. In some configurations, H can be implicitly obtained by the SN. For example, when the BS can configure / provide the SN with a list of starting positions for the panel indication fields assigned to the SN, as described in detail herein, the number of panel fields assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0181] In some implementations, the bit width of the panel indication field assigned to the SN in DCI signaling can have various configurations. In some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, when the BS can configure / provide to the SN a list of starting positions for the panel indication field assigned to the SN, as described in detail herein, the bit width of the panel field assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0182] In some implementations, the number (P) of polarization indication fields assigned to the SN and their bit width can be determined through various configurations. In some configurations, P equals L (L≠0). In this case, a one-to-one mapping can be used to associate the beam information and polarization information assigned to the SN. In some configurations, P equals T (T≠0). In this case, a one-to-one mapping can be used to associate the time information and polarization information assigned to the SN. In some configurations, P equals 1. In this case, the polarization information is common to the beam information and / or time information assigned to the SN in the new DCI. In some configurations, P equals 0. In this case, the new DCI signaling does not include the polarization information assigned to the SN. In some configurations, P can be implicitly obtained by the SN. For example, when the BS can configure / provide the SN with a list of starting positions for the polarization indication fields assigned to the SN, as described in detail herein, the number of polarization fields assigned to the SN can be implicitly obtained from the number of starting positions in that list.

[0183] In some implementations, the bit width of the polarization indicator field assigned to the SN in DCI signaling can have various configurations. In some configurations, the bit width can be a fixed value known to both the SN and the BS. In some configurations, the bit width can be a configurable value, configured / provided to each SN by the BS via RRC, MAC CE, or DCI signaling. In some configurations, the bit width can be implicitly obtained by the SN. For example, when the list of starting positions for the polarization indicator field assigned to the SN can be configured / provided to the SN by the BS, as described in detail herein, the bit width of the polarization field assigned to the SN can be implicitly obtained from the number of starting positions in the list.

[0184] In some implementations, the SN can determine the position of the corresponding allocated field in the DCI payload for each type of field. In some configurations, the starting position of the first allocated field within 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 starting position of the first allocated field within the DCI payload can be configured / provided to the SN by the BS. Since the number of corresponding allocated fields and the bit width of the corresponding fields can be known by the SN, the SN can obtain the corresponding allocation information from new DCI signaling.

[0185] In some configurations, the start position of the first allocated field and the end position of the last allocated field within 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 within the DCI payload can be configured / provided to the SN by the BS. When the number of fields is configured / provided to the SN, it may not be necessary to configure the corresponding field width, as it can be implicitly obtained by the SN. When the bit width of a field is configured / provided to the SN, it may not be necessary to configure the corresponding field number to the SN, as it can be implicitly obtained by the SN. In some configurations, the BS can configure / provide a list of start positions to the SN via at least one of RRC, MAC CE, or DCI signaling. Each start position corresponds to the start position of the allocated field within the DCI payload. In this case, the number of fields allocated to the SN can be implicitly obtained from the number of start positions configured / provided in the list. The bit width of each field can also be implicitly obtained by the SN because the allocated fields are consecutive for each type of field.

[0186] In some implementations, the SN can determine the size of a new / specific DCI signaling through various configurations. 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 monitored by the SN, such as DCI format 1_0. In some configurations, a special case is that, for each type of field, the size of the DCI can be implicitly calculated by the SN when the number of fields and their bit widths are the same and known to all SNs in the group, and when the SN can know / determine the number of SNs (the DCI includes information about these SNs).

[0187] In some implementations, the SN can determine the actual number of beam indicators and / or time indicators through various configurations. In some configurations, the number of beam indicators and / or time indicators can be determined through a specific implementation. For example, when configuring the RRC list of time resources, some time resources may be configured / provided with invalid time information, such as a duration of 0. Therefore, when the SN discovers / determines that a time indicator field refers to invalid time resource information, the SN can know / determine that the corresponding time indicator field and its associated beam information field 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 predefined for both the SN and the BS, or configured / provided to the SN by the BS through at least one of RRC, MAC CE, or DCI signaling. This invalid beam index / time index can be common to all SNs in the group, or it can be different for each SN. Thus, when the SN discovers / determines that the index of the corresponding field is a predefined invalid index, the SN knows / determines that the beam indicator field and its associated time indicator field are invalid.

[0188] In some implementations, the current DCI 2_8 can be enhanced with new field formats to indicate control information for a set of SNs. The aforementioned method for using new DCI signaling field formats to indicate control information for a set of SNs can also be applied to reusing DCI 2_8 signaling to indicate new field formats for control information for a set of SNs.

[0189] In some embodiments, group-related information can be configured / provided to the SN. Several implementations may need to be considered when taking into account that the BS can send / provide / transmit group signaling for a group of SNs. In some implementations, the BS can use group signaling to indicate control information for a group of SNs. To ensure that the SN knows that the monitored group signaling includes control information prepared for it, several configurations can be considered. For example, in some configurations, new specific parameters 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 indicates / indicates / notifies that group signaling is enabled for the SN. The SN should then monitor the group signaling and decode it to obtain the control information assigned to it. In some configurations, new group-specific parameters are defined for the SN to enable it to obtain control information from the group signaling. 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 described in detail herein, the number of beam index fields assigned in DCI 2_8 can be configured / provided to the SN. Once this parameter is configured / provided to the SN, it indicates / indicates / notifies that the group signaling function is enabled, and the SN should monitor the group signaling and decode it to obtain the control information assigned to it.

[0190] In some implementations, group-related information can be notified / provided to the SN. This information can include several configurations. In some configurations, the number of SNs in the group can be the total number of SNs in the group, or it can be the actual number of SNs within the group whose control information is included in the group signaling. For example, as described in detail herein, the number of SNs in the group can be configured / provided to the SN to help the SN determine the size of 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 group information to these three SNs. However, the group signaling may not always include control information for all three SNs. In this case, the actual number of SNs whose control information is included in the group signaling can be configured / provided to the SN.

[0191] In some configurations, a logical index can be configured / provided for the SN to represent its index within the group. This logical index can be used by the SN to obtain the location of the beam index field and the location of the time indication field assigned in the DCI 2_8 message. Furthermore, this logical 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, this logical index can be configured / provided to both the SN and the BS via OAM.

[0192] In some embodiments, priority can be configured / provided for a specific SN between unicast signaling and group signaling. There may be a scenario where an SN receives unicast signaling that includes only its own control information. 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 unicast and group signaling (e.g., different beam information indicating the same time resource in the two signaling sets), several configurations regarding the priority between these two signaling sets can be considered. In some configurations, the SN may follow the control information indicated in the most recently received signaling. In some configurations, group signaling takes precedence over unicast signaling. In some configurations, unicast signaling takes precedence over group signaling. In some configurations, signaling including a 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 this priority flag, this indicates / indicates / notifies that the group signaling has the highest priority. In some configurations, the control information indicated in both signaling sets can be manipulated by the SN. For example, when the beam information indicated in two signaling messages for the same time resource is different and the network node can support multiple beam operations simultaneously, the SN can use two beams to forward signals at the same time.

[0193] Now for reference Figure 10 A flowchart of a method 1000 for instructing control information to a network node (e.g., a network node number) is shown. This can be used in conjunction with... Figures 1 to 9 Method 1000 may be implemented using any of the detailed components and devices. In summary, method 1000 may include: sending / providing / transmitting a first message (1002), the first message indicating control information for a plurality of network nodes. Method 1000 may also include: receiving control information (1004).

[0194] At operation (1002), and in some arrangements, a wireless communication node (e.g., a base station (BS)) may send / provide / transmit a first message in downlink control information (DCI) to multiple network nodes (e.g., intelligent nodes (SN)), the first message indicating control information configured / provided for the multiple network nodes respectively.

[0195] In some configurations, one or more corresponding beam index fields and one or more corresponding time indication fields configured / provided in the DCI are configured for each of the multiple network nodes.

[0196] In some configurations, this wireless communication method may include configuring / providing one or more corresponding beam index fields for each of a plurality of network nodes, wherein the one or more corresponding beam index fields may be continuous or non-contiguous. Similarly, configuring / providing one or more corresponding time indication fields for each of a plurality of network nodes may be continuous or non-contiguous. The term “contiguous” only means that the assigned beam information field and the assigned time resource indication field are continuous. This does not mean that the information indicated in the corresponding fields is or must be “contiguous”. For example, if a SN is assigned two consecutive beam index fields, this means / indicates / notifies that the SN has been assigned beam index field X and beam index field X+1. This does not mean that the information indicated in the two beam index fields is or must be beam index Y and beam index Y+1.

[0197] In some implementations, multiple time indication fields in the DCI can be shared and used by multiple network nodes. For example... Figure 9 As shown, time indicator 1 is associated with beam index fields 1, 2, and 3, and time indicator 2 is associated with beam index fields 4, 5, and 6. Furthermore, the time indicator fields in the DCI are shared by the three SNs.

[0198] In some configurations, each of the multiple network nodes can be configured / provided with one or more corresponding beam index fields in the DCI. The one or more corresponding beam index fields configured / provided for each of the multiple network nodes can be consecutive or non-consecutive. In some configurations, each time indication field can be associated with one or more beam index fields. The one or more beam index fields associated with each time indication field can be used separately for one or more of the multiple network nodes.

[0199] In some configurations, multiple beam index fields in the DCI can be reinterpreted as / reused as / redefined as multiple beam pattern index fields in the DCI. Multiple time indication fields can be shared and used by one or more network nodes among the multiple network nodes. In some configurations, each beam pattern index field among the multiple beam pattern index fields can be sequentially associated with a corresponding time indication field among the multiple time indication fields in a one-to-one mapping. Furthermore, in some configurations, a beam pattern list can be configured / provided to each of the multiple network nodes, and the beam pattern list can include one or more beam patterns. As described in detail herein, the beam pattern list can be configured / provided by the BS to the SN via at least one of RRC, MAC CE, or DCI signaling, or it can be configured / provided to both the SN and the BS via OAM signaling / protocol.

[0200] In some configurations, each of the plurality of beam patterns may include one or more beam indices. The one or more beam indices in each of the plurality of beam patterns may be assigned to one or more network nodes among the plurality of network nodes. In some implementations, the beam pattern list may 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 is sent in a new / specific DCI format.

[0201] In some configurations, the DCI can be configured / provided to indicate control information for the plurality of network nodes using at least one of the following: For example, a new RNTI can be configured / provided to scramble the DCI indicating control information for the plurality of network nodes. Similarly, a conventional RNTI can be configured / provided to scramble the DCI with one or more values, one of which is configured / provided to scramble the DCI indicating control information for one network node, and one or more other values ​​are configured / provided to scramble the DCI indicating control information for the plurality of network nodes. The DCI indicating control information for the plurality of network nodes can be configured / provided to be monitored in a common search space. Furthermore, new dedicated parameters can be configured / provided to the plurality of network nodes to distinguish whether the DCI is configured / provided to indicate control information for the plurality of network nodes or control information for one network node.

[0202] In some configurations, the first message may be sent in a new DCI signaling format. The new DCI signaling may be scrambled using at least one of the following: For example, a new RNTI (e.g., ncr-G-RNTI) may be used for scrambling. Furthermore, a conventional RNTI configured / provided for scrambling the DCI may have multiple values, one of which is configured / provided to scramble the DCI indicating control information for a network node, and one or more other values ​​may be configured / provided to scramble the new DCI signaling indicating control information for the multiple network nodes. Each SN may be configured / provided with one or more ncr-G-RNTI values, for example, 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 the SN. This parameter may be predefined or configured / provided by the BS. When an SN is configured / provided with multiple ncr-G-RNTI values, it means that the SN is configured / provided to multiple groups, and each group has a different ncr-G-RNTI value.

[0203] In some configurations, the format may include or consist of multiple blocks, wherein each of the plurality of network nodes may be configured / provided with a corresponding block of the plurality of blocks. Each block may also include 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 fields in each of the plurality of blocks may be either one-to-one mappings or one-to-many mappings.

[0204] In some configurations, the format may include multiple blocks, wherein each network node may be configured / provided with one or more of the multiple blocks. Each block may further include 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.

[0205] In some configurations, the format may include multiple blocks and multiple time resource indication fields, wherein each of the multiple network nodes may be configured / provided with a corresponding block of the multiple blocks. Each block may further include 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, the multiple time resource indication fields may be shared by the multiple network nodes.

[0206] In some configurations, the relationship between each of the plurality of time indication fields and a field of a different type in a corresponding block of the plurality of blocks configured / provided for the corresponding network node among the plurality of network nodes can be either a one-to-one mapping or a one-to-many mapping. Furthermore, the relationship between different types of fields in each of the plurality of blocks can be either a one-to-one mapping or a one-to-many mapping.

[0207] In some configurations, the format may include multiple blocks and multiple time resource indication fields, wherein each of the multiple network nodes may be configured / provided with one or more corresponding blocks among the multiple blocks. Each block may 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 multiple time resource indication fields may be shared by the multiple network nodes. Furthermore, the relationship between each of the multiple time indication fields and the corresponding one or more blocks configured / provided for the corresponding network node among the multiple network nodes may be a one-to-one mapping or a one-to-many mapping.

[0208] In some configurations, the format may include at least one of the following: one or more beam indication fields, one or more time 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. Each of the plurality of network nodes may be configured / provided with corresponding one or more beam indication fields, one or more time indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields. In some configurations, the plurality of beam indication fields, the plurality of time indication fields, the plurality of frequency indication fields, the plurality of power indication fields, the plurality of panel indication fields, and the plurality of polarization indication fields configured / provided for corresponding network nodes in the plurality of network nodes may be continuous or non-continuous. The relationship between different types of fields configured / provided for corresponding network nodes in the plurality of network nodes may be a one-to-one mapping or a one-to-many mapping.

[0209] In some configurations, the format may include at least one of the following: one or more beam indication fields, one or more time 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. Each of the plurality of network nodes may be configured / provided with corresponding one or more beam indication fields, corresponding one or more frequency indication fields, corresponding one or more power indication fields, corresponding one or more panel indication fields, and corresponding one or more polarization indication fields. The one or more time indication fields configured / provided in the DCI may be shared by the plurality of network nodes. In some configurations, the plurality of beam indication fields, frequency indication fields, power indication fields, panel indication fields, and polarization indication fields configured / provided for corresponding network nodes in the plurality of network nodes may be continuous or non-continuous. The relationship between each of the plurality of time indication fields and the corresponding beam indication field, frequency indication field, power indication field, panel indication field, and polarization indication field configured / provided for the corresponding network node in the plurality of network nodes may be a one-to-one mapping or a one-to-many mapping. Similarly, the relationship between different types of fields configured / provided for corresponding network nodes among the multiple network nodes can be a one-to-one mapping or a one-to-many mapping.

[0210] In some configurations, each of the plurality of network nodes may be configured / provided with one or more specific parameters for obtaining the control information. Each of the plurality of network nodes may be configured / provided to obtain the control information through at least one of the following methods: new dedicated parameters for the network node, or implicit knowledge through one or more specific parameters. When the one or more specific parameters are configured / provided to the network node, the network node can know / determine that the first message includes control information assigned to the network node.

[0211] In some configurations, relevant information can be configured / provided to each of the plurality of network nodes to monitor and decode the first message. The relevant information may include at least one of the following: a logical index representing the corresponding network node, or the number of the plurality of network nodes configured / provided with the control information. The relevant information can be configured / provided from the wireless communication node to the network node via at least one of the following: RRC, MAC CE, or DCI signaling.

[0212] At least one aspect relates to a system, method, apparatus, or computer-readable medium. The wireless communication method may include: a wireless communication node sending / providing / transmitting a second message to one of a plurality of network nodes, the second message indicating control information configured / provided for the network node. Furthermore, when the control information indicated in the first message contradicts the control information indicated in the second message for the same network node, the priority between the first message and the second message may 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 the message including a priority flag in both the first message and the second message has the highest priority.

[0213] While various embodiments of the present solution have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the solution is not limited to the illustrated exemplary architectures or configurations, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0214] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of elements. Therefore, references to the first and second elements do not imply that only two elements can be used or that the first element must precede the second element in some way.

[0215] Furthermore, those skilled in the art will 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 referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0216] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. 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 technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation will not depart from the scope of this disclosure.

[0217] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by an integrated circuit (IC), which may 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 devices or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration that performs the functions described herein.

[0218] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium that enables the transfer of computer programs or code from one location to another. Storage media can be any available medium that is accessible to 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 the required program code in the form of instructions or data structures and that is accessible to a computer.

[0219] 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. Furthermore, for purposes of discussion, various modules are described as separate modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of this solution.

[0220] Furthermore, memory or other storage devices and communication components may be used in embodiments of this solution. It should be understood that, for clarity, the above description refers to embodiments of this solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality among different functional units, processing logic elements, or domains can be used without diminishing the effectiveness of this solution. For example, a function shown to be performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functionality and do not indicate a strict logical or physical structure or organization.

[0221] Various modifications to the embodiments described in this disclosure will be 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. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is accorded the broadest scope consistent with the novel features and principles disclosed herein as set forth in the appended claims.

Claims

1. A wireless communication method, comprising: A first message is sent from a wireless communication node to multiple network nodes, the first message indicating control information configured for each of the multiple network nodes.

2. The wireless communication method according to claim 1, wherein, The first message was sent in the DCI.

3. The wireless communication method according to claim 2, in, One or more corresponding beam index fields and one or more corresponding time indication fields in the DCI are configured for each of the plurality of network nodes.

4. The wireless communication method according to claim 3, in, The one or more corresponding beam index fields configured for each of the plurality of network nodes are either continuous or non-contiguous; and The one or more corresponding time indication fields configured for each of the plurality of network nodes are either continuous or non-continuous.

5. The wireless communication method according to claim 2, in, The multiple time indication fields in the DCI are shared and used by the multiple network nodes.

6. The wireless communication method according to claim 5, in, Each of the plurality of network nodes is configured with one or more corresponding beam index fields in the DCI; and Wherein, the one or more corresponding beam index fields configured for each of the plurality of network nodes are either continuous or non-continuous.

7. The wireless communication method according to claim 5, in, Each time indication field in the DCI is associated with one or more beam index fields; and The one or more beam index fields associated with each time indication field are used for one or more of the plurality of network nodes.

8. The wireless communication method according to claim 2, in, The multiple beam index fields in the DCI are reinterpreted as multiple beam pattern index fields in the DCI; and Among them, multiple time indication fields are shared and used by one or more network nodes among the multiple network nodes.

9. The wireless communication method according to claim 8, wherein, Each of the plurality of beam pattern index fields is sequentially associated with a corresponding time indication field among the plurality of time indication fields in a one-to-one mapping manner.

10. The wireless communication method according to claim 8, in, A list of beam patterns is configured for each of the plurality of network nodes; and The beam pattern list includes one or more beam patterns.

11. The wireless communication method according to claim 10, wherein, Each of the plurality of beam patterns includes one or more beam indices, and wherein the one or more beam indices in each of the plurality of beam patterns are respectively assigned to one or more network nodes among the plurality of network nodes.

12. The wireless communication method according to 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 according to claim 1, wherein, The first message is sent in the new DCI format.

14. The wireless communication method according to any one of claim 2 or claim 13, wherein, The DCI is configured to indicate the control information for the plurality of network nodes by at least one of the following: A new RNTI, configured to scramble the DCI indicating the control information for the plurality of network nodes; A conventional RNTI is configured to scramble the DCI with one or more values, wherein one of the multiple values ​​is configured to scramble the DCI indicating control information for a network node, and one or more other values ​​of the multiple values ​​are configured to scramble the DCI indicating control information for the multiple network nodes. The DCI, which indicates control information for the plurality of network nodes, is configured to monitor in a common search space; New dedicated parameters are configured for the plurality of network nodes, which are used to distinguish whether the DCI is configured to indicate control information for the plurality of network nodes or for a single network node.

15. The wireless communication method according to claim 1, wherein, The first message is sent in the new DCI signaling format.

16. The wireless communication method according to claim 15, wherein, The new DCI signaling is scrambled by at least one of the following: The new RNTI; or The conventional RNTI is configured to scramble the DCI with multiple values, wherein one of the multiple values ​​is configured to scramble the DCI indicating control information for a network node, and one or more other values ​​of the multiple values ​​are configured to scramble the new DCI signaling indicating control information for the multiple network nodes.

17. The wireless communication method according to any one of claim 13 or claim 15, in, The format includes multiple blocks, and each of the multiple network nodes is configured with a corresponding block from the multiple blocks; and Each of the plurality of blocks further includes 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 indicator fields; or One or more polarization indicator fields.

18. The wireless communication method according to claim 17, wherein, The relationships between different types of fields in each of the multiple blocks are either one-to-one mappings or one-to-many mappings.

19. The wireless communication method according to any one of claim 13 or claim 15, in, The format includes multiple blocks, and each of the multiple network nodes is configured with one or more corresponding blocks from the multiple blocks; and Each of the plurality of blocks further includes 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.

20. The wireless communication method according to any one of claim 13 or claim 15, in, The format includes multiple blocks and multiple time resource indication fields, and each of the multiple network nodes is configured with a corresponding block from the multiple blocks; and Each of the plurality of blocks further includes 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 indicator fields; or One or more polarization indicator fields.

21. The wireless communication method according to claim 20, wherein, Multiple time resource indication fields are shared by the multiple network nodes.

22. The wireless communication method according to claim 20, wherein, The relationship between each of the plurality of time indication fields and a field of a different type configured for the corresponding network node in one of the plurality of blocks is either a one-to-one mapping or a one-to-many mapping.

23. The wireless communication method according to claim 20, wherein, The relationships between different types of fields in each of the multiple blocks are either one-to-one mappings or one-to-many mappings.

24. The wireless communication method according to any one of claim 13 or claim 15, in, The format includes multiple blocks and multiple time resource indication fields, and each of the multiple network nodes is configured with one or more corresponding blocks from the multiple blocks; and Each of the plurality of blocks further includes 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.

25. The wireless communication method according to claim 24, wherein, The multiple time resource indication fields are shared by the multiple network nodes.

26. The wireless communication method according to claim 24, wherein, The relationship between each of the plurality of time indication fields and the corresponding one or more blocks configured for the corresponding network node in the plurality of blocks is a one-to-one mapping or a one-to-many mapping.

27. The wireless communication method according to any one of claim 13 or claim 15, in, The format includes at least one of the following: one or more beam indication fields, one or more time indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields; and Each of the plurality of network nodes is configured with one or more beam indication fields, one or more time indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields.

28. The wireless communication method according to claim 27, wherein, The plurality of beam indication fields, the plurality of time indication fields, the plurality of frequency indication fields, the plurality of power indication fields, the plurality of panel indication fields, and the plurality of polarization indication fields configured for corresponding network nodes among the plurality of network nodes may be continuous or discontinuous.

29. The wireless communication method according to claim 27, wherein, The relationship between different types of fields configured for corresponding network nodes among the multiple network nodes is a one-to-one mapping or a one-to-many mapping.

30. The wireless communication method according to any one of claims 13 or 15, in, The format includes at least one of the following: one or more beam indication fields, one or more time indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields; Each of the plurality of network nodes is configured with one or more beam indication fields, one or more frequency indication fields, one or more power indication fields, one or more panel indication fields, and one or more polarization indication fields; and The one or more time indication fields configured in the DCI are shared by the plurality of network nodes.

31. The wireless communication method according to claim 30, wherein, The multiple beam indication fields, multiple frequency indication fields, multiple power indication fields, multiple panel indication fields, and multiple polarization indication fields configured for corresponding network nodes among the multiple network nodes may be continuous or discontinuous.

32. The wireless communication method according to claim 30, wherein, The relationship between each of the plurality of time indication fields and the corresponding beam indication field, frequency indication field, power indication field, panel indication field and polarization indication field configured for the corresponding network node among the plurality of network nodes is a one-to-one mapping or a one-to-many mapping.

33. The wireless communication method according to claim 30, wherein, The relationship between different types of fields configured for corresponding network nodes among the multiple network nodes is a one-to-one mapping or a one-to-many mapping.

34. The wireless communication method according to claim 1, wherein, Each of the plurality of network nodes is configured with one or more specific parameters for obtaining the control information.

35. The wireless communication method according to any one of claim 1 or claim 34, wherein, Each of the plurality of network nodes is configured to obtain the control information by at least one of the following: New dedicated parameters for the network nodes; Implicitly known through one or more specific parameters, when said one or more specific parameters are configured to the network node, the network node can know that the first message includes control information assigned to the network node.

36. The wireless communication method according to claim 1, wherein, The relevant information is configured for each of the plurality of network nodes to monitor and decode the first message; The relevant information includes at least one of the following: Represents the logical index of the corresponding network node among the plurality of network nodes; or The number of the plurality of network nodes configured with the control information.

37. The wireless communication method according to claim 36, wherein, The relevant information is configured from the wireless communication node to the network node via at least one of the following: RRC, MAC CE, or DCI signaling.

38. The wireless communication method according to claim 1, further comprising: The wireless communication node sends a second message to one of the plurality of network nodes, the second message indicating control information configured for the network node.

39. The wireless communication method according to claim 38, wherein, When the control information indicated in the first message contradicts the control information indicated in the second message for the same network node, the priority between the first message and the second message includes at least one of the following: 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 The message containing the priority flag in the first message and the second message has the highest priority.

40. A wireless communication method, comprising: At least one of a plurality of network nodes receives a first message from a wireless communication node, the first message indicating control information configured for each of the plurality of network nodes; The wireless communication node is communicatively coupled to each of the plurality of network nodes through at least one of the following: 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 the following: a third forwarding link or a fourth forwarding link.

41. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 40.

42. A computer program product comprising a computer-readable program medium storing code, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 40.

Images