WO2025156382A1

WO2025156382A1 - Methods and apparatus for scheduling transmissions of multiple devices

Info

Publication number: WO2025156382A1
Application number: PCT/CN2024/082064
Authority: WO
Inventors: Shuai ZHOU; Shuaihua KOU; Xianghui HAN; Jing Shi; Jian Li
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-03-15
Filing date: 2024-03-15
Publication date: 2025-07-31
Anticipated expiration: 2026-09-15

Abstract

The present disclosure describes methods, system, and devices for scheduling transmissions of multiple devices. The method may include configuring, by a wireless access network node (WANN), a single downlink control information (DCI) to schedule for transmissions of a set of user equipments (UEs). At least a portion of scheduling information for a UE in the set of UEs and at least a portion of scheduling information for another UE in the set of UEs are configured separately in the single DCI. The method may further include transmitting, by the WANN, the single DCI to the set of UEs.

Description

METHODS AND APPARATUS FOR SCHEDULING TRANSMISSIONS OF MULTIPLE DEVICES

TECHNICAL FIELD

The present disclosure is directed generally to wireless communications. Particularly, the present disclosure relates to methods and apparatuses for scheduling transmissions of multiple devices.

BACKGROUND

In the development of communication technologies, a large number of devices are interconnected in virtual reality, smart medical and other scenarios, and collaborative transmissions between multiple devices has become a new direction for the development of communication technologies.

In addition, with the rapid development of mobile internet and growth of smart devices, mobile data traffic has exploded. Hotspot areas with high user density, such as stadiums, shopping centers, and transfer stations, are facing increasing pressure of multi-device transmissions. These multiple devices may have cooperative relationships or perform independent transmissions. In any case, they need to support a large amount of data traffic and high transmission reliability. In the advanced 5th Generation and 6th generation communication technology development, there will be requirement for efficient multiple devices transmission techniques.

Regardless of whether the transmissions of multiple devices are independent or collaborative, there is a need to schedule the transmissions of multiple devices efficiently. Therefore, how to schedule multiple devices is an essential problem to be researched and solved.

SUMMARY

This disclosure relates to methods and apparatuses for wireless communication, and more specifically, for scheduling transmission of multiple devices such as user equipments (UEs) . The various embodiments in the present disclosure may facilitate to optimize scheduling performance in a wireless communication system.

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

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

In another embodiment, an apparatus for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

In another embodiment, a device for wireless communication may include a memory storing instructions and a processing circuitry in communication with the memory. When the processing circuitry executes the instructions, the processing circuitry is configured to carry out the above methods.

In another embodiment, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods. The computer-readable medium includes a non-transitory computer-readable medium.

The above and other aspects and their implementations are described in greater detail in the drawings, the descriptions, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary system of wireless communication network.

FIG. 2 schematically shows an exemplary base station.

FIG. 3 schematically shows an exemplary user equipment.

FIG. 4 shows a flow diagram of an exemplary method for wireless communication.

FIG. 5 shows an exemplary arrangement of DCI fields in a group common DCI.

FIG. 6 shows another exemplary arrangement of DCI fields in a group common DCI.

FIG. 7 shows another exemplary arrangement of DCI fields in a group common DCI.

FIG. 8 shows an exemplary indexing of DCI fields in a group common DCI.

FIG. 9 shows a flow diagram of an exemplary method for wireless communication.

DETAILED DESCRIPTION

The present disclosure will now be described in detail hereinafter with reference to the accompanied drawings, which form a part of the present disclosure, and which show, by way of illustration, specific examples of embodiments. Please note that the present disclosure may, however, be embodied in a variety of different forms and, therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the embodiments to be set forth below.

Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in an embodiment” or “in some embodiments” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” or “in other embodiments” as used herein does not necessarily refer to a different embodiment. The phrase “in an implementation” or “in some implementations” as used herein does not necessarily refer to the same implementation and the phrase “in another implementation” or “in other implementations” as used herein does not necessarily refer to a different implementation. It is intended, for example, that claimed subject matter includes combinations of exemplary embodiments or implementations in whole or in part.

In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and/or, ” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” or “at least one” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a” , “an” , or “the” , again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” or “determined by” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

The present disclosure describes methods and apparatuses for scheduling transmissions of multiple devices.

The main idea of user collaboration technology is to aggregate multiple users for collaborative transmissions. In user collaborative transmissions, multiple devices are divided into anchor devices and assistant devices, and assistant devices are used to collaborate with anchor devices for data transmission. According to the collaboration relationship between the assistant devices and the anchor devices, collaborative transmission is divided into data duplication collaboration, data split collaboration and wireless backup collaboration. In data duplication collaboration transmission technology, the anchor devices and the assistant devices transmit the same data, mainly to improve the reliability of data transmission of the anchor devices. In data split collaboration, the anchor devices and the assistant devices transmit different data packets, mainly to increase the data transmission rate. In wireless backup collaboration, the assistant devices only forward the data of the anchor devices to the base station when the anchor devices power-off. In collaborative transmissions, since there is a collaborative relationship among devices, using one DCI scheduling transmissions of multiple devices simultaneously is a natural way to improve transmission efficiency.

For multiple devices independent transmissions, the basic scheduling scheme is to schedule the transmission of each device using a separate DCI. However, in some hotspot areas such as gathering places for big show, or some hot tourist attractions, there may be hundreds of devices need to be scheduled for transmission, scheduling the transmission of each device using a separate DCI may cause Physical Downlink Control Channel (PDCCH) blocking, which will significantly negate the user experience in hotspot areas. Therefore, scheduling transmissions of multiple devices using a single DCI may be a method to reduce PDCCH overhead and thereby reduce the probability of PDCCH blocking and guarantee user experience.

