Method and apparatus for scheduling transmissions of multiple devices

Abstract

This disclosure describes methods, systems, and apparatus for scheduling transmissions across multiple devices. The method may include: configuring a single downlink control information (DCI) by a radio access network node (WANN) to schedule transmissions across a set of user equipment (UEs). At least a portion of the scheduling information for one UE in the UE set and at least a portion of the scheduling information for another UE in the UE set are configured separately in the single DCI. The method may also include: the WANN transmitting the single DCI to the UE set.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication. Specifically, this disclosure relates to methods and apparatus for scheduling transmissions of multiple devices. Background Technology

[0002] In the development of communication technology, a large number of devices are interconnected in scenarios such as virtual reality and smart healthcare, and collaborative transmission between multiple devices has become a new direction for the development of communication technology.

[0003] Furthermore, with the rapid development of mobile internet and the growth of smart devices, mobile data traffic has surged. High-density hotspots such as stadiums, shopping malls, and transfer stations are facing increasing pressure from multi-device transmission. These multiple devices may collaborate or transmit independently. In any case, they need to support large data volumes and high transmission reliability. The evolution of fifth-generation and sixth-generation communication technologies will necessitate efficient multi-device transmission technologies.

[0004] Whether the transmissions of multiple devices are independent or collaborative, efficient scheduling of these transmissions is essential. Therefore, how to schedule multiple devices is a fundamental problem that needs to be studied and solved. Summary of the Invention

[0005] This disclosure relates to methods and apparatus for wireless communication, and more specifically, to methods and apparatus for scheduling transmissions of multiple devices such as user equipment (UE). Various embodiments in this disclosure contribute to optimizing scheduling performance in wireless communication systems.

[0006] In one embodiment, this disclosure describes a method for wireless communication. The method may include: configuring a single downlink control information (DCI) by a wireless access network node (WANN) to schedule transmissions of a set of user equipment (UEs). At least a portion of the scheduling information for one UE in the UE set and at least a portion of the scheduling information for another UE in the UE set are configured separately in the single DCI. The method may further include: the WANN transmitting the single DCI to the UE set.

[0007] In another embodiment, this disclosure describes a method for wireless communication. The method may include: receiving a single downlink control DCI from a radio access network node (WANN) by a first user equipment (UE). The single DCI may be configured to schedule transmissions of a set of UEs including the first UE. At least a portion of the scheduling information for one UE in the set of UEs and at least a portion of the scheduling information for another UE in the set of UEs may be configured separately within the single DCI.

[0008] In another embodiment, an apparatus for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to implement the method described above.

[0009] In another embodiment, a device for wireless communication may include a memory storing instructions and processing circuitry communicating with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to implement the method described above.

[0010] In another embodiment, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. The computer-readable medium includes a non-transient computer-readable medium.

[0011] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0012] Figure 1 An example system of a wireless communication network is shown.

[0013] Figure 2 An example base station is shown schematically.

[0014] Figure 3 An example user device is illustrated schematically.

[0015] Figure 4 A flowchart of an example method for wireless communication is shown.

[0016] Figure 5 This shows an example layout of the DCI field in the group public DCI.

[0017] Figure 6 Another example layout of the DCI field in the group public DCI is shown.

[0018] Figure 7 Another example layout of the DCI field in the group public DCI is shown.

[0019] Figure 8 An example index of the DCI field in the group public DCI is shown.

[0020] Figure 9 A flowchart of an example method for wireless communication is shown. Detailed Implementation

[0021] This disclosure will now be described in detail with reference to the accompanying drawings, which form a part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be implemented in a variety of different forms, and therefore, the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0022] Throughout the specification and claims, terms may have suggestive or implied meanings in the context, in addition to their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, exemplary embodiments or combinations of embodiments.

[0023] Generally, terms can be understood at least in part from their use in context. For example, terms used herein, such as “and,” “or,” or “and / or,” can include a variety of meanings, which can depend at least in part on the context in which these terms are used. Typically, “or,” when used in an associative list, such as A, B, or C, means A, B, and C in an inclusive sense, and A, B, or C in an exclusive sense. Furthermore, the terms “one or more” or “at least one,” as used herein, can be used, at least in part on context, to describe any feature, structure, or characteristic in a singular sense, or to describe a combination of features, structures, or characteristics in a plural sense. Similarly, terms such as “a,” “an,” or “the” can also be understood to convey either a singular or a plural usage, at least in part on context. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather to allow for the existence of additional factors that are not necessarily explicitly described, which, too, depends at least in part on the context.

[0024] This disclosure describes a method and apparatus for scheduling transmissions across multiple devices.

[0025] The main idea behind user collaboration technology is to aggregate multiple users for collaborative transmission. In user collaboration transmission, multiple devices are divided into anchor devices and auxiliary devices. The auxiliary devices assist the anchor devices in data transmission. Based on the collaborative relationship between the auxiliary and anchor devices, collaborative transmission is divided into data replication collaboration, data splitting collaboration, and wireless backup collaboration. In data replication collaboration, the anchor device and auxiliary device transmit the same data, primarily to improve the reliability of data transmission from the anchor device. In data splitting collaboration, the anchor device and auxiliary device transmit different data packets, primarily to improve the data transmission rate. In wireless backup collaboration, the auxiliary device only forwards the anchor device's data to the base station when the anchor device loses power. In collaborative transmission, due to the collaborative relationship between devices, using a single DCI to simultaneously schedule the transmission of multiple devices is a natural way to improve transmission efficiency.

[0026] For independent transmission by multiple devices, the basic scheduling scheme is to use a separate DCI to schedule the transmission of each device. However, in some hotspot areas (e.g., venues for large performances or popular tourist attractions), hundreds of devices may need to be scheduled for transmission. Using a separate DCI to schedule the transmission of each device may lead to Physical Downlink Control Channel (PDCCH) congestion, which will significantly affect the user experience in hotspot areas. Therefore, using a single DCI to schedule the transmission of multiple devices can be a method to reduce PDCCH overhead, thereby reducing the probability of PDCCH congestion and ensuring user experience.

[0027] Several DCI formats exist in existing protocols for scheduling the Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), or Physical Downlink Shared Channel (PDSCH). For example, as shown in Table 7.3.1-1 of 3GPP TS38.212 (reprinted below), the DCI format 0_0 / 0_2 / 1_0 / 1_2 is used to schedule one PUSCH / PDSCH within a cell. The fields in these DCI formats only indicate the information transmitted for one PUSCH / PDSCH.

