WO2024065432A1 - 调度方法、装置、设备及可读存储介质 - Google Patents

调度方法、装置、设备及可读存储介质 Download PDF

Info

Publication number
WO2024065432A1
WO2024065432A1 PCT/CN2022/122757 CN2022122757W WO2024065432A1 WO 2024065432 A1 WO2024065432 A1 WO 2024065432A1 CN 2022122757 W CN2022122757 W CN 2022122757W WO 2024065432 A1 WO2024065432 A1 WO 2024065432A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
pdsch
broadcast
scheduling
type
Prior art date
Application number
PCT/CN2022/122757
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 CN202280003815.8A priority Critical patent/CN116097866A/zh
Priority to PCT/CN2022/122757 priority patent/WO2024065432A1/zh
Publication of WO2024065432A1 publication Critical patent/WO2024065432A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • 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/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1273—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of downlink data flows

Definitions

  • the present disclosure relates to the field of communications, and in particular to a scheduling method, apparatus, device, and readable storage medium.
  • the above-mentioned method of reducing complexity can be applied to unicast channel and broadcast channel.
  • broadcast channel such as RAR, paging, etc.
  • the network may schedule the old version of legacy terminals exceeding 5MHz due to payload overhead considerations.
  • legacy terminals and eRedCap terminals coexist, the scheduling process of legacy terminals may be affected by the limitation of eRedCap terminals due to the 5 MHz data channel bandwidth limitation of eRedCap terminals.
  • the embodiments of the present disclosure provide a scheduling method, apparatus, device and readable storage medium, which separately schedule broadcast PDSCHs corresponding to different terminals in a network where different types of terminals coexist, so that when scheduling the broadcast PDSCH corresponding to the first type of terminal, it is possible to avoid affecting the scheduling of other types of terminals as much as possible.
  • the technical solution is as follows:
  • a scheduling method is provided, the method being performed by a network device, the method comprising:
  • a physical downlink shared channel PDSCH is separately scheduled and broadcasted to the first type of terminals.
  • a scheduling method is provided, the method being performed by a first type terminal, the method comprising:
  • a broadcast PDSCH sent by a network device is received, where the broadcast PDSCH is a channel scheduled separately by the network device.
  • a scheduling device which is applied to a network device, and includes:
  • the scheduling module is used to separately schedule broadcasting a physical downlink shared channel PDSCH to the first type of terminal.
  • a scheduling device which is applied to a terminal, and includes:
  • the receiving module is used to receive a broadcast PDSCH sent by a network device, where the broadcast PDSCH is a channel scheduled separately by the network device.
  • a terminal comprising:
  • transceiver coupled to the processor
  • the processor is configured to execute executable instructions to implement the scheduling method as described in the above-mentioned embodiment of the present disclosure.
  • a network device comprising:
  • transceiver coupled to the processor
  • the processor is configured to execute executable instructions to implement the scheduling method as described in the above-mentioned embodiment of the present disclosure.
  • a computer-readable storage medium which stores at least one instruction, at least one program, code set or instruction set, and the at least one instruction, at least one program, code set or instruction set is executed by a processor to implement the scheduling method as described in the above-mentioned embodiment of the present disclosure.
  • the broadcast PDSCH is scheduled separately for the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • FIG1 is an architecture block diagram of a communication system provided by an embodiment of the present disclosure
  • FIG2 is a flow chart of a scheduling method on a network device side provided by an exemplary embodiment of the present disclosure
  • FIG3 is a flowchart of a scheduling method on a network device side provided by another exemplary embodiment of the present disclosure.
  • FIG4 is a flowchart of a scheduling method on a network device side provided by another exemplary embodiment of the present disclosure.
  • FIG5 is a flowchart of a scheduling method on a network device side provided by another exemplary embodiment of the present disclosure.
  • FIG6 is a flowchart of a method for scheduling at a terminal side provided by an exemplary embodiment of the present disclosure
  • FIG. 7 is a flowchart of a method for scheduling interactively between a terminal side and a network device side provided by an exemplary embodiment of the present disclosure
  • FIG8 is a schematic diagram of the structure of a scheduling device shown in an exemplary embodiment of the present disclosure.
  • FIG9 is a schematic structural diagram of a scheduling device according to another exemplary embodiment of the present disclosure.
  • FIG. 10 is a structural block diagram of a communication device according to an exemplary embodiment of the present disclosure.
  • Reduce the baseband processing bandwidth for example: limit the frequency domain width of the Physical Downlink Shared Channel (PDSCH) received by the eRedCap terminal to within 5 MHz.
  • PDSCH Physical Downlink Shared Channel
  • the above-mentioned method of reducing complexity can be applied to unicast channel and broadcast channel.
  • broadcast channel such as RAR, paging, etc.
  • the network may schedule the old version of legacy terminals exceeding 5MHz due to payload overhead considerations.
  • legacy terminals and eRedCap terminals coexist, the scheduling process of legacy terminals may be affected by the limitations of eRedCap terminals due to the bandwidth limitations of eRedCap terminals.
  • FIG1 shows a block diagram of a communication system provided by an illustrative embodiment of the present disclosure.
  • the communication system may include: a core network 11 , an access network 12 , and a terminal 13 .
  • the core network 11 includes several core network devices 110.
  • the core network device 110 is a device deployed in the core network.
  • the function of the core network device is mainly to provide user connection, user management and service bearing, and to provide an interface to the external network as a bearer network.
  • the core network devices in the 5G NR system may include an access and mobility management function (Access and Mobility Management Function, AMF) network element, a user plane function (User Plane Function, UPF) network element and a session management function (Session Management Function, SMF) network element.
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • SMF Session Management Function
  • the core network device 30 in the embodiment of the present application may include a location management function network element.
  • the location management function network element includes a location server (location server), and the location server can be implemented as any of the following: LMF (Location Management Function), E-SMLC (Enhanced Serving Mobile Location Centre), SUPL (Secure User Plane Location), and SUPL SLP (SUPL Location Platform).
  • LMF Location Management Function
  • E-SMLC Enhanced Serving Mobile Location Centre
  • SUPL Secure User Plane Location
  • SUPL SLP SUPL SLP
  • the access network 12 includes several network devices 120.
  • the network device 120 may be a base station, which is a device deployed in the access network to provide wireless communication functions for terminals.
  • the base station may include various forms of macro base stations, micro base stations, relay stations, access points or transmission reception points (TRP), etc.
  • TRP transmission reception points
  • the names of devices with base station functions may be different.
  • LTE Long Term Evolution
  • eNodeB eNodeB
  • gNode B 5G New Radio
  • the name "base station” may change.
  • the above-mentioned devices that provide wireless communication functions for terminals are collectively referred to as network devices.
  • the terminal 13 may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem, as well as various forms of terminals, mobile stations (MS), terminals (terminal devices), etc.
  • the above-mentioned devices are collectively referred to as terminals.
  • the terminal 13 includes ordinary terminals and RedCap terminals, wherein the RedCap terminal has the characteristics of low complexity and power saving compared to ordinary terminals.
  • the network device 120 and the terminal 13 communicate with each other through some air interface technology, such as the Uu interface.
  • the RedCap terminal provided in the embodiment of the present application is a terminal obtained by performing version enhancement on the above-mentioned ordinary terminal, so that the RedCap terminal can better adapt to low-latency and high-speed scenarios.
  • the RedCap terminal can also be referred to as NR-lite (lightweight) terminal.
  • This type of device is similar to the Internet of Things device in LTE and needs to meet the following requirements:
  • wireless communication may be performed through a licensed frequency band or through an unlicensed frequency band.
  • FIG. 2 is a flowchart of a scheduling method provided by an exemplary embodiment of the present disclosure.
  • the method is described by taking the application of the method to a network device as an example. As shown in FIG. 2 , the method includes the following step 210 .
  • Step 210 Schedule and broadcast a physical downlink shared channel PDSCH to terminals of the first type separately.
  • the first type of terminal comprises an enhanced reduced capability eRedCap terminal.
  • the eRedCap terminal is an enhanced reduced capability terminal, that is, the eRedCap terminal is represented as enhanced Reduced Capability UE.
  • enhanced reduced capability is used to indicate the reduction of the terminal capability by enhancement.
  • the eRedCap terminal is a RedCap terminal, and the terminal capability of the eRedCap terminal is reduced compared with the ordinary terminal (legacy terminal).
  • the broadcast PDSCH carries at least one of the following information: a random access response RAR; a paging message.
  • the broadcast PDSCH carries the RAR; or the broadcast PDSCH carries the paging message; or the broadcast PDSCH carries the RAR and the paging message.
  • different terminals have their corresponding broadcast PDSCHs respectively.
  • a first broadcast PDSCH corresponding to a first type of terminal is scheduled separately; and/or a second broadcast PDSCH corresponding to a second type of terminal is scheduled separately.
  • the second type of terminal includes a common legacy terminal.
  • the first type of terminal includes the eRedCap terminal; the second type of terminal includes the legacy terminal is only an illustrative example, and the embodiments of the present application are not limited to this.
  • the following description is given by taking the first type of terminal as an eRedCap terminal and the second type of terminal as a non-eRedCap terminal (such as a legacy terminal) as an example.
  • the eRedCap terminal corresponds to the first broadcast PDSCH; the non-eRedCap terminal corresponds to the second broadcast PDSCH.
  • the first broadcast PDSCH corresponding to the eRedCap terminal is scheduled separately; and/or the second broadcast PDSCH corresponding to the non-eRedCap terminal is scheduled separately.
  • the process of separately scheduling broadcast PDSCHs corresponding to different terminals may be implemented in one of the following forms:
  • the first broadcast PDSCH corresponding to the eRedCap terminal is scheduled separately.
  • the second broadcast PDSCH corresponding to the non-eRedCap terminal is scheduled separately.
  • the first broadcast PDSCH corresponding to the eRedCap terminal is scheduled separately, and the second broadcast PDSCH corresponding to the non-eRedCap terminal is scheduled separately.
  • the broadcast PDSCH carrying different information is scheduled separately.
  • the broadcast PDSCH carrying RAR when the broadcast PDSCH carries RAR, the broadcast PDSCH carrying RAR is scheduled separately; when the broadcast PDSCH carries a paging message, the broadcast PDSCH carrying RAR is scheduled separately.
  • the process of separately scheduling the broadcast PDSCHs corresponding to different terminals can be implemented in one of the following forms:
  • the first broadcast PDSCH corresponding to the eRedCap terminal is Independent dispatch.
  • the network device when the broadcast PDSCH of the eRedCap terminal (ie, the first broadcast PDSCH corresponding to the eRedCap terminal) carries the RAR, the network device separately schedules the first broadcast PDSCH carrying the RAR.
  • the network device separately schedules the first broadcast PDSCH carrying the paging message.
  • the network device separately schedules the first broadcast PDSCH carrying the RAR, and separately schedules the first broadcast PDSCH carrying the paging message.
  • the second broadcast PDSCH corresponding to the non-eRedCap terminal is Individually scheduled.
  • the network device when the broadcast PDSCH of the non-eRedCap terminal (ie, the second broadcast PDSCH corresponding to the non-eRedCap terminal) carries the RAR, the network device separately schedules the second broadcast PDSCH carrying the RAR.
  • the network device separately schedules the second broadcast PDSCH carrying the paging message.
  • the network device separately schedules the second broadcast PDSCH carrying the RAR, and separately schedules the second broadcast PDSCH carrying the paging message.
  • the corresponding advertisements of eRedCap terminals and non-eRedCap terminals are The PDSCH is broadcast and scheduled separately.
  • the first broadcast PDSCH corresponding to the eRedCap terminal and the second broadcast PDSCH corresponding to the non-eRedCap terminal each carry a corresponding RAR, such as: the first broadcast PDSCH corresponding to the eRedCap terminal carries the first RAR, and the second broadcast PDSCH corresponding to the non-eRedCap terminal carries the second RAR.
  • the network device separately schedules the broadcast PDSCHs carrying different information
  • the network device separately schedules the first broadcast PDSCH carrying the first RAR and separately schedules the second broadcast PDSCH carrying the second RAR.
  • the first broadcast PDSCH corresponding to the eRedCap terminal and the second broadcast PDSCH corresponding to the non-eRedCap terminal each carry a corresponding paging message, such as: the first broadcast PDSCH corresponding to the eRedCap terminal carries the first paging message, and the second broadcast PDSCH corresponding to the non-eRedCap terminal carries the second paging message.
  • the network device separately schedules the broadcast PDSCHs carrying different information
  • the first broadcast PDSCH carrying the first paging message is separately scheduled
  • the second broadcast PDSCH carrying the second paging message is separately scheduled.
  • the network device schedules the broadcast PDSCHs carrying different information separately, it schedules the first broadcast PDSCH carrying the RAR separately, and schedules the second broadcast PDSCH carrying the paging message separately.
  • the network device separately schedules the first broadcast PDSCH carrying the paging message and the second broadcast PDSCH carrying the RAR when separately scheduling the broadcast PDSCHs carrying different information.
  • the first broadcast PDSCH corresponding to the eRedCap terminal and the second broadcast PDSCH corresponding to the non-eRedCap terminal each carry the corresponding RAR and paging message, such as: the first broadcast PDSCH corresponding to the eRedCap terminal carries the first RAR and the first paging message, and the second broadcast PDSCH corresponding to the non-eRedCap terminal carries the second RAR and the second paging message.
  • the network device separately schedules the broadcast PDSCHs carrying different information
  • the first broadcast PDSCH carrying the first RAR is separately scheduled, and the first broadcast PDSCH carrying the first paging message is separately scheduled
  • the second broadcast PDSCH carrying the second RAR is separately scheduled, and the second broadcast PDSCH carrying the second paging message is separately scheduled.
  • the non-eRedCap terminal is a legacy terminal.
  • the legacy terminal may have a greater bandwidth processing capability, for example: the bandwidth processing capability of the eRedCap terminal is within 5MHZ; the bandwidth processing capability of the legacy terminal is 20MHZ, etc.
  • the bandwidth processing capability of the eRedCap terminal is within 5MHZ; the bandwidth processing capability of the legacy terminal is 20MHZ, etc.
  • the broadcast PDSCH is scheduled separately for the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the impact on the scheduling of other types of terminals can be avoided as much as possible.
  • the process of performing separate scheduling for different broadcast channels includes at least one of the following methods:
  • Method 1 For separate scheduling of RAR, the first type of terminal is required to perform early indication when transmitting PRACH. For example: For separate scheduling of RAR, the eRedCap terminal is required to perform early indication when transmitting PRACH;
  • Method 2 For separate scheduling of paging, when a first type of terminal is in an idle state and CN side paging is to be performed, the first type of device type or the bandwidth capability of the first type of terminal is notified to the network device through inter-node RRC signaling.
  • the eRedCap device type or the bandwidth capability of the eRedCap terminal is notified to the network device through inter-node RRC signaling;
  • Method three configuring independent scheduling parameters and/or transmission resource parameters to implement a separate scheduling process for the broadcast PDSCH.
  • Method 1 For separate scheduling of RAR, the first type of terminal is required to perform early indication when transmitting PRACH.
  • step 210 may also be implemented as the following step 310 .
  • Step 310 Schedule the broadcast PDSCH carrying the RAR separately.
  • the following description is given by taking the first type of terminal as an eRedCap terminal as an example.
  • the broadcast PDSCH used to carry the enhanced reduced capability eRedCap terminal RAR is scheduled separately. That is, when the content carried by the broadcast PDSCH corresponding to the eRedCap terminal is RAR, when the broadcast PDSCH of the eRedCap terminal is transmitted, the broadcast PDSCH carrying RAR is scheduled separately.
  • the broadcast PDSCH corresponding to the eRedCap terminal is the first broadcast PDSCH.
  • the operation status and operation resources of the RAR in the first broadcast PDSCH carrying the RAR are read separately.
  • first indication information is received, where the first indication information is used to indicate to the network device the device type of the first type of terminal and/or the channel bandwidth of the terminal.
  • the first indication information is used to indicate to the network device the device type of the eRedCap terminal and/or the channel bandwidth of the terminal.
  • a physical random access channel PRACH is received, and the PRACH carries first indication information.
  • the first indication information includes early indication information.
  • the early indication information is used to indicate the device type of the eRedCap terminal and/or the channel bandwidth of the terminal to the network device.
  • the network device first receives the PRACH transmitted by the eRedCap terminal, and after receiving the PRACH transmitted by the eRedCap terminal, reads the advance indication information in the PRACH, so that the network device can determine the device type of the eRedCap terminal based on the advance indication information.
  • the network device receives terminal type information sent by the eRedCap terminal.
  • the terminal type information is indicated explicitly or implicitly through message 1 (message 1, MSG1); or, the terminal type information is carried through the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) of message A, etc.
  • message 1 messages 1, MSG1
  • PUSCH Physical Uplink Shared Channel
  • the terminal type information includes the device type of the eRedCap terminal. That is, the eRedCap terminal sends the terminal type indication information to the network device, so that the network device determines the device type of the eRedCap terminal according to the terminal type information.
  • the broadcast PDSCH is scheduled separately for the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • the information carried in the broadcast PDSCH is implemented as RAR as an example for explanation.
  • the network device separately schedules the broadcast PDSCH carrying the RAR, so as to avoid affecting the scheduling of the legacy terminal as much as possible when scheduling the broadcast PDSCH corresponding to the first type of terminal.
  • Method 2 For separate scheduling of paging, when the first type of terminal is in an idle state and needs to perform CN side paging, the first type of device type or the bandwidth capability of the first type of terminal is notified to the network device through inter-node RRC signaling.
  • step 210 may also be implemented as the following step 410 .
  • Step 410 separately schedule the broadcast PDSCH carrying the paging message.
  • the first type of terminal is implemented as an eRedCap terminal as an example for description.
  • the broadcast PDSCH when the content carried in the broadcast PDSCH is a paging message, when the broadcast PDSCH corresponding to the eRedCap terminal and carrying the paging message is transmitted, the broadcast PDSCH is scheduled separately.
  • second indication information is received, where the second indication information is used to indicate a device type of the terminal and/or a channel bandwidth of the terminal.
  • radio resource control RRC signaling is received, where the RRC signaling carries second indication information.
  • the RRC signaling includes the device type of the terminal and/or the channel bandwidth of the terminal.
  • the core network node will send the device type and/or bandwidth capability of the eRedCap terminal to the base station through inter-node RRC signaling.
  • the base station distinguishes whether the paged terminal is a legacy terminal or an eRedCap terminal based on the received device type and/or bandwidth capability information of the eRedCap terminal, and then adopts a scheduling strategy corresponding to the terminal type; for example, one broadcast PDSCH is used to carry paging messages for multiple legacy terminals, and another broadcast PDSCH is used to carry paging messages for multiple eRedCap terminals.
  • the frequency domain resource width of the broadcast PDSCH carrying the paging message of the legacy terminal may be greater than 5MHz, and the frequency domain resource width of the broadcast PDSCH carrying the paging message of the eRedCap terminal may be less than or equal to 5MHz.
  • the core network device when RRC signaling is sent to a network device through a node, the core network device sends RRC signaling to the network device through a node between the core network device and the network device. Based on the RRC signaling, the network device can determine the device type of the terminal and/or the channel bandwidth of the terminal.
  • the network device determines the device type of the eRedCap terminal based on RRC signaling; or, the network device determines the channel bandwidth of the eRedCap terminal based on RRC signaling; or, the network device determines the device type and channel bandwidth of the eRedCap terminal based on RRC signaling.
  • the RRC signaling includes at least one of the following:
  • the channel bandwidth of 5MHZ is used as an example for explanation.
  • the RRC signaling may include the following bytes: ChannelBWnomorethan5MHZ-r18;
  • the RRC signaling may include the following bytes: dataChannelBWnomorethan5MHZ-r18;
  • the RRC signaling may include the following bytes: PDSCHchannelBWnomorethan5MHZ-r18.
  • the broadcast PDSCH is scheduled separately for the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • the information in the broadcast PDSCH is implemented as a paging message as an example for explanation.
  • the broadcast PDSCH carrying the paging message is scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of the legacy terminal is avoided as much as possible.
  • Method 3 Allocating independent transmission resource parameters to achieve a separate scheduling process for the broadcast PDSCH.
  • step 210 may also be implemented as the following step 510 .
  • Step 510 configure independent scheduling parameters and/or transmission resource parameters for the first type of terminal.
  • broadcast PDSCHs of different terminals are scheduled separately.
  • the broadcast PDSCH carries at least one of the following information: RAR; paging message.
  • the first type of terminal is implemented as an eRedCap terminal as an example for description.
  • the network device configures independent scheduling parameters and/or transmission resource parameters for the eRedCap terminal.
  • the broadcast PDSCH corresponding to the eRedCap terminal is the first broadcast PDSCH.
  • the eRedCap terminal is configured with independent scheduling parameters and/or transmission resource parameters; or, when the first broadcast PDSCH carrying the paging message is scheduled separately, the eRedCap terminal is configured with independent scheduling parameters and/or transmission resource parameters.
  • the independent scheduling parameter and/or transmission resource parameter is used to indicate that the scheduling parameter and/or transmission resource parameter is sent separately for the first type of terminal.
  • the purpose is to enable legacy terminals to minimize the reading of downlink control information (DCI) and/or PDSCH that does not belong to themselves; and/or, to enable eRedCap terminals to minimize the reading of DCI that does not belong to the scheduling itself.
  • DCI downlink control information
  • eRedCap terminals to minimize the reading of DCI that does not belong to the scheduling itself.
  • the broadcast PDSCH is scheduled separately by configuring independent scheduling parameters and/or transmission resource parameters for the eRedCap terminal.
  • the process of separately scheduling the broadcast PDSCH is realized by allocating independent transmission resource parameters to the eRedCap terminal.
  • the broadcast PDSCH corresponding to the eRedCap terminal is the first broadcast PDSCH
  • the information carried in the first broadcast PDSCH is implemented as RAR.
  • the process of separately scheduling the first broadcast PDSCH is realized by allocating independent transmission resource parameters to the eRedCap terminal.
  • the process of separately scheduling the broadcast PDSCH is implemented by allocating independent transmission resource parameters to the eRedCap terminal.
  • the broadcast PDSCH corresponding to the eRedCap terminal is the first broadcast PDSCH
  • the information carried in the first broadcast PDSCH is implemented as a paging message.
  • the process of separately scheduling the first broadcast PDSCH is implemented by allocating independent transmission resource parameters to the eRedCap terminal.
  • the independent scheduling parameters and/or transmission resource parameters include at least one of the following:
  • Partial bandwidth BWP Partial bandwidth BWP; control resource group CORESET; common search space CSS; paging radio network temporary identifier P-RNTI; system information radio network temporary identifier SI-RNTI; random access radio network temporary identifier RA-RNTI; demodulation reference signal DMRS sequence or pattern; downlink control information DCI length; use of reserved bit indication in DCI.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as a BWP
  • the independent BWP is used to send the physical downlink control channel PDCCH and the physical downlink shared channel PDSCH to the eRedCap terminal.
  • the independent CORESET is used to send DCI for scheduling the broadcast PDSCH to the eRedCap terminal.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as a CSS
  • the independent CSS is used to send the DCI for scheduling the broadcast PDSCH to the eRedCap terminal.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as P-RNTI
  • the independent P-RNTI is used to send the PDSCH carrying the paging message and the scheduling DCI to the eRedCap terminal.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as SI-RNTI
  • the independent SI-RNTI is used to send the PDSCH carrying the system message and the scheduling DCI to the eRedCap terminal.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as RA-RNTI
  • the independent RA-RNTI is used to send the PDSCH carrying the RAR message and the scheduling DCI to the eRedCap terminal.
  • an independent DMRS sequence or DMRS pattern is used to send PDCCH and/or PDSCH to the eRedCap terminal.
  • the independent DCI length is used to send a DCI for scheduling a broadcast PDSCH to an eRedCap terminal.
  • the eRedCap terminal is instructed whether to receive the PDSCH based on the indication of the reserved bit in the DCI.
  • whether to send the PDSCH is determined based on the indication of the reserved bit in the DCI. For example, when the indication of the reserved bit in the DCI is 1, the corresponding PDSCH is not sent to the eRedCap terminal.
  • the broadcast PDSCH is scheduled separately to the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • FIG. 6 is a flowchart of a scheduling method provided by an exemplary embodiment of the present disclosure, and is described by taking the first type of terminal implemented as an eRedCap terminal as an example. As shown in FIG. 6 , the method includes the following step 610 .
  • Step 610 Receive a broadcast PDSCH sent by a network device.
  • the broadcast PDSCH is a channel scheduled separately by the network equipment.
  • the broadcast PDSCH carries at least one of the following information: RAR; paging message.
  • the broadcast PDSCH of the eRedCap terminal when the broadcast PDSCH of the eRedCap terminal is transmitted, the broadcast PDSCH carrying different information is scheduled separately.
  • the broadcast PDSCH carrying RAR and paging message is taken as an example for explanation.
  • the broadcast PDSCH carrying the RAR is scheduled separately, and the broadcast PDSCH carrying the paging message is scheduled separately.
  • the network device is further configured to separately schedule the second broadcast PDSCH when transmitting the second broadcast PDSCH of a non-eRedCap terminal.
  • the network device can not only separately schedule the first broadcast PDSCH, for example, separately schedule the first broadcast PDSCH carrying RAR, and schedule the first broadcast PDSCH carrying paging message; it can also separately schedule the second broadcast PDSCH, for example, separately schedule the second broadcast PDSCH carrying RAR, and schedule the second broadcast PDSCH carrying paging message.
  • first indication information is sent.
  • the first indication information is used to indicate the device type of the first type of terminal and/or the channel bandwidth of the terminal to the network device.
  • a PRACH is sent to the network device, where the PRACH includes first indication information.
  • the first indication information includes advance indication information
  • the advance indication information is used to indicate the device type of the eRedCap terminal to the network device.
  • the network device reads the advance indication information in the PRACH, so that the network device can determine the device type of the terminal based on the advance indication information. For example, determine the device type of the eRedCap terminal.
  • the eRedCap terminal sends terminal type information to the network device.
  • the terminal type information is indicated in an explicit or implicit manner through MSG1; or, the terminal type information is carried by the PUSCH of message A, etc.
  • the terminal type information includes the device type of the eRedCap terminal. That is, the eRedCap terminal sends the terminal type indication information to the network device, so that the network device determines the device type of the eRedCap terminal according to the terminal type information.
  • the broadcast PDSCH carrying the paging message is scheduled separately by the network device.
  • independent scheduling parameters and/or transmission resource parameters configured for the eRedCap terminal are received.
  • DCI downlink control information
  • PDSCH downlink control information
  • eRedCap terminal in order to enable the legacy terminal to minimize the reading of downlink control information (DCI) and/or PDSCH that does not belong to itself; and/or, to enable the eRedCap terminal to minimize the reading of DCI that does not belong to the scheduling itself, independent scheduling parameters and/or transmission resource parameters are configured for the eRedCap terminal.
  • DCI downlink control information
  • eRedCap terminal independent scheduling parameters and/or transmission resource parameters are configured for the eRedCap terminal.
  • the independent scheduling parameters and/or transmission resource parameters include at least one of the following:
  • Partial bandwidth BWP Partial bandwidth BWP; control resource group CORESET; common search space CSS; paging radio network temporary identifier P-RNTI; system information radio network temporary identifier SI-RNTI; random access radio network temporary identifier RA-RNTI; demodulation reference signal DMRS sequence or pattern; downlink control information DCI length; use of reserved bit indication in DCI.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as a BWP
  • the independent BWP is used to receive the physical downlink control channel PDCCH and the physical downlink shared channel PDSCH from the eRedCap terminal.
  • the independent CORESET is used to schedule the reception of DCI of the broadcast PDSCH to the eRedCap terminal.
  • the independent CSS is used to schedule the reception of DCI of the broadcast PDSCH to the eRedCap terminal.
  • the independent P-RNTI is used to receive the PDSCH carrying the paging message and the scheduling DCI to the eRedCap terminal.
  • the independent SI-RNTI is used to receive the PDSCH carrying the system message and the scheduling DCI from the eRedCap terminal.
  • the independent transmission resource parameter allocated to the broadcast channel is implemented as RA-RNTI
  • the independent RA-RNTI is used to receive the PDSCH carrying the RAR message and the scheduling DCI from the eRedCap terminal.
  • an independent DMRS sequence or DMRS pattern is used to receive PDCCH and/or PDSCH to the eRedCap terminal.
  • an independent transmission resource parameter allocated to a broadcast channel is implemented as a DCI length
  • the independent DCI length is used to receive the DCI that schedules the broadcast PDSCH.
  • whether to receive the PDSCH is determined based on the indication of the reserved bit in the DCI. For example, when the indication of the reserved bit in the DCI is 1, the corresponding PDSCH is not received by the eRedCap terminal.
  • the broadcast PDSCH is scheduled separately to the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • Figure 7 is a flowchart of a scheduling method provided by an exemplary embodiment of the present disclosure.
  • the method is applied to the interaction process between the eRedCap terminal and the network device as an example for explanation. As shown in Figure 7, the method includes the following steps 710 to 720.
  • Step 710 Schedule and broadcast a physical downlink shared channel PDSCH to terminals of the first type separately.
  • the following description is given by taking the first type of terminal as an eRedCap terminal as an example.
  • the eRedCap terminal is an enhanced reduced capability terminal, that is, the eRedCap terminal is represented as enhanced Reduced Capability UE.
  • enhanced reduced capability is used to indicate the reduction of the terminal capability by enhancement.
  • the eRedCap terminal is a RedCap terminal, and the terminal capability of the eRedCap terminal is reduced compared with the ordinary terminal.
  • the broadcast PDSCH carries at least one of the following information: a random access response RAR; and a paging message.
  • the broadcast PDSCH of the eRedCap terminal is transmitted, the broadcast PDSCHs carrying different information are scheduled separately.
  • the eRedCap terminal corresponds to the first broadcast PDSCH; the non-eRedCap terminal corresponds to the second broadcast PDSCH.
  • the broadcast PDSCH is scheduled separately, the first broadcast PDSCH corresponding to the eRedCap terminal is scheduled separately; and/or, the second broadcast PDSCH corresponding to the non-eRedCap terminal is scheduled separately.
  • the non-eRedCap terminal is a legacy terminal.
  • the broadcast PDSCH carrying different information is scheduled separately.
  • the broadcast PDSCH carrying RAR when the broadcast PDSCH carries RAR, the broadcast PDSCH carrying RAR is scheduled separately; when the broadcast PDSCH carries a paging message, the broadcast PDSCH carrying RAR is scheduled separately.
  • the process of separately scheduling the broadcast PDSCHs corresponding to different terminals can be implemented in one of the following forms:
  • the first broadcast PDSCH corresponding to the eRedCap terminal is Independent dispatch.
  • the network device when the broadcast PDSCH of the eRedCap terminal (ie, the first broadcast PDSCH corresponding to the eRedCap terminal) carries the RAR, the network device separately schedules the first broadcast PDSCH carrying the RAR.
  • the network device separately schedules the first broadcast PDSCH carrying the paging message.
  • the network device separately schedules the first broadcast PDSCH carrying the RAR, and separately schedules the first broadcast PDSCH carrying the paging message.
  • the second broadcast PDSCH corresponding to the non-eRedCap terminal is Individually scheduled.
  • the network device when the broadcast PDSCH of the non-eRedCap terminal (ie, the second broadcast PDSCH corresponding to the non-eRedCap terminal) carries the RAR, the network device separately schedules the second broadcast PDSCH carrying the RAR.
  • the network device separately schedules the second broadcast PDSCH carrying the paging message.
  • the network device separately schedules the second broadcast PDSCH carrying the RAR, and separately schedules the second broadcast PDSCH carrying the paging message.
  • the corresponding advertisements of eRedCap terminals and non-eRedCap terminals are The PDSCH is broadcast and scheduled separately.
  • the first broadcast PDSCH corresponding to the eRedCap terminal and the second broadcast PDSCH corresponding to the non-eRedCap terminal each carry a corresponding RAR, such as: the first broadcast PDSCH corresponding to the eRedCap terminal carries the first RAR, and the second broadcast PDSCH corresponding to the non-eRedCap terminal carries the second RAR.
  • the network device separately schedules the broadcast PDSCHs carrying different information
  • the network device separately schedules the first broadcast PDSCH carrying the first RAR and separately schedules the second broadcast PDSCH carrying the second RAR.
  • the network device separately schedules the broadcast PDSCHs carrying different information, it separately schedules the first broadcast PDSCH carrying the first paging message and separately schedules the second broadcast PDSCH carrying the second paging message.
  • the network device schedules the broadcast PDSCHs carrying different information separately, it schedules the first broadcast PDSCH carrying the RAR separately, and schedules the second broadcast PDSCH carrying the paging message separately.
  • the network device separately schedules the first broadcast PDSCH carrying the paging message and the second broadcast PDSCH carrying the RAR when separately scheduling the broadcast PDSCHs carrying different information.
  • the first broadcast PDSCH corresponding to the eRedCap terminal and the second broadcast PDSCH corresponding to the non-eRedCap terminal each carry the corresponding RAR and paging message, such as: the first broadcast PDSCH corresponding to the eRedCap terminal carries the first RAR and the first paging message, and the second broadcast PDSCH corresponding to the non-eRedCap terminal carries the second RAR and the second paging message.
  • the network device separately schedules the broadcast PDSCHs carrying different information
  • the first broadcast PDSCH carrying the first RAR is separately scheduled, and the first broadcast PDSCH carrying the first paging message is separately scheduled
  • the second broadcast PDSCH carrying the second RAR is separately scheduled, and the second broadcast PDSCH carrying the second paging message is separately scheduled.
  • the network device sends a broadcast PDSCH to the eRedCap terminal.
  • Step 720 Receive a broadcast PDSCH sent by a network device.
  • the broadcast PDSCH is a channel scheduled independently by the network device, that is, when the network device transmits the first broadcast PDSCH of the eRedCap terminal, the first broadcast PDSCH is scheduled independently.
  • the first broadcast PDSCH carries at least one of the following information: RAR; paging message.
  • a PRACH is sent to the network device, where the PRACH includes advance indication information, and the advance indication information is used to indicate the device type of the eRedCap terminal to the network device.
  • the paging message sent by the network device is received.
  • independent scheduling parameters and/or transmission resource parameters configured by the network device are received.
  • Step 720 has been described in the above step 610 and will not be repeated here.
  • the eRedCap terminal receives the broadcast PDSCH sent by the network device after the network device separately schedules the broadcast PDSCH of the eRedCap terminal. Based on the process of separate scheduling of the broadcast PDSCH by the network device, in a network where legacy terminals and eRedCap terminals coexist, the reception accuracy of the eRedCap terminal can be improved and the impact on the scheduling of the legacy terminal can be avoided as much as possible.
  • FIG8 is a structural block diagram of a scheduling device provided by an exemplary embodiment of the present disclosure.
  • the scheduling device is applied to a network device. As shown in FIG8 , the device includes:
  • the scheduling module 810 is configured to separately schedule broadcasting of a physical downlink shared channel PDSCH to the first type of terminals.
  • the broadcast PDSCH carries a random access response RAR
  • the scheduling module 810 is also used to separately schedule the broadcast PDSCH carrying the RAR.
  • the device further comprises:
  • the receiving module 820 is used to receive first indication information, where the first indication information is used to indicate the device type of the first type of terminal and/or the channel bandwidth of the terminal to the network device.
  • the receiving module 820 is further configured to:
  • a physical random access channel PRACH is received, where the PRACH carries the first indication information.
  • the broadcast PDSCH carries a paging message
  • the scheduling module 810 is also used to separately schedule the broadcast PDSCH carrying the paging message.
  • the receiving module 820 is further configured to:
  • Second indication information is received, where the second indication information is used to indicate a device type of the terminal and/or a channel bandwidth of the terminal.
  • the receiving module 820 is further configured to:
  • a radio resource control RRC signaling is received, where the RRC signaling carries the second indication information.
  • the RRC signaling is used to indicate at least one of the following information:
  • the PDSCH channel bandwidth corresponding to the first type of terminal is the PDSCH channel bandwidth corresponding to the first type of terminal.
  • the device further comprises:
  • the configuration module 830 is used to configure independent scheduling parameters and/or transmission resource parameters for the first type of terminal.
  • the independent scheduling parameters and/or transmission resource parameters include at least one of the following:
  • Paging radio network temporary identifier P-RNTI Paging radio network temporary identifier
  • SI-RNTI System information radio network temporary identifier SI-RNTI
  • Random access radio network temporary identifier RA-RNTI Random access radio network temporary identifier
  • the configuration module 830 is further configured to:
  • the scheduling module 810 is further configured to:
  • the second broadcast PDSCH corresponding to the second type of terminal is scheduled separately.
  • the first type of terminal includes an enhanced reduced capability eRedCap terminal; and the second type of terminal includes an ordinary legacy terminal.
  • FIG. 9 is a structural block diagram of a scheduling device provided by an exemplary embodiment of the present disclosure.
  • the scheduling device is applied to a first type of terminal. As shown in FIG. 9 , the device includes:
  • the receiving module 910 is configured to receive a broadcast PDSCH sent by a network device, where the broadcast PDSCH is a channel independently scheduled by the network device.
  • the device is further used for:
  • the sending module 920 is used to send first indication information, where the first indication information is used to indicate the device type of the first type of terminal and/or the channel bandwidth of the terminal to the network device.
  • the sending module 920 is further configured to:
  • a PRACH is sent to the network device, where the PRACH includes first indication information.
  • the broadcast PDSCH carries a paging message
  • the broadcast PDSCH carrying the paging message is scheduled separately by the network device.
  • the receiving module 910 is further configured to:
  • Receive independent scheduling parameters and/or transmission resource parameters configured by the network device are configured by the network device.
  • the independent scheduling parameters and/or transmission resource parameters include at least one of the following:
  • Paging radio network temporary identifier P-RNTI Paging radio network temporary identifier
  • SI-RNTI System information radio network temporary identifier SI-RNTI
  • Random access radio network temporary identifier RA-RNTI Random access radio network temporary identifier
  • the receiving module 910 is further configured to:
  • the broadcast PDSCH is scheduled separately to the first type of terminal, so that in a network where different types of terminals coexist, the broadcast PDSCHs corresponding to different terminals are scheduled separately, so that when the broadcast PDSCH corresponding to the first type of terminal is scheduled, the scheduling of other types of terminals can be avoided as much as possible.
  • the scheduling device provided in the above embodiment is only illustrated by the division of the above functional modules.
  • the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the scheduling device provided in the above embodiment and the scheduling method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
  • FIG10 shows a schematic structural diagram of a communication device 1000 (terminal or network device) provided by an exemplary embodiment of the present disclosure.
  • the terminal includes: a processor 1001 , a receiver 1002 , a transmitter 1003 , a memory 1004 and a bus 1005 .
  • the processor 1001 includes one or more processing cores.
  • the processor 1001 executes various functional applications and information processing by running software programs and modules.
  • the receiver 1002 and the transmitter 1003 may be implemented as a communication component, which may be a communication chip.
  • the memory 1004 is connected to the processor 1001 via a bus 1005 .
  • the memory 1004 may be used to store at least one instruction, and the processor 1001 may be used to execute the at least one instruction to implement each step in the above method embodiment.
  • memory 1004 can be implemented by any type of volatile or non-volatile storage device or a combination thereof.
  • Volatile or non-volatile storage devices include but are not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), read-only memory (ROM), magnetic memory, flash memory, and programmable read-only memory (PROM).
  • a non-transitory computer-readable storage medium when instructions in the non-transitory computer storage medium are executed by a processor of a terminal, enables the terminal to execute the above-mentioned scheduling method.
  • An exemplary embodiment of the present disclosure further provides a scheduling system, the system comprising: a terminal and a network device;
  • the network device includes the scheduling device provided by the embodiment shown in FIG8 .
  • the terminal includes a scheduling device provided in the embodiment shown in FIG9 ;
  • An exemplary embodiment of the present disclosure also provides a computer-readable storage medium, in which at least one instruction, at least one program, a code set or an instruction set is stored, and the at least one instruction, the at least one program, the code set or the instruction set is executed by the processor to implement the steps performed by the terminal in the scheduling method provided by the above-mentioned various method embodiments.