There are several DCI formats in existing protocols for scheduling 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 Third Generation Partnership Project (3GPP) TS 38.212 as reproduced below, the usage of DCI format 0_0/0_2/1_0/1_2 are scheduling of one PUSCH/PDSCH in one cell. The fields in those DCI formats indicate the information only for one PUSCH/PDSCH transmission.

DCI format 4_0/4_1/4_2 are for downlink broadcast or multicast scheduling. The fields in those DCI formats indicate the information only for multiple PDSCHs transmissions. However, since the PDSCH transmissions for broadcast or multicast are the same, the transmission information can be indicated in a single field.

The DCI format 0_3 and 1_3 which introduced in Rel-18 are used for scheduling one PUSCH/PDSCH of one device in one cell, or multiple PUSCHs/PDSCHs of one device in multiple cells with one PUSCH/PDSCH per cell.

The DCI format 2_0/2_1/2_2/2_3/2_4/2_5/2_6/2_7/2_8/2_9, and the DCI format 3_0/3_1/3_2 are used for transmitting some special information.

Table 7.3.1-1: DCI formats

In short, all the existence DCI formats in existing protocols cannot meet the requirement of scheduling multiple PUSCH transmissions for collaborative devices or the requirement of scheduling multiple independent PDSCH/PUSCH transmissions of multiple devices. One of the objectives of the present disclosure is to schedule multiple PUSCH/PDSCH transmissions with a single DCI for multiple devices to ensure uplink transmission performance in collaborative transmission and user experience in hotspot areas.

The present disclosure provides various embodiments discussing how to schedule multiple PUSCH/PDSCH transmissions of multiple devices using a single DCI. As described in detail below, a group common DCI is defined and used for multiple devices transmissions. For the design of the group common DCI, the classification enhancement of DCI fields may enable to indicate different information for different devices. In addition, with the enhancement of the indication information of the device combination and the indication of the location information of the DCI field, each device can obtain its own transmission scheduling information from the group common DCI accurately, and further perform corresponding transmission.

With the methods and apparatuses described in the present disclosure, multiple PUSCH/PDSCH transmissions of multiple devices can be scheduled using a single DCI. The transmission performance of users in collaborative transmissions and or in hotspot areas can be guaranteed, and multi-user transmission gains can be obtained in this phase.

A wireless access network provides network connectivity between a user equipment and an information or data network such as a voice or video communication network, the Internet, and the like. An example wireless access network may be based on cellular technologies, which may further be based on, for example, 5G NR technologies and/or formats. FIG. 1 shows an example system diagram of wireless communication network 100 including multiple user equipments (UEs) 122/124/126/128 and a wireless access network node (WANN) 110 according to various embodiments. The UEs 122/124/126/128 may include but is not limited to a mobile phone, smartphone, tablet, laptop computer, a smart electronics or appliance including an air conditioner, a television, a refrigerator, an oven and the like, or other devices that are capable of communicating wirelessly over a network.

The WANN 110 may include a wireless network base station, or a NG radio access network (NG-RAN) base station or node, which may include a nodeB (NB, e.g., a gNB) in a mobile telecommunications context. Each type of these wireless access network nodes may be configured to perform a corresponding set of wireless network functions. The set of wireless network functions between different types of wireless access network nodes may not be identical. The set of wireless network functions between different types of wireless access network nodes, however, may functionally overlap.

For simplicity and clarity, only one WANN and four UEs are shown in the wireless communication network 100. It will be appreciated that one or more WANNs may exist in the wireless communication network, and each WANN may serve one or more UEs in the meantime. Besides UEs and WANNs, the network 100 may further comprise any other network nodes with different functions such as the network nodes in core network of the wireless communication network 100. In addition, while various embodiments will be discussed in the context of the particular example wireless communication network 100, the underlying principle applies to other applicable wireless communication networks.

FIG. 2 shows an example of electronic device 200 to implement a wireless access network node such as the WANN 110. The example electronic device 200 may include radio transmitting/receiving (Tx/Rx) circuitry 208 to transmit/receive communication with UEs and/or other WANNs. The electronic device 200 may also include network interface circuitry 209 to communicate the WANN with other WANNs and/or a core network, e.g., optical or wireline interconnects, Ethernet, and/or other data transmission mediums/protocols. The electronic device 200 may optionally include an input/output (I/O) interface 206 to communicate with an operator or the like.

The electronic device 200 may also include system circuitry 204. The system circuitry 204 may include processor (s) 221 and/or memory 222. The memory 222 may include an operating system 224, instructions 226, and parameters 228. The instructions 226 may be configured for the one or more of the processors 221 to perform the functions of the network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, scheduling schemes, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.

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

The communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation /demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and/or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings. As one specific example, the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G /Long Term Evolution (LTE) , 5G standards, 6G standards, or any other telecommunication standards. The techniques described below, however, are applicable to other wireless communications technologies whether arising from the 3GPP, GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.

The system circuitry 304 may include one or more processors 321 and memories 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to carry out desired functionality for the electronic device 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, 6G, or other data that the electronic device 300 will send, or has received, through the communication interfaces 302. In various implementations, a system power for the electronic device 300 may be supplied by a power storage device, such as a battery or a transformer.

The present disclosure describes various embodiment for scheduling transmissions of multiple devices, which may be implemented, partly or totally, on the WANN and/or the UEs described above in FIGs. 1-3.

Referring to FIG. 4, the present disclosure describes various embodiments of a method 400 for wireless communication for scheduling transmissions of multiple UEs. The method 400 may include a portion or all of the following operations:

