Scheduling method, apparatus, device, and readable storage medium

Abstract

The present disclosure provides a scheduling method, device, equipment and readable storage medium, and relates to the field of communication. The method comprises: receiving a common physical downlink shared channel (PDSCH), and the receiving mode of the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of a first type terminal. The receiving mode of the common PDSCH can be determined based on the transmission resource parameters of the common PDSCH of the first type terminal, so that the first type terminal can differentially adjust the receiving mode of the common PDSCH after determining the transmission resource parameters of the common PDSCH. When the common PDSCH is used by ordinary terminals and the first type terminal, the terminal behavior of the first type terminal is clarified, and the accuracy of scheduling the first type terminal is improved.

Description

[0001] This application is a divisional application of the invention patent application filed on September 29, 2022, with application number 202280003823.2 and entitled "Scheduling Method, Apparatus, Device and Readable Storage Medium". Technical Field

[0002] This disclosure relates to the field of communications, and in particular to a scheduling method, apparatus, device, and readable storage medium. Background Technology

[0003] In 5G New Radio (NR), in order to meet the high speed and high latency requirements of mid-range IoT devices, a new type of terminal (User Equipment, UE) device has been designed. In the 3GPP standardization, this new terminal type is called RedCap (Reduced Capability) terminal, which includes the enhanced reduced capability eRedCap terminal.

[0004] In related technologies, eRedCap terminals and ordinary terminals share the same common information, such as system messages, paging messages, and random access responses. However, when the baseband processing bandwidth of the common channel or the transmission block size (TBS) used exceeds the terminal capability of the eRedCap terminal, there is no good solution to the problem of how the eRedCap terminal should handle this. Summary of the Invention

[0005] This disclosure provides a scheduling method, apparatus, device, and readable storage medium, enabling a first type of terminal (such as an eRedCap terminal) to differentially adjust its reception mode of the common PDSCH based on the transmission resource parameters of the common PDSCH after receiving the common PDSCH. The technical solution is as follows: According to one aspect of this disclosure, a scheduling method is provided, the method being executed by a first type of terminal, the method comprising: The common physical downlink shared channel (PDSCH) is received, and the method of receiving the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal.

[0006] On the other hand, a scheduling method is provided, the method being executed by an access network device, the method comprising: Configure transmission resource parameters for a common PDSCH on a first type of terminal, wherein the transmission resource parameters are used to indicate the receiving method of the common PDSCH.

[0007] On the other hand, a scheduling device is provided, which is applied to a terminal, and the device includes: The determination module is used to receive the common physical downlink shared channel (PDSCH), wherein the method of receiving the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal.

[0008] On the other hand, a scheduling device is provided, which is applied to an access network device, and the device includes: A configuration module is used to configure the transmission resource parameters of the common PDSCH for the first type of terminal, wherein the transmission resource parameters are used to indicate the reception method of the common PDSCH.

[0009] On the other hand, a terminal is provided, the terminal comprising: processor; A transceiver connected to the processor; The processor is configured to execute executable instructions to implement the scheduling method as described in the embodiments of this disclosure above.

[0010] On the other hand, an access network device is provided, the network device comprising: processor; A transceiver connected to the processor; The processor is configured to execute executable instructions to implement the scheduling method as described in the embodiments of this disclosure above.

[0011] On the other hand, a computer-readable storage medium is provided that stores at least one instruction, at least one program, code set, or instruction set, wherein 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 embodiments of this disclosure above.

[0012] The beneficial effects of the technical solutions provided in this disclosure include at least the following: The reception method of the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal. This allows the first type of terminal to adjust its reception method of the common PDSCH differently after determining the transmission resource parameters of the common PDSCH. When ordinary terminals and first type terminals use the common PDSCH, the terminal behavior of the first type of terminal is clarified, and the accuracy of scheduling of the first type of terminal is improved. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is an architectural block diagram of the communication system provided in the embodiments of this disclosure; Figure 2 This is a flowchart of a terminal-side scheduling method provided in an exemplary embodiment of this disclosure; Figure 3 This is a flowchart of a terminal-side scheduling method provided in another exemplary embodiment of this disclosure; Figure 4 This is a flowchart of a terminal-side scheduling method provided in another exemplary embodiment of the present disclosure; Figure 5 This is a flowchart of a terminal-side scheduling method provided in yet another exemplary embodiment of this disclosure; Figure 6 This disclosure also provides a flowchart of a terminal-side scheduling method according to an exemplary embodiment; Figure 7 This is a flowchart of a scheduling method on the access network device side provided in an exemplary embodiment of this disclosure; Figure 8 This is a flowchart of a scheduling method on the access network device side provided in another exemplary embodiment of this disclosure; Figure 9 This is a flowchart of a scheduling method on the access network device side provided in another exemplary embodiment of the present disclosure; Figure 10 This is a flowchart of a scheduling method on the access network device side provided in yet another exemplary embodiment of this disclosure; Figure 11 This is a flowchart of a scheduling method for interaction between the access network device side and the terminal side provided in an exemplary embodiment of this disclosure; Figure 12 This is a schematic diagram of the structure of a scheduling device shown in an exemplary embodiment of the present disclosure; Figure 13 This is a schematic diagram of the structure of a scheduling device shown in another exemplary embodiment of this disclosure; Figure 14 This is a structural block diagram of a communication device illustrated in an exemplary embodiment of this disclosure. Detailed Implementation

[0015] To make the objectives, technical solutions, and advantages of this disclosure clearer, the embodiments of this disclosure will be described in further detail below with reference to the accompanying drawings.

[0016] In Long Term Evolution (LTE) 4G systems, Narrow Band Internet of Things (NB-IoT) and Machine Type Communication (MTC) technologies are typically used for communication in low-speed, high-latency scenarios in IoT services. NB-IoT typically supports speeds of only a few hundred kilobytes per second (Mbps), while MTC typically supports speeds of only a few megabytes per second (Mbps). However, with the continuous development of IoT services, such as video surveillance, smart homes, wearable devices, and industrial sensing and monitoring, these services often require speeds of tens to 100 megabytes per second (Mbps) and relatively high latency. Based on this, a new type of terminal device has been proposed in 5G New Radio (NR). In the 3rd Generation Partnership Project (3GPP) standardization, this new terminal type is called Reduced Capability UE (RedCap terminal), which includes eRedCap terminals.

[0017] In related technologies, Type I terminals (such as eRedCap terminals) and ordinary terminals share the same common information, such as system messages, paging messages, and random access responses. However, to reduce the complexity of Type I terminals, the baseband processing bandwidth of the Physical Downlink Shared Channel (PDSCH) received by Type I terminals is usually limited; or, the TBS of the PDSCH received by Type I terminals is limited. Therefore, there is a difference in processing capabilities between Type I terminals and ordinary terminals. Although Type I terminals and ordinary terminals share the same common channel, there is no good solution to the problem of how Type I terminals should handle situations where the baseband processing bandwidth of the common channel or the TBS used exceeds the terminal capability of Type I terminals.

[0018] Figure 1 A block diagram of a communication system provided in an illustrative embodiment of the present disclosure is shown. The communication system may include: a core network 11, an access network 12, and a terminal 13.

[0019] The core network 11 includes several core network devices 110. Core network devices 110 are deployed within the core network, and their main functions are to provide user connectivity, manage users, and bear services, serving as the interface to external networks. For example, core network devices in a 5G NR system may include Access and Mobility Management Function (AMF) network elements, User Plane Function (UPF) network elements, and Session Management Function (SMF) network elements. For instance, in this embodiment, core network device 30 may include a location management function network element. Optionally, the location management function network element includes a location server, which can be implemented as any of the following: LMF (Location Management Function), E-SMLC (Enhanced Serving Mobile Location Centre), SUPL (Secure User Plane Location), or SUPL SLP (Secure User Plane Location Platform).

[0020] Access network 12 includes a plurality of access network devices 120. Access network devices 120 may be base stations, which are devices deployed in the access network to provide wireless communication functions for terminals. Base stations may include various forms of macro base stations, micro base stations, relay stations, access points, or transmission reception points (TRPs), etc. In systems employing different wireless access technologies, the names of devices with base station functions may differ; for example, in LTE systems, they are called eNodeB or eNB; in 5G NR systems, they are called gNode B or gNB. As communication technologies evolve, the term "base station" may change. For convenience in this embodiment, the aforementioned devices providing wireless communication functions for terminals are collectively referred to as access network devices.