Landscapes

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

Abstract

本公开提供了一种调度方法、装置、设备及可读存储介质，涉及通信领域。该方法包括：向第一类型终端单独调度广播物理下行共享信道PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。

Description

调度方法、装置、设备及可读存储介质 技术领域
本公开涉及通信领域，特别涉及一种调度方法、装置、设备及可读存储介质。
背景技术
在5G新空口(New Radio，NR)中，在第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)的版本Release17，通过对普通终端采用降低复杂度的方法，得到对数据速率要求较为宽松的降低能力终端设备Reduced capability UE，即：RedCap终端。除此之外，Release18计划在Release17的基础上进一步降低终端成本，以满足介于R17 RedCap与LPWA终端之间的业务/终端成本需求。
相关技术中，上述降低复杂度的方法可以应用到单播信道unicast channel和广播信道broadcast channel中，对于broadcast channel，例如RAR、paging等，网络出于负载开销payload overhead的考虑，可能对旧版legacy终端的调度超出5MHz。
然而，在legacy终端和eRedCap终端共存的网络中，基于eRedCap终端的5MHz数据信道带宽的限制，legacy终端的调度的过程可能会受到eRedCap终端限制的影响。
发明内容
本公开实施例提供了一种调度方法、装置、设备及可读存储介质，在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。所述技术方案如下：
根据本公开的一方面，提供了一种调度方法，所述方法由网络设备执行，所述方法包括：
向第一类型终端单独调度广播物理下行共享信道PDSCH。
另一方面，提供了一种调度方法，所述方法由第一类型终端执行，所述方法包括：
接收网络设备发送的广播PDSCH，所述广播PDSCH是由所述网络设备单独调度的信道。
另一方面，提供了一种调度装置，所述装置应用于网络设备，所述装置包括：
调度模块，用于向第一类型终端单独调度广播物理下行共享信道PDSCH。
另一方面，提供了一种调度装置，所述装置应用于终端，所述装置包括：
接收模块，用于接收网络设备发送的广播PDSCH，所述广播PDSCH是由所述网络设备单独调度的信道。
另一方面，提供了一种终端，该终端包括：
处理器；
与处理器相连的收发器；
其中，处理器被配置为执行可执行指令以实现如上述本公开实施例所述的调度方法。
另一方面，提供了一种网络设备，该网络设备包括：
处理器；
与处理器相连的收发器；
其中，处理器被配置为执行可执行指令以实现如上述本公开实施例所述的调度方法。
另一方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，上述至少一条指令、至少一段程序、代码集或指令集由处理器执行以实现如上述本公开实施例所述的调度方法。
本公开实施例提供的技术方案带来的有益效果至少包括：
向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
附图说明
为了更清楚地说明本公开实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本公开实施例提供的通信系统的架构框图；
图2是本公开一个示例性实施例提供的网络设备侧进行调度方法的流程图；
图3是本公开另一个示例性实施例提供的网络设备侧进行调度方法的流程图；
图4是本公开再一个示例性实施例提供的网络设备侧进行调度方法的流程图；
图5是本公开又一个示例性实施例提供的网络设备侧进行调度方法的流程图；
图6是本公开一个示例性实施例提供的终端侧进行调度方法的流程图；
图7是本公开一个示例性实施例提供的终端侧和网络设备侧交互进行调度方法的流程图；
图8是本公开一个示例性实施例示出的调度装置的结构示意图；
图9是本公开另一个示例性实施例示出的调度装置的结构示意图；
图10是本公开一个示例性实施例示出的通信设备的结构框图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚，下面将结合附图对本公开实施方式作进一步地详细描述。
在5G新空口(New Radio，NR)中，在3GPP的R17中，通常采用下述降低复杂度complexity reduction的方法，以得到对数据速率要求较为宽松的降低能力终端设备RedCap终端。
(1)降低基带处理带宽，例如：限制eRedCap终端接收的物理下行共享信道(Physical Downlink Shared Channel，PDSCH)的频域宽度在5MHz之内。
(2)限制最大资源块RB的数量，例如：将数据信道的资源个数缩减到5MHZ以内，缩减的资源在频域上是连续或者离散的。
相关技术中，上述降低复杂度的方法可以应用到单播信道unicast channel和广播信道broadcast channel中，对于broadcast channel，例如RAR、paging等，网络出于负载开销payload overhead的考虑，可能对旧版legacy终端的调度超出5MHz。
然而，在legacy终端和eRedCap终端共存的网络中，基于eRedCap终端的带宽限制，legacy终端的调度的过程可能会受到eRedCap终端限制的影响。
图1示出了本公开一个示意性实施例提供的通信系统的框图，该通信系统可以包括：核心网11、接入网12和终端13。
核心网11中包括若干个核心网设备110。核心网设备110是部署在核心网中的设备，核心网设备的功能主要是提供用户连接、对用户的管理以及对业务完成承载，作为承载网络提供到外部网络的接口。例如，5G NR系统中的核心网设备可以包括接入和移动性管理功能(Access and Mobility Management Function，AMF)网元、用户平面功能(User Plane Function，UPF)网元和会话管理功能(Session Management Function，SMF)网元等。示例性的，本申请实施例中的核心网设备30可以包括位置管理功能网元。可选地，位置管理功能网元包括位置服务器(location server)，位置服务器可以实现为以下任意一项：LMF(Location Management Function，位置管理网元)、E-SMLC(Enhanced Serving Mobile Location Centre，增强服务的流动定位中心)、SUPL(Secure User Plane Location，安全用户平面定位)、SUPL SLP(SUPL Location Platform，安全用户平面定位平台)。
接入网12中包括若干个网络设备120。网络设备120可以是基站，基站是一种部署在接入网中用以为终端提供无线通信功能的装置。基站可以包括各种形式的宏基站，微基站，中继站，接入点或发送接收点(Transmission Reception Point，TRP)等等。在采用不同的无线接入技术的系统中，具备基站功能的设备的名称可能会有所不同，例如在长期演进(Long Term Evolution，LTE)系统中，称为eNodeB或者eNB；在5G新空口(New Radio，NR)系统中，称为gNode B或者gNB。随着通信技术的演进，“基站”这一名称可能描述会变化。为方便本公开实施例中，上述为终端提供无线通信功能的装置统称为网络设备。
终端13可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设 备、计算设备或连接到无线调制解调器的其他处理设备，以及各种形式的终端，移动台(Mobile Station，MS)，终端(terminal device)等等。为方便描述，上面提到的设备统称为终端。本申请实施例中，终端13中包括普通终端和RedCap终端，其中，RedCap终端相比于普通终端存在复杂度低、功率节省的特点。网络设备120与终端13之间通过某种空口技术互相通信，例如Uu接口。
基于5G的工业传感器(Industrial sensor)、监控摄像(video surveillance)以及可穿戴类设备等不需要支持这么大的带宽，尤其是工业传感器类，仅需要数兆的传输带宽。此类终端在5G后续版本增强中可能被归为一种新的设备类型，并进行相应的技术特性改进。也即，本申请实施例提供的RedCap终端，RedCap终端是对上述普通终端进行版本增强后得到的终端，从而使得RedCap终端能够更好地适应低时延以及较高速率的场景。RedCap终端也可以简称为NR-lite(轻量级)终端，该类设备同LTE中的物联网设备类似，需要满足如下要求：
1、低造价，低复杂度；
2、一定程度的覆盖增强；
3、节省功率。
可选地，以上述终端13和网络设备120之间进行无线通信的过程中，可以通过授权频段进行无线通信，也可以通过非授权频段进行无线通信。
示意性的，请参考图2，本公开一个示例性实施例提供的调度方法的流程图，以该方法应用于网络设备为例进行说明，如图2所示，该方法包括如下步骤210。
步骤210，向第一类型终端单独调度广播物理下行共享信道PDSCH。
可选地，第一类型终端包括增强降低能力eRedCap终端。
其中，eRedCap终端为增强性增强降低能力的终端，也即：eRedCap终端表示为enhanced Reduced Capability UE。示意性的，增强降低能力用于指示增强对终端能力的降低。示意性的，eRedCap终端为RedCap终端，相较普通终端(legacy终端)，eRedCap终端的终端能力有所降低。
可选地，广播PDSCH承载有如下至少一种信息：随机接入响应RAR；寻呼消息。例如：广播PDSCH承载有RAR；或者，广播PDSCH承载有寻呼消息；或者，广播PDSCH承载有RAR和寻呼消息。
在一个可选的实施例中，不同的终端分别有其对应的广播PDSCH。
可选地，对第一类型终端对应的第一广播PDSCH进行单独调度；和/或，对第二类型终端对应的第二广播PDSCH进行单独调度。示意性的，第二类型终端包括普通legacy终端。
值得注意的是，第一类型终端包括eRedCap终端；第二类型终端包括legacy终端仅为示意性的举例，本申请实施例对此不加以限定。
在一个可选的实施例中，以第一类型终端实现为eRedCap终端；第二类型终端实现为非eRedCap终端(如：legacy终端)为例进行如下说明。
其中，eRedCap终端对应第一广播PDSCH；非eRedCap终端对应的第二广播PDSCH。
可选地，在对广播PDSCH进行调度时，对eRedCap终端对应的第一广播PDSCH进行单独调度；和/或，对非eRedCap终端对应的第二广播PDSCH进行单独调度。
示意性的，对不同终端分别对应的广播PDSCH进行单独调度的过程可以实现为如下形式中的一种：
1、针对eRedCap终端的广播PDSCH进行单独调度。
示意性的，针对eRedCap终端而言，在对eRedCap终端的广播PDSCH进行调度时，对eRedCap终端对应的第一广播PDSCH进行单独调度。
2、针对非eRedCap终端的广播PDSCH进行单独调度。
示意性的，针对非eRedCap终端而言，在对非eRedCap终端的广播PDSCH进行调度时，对非eRedCap终端对应的第二广播PDSCH进行单独调度。
3、针对eRedCap终端和非eRedCap终端分别对应的广播PDSCH进行单独 调度。
示意性的，针对eRedCap终端和非eRedCap终端而言，在对终端对应的广播PDSCH进行调度时，对eRedCap终端对应的第一广播PDSCH进行单独调度，并对非eRedCap终端对应的第二广播PDSCH进行单独调度。
值得注意的是，以上仅为示意性的举例本申请实施例对此不加以限定。
可选地，在对eRedCap终端的广播PDSCH进行传输时，对承载有不同信息的广播PDSCH进行分别调度。示意性的，当广播PDSCH承载有RAR时，对承载有RAR的广播PDSCH进行单独调度；当广播PDSCH承载有寻呼消息时，对承载有RAR的广播PDSCH进行单独调度。
示意性的，根据承载信息的差异，对不同终端分别对应的广播PDSCH进行单独调度的过程可以实现为如下形式中的一种：
1、根据承载信息的差异，对eRedCap终端对应的第一广播PDSCH进行单 独调度。
示意性的，当eRedCap终端的广播PDSCH(即：与eRedCap终端对应的第一广播PDSCH)承载有RAR时，网络设备对承载有RAR的第一广播PDSCH进行单独调度。
或者，当与eRedCap终端对应的第一广播PDSCH承载有寻呼消息时，网络设备对承载有寻呼消息的第一广播PDSCH进行单独调度。
或者，当与eRedCap终端对应的第一广播PDSCH承载有RAR和寻呼消息时，网络设备对承载有RAR的第一广播PDSCH进行单独调度，对承载有寻呼消息的第一广播PDSCH进行单独调度。
2、根据承载信息的差异，对非eRedCap终端对应的第二广播PDSCH进行 单独调度。
示意性的，当非eRedCap终端的广播PDSCH(即：与非eRedCap终端对应的第二广播PDSCH)承载有RAR时，网络设备对承载有RAR的第二广播PDSCH进行单独调度。
或者，当与非eRedCap终端对应的第二广播PDSCH承载有寻呼消息时，网络设备对承载有寻呼消息的第二广播PDSCH进行单独调度。
或者，当与非eRedCap终端对应的第二广播PDSCH承载有RAR和寻呼消息时，网络设备对承载有RAR的第二广播PDSCH进行单独调度，对承载有寻呼消息的第二广播PDSCH进行单独调度。
3、根据承载信息的差异，对eRedCap终端和非eRedCap终端分别对应的广 播PDSCH进行单独调度。
(1)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应的第二广播PDSCH各自承载有对应的RAR时，如：与eRedCap终端对应的第一广播PDSCH承载有第一RAR，与非eRedCap终端对应的第二广播PDSCH承载有第二RAR。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，网络设备对承载有第一RAR的第一广播PDSCH进行单独调度，对承载有第二RAR的第二广播PDSCH进行单独调度。
(2)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应的第二广播PDSCH各自承载有对应的寻呼消息时，如：与eRedCap终端对应的第一广播PDSCH承载有第一寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有第二寻呼消息。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有第一寻呼消息的第一广播PDSCH进行单独调度，对承载有第二寻呼消息的第二广播PDSCH进行单独调度。
(3)当与eRedCap终端对应的第一广播PDSCH承载有RAR，与非eRedCap终端对应的第二广播PDSCH承载有寻呼消息时。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有RAR的第一广播PDSCH进行单独调度，对承载有寻呼消息的第二广播PDSCH进行单独调度。
(4)当与eRedCap终端对应的第一广播PDSCH承载有寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有RAR时。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有寻呼消息的第一广播PDSCH进行单独调度，对承载有RAR的第二广播PDSCH进行单独调度。
(5)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应的第二广播PDSCH各自承载有对应的RAR和寻呼消息时，如：与eRedCap终端对应的第一广播PDSCH承载有第一RAR和第一寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有第二RAR和第二寻呼消息。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有第一RAR的第一广播PDSCH进行单独调度，对承载有第一寻呼消息的第一广播PDSCH进行单独调度；对承载有第二RAR的第二广播PDSCH进行单独调度，对承载有第二寻呼消息的第二广播PDSCH进行单独调度。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
可选地，上述非eRedCap终端即为legacy终端。可选地，相较eRedCap终端，legacy终端可以拥有更大的带宽处理能力，例如：eRedCap终端的带宽处理能力为5MHZ以内；legacy终端的带宽处理能力为20MHZ等。以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造 成影响。
本申请实施例中，根据广播信道承载信息的差异，针对不同广播信道进行单独调度的过程包括如下方式中的至少一种：
方法一：对于RAR的单独separate调度，要求第一类型终端在传输PRACH时进行early indication。例如：对于RAR的单独separate调度，要求eRedCap终端在传输PRACH时进行early indication；
方法二：对于paging的separate调度，第一类型终端的空闲idle状态下要进行CN侧寻呼时，通过节点间RRC信令将第一类型设备类型或者第一类型终端的带宽能力等通知给网络设备。例如：对于paging的separate调度，eRedCap终端的空闲idle状态下要进行CN侧寻呼时，通过节点间RRC信令将eRedCap设备类型或者eRedCap终端的带宽能力等通知给网络设备；
方法三：通过配置独立的调度参数和/或传输资源参数，以实现对广播PDSCH进行单独调度的过程。
针对上述方法，分别进行详细介绍。
方法一：对于RAR的单独separate调度，要求第一类型终端在传输PRACH时进行early indication。
示意性的，如图3所示，上述步骤210还可以实现为如下步骤310。
步骤310，对承载RAR的广播PDSCH进行单独调度。
在一个可选的实施例中，以第一类型终端实现为eRedCap终端为例进行如下说明。
示意性的，在对广播物理下行共享信道PDSCH进行传输时，对用于承载增强降低能力eRedCap终端RAR的广播PDSCH进行单独调度。也即：当eRedCap终端对应的广播PDSCH承载的内容为RAR时，在对eRedCap终端的广播PDSCH进行传输时，对承载有RAR的广播PDSCH进行单独调度。
例如：eRedCap终端对应的广播PDSCH为第一广播PDSCH，在对eRedCap终端的第一广播PDSCH进行传输时，对承载有RAR的第一广播PDSCH中RAR的运行状态、运行资源等进行单独读取。
可选地，接收第一指示信息，第一指示信息用于向网络设备指示第一类型终 端的设备类型和/或终端的信道带宽。例如：第一指示信息用于向网络设备指示eRedCap终端的设备类型和/或终端的信道带宽。
可选地，接收物理随机接入信道PRACH，PRACH上承载有第一指示信息。
示意性的，第一指示信息包括提前指示信息early indication。提前指示信息用于向网络设备指示eRedCap终端的设备类型和/或终端的信道带宽。
例如：网络设备首先接收eRedCap终端传输的PRACH，并在接收到eRedCap终端传输的PRACH后，对PRACH中的提前指示信息进行读取，以便于网络设备基于该提前指示信息，确定eRedCap终端的设备类型。
可选地，网络设备接收eRedCap终端发送的终端类型信息。
示意性的，终端类型信息通过消息1(message 1，MSG1)显式或隐式的方式指示；或者，终端类型信息通过消息A的物理上行共享信道(Physical Uplink Shared Channel，PUSCH)承载等。
可选地，终端类型信息中包括eRedCap终端的设备类型。也即：eRedCap终端向网络设备发送终端类型指示信息，以便网络设备根据终端类型信息确定eRedCap终端的设备类型。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
在本申请实施例中，以广播PDSCH中承载的信息实现为RAR为例进行说明。在对第一类型终端的广播PDSCH进行传输时，网络设备对承载有RAR的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，尽量避免对legacy终端的调度造成影响。
方式二：对于paging的separate调度，第一类型终端的空闲idle状态下要进行CN侧寻呼时，通过节点间RRC信令将第一类型设备类型或者第一类型终端的带宽能力等通知给网络设备。
示意性的，如图4所示，上述步骤210还可以实现为如下步骤410。
步骤410，对承载寻呼消息的广播PDSCH进行单独调度。
在一个可选的实施例中，以第一类型终端实现为eRedCap终端为例进行说明。
示意性的，当广播PDSCH中承载的内容是寻呼消息时，在对与eRedCap终端对应的、承载有寻呼消息的广播PDSCH进行传输时，对广播PDSCH进行单独调度。
在一个可选的实施例中，接收第二指示信息，第二指示信息用于指示终端的设备类型和/或终端的信道带宽。
可选地，接收无线资源控制RRC信令，RRC信令上承载有第二指示信息。
其中，RRC信令中包括终端的设备类型和/或终端的信道带宽。
示意性的，当eRedCap终端处于空闲状态下，需要对其进行(core network)CN核心网侧寻呼时，核心网节点将通过节点间RRC信令将eRedCap终端的设备类型和/或带宽能力发送至基站。基站基于收到的eRedCap终端的设备类型和/或带宽能力信息来区分被寻呼的终端是legacy终端还是eRedCap终端，进而采取与终端类型相对应的调度策略；比如采用一个广播PDSCH承载多个legacy终端的寻呼消息，采用另外一个广播PDSCH来承载多个eRedCap终端的寻呼消息。可选的，承载legacy终端寻呼消息的广播PDSCH频域资源宽度可大于5MHz，承载eRedCap终端寻呼消息的广播PDSCH的频域资源宽度小于等于5MHz。
示意性的，在通过节点向网络设备发送RRC信令时，通过核心网设备与网络设备之间的节点，由核心网设备向网络设备发送RRC信令，网络设备基于RRC信令，能够确定终端的设备类型和/或终端的信道带宽。
例如：网络设备基于RRC信令，确定eRedCap终端的设备类型；或者，网络设备基于RRC信令，确定eRedCap终端的信道带宽；或者，网络设备基于RRC信令，确定eRedCap终端的设备类型和信道带宽等。
在一个可选的实施例中，RRC信令包括如下至少一种：
eRedCap终端对应的信道带宽；eRedCap终端对应的数据信道带宽；eRedCap终端对应的PDSCH信道带宽。
示意性的，以信道带宽为5MHZ为例进行说明。当RRC信令实现为eRedCap终端对应的信道带宽时，RRC信令中可能包括如下字节：ChannelBWnomorethan5MHZ-r18；当RRC信令实现为eRedCap终端对应的数据信道带宽时，RRC信令中可能包括如下字节：dataChannelBWnomorethan5MHZ- r18；当RRC信令实现为eRedCap终端对应的PDSCH信道带宽时，RRC信令中可能包括如下字节：PDSCHChannelBWnomorethan5MHZ-r18。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
在本申请实施例中，以广播PDSCH中的信息实现为寻呼消息为例进行说明。在对第一类型终端的广播PDSCH进行传输时，对承载有寻呼消息的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，尽量避免对legacy终端的调度造成影响。
方式三：通过分配独立的传输资源参数，以实现对广播PDSCH进行单独调度的过程。
示意性的，如图5所示，上述步骤210还可以实现为如下步骤510。
步骤510，对第一类型终端配置独立的调度参数和/或传输资源参数。
可选地，在进行广播PDSCH传输时，对不同终端的广播PDSCH进行分别调度。可选地，广播PDSCH承载有如下至少一种信息：RAR；寻呼消息。
在一个可选的实施例中，以第一类型终端实现为eRedCap终端为例进行说明。
示意性的，在对广播PDSCH进行单独调度时，相较于legacy终端，网络设备为eRedCap终端配置独立的调度参数和/或传输资源参数。例如：eRedCap终端对应的广播PDSCH为第一广播PDSCH，在对承载有RAR的第一广播PDSCH进行单独调度时，为eRedCap终端配置独立的调度参数和/或传输资源参数；或者，在对承载有寻呼消息的第一广播PDSCH进行单独调度时，为eRedCap终端配置独立的调度参数和/或传输资源参数等。
可选地，独立的调度参数和/或传输资源参数用于指示该调度参数和/或传输资源参数是为第一类型终端所单独发送的。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
示意性的，为使得legacy终端尽量减少不属于自身的下行控制信息 (Downlink Control Information，DCI)和/或PDSCH的读取；和/或，使得eRedCap终端尽量减少不属于调度自身的DCI的读取。
在一个可选的实施例中，通过对eRedCap终端配置独立的调度参数和/或传输资源参数，对广播PDSCH进行单独调度。
可选地，以广播PDSCH中承载的信息实现为RAR为例，在需要对广播PDSCH进行单独调度时，通过为eRedCap终端分配独立的传输资源参数，实现对广播PDSCH进行单独调度的过程。例如：eRedCap终端对应的广播PDSCH为第一广播PDSCH，第一广播PDSCH中承载的信息实现为RAR，在需要对第一广播PDSCH进行单独调度时，通过为eRedCap终端分配独立的传输资源参数，实现对第一广播PDSCH进行单独调度的过程。
可选地，以广播PDSCH中承载的信息实现为寻呼消息为例，在需要对广播PDSCH进行单独调度时，通过为eRedCap终端分配独立的传输资源参数，实现对广播PDSCH进行单独调度的过程。例如：eRedCap终端对应的广播PDSCH为第一广播PDSCH，第一广播PDSCH中承载的信息实现为寻呼消息，在需要对第一广播PDSCH进行单独调度时，通过为eRedCap终端分配独立的传输资源参数，实现对第一广播PDSCH进行单独调度的过程。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
在一个可选的实施例中，独立的调度参数和/或传输资源参数包括如下至少一种：
部分带宽BWP；控制资源组CORESET；公共搜索空间CSS；寻呼无线网临时标识P-RNTI；系统信息无线网临时标识SI-RNTI；随机接入无线网临时标识RA-RNTI；解调参考信号DMRS序列或模式；下行控制信息DCI长度；使用DCI中的保留位指示。
可选地，当对广播信道分配独立的传输资源参数实现为BWP时，使用独立的BWP向eRedCap终端进行物理下行控制信道PDCCH与物理下行共享信道PDSCH的发送。
可选地，当对广播信道分配独立的传输资源参数实现为CORESET时，使用独立的CORESET向eRedCap终端进行调度广播PDSCH的DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为CSS时，使用独立的CSS向eRedCap终端进行调度广播PDSCH的DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为P-RNTI时，使用独立的P-RNTI向eRedCap终端进行承载寻呼消息的PDSCH与调度DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为SI-RNTI时，使用独立的SI-RNTI向eRedCap终端进行承载系统消息的PDSCH与调度DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为RA-RNTI时，使用独立的RA-RNTI向eRedCap终端进行承载RAR消息的PDSCH与调度DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为DMRS序列或模式时，使用独立的DMRS序列，或者DMRS pattern向eRedCap终端进行PDCCH和/或PDSCH的发送。
可选地，当对广播信道分配独立的传输资源参数实现为DCI长度时，使用独立的DCI长度向eRedCap终端进行调度广播PDSCH的DCI的发送。
可选地，当对广播信道分配独立的传输资源参数实现为DCI中使用保留位的指标时，基于DCI中的保留比特位的指示，指示eRedCap终端是否接收PDSCH。示意性的，根据DCI中的保留比特位的指示，确定是否发送PDSCH。例如：当DCI中保留比特位的指示为1，不向eRedCap终端发送进行相应的PDSCH等。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，在向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
示意性的，请参考图6，本公开一个示例性实施例提供的调度方法的流程图，以第一类型终端实现为eRedCap终端为例进行说明，如图6所示，该方法包括如下步骤610。
步骤610，接收网络设备发送的广播PDSCH。
其中，广播PDSCH是由网络设备单独调度的信道。
示意性的，广播PDSCH承载有如下至少一种信息：RAR；寻呼消息。
可选地，在对eRedCap终端的广播PDSCH进行传输时，对承载有不同信息 的广播PDSCH分别调度。例如：以广播PDSCH承载有RAR和寻呼消息为例进行说明。
在对eRedCap终端的广播PDSCH进行传输时，对承载有RAR的广播PDSCH进行单独调度，对承载有寻呼消息的广播PDSCH进行单独调度。
在一个可选的实施例中，网络设备还用于在对非eRedCap终端的第二广播PDSCH进行传输时，对第二广播PDSCH进行单独调度。
示意性的，网络设备不仅能够对第一广播PDSCH进行单独调度，例如：对承载有RAR的第一广播PDSCH进行单独调度，对承载有寻呼消息的第一广播PDSCH进行调度；还能够对第二广播PDSCH进行单独调度，例如：对承载有RAR的第二广播PDSCH进行单独调度，对承载有寻呼消息的第二广播PDSCH进行调度。
在一个可选的实施例中，发送第一指示信息。
其中，第一指示信息用于向网络设备指示第一类型终端的设备类型和/或终端的信道带宽。
可选地，向网络设备发送PRACH，PRACH中包括第一指示信息。
示意性的，第一指示信息包括提前指示信息，提前指示信息用于向网络设备指示eRedCap终端的设备类型。
示意性的，eRedCap终端向网络设备发送PRACH后，网络设备对PRACH中的提前指示信息进行读取，以便于网络设备基于该提前指示信息，向确定终端的设备类型。例如：确定eRedCap终端的设备类型。
可选地，eRedCap终端向网络设备发送终端类型信息。
示意性的，终端类型信息通过MSG1显式或隐式的方式指示；或者，终端类型信息通过消息A的PUSCH承载等。
可选地，终端类型信息中包括eRedCap终端的设备类型。也即：eRedCap终端向网络设备发送终端类型指示信息，以便网络设备根据终端类型信息确定eRedCap终端的设备类型。
在一个可选的实施例中，承载有寻呼消息的广播PDSCH由网络设备单独调度。
在一个可选的实施例中，响应于网络设备对广播PDSCH进行单独调度时，接收为eRedCap终端配置独立的调度参数和/或传输资源参数。
示意性的，为使得legacy终端尽量减少不属于自身的下行控制信息(Downlink Control Information，DCI)和/或PDSCH的读取；和/或，使得eRedCap终端尽量减少不属于调度自身的DCI的读取，为eRedCap终端配置独立的调度参数和/或传输资源参数。
在一个可选的实施例中，独立的调度参数和/或传输资源参数包括如下至少一种：
部分带宽BWP；控制资源组CORESET；公共搜索空间CSS；寻呼无线网临时标识P-RNTI；系统信息无线网临时标识SI-RNTI；随机接入无线网临时标识RA-RNTI；解调参考信号DMRS序列或模式；下行控制信息DCI长度；使用DCI中的保留位指示。
可选地，当对广播信道分配独立的传输资源参数实现为BWP时，使用独立的BWP向eRedCap终端进行物理下行控制信道PDCCH与物理下行共享信道PDSCH的接收。
可选地，当对广播信道分配独立的传输资源参数实现为CORESET时，使用独立的CORESET向eRedCap终端进行调度广播PDSCH的DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为CSS时，使用独立的CSS向eRedCap终端进行调度广播PDSCH的DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为P-RNTI时，使用独立的P-RNTI向eRedCap终端进行承载寻呼消息的PDSCH与调度DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为SI-RNTI时，使用独立的SI-RNTI向eRedCap终端进行承载系统消息的PDSCH与调度DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为RA-RNTI时，使用独立的RA-RNTI向eRedCap终端进行承载RAR消息的PDSCH与调度DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为DMRS序列或模式时，使用独立的DMRS序列，或者DMRS pattern向eRedCap终端进行PDCCH和/或PDSCH的接收。
可选地，当对广播信道分配独立的传输资源参数实现为DCI长度时，使用独立的DCI长度进行调度广播PDSCH的DCI的接收。
可选地，当对广播信道分配独立的传输资源参数实现为DCI中使用保留位的指标时，基于DCI中的保留比特位的指示，确定是否接收PDSCH。例如：当DCI中保留比特位的指示为1，不向eRedCap终端接收进行相应的PDSCH。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
示意性的，请参考图7，为本公开一个示例性实施例提供的调度方法流程图，以将该方法应用于eRedCap终端和网络设备之间的交互过程为例进行说明，如图7所示，该方法包括如下步骤710至步骤720。
步骤710，向第一类型终端单独调度广播物理下行共享信道PDSCH。
可选地，以第一类型终端实现为eRedCap终端为例进行如下说明。
其中，eRedCap终端为增强性增强降低能力的终端，也即：eRedCap终端表示为enhanced Reduced Capability UE。示意性的，增强降低能力用于指示增强对终端能力的降低。示意性的，eRedCap终端为RedCap终端，相较普通终端，eRedCap终端的终端能力有所降低。
可选地，广播PDSCH承载有如下至少一种信息：随机接入响应RAR；寻呼消息。示意性的，在对eRedCap终端的广播PDSCH进行传输时，对承载有不同信息的广播PDSCH进行分别调度。
可选地，eRedCap终端对应第一广播PDSCH；非eRedCap终端对应的第二广播PDSCH。在对广播PDSCH进行单独调度时，对eRedCap终端对应的第一广播PDSCH进行单独调度；和/或，对非eRedCap终端对应的第二广播PDSCH进行单独调度。示意性的，非eRedCap终端即为legacy终端。
可选地，在对eRedCap终端的广播PDSCH进行传输时，对承载有不同信息的广播PDSCH进行分别调度。示意性的，当广播PDSCH承载有RAR时，对承载有RAR的广播PDSCH进行单独调度；当广播PDSCH承载有寻呼消息时，对承载有RAR的广播PDSCH进行单独调度。
示意性的，根据承载信息的差异，对不同终端分别对应的广播PDSCH进行 单独调度的过程可以实现为如下形式中的一种：
1、根据承载信息的差异，对eRedCap终端对应的第一广播PDSCH进行单 独调度。
示意性的，当eRedCap终端的广播PDSCH(即：与eRedCap终端对应的第一广播PDSCH)承载有RAR时，网络设备对承载有RAR的第一广播PDSCH进行单独调度。
或者，当与eRedCap终端对应的第一广播PDSCH承载有寻呼消息时，网络设备对承载有寻呼消息的第一广播PDSCH进行单独调度。
或者，当与eRedCap终端对应的第一广播PDSCH承载有RAR和寻呼消息时，网络设备对承载有RAR的第一广播PDSCH进行单独调度，对承载有寻呼消息的第一广播PDSCH进行单独调度。
2、根据承载信息的差异，对非eRedCap终端对应的第二广播PDSCH进行 单独调度。
示意性的，当非eRedCap终端的广播PDSCH(即：与非eRedCap终端对应的第二广播PDSCH)承载有RAR时，网络设备对承载有RAR的第二广播PDSCH进行单独调度。
或者，当与非eRedCap终端对应的第二广播PDSCH承载有寻呼消息时，网络设备对承载有寻呼消息的第二广播PDSCH进行单独调度。
或者，当与非eRedCap终端对应的第二广播PDSCH承载有RAR和寻呼消息时，网络设备对承载有RAR的第二广播PDSCH进行单独调度，对承载有寻呼消息的第二广播PDSCH进行单独调度。
3、根据承载信息的差异，对eRedCap终端和非eRedCap终端分别对应的广 播PDSCH进行单独调度。
(1)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应的第二广播PDSCH各自承载有对应的RAR时，如：与eRedCap终端对应的第一广播PDSCH承载有第一RAR，与非eRedCap终端对应的第二广播PDSCH承载有第二RAR。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，网络设备对承载有第一RAR的第一广播PDSCH进行单独调度，对承载有第二RAR的第二广播PDSCH进行单独调度。
(2)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应 的第二广播PDSCH各自承载有对应的寻呼消息时，如：与eRedCap终端对应的第一广播PDSCH承载有第一寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有第二寻呼消息网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有第一寻呼消息的第一广播PDSCH进行单独调度，对承载有第二寻呼消息的第二广播PDSCH进行单独调度。
(3)当与eRedCap终端对应的第一广播PDSCH承载有RAR，与非eRedCap终端对应的第二广播PDSCH承载有寻呼消息时。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有RAR的第一广播PDSCH进行单独调度，对承载有寻呼消息的第二广播PDSCH进行单独调度。
(4)当与eRedCap终端对应的第一广播PDSCH承载有寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有RAR时。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有寻呼消息的第一广播PDSCH进行单独调度，对承载有RAR的第二广播PDSCH进行单独调度。
(5)当与eRedCap终端对应的第一广播PDSCH和与非eRedCap终端对应的第二广播PDSCH各自承载有对应的RAR和寻呼消息时，如：与eRedCap终端对应的第一广播PDSCH承载有第一RAR和第一寻呼消息，与非eRedCap终端对应的第二广播PDSCH承载有第二RAR和第二寻呼消息。网络设备在对承载有不同信息的广播PDSCH进行分别调度时，对承载有第一RAR的第一广播PDSCH进行单独调度，对承载有第一寻呼消息的第一广播PDSCH进行单独调度；对承载有第二RAR的第二广播PDSCH进行单独调度，对承载有第二寻呼消息的第二广播PDSCH进行单独调度。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
示意性的，网络设备向eRedCap终端发送广播PDSCH。
步骤720，接收网络设备发送的广播PDSCH。
其中，广播PDSCH是由网络设备单独调度的信道。也即：网络设备在对eRedCap终端的第一广播PDSCH进行传输时，对第一广播PDSCH进行单独调度。
示意性的，第一广播PDSCH承载有如下至少一种信息：RAR；寻呼消息。
可选地，响应于网络设备对承载RAR的广播PDSCH进行单独调度，向网络设备发送PRACH，PRACH中包括提前指示信息，提前指示信息用于向网络 设备指示eRedCap终端的设备类型。
可选地，响应于网络设备对承载寻呼消息的广播PDSCH中的寻呼消息进行单独调度，接收网络设备发送的寻呼消息。
可选地，响应于网络设备对广播PDSCH进行单独调度时，接收网络设备配置的独立的调度参数和/或传输资源参数。
步骤720已在上述步骤610中进行的说明，此处不再赘述。
值得注意的是，以上仅为示意性的举例，本申请实施例对此不加以限定。
综上所述，eRedCap终端接收网络设备对eRedCap终端的广播PDSCH进行单独调度后下发的广播PDSCH，基于网络设备对广播PDSCH进行单独调度的过程，使得在legacy终端和eRedCap终端共存的网络中，既能够提高eRedCap终端的接收准确率，也能够尽量避免对legacy终端的调度造成影响。
图8是本公开一个示例性实施例提供的调度装置的结构框图，该调度装置应用于网络设备，如图8所示，该装置包括：
调度模块810，用于向第一类型终端单独调度广播物理下行共享信道PDSCH。
在一个可选的实施例中，所述广播PDSCH承载有随机接入响应RAR；
所述调度模块810还用于对承载RAR的广播PDSCH进行单独调度。
在一个可选的实施例中，所述装置还包括：
接收模块820，用于接收第一指示信息，所述第一指示信息用于向所述网络设备指示所述第一类型终端的设备类型和/或终端的信道带宽。
在一个可选的实施例中，所述接收模块820还用于：
接收物理随机接入信道PRACH，所述PRACH上承载有所述第一指示信息。
在一个可选的实施例中，所述广播PDSCH承载有寻呼消息；
所述调度模块810还用于对承载寻呼消息的广播PDSCH进行单独调度。
在一个可选的实施例中，所述接收模块820还用于：
接收第二指示信息，所述第二指示信息用于指示终端的设备类型和/或终端的信道带宽。
在一个可选的实施例中，所述接收模块820还用于：
接收无线资源控制RRC信令，所述RRC信令上承载有所述第二指示信息。
在一个可选的实施例中，所述RRC信令用于指示如下信息中的至少一种：
所述第一类型终端对应的信道带宽；
所述第一类型终端对应的数据信道带宽；
所述第一类型终端对应的PDSCH信道带宽。
在一个可选的实施例中，所述装置还包括：
配置模块830，用于对所述第一类型终端配置独立的调度参数和/或传输资源参数。
在一个可选的实施例中，所述独立的调度参数和/或传输资源参数包括如下至少一种：
部分带宽BWP；
控制资源组CORESET；
公共搜索空间CSS；
寻呼无线网临时标识P-RNTI；
系统信息无线网临时标识SI-RNTI；
随机接入无线网临时标识RA-RNTI；
解调参考信号DMRS序列或模式；
下行控制信息DCI长度；
使用DCI中的保留位指示。
在一个可选的实施例中，所述配置模块830还用于：
使用独立的BWP向所述第一类型终端进行物理下行控制信道PDCCH与物理下行共享信道PDSCH的发送；和/或，
使用独立的CORESET向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
使用独立的CSS向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
使用独立的P-RNTI向所述第一类型终端进行承载寻呼消息的PDSCH与调度DCI的发送；和/或，
使用独立的SI-RNTI向所述第一类型终端进行承载系统消息的PDSCH与调度DCI的发送；和/或，
使用独立的RA-RNTI向所述第一类型终端进行承载RAR消息的PDSCH 与调度DCI的发送；和/或，
使用独立的DMRS序列，或者DMRS pattern向所述第一类型终端进行PDCCH和/或PDSCH的发送；和/或，
使用独立的DCI长度向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
基于DCI中的保留比特位的指示，指示所述第一类型终端是否接收PDSCH。
在一个可选的实施例中，所述调度模块810，还用于：
对所述第一类型终端对应的第一广播PDSCH进行单独调度；和/或，
对第二类型终端对应的第二广播PDSCH进行单独调度。
在一个可选的实施例中，所述第一类型终端包括增强降低能力eRedCap终端；所述第二类型终端包括普通legacy终端。
图9是本公开一个示例性实施例提供的调度装置的结构框图，该调度装置应用于第一类型终端，如图9所示，该装置包括：
接收模块910，用于接收网络设备发送的广播PDSCH，所述广播PDSCH是由所述网络设备单独调度的信道。
在一个可选的实施例中，所述装置还用于：
发送模块920，用于发送第一指示信息，所述第一指示信息用于向所述网络设备指示所述第一类型终端的设备类型和/或终端的信道带宽。
在一个可选的实施例中，所述发送模块920还用于：
向所述网络设备发送PRACH，所述PRACH中包括第一指示信息。
在一个可选的实施例中，所述广播PDSCH承载有寻呼消息；
承载有所述寻呼消息的广播PDSCH由所述网络设备单独调度。
在一个可选的实施例中，所述接收模块910还用于：
接收所述网络设备配置的独立的调度参数和/或传输资源参数。
在一个可选的实施例中，所述独立的调度参数和/或传输资源参数包括如下至少一种：
部分带宽BWP；
控制资源组CORESET；
公共搜索空间CSS；
寻呼无线网临时标识P-RNTI；
系统信息无线网临时标识SI-RNTI；
随机接入无线网临时标识RA-RNTI；
解调参考信号DMRS序列或模式；
下行控制信息DCI长度；
使用DCI中的保留位指示。
在一个可选的实施例中，所述接收模块910还用于：
使用独立的BWP进行PDCCH与PDSCH的接收；和/或，
使用独立的CORESET进行调度广播PDSCH的DCI的接收；和/或，
使用独立的CSS进行调度广播PDSCH的DCI的接收；和/或，
使用独立的P-RNTI进行承载寻呼消息的PDSCH与调度DCI的接收；和/或，
使用独立的SI-RNTI进行承载系统消息的PDSCH与调度DCI的接收；和/或，
使用独立的RA-RNTI进行承载RAR消息的PDSCH与调度DCI的接收；和/或，
使用独立的DMRS序列，或者DMRS pattern进行PDCCH和/或PDSCH的接收；和/或，
使用独立的DCI长度进行调度广播PDSCH的DCI的接收；和/或，
基于DCI中的保留比特位的指示，确定是否接收PDSCH。
综上所述，向第一类型终端单独调度广播PDSCH，以使得在不同类型终端共存的网络中，对不同终端对应的广播PDSCH进行单独调度，从而在对第一类型终端对应的广播PDSCH进行调度时，能够尽量避免对其他类型终端的调度造成影响。
需要说明的是：上述实施例提供的调度装置，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的调度装置与调度方法实施例属于同一构思，其 具体实现过程详见方法实施例，这里不再赘述。
图10示出了本公开一个示例性实施例提供的通信设备1000(终端或网络设备)的结构示意图，该终端包括：处理器1001、接收器1002、发射器1003、存储器1004和总线1005。
处理器1001包括一个或者一个以上处理核心，处理器1001通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器1002和发射器1003可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器1004通过总线1005与处理器1001相连。
存储器1004可用于存储至少一个指令，处理器1001用于执行该至少一个指令，以实现上述方法实施例中的各个步骤。
此外，存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(Erasable Programmable Read Only Memory,EEPROM)，可擦除可编程只读存储器(Erasable Programmable Read Only Memory,EPROM)，静态随时存取存储器(Static Random Access Memory，SRAM)，只读存储器(Read-Only Memory,ROM)，磁存储器，快闪存储器，可编程只读存储器(Programmable Read-Only Memory，PROM)。
一种非临时性计算机可读存储介质，当所述非临时性计算机存储介质中的指令由终端的处理器执行时，使得终端能够执行上述调度方法。
本公开一示例性实施例还提供了一种调度系统，所述系统包括：终端和网络设备；
所述网络设备包括如图8所示实施例提供的调度装置。
所述终端包括如图9所示实施例提供的调度装置；
本公开一示例性实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有至少一条指令、至少一段程序、代码集或指令集，所述至少一条指令、所述至少一段程序、所述代码集或指令集由所述处理器执行以实现上 述各个方法实施例提供的调度方法中由终端执行的步骤。
应当理解的是，在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (25)

  1. 一种调度方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    向第一类型终端单独调度广播物理下行共享信道PDSCH。
  2. 根据权利要求1所述的方法，其特征在于，所述广播PDSCH承载有随机接入响应RAR；
    所述方法还包括：
    对承载RAR的广播PDSCH进行单独调度。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    接收第一指示信息，所述第一指示信息用于向所述网络设备指示所述第一类型终端的设备类型和/或终端的信道带宽。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    接收物理随机接入信道PRACH，所述PRACH上承载有所述第一指示信息。
  5. 根据权利要求1所述的方法，其特征在于，所述广播PDSCH承载有寻呼消息；
    所述方法还包括：
    对承载寻呼消息的广播PDSCH进行单独调度。
  6. 根据权利要求5所述的方法，其特征在于，所述方法还包括：
    接收第二指示信息，所述第二指示信息用于指示终端的设备类型和/或终端的信道带宽。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    接收无线资源控制RRC信令，所述RRC信令上承载有所述第二指示信息。
  8. 根据权利要求7所述的方法，其特征在于，所述RRC信令用于指示如下 信息中的至少一种：
    所述第一类型终端对应的信道带宽；
    所述第一类型终端对应的数据信道带宽；
    所述第一类型终端对应的PDSCH信道带宽。
  9. 根据权利要求1至8任一所述的方法，其特征在于，所述方法还包括：
    对所述第一类型终端配置独立的调度参数和/或传输资源参数。
  10. 根据权利要求9所述的方法，其特征在于，所述独立的调度参数和/或传输资源参数包括如下至少一种：
    部分带宽BWP；
    控制资源组CORESET；
    公共搜索空间CSS；
    寻呼无线网临时标识P-RNTI；
    系统信息无线网临时标识SI-RNTI；
    随机接入无线网临时标识RA-RNTI；
    解调参考信号DMRS序列或模式；
    下行控制信息DCI长度；
    使用DCI中的保留位指示。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    使用独立的BWP向所述第一类型终端进行物理下行控制信道PDCCH与物理下行共享信道PDSCH的发送；和/或，
    使用独立的CORESET向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
    使用独立的CSS向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
    使用独立的P-RNTI向所述第一类型终端进行承载寻呼消息的PDSCH与调度DCI的发送；和/或，
    使用独立的SI-RNTI向所述第一类型终端进行承载系统消息的PDSCH与 调度DCI的发送；和/或，
    使用独立的RA-RNTI向所述第一类型终端进行承载RAR消息的PDSCH与调度DCI的发送；和/或，
    使用独立的DMRS序列，或者DMRS pattern向所述第一类型终端进行PDCCH和/或PDSCH的发送；和/或，
    使用独立的DCI长度向所述第一类型终端进行调度广播PDSCH的DCI的发送；和/或，
    基于DCI中的保留比特位的指示，指示所述第一类型终端是否接收PDSCH。
  12. 根据权利要求1至8任一所述的方法，其特征在于，所述方法还包括：
    对所述第一类型终端对应的第一广播PDSCH进行单独调度；和/或，
    对第二类型终端对应的第二广播PDSCH进行单独调度。
  13. 根据权利要求12所述的方法，其特征在于，
    所述第一类型终端包括增强降低能力eRedCap终端；
    所述第二类型终端包括普通legacy终端。
  14. 一种调度方法，其特征在于，所述方法由第一类型终端执行，所述方法包括：
    接收网络设备发送的广播PDSCH，所述广播PDSCH是由所述网络设备单独调度的信道。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    发送第一指示信息，所述第一指示信息用于向所述网络设备指示所述第一类型终端的设备类型和/或终端的信道带宽。
  16. 根据权利要求15所述的方法，其特征在于，所述方法还包括：
    向所述网络设备发送PRACH，所述PRACH中包括第一指示信息。
  17. 根据权利要求14所述的方法，其特征在于，所述广播PDSCH承载有寻 呼消息；
    承载有所述寻呼消息的广播PDSCH由所述网络设备单独调度。
  18. 根据权利要求14至17任一所述的方法，其特征在于，所述方法还包括：
    接收所述网络设备配置的独立的调度参数和/或传输资源参数。
  19. 根据权利要求18所述的方法，其特征在于，所述独立的调度参数和/或传输资源参数包括如下至少一种：
    部分带宽BWP；
    控制资源组CORESET；
    公共搜索空间CSS；
    寻呼无线网临时标识P-RNTI；
    系统信息无线网临时标识SI-RNTI；
    随机接入无线网临时标识RA-RNTI；
    解调参考信号DMRS序列或模式；
    下行控制信息DCI长度；
    使用DCI中的保留位指示。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    使用独立的BWP进行PDCCH与PDSCH的接收；和/或，
    使用独立的CORESET进行调度广播PDSCH的DCI的接收；和/或，
    使用独立的CSS进行调度广播PDSCH的DCI的接收；和/或，
    使用独立的P-RNTI进行承载寻呼消息的PDSCH与调度DCI的接收；和/或，
    使用独立的SI-RNTI进行承载系统消息的PDSCH与调度DCI的接收；和/或，
    使用独立的RA-RNTI进行承载RAR消息的PDSCH与调度DCI的接收；和/或，
    使用独立的DMRS序列，或者DMRS pattern进行PDCCH和/或PDSCH的接收；和/或，
    使用独立的DCI长度进行调度广播PDSCH的DCI的接收；和/或，
    基于DCI中的保留比特位的指示，确定是否接收PDSCH。
  21. 一种调度装置，其特征在于，应用于网络设备，所述装置包括：
    调度模块，用于向第一类型终端单独调度广播物理下行共享信道PDSCH。
  22. 一种调度装置，其特征在于，应用于第一类型终端，所述装置包括：
    接收模块，用于接收网络设备发送的广播PDSCH，所述广播PDSCH是由所述网络设备单独调度的信道。
  23. 一种网络设备，其特征在于，所述网络设备包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为执行可执行指令以实现如权利要求1至13任一所述的调度方法。
  24. 一种终端，其特征在于，所述终端包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为执行可执行指令以实现如权利要求14至20任一所述的调度方法。
  25. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有至少一条指令，所述至少一条指令由处理器执行以实现如权利要求1至20任一所述的调度方法。