At step 410, the WANN 110 may configure a single DCI to schedule for transmissions of a set of UEs. At least a portion of scheduling information for a UE in the set of UEs and at least a portion of scheduling information for another UE in the set of UEs are configured separately in the single DCI. For example, the set of UEs 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 scheduling information and the second scheduling information may be configured separately in the single DCI. In an 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 same as the configured second scheduling information. At step 420, the WANN 110 may transmit the configured single DCI to the set of UEs.

In some implementations, the set of UEs may be configured with a same radio network temporary identifier (RNTI) , and the RNTI may be used for a single DCI scrambling.

In some implementations, the transmissions of a set of UEs are multiple independent unicast transmissions or UE collaborative transmissions. Information is exchanged between the set of UEs through UE-to-UE interfaces in UE collaborative transmissions.

In some implementations, for a specific scheduling, the WANN 110 may identify a subset of UEs from the set of UEs, each subset is a specific UE combination of the set of UEs. At least a portion of scheduling information in the single DCI is configured separately for each UE in the subset of UEs.

In some implementations, the single DCI may include a UE combination indicator field indicating the identified subset of UEs.

In some implementations, the WANN 110 may configure an identifier of each UE in the set of UEs, and the UE combination indicator field indicates the subset of UEs by identifiers of UEs in the subset UEs.

In some implementations, a UE combination table may include a plurality of predetermined entries, each of which indicates a different subset of UEs. The UE combination indicator field may indicate the identified subset of UEs by an index of an entry in the UE combination table corresponding to the subset of UEs.

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

In some implementations, the single DCI may include a plurality of fields. The WANN 110 may categorize the plurality of fields into a plurality of field types based on scheduling information configured for the set of UEs in the fields.

The plurality of field types may include a first field type, a second field type, and a third field type. For a field with the first field type, the schedule information in the field is configured commonly for each of the set of UEs. For example, all UEs in the set of UEs have a same or common field value for this field. A field with the first field type may be referred to as a common DCI field. For a field with the second field type, the schedule information in the field is configured separately for UEs in the set of UEs. For example, the different UEs in the set of UEs may be configured with separate field values for the same field. The separate field values may be same or different from each other. A field with the second field type may be referred to as a specific DCI field. If a field has the third field type, the field may be configurably designated by the WANN 110 to belong to the first field type and the second field type according to transmission scheme or specific scenarios. A field with the third field type may be referred to as a configured DCI field.

In some implementations, the WANN 110 may determine a field type for each field in the single DCI based on transmission scheme applied to the transmission of the set of UEs. Then, the WANN 110 may transmit a signaling carrying information on the determined field types to the set of UEs.

In some implementations, the WANN 110 may predefine a field type of each field in the single DCI based on transmission scheme.

In some implementations, where a field of the single DCI belongs to the second field type, the WANN 110 may configure a field value combination table for the field. The field value combination table may include a plurality of predetermined entries with different value combinations. Each of the entries may indicate a combination of separate field values of the field and the separate values in the entry are respectively configured for different UEs in the set of UEs. The separate values may be same or different from each other. Then, the WANN 110 may assign an index of the field value combination table to the field of the single DCI. In this way, the single DCI may not have to include the different field values of the field configured for the different UEs respectively, thereby reducing the size of the single DCI.

In some implementations, for each UE in the set of UEs, the WANN 110 may transmit to the UE a UE specific signaling carrying UE specific location information locating fields configured for the specific UE in the single DCI. For example, the WANN 110 may transmit to the UE 122 a signaling carrying the first location information locating fields configured for the UE 122 in the single DCI, and transmit to the UE 124 another signaling carrying the second location information locating fields configured for the UE 124 in the single DCI. The first location information may not include information locating fields specifically configured for the UE 124 in the single DCI. In the same way, the second location information may not include information locating fields specifically configured for the UE 122 in the single DCI.

The UE specific location information locating the fields may include a start position of each common DCI field and each specific DCI field of the specific UE and a length of each of the field. The signaling may be a Radio Resource Control (RRC) signaling or another higher layer signaling.

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

In some implementations, where individual fields in the second block of fields belong to the second field type, for each UE in the set of UEs, the WANN 110 may transmit to the UE a specific signaling carrying information locating a second block of fields in the single DCI. Each field in the second block of fields may be configured for UEs in the set of UEs with separate field values. The information locating the second block of fields may include a start position of each field in the second block of fields configured for the UE and a length of the field configured for the UE.

In some implementations, where the transmissions of the set of UEs are collaborative transmissions, an index may be defined for each UE in the set of UEs. As such, a location of a field configured for the UE in the single DCI may be determined by the index of the UE and a length of the field.

In some implementations, the WANN 110 may split scheduling information in the single DCI into a plurality of scheduling information portions and separately transmit the plurality of scheduling information portions to the set of UEs. For example, the WANN 110 may split the scheduling information in the single DCI into two scheduling information portions, i.e., the first scheduling information portion and the second scheduling information portion. For example, the WANN 110 may first transmit a message carrying the first scheduling information portion to the set of UEs, and then transmit another message carrying the second scheduling information portion to the set of UEs.

The plurality of scheduling information portions may be transmitted via different channels. For example, the first scheduling information portion may be transmitted on a control channel while the second scheduling information portion may be transmitted on a data transmission channel.

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

The second scheduling information portion may include scheduling information configured separately for individual UEs in the set of UEs. That is, the scheduling information in the second scheduling information portion is specific to individual UEs in the set of UEs. As such, the WANN 110 may separately transmitting to each of the set of UEs a specific message carrying the second scheduling information.