[0021] Terminal 13 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem, as well as various forms of terminals, such as mobile stations (MS) and terminal devices. For ease of description, the devices mentioned above are collectively referred to as terminals. In this embodiment, terminal 13 includes ordinary terminals and eRedCap terminals, wherein eRedCap terminals have the characteristics of lower complexity and lower power consumption compared to ordinary terminals. Access network device 120 and terminal 13 communicate with each other through some air interface technology, such as the Uu interface.

[0022] 5G-based industrial sensors, video surveillance cameras, and wearable devices do not require such high bandwidth, especially industrial sensors, which only need a few megabits of bandwidth. These types of terminals may be classified as a new terminal type in subsequent 5G enhancements and will undergo corresponding technical feature improvements. That is, the eRedCap terminal provided in this application is an enhanced version of the aforementioned ordinary terminal, enabling it to better adapt to low-latency and high-speed scenarios. The eRedCap terminal can also be simply referred to as an NR-lite (lightweight) terminal. Similar to IoT devices in LTE, this type of device needs to meet the following requirements: 1. Low cost and low complexity; 2. Enhanced coverage to a certain extent; 3. Saves power.

[0023] Optionally, during the wireless communication between the aforementioned terminal 13 and the access network device 120, wireless communication can be conducted via licensed frequency bands or unlicensed frequency bands.

[0024] This is illustrative; please refer to it. Figure 2 This disclosure provides a flowchart of a scheduling method according to an exemplary embodiment, using the application of the method to a first type of terminal as an example for illustration. Figure 2 As shown, the method includes the following step 210.

[0025] Step 210: Receive the common physical downlink shared channel (PDSCH).

[0026] The method of receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal.

[0027] Optionally, the first type of terminal includes an enhanced reduced capability (eRedCap) terminal. Here, eRedCap terminal is used to indicate a terminal with enhanced reduced capability; that is, an eRedCap terminal is represented as an enhanced Reduced Capability UE. Illustratively, enhanced reduced capability is used to indicate the reduction in terminal capability due to enhancement.

[0028] The implementation of the first type of terminal as an eRedCap terminal is merely an illustrative example, and the embodiments of this application do not limit it.

[0029] To illustrate, compared to ordinary terminals, eRedCap terminals have reduced terminal capabilities, typically in at least one of the following ways.

[0030] (1) Reduce the baseband processing bandwidth, for example: limit the frequency domain width of the PDSCH received by the eRedCap terminal to within 5MHz; (2) Limit the TBS of each PDSCH, for example: limit the maximum TBS of each PDSCH to within 10,000 bits.

[0031] In some alternative embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the first type of terminal and TBS.

[0032] Optionally, the first type of terminal receives transmission resource parameters sent by the access network device. Illustratively, the access network device transmits the allocated public PDSCH transmission resource parameters to the first type of terminal via the Physical Downlink Control Channel (PDCCH).

[0033] Optionally, the public PDSCH refers to the data transmission channel shared by ordinary terminals and Type 1 terminals; that is, the public PDSCH is a channel used by both ordinary terminals and Type 1 terminals.

[0034] Indicatively, when the first type of terminal is implemented as an eRedCap terminal, the common PDSCH refers to the data transmission channel shared by ordinary terminals and eRedCap terminals. In other words, the common PDSCH is a channel used by both ordinary terminals and eRedCap terminals.

[0035] In an optional embodiment, the method of receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

[0036] In an optional embodiment, the first type of terminal is implemented as an eRedCap terminal as an example. When determining the reception method of the public PDSCH based on the transmission resource parameters of the public PDSCH of the eRedCap terminal and the terminal capabilities corresponding to the eRedCap terminal, the transmission resource parameters of one or more public PDSCHs allocated to the eRedCap terminal are compared with the terminal capabilities corresponding to the eRedCap terminal to determine the reception method of the public PDSCH of the eRedCap terminal.

[0037] Optionally, the baseband processing bandwidth of the common PDSCH of the eRedCap terminal is used as an example to illustrate the process. When determining the terminal capabilities corresponding to the eRedCap terminal, the bandwidth processing capability of the eRedCap terminal is determined.

[0038] To illustrate, after determining the bandwidth processing capability of the eRedCap terminal, the baseband processing bandwidth of the public PDSCH is compared with the bandwidth processing capability of the eRedCap terminal, and the reception method of the public PDSCH is determined based on the comparison result of the baseband processing bandwidth and the bandwidth processing capability.

[0039] Optionally, the TBS of the common PDSCH of the eRedCap terminal, implemented with transmission resource parameters, is used as an example for explanation. When determining the terminal capabilities corresponding to the eRedCap terminal, the transmission block processing capability that the eRedCap terminal can receive or read is determined.

[0040] To illustrate, after determining the transport block processing capability corresponding to the eRedCap terminal, the TBS of the public PDSCH is compared with the transport block processing capability of the eRedCap terminal, and the reception method of the public PDSCH is determined based on the comparison result of TBS and transport block processing capability.

[0041] Optionally, the baseband processing bandwidth and TBS of the common PDSCH of the eRedCap terminal are used as an example for explanation. When determining the terminal capabilities corresponding to the eRedCap terminal, the bandwidth processing capability and transport block processing capability of the eRedCap terminal are determined. The baseband processing bandwidth and TBS of the common PDSCH are compared with the corresponding terminal capabilities. That is, the baseband processing bandwidth of the common PDSCH is compared with the bandwidth processing capability of the eRedCap terminal; the TBS of the common PDSCH is compared with the transport block processing capability of the eRedCap terminal. Based on the baseband comparison results and the transport block comparison results, the reception method for the common PDSCH is determined.

[0042] It is worth noting that the above description of the eRedCap terminal as the first type of terminal is merely an illustrative example, and the embodiments of this application do not limit this.

[0043] In summary, determining the reception method of the common PDSCH based on the transmission resource parameters of the common PDSCH of the first type of terminal enables the first type of terminal to adjust its reception method differently after determining the transmission resource parameters of the common PDSCH. When ordinary terminals and first type terminals use the common PDSCH, the terminal behavior of the first type of terminal is clarified, and the accuracy of scheduling of the first type of terminal is improved.

[0044] In this embodiment of the application, the comparison of terminal capabilities and transmission resource parameters for the first type of terminal (e.g., eRedCap terminal) includes at least one of the following processing methods: Method 1: When the transmission resource parameters exceed the processing capacity of the first type of terminal, the first type of terminal does not expect the PDSCH to contain its resource information. That is, the first type of terminal abandons processing the common PDSCH. For example, when the transmission resource parameters exceed the processing capacity of the first type of terminal, the eRedCap terminal does not expect the PDSCH to contain its resource information. That is, the eRedCap terminal abandons processing the common PDSCH. Method 2: When the transmission resource parameters exceed the processing capability of the Type 1 terminal, the common PDSCH may contain resource information of the Type 1 terminal. The Type 1 terminal reads the resource allocation range in the PDCCH, receives partial resource information according to its terminal capabilities, and attempts to demodulate resources within its capability range to recover the information. For example, when the transmission resource parameters exceed the processing capability of the eRedCap terminal, the common PDSCH may contain resource information of the eRedCap terminal. The eRedCap terminal reads the resource allocation range in the PDCCH, receives partial resource information according to its terminal capabilities, and attempts to demodulate resources within its capability range to recover the information. Method 3: Define a preset threshold, which can be higher or lower than the terminal's capability. When the transmission resource parameters exceed the preset threshold, the Type 1 terminal abandons processing subsequent common PDSCH. When the transmission resource parameters are lower than the preset threshold, the Type 1 terminal attempts to demodulate the common PDSCH. For example: Define a preset threshold, which can be higher or lower than the terminal's capability. When the transmission resource parameters exceed the preset threshold, the eRedCap terminal abandons processing subsequent common PDSCH. When the transmission resource parameters are lower than the preset threshold, the eRedCap terminal attempts to demodulate the common PDSCH.

[0045] The above methods will be described in detail.

[0046] Method 1: When the transmission resource parameters exceed the processing capacity of the first type of terminal, the first type of terminal abandons the processing of the common PDSCH.

[0047] Indicative, such as Figure 3 As shown, step 210 above can also be implemented as steps 310 to 322 below.

[0048] Step 310: Receive the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

[0049] This is illustrated using the example of a first-type terminal implemented as an eRedCap terminal.

[0050] Optionally, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the first type of terminal. For example, the access network device transmits the transmission resource parameters of the common PDSCH allocated to the first type of terminal via the PDCCH to the first type of terminal through the eRedCap. In other embodiments, the transmission resource parameters may also be parameters indicated by the core network device to the first type of terminal.