PCT/CN2022/122757 2022-09-29 2022-09-29 调度方法、装置、设备及可读存储介质 WO2024065432A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280003815.8A CN116097866A (zh) 2022-09-29 2022-09-29 调度方法、装置、设备及可读存储介质
PCT/CN2022/122757 WO2024065432A1 (zh) 2022-09-29 2022-09-29 调度方法、装置、设备及可读存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/122757 WO2024065432A1 (zh) 2022-09-29 2022-09-29 调度方法、装置、设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2024065432A1 true WO2024065432A1 (zh) 2024-04-04

Family

ID=86201126

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/122757 WO2024065432A1 (zh) 2022-09-29 2022-09-29 调度方法、装置、设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN116097866A (zh)
WO (1) WO2024065432A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020235884A1 (en) * 2019-05-17 2020-11-26 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in a wireless communication system
CN113473632A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 物理下行共享信道的调度方法、网络设备及终端设备
CN113518413A (zh) * 2020-04-10 2021-10-19 华为技术有限公司 一种通信方法、装置及系统
CN113766659A (zh) * 2020-06-04 2021-12-07 华为技术有限公司 随机接入的方法、装置和系统
CN114982317A (zh) * 2020-02-10 2022-08-30 华为技术有限公司 一种寻呼方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020235884A1 (en) * 2019-05-17 2020-11-26 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in a wireless communication system
CN114982317A (zh) * 2020-02-10 2022-08-30 华为技术有限公司 一种寻呼方法及装置
CN113473632A (zh) * 2020-03-31 2021-10-01 维沃移动通信有限公司 物理下行共享信道的调度方法、网络设备及终端设备
CN113518413A (zh) * 2020-04-10 2021-10-19 华为技术有限公司 一种通信方法、装置及系统
CN113766659A (zh) * 2020-06-04 2021-12-07 华为技术有限公司 随机接入的方法、装置和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE: "Views on one DCI scheduling multiple PDSCHs on multiple carriers", 3GPP TSG RAN MEETING #91E, RP-210604, 15 March 2021 (2021-03-15), XP051985963 *