Referring to FIG. 9, the present disclosure describes various embodiments of a method 900 for wireless communication. The method 900 may include a portion or all of the following operations:

At step 910, the UE 122 may receive a single DCI from the WANN 110. The single DCI may be configured by the WANN 110 to schedule for transmissions of a set of UEs including the UE 122. At least a portion of scheduling information for a UE in the set of UEs and at least a portion of scheduling information for another UE in the set of UEs are configured separately in the single DCI.

In some implementations, for a specific scheduling, a subset of UEs may be identified from the set of UEs by the WANN 110, each subset is a specific UE combination of the set of UEs. At least a portion of scheduling information in the single DCI is configured separately for each UE in the subset of UEs.

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

In some implementations, the single DCI may include a plurality of fields. the plurality of fields may be categorized into a plurality of field types based on scheduling information configured for the set of UEs in the fields.

In some implementations, the UE 122 may receive from the WANN 110 a signaling carrying information on a field type for each field in the single DCI. The field type for each field in the single DCI may be determined based on transmission scheme applied to the transmission of the set of UEs.

In some implementations, where a field of the single DCI belongs to the second field type, the UE 122 may obtain a field value combination table for the field. The field value combination table may include a plurality of predetermined entries with different value combinations. Each of the entries may indicate a combination of separate field values of the field and the separate values in the entry are respectively configured for different UEs in the set of UEs. The separate values may be same or different from each other. An index of the field value combination table may be assigned to the field of the single DCI. In this way, the single DCI may not have to include the different field values of the field configured for the different UEs respectively, thereby reducing the size of the single DCI.

In some implementations, the UE 122 may receive from the WANN 110 a UE specific signaling carrying UE specific location information locating fields configured for the UE 122 in the single DCI.

The UE specific location information locating the fields may include a start position of each common DCI field and each specific DCI field of the UE 122 and a length of each of the field. The signaling may be a Radio Resource Control (RRC) signaling or another higher layer signaling.

In some implementations, where individual fields in a first block of fields belong to the first field type, the UE 122 may receive from the WANN 110 a common signaling carrying information locating a first block of fields in the single DCI. Each field in the first block of fields may be configured for the set of UEs with a common field value. The information locating the first block of fields may include a start position of the first block of fields in the single DCI and a length of the first block of fields.

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

In some implementations, the scheduling information in the single DCI may be split into a plurality of scheduling information portions by the WANN 110. The UE 122 may separately receive from the WANN 110 the plurality of scheduling information portions.

The UE 122 may receive the plurality of scheduling information portions via different channels. For example, the first scheduling information portion may be received on a control channel while the second scheduling information portion may be received on a data transmission channel.

In some implementations, the first scheduling information portion may include scheduling information configured commonly for each of the set of UEs. That is, the scheduling information in the first scheduling information portion is common or same to all UEs in the set of UEs. The UE 122 and other UEs in the set of UEs may receive a common message carrying the first scheduling information portion.

The second scheduling information portion may include scheduling information configured separately for individual UEs in the set of UEs. That is, the scheduling information in the second scheduling information portion is specific to individual UEs in the set of UEs. As such, the UE 122 may receive from the WANN 110 a specific message carrying the second scheduling information specifically configured for the UE 122.

The present disclosure describes various embodiments to further discuss the scheduling for the transmissions of multiple devices using a single DCI as follows:

Embodiment 1

Since the single DCI is used to scheduling multiple devices transmissions, the single DCI is a group common DCI to be received by a group of multiple devices such as UEs. The group devices may be configured with a same Radio Network Temporary Identifier (RNTI) , and the RNTI is used for the group common DCI scrambling. The multiple devices scheduled by a group common DCI, i.e., the single DCI, may be configured with the same search space and Control Resource Set (CORESET) resources.

In some implementations, the transmissions of the multiple devices are collaborative, and the multiple devices can exchange information through device-to-device interfaces.

In some implementations, the transmissions of the multiple devices are independent, and the multiple devices are independent of each other and unable to exchange information.

In some implementations, a set may be defined for the multiple devices that can be scheduled by a group common DCI, and the set may be called as “device set” . In the set, the multiple devices may be numbered and each device corresponds to a device identifier in the set. For each specific scheduling in the single DCI, the single DCI may schedule the specific scheduling for different subsets of a device set, and each subset include a different device combination of the multiple devices.

In some implementations, the single DCI may introduce a new DCI field to indicate the information of the device combination, and the new DCI field may be named as “device combination indicator. ”

In some implementations, the new DCI field may indicate a value of a table index. Take four devices such as UEs 122/124/126/128 as example, as shown in Table 1, the table includes 15 device combinations. Each entry may indicate one combination of one or more of the multiple devices. The value n of the new DCI field is the index of an entry in the table corresponding a specific device combination.

In some implementations, the new DCI field may be a bitmap of different device combinations. Take the four devices as example, the value “1111” may indicate the specific scheduling is configured for all the four devices, and the value “1001” may indicate the specific scheduling is configured for the UE 122 and the UE 128.

Embodiment 2

The DCI fields in the single DCI may be divided into different types for multiple devices transmissions scheduling. The first type of DCI fields may indicate the same scheduling information for multiple devices, which may be called as common DCI fields. The second type of DCI fields may indicate different scheduling information for each device, which can be called as specific DCI fields. The third type of DCI fields may be configured as the first type or the second type according to the transmission situations. The third type of DCI fields may be called as configured DCI fields.

The first type of DCI fields may include at least one of identifier for DCI format, 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, virtual resource block (VRP) -to-physical resource block (PRB) mapping, PRB bundling size indicator, rate matching indicator, or ZP CSI-RS trigger.