[0051] In some alternative embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the first type of terminal and TBS.

[0052] Indicatively, when a first-type terminal receives the transmission resource parameters of a common PDSCH, it receives the baseband processing bandwidth of the common PDSCH allocated to the first-type terminal; or, it receives the TBS of the common PDSCH allocated to the first-type terminal; or, it receives both the baseband processing bandwidth and the TBS of the common PDSCH allocated to the first-type terminal.

[0053] Step 321: If the transmission resource parameters of the public PDSCH exceed the range of the terminal capability corresponding to the first type of terminal, stop receiving the public PDSCH.

[0054] Among them, the terminal capabilities corresponding to the first type of terminal include the resource processing capability of the first type of terminal for PDSCH.

[0055] This is illustrated using the example of a first-type terminal implemented as an eRedCap terminal.

[0056] Optionally, the terminal capabilities corresponding to the eRedCap terminal are implemented as the terminal capabilities configured by the access network device for the eRedCap terminal; or, the terminal capabilities corresponding to the eRedCap terminal are implemented as the terminal capabilities configured by the eRedCap terminal itself, etc.

[0057] Optionally, if the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal exceed the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal cannot receive the public PDSCH.

[0058] Specifically, for different transmission resource parameters, the reception of the public PDSCH by the eRedCap terminal includes at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. As an illustration, when the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the bandwidth processing capacity of the eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0059] 2. The transmission resource parameters include TBS. When the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the transport block processing capacity of the corresponding eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0060] 3. The transmission resource parameters include baseband processing bandwidth and TBS. 3.1 When the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the bandwidth processing capacity of the corresponding eRedCap terminal, and the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the transport block processing capacity of the corresponding eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0061] 3.2 If the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the bandwidth processing capacity of the eRedCap terminal (i.e., does not exceed the bandwidth processing capacity of the eRedCap terminal), but the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the transport block processing capacity of the eRedCap terminal, the eRedCap terminal will stop receiving the public PDSCH.

[0062] 3.3 If the baseband bandwidth of the public PDSCH allocated to the eRedCap terminal is within the range of the transport block processing capability of the eRedCap terminal (i.e., does not exceed the transport block processing capability of the eRedCap terminal), but the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the bandwidth processing capability of the eRedCap terminal, the eRedCap terminal will stop receiving the public PDSCH.

[0063] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0064] Step 322: Receive the public PDSCH if the transmission resource parameters of the public PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal.

[0065] Optionally, when the transmission resource parameters of the public PDSCH allocated to the first type of terminal are within the terminal capability corresponding to the first type of terminal, the first type of terminal can receive the public PDSCH. For example, when the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are within the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive the public PDSCH.

[0066] This is illustrated using an example of a Type 1 terminal implemented as an eRedCap terminal. Specifically, for different transmission resource parameters, the eRedCap terminal's reception of the common PDSCH includes at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. To illustrate, when the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the bandwidth processing capability of the corresponding eRedCap terminal, the eRedCap terminal receives the public PDSCH.

[0067] 2. The transmission resource parameters include TBS. When the TBS of the public PDSCH allocated to the eRedCap terminal is within the transport block processing capacity of the corresponding eRedCap terminal, the eRedCap terminal will receive the public PDSCH.

[0068] 3. The transmission resource parameters include baseband processing bandwidth and TBS. When the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the bandwidth processing capacity of the corresponding eRedCap terminal, and the TBS of the public PDSCH allocated to the eRedCap terminal is within the transport block processing capacity of the corresponding eRedCap terminal, the eRedCap terminal receives the public PDSCH.

[0069] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0070] In this embodiment, the process of receiving a public PDSCH is described. After a first-type terminal receives the transmission resource parameters of the public PDSCH allocated to it, if the transmission resource parameters of the public PDSCH exceed the range of the terminal capability corresponding to the first-type terminal, it will stop receiving the public PDSCH; if the transmission resource parameters of the public PDSCH are within the range of the terminal capability corresponding to the first-type terminal, it will receive the public PDSCH. This differentiates the method of receiving the public PDSCH, clarifies the behavior of the first-type terminal, and improves the accuracy of scheduling the first-type terminal.

[0071] Method 2: When the transmission resource parameters exceed the processing capability of the first type of terminal, the first type of terminal reads the resource allocation range in the PDCCH and receives part of the resource information according to the terminal capability.

[0072] Indicative, such as Figure 4 As shown, step 210 above can also be implemented as steps 410 to 420 below.

[0073] Step 410: Receive the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

[0074] Optionally, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the first type of terminal. For example, the access network device transmits transmission resource parameters of the common PDSCH allocated to the first type of terminal to the first type of terminal via PDCCH. In other embodiments, the transmission resource parameters can also be parameters indicated by the core network device to the first type of terminal. For example, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the eRedCap terminal. For example, the access network device transmits transmission resource parameters of the common PDSCH allocated to the eRedCap terminal to the eRedCap terminal via PDCCH. In other embodiments, the transmission resource parameters can also be parameters configured by the core network device to the eRedCap terminal.

[0075] Optionally, the transmission resource parameters include at least one of the baseband processing bandwidth of the common PDSCH allocated to the first type of terminal and the TBS. For example, the transmission resource parameters include at least one of the baseband processing bandwidth of the common PDSCH allocated to the eRedCap terminal and the TBS.

[0076] Step 420: If the baseband processing bandwidth of the public PDSCH exceeds the range of the terminal capability corresponding to the first type of terminal, receive a portion of the public PDSCH resources on the baseband processing bandwidth based on the terminal capability.

[0077] The terminal capabilities corresponding to the first type of terminal represent the processing capabilities of the first type of terminal. Optionally, the terminal capabilities corresponding to the first type of terminal are implemented as the terminal capabilities configured by the access network device for the first type of terminal; or, the terminal capabilities corresponding to the first type of terminal implement the terminal capabilities configured by the first type of terminal itself, etc. For example, the terminal capabilities corresponding to the eRedCap terminal represent the processing capabilities of the eRedCap terminal. Optionally, the terminal capabilities corresponding to the eRedCap terminal are implemented as the terminal capabilities configured by the access network device for the eRedCap terminal; or, the terminal capabilities corresponding to the eRedCap terminal implement the terminal capabilities configured by the eRedCap terminal itself, etc.

[0078] In an optional embodiment, the first type of terminal is implemented as an eRedCap terminal as an example. After determining the terminal capabilities corresponding to the eRedCap terminal, the bandwidth processing capability corresponding to the eRedCap terminal is determined. Illustratively, when the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the terminal capability corresponding to the eRedCap terminal, a portion of the public PDSCH resources on the baseband processing bandwidth is received based on the terminal capability.

[0079] Among them, a portion of the public PDSCH resources are used to represent resource information transmitted on the baseband processing bandwidth and that can be received by the eRedCap terminal. Optionally, a portion of the public PDSCH resources is determined by the first type of terminal based on its own capabilities.

[0080] It should be noted that the resources transmitted on the baseband processing bandwidth can be implemented as resources within the terminal's capabilities or resources exceeding the terminal's capabilities. In other words, the resources transmitted on the baseband processing bandwidth can exceed the terminal's corresponding capabilities.

[0081] As an illustration, when the resources transmitted on the baseband processing bandwidth are within the terminal's capability range, the terminal receives these resources and uses them as part of the common PDSCH resources; when the resources transmitted on the baseband processing bandwidth are outside the terminal's capability range, the terminal determines from the resources transmitted on the baseband processing bandwidth a portion that is within its bandwidth processing capability range and uses it as part of the common PDSCH resources, etc. The above are merely illustrative examples, and the embodiments of this application do not limit this.

[0082] This illustration demonstrates the process of obtaining some public PDSCH resources.

[0083] In an optional embodiment, if the baseband processing bandwidth of the public PDSCH exceeds the capability range of the terminal corresponding to the first type of terminal, the resource allocation range corresponding to the first type of terminal on the public PDSCH is read from the physical downlink control channel PDCCH. The resource allocation range represents the resources transmitted on the baseband processing bandwidth.

[0084] For example: In response to the fact that the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the range of the terminal capability corresponding to the eRedCap terminal, the resource allocation range corresponding to the eRedCap terminal is read from the PDCCH.

[0085] The PDCCH is used to transmit control information, including the time-domain resource allocation information and frequency-domain resource allocation information of the PDSCH.

