WO2023279389A1 - 组调度指令处理方法及装置、通信设备及存储介质 - Google Patents

组调度指令处理方法及装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2023279389A1
WO2023279389A1 PCT/CN2021/105565 CN2021105565W WO2023279389A1 WO 2023279389 A1 WO2023279389 A1 WO 2023279389A1 CN 2021105565 W CN2021105565 W CN 2021105565W WO 2023279389 A1 WO2023279389 A1 WO 2023279389A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
dci
type
information
ues
Prior art date
Application number
PCT/CN2021/105565
Other languages
English (en)
French (fr)
Inventor
李艳华
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202180002110.XA priority Critical patent/CN115868233B/zh
Priority to PCT/CN2021/105565 priority patent/WO2023279389A1/zh
Priority to EP21948883.0A priority patent/EP4366427A1/en
Publication of WO2023279389A1 publication Critical patent/WO2023279389A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H04W72/232—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the physical layer, e.g. DCI signalling

Definitions

  • the present disclosure relates to the technical field of wireless communication but is not limited to the technical field of wireless communication, and in particular relates to a method and device for processing a group scheduling instruction, a communication device, and a storage medium.
  • Multimodality involves multiple sources or forms of information. For example, people have senses of touch, hearing, vision, and smell; the medium of information includes voice, video, and text. In order to perceive user input from multiple dimensions, there are many types and quantities of applications (Application, App) and/or devices used for multimodal information collection, including multiple cameras, speakers, sensors, keyboards, and fingerprint collectors etc. These devices for collecting multiple modal information can be used in the same device or across devices. On the server side, data fusion (Data Fusion) of multi-modal data sets is also called information fusion (Information Fusion), which is to synthesize and combine incomplete information about a certain environmental characteristic provided by multiple sensors or information sources.
  • Data Fusion data fusion
  • Information Fusion Information Fusion
  • the server After the server completes data fusion and makes a decision, it obtains multimodal output.
  • This process is a service distribution process. Often the service is not distributed to a single device, but is likely to be a linkage of several related devices. For example, judging the owner's return through voiceprint and video can trigger the curtains to be drawn and the air conditioner to be turned on at the same time. This also involves the issue of group collaboration between multiple output devices.
  • Embodiments of the present disclosure provide a method and device for processing a group scheduling instruction, a communication device, and a storage medium.
  • the first aspect of the embodiments of the present disclosure provides a method for processing a group scheduling instruction, which is executed by a network device, and the method includes:
  • UE User Equipment
  • the second aspect of the embodiments of the present disclosure provides a method for processing a group scheduling instruction, which is performed by a UE, and the method includes:
  • a group scheduling instruction for a user equipment UE group is received, wherein the UE group includes one or more UEs.
  • the third aspect of the embodiments of the present disclosure provides an apparatus for processing group scheduling instructions, which is executed by a network device, and the apparatus includes:
  • a sending module configured to send a group scheduling instruction for a user equipment UE group, where the UE group includes one or more UEs.
  • the fourth aspect of the embodiments of the present disclosure provides an apparatus for processing a group scheduling instruction, wherein, executed by a UE, the apparatus includes:
  • the receiving module is configured to receive a group scheduling instruction for a user equipment UE group, wherein the UE group includes one or more UEs.
  • the fifth aspect of the embodiments of the present disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein the processor runs the executable When the program is executed, a group scheduling instruction processing method is provided as described in the first aspect or the second aspect.
  • the sixth aspect of the embodiments of the present disclosure provides a computer storage medium, the computer storage medium stores an executable program; after the executable program is executed by a processor, it can realize the combination provided by the aforementioned first aspect or the second aspect. Scheduling command processing method.
  • the network side can issue a group scheduling instruction, so as to realize the scheduling of the entire UE group, and has the characteristics of low scheduling signaling overhead and high efficiency.
  • Fig. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • Fig. 2 is a schematic flowchart of a method for processing a group scheduling instruction according to an exemplary embodiment
  • Fig. 3 is a schematic diagram showing a first type of DCI according to an exemplary embodiment
  • Fig. 4 is a schematic diagram showing a second type of DCI according to an exemplary embodiment
  • Fig. 5 is a schematic diagram showing a third type of DCI according to an exemplary embodiment
  • Fig. 6 is a schematic diagram of a third type of DCI according to an exemplary embodiment
  • Fig. 7 is a schematic flowchart of a method for processing a group scheduling instruction according to an exemplary embodiment
  • Fig. 8 is a schematic flowchart of a method for processing a group scheduling instruction according to an exemplary embodiment
  • Fig. 9 is a schematic flowchart of a method for processing a group scheduling instruction according to an exemplary embodiment
  • Fig. 10 is a schematic structural diagram of a device for processing group scheduling instructions according to an exemplary embodiment
  • Fig. 11 is a schematic structural diagram of a device for processing group scheduling instructions according to an exemplary embodiment
  • Fig. 12 is a schematic structural diagram of a UE according to an exemplary embodiment
  • Fig. 13 is a schematic structural diagram of a communication device according to an exemplary embodiment.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of the embodiments of the present disclosure, first information may also be called second information, and similarly, second information may also be called first information. Depending on the context, the word “if” as used herein may be interpreted as “at” or "when” or "in response to a determination.”
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: several UEs 11 and several access devices 12 .
  • UE11 may be a device that provides voice and/or data connectivity to a user.
  • UE11 can communicate with one or more core networks via a radio access network (Radio Access Network, RAN), and UE11 can be an Internet of Things UE, such as a sensor device, a mobile phone (or called a "cellular" phone) and a device with an Internet of Things
  • RAN Radio Access Network
  • UE11 can be an Internet of Things UE, such as a sensor device, a mobile phone (or called a "cellular" phone) and a device with an Internet of Things
  • the UE's computer for example, may be a fixed, portable, pocket, hand-held, built-in or vehicle-mounted device.
  • UE11 may also be a device of an unmanned aerial vehicle.
  • UE11 may also be a vehicle-mounted device, for example, it may be a trip computer with a wireless communication function, or a wireless communication device connected externally to the trip computer.
  • the UE11 may also be a roadside device, for example, it may be a street lamp, a signal lamp, or other roadside devices with a wireless communication function.
  • the access device 12 may be a network side device in a wireless communication system.
  • the wireless communication system may be a fourth generation mobile communication technology (the 4th generation mobile communication, 4G) system, also known as a Long Term Evolution (LTE) system; or, the wireless communication system may also be a 5G system, Also known as new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network, New Generation Radio Access Network).
  • the MTC system the MTC system.
  • the access device 12 may be an evolved access device (eNB) adopted in a 4G system.
  • the access device 12 may also be an access device (gNB) adopting a centralized and distributed architecture in the 5G system.
  • eNB evolved access device
  • gNB access device
  • the access device 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is provided with a packet data convergence protocol (Packet Data Convergence Protocol, PDCP) layer, radio link layer control protocol (Radio Link Control, RLC) layer, media access control (Media Access Control, MAC) layer protocol stack;
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC media access control
  • a physical (Physical, PHY) layer protocol stack is set in the unit, and the embodiment of the present disclosure does not limit the specific implementation manner of the access device 12 .
  • a wireless connection may be established between the access device 12 and the UE 11 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on a technical standard of a next-generation mobile communication network based on 5G.
  • an E2E (End to End, end-to-end) connection can also be established between UE11.
  • V2V vehicle to vehicle, vehicle-to-vehicle
  • V2I vehicle to Infrastructure, vehicle-to-roadside equipment
  • V2P vehicle to pedestrian, vehicle-to-person communication in vehicle to everything (V2X) communication Wait for the scene.
  • the above wireless communication system may further include a network management device 13 .
  • the network management device 13 may be a core network device in the wireless communication system, for example, the network management device 13 may be a mobility management entity (Mobility Management Entity, MME).
  • MME Mobility Management Entity
  • the network management device can also be other core network devices, such as Serving GateWay (SGW), Public Data Network Gateway (Public Data Network GateWay, PGW), policy and charging rule functional unit (Policy and Charging Rules Function, PCRF) or Home Subscriber Server (Home Subscriber Server, HSS), etc.
  • SGW Serving GateWay
  • PGW Public Data Network Gateway
  • PCRF Policy and Charging Rules Function
  • HSS Home Subscriber Server
  • an embodiment of the present disclosure provides a group scheduling instruction processing method, which is executed by a network device, and the method includes:
  • S110 Send a group scheduling instruction for a UE group, where the UE group includes one or more UEs.
  • the network equipment includes but is not limited to access equipment such as a base station.
  • the network device issues a group scheduling instruction for a UE group, and the group scheduling instruction is for a UE group.
  • This newly introduced group scheduling instruction can be scheduled for a specific UE group, and has the characteristics of high scheduling flexibility.
  • multiple UEs in the UE group have associated or similar UEs in service; or, the UEs in the UE group have frequent data interaction.
  • the UEs in the UE group can be jointly scheduled through the group scheduling instruction.
  • scheduling optimization such as scheduling synchronization can be realized; Know the scheduling situation of other UEs.
  • the UE group includes one or more of the following UEs:
  • Multimodal output UE
  • a graphics device outputs images
  • an audio device outputs audio
  • a camera device captures images.
  • the services of these devices are related, and these devices are all connected to the network, and they are all UEs of the network; these devices can be called multi-mode output UEs, and can be grouped into a UE group.
  • a federated learning UE may be used for multiple UEs for federated training of a machine learning model.
  • the UE group where the federated learning UE belongs can be called the federated learning UE group.
  • resource scheduling is performed on the UEs in the federated learning UE group through group scheduling instructions.
  • UEs that need to communicate may communicate well based on a scheduling instruction.
  • the group scheduling instruction is: downlink control information DCI of a group type physical downlink control channel PDCCH; wherein, the group type PDCCH DCI is: the UE group targeted for transmission through the physical downlink control channel PDCCH The downlink control information DCI.
  • the foregoing group scheduling instruction may be a physical layer scheduling instruction.
  • DCI at the physical layer has the characteristics of high scheduling dynamics and low delay.
  • the UE group has a group radio network temporary identity (Radio Network Tempory Identity, RNTI), wherein the group RNTI is at least used to scramble the group type PDCCH DCI.
  • group radio network temporary identity Radio Network Tempory Identity, RNTI
  • a group RNTI is configured for the UE group, and the group RNTI is for the entire UE group, and all UEs in the UE group know it.
  • the group RNTI here is different from the RNTI of a single UE. If a UE is in a UE group, it may have a group RNTI at the same time, and may also have an RNTI for communication between itself and a network device.
  • the set of RNTIs includes at least one of the following:
  • the downlink group RNTI is used for scrambling the downlink transmission of the UE group
  • the uplink group RNTI is used for scrambling the uplink transmission of the UE group
  • the uplink and downlink common group RNTI can be used for scrambling the uplink transmission and downlink transmission of the group.
  • the downlink group RNTI can be set separately for this UE group , the downlink group RNTI can be used by the network side to scramble the downlink transmission of these UEs.
  • This downlink group RNTI can be dedicated to scrambling of downlink transmission.
  • the downlink transmission here includes but not limited to downlink instructions and/or downlink data.
  • the downlink instructions include but not limited to downlink scheduling instructions.
  • the downlink scheduling instruction here may include but not limited to the aforementioned group scheduling instruction.
  • Some UE groups may upload synchronously. For example, multiple cameras capture different videos captured in the same capture scene. These videos can be spliced into stereoscopic videos or used for simultaneous live broadcast.
  • the UE composed of such camera devices may have a large amount of data that needs to be synchronized or associated with the transmission.
  • the uplink group RNTI for such UE group uplink transmission can be set. This uplink group RNTI can be dedicated to the RNTI for downlink transmission.
  • the uplink group RNTI and the downlink group RNTI can be configured at the same time.
  • the group RNTI configured for this UE group may be a general uplink group RNTI that can be used for both downlink transmission scrambling and uplink transmission scrambling.
  • the group type PDCCH DCI includes one of the following:
  • the first type of DCI wherein the first type of DCI has different independent authorization information for a single UE in the UE group;
  • the second type of DCI wherein the first type of DCI is for public grant information of all UEs in the UE group; wherein the public grant information is used for resource scheduling of UEs in the UE group;
  • the third type of DCI wherein the third type of DCI is for public information of at least some UEs in the UE group and for independent information of a single UE in the UE group.
  • the first type of DCI may include one or more grant blocks, and the one or more grants may consist of one or more bits. Different authorization blocks may correspond to different bits.
  • FIG. 3 is a structural diagram of the first type of DCI.
  • authorization block 1 can be used for UE1 in the UE group
  • authorization block 2 can be used for UE2 in the UE group
  • authorization block 3 can be used for UE3 in the UE group.
  • different grant blocks may be used to schedule different UEs in the same UE group.
  • the authorization block can be used for resource scheduling and/or transmission parameter configuration of the UE.
  • the transmission parameters include but are not limited to the configuration of Modulation and Coding Scheme (MCS).
  • UEs within a UE group have group numbers and the like.
  • the UE can determine which authorization block is used for its own scheduling according to the correspondence between the sequence number of the authorization block in the first type of DCI and the group number.
  • the nth grant block in the first type of DCI can be used for scheduling the UE whose group number is n in the UE group.
  • the first type of DCI can be scrambled with the group RNTI as a whole, and different grant blocks can be scrambled with the RNTI of a single UE.
  • the UE receives the first type of DCI, it can use the group RNTI first.
  • the RNTI descrambles, and then uses its own RNTI to perform descrambling.
  • the authorization block that is successfully descrambled is its own scheduling. In this way, the ordering of the authorization blocks of the first type of DCI can be flexibly set.
  • some common parameters in each grant block can share a common part (common part). For example, when UEs in a UE group are relatively close geographically and have little difference in channel status, a common MCS level can be shared to save signaling overhead.
  • UE scheduling can be performed with maximum flexibility.
  • the public grant information carried by the second type of DCI is scheduled for the entire UE, for example, the public grant information schedules the resource pool available to the entire UE group. Which resource is used by which UE in the UE group may be related to authorization rules related to resource allocation between UEs in the UE group.
  • the second type of DCI schedules a segment of resources.
  • the UE After receiving the second type of DCI, the UE knows the resource pool corresponding to the entire UE group, and then according to the resource sharing policy and its own group number in the UE group, first Divide the resources equally into shares equal to the number of UEs in the UE group, and then select the Mth resource as the resource to be scheduled according to its own group number M.
  • the resource pool corresponding to the entire UE group
  • the resource sharing policy and its own group number in the UE group first Divide the resources equally into shares equal to the number of UEs in the UE group, and then select the Mth resource as the resource to be scheduled according to its own group number M.
  • FIG. 4 is a schematic diagram of a second type of DCI.
  • the public grant information included in the second type DCI is used to determine resource scheduling for a single UE according to grant rules.
  • the authorization rules include:
  • the authorization rule is used to determine the resource allocation of UEs in the UE group.
  • the network device negotiates the authorization rules with any UE in the UE group or the main UE in the UE group, and finally notifies each UE of the authorization rules, so that the subsequent scheduling can be performed directly according to the pre-negotiated authorization rules.
  • Resource allocation is enough.
  • the authorization rule may be stipulated in a protocol, and the protocol may be a communication standard protocol or a private protocol that is commonly observed by multiple manufacturers.
  • the authorization rules can be written into the protocol.
  • both the network device and the UE will write it in advance, so that the UE and the network device can know without exchanging information.
  • the base station directly delivers the identification of the corresponding authorization rule to the UE, and the UE can know the authorization rule for resource allocation between UEs indicated by the network device after receiving it.
  • the public authorization information carried by the second type of DCI can save the bit overhead of the DCI in this manner to the greatest extent.
  • the group-type DCI may further include a third-type DCI different from the foregoing first-type DCI and/or second-type DCI.
  • the third type of DCI can be understood as a mixture of the first type of DCI and the second type of DCI to a certain extent.
  • the third type of DCI may include a common part and an independent part, the common part may be used to carry common information, and the independent part may be used for independent information for a single UE.
  • FIG. 5 is a schematic diagram of a third type of DCI.
  • public information and two independent information are shown, which are independent information 1 and independent information 2 respectively; the independent information 1 and independent information 2 here can be aimed at different UEs in the UE group.
  • the public part carrying the public information can be set in the middle part of the bits contained in the third type DCI, and the independent information can be set in the middle part of the bits contained in the third type DCI. edge part.
  • the public information may be information for at least two UEs in the UE group; and the independent information may be information for a single UE in the UE group.
  • the public information may be information for all UEs in the entire UE group.
  • the public information may be information of some UEs in the UE group. For example, assuming that all UEs in the UE group use the same MCS, the indication of the MCS at this time can be implemented by public information. For another example, if the resources of different UEs in the UE group are different, then the independent information indicates different resources of each UE.
  • the resource identifiers of the frequency-domain resources can be carried in the public information, and the resource identifiers of different UEs can be The indication information of the time domain position is carried in the independent information.
  • the third type of DCI has both a part carrying public information and a part carrying independent information.
  • the bit overhead can be reduced through the part corresponding to the public information, and flexible scheduling can be realized through the part of independent information. , which strikes a good balance between bit overhead and flexible scheduling.
  • the third type of DCI includes:
  • Level 1 DCI and at least one Level 2 DCI.
  • the relationship between the first-level DCI and the second-level DCI may include:
  • the primary DCI indicates the common information
  • the secondary DCI indicates the independent information
  • the first-level DCI is the scheduling DCI of the second-level DCI, that is, the first-level DCI is also used for scheduling the second-level DCI.
  • the first-level DCI is used to schedule the second-level DCI, it can be determined whether the second-level DCI needs to be scheduled according to whether there is independent information for UEs in the UE group. If there is independent information for a UE in the UE group, the second-level DCI At this time, the first-level DCI will schedule the second-level DCI. After receiving the first-level DCI, the UEs in the UE group receive the second-level DCI on the corresponding resources according to the scheduling information of the second-level DCI carried by the first-level DCI. If there is currently no independent information for a single UE in the UE group, only the first-level DCI in the third type of DCI is used to implement the scheduling of the UE group.
  • the number of bits included in the first-level DCI may be fixed, and some bits in the first-level DCI are used for scheduling the second-level DCI.
  • the number of bits of the secondary DCI is variable, and the specific number of bits contained in the secondary DCI may be determined according to the bit overhead of the independent information, or the number of UEs to receive the independent information. Generally, the greater the bit overhead of the independent information, the more bits the secondary DCI contains, and/or the greater the number of UEs to receive the independent information, the greater the number of authorized blocks carried by the secondary DCI, Then the bit number of the corresponding secondary DCI is also more.
  • the third type of DCI has a first-level DCI and a second-level DCI in the setting format of the DCI, but in specific applications, whether the third-type DCI delivers the second-level DCI needs to be based on whether there is currently It is determined by the independent information of a certain UE in the UE. As shown in FIG. 6, the third type DCI can be divided into two levels.
  • an obvious delimiter can be set for different levels of DCI. For example, there is a delimiter between the first-level DCI and the second-level DCI, and the delimiter may be composed of a preset sequence.
  • the first-level DCI and the second-level DCI can be scrambled with different scrambling sequences, so after receiving it, the UE can know which is the first-level DCI and which is the second-level DCI according to the different scrambling sequences .
  • the primary DCI may be scrambled using the group RNTI
  • the secondary DCI may be scrambled using the RNTI of the scheduled UE itself.
  • a UE group can have multiple group RNTIs. At this time, the primary DCI and secondary DCI can be scrambled with different group RNTIs. In this case, there is no need to set a separator, and the UE receives the third Type DCI can also be divided into primary DCI and secondary DCI.
  • the position and/or length of the first-level DCI may be relatively fixed.
  • the UE can first determine the first-level DCI according to the configuration of the position and/or length of the first-level DCI. DCI and other backups can be considered as secondary DCI.
  • Fig. 6 is a group type PDCCH DCI including both primary DCI and secondary DCI.
  • Different authorization blocks may be included in the secondary DCI, and different authorization blocks may be aimed at different UEs in the UE group.
  • an embodiment of the present disclosure provides a method, which may include:
  • S210 Receive capability information reported by the UE, where the capability information indicates a type of scheduling instruction supported by the corresponding UE.
  • the step S210 of receiving capability information may be performed alone, or may be performed in combination with the aforementioned step S110 and the like.
  • S210 may be executed first, so as to determine whether all UEs in the corresponding UE group support the group scheduling instruction according to the received capability information, and then it may be determined to send the group scheduling instruction for the UE group.
  • group scheduling instructions can still be used for most of the UE group, and individual UEs that do not support group scheduling instructions can be scheduled separately, which can still reduce signaling Purpose of overhead and scheduling times.
  • scheduling instructions include at least one of the following:
  • the scheduling instruction for all UEs in the cell can generally be a broadcast instruction.
  • the capability information may be used to indicate whether the UE supports the group scheduling instruction.
  • the UE can at least receive and decode the corresponding group scheduling instruction.
  • all UEs in a UE group are peers, that is, all UEs in the UE group are not managed or managed, represent or be represented, and so on.
  • the first type of UE can be a management UE
  • the second type of UE can be an ordinary UE
  • the management UE may manage or represent the second type of UE to transmit and send and receive information related to UE group communication with the network side.
  • this is just an example.
  • the network side can determine whether the corresponding UE supports the group scheduling instruction, or which types of scheduling instructions it supports.
  • the capability information indicates at least one of the following:
  • the UE supports the type of the decoded scheduling instruction, and the type of the scheduling instruction includes: a group scheduling instruction for a group of UEs and/or an individual scheduling instruction for a single UE.
  • an embodiment of the present disclosure provides a method for processing a group scheduling instruction, which is executed by a UE, and the method includes:
  • S310 Receive a group scheduling instruction for a UE group, where the UE group includes one or more UEs.
  • the UE may be various types of UEs.
  • the UE may be a wearable device such as a mobile phone, a tablet computer, a smart watch, or smart glasses, a vehicle-mounted device, a smart home device, or a smart office device.
  • the UE may be a terminal device that has joined a UE group.
  • the UE will receive a group scheduling instruction for the UE group.
  • the group scheduling instruction for the UE group may include: a scheduling instruction for multiple UEs in the UE group.
  • the scheduling instruction is a group scheduling instruction, which has the characteristics of small signaling overhead and high scheduling efficiency.
  • the group of UEs has a group RNTI; the method further comprises:
  • the set of dispatch instructions is descrambled based on the set of RNTIs.
  • the group RNTI here may be the RNTI pre-allocated to the UE group by the network side.
  • the RNTI allocated when the network side establishes the UE group or the RNTI for the UE group after the UE group is established is the RNTI for the UE group, so it is called the group RNTI.
  • the group of RNTIs may be delivered through RRC layer messages such as RRC signaling. Of course, only the message of sending the group RNTI is illustrated here, and the specific implementation is not limited thereto.
  • the group RNTI can also be received based on the MAC CE sent by the base station side.
  • the set of RNTIs includes at least one of the following:
  • the downlink group RNTI is used for scrambling the downlink transmission of the UE group
  • the uplink group RNTI is used for scrambling the uplink transmission of the UE group
  • the uplink and downlink common group RNTI can be used for scrambling the uplink transmission and downlink transmission of the group.
  • a UE group may have one or more group RNTIs. According to the function of the group RNTI can be divided into:
  • Downlink group RNTI which can scramble downlink transmission
  • Uplink group RNTI which can scramble uplink transmission
  • the RNTI of the uplink and downlink group can be used for scrambling of uplink transmission, and can also be used for scrambling of downlink transmission.
  • the UE in the UE group uses the group RNTI for scrambling and/or descrambling, it can use the corresponding group RNTI for scrambling and descrambling according to the transmission direction to be scrambled or to be scrambled.
  • the transmission direction here can be at least divided into: an uplink transmission direction from the UE to the network side, and/or a downlink transmission direction from the network side to the UE.
  • the group scheduling instruction includes: group type PDCCH DCI.
  • the group scheduling instruction is a kind of DCI for PDCCH transmission. And this group scheduling instruction is for the UE group, so the PDCCH DCI is called group type PDCCH DCI. DCI has the characteristics of high dynamics and low delay.
  • the group type PDCCH DCI includes at least one of the following:
  • the first type of DCI wherein the first type of DCI has different independent authorization information for a single UE in the UE group;
  • the second type of DCI wherein the first type of DCI is directed to public authorization information of all UEs in the UE group;
  • the third type of DCI wherein the third type of DCI is for public information of at least some UEs in the UE group and for independent information of a single UE in the UE group.
  • the first type of DCI includes authorization blocks; wherein different authorization blocks have corresponding relationships with different UEs in the UE group.
  • Different authorization blocks have corresponding relationships with different UEs in the UE group, so as to realize independent scheduling of sub-authorization blocks of a single UE.
  • the public authorization information directly carried by the second type DCI includes but is not limited to at least one of the following:
  • Indication information of authorization rules for resource allocation between different UEs in the UE group is not limited to:
  • the public authorization information included in the second type DCI includes:
  • the authorization rule is used to determine the resource allocation of UEs in the UE group.
  • the authorization rule may be agreed upon in the agreement, or negotiated in advance between the UE group and the network side equipment.
  • the prior negotiation here may occur when the UE group is established, or it may be when the UE group is established after.
  • the public information included in the third type DCI is used to indicate the parameters shared by at least some UEs in the UE group; the independent authorization information included in the third type DCI is used to indicate the UE Differential authorization parameters within a group.
  • the common parameters include: modulation and coding strategy MCS; and/or, the differential grant parameters include: resource scheduling parameters for different UEs within the UE.
  • the public information may be public information of resource scheduling of the UE group, the public information indicates the frequency domain resources and/or time domain resources used by the scheduled resources of each UE in the UE group, and the difference
  • the authorization parameter may indicate different time domain resources used by different UEs when using the same frequency domain resource, or indicate different frequency domain resources when different UEs use the same time domain resource.
  • the third type of DCI includes: primary DCI and at least one secondary DCI; wherein, the primary DCI indicates the common information; and the secondary DCI indicates the independent information.
  • the first-level DCI may directly carry public information
  • the second-level DCI may also directly carry independent information.
  • both the first-level DCI and the second-level DCI can realize the indication of common information and independent information through the corresponding relationship between the information carried by itself and the corresponding public information and independent information.
  • an embodiment of the present disclosure also provides a method, which can be executed by a UE, including:
  • S410 Report capability information to the base station, where the capability information at least indicates the type of scheduling instruction supported by the UE.
  • the capability information may at least indicate whether the UE supports the group scheduling instruction. For example, if the UE supports the group scheduling instruction, it indicates that the UE can receive the group scheduling instruction.
  • the group of scheduling instructions here may be the group of scheduling instructions mentioned in the foregoing embodiments.
  • scheduling coordination processing is added for newly added application scenarios in the network that require group synchronization.
  • the users who need group synchronization are multi-modal output UEs.
  • UEs requiring group synchronization may be federated learning UEs.
  • the network may schedule and group UEs according to the following scheme to obtain UE groups;
  • scheduling and grouping UEs may be grouping according to services to obtain UE groups
  • scheduling and grouping UEs may be grouping according to geographic locations to obtain UE groups.
  • the base station obtains grouping information of UEs from the core network, and schedules and groups the UEs to obtain UE groups;
  • the core network may directly carry the group ID (group ID) of the UE group to which the UE belongs.
  • the base station obtains information from the core network that requires coordinated scheduling of multiple UEs, thereby dividing the UEs into a UE group; for example, the core network indicates to the base station the minimum arrival time limit between data streams of multiple UEs
  • the quality of service (Quality of Service, QoS) requirement in order to meet the QoS requirement, the base station needs to perform cooperative scheduling or synchronous scheduling with UE group as the granularity for some UEs.
  • QoS Quality of Service
  • the group scheduling instruction provided by the network that is, the PDCCH DCI of the group (Group) type, performs group scheduling on the UE group users, specifically:
  • a group (Group) RNTI for group scheduling is introduced; the network notifies the UE of the group RNTI in advance through public signaling or dedicated signaling.
  • the group RNTI used for group scheduling can be used for scheduling in uplink and/or downlink directions;
  • the network device can issue the group RNTI1 in the uplink direction and the group RNTI2 in the downlink direction at the same time;
  • the network device can only deliver the group RNTI1 in the uplink direction;
  • the network device may only deliver the group RNTI2 in the downlink direction.
  • Group PDCCH DCI for group scheduling, where group RNTI will be used for scrambling group type PDCCH DCI (group PDCCH DCI) where the format of Group PDCCH DCI may be as follows:
  • the network can notify each UE of the position of its authorization information (authorization block) in the Group PDCCH DCI, and then the UE can find its corresponding authorization information for interpretation.
  • the authorization information of each UE can be used as an authorization block (block);
  • the authorization block (block1), the authorization block (block2), and the authorization block (block3) respectively identify the authorization of UE1, UE2, and UE3;
  • the UE performs reception on corresponding resources according to respective authorization information.
  • the DCI shown in FIG. 4 to FIG. 6 can be used.
  • each authorization block can be moved out and placed in a common part. For example, groups of UEs are often relatively close to each other, so there is little difference in channel status. For example, if there is a common MCS level, they can be shared to save signaling overhead.
  • a public authorization block (block0), which identifies part of the public information authorized by all UEs, followed by the authorization block (block1), authorization block (block2), and authorization block (block3), respectively Independent information identifying UE1, UE2, and UE3.
  • the index (index) of the UE in the group such as 0, 1, 2...
  • equal resources in the frequency domain are divided into three shares, and UEs numbered 0, 1, and 2 use the first share of frequency domain resources, the second share of frequency domain resources, and the third share of frequency domain resources.
  • frequency domain resources are divided into 3 shares.
  • UEs numbered 0, 1, and 2 use the first frequency domain resource, the second frequency domain resource, and the third frequency domain resource respectively.
  • the starting point and end point of their use can be in The network is informed in the DCI.
  • the third method the above two methods are used in combination, that is, the DCI carries a common piece of authorization information for shared use by some UEs, and may also carry separate authorization information for some UEs.
  • the separate authorization information here is the independent information mentioned in the foregoing embodiments.
  • the information shared and used by the UE is the aforementioned public information.
  • the first part uses method 1 to indicate the resource authorization of UE1 and UE2
  • the second part uses method 2 to indicate the resource authorization of UE3 and UE4.
  • the DCI corresponding to the first way indicates the authorization of UE1 and UE2, and there may be two ways:
  • authorization block (block1) For example: authorization block (block1), authorization block (block2), respectively identify the resource authorization of UE1 and UE2;
  • public authorization block (block0), identifying the public part parameters authorized by UE1 and UE2, followed by authorization block (block1), authorization block (block2), respectively identifying UE1, UE2, and other authorized resource parts;
  • the DCI corresponding to the second method indicates the authorization of UE3 and UE4, that is, carries a piece of public authorization information, and UE3 and UE4 are shared and used according to the rules defined in advance or notified by the network.
  • the DCI corresponding to the third manner may be as shown in FIG. 5 or FIG. 6 .
  • a group type PDCCH DCI comprising two levels of DCI is introduced with reference to FIG. 6 .
  • the DCI of the second-level scheduling can be introduced into the form of the first-level DCI.
  • the first-level DCI can carry the public information of packet scheduling
  • the first-level DCI may carry the scheduling information of the second-level scheduling DCI; the second-level DCI may schedule multiple grants.
  • the secondary DCI is scheduled by the primary DCI.
  • the first-level DCI can also carry some public information of some UEs in the UE group; the second-level DCI can indicate independent information different from the public information for each UE.
  • the UE will report to the network whether it has the capability of group scheduling:
  • the UE reports to the network through the existing UE capability information.
  • an embodiment of the present disclosure provides an apparatus for processing group scheduling instructions, and the apparatus includes:
  • the sending module 110 is configured to send a group scheduling instruction for a user equipment UE group, where the UE group includes one or more UEs.
  • the sending module 110 may include a program module; after the program module is executed by the processor, the group scheduling instruction for the UE group can be sent.
  • the sending module 110 may be a combination of hardware and software; the combination of hardware and software includes, but is not limited to: various programmable arrays; the programmable arrays include, but is not limited to: field programmable arrays and /or complex programmable arrays.
  • the sending module 110 may also include but not limited to: a pure hardware module; the pure hardware module includes but not limited to an application specific integrated circuit.
  • the UE group includes one or more of the following UEs:
  • Multimodal output UE
  • the group scheduling instruction is: downlink control information DCI of a group type physical downlink control channel PDCCH; wherein, the group type PDCCH DCI is: the UE group targeted for transmission through the physical downlink control channel PDCCH The downlink control information DCI.
  • the UE group has a group radio network temporary identifier RNTI, wherein the group RNTI is at least used for scrambling the group type PDCCH DCI.
  • the set of RNTIs includes at least one of the following:
  • the downlink group RNTI is used for scrambling the downlink transmission of the UE group
  • the uplink group RNTI is used for scrambling the uplink transmission of the UE group
  • the uplink and downlink common group RNTI can be used for scrambling the uplink transmission and downlink transmission of the group.
  • the group type PDCCH DCI includes one of the following:
  • the first type of DCI wherein the first type of DCI has different independent authorization information for a single UE in the UE group;
  • the second type of DCI wherein the first type of DCI is for public grant information of all UEs in the UE group; wherein the public grant information is used for resource scheduling of UEs in the UE group;
  • the third type of DCI wherein the third type of DCI is for public information of at least some UEs in the UE group and for independent information of a single UE in the UE group.
  • the first type of DCI includes authorization blocks; wherein different authorization blocks have corresponding relationships with different UEs in the UE group.
  • the public grant information included in the second type DCI is used to determine resource scheduling for a single UE according to grant rules
  • the authorization rules include:
  • the authorization rule is used to determine the resource allocation of UEs in the UE group.
  • the third type of DCI includes:
  • Level 1 DCI and at least one Level 2 DCI are Level 1 DCI and at least one Level 2 DCI;
  • the primary DCI indicates the common information
  • the secondary DCI indicates the independent information
  • the device also includes:
  • the receiving module is configured to receive the capability information reported by the UE, wherein the capability information indicates the type of scheduling instruction supported by the corresponding UE.
  • the capability information indicates at least one of the following:
  • the UE supports the type of the decoded scheduling instruction, and the type of the scheduling instruction includes: a group scheduling instruction for a group of UEs and/or an individual scheduling instruction for a single UE.
  • an embodiment of the present disclosure provides an apparatus for processing group scheduling instructions, and the apparatus includes:
  • the receiving module 210 is configured to receive a group scheduling instruction for a user equipment UE group, where the UE group includes one or more UEs.
  • the receiving module 210 may be a program module; after the program module is executed by the processor, it can realize the reception of the group scheduling instruction.
  • the receiving module 210 may be a combination of hardware and software; the combination of hardware and software includes, but is not limited to: various programmable arrays.
  • the programmable array includes: a field programmable array and/or a complex programmable array.
  • the receiving module 210 includes but is not limited to
  • the UE group has a group RNTI; the apparatus further includes:
  • a descrambling module configured to descramble the set of scheduling instructions based on the set of RNTIs.
  • the set of RNTIs includes at least one of the following:
  • the downlink group RNTI is used for scrambling the downlink transmission of the UE group
  • the uplink group RNTI is used for scrambling the uplink transmission of the UE group
  • the uplink and downlink common group RNTI can be used for scrambling the uplink transmission and downlink transmission of the group.
  • the group scheduling instruction includes: group type PDCCH DCI.
  • the first type of DCI wherein the first type of DCI has different independent authorization information for a single UE in the UE group;
  • the second type of DCI wherein the first type of DCI is directed to public authorization information of all UEs in the UE group;
  • the third type of DCI wherein the third type of DCI is for public information of at least some UEs in the UE group and for independent information of a single UE in the UE group.
  • the first type of DCI includes authorization blocks; wherein different authorization blocks have corresponding relationships with different UEs in the UE group.
  • the public authorization information included in the second type DCI includes:
  • the authorization rule is used to determine the resource allocation of UEs in the UE group.
  • the third type of DCI includes:
  • Level 1 DCI and at least one Level 2 DCI are Level 1 DCI and at least one Level 2 DCI;
  • the primary DCI indicates the common information; the secondary DCI indicates the independent information; and/or, the primary DCI is also used to schedule the secondary DCI.
  • An embodiment of the present disclosure provides a communication device, including:
  • memory for storing processor-executable instructions
  • the processor is configured to execute the terminal control method and/or the information processing method provided by any of the foregoing technical solutions.
  • the processor may include various types of storage media, which are non-transitory computer storage media, and can continue to memorize and store information thereon after the communication device is powered off.
  • the communication device includes: an access device or a UE or a core network device.
  • the processor may be connected to the memory through a bus or the like, for reading the executable program stored on the memory, for example, at least one of the methods shown in FIG. 2 , FIG. 6 to FIG. 9 .
  • Fig. 12 is a block diagram of a UE 800 according to an exemplary embodiment.
  • UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.
  • UE 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and communication component 816 .
  • Processing component 802 generally controls the overall operations of UE 800, such as those associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method.
  • processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802 .
  • the memory 804 is configured to store various types of data to support operations at the UE 800 . Examples of such data include instructions for any application or method operating on UE800, contact data, phonebook data, messages, pictures, videos, etc.
  • the memory 804 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Disk
  • the power supply component 806 provides power to various components of the UE 800 .
  • Power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for UE 800 .
  • the multimedia component 808 includes a screen providing an output interface between the UE 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action.
  • the multimedia component 808 includes a front camera and/or a rear camera. When the UE800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.
  • the audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC), which is configured to receive an external audio signal when the UE 800 is in an operation mode, such as a call mode, a recording mode, and a voice recognition mode. Received audio signals may be further stored in memory 804 or sent via communication component 816 .
  • the audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.
  • Sensor component 814 includes one or more sensors for providing various aspects of status assessment for UE 800 .
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and the keypad of the UE800, the sensor component 814 can also detect the position change of the UE800 or a component of the UE800, and the user and Presence or absence of UE800 contact, UE800 orientation or acceleration/deceleration and temperature change of UE800.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communications between UE 800 and other devices.
  • the UE800 can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • NFC near field communication
  • the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID Radio Frequency Identification
  • IrDA Infrared Data Association
  • UWB Ultra Wide Band
  • Bluetooth Bluetooth
  • UE 800 may be powered by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gates Arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic implementations for performing the methods described above.
  • ASICs Application Specific Integrated Circuits
  • DSPs Digital Signal Processors
  • DSPDs Digital Signal Processing Devices
  • PLDs Programmable Logic Devices
  • FPGAs Field Programmable Gates Arrays
  • controllers microcontrollers, microprocessors or other electronic implementations for performing the methods described above.
  • non-transitory computer-readable storage medium including instructions, such as the memory 804 including instructions, which can be executed by the processor 820 of the UE 800 to complete the above method.
  • the non-transitory computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an embodiment of the present disclosure shows a structure of an access device.
  • the communication device 900 may be provided as a network side device.
  • the communication device may be the aforementioned access device and/or core network device.
  • the communication device 900 includes a processing component 922 , which further includes one or more processors, and a memory resource represented by a memory 932 for storing instructions executable by the processing component 922 , such as application programs.
  • the application program stored in memory 932 may include one or more modules each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions, so as to execute any of the aforementioned methods applied to the access device, for example, the methods shown in FIG. 2 , FIG. 6 to FIG. 9 .
  • the communication device 900 may also include a power supply component 926 configured to perform power management of the communication device 900, a wired or wireless network interface 950 configured to connect the communication device 900 to a network, and an input output (I/O) interface 958 .
  • the communication device 900 can operate based on an operating system stored in the memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供一种组调度指令处理方法及装置、通信设备及存储介质。本公开实施例提供一种组调度指令处理方法，由网络设备执行，所述方法包括：发送针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。