The second type of DCI fields may include at least one of modulation and coding scheme (MCS) , new data indicator (NDI) , or redundancy version (RV) .

The third type of DCI fields may include at least one of 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, preceding information and number of layers, antenna ports, PTRS-DMRS association, beta_offset indicator, DMRS sequence initialization, UL-SCH indicator, CSI request, open-loop power control parameter set indication, TPC for PUCCH, One-shot HARQ-ACK request, enhanced Type-3 codebook indicator, PDSCH group index, new feedback indicator, number of request PDSCH groups, HARQ-ACK retransmission indicator, CBG flushing out information (CBGFI) , or PUCCH cell indicator.

In the scheduling transmission of multiple devices, a single value is used to denote the scheduling information of each first type of DCI field in the single DCI, whereas multiple values of each second type DCI filed is used to respectively denote the scheduling information for different devices in the single DCI. The configuration of different values for different devices in the second type of DCI field engenders a substantial escalation in the size of the DCI with the accretion of scheduled devices, culminating in suboptimal control overhead. To address the issue, it is desirable to define a table of different field values combination of a second type DCI filed for different scheduling information of multiple devices. As such, the DCI does not have to include all different values for different devices in a second type of DCI field and may simply include an index of the filed value combination table to indicate the different values of second type DCI fields for multiple devices.

In some implementations, the type of each DCI field in the single DCI may be predefined. For example, where the transmissions of multiple devices are collaborative, a table of different type of DCI fields can be predefined, take a table following for example. The WANN 110 may configure the transmission scheme, such as Uplink Single-Frequency Network (UL SFN) , Space Division Multiplexing (SDM) , Frequency Division Multiplexing (FDM) , Time Division Multiplexing (TDM) , for the collaborative transmissions of the multiple devices. The multiple devices may determine the type information of each DCI field in accordance with the table predefining the types of the DCI fields and the transmission scheme. For example, where the transmission scheme is SDM, the field of “downlink assignment index” is the first type field, i.e., a common DCI field, the field of “TPC command for PUSCH” is the second type field, i.e., a specific DCI field, and the field of “SRS resource indicator” is the third type field, i.e., a configured DCI field. By contrast, where the transmission scheme is TDM, the field of “downlink assignment index” is the third type field, i.e., a configured DCI field, the field of “TPC command for PUSCH” is the second type field, i.e., a specific DCI field, and the field of “SRS resource indicator” is the third type field, i.e., a configured DCI field.

In some implementations, where there is no predefined type information of each DCI field, the network such as the WANN 110 may configure the type of each DCI field in the single DCI according to transmission scheme. While the DCI field are configured by the network, the information of the type of each DCI field may be informed to devices such as the UES 122/124/126/128 by signaling, such as RRC or MAC CE.

Embodiment 3

Since a group common DCI comprises multiple DCI fields and each of the DCI field may be configured for multiple devices in the group common DCI, an indication of each DCI field location is introduced.

In some implementations, there are different types of DCI fields in the group common DCI and the different type of DCI fields may be arranged in a cross order in the group common DCI. As shown in FIG. 5, 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. The specific1-1 represents the specific1 field configured for the device 1 such as the UE 122, the specific1-3 represents the specific1 field configured for the device 3 such as the UE 126, and the specific1-4 represents the specific1 field configured for the device 4 such as the UE 128. Similarly, the specific2-1 represents the specific2 field configured for the device 1 such as the UE 122, the specific2-3 represents the specific2 field configured for the device 3 such as the UE 126, and the specific2-4 represents the specific2 field configured for the device 4 such as the UE 128.

In some implementations, multiple device-specific signaling may be used to indicate the start position and length of every field to each device. For example, the WANN 110 may transmit to the UE 122 a signaling carrying the first location information locating fields configured for the UE 122 in the single DCI, and transmit to the UE 124 another signaling carrying the second location information locating fields configured for the UE 124 in the single DCI. The first location information may not include information locating fields specifically configured for the UE 124 in the single DCI. In the same way, the second location information may not include information locating fields specifically configured for the UE 122 in the single DCI. The UE specific location information locating the fields may include a start position of each common DCI field and each specific DCI field of the specific UE and a length of each of the field. The signaling may be a RRC signaling or other higher layer signaling.

In some implementations, the multiple DCI fields in a group common DCI may arranged in order by types. For example, DCI fields of the same type are arranged in sequence first, followed by another type of DCI fields. As shown in FIG. 6, the common DCI fields, common1, common2, and common3 are arranged in the group common DCI sequentially, and then the specific DCI fields specific1-1, specific1-3, specific1-4, specific2-1, specific2-3, and specific2-4 are sequentially arranged in the group common DCI following the common DCI fields.

In some implementations, multiple device-specific signaling may be used to indicate the start position and length of every field to each device. The signaling can be a RRC signaling or other higher layer signaling.

In some implementations, a single common signaling may be used to indicate the start position and length of a first DCI fields block. The first DCI fields block may include multiple DCI fields which are common to each device, i.e., common DCI fields. Additionally, multiple device-specific signaling may be used to indicate the start position of every DCI fields which are specific to each device, i.e., specific DCI fields.

In some implementations, multiple DCI fields of a group common DCI may be arranged in order by different devices. As shown in FIG. 7, the group common DCI sequentially arrange two specific fields configured for the device 1 such as the UE 122, two specific fields configured for the device 3 such as the UE 126, and then two specific fields configured for the device 4 such as the UE 128.

In some implementations, a common signaling may be used to indicate the start position and length of a first DCI fields block. The first DCI fields block may include multiple DCI fields which are common to each device, i.e., common DCI fields. And multiple device-specific signaling may be used to indicate the start position and length of a second DCI fields block corresponding to each device. The second DCI fields block may include multiple DCI fields which are specific to each device, i.e., specific DCI fields.