[0086] Schematic example, taking the first type of terminal implemented as an eRedCap terminal, when the baseband processing bandwidth of the common PDSCH exceeds the bandwidth processing capability corresponding to the eRedCap terminal, the resource allocation range corresponding to the eRedCap terminal is read from the PDCCH. For example, the eRedCap terminal reads the time-domain resource allocation information corresponding to the eRedCap terminal from the PDCCH, and / or, the eRedCap terminal reads the frequency-domain resource allocation information corresponding to the eRedCap terminal from the PDCCH. That is, the resource allocation range includes at least one of time-domain resource allocation information and frequency-domain resource allocation information.

[0087] In an optional embodiment, a portion of the public PDSCH resources within the resource allocation range are received based on the terminal's capabilities.

[0088] Optionally, based on the terminal capabilities corresponding to the eRedCap terminal, the eRedCap terminal can read a portion of the public PDSCH resources within its terminal capability range from the public PDSCH. Illustratively, based on the bandwidth processing capabilities corresponding to the eRedCap terminal, the eRedCap terminal can read resource information transmitted on the baseband processing bandwidth that belongs to its bandwidth processing capabilities; this resource information is the aforementioned portion of the public PDSCH resources.

[0089] For example: the bandwidth processing capability corresponding to the eRedCap terminal is 3MHz; the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is 5MHz. Since the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the terminal capability corresponding to the eRedCap terminal, the resource allocation range corresponding to the eRedCap terminal is read from the PDCCH. For example: the resource allocation range corresponding to the eRedCap terminal is read from the PDCCH as 0 to 4MHz.

[0090] The resource allocation range corresponding to the eRedCap terminal is used to indicate the resource allocation range that the eRedCap terminal is expected to receive, and the resource allocation range is within the baseband processing bandwidth.

[0091] Indicatively, the resource allocation range is less than the terminal capability corresponding to the eRedCap terminal (i.e., the resource allocation range does not exceed the processing capability of the terminal and can process the resources within the allocation range); or, the resource allocation range is equal to the terminal capability corresponding to the eRedCap terminal; or, the resource allocation range is greater than the terminal capability corresponding to the eRedCap terminal.

[0092] To illustrate, when the resource allocation range is less than the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive all public PDSCH resources within the resource allocation range from the public PDSCH; or, when the resource allocation range is equal to the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive all public PDSCH resources within the resource allocation range from the public PDSCH; or, when the resource allocation range is greater than the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive a portion of the public PDSCH resources within the resource allocation range from the public PDSCH, that is: the eRedCap terminal reads from the public PDSCH resources that are within the resource allocation range (within the baseband processing bandwidth) and that the eRedCap terminal can receive.

[0093] Optionally, the example is taken with a resource allocation range of 0 to 4 MHz and a terminal capability of 3 MHz corresponding to the eRedCap terminal. When receiving a portion of the public PDSCH resources within the resource allocation range based on the terminal capability, the example receives a portion of the public PDSCH resources transmitted on the 0 to 3 MHz bandwidth.

[0094] Due to limitations in the capabilities of the eRedCap terminal, public PDSCH resources transmitted on the 3MHz to 4MHz bandwidth that are intended to be received by the eRedCap terminal cannot be directly received by the eRedCap terminal. Optionally, based on the above situation, the resources transmitted on the 3MHz to 4MHz bandwidth can be restored through the following process.

[0095] In an optional embodiment, within the resource allocation range, the resource data exceeding the public PDSCH resources is padded to obtain channel resources.

[0096] Optionally, the range used to represent data completion within the resource allocation range is the resource allocation range. When the resource allocation range is greater than the terminal capability corresponding to the eRedCap terminal, resources that are within the resource allocation range but outside the terminal capability range and cannot be received by the eRedCap terminal are completed.

[0097] In illustrative terms, the resource allocation range is 0 to 4 MHz; the eRedCap terminal's corresponding terminal capability is 3 MHz. Therefore, when supplementing data for resources exceeding the allocated common PDSCH resources, the portion of common PDSCH resources within the 0 to 3 MHz bandwidth is retained, and data supplementation is performed on resources within the 3 MHz to 4 MHz bandwidth. This process of supplementing data for a portion of the common PDSCH resources is then implemented, and the supplemented resources are used as channel resources. In other words, channel resources include both a portion of the common PDSCH resources and the supplemented resources obtained after data supplementation based on the portion of the common PDSCH resources.

[0098] As an illustration, when padding some public PDSCH resources with data, the unreceived resources are padded, for example, with 0s or 1s, to obtain the channel resources.

[0099] In an optional embodiment, the channel resources are demodulated to obtain channel transmission data.

[0100] To illustrate, after obtaining the channel resources based on the above data completion operation, the channel resources are demodulated to obtain the channel transmission data.

[0101] Optionally, after obtaining the aforementioned channel resources, an attempt is made to demodulate the channel resources. If demodulation is successful, channel transmission data is obtained. Alternatively, if demodulation fails, the data padding format is changed, such as replacing "padded with 1" with "padded with 0", and an attempt is made to demodulate the channel resources after changing the data padding format. The above process is repeated until channel transmission data is obtained.

[0102] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0103] This application describes a method for receiving channel transmission data as comprehensively as possible through data completion. When the baseband processing bandwidth of the common PDSCH is within the terminal capability of the first type of terminal, the common PDSCH can be received. When the baseband processing bandwidth of the common PDSCH exceeds the terminal capability of the first type of terminal, a portion of the common PDSCH resources within the baseband processing bandwidth and resource allocation range can be received based on the terminal capability. Data completion is then performed on this portion of the common PDSCH resources based on the resource allocation range, thereby demodulating the completed channel resources to obtain the restored channel transmission data as comprehensively as possible. This allows the first type of terminal to acquire information sent by the access network device as comprehensively as possible, avoiding indiscriminate data discarding within the terminal capability range.

[0104] Method 3: Define a preset threshold, which can be higher or lower than the terminal's capability. When the transmission resource parameters exceed the preset threshold, the Type 1 terminal abandons processing subsequent common PDSCH. When the transmission resource parameters are lower than the preset threshold, the Type 1 terminal attempts to demodulate the common PDSCH.

[0105] Indicative, such as Figure 5 As shown, step 210 above can also be implemented as steps 510 to 522 below.

[0106] Step 510: Receive the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

[0107] Optionally, the first type of terminal is implemented as an eRedCap terminal as an example for explanation. The transmission resource parameters are implemented as resource parameters allocated by the access network device to the eRedCap terminal. Illustratively, the access network device transmits the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal to the eRedCap terminal via the PDCCH. In other embodiments, the transmission resource parameters may also be parameters configured by the core network device for the eRedCap terminal.

[0108] Optionally, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the first type of terminal and TBS.

[0109] Step 521: In response to the transmission resource parameters of the public PDSCH exceeding the preset threshold corresponding to the first type of terminal, stop receiving the public PDSCH.

[0110] In an optional embodiment, the following description is based on an example of a first type of terminal implemented as an eRedCap terminal. In response to the transmission resource parameters of the common PDSCH exceeding a preset threshold corresponding to the eRedCap terminal, reception of the common PDSCH is stopped.

[0111] Optionally, a preset threshold can be determined for the eRedCap terminal.

[0112] The preset threshold assigned to the eRedCap terminal represents the threshold processing capability pre-configured for the eRedCap terminal. Illustratively, the preset threshold may be the processing capability configured by the access network device for the eRedCap terminal; or, the preset threshold may be the processing capability agreed upon in the protocol; or, the preset threshold may be a value determined empirically, for example, if threshold value A achieves better data transmission results during multiple transmissions, then threshold value A may be used as the preset threshold.

[0113] Optionally, if the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal exceed the preset threshold corresponding to the eRedCap terminal, the eRedCap terminal will be unable to receive the public PDSCH.

[0114] Schematic, the preset thresholds include at least one of a preset bandwidth threshold set for baseband processing bandwidth and a preset TBS threshold set for TBS.

[0115] Specifically, for different transmission resource parameters, the reception of the public PDSCH by the eRedCap terminal includes at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. As an illustration, when the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the preset bandwidth threshold corresponding to the eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0116] 2. The transmission resource parameters include TBS. As an illustration, when the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the preset TBS threshold corresponding to the eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0117] 3. The transmission resource parameters include baseband processing bandwidth and TBS. 3.1 When the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the preset bandwidth threshold corresponding to the eRedCap terminal, and the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the preset TBS threshold corresponding to the eRedCap terminal, the eRedCap terminal stops receiving the public PDSCH.