[0028] DCI formats 4_0 / 4_1 / 4_2 are used for downlink broadcast or multicast scheduling. Fields in these DCI formats indicate information specific to multiple PDSCH transmissions. However, since broadcast or multicast PDSCH transmissions are identical, transmission information can be indicated in a single field.

[0029] The DCI formats 0_3 and 1_3 introduced in Rel-18 are used to schedule one PUSCH / PDSCH of a device in a cell, or to schedule multiple PUSCH / PDSCH of a device in multiple cells (where one PUSCH / PDSCH is per cell).

[0030] DCI formats 2_0 / 2_1 / 2_2 / 2_3 / 2_4 / 2_5 / 2_6 / 2_7 / 2_8 / 2_9 and DCI formats 3_0 / 3_1 / 3_2 are used to transmit some special information.

[0031] Table 7.3.1-1: DCI Format

[0032] In short, none of the existing DCI formats in current protocols can meet the requirements for scheduling multiple PUSCH transmissions for cooperating devices, or for scheduling multiple independent PDSCH / PUSCH transmissions for multiple devices. One of the purposes of this disclosure is to use a single DCI to schedule multiple PUSCH / PDSCH transmissions for multiple devices, thereby ensuring uplink transmission performance and user experience in hotspot areas during cooperative transmissions.

[0033] This disclosure provides various embodiments for discussing how to schedule multiple PUSCH / PDSCH transmissions from multiple devices using a single DCI. As detailed below, a group common DCI is defined for multi-device transmission. For the design of the group common DCI, the classification enhancement of the DCI fields enables the indication of different information for different devices. Furthermore, by enhancing the indication information of device combinations and the location information of the DCI fields, each device can accurately obtain its own transmission scheduling information from the group common DCI and further execute the corresponding transmission.

[0034] Using the methods and apparatus described in this disclosure, multiple PUSCH / PDSCH transmissions from multiple devices can be scheduled using a single DCI. This ensures the transmission performance of cooperative transmissions and / or users in hotspot areas, and achieves multi-user transmission gain at this stage.

[0035] A radio access network provides network connectivity between user equipment and information or data networks (e.g., voice or video communication networks, the Internet, etc.). Example radio access networks may be based on cellular technology, which may further be based on, for example, 5G NR technology and / or formats. Figure 1 An example system diagram of a wireless communication network 100, comprising multiple user equipment (UEs) 122 / 124 / 126 / 128 and a wireless access network node (WANN) 110, is shown according to various embodiments. The UEs 122 / 124 / 126 / 128 may include, but are not limited to, mobile phones, smartphones, tablets, laptops, smart electronic devices or appliances including air conditioners, televisions, refrigerators, ovens, etc., or other devices capable of wireless communication over the network.

[0036] WANN 110 may include a wireless network base station or an NG (Next Generation) radio access network (NG-RAN) base station or node, which in the mobile communication context may include a node B (NB, such as a gNB)). Each type of these radio access network nodes can be configured to perform a corresponding set of wireless network functions. The wireless network function sets between different types of radio access network nodes may not be entirely identical. However, the wireless network function sets between different types of radio access network nodes may overlap functionally.

[0037] For simplicity and clarity, only one WANN and four UEs are shown in the wireless communication network 100. It will be understood that one or more WANNs may exist in the wireless communication network, and each WANN can serve one or more UEs simultaneously. In addition to UEs and WANNs, network 100 may also include any other network nodes with different functions, such as network nodes in the core network of wireless communication network 100. Furthermore, although various embodiments will be discussed in the context of the specific example wireless communication network 100, the basic principles apply to other applicable wireless communication networks.

[0038] Figure 2 An example of an electronic device 200 implementing a wireless access network node (e.g., WANN 110) is shown. This example electronic device 200 may include wireless transmit / receive (Tx / Rx) circuitry 208 for communicating with a UE and / or other WANNs. The electronic device 200 may also include network interface circuitry 209 to enable the WANN to communicate with other WANNs and / or the core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The electronic device 200 may optionally include input / output (I / O) interfaces 206 for communication with operators, etc.