In some implementations, the transmissions of multiple devices are collaborative, and the multiple devices may exchange information through device-to-device interfaces. Device index for the collaborative devices may be predefined.

In some implementations, a signaling may be used to indicate the length of each specific DCI field of each device. Multiple devices may exchange the length information through device-to-device interfaces. Then, each device may calculate the location of each field in accordance with the device index sequence of the scheduled devices and the length of other devices specific fields. Specifically, every device may read its own DCI fields by skipping a length of bits. The skipping length may be calculates based on the device index and the length of other devices specific fields.

For example, as shown in FIG. 8, the device combination of this scheduling is {UE 122, UE 126, UE 128} . The index of UE 122 is index0, the index of UE 126 is index1, and the index of UE 128 is index2. After receiving the group common DCI, the UE 122 may read the common1 field in sequence. When the UE 122 reads the specific1 field, because the index corresponding to the UE 122 is index0, the UE 122 may directly read the specific field after reading the common1 field. Then, the UE 122 may skip (L1-3 + L1-4) bits to read the common2 field.

As for the UE 126, after receiving the group common DCI, the UE 126 may read the common1 field in sequence. When the UE 126 reads the specific1 field, because the index corresponding to the UE 126 is index1, it may skip (L1-1) bits to read its own specific field value. Then, the UE 126 may skip (L1_4) bits to read the common2 field. Similarly, after receiving the DCI, the UE 128 may first read the common1 field in sequence.

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

Moreover, even if the specific DCI fields information of each device is indicated by device-specific signaling, some devices can further read the specific DCI field information of other devices based on the location of the common fields and their own specific fields. To prevent a device from reading the specific DCI field information of other devices from the group common DCI, in case that the transmissions of multiple devices are independent, a device-specific scheduling information indication rule may be defined to protect device-specific scheduling information from being obtained by other devices. For example, two different MCS index table may be defined to indicate device-specific MCS information for two independent devices scheduled by a group common DCI.

Embodiment 4

In this embodiment, a two-stage scheduling information transmission structure for transmitting scheduling information in a group common DCI is defined. For example, the two-stage scheduling information transmission structure can be called as two-stage DCI. In the first stage, the WANN 110 may transmit a portion of the scheduling information, referred to as first stage DCI information, in the group common DCI. In the second stage, the WANN 110 may transmit remained scheduling information, referred to as second stage DCI information, in the group common DCI.

In some implementations, the two-stage DCI may be transmitted in different channels. For example, the first stage DCI information may be transmitted on a control channel, for example, carried on a PDCCH. The second stage DCI information may be transmitted on a data transmission channel, for example, carried on a PDSCH.

In some implementations, the two-stage DCI may be used for scheduling transmission of multiple devices.

In some implementations, the two-stage DCI may be carried by different numbers of DCI messages. The first stage DCI information may be carried by a single DCI message to be received by multiple devices. The second stage DCI information may be carried in different DCI messages to be respectively received by each device.

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

In some implementations, the first stage DCI information may include at least one of identifier for CI format, 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, virtual resource block (VRP) -to-physical resource block (PRB) mapping, PRB bundling size indicator, rate matching indicator, or ZP CSI-RS trigger.

In some implementations, the second stage DCI information may include at least one of modulation and coding scheme (MCS) , new data indicator (NDI) , redundancy version (RV) .

In some implementations, some DCI fields may not be fixed in the first stage DCI information or the second stage DCI information, which means the DCI fields may be included the first stage DCI information or the second stage DCI information according to specific transmission situations. Such fields may include one or more of HPN, SRS request, SRS offset indicator, PUCCH resource indicator (PRI) , PDSCH-to-HARQ_feedback timing indicator, transmission configuration indication (TCI) , CBG (code block group) transmission information (CBGTI) , downlink assignment indicator (DAI) , transmission power command (TPC) for the scheduled PUSCH, SRS resource set indicator, SRS resource indicator, preceding information and number of layers, Antenna ports, PTRS-DMRS association, beta_offset indicator, DMRS sequence initialization, UL-SCH indicator, CSI request, open-loop power control parameter set indication, TPC for PUCCH, One-shot HARQ-ACK request, enhanced Type-3 codebook indicator, PDSCH group index, new feedback indicator, number of request PDSCH groups, HARQ-ACK re-transmission indicator, CBG flushing out information (CBGFI) , or PUCCH cell indicator.

The present disclosure describes methods, apparatuses, and computer-readable medium for wireless communication. The present disclosure addresses the issues with optimizing wireless communication configurations. The methods, apparatuses, and computer-readable medium described in the present disclosure may facilitate the performance of wireless communication, thus improving efficiency and overall performance. The methods, apparatuses, and computer-readable medium described in the present disclosure may improves the overall efficiency of the wireless communication systems.

In some other embodiments, a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the above methods. The computer-readable medium may be referred as non-transitory computer-readable media (CRM) that stores data for extended periods such as a flash drive or compact disk (CD) , or for short periods in the presence of power such as a memory device or random access memory (RAM) .

In some embodiments, computer-readable instructions may be included in a software, which is embodied in one or more tangible, non-transitory, computer-readable media. Such non-transitory computer-readable media can be media associated with user-accessible mass storage as well as certain short-duration storage that are of non-transitory nature, such as internal mass storage or ROM. The software implementing various embodiments of the present disclosure can be stored in such devices and executed by a processor (or processing circuitry) . A computer-readable medium can include one or more memory devices or chips, according to particular needs. The software can cause the processor (including CPU, GPU, FPGA, and the like) to execute particular processes or particular parts of particular processes described herein, including defining data structures stored in RAM and modifying such data structures according to the processes defined by the software.

Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.

Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments, for non-limiting examples, a portion from one or more embodiment may be combined with another portion of other embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.