[0118] 3.2If the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the preset bandwidth threshold corresponding to the eRedCap terminal, but the TBS of the public PDSCH allocated to the eRedCap terminal exceeds the preset TBS threshold corresponding to the eRedCap terminal, the eRedCap terminal will stop receiving the public PDSCH.

[0119] 3.3 If the baseband bandwidth (TBS) of the public PDSCH allocated to the eRedCap terminal is within the preset TBS threshold corresponding to the eRedCap terminal, but the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal exceeds the preset bandwidth threshold corresponding to the eRedCap terminal, the eRedCap terminal will stop receiving the public PDSCH.

[0120] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0121] Step 522: In response to the transmission resource parameters of the common PDSCH being within the preset threshold corresponding to the first type of terminal, receive the common PDSCH.

[0122] In an optional embodiment, the following description is based on an example of a first-type terminal implemented as an eRedCap terminal. When the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are within the range of the preset threshold corresponding to the eRedCap terminal, the eRedCap terminal is able to receive the public PDSCH.

[0123] Specifically, for different transmission resource parameters, the reception of the public PDSCH by the eRedCap terminal includes at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. When the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the preset bandwidth threshold corresponding to the eRedCap terminal, the eRedCap terminal will receive the public PDSCH.

[0124] 2. The transmission resource parameters include TBS. When the TBS of the public PDSCH allocated to the eRedCap terminal is within the preset TBS threshold corresponding to the eRedCap terminal, the eRedCap terminal will receive the public PDSCH.

[0125] 3. The transmission resource parameters include baseband processing bandwidth and TBS. When the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal is within the preset bandwidth threshold corresponding to the eRedCap terminal, and the TBS of the public PDSCH allocated to the eRedCap terminal is within the preset TBS threshold corresponding to the eRedCap terminal, the eRedCap terminal receives the public PDSCH.

[0126] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0127] In this embodiment, a preset threshold is pre-configured for the first type of terminal. When the transmission resource parameters of the common PDSCH exceed the range of the preset threshold corresponding to the first type of terminal, the reception of the common PDSCH will stop; when the transmission resource parameters of the common PDSCH are within the range of the preset threshold corresponding to the first type of terminal, the common PDSCH will be received. This differentiates the reception method of the common PDSCH, clarifies the behavior of the first type of terminal, and improves the accuracy of scheduling the first type of terminal.

[0128] In some optional embodiments, the transport resource parameters of the public PDSCH allocated to the first type of terminal are read from the PDCCH. (Illustrative example, such as...) Figure 6 As shown, step 210 above can also be implemented as steps 610 to 620 below.

[0129] Step 610: Receive PDCCH.

[0130] The PDCCH carries indication information, which indicates the transmission resource parameters of the public PDSCH allocated to the first type of terminal. The following explanation is illustratively illustrated using an eRedCap terminal as an example of the first type of terminal. The eRedCap terminal can determine the transmission resource parameters of the public PDSCH allocated to it through the indication information carried on the PDCCH.

[0131] Optionally, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the eRedCap terminal. Schematic, the access network device transmits the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal via the PDCCH.

[0132] In some optional embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0133] Indicatively, when receiving the transmission resource parameters of the common PDSCH, the eRedCap terminal receives the baseband processing bandwidth of the common PDSCH allocated to the eRedCap terminal; or, receives the TBS of the common PDSCH allocated to the eRedCap terminal; or, receives both the baseband processing bandwidth and TBS of the common PDSCH allocated to the eRedCap terminal.

[0134] Step 620: Determine the receiving method of the public PDSCH based on the transmission resource parameters of the public PDSCH allocated to the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

[0135] In an optional embodiment, the following description is based on an example of a first type of terminal implemented as an eRedCap terminal.

[0136] Optionally, after receiving the PDCCH, the eRedCap terminal reads the PDCCH and determines the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal based on the indication information carried on the PDCCH, thereby determining the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal; or, determining the TBS of the public PDSCH allocated to the eRedCap terminal; or, determining both the baseband processing bandwidth and TBS of the public PDSCH allocated to the eRedCap terminal.

[0137] The terminal capability corresponding to the eRedCap terminal refers to the processing capability of the eRedCap terminal. Optionally, the terminal capability corresponding to the eRedCap terminal is implemented as the terminal capability configured by the access network equipment for the eRedCap terminal; or, the terminal capability corresponding to the eRedCap terminal is implemented as the terminal capability configured by the eRedCap terminal itself, etc.

[0138] In an optional embodiment, the method of receiving the public PDSCH includes the following forms.

[0139] (1) Stop receiving public PDSCH Optionally, if the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal exceed the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal cannot receive the public PDSCH.

[0140] (2) Receiving public PDSCH Optionally, when the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are within the range of the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive the public PDSCH.

[0141] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0142] In this embodiment, the process of specifying the transmission resource parameters of the public PDSCH allocated to a first-type terminal by the indication information carried by the PDCCH is described. The first-type terminal can determine the transmission resource parameters by reading the PDCCH, and based on the transmission resource parameters and the terminal capabilities of the first-type terminal, adjust the reception method of the public PDSCH differently. When ordinary terminals and first-type terminals use the public PDSCH, the behavior of the first-type terminal is clarified, and the accuracy of scheduling the first-type terminal is improved.

[0143] This is illustrative; please refer to it. Figure 7 This disclosure provides a flowchart of a scheduling method according to an exemplary embodiment, using the application of this method to an access network device as an example for illustration. Figure 7 As shown, the method includes the following steps 710 to 720.

[0144] Step 710: Send PDCCH to the first type of terminal.

[0145] The PDCCH carries indication information.

[0146] In an optional embodiment, the following description is based on an example of a first type of terminal implemented as an eRedCap terminal.

[0147] The indication information is used to indicate the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal.

[0148] Optionally, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the eRedCap terminal. Illustratively, the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal are transmitted via the PDCCH.

[0149] In some optional embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0150] Indicatively, when receiving the transmission resource parameters of the common PDSCH, the eRedCap terminal receives the baseband processing bandwidth of the common PDSCH allocated to the eRedCap terminal; or, receives the TBS of the common PDSCH allocated to the eRedCap terminal; or, receives both the baseband processing bandwidth and TBS of the common PDSCH allocated to the eRedCap terminal.

[0151] Step 720: Configure the transmission resource parameters of the common PDSCH for the first type of terminal.

[0152] The transmission resource parameters are used to indicate the reception method of the public PDSCH. That is, the reception method of the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal.

[0153] In an optional embodiment, the method of receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal. Optionally, the following description takes an eRedCap terminal as an example of the first type of terminal.

[0154] The eRedCap terminal is used to determine the reception method of the public PDSCH based on transmission resource parameters and terminal capabilities. The terminal capabilities corresponding to the eRedCap terminal represent the processing capabilities of the eRedCap terminal.

[0155] Optionally, after receiving the PDCCH, the eRedCap terminal determines the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal based on the indication information carried by the PDCCH, and determines the following receiving method for the public PDSCH based on the transmission resource parameters and the terminal capabilities.

[0156] (1) Stop receiving public PDSCH Optionally, if the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal exceed the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal cannot receive the public PDSCH.

[0157] (2) Receiving public PDSCH Optionally, when the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are within the range of the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive the public PDSCH.

[0158] Optionally, the transmission resource parameters include at least one of the baseband processing bandwidth and transport block size of the common PDSCH.

[0159] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0160] In summary, after the access network equipment sends the common PDSCH and PDCCH to the first type of terminal, the first type of terminal can adjust its reception method of the common PDSCH differently based on the transmission resource parameters it reads and the terminal capabilities it possesses. This clarifies the behavior of the first type of terminal when ordinary terminals and the first type of terminal use the common PDSCH, thereby improving the accuracy of scheduling the first type of terminal.

[0161] In this embodiment, the access network device comprehensively analyzes the terminal capabilities of the first type of terminal and whether there are resources in the public PDSCH for transmission to the first type of terminal, thereby determining the transmission resource parameters of the public PDSCH allocated to the first type of terminal. Regarding the three methods for comparing terminal capabilities and transmission resource parameters on the terminal side, the access network device's restriction on transmission resource parameters is implemented in at least one of the following ways: For Method 1 on the terminal side, the access network equipment side is implemented as follows: If the public PDSCH contains data that a Type 1 terminal needs to read, the transmission resource parameters transmitted by the access network device must be within the terminal capabilities of the Type 1 terminal. If the public PDSCH does not contain data that a Type 1 terminal needs to read, the transmission resource parameters transmitted by the access network device are not limited by the terminal capabilities of the Type 1 terminal. For example, if the public PDSCH contains data that an eRedCap terminal needs to read, the transmission resource parameters transmitted by the access network device must be within the terminal capabilities of the eRedCap terminal; if the public PDSCH does not contain data that an eRedCap terminal needs to read, the transmission resource parameters transmitted by the access network device are not limited by the terminal capabilities of the eRedCap terminal.