[0039] Electronic device 200 may also include system circuitry 204. System circuitry 204 may include one or more processors 221 and / or memory 222. Memory 222 may include operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for use by one or more processors 221 to perform functions of the network node. Parameters 228 may include parameters that support the execution of instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0040] Figure 3 An example of an electronic device 300 implementing a user equipment (e.g., UE 122 / 124 / 126 / 128) is shown. The electronic device 300 may include a communication interface 302, system circuitry 304, input / output (I / O) interface 306, display circuitry 308, and storage device 309. Display circuitry 308 may include a user interface 310. System circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuit. System circuitry 304 may be implemented, for example, using one or more systems-on-a-chip (SoC), application-specific integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuitry 304 may be part of an implementation of any desired functionality within the electronic device 300. In this regard, system circuitry 304 may include logic that facilitates, for example, decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (as an example, for internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 310. User interface 310 and input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic outputs, voice or facial recognition inputs, buttons, switches, speakers, and other user interface elements. Additional examples of I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.

[0041] Communication interface 302 may include radio frequency (RF) transmitting (Tx) and receiving (Rx) circuitry 316, which processes the transmission and reception of signals via one or more antennas 314. Communication interface 302 may include one or more transceivers. These transceivers may be wireless transceivers, including modulation / demodulation circuitry, digital-to-analog converters (DACs), shapers, analog-to-digital converters (ADCs), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium. Transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK (Quadrature Phase Shift Keying), 16-QAM (Quadrature Amplitude Modulation), 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, communication interface 302 may include a transceiver supporting transmission and reception under the following standards: 2G (the 2nd generation mobile communication technology), 3G (the 3rd generation mobile communication technology), Bluetooth (BT), WiFi (wireless fidelity), Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, 4G / Long Term Evolution (LTE), 5G standard, 6G standard, or other telecommunications standards. However, the technologies described below, whether derived from 3GPP, the GSM (Global System for Mobile Communications) Association, 3GPP2, IEEE (Institute of Electrical and Electronics Engineers), or other partners or standards bodies, are applicable to other wireless communication technologies.

[0042] System circuitry 304 may include one or more processors 321 and memory 322. Memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. Processor 321 is configured to execute instructions 326 to achieve the desired functionality of electronic device 300. Parameters 328 can provide and specify configuration and operational options for instructions 326. Memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that electronic device 300 will send or has received via communication interface 302. In various embodiments, system power for electronic device 300 may be provided by power storage devices such as batteries or transformers.

[0043] This disclosure describes various embodiments for scheduling transmissions across multiple devices, which may be partially or wholly described above. Figures 1 to 3 Implemented on the WANN and / or UE as described in the document.

[0044] Reference Figure 4 This disclosure describes various embodiments of a method 400 for scheduling transmissions of multiple UEs in wireless communication. The method 400 may include some or all of the following operations: In step 410, WANN 110 can configure a single DCI to schedule transmissions for a set of UEs. At least a portion of the scheduling information for one UE in the UE set and at least a portion of the scheduling information for another UE in the UE set are configured separately in this single DCI. For example, the UE set may include a first UE 122 and a second UE 124. The single DCI may include first scheduling information configured for the first UE 122 and second scheduling information configured for the second UE 124. The first and second scheduling information can be configured separately in this single DCI. In one example, the configured first scheduling information may be different from the configured second scheduling information. In another example, the configured first scheduling information may be the same as the configured second scheduling information. In step 420, WANN 110 can transmit the configured single DCI to the UE set.

[0045] In some implementations, the UE set may be configured with the same radionetwork temporary identifier (RNTI), and the RNTI may be used for a single DCI scrambling.

[0046] In some implementations, the transmission of a UE set is either multiple independent unicast transmissions or UE cooperative transmissions. In UE cooperative transmissions, information is exchanged between UE sets via UE-to-UE interfaces.

[0047] In some implementations, for a specific schedule, the WANN 110 can identify a subset of UEs from the UE set, each subset being a specific combination of UEs within that UE set. At least a portion of the scheduling information in the single DCI is configured individually for each UE in that subset.

[0048] In some implementations, the single DCI may include a UE combination indicator field that indicates a subset of the identified UEs.

[0049] In some implementations, the WANN 110 can be configured with an identifier for each UE in the UE set, and the UE combination indicator field indicates the UE subset by the identifier of the UE in the UE subset.

[0050] In some implementations, the UE combination table may include multiple predetermined entries, each indicating a different subset of UEs. The UE combination indicator field can indicate the identified subset of UEs by indexing the entry in the UE combination table corresponding to that subset of UEs.

[0051] In some implementations, the UE combination indicator field may include a bitmap indicating the identified subset of UEs.

[0052] In some implementations, the single DCI may include multiple fields. The WANN 110 may classify these multiple fields into multiple field types based on the scheduling information configured for the UE set within these fields.

[0053] These multiple field types can include a first field type, a second field type, and a third field type. For a field with a first field type, the scheduling information in that field is configured publicly for each UE in the UE set. For example, all UEs in the UE set have the same or common field value for that field. A field with a first field type can be referred to as a common DCI field. For a field with a second field type, the scheduling information in that field is configured individually for each UE in the UE set. For example, different UEs in the UE set can configure individual field values ​​for the same field. Individual field values ​​can be the same or different from each other. A field with a second field type can be referred to as a specific DCI field. If a field has a third field type, then that field can be configurably specified by the WANN 110 as belonging to either the first or second field type based on the transmission scheme or specific scenario. A field with a third field type can be referred to as a configured DCI field.

[0054] In some implementations, the WANN 110 can determine the field type of each field in the single DCI based on the transmission scheme applied to the UE set. The WANN 110 can then transmit signaling carrying information about the determined field types to the UE set.

[0055] In some implementations, the WANN 110 can predefine the field type of each field in the single DCI based on the transport scheme.

[0056] In some implementations, when a field of a single DCI belongs to a second field type, the WANN 110 can configure a field value combination table for that field. This field value combination table can include multiple predetermined entries with different value combinations. Each entry can indicate a combination of individual field values ​​for that field, and the independent values ​​in that entry are configured for different UEs within the UE set. The independent values ​​can be the same or different from each other. The WANN 110 can then assign an index of the field value combination table to that field of the single DCI. In this way, the single DCI does not need to include different field values ​​configured for different UEs, thereby reducing the size of the single DCI.

[0057] In some implementations, for each UE in the UE set, WANN 110 may transmit UE-specific signaling to that UE carrying UE-specific location information, which locates a field in the single DCI configured for that specific UE. For example, WANN 110 may transmit signaling to UE 122 carrying first location information, which locates a field in the single DCI configured for UE 122, and transmit another signaling to UE 124 carrying second location information, which locates a field in the single DCI configured for UE 124. The first location information may not include information locating a field in the single DCI specifically configured for UE 124. Similarly, the second location information may not include information locating a field in the single DCI specifically configured for UE 122.

[0058] The UE-specific location information for the location field may include each common DCI field of that particular UE, the start position of each specific DCI field, and the length of each field. This signaling may be Radio Resource Control (RRC) signaling or another higher-level signaling.

[0059] In some implementations, when the fields in the first field block belong to a first field type, the WANN 110 can transmit common signaling carrying information locating the first field block in the single DCI. Each field in the first field block can be configured with a common field value for the UE set. The information locating the first field block may include the start position of the first field block in the single DCI and the length of the first field block.

[0060] In some implementations, when the fields in the second field block belong to the second field type, for each UE in the UE set, the WANN 110 can transmit specific signaling to that UE carrying information locating the second field block in the single DCI. Each field in the second field block can be configured with a separate field value for each UE in the UE set. The information locating the second field block may include the start position of each field in the second field block configured for that UE and the length of that field configured for that UE.

[0061] In some implementations, when the transmission of the UE set is a cooperative transmission, an index can be defined for each UE in the UE set. Thus, the position of a field configured for that UE within a single DCI can be determined by the UE's index and the length of that field.

[0062] In some implementations, the WANN 110 can split the scheduling information in a single DCI into multiple scheduling information parts and transmit these multiple scheduling information parts separately to the UE set. For example, the WANN 110 can split the scheduling information in a single DCI into two scheduling information parts (i.e., a first scheduling information part and a second scheduling information part). For example, the WANN 110 can first transmit a message carrying the first scheduling information part to the UE set, and then transmit another message carrying the second scheduling information part to the UE set.

[0063] These multiple scheduling information portions can be transmitted through different channels. For example, the first scheduling information portion can be transmitted on the control channel, while the second scheduling information portion can be transmitted on the data transmission channel.

[0064] In some implementations, the first scheduling information portion may include scheduling information that is commonly configured for each UE in the UE set. That is, the scheduling information in the first scheduling information portion is common or the same for all UEs in the UE set. The WANN 110 may transmit a common message carrying the first scheduling information portion to the UE set.

[0065] The second scheduling information section may include scheduling information configured individually for each UE in the UE set. In other words, the scheduling information in the second scheduling information section is specific to each UE in the UE set. Thus, the WANN 110 can transmit a specific message carrying the second scheduling information to each UE in the UE set individually.

[0066] Reference Figure 9 This disclosure describes various embodiments of a method 900 for wireless communication. The method 900 may include some or all of the following operations: In step 910, UE 122 may receive a single DCI from WANN 110. This single DCI may be configured by WANN 110 for scheduling transmissions of a set of UEs including UE 122. At least a portion of the scheduling information of one UE in the set of UEs and at least a portion of the scheduling information of another UE in the set of UEs are configured separately in this single DCI.

[0067] In some implementations, the UE set may be configured with the same Radio Network Temporary Identifier (RNTI), and the RNTI may be used for a single DCI scrambling.

[0068] In some implementations, the transmission of a UE set is either multiple independent unicast transmissions or UE cooperative transmissions. In UE cooperative transmissions, information is exchanged between UE sets via UE-to-UE interfaces.

[0069] In some implementations, for a specific schedule, the WANN 110 can identify a subset of UEs from the UE set, each subset being a specific combination of UEs within the UE set. At least a portion of the scheduling information in this single DCI is configured individually for each UE in that subset.

[0070] In some implementations, the single DCI may include a UE combination indicator field that indicates a subset of the identified UEs.

[0071] In some implementations, the UEs in the set are numbered, each UE in the UE set may have an identifier, and the UE combination indicator field indicates the UE subset by the identifier of the UE in the UE subset.

[0072] In some implementations, the UE combination table may include multiple predetermined entries, each indicating a different subset of UEs. The UE combination indicator field can indicate the identified subset of UEs by indexing the entry in the UE combination table corresponding to that subset of UEs.

[0073] In some implementations, the UE combination indicator field may include a bitmap indicating the identified subset of UEs.

[0074] In some implementations, the single DCI includes multiple fields, and these fields are categorized into multiple field types based on scheduling information configured for the UE set within these fields.

[0075] These multiple field types can include a first field type, a second field type, and a third field type. For a field with a first field type, the scheduling information in that field is configured publicly for each UE in the UE set. For example, all UEs in the UE set have the same or common field value for that field. A field with a first field type can be referred to as a common DCI field. For a field with a second field type, the scheduling information in that field is configured individually for each UE in the UE set. For example, different UEs in the UE set can configure individual field values ​​for the same field. Individual field values ​​can be the same or different from each other. A field with a second field type can be referred to as a specific DCI field. If a field has a third field type, then that field can be configurably specified by the WANN 110 as belonging to either the first or second field type based on the transmission scheme or specific scenario. A field with a third field type can be referred to as a configured DCI field.

[0076] In some implementations, UE 122 can receive signaling from WANN 110 carrying information about the field type of each field in the single DCI. The field type of each field in the single DCI can be determined based on the transmission scheme applied to the UE set.

[0077] In some implementations, when a field of a single DCI belongs to a second field type, UE 122 can obtain a field value combination table for that field. This field value combination table can include multiple predetermined entries with different value combinations. Each entry can indicate a combination of individual field values ​​for that field, and the independent values ​​in that entry are configured for different UEs within the UE set. The independent values ​​can be the same or different from each other. An index of the field value combination table can be assigned to a field of the single DCI. In this way, the single DCI does not need to include different field values ​​for that field configured for different UEs, thereby reducing the size of the single DCI.

[0078] In some implementations, UE 122 may receive UE-specific signaling from WANN 110 carrying UE-specific location information that locates a field configured for UE 122 in the single DCI.

[0079] The UE-specific location information for the location field may include the start position of each common DCI field and each specific DCI field of UE 122, as well as the length of each field. This signaling may be Radio Resource Control (RRC) signaling or another higher-layer signaling.

[0080] In some implementations, when each field in the first field block belongs to a first field type, UE 122 can receive common signaling from WANN 110 carrying information for locating the first field block in the single DCI. Each field in the first field block can be configured with a common field value for the UE set. The information for locating the first field block may include the start position of the first field block in the single DCI and the length of the first field block.

[0081] In some implementations, when the fields in the second field block belong to the second field type, UE 122 can receive specific signaling from WANN 110 carrying information locating the second field block in the single DCI. Each field in the second field block can be configured with a separate field value for each UE in the UE set. The information locating the second field block may include the start position of each field in the second field block configured for the UE 122 and the length of the field configured for the UE.

[0082] In some implementations, the scheduling information in a single DCI can be split into multiple scheduling information portions by the WANN 110. The UE 122 can receive these multiple scheduling information portions individually from the WANN 110.

[0083] UE 122 can receive the multiple scheduling information portions through different channels. For example, the first scheduling information portion can be received on the control channel, while the second scheduling information portion can be received on the data transmission channel.

[0084] In some implementations, the first scheduling information portion may include scheduling information that is commonly configured for each UE in the UE set. That is, the scheduling information in the first scheduling information portion is common or the same for all UEs in the UE set. UE 122 and other UEs in the UE set can receive common messages carrying the first scheduling information portion.

[0085] The second scheduling information section may include scheduling information configured individually for each UE in the UE set. In other words, the scheduling information in the second scheduling information section is specific to each UE in the UE set. Thus, UE 122 can receive a specific message from WANN 110 carrying the second scheduling information specifically configured for UE 122.

[0086] This disclosure describes various embodiments to further discuss scheduling transmissions of multiple devices using a single DCI, as follows: Example 1 Since this single DCI is used to schedule transmissions across multiple devices, it is a group common DCI and will be received by a group of devices (e.g., UEs). These devices can be configured with the same Radio Network Temporary Identifier (RNTI), and this RNTI is used for scrambling the group common DCI. Multiple devices scheduled by the group common DCI (i.e., this single DCI) can be configured with the same search space and Control Resource Set (CORESET) resources.

[0087] In some implementations, the transmissions of multiple devices are cooperative, and multiple devices can exchange information through a device-to-device interface.

[0088] In some implementations, the transmissions of multiple devices are independent, and the multiple devices are independent of each other and cannot exchange information.

[0089] In some implementations, a set, referred to as a "device set," can be defined for multiple devices that can be scheduled through a common DCI. Within this set, the multiple devices can be numbered, and each device corresponds to a device identifier within that set. For each specific schedule in a single DCI, that single DCI can schedule that specific schedule for a different subset of the device set, and each subset includes different combinations of multiple devices.

[0090] In some implementations, the single DCI may introduce a new DCI field to indicate information about the device portfolio, and this new DCI field may be referred to as a "device portfolio indicator".

[0091] In some implementations, this new DCI field can indicate the value of a table index. Taking four devices (e.g., UE122 / 124 / 126 / 128) as an example, as shown in Table 1, the table includes 15 device combinations. Each entry can indicate a combination of one or more devices from a plurality of devices. The value 'n' of this new DCI field is the index of the entry in the table corresponding to a specific device combination.

[0092]

[0093] In some implementations, the new DCI field can be a bitmap of different device combinations. For example, with four devices, the value "1111" can indicate that the specific schedule is configured for all four devices, while the value "1001" can indicate that the specific schedule is configured for UE 122 and UE 128.

[0094] Example 2 The DCI fields within a single DCI can be categorized into different types based on multi-device transmission scheduling. The first type of DCI field indicates the same scheduling information for multiple devices; this can be referred to as a common DCI field. The second type of DCI field indicates different scheduling information for each device; this can be referred to as a specific DCI field. The third type of DCI field can be configured as either the first or second type depending on the transmission situation. This third type of DCI field can be referred to as a configured DCI field.

[0095] The first type of DCI field may include at least one of the following: DCI format identifier, carrier indicator, uplink (UL) / supplementary uplink (SUL) indicator, frequency domain resource allocation, time domain resource allocation, frequency hopping, priority indicator, invalid symbol pattern indicator, channel access CPext (Cyclic Prefix Extension), virtual resource block (VRP) to physical resource block (PRB) mapping, PRB binding size indicator, rate matching indicator, or ZP (zero power) CSI (channel state information) - RS (reference signal) trigger.

[0096] The second type of DCI field may include at least one of the following: modulation and coding scheme (MCS), new data indicator (NDI), or redundancy version (RV).

[0097] The third type of DCI field may include at least one of the following: Hybrid Automatic Repeat Request (HARQ) process number (HPN), Sounding Reference Signal (SRS) request, SRS offset indicator, PUCCH resource indicator (PRI), PDSCH to HARQ feedback timing indicator, transmission configuration indication (TCI), code block group (CBG) transmission information (CBGTI), downlink assignment indicator (DAI), transmission power command (TPC) for the scheduled PUSCH, SRS resource set indicator, SRS resource indicator, precoding information and layer number, antenna port, PTRS (Physical Tracking Reference Signal) - DMRS (Demodulation Reference Signal). Signal (demodulation reference signal) association, beta_offset indicator, DMRS sequence initialization, UL-SCH (shared channel) indicator, CSI request, open-loop power control parameter set indicator, TPC for PUCCH, one-time HARQ-ACK (acknowledgement) request, enhanced Type-3 codebook indicator, PDSCH group index, new feedback indicator, number of requested PDSCH groups, HARQ-ACK retransmission indicator, CBG flushingout information (CBGFI) or PUCCH cell indicator.

[0098] In multi-device scheduling transmission, a single value is used to represent the scheduling information of each first-type DCI field in a single DCI, while multiple values ​​are used in each second-type DCI field to represent the scheduling information of different devices within that single DCI. Configuring different values ​​for different devices in the second-type DCI fields leads to a significant increase in DCI size as the number of scheduled devices increases, ultimately resulting in suboptimal control overhead. To address this issue, it is desirable to define a table for different combinations of field values ​​in the second-type DCI fields to represent the different scheduling information for multiple devices. This way, the DCI does not need to include all the different values ​​for different devices in the second-type DCI fields, but can simply include an index of the field value combination table to indicate the different values ​​of the second-type DCI fields for multiple devices.

[0099] In some implementations, the type of each DCI field in a single DCI can be predefined. For example, when multiple devices are cooperating, a table of different DCI field types can be predefined, as shown in the table below. WANN 110 can configure transmission schemes for cooperative transmission of multiple devices, such as: Uplink Single-Frequency Network (UL SFN), Space Division Multiplexing (SDM), Frequency Division Multiplexing (FDM), and Time Division Multiplexing (TDM). Multiple devices can determine the type information of each DCI field based on the table of predefined DCI field types and transmission schemes. For example, when the transmission scheme is SDM, the "Downlink Allocation Indicator" field is a first-type field, i.e., a common DCI field; the "TPC Command for PUSCH" field is a second-type field, i.e., a specific DCI field; and the "SRS Resource Indicator" field is a third-type field, i.e., a configured DCI field. In contrast, when the transport scheme is TDM, the "Downlink Allocation Indicator" field is a third type field, i.e., a configured DCI field, the "TPC Command for PUSCH" field is a second type field, i.e., a specific DCI field, and the "SRS Resource Indicator" field is a third type field, i.e., a configured DCI field.

[0100]

[0101] In some implementations, when there is no predefined type information for each DCI field, the network (e.g., WANN110) can configure the type of each DCI field in a single DCI according to the transmission scheme. When the DCI fields are configured by the network, the type information of each DCI field can be notified to the device (e.g., UE 122 / 124 / 126 / 128) via signaling (e.g., RRC or MAC CE).

[0102] Example 3 Since the group common DCI contains multiple DCI fields, and each DCI field may be configured for multiple devices in the group common DCI, an indication of the location of each DCI field is introduced.

[0103] In some implementations, different types of DCI fields exist within the group common DCI, and these different types of DCI fields can be arranged in an interleaved order within the group common DCI. For example... Figure 5 As shown, the common DCI fields common1, common2, and common3 are mixed with the specific DCI fields specific1-1, specific1-3, specific1-4, specific2-1, specific2-3, and specific2-4. specific1-1 represents the specific1 field configured for device 1 (e.g., UE 122), specific1-3 represents the specific1 field configured for device 3 (e.g., UE 126), and specific1-4 represents the specific1 field configured for device 4 (e.g., UE 128). Similarly, specific2-1 represents the specific2 field configured for device 1 (e.g., UE 122), specific2-3 represents the specific2 field configured for device 3 (e.g., UE 126), and specific2-4 represents the specific2 field configured for device 4 (e.g., UE 128).

[0104] In some implementations, multiple device-specific signaling messages can be used to indicate the start position and length of each field to each device. For example, WANN 110 can transmit signaling carrying first location information to UE 122, which locates the field configured for UE 122 in the single DCI, and another signaling carrying second location information to UE 124, which locates the field configured for UE 124 in the single DCI. The first location information may not include information locating the field specifically configured for UE 124 in the single DCI. Similarly, the second location information may not include information locating the field specifically configured for UE 122 in the single DCI. The UE-specific location information for locating fields may include each common DCI field of the particular UE and the start position of each specific DCI field, as well as the length of each field. This signaling may be RRC signaling or other higher-layer signaling.

[0105] In some implementations, multiple DCI fields in a group common DCI can be arranged in type order. For example, DCI fields of the same type are arranged first, followed by DCI fields of another type. Figure 6 As shown, the common DCI fields common1, common2, and common3 are arranged in order within the group common DCI, and then the specific DCI fields specific1-1, specific1-3, specific1-4, specific2-1, specific2-3, and specific2-4 are arranged in order following the common DCI fields within the group common DCI.

[0106] In some implementations, multiple device-specific signaling messages can be used to indicate the start position and length of each field to each device. This signaling can be RRC signaling or other higher-level signaling.

[0107] In some implementations, a single common signaling can be used to indicate the start position and length of the first DCI field block. The first DCI field block may include multiple DCI fields that are common to each device, i.e., common DCI fields. Alternatively, multiple device-specific signaling can be used to indicate the start position of each DCI field (i.e., specific DCI field) that is specific to each device.

[0108] In some implementations, multiple DCI fields of a group common DCI can be arranged in a different device order. For example... Figure 7 As shown, the group common DCI is arranged in the following order: two specific fields configured for device 1 (e.g., UE 122), two specific fields configured for device 3 (e.g., UE 126), and then two specific fields configured for device 4 (e.g., UE 128).

[0109] In some implementations, multiple device-specific signaling messages can be used to indicate the start position and length of each field to each device. This signaling can be RRC signaling or other higher-level signaling.

[0110] In some implementations, common signaling can be used to indicate the start position and length of the first DCI field block. The first DCI field block may include multiple DCI fields that are common to each device, i.e., common DCI fields. Multiple device-specific signaling can be used to indicate the start position and length of the second DCI field block corresponding to each device. The second DCI field block may include multiple device-specific DCI fields, i.e., specific DCI fields.

[0111] In some implementations, transmissions from multiple devices are cooperative, and the devices can exchange information via device-to-device interfaces. Device indexes can be predefined for the cooperating devices.

[0112] In some implementations, signaling can be used to indicate the length of each specific DCI field for each device. Multiple devices can exchange length information via a device-to-device interface. Each device can then calculate the position of each field based on the device index order of the scheduled devices and the lengths of other device-specific fields. Specifically, each device can read its own DCI field by skipping a certain length of bits. The skipped length can be calculated based on the device index and the lengths of other device-specific fields.

[0113] For example, such as Figure 8 As shown, the device combination scheduled in this instance is {UE 122, UE 126, UE 128}. UE 122's index is index0, UE 126's index is index1, and UE 128's index is index2. After receiving the group common DCI, UE 122 can read the common1 field sequentially. When UE 122 reads the specific1 field, since UE 122's corresponding index is index0, UE 122 can directly read the specific field after reading the common1 field. Then, UE 122 can skip (L1-3 + L1-4) bits to read the common2 field.

[0114] For UE 126, after receiving the group common DCI, UE 126 can sequentially read the common1 field. When UE 126 reads the specific1 field, since UE 126's corresponding index is index1, it can skip (L1-1) bits to read its own specific field value. Then, UE 126 can skip (L1_4) bits to read the common2 field. Similarly, after receiving the DCI, UE 128 can first sequentially read the common1 field.

[0115] When UE 128 reads the specific1 field, since UE 128's corresponding index is index2, it can skip (L1-1+L1-3) bits to read its own specific1 field. Since UE 128 is the last device in this scheduling, it can directly read the common2 field after reading its own specific1 field value.

[0116] Furthermore, even though each device's specific DCI field information is indicated via device-specific signaling, some devices can still further read other devices' specific DCI field information based on the location of the common field and their own specific fields. To prevent one device from reading other devices' specific DCI field information from the group's common DCI when multiple devices are transmitting independently, device-specific scheduling information indication rules can be defined to protect device-specific scheduling information from being obtained by other devices. For example, two different MCS index tables can be defined to indicate device-specific MCS information for two independent devices scheduled by the group's common DCI.

[0117] Example 4 In this embodiment, a two-level scheduling information transmission structure is defined for transmitting scheduling information in a group common DCI. For example, this two-level scheduling information transmission structure can be referred to as a two-level DCI. In the first level, WANN 110 can transmit a portion of the scheduling information in the group common DCI, which is referred to as first-level DCI information. In the second level, WANN 110 can transmit the remaining scheduling information in the group common DCI, which is referred to as second-level DCI information.

[0118] In some implementations, the two levels of DCI can be transmitted on different channels. For example, the first-level DCI information can be transmitted on a control channel, such as on a PDCCH. The second-level DCI information can be transmitted on a data transmission channel, such as on a PDSCH.

[0119] In some implementations, two-level DCI can be used to schedule transmissions across multiple devices.

[0120] In some implementations, the two-level DCI can be carried by different numbers of DCI messages. The first-level DCI information can be carried by a single DCI message for multiple devices to receive. The second-level DCI information can be carried in different DCI messages, each received by a separate device.

[0121] In some implementations, the two-level DCI may include different scheduling information. Specifically, the first-level DCI information may include common scheduling information for multiple devices. The second-level DCI information may include unique scheduling information for each device.

[0122] In some implementations, the first-level DCI information may include at least one of the following: a CI format identifier, a carrier indicator, an uplink (UL) / supplementary uplink (SUL) indicator, a frequency domain resource allocation, a time domain resource allocation, a frequency hopping, a priority indicator, an invalid symbol pattern indicator, a channel access CPext, a virtual resource block (VRP) to physical resource block (PRB) mapping, a PRB binding size indicator, a rate matching indicator, or a ZP CSI-RS trigger.

[0123] In some implementations, the second-level DCI information may include at least one of the following: modulation and coding scheme (MCS), new data indicator (NDI), and redundancy version (RV).

[0124] In some implementations, some DCI fields may not be fixed in the first-level DCI information or the second-level DCI information. This means that these DCI fields can be included in the first-level DCI information or the second-level DCI information depending on the specific transmission situation. These fields may include one or more of the following: HPN, SRS request, SRS offset indicator, PUCCH resource indicator (PRI), PDSCH to HARQ feedback (HARQ_feedback) timing indicator, Transmission Configuration Indicator (TCI), CBG (Code Block Group) Transmission Information (CBGTI), Downlink Allocation Indicator (DAI), Transmission Power Command (TPC) for Scheduled PUSCH, SRS Resource Set Indicator, SRS Resource Indicator, Precoding Information and Layer Number, Antenna Port, PTRS-DMRS Association, beta_offset Indicator, DMRS Sequence Initialization, UL-SCH Indicator, CSI Request, Open-Loop Power Control Parameter Set Indicator, TPC for PUCCH, One-Time HARQ-ACK Request, Enhanced Type-3 Codebook Indicator, PDSCH Group Index, New Feedback Indicator, Number of Requested PDSCH Groups, HARQ-ACK Retransmission Indicator, CBG Clear Information (CBGFI), or PUCCH Cell Indicator.

[0125] This disclosure describes methods, apparatus, and computer-readable media for wireless communication. This disclosure addresses the problem of optimizing wireless communication configurations. The methods, apparatus, and computer-readable media described in this disclosure can help improve the performance of wireless communication, thereby increasing efficiency and overall performance. The methods, apparatus, and computer-readable media described in this disclosure can improve the overall efficiency of wireless communication systems.

[0126] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the methods described above. A computer-readable medium may be referred to as a non-transitory computer-readable medium (CRM) that stores data over a long period, such as a flash drive or compact disk (CD), or stores data while powered, such as a storage device or random access memory (RAM).

[0127] In some embodiments, computer-readable instructions may be contained in software embodied in one or more tangible, non-transient computer-readable media. Such non-transient computer-readable media may be associated with user-accessible mass storage and certain short-term memories with non-transient properties, such as internal mass storage or ROM (read-only memory). Software implementing various embodiments of this disclosure may be stored in these devices and executed by a processor (or processing circuitry). Depending on specific needs, the computer-readable medium may include one or more memory devices or chips. The software may cause a processor (including a CPU (Central Processing Unit), GPU (Graphics Processing Unit), FPGA (Field Programmable Gate Array), etc.) to perform a specific process or a specific portion of a specific process described herein, including defining data structures stored in RAM and modifying these data structures according to a software-defined process.

[0128] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be included or are all included in any single implementation thereof. Rather, the language referring to features and advantages is to be understood as meaning that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, the discussion of features and advantages, and similar language throughout this specification, may, but do not necessarily, refer to the same embodiments.

[0129] Furthermore, the features, advantages, and characteristics described in this solution can be combined in any suitable manner of one or more embodiments. As a non-limiting example, a portion from one or more embodiments can be combined with another portion from other embodiments. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in all embodiments of this solution may be recognized in certain embodiments.

Claims

1. A method for wireless communication, comprising: A single downlink control information (DCI) is configured by a radio access network node (WANN) to schedule transmissions of a set of user equipment (UEs), wherein at least a portion of the scheduling information for one UE in the set of UEs and at least a portion of the scheduling information for another UE in the set of UEs are configured separately in the single DCI. The WANN transmits the single DCI to the UE set.

2. The method according to claim 1, wherein, The transmission of the UE set is either multiple independent unicast transmissions or UE cooperative transmissions, and in UE cooperative transmissions, information is exchanged between the UE set through UE-to-UE interfaces.

3. The method according to claim 1, further comprising: For each specific scheduling procedure, a subset of UEs is identified from the UE set, wherein at least a portion of the scheduling information in the single DCI is configured individually for each UE in the subset of UEs.

4. The method according to claim 3, wherein, The single DCI includes a UE combination indicator field that indicates a subset of the identified UEs.

5. The method according to claim 4, further comprising: For each UE in the UE set, a configuration identifier is provided, and the UE combination indicator field indicates the identified UE subset by the identifier of the UE in the identified UE subset.

6. The method according to claim 4, wherein, The UE combination indicator field includes an index to an entry in the UE combination table, which includes multiple predetermined entries, each indicating a different subset of the identified UEs.

7. The method according to claim 4, wherein, The UE combination indicator field includes a bitmap indicating the identified subset of UEs.

8. The method according to claim 1, wherein, The single DCI includes multiple fields, and the method further includes: Based on the scheduling information configured for the UE set in these fields, the multiple fields are classified into multiple field types.

9. The method according to claim 8, wherein, The plurality of field types include a first field type and a second field type. The scheduling information in the fields with the first field type is configured publicly for each UE in the UE set, while the scheduling information in the fields with the second field type is configured individually for each UE in the UE set.

10. The method according to claim 9, wherein, The plurality of field types further include a third field type, wherein fields having the third field type are configurably specified to belong to the first field type and the second field type.

11. The method of claim 9, further comprising: In response to the fact that a field of a single DCI belongs to the second field type, a field value combination table is configured for the field. The field value combination table includes multiple predetermined entries, each entry indicating a combination of individual values ​​of the field, and each individual value is configured for a UE in the UE set. as well as Assign an index to the field value combination table to the field of the single DCI.

12. The method according to claim 8, further comprising: Based on the transmission scheme, the field type of each field in the single DCI is predefined.

13. The method of claim 8, further comprising: Based on the transmission scheme applied to the UE set, the field type of each field in the single DCI is determined.

14. The method of claim 13, further comprising: Transmit signaling carrying information about the determined field type to the UE set.

15. The method according to claim 1, further comprising: Transmit UE-specific signaling to each UE in the UE set, carrying information about the fields configured for the UE in the single DCI, including fields commonly configured for the UE and fields configured separately, the signaling being Radio Resource Control (RRC) signaling or another higher-layer signaling.

16. The method according to claim 15, wherein, The information for locating fields configured for the UE includes the starting position of each commonly configured field, the starting position of each individually configured field configured for the UE, and the length of each field. Each UE in the UE set has the same starting position for commonly configured fields in the single DCI, while each UE in the UE set has a different starting position for individually configured fields.

17. The method according to claim 1, further comprising: A common signaling message carrying information locating a first field block in a single DCI is transmitted to the UE set, wherein each field in the first field block is configured with a common field value for the UE set.

18. The method according to claim 17, wherein, The information for locating the first field block includes the starting position of the first field block and the length of the first field block.

19. The method according to claim 1, further comprising: Transmit UE-specific signaling to a specific UE in the UE set, carrying information about the fields configured for the UE in the single DCI, each field being configured individually for the UE in the UE set.

20. The method according to claim 19, wherein, The location field information includes the starting position of each field configured for the specific UE and the length of the field configured for the specific UE.

21. The method according to claim 1, further comprising: Transmit UE-specific signaling carrying information about locating a second field block in a single DCI to a specific UE in the UE set, wherein each field in the second field block is configured with a separate field value for the UE in the UE set.

22. The method according to claim 21, wherein, The information for locating the second field block includes the starting position of the second field block configured for the specific UE and the length of the second field block configured for the specific UE.

23. The method according to claim 1, wherein, The transmission of the UE set is a cooperative transmission, and the method further includes: An index is defined for each UE in the UE set, and the position of a field configured for the UE in the single DCI is determined by the index of the UE and the length of the field.

24. The method according to claim 1, wherein, The step of transmitting the single DCI to the UE set includes: The scheduling information in the single DCI is split into multiple scheduling information parts; and The multiple scheduling information portions are transmitted separately to the UE set.

25. The method of claim 24, further comprising: The multiple scheduling information components are transmitted through different channels, wherein the different channels include at least a control channel or a data transmission channel.

26. The method of claim 24, wherein, The plurality of scheduling information portions include a first scheduling information portion and a second scheduling information portion. The first scheduling information portion includes scheduling information that is commonly configured for each UE in the UE set, and the second scheduling information portion includes scheduling information that is individually configured for each UE in the UE set.

27. The method of claim 26, wherein, The step of transmitting the plurality of scheduling information portions separately to the UE set includes: Transmit a first common message carrying the first scheduling information portion to the UE set; and A second message carrying the second scheduling information portion is transmitted individually to each UE in the UE set.

28. The method according to claim 1, further comprising: The same Radio Network Temporary Identifier (RNTI) is configured for the UE set, and the RNTI is used for single DCI scrambling.

29. The method according to claim 1, further comprising: Define UE-specific scheduling information indication rules for the UEs in the UE set.

30. A method for wireless communication, comprising: A first user equipment (UE) receives a single downlink control DCI from a radio access network node (WANN), wherein the single DCI is configured to schedule transmissions of a set of UEs including the first UE, and at least a portion of the scheduling information for one UE in the set of UEs and at least a portion of the scheduling information for another UE in the set of UEs are configured separately in the single DCI.

31. The method according to claim 30, wherein, The transmission of the UE set is either multiple independent unicast transmissions or UE cooperative transmissions, and in UE cooperative transmissions, information is exchanged between the UE set through UE-to-UE interfaces.

32. The method according to claim 30, wherein, For each specific scheduling process, a subset of UEs is identified from the UE set, and at least a portion of the scheduling information in the single DCI is configured individually for each UE in the UE subset.

33. The method according to claim 32, wherein, The single DCI includes a UE combination indicator field that indicates a subset of the identified UEs.

34. The method according to claim 33, wherein, The UEs in the set are numbered, each UE in the set has an identifier, and the UE combination indicator field indicates the identified UE subset by the identifier of the UE in the identified UE subset.

35. The method according to claim 34, wherein, The UE combination indicator field indicates the identified subset of UEs by indexing an entry in the UE combination table, which includes multiple predetermined entries, each indicating a different identified subset of UEs.

36. The method according to claim 33, wherein, The UE combination indicator field includes a bitmap indicating the identified subset of UEs.

37. The method of claim 30, wherein, The single DCI includes multiple fields, and these multiple fields are classified into multiple field types based on the scheduling information configured for the UE set in these fields.

38. The method according to claim 37, wherein, The plurality of field types include a first field type and a second field type. The scheduling information in the fields with the first field type is configured publicly for each UE in the UE set, while the scheduling information in the fields with the second field type is configured individually for each UE in the UE set.

39. The method according to claim 38, wherein, The plurality of field types further include a third field type, wherein fields having the third field type are configurably specified to belong to the first field type and the second field type.

40. The method of claim 38, further comprising: In response to the fact that a field of a single DCI belongs to the second field type, a field value combination table for the field is obtained. The field value combination table includes multiple predetermined entries, each entry indicating a combination of individual values ​​of the field, each individual value being configured for a UE in the UE set.

41. The method of claim 37, further comprising: Based on the transmission scheme applied to the UE set, the field type of each field in the single DCI is obtained.

42. The method of claim 37, further comprising: Receive signaling from the WANN carrying information about the determined field type.

43. The method of claim 30, further comprising: The WANN receives UE-specific signaling carrying information about fields configured for the UE in the single DCI, including fields publicly configured for the UE and fields configured separately, and the signaling is Radio Resource Control (RRC) signaling or another higher-layer signaling.

44. The method according to claim 43, wherein, The information for locating fields configured for the first UE includes the starting position of each commonly configured field, the starting position of each individually configured field configured for the first UE, and the length of each field. Each UE in the UE set has the same starting position for commonly configured fields in the single DCI, while each UE in the UE set has a different starting position for individually configured fields.

45. The method of claim 30, further comprising: The WANN receives public signaling carrying information locating a first field block in the single DCI, wherein each field in the first field block is configured with a public field value for the UE set.

46. ​​The method according to claim 45, wherein, The information for locating the first field block includes the starting position of the first field block and the length of the first field block.

47. The method of claim 30, further comprising: The WANN receives UE-specific signaling carrying information about the fields configured for the UE in the single DCI, each field being configured individually for the UE in the UE set.

48. The method according to claim 47, wherein, The location field information includes the starting position of each field configured for the first UE and the length of the field configured for the first UE.

49. The method of claim 30, further comprising: The WANN receives UE-specific signaling carrying information about locating a second field block in the single DCI, wherein each field in the second field block has a separate field value configured for UEs in the UE set.

50. The method according to claim 49, wherein, The information for locating the second field block includes the starting position of the second field block configured for the first UE and the length of the second field block configured for the first UE.

51. The method according to claim 30, wherein, The transmission of the UE set is a cooperative transmission, an index is defined for each UE in the UE set, and the position of the field configured for the first UE in the single DCI is determined by the index of the first UE and the length of the field.

52. The method according to claim 30, wherein, The scheduling information in a single DCI is split into multiple scheduling information parts, and the method further includes: The multiple scheduling information portions are received individually from the WANN.

53. The method according to claim 52, wherein, The multiple scheduling information components are received through different channels, including control channels and data transmission channels.

54. The method according to claim 52, wherein, The plurality of scheduling information portions include a first scheduling information portion and a second scheduling information portion. The first scheduling information portion includes scheduling information that is commonly configured for each UE in the UE set, and the second scheduling information portion includes scheduling information that is individually configured for each UE in the UE set.

55. The method of claim 54, further comprising: Receive a first public message carrying the first scheduling information portion from the WANN; as well as Receive a second message from the WANN carrying the second scheduling information portion.

56. The method of claim 30, wherein, The UE set is configured with the same Radio Network Temporary Identifier (RNTI), and the RNTI is used for scrambling the single DCI.

57. The method of claim 30, further comprising: UE-specific scheduling information indication rules for UEs in the UE set are defined for at least some fields in the single DCI.

58. 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 57.

59. A non-transitory computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 57.

Images