Claims

A method for wireless communication, comprising:

configuring, by a wireless access network node (WANN) , a single downlink control information (DCI) to schedule for transmissions of a set of user equipments (UEs) , wherein at least a portion of scheduling information for a UE in the set of UEs and at least a portion of scheduling information for another UE in the set of UEs are configured separately in the single DCI;

transmitting, by the WANN, the single DCI to the set of UEs.
The method of claim 1, wherein the transmissions of a set of UEs are multiple independent unicast transmissions or UE collaborative transmissions, and information is exchanged between the set of UEs through UE-to-UE interfaces in UE collaborative transmissions.
The method of claim 1, further comprising:

identifying a subset of UEs from the set of UEs for each specific scheduling process, wherein at least a portion of scheduling information in the single DCI is configured separately for each UE in the subset of UEs.
The method of claim 3, wherein the single DCI comprises a UE combination indicator field indicating the identified subset of UEs.
The method of claim 4, further comprising:

configuring an identifier for each UE in the set of UEs, and the UE combination indicator field indicates the identified subset of UEs by identifiers of UEs in the identified subset UEs.
The method of claim 4, wherein the UE combination indicator field comprising an index of an entry in a UE combination table, the UE combination table comprises a plurality of predetermined entries, each entry indicates a different identified subset of UEs.
The method of claim 4, wherein the UE combination indicator field comprises a bitmap indicating the identified subset of UEs.
The method of claim 1, wherein the single DCI comprises a plurality of fields, and the method further comprises:

categorizing the plurality of fields into a plurality of field types based on scheduling information configured for the set of UEs in the fields.
The method of claim 8, wherein the plurality of field types comprises a first field type and a second field type, schedule information in a field with the first field type is configured commonly for each of the set of UEs, and schedule information in a field with the second field type is configured separately for UEs in the set of UEs.
The method of claim 9, wherein the plurality of field types further comprises a third field type, a field with the third field type is configurably designated to belong to the first field type and the second field type.
The method of claim 9, further comprising:

in response to a field of the single DCI belonging to the second field type, configuring a field value combination table for the field, the field value combination table comprises a plurality of predetermined entries, each of which indicates a combination of separate values of the field, the separate values are respectively configured for UEs in the set of UEs; and

assigning an index of the field value combination table to the field of the single DCI.
The method of claim 8, further comprising:

predefining a field type of each field in the single DCI based on transmission scheme.
The method of claim 8, further comprising:

determining a field type for each field in the single DCI based on transmission scheme applied to the transmission of the set of UEs.
The method of claim 13, further comprising:

transmitting, to the set of UEs, a signaling carrying information on the determined field types.
The method of claim 1, further comprising:

transmitting, to each UE in the set of UEs, a UE specific signaling carrying information locating fields configured for the UE in the single DCI, the fields comprising commonly configured fields and separately configured fields for the UE, the signaling is a Radio Resource Control (RRC) signaling or another higher layer signaling.
The method of claim 15, wherein the information locating the fields configured for the UE comprising a start position of each commonly configured field, a start position of each separately configured field configured for the UE, and a length of each of the field, each UE in the set of UEs has a same start position in the single DCI for a commonly figured field and each UE in the set of UEs has a different start position for a separately configured field.
The method of claim 1, further comprising:

transmitting, to the set of UEs, a common signaling carrying information locating a first block of fields in the single DCI, each field in the first block of fields is configured for the set of UEs with a common field value.
The method of claim 17, wherein the information locating the first block of fields comprising a start position of the first block of fields and a length of the first block of fields.
The method of claim 1, further comprising:

transmitting, to a specific UE in the set of UEs, a UE specific signaling carrying information locating fields configured for the UE in the single DCI, each field is configured separately for UEs in the set of UEs.
The method of claim 19, wherein the information locating fields comprising a start position of each field configured for the specific UE and a length of the field configured for the specific UE.
The method of claim 1, further comprising:

transmitting, to a specific UE in the set of UEs, a UE specific signaling carrying information locating a second block of fields in the single DCI, each field in the second block of fields is configured for UEs in the set of UEs with separate field values.
The method of claim 21, wherein the information locating the second block of fields comprising a start position of the second block of fields configured for the specific UE and a length of the second block of fields configured for the specific UE.
The method of claim 1, wherein the transmissions of the set of UEs are collaborative transmissions, and the method further comprises:

defining an index for each UE in the set of UEs, and a location of a field configured for the UE in the single DCI is determined by the index of the UE and a length of the field.
The method of claim 1, wherein the transmitting the single DCI to the set of UEs comprises:

splitting scheduling information in the single DCI into a plurality of scheduling information portions; and

separately transmitting the plurality of scheduling information portions to the set of UEs.
The method of claim 24, further comprising:

transmitting the plurality of scheduling information portions via different channels, the different channels comprise at least a control channel or a data transmission channel.
The method of claim 24, wherein the plurality of scheduling information portions comprises a first scheduling information portion and a second scheduling information portion, the first scheduling information portion comprises scheduling information configured commonly for each of the set of UEs, the second scheduling information portion comprises scheduling information configured separately for UEs in the set of UEs.
The method of claim 26, wherein the separately transmitting the plurality of scheduling information portions to the set of UEs comprises:

transmitting a first common message carrying the first scheduling information portion to the set of UEs; and

separately transmitting, to each UE of the set of UEs, a second message carrying the second scheduling information portion.
The method of claim 1, further comprising:

configuring a same radio network temporary identifier (RNTI) for the set of UEs, and the RNTI is used for a single DCI scrambling.
The method of claim 1, further comprising:

defining a UE specific scheduling information indication rule for UEs of the set of UEs.
A method for wireless communication, comprising:

receiving, by a first user equipment (UE) , a single downlink control DCI from a wireless access network node (WANN) , wherein the single DCI is configured to schedule for transmissions of a set of UEs including the first UE, at least a portion of scheduling information for a UE in the set of UEs and at least a portion of scheduling information for another UE in the set of UEs are configured separately in the single DCI.
The method of claim 30, wherein the transmissions of a set of UEs are multiple independent unicast transmissions or UE collaborative transmissions, and information is exchanged between the set of UEs through UE-to-UE interfaces in UE collaborative transmissions.
The method of claim 30, wherein a subset of UEs from the set of UEs is identified for each specific scheduling process, and at least a portion of scheduling information in the single DCI is configured separately for each UE in the subset of UEs.
The method of claim 32, wherein the single DCI comprises a UE combination indicator field indicating the identified subset of UEs.
The method of claim 33, wherein the UEs in the set are numbered, each UE in the set of UEs has an identifier, and the UE combination indicator field indicates the identified subset of UEs by identifiers of UEs in the identified subset UEs.
The method of claim 34, wherein the UE combination indicator field indicates the identified subset of UEs by an index of an entry in a UE combination table, the UE combination table comprises a plurality of predetermined entries, each entry indicates a different subset of UEs.
The method of claim 33, wherein the UE combination indicator field comprises a bitmap indicating the identified subset of UEs.
The method of claim 30, wherein the single DCI comprises a plurality of fields, and the plurality of fields are categorized into a plurality of field types based on scheduling information configured for the set of UEs in the fields.
The method of claim 37, wherein the plurality of field types comprises a first field type and a second field type, schedule information in a field with the first field type is configured commonly for each of the set of UEs, and schedule information in a field with the second field type is configured separately for UEs in the set of UEs.
The method of claim 38, wherein the plurality of field types further comprises a third field type, a field with the third field type is configurably designated to belong to the first field type and the second field type.
The method of claim 38, further comprising:

in response to a field of the single DCI belonging to the second field type, obtaining a field value combination table for the field, the field value combination table comprises a plurality of predetermined entries, each of which indicates a combination of separate values of the field, the separate values are respectively configured for UEs in the set of UEs.
The method of claim 37, further comprising:

obtaining a field type for each field in the single DCI based on transmission scheme applied to the transmission of the set of UEs.
The method of claim 37, further comprising:

receiving, from the WANN, a signaling carrying information on the determined field types.
The method of claim 30, further comprising:

receiving, from the WANN, a UE specific signaling carrying information locating fields configured for the first UE in the single DCI, the fields comprising commonly configured fields and separately configured fields for the first UE, the signaling is a Radio Resource Control (RRC) signaling or another higher layer signaling.
The method of claim 43, wherein the information locating the fields configured for the first UE comprising a start position of each commonly configured field, a start position of each separately configured field configured for the first UE, and a length of each of the field, each UE in the set of UEs has a same start position in the single DCI for a commonly figured field and each UE in the set of UEs has a different start position for a separately configured field.
The method of claim 30, further comprising:

receiving, from the WANN, a common signaling carrying information locating a first block of fields in the single DCI, each field in the first block of fields is configured for the set of UEs with a common field value.
The method of claim 45, wherein the information locating the first block of fields comprising a start position of the first block of fields and a length of the first block of fields.
The method of claim 30, further comprising:

receiving, from the WANN, a UE specific signaling carrying information locating fields configured for the first UE in the single DCI, each field is configured separately for UEs in the set of UEs.
The method of claim 47, wherein the information locating fields comprising a start position of each field configured for the first UE and a length of the field configured for the first UE.
The method of claim 30, further comprising:

receiving, from the WANN, a UE specific signaling carrying information locating a second block of fields in the single DCI, each field in the second block of fields is configured for UEs in the set of UEs with separate field values.
The method of claim 49, wherein the information locating the second block of fields comprising a start position of the second block of fields configured for the first UE and a length of the second block of fields configured for the first UE.
The method of claim 30, wherein the transmissions of the set of UEs are collaborative transmissions, an index is defined for each UE in the set of UEs, and a location of a field configured for the first UE in the single DCI is determined by the index of the first UE and a length of the field.
The method of claim 30, wherein the scheduling information in the single DCI is split into a plurality of scheduling information portions, the method further comprises:

separately receiving, from the WANN, the plurality of scheduling information portions.
The method of claim 52, wherein the plurality of scheduling information portions are received via different channels, the different channels comprises a control channel and a data transmission channel.
The method of claim 52, wherein the plurality of scheduling information portions comprises a first scheduling information portion and a second scheduling information portion, the first scheduling information portion comprises scheduling information configured commonly for each of the set of UEs, the second scheduling information portion comprises scheduling information configured separately for UEs in the set of UEs.
The method of claim 54, further comprising:

receiving, from the WANN, a first common message carrying the first scheduling information portion; and

receiving, from the WANN, a second message carrying the second scheduling information portion.
The method of claim 30, wherein the set of UEs are configured with a same radio network temporary identifier (RNTI) , and the RNTI is used for the single DCI scrambling.
The method of claim 30, further comprising:

a UE specific scheduling information indication rule is defined at least for a portion fields in the single DCI for UE of the set of UEs.
A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 57.
A non-transitory computer program product comprising a computer-readable program medium code stored thereupon, the computer-readable program medium code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 57.