[0162] For Method 2 on the terminal side, the access network equipment side is implemented as follows: When access network equipment performs public PDSCH transmission, the terminal capability limitations of Type I terminals are not considered. For example, when access network equipment performs public PDSCH transmission, the terminal capability limitations of eRedCap terminals are not considered.

[0163] For Method 3 on the terminal side, the access network equipment side is implemented as follows: If the public PDSCH contains data that the first type of terminal needs to read, the transmission resource parameters transmitted by the access network device must be within a preset threshold; if the public PDSCH does not contain data that the first type of terminal needs to read, the transmission resource parameters transmitted by the access network device are not subject to the preset threshold. For example: if the public PDSCH contains data that the eRedCap terminal needs to read, the transmission resource parameters transmitted by the access network device must be within a preset threshold; if the public PDSCH does not contain data that the eRedCap terminal needs to read, the transmission resource parameters transmitted by the access network device are not subject to the preset threshold.

[0164] The above methods will be described in detail.

[0165] Method 1: If the public PDSCH contains data that the first type of terminal needs to read, then the transmission resource parameters transmitted by the access network device must be within the terminal capabilities of the first type of terminal.

[0166] Indicative, such as Figure 8 As shown, step 720 above can also be implemented as steps 810 to 820 below.

[0167] Step 810: Receive terminal capabilities reported by the first type of terminal.

[0168] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0169] As an illustration, the access network equipment first determines the terminal capabilities corresponding to the eRedCap terminal.

[0170] Optionally, the terminal capabilities corresponding to the eRedCap terminal include at least one of bandwidth processing capability and transport block processing capability. Bandwidth processing capability represents the baseband bandwidth processing limit that the eRedCap terminal can handle; transport block processing capability represents the TBS limit that the eRedCap terminal can receive or read.

[0171] In one optional embodiment, the access network device configures the eRedCap terminal's terminal capabilities to the eRedCap terminal and obtains the eRedCap terminal's terminal capabilities; or, the eRedCap terminal determines its terminal capabilities based on the default configuration, and the access network device determines the eRedCap terminal's terminal capabilities based on the information sent by the terminal to the access network device, etc.

[0172] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0173] Step 820: If there is data to be transmitted to the first type of terminal in the public PDSCH, configure the transmission resource parameters of the public PDSCH within the terminal capability range for the first type of terminal.

[0174] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0175] To illustrate, when the access network device determines that there are resources in the public PDSCH that need to be transmitted to the eRedCap terminal, that is, there are resources in the public PDSCH that need to be received by the eRedCap terminal, the access network device determines that the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are less than the terminal's capacity.

[0176] The transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0177] When it is determined that the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are less than the terminal's capacity, the corresponding transmission resource parameters are restricted to within the corresponding terminal's capacity based on the difference in transmission resource parameters.

[0178] For different transmission resource parameters, the limitations of the transmission resource parameters include at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. As an illustration, when the transmission resource parameters are implemented as baseband processing bandwidth, the baseband processing bandwidth of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the bandwidth processing capacity corresponding to the eRedCap terminal.

[0179] 2. The transmission resource parameters include TBS. As an illustration, when the transmission resource parameter is implemented as TBS, the TBS of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the transmission block processing capacity corresponding to the eRedCap terminal.

[0180] 3. The transmission resource parameters include baseband processing bandwidth and TBS. Indicatively, when the transmission resource parameters are implemented as baseband processing bandwidth and TBS, the baseband processing bandwidth of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the bandwidth processing capacity corresponding to the eRedCap terminal, and the TBS of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the transport block processing capacity corresponding to the eRedCap terminal.

[0181] Optionally, based on the above process, the transmission resource parameters of the common PDSCH allocated by the access network device to the eRedCap terminal are less than the terminal's capability, thereby enabling the eRedCap terminal to receive the transmission resource parameters more accurately and completely, so that the eRedCap terminal can receive the common PDSCH more accurately based on the transmission resource parameters.

[0182] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0183] In this embodiment, before the access network device allocates the transmission resource parameters of the common PDSCH to the first type of terminal, it first determines the terminal capability of the first type of terminal. Then, within the range of the terminal capability, it allocates the transmission resource parameters of the common PDSCH to the first type of terminal, so that the first type of terminal can read more accurate transmission resource parameters that are more in line with its own characteristics and determine the PDSCH reception process. This makes it easier for the first type of terminal to understand its own terminal behavior and improves the accuracy of scheduling the first type of terminal.

[0184] Method 2: When the access network equipment performs public PDSCH transmission, the terminal capability limitations of the first type of terminal are not considered.

[0185] Indicative, such as Figure 9 As shown, steps 710 to 720 above can also be implemented as steps 910 to 920 below.

[0186] Step 910: Send PDCCH to the first type of terminal.

[0187] The PDCCH carries indication information, which is used to indicate the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

[0188] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0189] In other words, by sending the PDCCH to the eRedCap terminal, the access network device enables the eRedCap terminal to determine the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal.

[0190] Optionally, the PDCCH also carries the resource allocation range on the public PDSCH corresponding to the first type of terminal.

[0191] In some optional embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0192] Indicatively, when receiving the transmission resource parameters of the common PDSCH, the eRedCap terminal receives the baseband processing bandwidth of the common PDSCH allocated to the eRedCap terminal; or, receives the TBS of the common PDSCH allocated to the eRedCap terminal; or, receives both the baseband processing bandwidth and TBS of the common PDSCH allocated to the eRedCap terminal.

[0193] In an optional embodiment, the PDCCH is also used to indicate the resource allocation range corresponding to the eRedCap terminal on the public PDSCH.

[0194] Optionally, after the access network device sends the PDCCH to the eRedCap terminal, the eRedCap terminal can read the resource allocation range corresponding to the eRedCap terminal from the PDCCH.

[0195] Schematic, the resource allocation range includes at least one of time-domain resource allocation information and frequency-domain resource allocation information. The resource allocation range corresponding to the eRedCap terminal is used to indicate the resource allocation range that is expected to be received by the eRedCap terminal, and the resource allocation range is within the baseband processing bandwidth.

[0196] Step 920: Send a common PDSCH to the first type of terminal.

[0197] In an optional embodiment, the following description uses an eRedCap terminal as an example of a first type of terminal. The eRedCap terminal is used to determine the reception method of the public PDSCH based on transmission resource parameters and terminal capabilities.

[0198] Optionally, in response to the baseband processing bandwidth of the public PDSCH being within the terminal capability corresponding to the eRedCap terminal, the public PDSCH is received.

[0199] In an optional embodiment, in response to the baseband processing bandwidth of the public PDSCH exceeding the range of the terminal capability corresponding to the eRedCap terminal, a portion of the public PDSCH resources on the baseband processing bandwidth are received based on the terminal capability.

[0200] Optionally, based on the terminal's capabilities, a portion of the public PDSCH resources within the resource allocation range are received; using the resource allocation range as a benchmark, the data of the portion of the public PDSCH resources is supplemented to obtain the channel resources.

[0201] The resource allocation range is used as a reference to represent the range for data completion. When the resource allocation range is greater than the terminal capability corresponding to the eRedCap terminal, resources that are within the resource allocation range but outside the terminal capability range and cannot be received by the eRedCap terminal are completed to obtain the completed channel resources.

[0202] Optionally, the channel resources are demodulated to obtain the channel transmission data.

[0203] To illustrate, after obtaining the channel resources based on the above data completion operation, the channel resources are demodulated to obtain the channel transmission data.

[0204] In an optional embodiment, after demodulating the channel resources and obtaining the channel transmission data, reception of the common PDSCH is stopped.

[0205] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0206] In this embodiment, it is described that the PDCCH sent by the access network device to the first type of terminal also carries the resource allocation range on the public PDSCH corresponding to the first type of terminal. Therefore, when the baseband processing bandwidth of the public PDSCH allocated to the first type of terminal exceeds the range of the terminal capability corresponding to the first type of terminal, the first type of terminal can receive part of the public PDSCH resources within the baseband processing bandwidth and within the resource allocation range based on the terminal capability. And based on the resource allocation range, the data of part of the public PDSCH resources is supplemented, so that the first type of terminal can demodulate the supplemented channel resources to obtain the restored channel transmission data as much as possible. This not only helps to avoid the first type of terminal discarding data indiscriminately, but also helps the first type of terminal to clarify its own terminal behavior.