Also Published As

Publication number Publication date
CN116097866A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
US20220070918A1 (en) Communication Method And Device
RU2768363C2 (ru) Способ передачи данных и устройство
CN111357332B (zh) 跳过寻呼检测的方法、装置、终端及接入网设备
CN108418661B (zh) 数据传输方法及装置
CN111345075B (zh) 省电方法、装置、设备及可读存储介质
CN114827987A (zh) 资源分配方法、第一设备及第二设备
EP3412060B1 (en) Devices and method for flexible user equipment identification
CN113840241A (zh) 一种通信方法及通信装置
WO2021243655A1 (zh) 信息配置方法、装置、设备及可读存储介质
CN111586667A (zh) 通信方法及终端设备、核心网设备
CN111436031A (zh) V2x的通信方法及装置、存储介质和电子装置
CN116508367A (zh) 用于小数据传输或接收的方法及装置
CN111586852B (zh) 一种通信方法及装置
EP3949574A1 (en) Paging and multi-identity module wireless communication devices
EP3836659A1 (en) Information transmission method, communication device and network device
US20220287004A1 (en) Communication control method and user equipment
WO2024065432A1 (zh) 调度方法、装置、设备及可读存储介质
WO2023015507A1 (zh) 省电方法、装置、设备及可读存储介质
US20220394775A1 (en) Method and apparatus for switching of data transmission between radio access technologies for early data transmission
CN116325818A (zh) 一种通信方法及装置
WO2024065434A1 (zh) 调度方法、装置、设备及可读存储介质
WO2022205365A1 (zh) 激活时间的确定方法、装置、设备及存储介质
WO2022224942A1 (ja) 端末、基地局及び通信方法
WO2022224941A1 (ja) 端末、基地局及び通信方法
US20230209534A1 (en) Communication control method

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: 22960069

Country of ref document: EP

Kind code of ref document: A1