Description

组调度指令处理方法及装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种组调度指令处理方法及装置、通信设备及存储介质。
背景技术
多模态(Modality)中涉及到多种信息的来源或者形式，例如，人有触觉，听觉，视觉，嗅觉；信息的媒介，有语音、视频、文字等。为从多个维度感知到用户的输入，用于多模态信息采集的应用程序(Application，App)和/或装置的类型和数量众多，包括多个摄像头、音箱、传感器、键盘、指纹采集器等等。这些采集多个模态信息的装置可以在同一台设备，也可以跨设备使用。在服务器端需要进行多模态数据集的数据融合(Data Fusion)也称为信息融合(Information Fusion)，即将多个传感器或者信息源所提供的关于某一环境特征的不完整信息加以综合和数据分析处理，以形成相对完整、一致的感知描述，从而实现更加准确的识别和判断功能。在服务器完成数据融合，做出决策之后，得到多模态输出，这个过程是一个服务的分发的过程。往往服务也不是分发到单个设备，而很可能是相关的若干个设备的联动。比如通过声纹和视频判决主人回来，可以同时触发窗帘拉上以及空调开启。这里也涉及到多个输出设备之间需要进行成组协同的问题。
发明内容
本公开实施例提供一种组调度指令处理方法及装置、通信设备及存储介质。
本公开实施例第一方面提供一种组调度指令处理方法，由网络设备执行，所述方法包括：
发送针对用户设备(User Equipment，UE)组的组调度指令，其中，所述UE组包括一个或多个UE。
本公开实施例第二方面提供一种组调度指令处理方法，其中，由UE执行，所述方法包括：
接收针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
本公开实施例第三方面提供一种组调度指令处理装置，由网络设备执行，所述装置包括：
发送模块，被配置为发送针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
本公开实施例第四方面提供一种组调度指令处理装置，其中，由UE执行，所述装置包括：
接收模块，被配置为接收针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
本公开实施例第五方面提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如前述第一方面或第二方面提供组调度指令处理方法。
本公开实施例第六方面提供一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现前述的第一方面或第二方面提供的组调度指令处理方法。
本公开实施例提供的技术方案，网络侧可以下发组调度指令，从而实现对整个UE组的调度，具有调度信令开销小及效率高的特点。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开实施例。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信***的结构示意图；
图2是根据一示例性实施例示出的一种组调度指令处理方法的流程示意图；
图3是根据一示例性实施例示出的一种第一类型DCI的示意图；
图4是根据一示例性实施例示出的一种第二类型DCI的示意图；
图5是根据一示例性实施例示出的一种第三类型DCI的示意图；
图6是根据一示例性实施例示出的一种第三类型DCI的示意图；
图7是根据一示例性实施例示出的一种组调度指令处理方法的流程示意图；
图8是根据一示例性实施例示出的一种组调度指令处理方法的流程示意图；
图9是根据一示例性实施例示出的一种组调度指令处理方法的流程示意图；
图10是根据一示例性实施例示出的一种组调度指令处理装置的结构示意图；
图11是根据一示例性实施例示出的一种组调度指令处理装置的结构示意图；
图12是根据一示例性实施例示出的一种UE的结构示意图；
图13是根据一示例性实施例示出的一种通信设备的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。 在本公开实施例和所附权利要求书中所使用的单数形式的“一种”、“”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信***的结构示意图。如图1所示，无线通信***是基于蜂窝移动通信技术的通信***，该无线通信***可以包括：若干个UE11以及若干个接入设备12。
其中，UE11可以是指向用户提供语音和/或数据连通性的设备。UE11可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，UE11可以是物联网UE，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网UE的计算机，例如，可以是固定式、便携式、袖珍式、手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程UE(remote terminal)、接入UE(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户UE(user equipment，UE)。或者，UE11也可以是无人飞行器的设备。或者，UE11也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，UE11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
接入设备12可以是无线通信***中的网络侧设备。其中，该无线通信***可以是***移动通信技术(the 4th generation mobile communication，4G)***，又称长期演进(Long Term Evolution，LTE)***；或者，该无线通信***也可以是5G***，又称新空口(new radio，NR)***或5G NR***。或者，该无线通信***也可以是5G***的再下一代***。其中，5G***中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC***。
其中，接入设备12可以是4G***中采用的演进型接入设备(eNB)。或者，接入设备12也可以是5G***中采用集中分布式架构的接入设备(gNB)。当接入设备12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对接入设备12的具体实现方式不加以限定。
接入设备12和UE11之间可以通过无线空口建立无线连接。在不同的实施方式中，该无线空口是基于***移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信 网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，UE11之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
在一些实施例中，上述无线通信***还可以包含网络管理设备13。
若干个接入设备12分别与网络管理设备13相连。其中，网络管理设备13可以是无线通信***中的核心网设备，比如，该网络管理设备13可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备13的实现形态，本公开实施例不做限定。
如图2所示、本公开实施例提供一种组调度指令处理方法，由网络设备执行，所述方法包括：
S110：发送针对UE组的组调度指令，其中，所述UE组包括一个或多个UE。
该网络设备包括但不限于基站等接入设备。
示例性地，网络设备会针对UE组下发组调度指令，该组调度指令是针对一个UE组的。这种新引入的组调度指令，可以针对以特定UE组进行调度，具有调度灵活性高的特点。
在本公开实施例中，UE组内的多个UE在业务上具有关联性或者相似性的UE；或者，UE组内UE具有频繁的数据交互。如此针对UE组内的UE可以通过组调度指令联合调度，一方面可以实现调度的同步性等调度优化；另一方面采用组调度指令，UE组内的UE在被授权的情况下，还可以在知晓其他UE的被调度情况。
示例性地，所述UE组包括一个或多个如下UE：
多模态输出UE；
联邦学习UE。
例如，在一些情况下，图像设备输出图像，音频设备输出音频，摄像头设备采集图像。这些设备的业务是具有关联性，这些设备都连接到网络，都是网络的UE；这些设备就可以被称之为多模态输出UE，可以组到一个UE组内。
在一些实施例中，联邦学习UE可以用于对机器学习模型的联邦训练的多个UE。联邦学习UE所在的UE组可以称之为联邦学习UE组，联邦学习UE组内的多个UE可能存在大量的数据交互，此时，通过组调度指令对联邦学习UE组内的UE进行资源调度，可以需要通信的UE基于一个调度指令就可能很好的通信。
在一些实施例中，所述组调度指令为：组类型物理下行控制信道PDCCH的下行控制信息DCI；其中，所述组类型PDCCH DCI为：通过物理下行控制信道PDCCH传输的针对的所述UE组的下行 控制信息DCI。
在本公开实施例中，上述组调度指令可为物理层的调度指令。物理层的DCI具有调度动态性高及延时小的特点。
在一些实施例中，所述UE组具有组无线网络临时标识(Radio Network Tempory Identity，RNTI)，其中，所述组RNTI，至少用于加扰所述组类型PDCCH DCI。
在本公开实施例中针对UE组配置有组RNTI，该组RNTI是针对整个UE组的，该UE组内的所有UE都是知晓的。
此处的组RNTI是不同于单个UE的RNTI。若一个UE位于一个UE组内，可以同时具有组RNTI，还可以具有自身与网络设备通信的RNTI。
在一些实施例中，所述组RNTI包括以下至少之一：
下行组RNTI，用于所述UE组的下行传输的加扰；
上行组RNTI，用于所述UE组的上行传输的加扰；
上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
例如，针对多模态输出UE组，由于多模态输出UE组内的UE更多的是输出，输出时更多的是从网络侧接收数据，因此针对这种UE组可以单独设置下行组RNTI，该下行组RNTI可以用于网络侧给这些UE的下行传输的加扰。
这种下行组RNTI可以专用于下行传输的加扰。
此处的下行传输包括但不限于下行指令和/或下行数据。该下行指令包括但不限于下行调度指令。此处的下行调度指令可以包括但不限于前述的组调度指令。
有的UE组可能同步上传，例如，多个摄像设备采集在同一个采集场景下采集的不同视频，这些视频可以拼接成立体视频，或者用于同步直播等。这种摄像设备组成的UE，可能是有大量数据需要同步或者关联传输的。针对这种UE形成的UE组，更多的上行资源的请求和业务数据的上传。故可以设置用于这种UE组上行传输的上行组RNTI。这种上行组RNTI可以专用于下行传输的RNTI。
针对有些UE组可能有上行传输也有下行传输，针对这种UE组可以同时配置上行组RNTI和下行组RNTI。当然在另一个实施例中，针对这种UE组配置的组RNTI可以一个既可以用于下行传输加扰，也可以用于上行传输加扰的上行行通用组RNTI。
在一些实施例中，所述组类型PDCCH DCI包括以下之一：
第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；其中，所述公共授权信息用于所述UE组内UE的资源调度；
第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
第一类型DCI可以包括一个或多个授权块，一个或多个授权可以由一个或多个比特组成。不同的授权块可以对应不同的比特。
示例性地，图3为第一类型DCI的一种结构图。如图3所示，授权块1可以用于UE组内的UE1，授权块2可以用于UE组内UE2,而授权块3可以用于UE组内的UE3。
第一类型DCI对于同一个UE组内的不同UE，可以采用不同的授权块分别调度。
该授权块可以用于UE的资源调度和/或传输参数配置。该传输参数包括但不限于调制与编码策略(Modulation and Coding Scheme，MCS)的配置。
在一些实施例中，一个UE组内的UE具有组编号等。如此，在使用第一类型DCI进行该UE组的调度时，可以根据授权块在第一类型DCI中排序编号与组编号之间的对应关系，供UE确定出哪一个授权块是对自身的调度。有鉴于此，第一类型DCI中的第n个授权块，能够用于UE组内组编号为n的UE的调度。采用这种对应关系，具有第一类型DCI的比特开销小，UE解码简单的特点。
在另一个实施例中，第一类型DCI可以整个用组RNTI加扰，而对不同的授权块可以用单个UE自身的RNTI加扰，如此，UE接收到第一类型DCI时，可以先用组RNTI解扰，然后用自身的RNTI进行解扰，解扰成功的授权块就是对自身的调度，如此第一类型DCI的授权块的排序可以灵活设置。
如图3，第一类型DCI的实施场景中，为了进一步节约信令开销；各个授权(grant)块中公共的部分参数可以共用一个公共部分(common part)。例如，一个UE组内的UE的地理距离比较近，信道状态差别不大时，有公共的MCS等级可以共用，以节约信令开销。
在一个实施例中，第一类型DCI由于为不同的UE配置了不同的授权块，因此可以以最大灵活度进行UE的调度。
所述第二类型DCI携带的公共授权信息，这种公共授权信息是针对整个UE调度的，例如，公共授权信息调度的是整个UE组可使用的资源池。而UE组内哪个UE使用哪一块资源，可以根据UE组内UE之间进行资源分配相关授权规则相关。
示例性地，第二类型DCI调度了一段资源，UE接收到该第二类型DCI之后，知晓了整个UE组所对应的资源池，然后根据资源平分策略及自身在UE组内的组编号，先将资源平分为等于UE组内UE个数的份数，然后根据自身的组编号M，选择第M份资源作为自身被调度的资源。当然此处仅仅是举例，具体实现不限于此举例。
图4所示为一种第二类型DCI的示意图。
在一些实施例中，所述第二类型DCI包括的公共授权信息，用于根据授权规则确定针对单个UE的资源调度。
UE和网络设备之间确定授权规则的方式有很多种，以下提供几种可选方式：
所述授权规则包括：
预先协商的授权规则；
或者，
协议约定的授权规则；
其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
例如，网络设备和UE组内任何一个UE或者UE组内的主UE协商出所述授权规则，并最终将 授权规则通知到各个UE，如此在后续调度时，可以直接根据预先协商的授权规则进行资源分配即可。
再例如，该授权规则可以为协议约定的，该协议可以为通信标准协议或者多个厂商之间共同遵守的私有协议。总之，在一些实施例中，该授权规则可以写入到协议中。
若授权规则写入到协议中，则网络设备和UE都会预先写入，从而UE和网络设备之间可以不用交互信息就可以知晓。
当然协议约定的授权规则可能有多套，规则的具体内容协议限定的，但是具体使用协议限定的那个授权规则，在网络设备进行资源调度之前，可以和UE之间协商。示例性地，基站直接将对应的授权规则的标识下发给UE，UE接收到之后就可以知晓网络设备指示的用于UE之间资源分配的授权规则。
第二类型DCI携带的公共授权信息，采用这种方式可以最大限度的节省DCI的比特开销。
在一些实施例中，所述组类型DCI还可以包括不同于前述第一类型DCI和/或第二类型DCI的第三类型DCI。示例性地，第三类型DCI一定程度上可以理解为第一类型DCI和第二类型DCI的混合体。
例如，第三类型DCI可包括公共部分和独立部分，公共部分可以用于携带公共信息，而独立部分可以用于针对单个UE的独立信息。
图5所示为一种第三类型DCI的示意图。在图5中展示有公共信息和两个独立信息，分别是独立信息1、独立信息2；此处的独立信息1和独立信息2可针对UE组内的不同UE。
在一些实施例中，为了至少确保公共部分的传输成功，可以将携带公共信息的公共部分设置在第三类型DCI所包含比特的中间部分，而将独立信息设置在第三类型DCI所包含比特的边缘部分。
公共信息可以是针对UE组内至少两个UE的信息；而独立信息可以是针对UE组内单个UE的信息。
在一个实施例中，公共信息可以是针对整个UE组内所有UE的信息。
在另一个实施例中，公共信息可以是UE组内部分UE的信息。例如，假设UE组内所有UE采用相同MCS，则此时MCS的指示可以由公共信息来实现。再例如，UE组内不同UE的资源不同，则独立信息指示的各个UE的不同资源。
又示例性地，为UE组内所有的UE调度的频域资源相同，但是时域资源不同，则从比特开销考虑，可以将频域资源的资源标识携带在公共信息内，而将不同UE的时域位置的指示信息携带在独立信息内。
总之，在本公开实施例中，第三类型DCI同时具有携带公共信息的部分和携带独立信息的部分，一方面可以通过公共信息对应的部分减少比特开销，同时可以通过独立信息的部分实现灵活调度，在比特开销和灵活调度之间很好的取得了平衡。
在一个实施例中，所述第三类型DCI包括：
一级DCI和至少一个二级DCI。
此时，一级DCI和二级DCI之间的关联关系可包括：
所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息；
和/或，一级DCI为二级DCI的调度DCI，即一级DCI，还用于调度二级DCI。
若一级DCI用于调度二级DCI，可以根据当前是否有针对UE组内UE的独立信息，确定是否需要调度二级DCI，若有针对UE组内某一个UE的独立信息，则二级DCI来携带，则此时一级DCI将调度二级DCI，UE组内的UE接收到一级DCI之后，根据一级DCI携带的二级DCI的调度信息，在对应的资源上接收二级DCI。若当前没有针对UE组内单个UE的独立信息，则仅仅使用第三类DCI中的一级DCI实现对UE组的调度。
在一个实施例中，所述一级DCI包含的比特数可为固定个数，在一级DCI内有部分比特是用于调度二级DCI的。
在另一个实施例中，二级DCI的比特数目为可变的，二级DCI具体包含的比特数可以根据独立信息的比特开销来确定，或者待接收独立信息的UE的个数来确定。通常独立信息的比特开销越大，则二级DCI包含的比特就越多，和/或待接收独立信息的UE的个数越多，则二级DCI携带的授权块的个数就越多，则对应的二级DCI的比特数也越多。
当然以上仅仅是对一级DCI和二级DCI的举例描述，具体实现不局限于上述举例。
即，在一些实施例中第三类型DCI在DCI的设置格式上，具有一级DCI和二级DCI，但是具体应用时第三类型DCI是否下发二级DCI，需要根据当前是否有针对UE组内某一个UE的独立信息来确定。如图6所示，第三类型DCI可以分为两级。
若一级DCI和二级DCI之间不存在调度关系或者存在调度关系但是一级DCI和二级DCI在连续的通信资源上同时发送，则不同级的DCI可以设置明显的分界符等。例如，一级DCI和二级DCI之间具有分割符，该分隔符可以由预设序列组成。
当然在一些实施例中，一级DCI和二级DCI可以用不同的加扰序列进行加扰，因此UE接收到之后根据加扰序列的不同，可以知晓哪个是一级DCI，哪个是二级DCI。示例性地，一级DCI可以采用组RNTI加扰，而二级DCI则采用被调度UE自身的RNTI加扰。又示例性地，一个UE组可以具有多个组RNTI，此时，一级DCI和二级DCI可以用不同的组RNTI加扰，这种情况下，则无需设置分割符，UE接收到第三类型DCI也能够分割出一级DCI和二级DCI。
当然在一些情况下，一级DCI的位置和/或长度可以是相对固定，如此，UE在接收到第三类型DCI之后根据一级DCI的位置和/或长度的配置，可以先确定出一级DCI，其他备份就均可以认为是二级DCI。
图6为一种同时包含一级DCI和二级DCI的组类型PDCCH DCI。
在二级DCI内可以包含不同的授权块，不同的授权块可是针对UE组内的不同UE。
以上是第三类型DCI的描述，具体实现是不局限于上述描述。
如图7所示，本公开实施例提供了一种方法，该方法可包括：
S210：接收UE上报的能力信息，其中，所述能力信息指示对应UE支持的调度指令的类型。
该能力信息的接收的步骤S210可以单独执行，也可以与前述的步骤S110等组合执行。
若S210与S110组合执行，则可以先执行S210，以便根据接收的能力信息确定出对应UE组内的所有UE是否支持组调度指令，则可以确定针对该UE组发送组调度指令。
若确定出UE组内有UE不支持组调度指令，则可以确定不向该UE组发送组调度指令。当然若UE组内的大部分UE都支持组调度指令时，针对该UE组的大部分依然可以使用组调度指令，针对个别的不支持组调度指令的UE则可以单独调度，依然可以减少信令开销和调度次数的目的。
此处的调度指令的类型包括以下至少之一：
针对UE组的组调度指令；
针对单个UE的调度指令；
针对小区内所有UE的调度指令。
针对小区内所有UE的调度指令一般可为广播指令。
在一个实施例中，所述能力信息，可用于指示UE是否支持所述组调度指令。
若UE支持组调度指令，则UE至少能够接收并解码对应的组调度指令。
在一个实施例中，一个UE组内的所有UE都是对等，即UE组内所有UE没有管理或者被管理，代表或者被代表等情况。
在还有一些情况下，若UE组内设置有两类型UE，可分别是第一类UE和第二类UE；例如，第一类UE可为管理UE，第二类UE可为普通UE；管理UE可以管理或者代表第二类UE与网络侧进行关于UE组通信相关信息的传输和收发。当然此处仅仅是举例说明。
如此，网络侧收到UE上报的能力信息，可以确定对应的UE是否支持组调度指令，或者，支持哪些种类的调度指令。
在一些实施例中，所述能力信息，指示以下至少之一：
所述UE是否支持解码所述组调度指令；
所述UE支持解码的调度指令的类型，所述调度指令的类型包括：针对UE组的组调度指令和/或针对单个UE的单独调度指令。
如图8所示，本公开实施例提供一种组调度指令处理方法，其中，由UE执行，所述方法包括：
S310：接收针对UE组的组调度指令，其中，所述UE组包括一个或多个UE。
该UE可以各种类型的UE，示例性地，该UE可为手机、平板电脑、智能手表或者智能眼镜等可穿戴式设备、车载设备、智能家居设备或者智能办公设备等。
以上仅仅是对UE的举例。
在本公开实施例中，该UE可为加入了UE组的终端设备。
该UE会接收针对UE组的组调度指令。在本公开实施例中，针对UE组的组调度指令可包括：面向UE组内多个UE的调度指令。
在本公开实施例中，该调度指令为组调度指令，具有信令开销小及调度效率高的特点。
在一些实施例中，所述UE组具有组RNTI；所述方法还包括：
基于所述组RNTI解扰所述组调度指令。
此处的组RNTI可为网络侧预先分配给UE组的RNTI。示例性地，在网络侧建立UE组时分配的RNTI或者在UE组建立之后针对UE组的RNTI，该RNTI是针对UE组的RNTI，因此称之为组RNTI。该组RNTI可以是通过RRC信令等RRC层消息下发的。当然此处仅仅对下发组RNTI的消息进行举例说明，具体实现不限于此，例如，组RNTI还可以基于基站侧下发的MAC CE接收。
在一个实施例中，所述组RNTI包括以下至少之一：
下行组RNTI，用于所述UE组的下行传输的加扰；
上行组RNTI，用于所述UE组的上行传输的加扰；
上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
在本公开实施例中，一个UE组可以具有一个或多个组RNTI。根据组RNTI的功能可以分为：
下行组RNTI，可以加扰下行传输；
上行组RNTI，可以加扰上行传输；
上下行组RNTI，就可以用于上行传输的加扰，也可以用于下行传输的加扰。
UE组内的UE在使用组RNTI加扰和/或解扰时，可根据待加扰或待加扰的传输方向，使用对应的组RNTI加解扰。此处的传输方向至少可以分为：UE向网络侧的上行传输方向，和/或网络侧向UE的下行传输方向。
在一些实施例中，所述组调度指令包括：组类型PDCCH DCI。
在本公开实施例中，所述组调度指令是一种PDCCH传输的DCI。且这种组调度指令是针对UE组的，因此该PDCCH DCI称之为组类型PDCCH DCI。DCI具有动态性高及延时性小的特点。
在一些实施例中，所述组类型PDCCH DCI包括以下至少之一：
第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；
第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
此处的三类型DCI的具体描述可以参见前述实施例的对应位置，此处就不再重复了。
在一些实施例中，所述第一类型DCI包括授权块；其中，不同的授权块与所述UE组内不同UE具有对应关系。
不同的授权块与UE组内不同UE具有对应关系，从而实现单UE的分授权块的独立调度。
第二类型DCI直接携带的公共授权信息，该公共授权信息包括但不限于以下至少之一：
针对UE组的资源调度信息；
在UE组内不同UE之间进行资源分配的授权规则的指示信息。
当然以上仅是第第二类型DCI携带的公共授权信息的举例说明，具体实现时不局限于此。
在一些实施例中，所述第二类型DCI包括的公共授权信息包括：
预先协商的授权规则；
或者，
协议约定的授权规则；
其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
在本公开实施例中，该授权规则可以协议约定的，也可以是UE组和网络侧设备事先协商的，此处的事先协商可以是发生在UE组建立的时候，也可以是在UE组建立之后。
在一些实施例中，所述第三类型DCI包括的公共信息，用于指示所述UE组内至少部分UE共用的参数；所述第三类型DCI包含的独立授权信息，用于指示所述UE组内的差异授权参数。
在一些实施例中，所述共用的参数包括：调制与编码策略MCS；和/或，所述差异授权参数包括：针对所述UE内不同UE的资源调度参数。
在另一些实施例中，所述公共信息可为UE组的资源调度的公共信息，该公共信息指示UE组内各UE被调度的资源所使用的频域资源和/或时域资源，而差异授权参数可以指示不同UE在使用相同频域资源时使用的不同时域资源，或者，指示不同UE在使用相同时域资源时的不同频域资源。
在一些实施例中，所述第三类型DCI包括：一级DCI和至少一个二级DCI；其中，所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息。
示例性地，一级DCI可以直接携带公共信息，二级DCI也可以直接携带独立信息。在另一些实施例中，一级DCI和二级DCI都可以通过自身携带的信息与对应公共信息和独立信息之间的对应关系，实现公共信息和独立信息的指示。
如图9所示，本公开实施例还提供一种方法，该方法可由UE执行，包括：
S410：向基站上报能力信息，该能力信息至少指示UE支持的调度指令的类型。该能力信息，可至少指示UE是否支持组调度指令，例如，UE支持组调度指令则表明UE可以接收组调度指令。
此处的该组调度指令可为前述实施例提到的组调度指令。本公开实施例中，为网络中新增加的需要进行成组同步的应用场景，增加调度协同处理。
作为一种实施例：需要成组同步的用户为多模态输出UE。
作为一种实施例：需要成组同步的UE可为联邦学习UE。
在一个实施例中，网络可以按照如下方案，对UE进行调度分组，得到UE分组；
作为一种实施例：对UE进行调度分组可以是按照业务进行分组，得到UE分组；
作为一种实施例：对UE进行调度分组可以是按照地理位置进行分组，得到UE分组。
示例性地，基站从核心网获取到UE的分组信息，对UE进行对UE进行调度分组，得到UE分组；
其中，核心网可以直接携带UE所属的UE组的组标识(group ID)。
示例性地，基站从核心网获取到需要对多个UE进行协同调度的信息，从而将UE划分到一个UE组；比如核心网向基站指示了多个UE的数据流之间到达时间的最小限制的服务质量(Quality of Service，QoS)需求，为满足该QoS需求，基站需要对该部分UE进行以UE组为粒度的协同调度或同步调度。
在一个实施例中，网络将提供的组调度指令，即组(Group)类型的PDCCH DCI，对该UE组 用户进行成组调度，具体地：
引入用于组调度的组(Group)RNTI；该组RNTI是网络事先通过公共信令或者专用信令通知UE。
示例性地：用于组调度的组RNTI可以用于上行和/或者下行方向的调度；
在一种实施例中，网络设备可以同时下发上行方向的组RNTI1和下行方向的组RNTI2；
在一种实施例中网络设备可以仅下发上行方向的组RNTI1；
在一种实施例中网络设备可以仅下发下行方向的组RNTI2。
针对组调度指令，引入用于组调度的Group PDCCH DCI，其中组RNTI将用于加扰组类型PDCCH DCI(group PDCCH DCI)其中，Group PDCCH DCI的格式可能如下：
第一种方式：参考图3所示，DCI中携带分离的授权信息：
作为一个实施例如下：
情况A：组类型PDCCH DCI中不提取公共信息；
其中，网络可以通知每个UE其授权信息(授权块)在该Group PDCCH DCI中的位置，则UE可以找到对应的自己的授权信息进行解读。
此时每个UE的授权信息可作为一个授权块(block)；
比如：授权块(block1)，授权块(block2)，授权块(block3)各自标识UE1，UE2，UE3的授权；
UE根据各自的授权信息在相应资源上进行接收。
为进一步节约信令开销，可以采用图4至图6所示的DCI。
情况B：提取公共信息；
各个授权块中公共的部分信息可以挪出来放在一个公共部分。例如，成组的UE往往距离比较近，因此信道状态差别不大，比如有公共的MCS等级，则可以共用以节约信令开销。
比如：在授权中，存在一个公共授权块(block0)，标识所有UE授权的部分公共信息，紧跟其后，为授权块(block1)，授权块(block2)，授权块(block3)，各自分别标识UE1，UE2，UE3的独立信息。
第二种方式：DCI中携带公共的一个授权信息，UE之间按照预先定义或者网络通知的规则进行共享使用：例如，参考图4。
其预先设定的规则包括：
UE在组内的索引(index)，比如0、1、2…
资源如何分配：
比如，频域均等资源分为3份，编号为0、1、2的UE分别使用第一份频域资源、第二份频域资源及第三份频域资源。
比如，频域资源分为3份，编号为0、1、2的UE分别使用第一份频域资源、第二份频域资源及第三份频域资源，其使用的起点和终点可以在DCI中告知网络。
第三种方式：以上两种方式组合使用，即DCI中携带公共的一个授权信息供部分UE共享使用，也可以为部分UE携带单独的授权信息。此处的单独的授权信息即为前述实施例中提到的独立信息。此处UE共享使用的信息即为前述公共信息。
比如：在授权中，存在两个部分，其中，第一部分采用方式1方式来指示UE1和UE2的资源授权，而第二部分则采用方式2来指示UE3和UE4的资源授权。
其中，对于第一部分，第一种方式对应的DCI来指示UE1和UE2的授权，又可能存在两种方式：
比如：授权块(block1)，授权块(block2)，各自标识UE1，UE2的资源授权；
或者：公共授权块(block0)，标识UE1和UE2授权的公共部分参数，紧跟其后，为授权块(block1)，授权块(block2)，各自分别标识UE1，UE2，其他授权资源部分；
其中，对于第二部分，第二种方式对应的DCI来指示UE3和UE4的授权，即携带公共的一个授权信息，UE3和UE4之间按照预先定义或者网络通知的规则进行共享使用。
第三种方式对应的DCI可如图5或图6所示。
在一些实施例中，参考图6引入一种包括两级DCI的组类型PDCCH DCI。
一级DCI的形式上可以引入二级调度的DCI。
作为一个实施例：一级DCI可以携带分组调度的公共信息；
作为一个实施例：一级DCI可以携带第二级调度DCI的调度信息；其中第二级别DCI可以对多个授权进行调度。
在一些实施例中，一级DCI和二级DCI存在调度关系，即二级DCI由一级DCI进行调度。同时，一级DCI还可以携带UE组内部分UE的若干公共信息；而二级DCI则可以指明每个UE不同于公共信息的独立信息。
在一些实施例中，UE将上报给网络是否具有组调度的能力：
引入UE能力，即是否支持解码组类型(Group)PDCCH DCI；即是否支持组调度的功能；
引入UE能力，即是否支持同时解码组类型(Group)PDCCH DCI和其他调度PDCCH DCI；
UE通过现有的UE能力信息上报给网络。
如图10所示，本公开实施例提供一种组调度指令处理装置，所述装置包括：
发送模块110，被配置为发送针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
在一些实施例中，发送模块110可包括程序模块；该程序模块被处理器执行之后，能够发送针对UE组的组调度指令。
在另一些实施例中，该发送模块110可为软硬结合模块；所述软硬结合模块包括但不限于：各种可编程阵列；所述可编程阵列包括但不限于：现场可编程阵列和/或复杂可编程阵列。
在还有一些实施例中，该发送模块110还可包括但不限于：纯硬件模块；所述纯硬件模块包括但不限于专用集成电路。
在一些实施例中，所述UE组包括一个或多个如下UE：
多模态输出UE；
联邦学习UE。
在一些实施例中，所述组调度指令为：组类型物理下行控制信道PDCCH的下行控制信息DCI；其中，所述组类型PDCCH DCI为：通过物理下行控制信道PDCCH传输的针对的所述UE组的下行控制信息DCI。
在一些实施例中，所述UE组具有组无线网络临时标识RNTI，其中，所述组RNTI，至少用于加扰所述组类型PDCCH DCI。
在一些实施例中，所述组RNTI包括以下至少之一：
下行组RNTI，用于所述UE组的下行传输的加扰；
上行组RNTI，用于所述UE组的上行传输的加扰；
上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
在一些实施例中，所述组类型PDCCH DCI包括以下之一：
第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；其中，所述公共授权信息用于所述UE组内UE的资源调度；
第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
在一些实施例中，所述第一类型DCI包括授权块；其中，不同的授权块与所述UE组内不同UE具有对应关系。
在一些实施例中，所述第二类型DCI包括的公共授权信息，用于根据授权规则确定针对单个UE的资源调度；
所述授权规则包括：
预先协商的授权规则；
或者，
协议约定的授权规则；
其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
在一些实施例中，所述第三类型DCI包括：
一级DCI和至少一个二级DCI；
其中，所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息。
在一些实施例中，所述装置还包括：
接收模块，被配置为接收UE上报的能力信息，其中，所述能力信息指示对应UE支持的调度指 令的类型。
在一些实施例中，所述能力信息，指示以下至少之一：
所述UE是否支持解码所述组调度指令；
所述UE支持解码的调度指令的类型，所述调度指令的类型包括：针对UE组的组调度指令和/或针对单个UE的单独调度指令。
如图11所示，本公开实施例提供一种组调度指令处理装置，所述装置包括：
接收模块210，被配置为接收针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
在一个实施例中，所述接收模块210可为程序模块；所述程序模块被处理器执行后，能够实现组调度指令的接收。
在另一个实施例中，所述接收模块210可为软硬结合模块；所述软硬结合模块包括但不限于：各种可编程阵列。所述可编程阵列包括：现场可编程阵列和/或复杂可编程阵列。
在还有一个实施例中，所述接收模块210包括但不限于
在一个实施例中，所述UE组具有组RNTI；所述装置还包括：
解扰模块，被配置为基于所述组RNTI解扰所述组调度指令。
在一个实施例中，所述组RNTI包括以下至少之一：
下行组RNTI，用于所述UE组的下行传输的加扰；
上行组RNTI，用于所述UE组的上行传输的加扰；
上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
在一个实施例中，所述组调度指令包括：组类型PDCCH DCI。
在一个实施例中，第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；
第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
在一个实施例中，所述第一类型DCI包括授权块；其中，不同的授权块与所述UE组内不同UE具有对应关系。
在一个实施例中，所述第二类型DCI包括的公共授权信息包括：
预先协商的授权规则；
或者，
协议约定的授权规则；
其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
在一个实施例中，所述第三类型DCI包括：
一级DCI和至少一个二级DCI；
其中，所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息；和/或，所述一级DCI，还用于调度所述二级DCI。
本公开实施例提供一种通信设备，包括：
用于存储处理器可执行指令的存储器；
处理器，分别存储器连接；
其中，处理器被配置为执行前述任意技术方案提供的终端的控制方法和/或信息处理方法。
处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
这里，所述通信设备包括：接入设备或UE或者核心网设备。
所述处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图2、图6至图9所示的方法的至少其中之一。
图12是根据一示例性实施例示出的一种UE800的框图。例如，UE 800可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图12，UE800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制UE800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在UE800的操作。这些数据的示例包括用于在UE800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为UE800的各种组件提供电力。电源组件806可以包括电源管理***，一个或多个电源，及其他与为UE800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述UE800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄 像头。当UE800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜***或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当UE800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和***接口模块之间提供接口，上述***接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为UE800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为UE800的显示器和小键盘，传感器组件814还可以检测UE800或UE800一个组件的位置改变，用户与UE800接触的存在或不存在，UE800方位或加速/减速和UE800的温度变化。传感器组件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于UE800和其他设备之间有线或无线方式的通信。UE800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理***的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，UE800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由UE800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图13所示，本公开一实施例示出一种接入设备的结构。例如，通信设备900可以被提供为一网络侧设备。该通信设备可为前述的接入设备和/或核心网设备。
参照图13，通信设备900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述接入设备的任意方法，例如，如图2、图6至 图9所示方法。
通信设备900还可以包括一个电源组件926被配置为执行通信设备900的电源管理，一个有线或无线网络接口950被配置为将通信设备900连接到网络，和一个输入输出(I/O)接口958。通信设备900可以操作基于存储在存储器932的操作***，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (23)

  1. 一种组调度指令处理方法，由网络设备执行，所述方法包括：
    发送针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
  2. 根据权利要求1所述的方法，其中，所述UE组包括一个或多个如下UE：
    多模态输出UE；
    联邦学习UE。
  3. 根据权利要求1或2所述的方法，其中，所述组调度指令为：组类型物理下行控制信道PDCCH的下行控制信息DCI；其中，所述组类型PDCCH DCI为：通过物理下行控制信道PDCCH传输的针对的所述UE组的下行控制信息DCI。
  4. 根据权利要求3所述的方法，其中，所述UE组具有组无线网络临时标识RNTI，其中，所述组RNTI，至少用于加扰所述组类型PDCCH DCI。
  5. 根据权利要求4所述的方法，其中，所述组RNTI包括以下至少之一：
    下行组RNTI，用于所述UE组的下行传输的加扰；或
    上行组RNTI，用于所述UE组的上行传输的加扰；或
    上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
  6. 根据权利要求3所述的方法，其中，所述组类型PDCCH DCI包括以下之一：
    第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
    第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；其中，所述公共授权信息用于所述UE组内UE的资源调度；
    第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
  7. 根据权利要求6所述的方法，其中，所述第一类型DCI包括授权块；其中，不同的授权块与所述UE组内不同UE具有对应关系。
  8. 根据权利要求6所述的方法，其中，所述第二类型DCI包括的公共授权信息，用于根据授权规则确定针对单个UE的资源调度；
    所述授权规则包括：
    预先协商的授权规则；或
    协议约定的授权规则；
    其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
  9. 根据权利要6所述的方法，其中，所述第三类型DCI包括：
    一级DCI和至少一个二级DCI；
    其中，所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息，和/或，所述一级DCI，还用于调度所述二级DCI。
  10. 根据权利要求1至9任一项所述的方法，其中，所述方法还包括：
    接收UE上报的能力信息，其中，所述能力信息指示对应UE支持的调度指令的类型。
  11. 根据权利要求10所述的方法，其中，所述能力信息，指示以下至少之一：
    所述UE是否支持解码所述组调度指令；或
    所述UE支持解码的调度指令的类型，所述调度指令的类型包括：针对UE组的组调度指令和/或针对单个UE的单独调度指令。
  12. 一种组调度指令处理方法，其中，由UE执行，所述方法包括：
    接收针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
  13. 根据权利要求12所述的方法，其中，所述UE组具有组RNTI；所述方法还包括：
    基于所述组RNTI解扰所述组调度指令。
  14. 根据权利要求12所述的方法，其中，所述组RNTI包括以下至少之一：
    下行组RNTI，用于所述UE组的下行传输的加扰；或
    上行组RNTI，用于所述UE组的上行传输的加扰；或
    上下行通用组RNTI，能够用于所述组的上行传输和下行传输的加扰。
  15. 根据权利要求12至14任一项所述的方法，其中，所述组调度指令包括：组类型PDCCH DCI。
  16. 根据权利要求15所述的方法，其中，
    第一类型DCI，其中，所述第一类型DCI针对所述UE组内单个UE具有不同的独立授权信息；
    第二类型DCI，其中，所述第一类型DCI针对所述UE组内所有UE的公共授权信息；
    第三类型DCI，其中，所述第三类型DCI针对所述UE组内至少部分UE的公共信息和针对所述UE组内单个UE的独立信息。
  17. 根据权利要求16所述的方法，其中，所述第一类型DCI包括授权块；其中，不同的授权块与所述UE组内不同UE具有对应关系。
  18. 根据权利要求16或17所述的方法，其中，所述第二类型DCI包括的公共授权信息包括：
    预先协商的授权规则；或
    协议约定的授权规则；
    其中，所述授权规则，用于确定所述UE组内的UE的资源分配。
  19. 根据权利要16所述的方法，其中，所述第三类型DCI包括：
    一级DCI和至少一个二级DCI；
    其中，所述一级DCI指示所述公共信息；所述二级DCI指示所述独立信息，和/或，所述一级DCI，还用于调度所述二级DCI。
  20. 一种组调度指令处理装置，所述装置包括：
    发送模块，被配置为发送针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
  21. 一种组调度指令处理装置，其中，所述装置包括：
    接收模块，被配置为接收针对用户设备UE组的组调度指令，其中，所述UE组包括一个或多个UE。
  22. 一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至19任一项提供的方法。
  23. 一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如权利要求1至19任一项提供的方法。
PCT/CN2021/105565 2021-07-09 2021-07-09 组调度指令处理方法及装置、通信设备及存储介质 WO2023279389A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202180002110.XA CN115868233B (zh) 2021-07-09 2021-07-09 组调度指令处理方法及装置、通信设备及存储介质
PCT/CN2021/105565 WO2023279389A1 (zh) 2021-07-09 2021-07-09 组调度指令处理方法及装置、通信设备及存储介质
EP21948883.0A EP4366427A1 (en) 2021-07-09 2021-07-09 Group-scheduling instruction processing method and apparatus, communication device, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/105565 WO2023279389A1 (zh) 2021-07-09 2021-07-09 组调度指令处理方法及装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023279389A1 true WO2023279389A1 (zh) 2023-01-12

Family

ID=84800186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/105565 WO2023279389A1 (zh) 2021-07-09 2021-07-09 组调度指令处理方法及装置、通信设备及存储介质

Country Status (3)

Country Link
EP (1) EP4366427A1 (zh)
CN (1) CN115868233B (zh)
WO (1) WO2023279389A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101815255A (zh) * 2010-04-28 2010-08-25 中兴通讯股份有限公司 一种群组调度区域信息的查询方法及***
CN102333381A (zh) * 2011-10-28 2012-01-25 电信科学技术研究院 一种资源调度及数据传输的方法、装置
CN103687034A (zh) * 2012-08-30 2014-03-26 电信科学技术研究院 一种组调度方法及装置
CN104066194A (zh) * 2013-03-19 2014-09-24 电信科学技术研究院 数据传输调度和数据传输方法及设备
CN109479266A (zh) * 2016-11-03 2019-03-15 华为技术有限公司 数据传输方法、网络设备及终端设备
CN111373826A (zh) * 2020-02-19 2020-07-03 北京小米移动软件有限公司 信息处理方法、装置、基站、终端及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101815255A (zh) * 2010-04-28 2010-08-25 中兴通讯股份有限公司 一种群组调度区域信息的查询方法及***
CN102333381A (zh) * 2011-10-28 2012-01-25 电信科学技术研究院 一种资源调度及数据传输的方法、装置
CN103687034A (zh) * 2012-08-30 2014-03-26 电信科学技术研究院 一种组调度方法及装置
CN104066194A (zh) * 2013-03-19 2014-09-24 电信科学技术研究院 数据传输调度和数据传输方法及设备
CN109479266A (zh) * 2016-11-03 2019-03-15 华为技术有限公司 数据传输方法、网络设备及终端设备
CN111373826A (zh) * 2020-02-19 2020-07-03 北京小米移动软件有限公司 信息处理方法、装置、基站、终端及存储介质

Also Published As

Publication number Publication date
CN115868233A (zh) 2023-03-28
EP4366427A1 (en) 2024-05-08
CN115868233B (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
WO2021243618A1 (zh) 一种资源调度的方法、装置、通信设备及存储介质
CN106992953B (zh) ***信息获取方法及装置
WO2021159254A1 (zh) Dci的传输方法、装置、通信设备及存储介质
JP2023532042A (ja) 情報伝送方法、装置、通信機器及び記憶媒体
WO2019100259A1 (zh) 数据传输方法、装置及无人机
WO2021007823A1 (zh) 信息指示、确定方法及装置、通信设备及存储介质
WO2021163930A1 (zh) 信息处理方法、装置、基站、终端及存储介质
WO2021159252A1 (zh) 传输调度方法、装置、通信设备及存储介质
WO2023279389A1 (zh) 组调度指令处理方法及装置、通信设备及存储介质
CN110945827B (zh) 下行控制信息配置方法、装置、通信设备及存储介质
CN110945828B (zh) 解调参考信号处理方法及其装置、通信设备及存储介质
EP4376529A1 (en) Information processing method and apparatus, communication device, and storage medium
WO2022257133A1 (zh) 多终端共享pdu会话的方法、装置、通信设备及存储介质
WO2023197188A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2024026757A1 (zh) 多流同步门限处理方法以及装置、通信设备及存储介质
US20230276500A1 (en) Method for random access, communication device, and storage medium
WO2023283809A1 (zh) 接入控制处理方法、装置、通信设备及存储介质
WO2023197274A1 (zh) 资源配置的方法、装置、通信设备及存储介质
WO2023151055A1 (zh) 发送配置信息的方法、装置、通信设备及存储介质
WO2023155111A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023279370A1 (zh) 接纳控制方法、装置、通信设备及存储介质
CN117859395A (zh) 逻辑信道的调度方法、装置、通信设备及存储介质
CN117322020A (zh) 一种***消息传输方法、装置、通信设备及存储介质
CN115968564A (zh) 寻呼方法、装置、通信设备及存储介质
CN116530188A (zh) 调度处理方法以及装置、通信设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21948883

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18577726

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2021948883

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021948883

Country of ref document: EP

Effective date: 20240131

NENP Non-entry into the national phase

Ref country code: DE