[0207] Method 3: If the public PDSCH contains data that the first type of terminal needs to read, the transmission resource parameters transmitted by the access network device must be within the preset threshold; if the public PDSCH does not contain data that the first type of terminal needs to read, the transmission resource parameters transmitted by the access network device are not subject to the preset threshold.

[0208] Indicative, such as Figure 10 As shown, step 720 above can also be implemented as steps 1010 to 1020 below.

[0209] Step 1010: Obtain the preset threshold configured for the first type of terminal.

[0210] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0211] As an illustration, the access network device first determines a preset threshold configured for the eRedCap terminal. Optionally, the preset threshold includes at least one of a preset bandwidth threshold and a preset TBS threshold.

[0212] In one optional embodiment, the access network device configures a preset threshold for the eRedCap terminal and obtains the preset threshold of the eRedCap terminal; or, the eRedCap terminal determines the preset threshold of the eRedCap terminal based on the default configuration, and the access network device determines the preset threshold of the eRedCap terminal based on the information sent by the terminal to the access network device, etc.

[0213] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0214] Step 1020: If there is data to be transmitted to the first type of terminal in the public PDSCH, configure the transmission resource parameters of the public PDSCH within a preset threshold range for the first type of terminal.

[0215] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0216] To illustrate, let's take the example of an access network device sending a common PDSCH to an eRedCap terminal. When the access network device determines that there are resources in the common PDSCH that need to be transmitted to the eRedCap terminal, that is, resources in the common PDSCH that need to be received by the eRedCap terminal, it determines that the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal are less than a preset threshold.

[0217] The transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0218] When it is determined that the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are less than a preset threshold, the corresponding transmission resource parameters are restricted to within the corresponding preset threshold based on the difference in transmission resource parameters.

[0219] For different transmission resource parameters, the limitations of the transmission resource parameters include at least one of the following: 1. The transmission resource parameters include baseband processing bandwidth. As an illustration, when the transmission resource parameters are implemented as baseband processing bandwidth, the baseband processing bandwidth of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the preset bandwidth threshold corresponding to the eRedCap terminal.

[0220] 2. The transmission resource parameters include TBS. As an illustration, when the transmission resource parameter is implemented as TBS, the TBS of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the preset TBS threshold corresponding to the eRedCap terminal.

[0221] 3. The transmission resource parameters include baseband processing bandwidth and TBS. Indicatively, when the transmission resource parameters are implemented as baseband processing bandwidth and TBS, the baseband processing bandwidth of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the preset bandwidth threshold corresponding to the eRedCap terminal, and the TBS of the common PDSCH allocated by the access network device to the eRedCap terminal is limited to the preset TBS threshold corresponding to the eRedCap terminal.

[0222] Optionally, based on the above process, the transmission resource parameters of the public PDSCH allocated by the access network device to the eRedCap terminal are made to be less than a preset threshold, so that the eRedCap terminal can receive the transmission resource parameters more accurately and completely, so that the eRedCap terminal can receive the public PDSCH more comprehensively.

[0223] It is worth noting that the above are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0224] In this embodiment of the application, before the transmission resource parameters of the common PDSCH of the first type of terminal in the access network device are obtained, a preset threshold is first determined for the first type of terminal. Within the range of the preset threshold, the transmission resource parameters of the common PDSCH are allocated to the first type of terminal, so that the first type of terminal can read more accurate transmission resource parameters and determine the receiving process of PDSCH, which facilitates the improvement of the accuracy of scheduling of the first type of terminal.

[0225] Figure 11 This is a structural block diagram of a scheduling method provided in an exemplary embodiment of the present disclosure, and the method is described using the interaction process between a first type of terminal and an access network device as an example.

[0226] Step 1110: The access network device sends a PDCCH to the first type of terminal.

[0227] The PDCCH carries indication information.

[0228] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0229] The indication information is used to indicate the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal. Optionally, the transmission resource parameters are implemented as resource parameters allocated by the access network device to the eRedCap terminal. Illustratively, the transmission resource parameters of the common PDSCH allocated to the eRedCap terminal are transmitted via the PDCCH.

[0230] In some optional embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0231] Indicatively, when receiving the transmission resource parameters of the common PDSCH, the eRedCap terminal receives the baseband processing bandwidth of the common PDSCH allocated to the eRedCap terminal; or, receives the TBS of the common PDSCH allocated to the eRedCap terminal; or, receives both the baseband processing bandwidth and TBS of the common PDSCH allocated to the eRedCap terminal.

[0232] Step 1120: The access network device sends a common PDSCH to the first type of terminal.

[0233] In an optional embodiment, the following description is given using the first type of terminal as an eRedCap terminal as an example.

[0234] Optionally, after receiving the PDCCH, the eRedCap terminal determines the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal based on the indication information carried by the PDCCH, and determines the following receiving method for the public PDSCH based on the transmission resource parameters and the terminal capabilities.

[0235] (1) Stop receiving public PDSCH Optionally, if the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal exceed the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal cannot receive the public PDSCH.

[0236] (2) Receiving public PDSCH Optionally, when the transmission resource parameters of the public PDSCH allocated to the eRedCap terminal are within the range of the terminal capability corresponding to the eRedCap terminal, the eRedCap terminal can receive the public PDSCH.

[0237] Step 1130: Determine the receiving method of the public PDSCH based on the transmission resource parameters of the public PDSCH allocated to the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

[0238] Optionally, taking the first type of terminal, the eRedCap terminal, as an example, the following explanation is provided. The terminal capabilities corresponding to the eRedCap terminal are used to represent the processing capabilities of the eRedCap terminal.

[0239] In some optional embodiments, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0240] Optionally, the terminal receives transmission resource parameters sent by the access network device. Illustratively, the access network device transmits the allocated public PDSCH transmission resource parameters to the eRedCap terminal via the PDCCH. Optionally, the public PDSCH refers to the transmission communication data channel shared by ordinary terminals and eRedCap terminals; that is, the public PDSCH is a channel used jointly by ordinary terminals and eRedCap terminals.

[0241] In summary, based on the transmission resource parameters of the common PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal, the reception method of the common PDSCH is determined. This allows the first type of terminal to adjust its reception method differently based on its terminal capabilities after determining the transmission resource parameters of the common PDSCH. When ordinary terminals and first type terminals use the common PDSCH, the behavior of the first type of terminal is clarified, and the accuracy of scheduling the first type of terminal is improved.

[0242] Figure 12 This is a structural block diagram of a scheduling device provided in an exemplary embodiment of this disclosure, such as... Figure 12 As shown, the device includes: The receiving module 1210 is used to receive the common physical downlink shared channel (PDSCH), wherein the method of receiving the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal.

[0243] In an optional embodiment, the method of receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

[0244] In an optional embodiment, the transmission resource parameters include at least one of the baseband processing bandwidth of the public PDSCH allocated to the eRedCap terminal and TBS.

[0245] In an optional embodiment, the receiving module 1210 is further configured to receive the public PDSCH when the transmission resource parameters of the public PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal.

[0246] In an optional embodiment, the receiving module 1210 is further configured to stop receiving the public PDSCH when the transmission resource parameters of the public PDSCH exceed the range of the terminal capability corresponding to the first type of terminal.

[0247] In an optional embodiment, the transmission resource parameters include baseband processing bandwidth; The device further includes: The resource receiving module 1220 is used to receive a portion of the public PDSCH resources on the baseband processing bandwidth based on the terminal capability when the baseband processing bandwidth of the public PDSCH exceeds the range of the terminal capability corresponding to the first type of terminal.

[0248] In an optional embodiment, the resource receiving module 1220 is further configured to read the resource allocation range corresponding to the first type of terminal on the public PDSCH from the physical downlink control channel PDCCH when the baseband processing bandwidth of the public PDSCH exceeds the range of the terminal capability corresponding to the first type of terminal; and receive a portion of the public PDSCH resources within the resource allocation range based on the terminal capability.

[0249] In an optional embodiment, the apparatus further includes: The data completion module 1230 is used to complete the resource data that exceeds the portion of public PDSCH resources within the resource allocation range, so as to obtain the channel resources; The demodulation module 1240 is also used to demodulate the channel resources to obtain channel transmission data.

[0250] In an optional embodiment, the receiving module 1210 is further configured to receive the public PDSCH in response to the transmission resource parameters of the public PDSCH being within a preset threshold corresponding to the first type of terminal.

[0251] In an optional embodiment, the receiving module 1210 is further configured to stop receiving the public PDSCH in response to the transmission resource parameters of the public PDSCH exceeding a preset threshold corresponding to the first type of terminal.

[0252] In an optional embodiment, the receiving module 1210 is further configured to receive indication information, the indication information being used to indicate the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

[0253] In an optional embodiment, the receiving module 1210 is further configured to receive a PDCCH, the PDCCH carrying the indication information.

[0254] In an optional embodiment, the first type of terminal includes an enhanced redcap terminal.

[0255] In summary, determining the reception method of the common PDSCH based on the transmission resource parameters of the common PDSCH of the first type of terminal enables the first type of terminal to adjust its reception method differently after determining the transmission resource parameters of the common PDSCH. When ordinary terminals and first type terminals use the common PDSCH, the terminal behavior of the first type of terminal is clarified, and the accuracy of scheduling of the first type of terminal is improved.

[0256] Figure 13 This is a structural block diagram of a scheduling device provided in an exemplary embodiment of this disclosure, such as... Figure 13As shown, the device includes: The configuration module 1310 is used to configure the transmission resource parameters of the common PDSCH to the first type of terminal, wherein the transmission resource parameters are used to indicate the receiving method of the common PDSCH.

[0257] In an optional embodiment, the method of receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

[0258] In an optional embodiment, the transmission resource parameters include at least one of the baseband processing bandwidth of the common PDSCH and the transport block size.

[0259] In an optional embodiment, the configuration module 1310 is further configured to receive terminal capabilities reported by the first type of terminal; If data to be transmitted to the first type of terminal exists in the public PDSCH, the transmission resource parameters of the public PDSCH within the terminal's capability range are configured for the first type of terminal.

[0260] In an optional embodiment, the configuration module 1310 is further configured to send a PDCCH to the first type of terminal, the PDCCH being used to indicate the transmission resource parameters of the public PDSCH configured for the first type of terminal.

[0261] In an optional embodiment, the PDCCH is further used to indicate the resource allocation range on the public PDSCH corresponding to the first type of terminal.

[0262] In an optional embodiment, the configuration module 1310 is further configured to configure transmission resource parameters of the public PDSCH within a preset threshold range for the first type of terminal when there is data to be transmitted to the first type of terminal in the public PDSCH.

[0263] In an optional embodiment, the first type of terminal includes an eRedCap terminal.

[0264] In summary, after the access network equipment sends the common PDSCH and PDCCH to the first type of terminal, the first type of terminal can adjust its reception method of the common PDSCH differently based on the transmission resource parameters it reads and the terminal capabilities it possesses. This clarifies the behavior of the first type of terminal when ordinary terminals and the first type of terminal use the common PDSCH, thereby improving the accuracy of scheduling the first type of terminal.

[0265] It should be noted that the scheduling device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the scheduling device and scheduling method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0266] Figure 14 A schematic diagram of the structure of a communication device 1400 (terminal or access network device) provided in an exemplary embodiment of the present disclosure is shown. The terminal includes: a processor 1401, a receiver 1402, a transmitter 1403, a memory 1404, and a bus 1405.

[0267] The processor 1401 includes one or more processing cores, and the processor 1401 executes various functional applications and information processing by running software programs and modules.

[0268] The receiver 1402 and the transmitter 1403 can be implemented as a communication component, which can be a communication chip.

[0269] The memory 1404 is connected to the processor 1401 via the bus 1405.

[0270] The memory 1404 can be used to store at least one instruction, and the processor 1401 can execute the at least one instruction to implement the various steps in the above method embodiments.

[0271] Furthermore, the memory 1404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but 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 storage, flash memory, and programmable read-only memory (PROM).

[0272] A non-transitory computer-readable storage medium, wherein when instructions in the non-transitory computer storage medium are executed by a terminal's processor, the terminal is able to execute the aforementioned scheduling method.

[0273] An exemplary embodiment of this disclosure also provides a message receiving system, the system comprising: a terminal and an access network device; The terminal includes, for example: Figure 12 The scheduling device provided in the illustrated embodiment; The access network equipment includes, for example, Figure 13 The scheduling device provided in the illustrated embodiment.

[0274] An exemplary embodiment of this disclosure also provides a computer-readable storage medium storing at least one instruction, at least one program, a code set, or an instruction set, wherein 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 executed by the terminal in the scheduling methods provided in the above-described method embodiments.

[0275] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0276] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0277] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A scheduling method, characterized in that, The method is executed by a first type of terminal, and the method includes: The common physical downlink shared channel (PDSCH) is received, and the method of receiving the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal; the first type of terminal includes an enhanced redcap terminal (eRedCap), and the common PDSCH is a channel shared by ordinary terminals and eRedCap terminals. The receiving of the common physical downlink shared channel (PDSCH) includes: If the transmission resource parameters of the public PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal, the public PDSCH is received.

2. The method according to claim 1, characterized in that, The method for receiving the public PDSCH is determined based on the transmission resource parameters of the public PDSCH of the first type of terminal and the terminal capabilities corresponding to the first type of terminal.

3. The method according to claim 1, characterized in that, The transmission resource parameters include at least one of the baseband processing bandwidth and transport block size of the common PDSCH.

4. The method according to claim 1, characterized in that, The method further includes: If the transmission resource parameters of the public PDSCH exceed the range of the terminal capabilities corresponding to the first type of terminal, the reception of the public PDSCH shall be stopped.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: Receive indication information, which indicates the transmission resource parameters of the public PDSCH allocated to the first type of terminal.

6. The method according to claim 5, characterized in that, The method further includes: Receive the Physical Downlink Control Channel (PDCCH), which carries the indication information.

7. A scheduling method, characterized in that, The method is executed by an access network device, and the method includes: The transmission resource parameters of a common PDSCH are configured for a first type of terminal, the transmission resource parameters being used to indicate the reception mode of the common PDSCH; the first type of terminal includes an enhanced redcap terminal (eRedCap), and the common PDSCH is a channel shared by both ordinary terminals and enhanced redcap terminals; when the transmission resource parameters of the common PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal, the common PDSCH is received by the first type of terminal.

8. The method according to claim 7, characterized in that, The transmission resource parameters include at least one of the baseband processing bandwidth and transport block size of the common PDSCH.

9. The method according to claim 7, characterized in that, The configuration of the common PDSCH transmission resource parameters for the first type of terminal includes: Receive terminal capabilities reported by the first type of terminal; If data to be transmitted to the first type of terminal exists in the public PDSCH, the transmission resource parameters of the public PDSCH within the terminal's capability range are configured for the first type of terminal.

10. The method according to claim 7, characterized in that, The configuration of the common PDSCH transmission resource parameters for the first type of terminal includes: A PDCCH is sent to the first type of terminal, the PDCCH being used to indicate the transmission resource parameters of the common PDSCH configured for the first type of terminal.

11. A scheduling device, characterized in that, The device includes: A receiving module is configured to receive a common physical downlink shared channel (PDSCH), wherein the method of receiving the common PDSCH is determined based on the transmission resource parameters of the common PDSCH of the first type of terminal; the first type of terminal includes an enhanced redcap (eRedCap) terminal, and the common PDSCH is a channel shared by ordinary terminals and eRedCap terminals; wherein receiving the common PDSCH includes: receiving the common PDSCH when the transmission resource parameters of the common PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal.

12. A scheduling device, characterized in that, The device includes: A configuration module is used to configure transmission resource parameters of a common PDSCH for a first type of terminal. The transmission resource parameters are used to indicate the reception mode of the common PDSCH. The first type of terminal includes an enhanced redcap (eRedCap) terminal. The common PDSCH is a channel shared by both ordinary terminals and eRedCap terminals. When the transmission resource parameters of the common PDSCH are within the range of the terminal capabilities corresponding to the first type of terminal, the common PDSCH is received by the first type of terminal.

13. A terminal, characterized in that, The terminal includes: processor; A transceiver connected to the processor; The processor is configured to execute executable instructions to implement the scheduling method as described in any one of claims 1 to 6.

14. An access network device, characterized in that, The access network equipment includes: processor; A transceiver connected to the processor; The processor is configured to execute executable instructions to implement the scheduling method as described in any one of claims 7 to 10.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction, which is executed by a processor to implement the scheduling method as described in any one of claims 1 to 6 and the scheduling method as described in any one of claims 7 to 10.

Images