Data scheduling method, device, and computer-readable storage medium

Abstract

The present application provides a data scheduling method, a device, and a computer-readable storage medium. The data scheduling method comprises: receiving configuration information, wherein the configuration information is used for configuring a frequency domain resource available to a first communication node; and on the basis of the configuration information, performing at least one of the following operations: monitoring a first physical control channel to acquire control information, receiving / transmitting a first physical shared channel on one or more specified bandwidth parts, and sending hybrid automatic repeat request acknowledgment information, wherein the first physical shared channel is transmitted on the one or more specified bandwidth parts in a specified scheduling mode, and the specified scheduling mode includes a frequency domain repetition scheduling mode. The method improves the reliability of data transmission.

Description

Data scheduling methods, devices and computer-readable storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to data scheduling methods, devices and computer-readable storage media. Background Technology

[0002] Wireless communication systems will exhibit a development trend of "convergence, intelligence, high speed, and ubiquity." To adapt to this trend, intelligent, diverse, and flexible wireless functions are needed to support new application ecosystems and development demands. To meet these demands, a more flexible and efficient frequency domain architecture is required. Under this new architecture, multiple sub-frequency domain resources, such as bandwidth portions, can be activated simultaneously on a single frequency domain resource. Therefore, how to achieve data scheduling under this new frequency domain architecture is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0003] This application provides a data scheduling method, an apparatus, and a computer-readable storage medium.

[0004] In a first aspect, embodiments of this application provide a data scheduling method applied to a first communication node, comprising: receiving configuration information; the configuration information being used to configure frequency domain resources available to the first communication node; and performing at least one of the following operations based on the configuration information: monitoring a first physical control channel to obtain control information; receiving / transmitting a first physical shared channel on one or more specified bandwidth portions; wherein the first physical shared channel is transmitted on the one or more specified bandwidth portions according to a specified scheduling method, the specified scheduling method including a frequency domain repetitive scheduling method; and sending hybrid automatic repeat request response information.

[0005] Secondly, embodiments of this application provide a data scheduling method applied to a second communication node, comprising: sending configuration information; the configuration information being used to configure frequency domain resources available to a first communication node; and performing at least one of the following operations based on the configuration information: sending control information; transmitting / receiving a first physical shared channel on one or more specified bandwidth portions; wherein the first physical shared channel is transmitted on the one or more specified bandwidth portions according to a specified scheduling method, the specified scheduling method including a frequency domain repetitive scheduling method; and receiving hybrid automatic repeat request response information.

[0006] Thirdly, embodiments of this application provide a communication node, including: a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the data scheduling method provided in the first or second aspect of embodiments of this application.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the data scheduling method provided in the first or second aspect of embodiments of this application. Attached Figure Description

[0008] Figure 1 is a schematic diagram of a wireless communication system to which the data scheduling method provided in this application is applicable;

[0009] Figure 2 is a flowchart illustrating a data scheduling method provided in an embodiment of this application.

[0010] Figure 3 is a schematic diagram of a resource configuration method provided in an embodiment of this application;

[0011] Figure 4 is another schematic diagram of the resource configuration method provided in the embodiments of this application;

[0012] Figure 5 is a schematic diagram of a frequency repetition scheduling method provided in an embodiment of this application;

[0013] Figure 6 is another schematic diagram of the frequency repetition scheduling method provided in the embodiments of this application;

[0014] Figure 7 is a schematic diagram of a structure of control information provided in an embodiment of this application;

[0015] Figure 8 is a schematic diagram of another structure of control information provided in an embodiment of this application;

[0016] Figure 9 is a schematic diagram of a frequency domain allocation indication in the control information provided in an embodiment of this application;

[0017] Figure 10 is another schematic diagram of the frequency domain allocation indication in the control information provided in the embodiments of this application;

[0018] Figure 11 is a schematic flowchart of another data scheduling method provided in an embodiment of this application;

[0019] Figure 12 is a schematic diagram of a data scheduling device provided in an embodiment of this application;

[0020] Figure 13 is a schematic diagram of another structure of the data scheduling device provided in an embodiment of this application;

[0021] Figure 14 is a schematic diagram of a communication node provided in an embodiment of this application. Detailed Implementation

[0022] The data scheduling method provided in this application can be applied to various wireless communication systems, such as Long Term Evolution (LTE) systems, 4th-generation (4G) systems, 5th-generation (5G) systems, LTE and 5G hybrid architecture systems, 5G New Radio (NR) systems, and new communication systems emerging in future communication development, such as 6th-generation (6G) systems. Figure 1 is a schematic diagram of a wireless communication system to which the data scheduling method provided in this application is applicable. As shown in Figure 1, the wireless communication system includes a terminal device 110, an access network device 120, and a core network device 130.

[0023] Terminal device 110 can be a device with wireless transceiver capabilities, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted); on water (such as ships); or in the air (such as airplanes, balloons and satellites). Examples of terminal devices 110 include: UEs, mobile phones, mobile stations, tablets, laptops, Ultra-mobile Personal Computers (UMPCs), handheld computers, netbooks, Personal Digital Assistants (PDAs), and other network-connected user devices; virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.; IoT nodes in the Internet of Things (IoT); in-vehicle communication devices in the Internet of Vehicles (IoV); entertainment and gaming devices or systems; and GPS devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal device 110. Furthermore, the term "terminal device" can be abbreviated as "terminal."

[0024] Access network equipment 120 is an access device through which terminal equipment 110 wirelessly accesses the wireless communication system. It can be a base station, an evolved NodeB (eNB or eNodeB) in Long Term Evolution Advanced (LTE), a transmission reception point (TRP), a base station or gNB in ​​a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a Wireless Fidelity (WiFi) system. Base stations can include various macro base stations, micro base stations, femtocell base stations, wireless remote units, routers, WiFi devices, or various network-side devices such as primary cells and secondary cells, as well as location management function (LMF) devices. It can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU) or a distributed unit (DU). The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. Furthermore, the access network equipment can be simply referred to as a base station.

[0025] Core network equipment 130 may include access and mobility management network elements and session management network elements. For example, terminal equipment 110 can access the core network through access network equipment 120 to achieve data transmission.

[0026] Figure 2 is a flowchart illustrating a data scheduling method provided in an embodiment of this application. As shown in Figure 2, the method is applied to a first communication node. In this embodiment, the first communication node can be a terminal, and the second communication node can be a base station. The method may include:

[0027] S201, Receive configuration information.

[0028] The configuration information is used to configure the frequency domain resources available to the first communication node.

[0029] S202. Based on the configuration information, perform at least one of the following operations: listen to the first physical control channel to obtain control information, receive / transmit the first physical shared channel on one or more specified bandwidth portions, and send hybrid automatic repeat request response information; wherein the first physical shared channel is transmitted on one or more specified bandwidth portions according to a specified scheduling method, and the specified scheduling method includes frequency domain repetitive scheduling.

[0030] Frequency domain repetitive scheduling is used to indicate that the first physical shared channel is repeatedly transmitted on one or more specified bandwidth portions. That is, the first physical shared channel is transmitted on one or more specified bandwidth portions, and the data content (information bits) transmitted on one or more specified bandwidth portions is the same. A complete data block is transmitted on each specified bandwidth portion.

[0031] The aforementioned first physical shared channel includes a physical shared downlink channel and / or a physical shared uplink channel.

[0032] By repeatedly transmitting the first physical shared channel on one or more specified bandwidth portions, if data transmission fails on one specified bandwidth portion, data can still be successfully transmitted on other specified bandwidth portions, thus ensuring the successful transmission of the first physical shared channel. This method can improve the reliability of data transmission.

[0033] Furthermore, by repeatedly transmitting the first physical shared channel over one or more specified bandwidth portions, time-domain repetitive operations can be reduced, data can be transmitted as quickly as possible, data transmission latency can be reduced, and this is more beneficial for latency-sensitive services.

[0034] Configuration information may include at least one of the following: one or more frequency resources, one or more subsets of frequency resources, one or more components, and bandwidth configuration.

[0035] The components include at least one of the following: cell, carrier, frequency band, and bandwidth. The carrier may include an uplink carrier and / or a downlink carrier. The aforementioned cell, uplink carrier, and / or downlink carrier may be a dummy carrier.

[0036] The components mentioned above may be of the same type of resource. For example, they may all be frequency bands or all be carriers. Alternatively, the components may be of different types of resources. For example, one component may be a virtual carrier, and another component may be a frequency band.

[0037] The aforementioned components may include a primary component and / or one or more secondary components.

[0038] The aforementioned frequency resources include uplink frequency resources and / or downlink frequency resources.

[0039] In one example, the frequency resources mentioned above include one or more uplink frequency resources and one or more downlink frequency resources. The number of uplink frequency resources and the number of downlink frequency resources are not necessarily equal. Each uplink frequency resource is associated with one downlink frequency resource. One or more uplink frequency domain resources may be associated with the same downlink frequency domain resource, and one or more downlink frequency domain resources may be associated with the same uplink frequency domain resource. The uplink frequency resources include one or more components / bandwidth portions. The downlink frequency resources include one or more components / bandwidth portions.

[0040] In another example, the frequency domain resources described above include one or more components / bandwidth portions. One of these components includes one or more uplink frequency domain resources and one or more downlink frequency domain resources.

[0041] The aforementioned frequency resources are either cell groups or carrier groups. A cell group contains one or more cells, and a carrier group contains one or more carriers / virtual carriers.

[0042] In one example, the aforementioned frequency resources or subsets of frequency resources are cells.

[0043] The cell may include one or more uplink carriers and one or more downlink carriers. These uplink and / or downlink carriers are virtual carriers. For example, the cell may include one uplink virtual carrier and one downlink virtual carrier. Alternatively, the cell may contain only one uplink virtual carrier.

[0044] In another example, the frequency resources described above are virtual carriers. Alternatively, a subset of the frequency resources may be virtual carriers. The virtual carriers described above include at least one of uplink virtual carriers and downlink virtual carriers. Each virtual carrier may contain one or more frequency bands (i.e., components).

[0045] Two or more frequency bands that are adjacent in frequency band can be included in the same virtual carrier (or virtualized as a single virtual carrier). Two or more frequency bands that are spaced apart by an integer multiple of the subcarrier spacing can be included in the same virtual carrier (or virtualized as a single virtual carrier). Two or more frequency bands that support the same first communication node capability can be included in the same virtual carrier (or virtualized as a single virtual carrier).

[0046] Each component contains (or can be configured with) one or more Bandwidth Parts (BWPs). Only one Bandwidth Part can be active on each component at a time. For example, a frequency resource is composed of frequency bands, and each frequency band has one active Bandwidth Part. As shown in Figure 3, a frequency resource can include multiple frequency resource subsets, each frequency resource subset can include one or more components, each component includes one or more Bandwidth Parts, and only one Bandwidth Part can be active on each component at a time.

[0047] Frequency resources can be carriers or virtual carriers. As shown in Figure 4, the frequency resources mentioned above contain one or more active BWPs (the BWPs can be considered as components).

[0048] In some embodiments, the first communication node listens to the first physical control channel to obtain control information, including: listening to only a specified first physical control channel / control information, or listening to only a specified first physical control channel / control information on a specific component / bandwidth portion.

[0049] A specific component includes at least one of the following: an active component, a primary component, a highest priority component, or a component indicated by a high-level parameter.

[0050] The first communication node listens only on the designated first physical control channel on a specific bandwidth portion. The specific bandwidth portion includes at least one of the following: the active bandwidth portion, the default bandwidth portion, the active bandwidth portion on the primary component, the highest priority bandwidth portion, the active bandwidth portion on the highest priority component, and the bandwidth portion indicated by higher-level parameters.

[0051] The first communication node listens to the designated first physical control channel only on specific components / bandwidth portions, effectively reducing blind detection of control channels on other components / bandwidth portions and reducing power consumption on other components / bandwidth portions, thereby achieving energy saving for the first communication node. Additionally, the second communication node (such as a base station) can also transmit the designated first physical control channel only on specific components / bandwidth portions, thus achieving power saving for the second communication node.

[0052] Secondly, to ensure the transmission of any potential control channels, resources need to be reserved for control channel transmission. However, these reserved resources cannot be used for data transmission, leading to resource waste. Since the first communication node only listens to the designated first physical control channel on a specific component / bandwidth portion, the second communication node can also only transmit on the designated first physical control channel on the same specific component / bandwidth portion. Thus, control channel transmission resources do not need to be reserved on other component / bandwidth portions, and all resources can be used for data transmission. This effectively reduces resource waste.

[0053] The designated first physical control channel includes at least one of the following: scheduling control information, the first physical control channel for bearer group common control information, non-scheduling control information, scheduling control information for cross-component scheduling, and control information in a specific format. The first communication node listens for control information of all formats on the primary component. The first communication node listens for scheduling control information that only supports self-scheduling type on the secondary component; self-scheduling type means that the control information for the scheduling data and the scheduled data are on the same component.

[0054] In some embodiments, the first communication node transmits a first physical shared channel over one or more specified bandwidth portions.

[0055] One or more specified bandwidth portions include at least one of the following:

[0056] Scenario 1: One or more active bandwidth portions on the same cell / carrier / carrier group.

[0057] Multiple active bandwidth portions can be configured on the same cell / carrier. The first physical shared channel (or the scheduled data) can be transmitted on multiple active bandwidth portions, thereby improving data reliability, accelerating data transmission, and reducing transmission latency.

[0058] Scenario 2: One or more active bandwidth portions on the same component.

[0059] Scenario 3: Activated bandwidth portions / frequency resources on one or more components; wherein each component corresponds to one activated bandwidth portion / frequency resource.

[0060] A cell / carrier supports multiple components, such as frequency bands, and one bandwidth portion can be active in each frequency band simultaneously. Scheduled data can be transmitted across components on multiple active bandwidth portions (BWPs) across multiple components. This effectively improves data transmission reliability, accelerates data transmission, and reduces transmission latency.

[0061] Alternatively, one or more specified bandwidth portions are frequency resources on one or more components that do not have configurations such as bandwidth portion indexes.

[0062] One or more specified bandwidth portions are determined by at least one of the following: predefined, second communication node indication, resource occupancy on the component / activated BWP, and transmission type (e.g., first transmission or retransmission).

[0063] One or more specified bandwidth portions are determined by a predefined method. For example, it is predefined that when a scheduling instruction is received on BWP1, the scheduled data will be transmitted on both BWP1 and BWP2. Another example is the predefined BWP selection rule: when a scheduling instruction is received on a BWP, the scheduled data will be transmitted on that BWP and on BWPs with the same bandwidth.

[0064] One or more designated bandwidth portions are determined by the method indicated by the second communication node. This indication can be in the form of Radio Resource Control (RRC) parameters and / or Downlink Control Information (DCI) indication. The DCI indicates one or more designated bandwidth portions by indicating bandwidth portion indices. The DCI indicates one or more designated bandwidth portions in the form of a bitmap. For example, bit "1" corresponds to a designated BWP, and bit "0" corresponds to an undesignated BWP.

[0065] One or more designated bandwidth portions are jointly determined by a predefined method and an indication from a second communication node. For example, n target BWPs are predefined, and the second communication node indicates whether a target BWP is selected. For example, the scheduling DCI includes an indication field to indicate whether a target BWP is a designated BWP for transmitting the first physical shared channel; bit '1' indicates that the predefined target BWP is a designated BWP, and bit '0' indicates that the predefined target BWP is not a designated BWP.

[0066] One or more specified bandwidth portions can also be determined by resource usage on the component / activated BWP.

[0067] The number of specified bandwidth segments can be determined by at least one of the following: predefined, second communication node indication, transmission type (first transmission or retransmission), or service type.

[0068] The number of one or more specified bandwidth portions is determined by the transmission type. For example, for the first physical shared channel of the initial transmission, the number of specified bandwidth portions is 1; for the first physical shared channel of retransmissions, the number of specified bandwidth portions is greater than 1.

[0069] The number of one or more specified bandwidth portions is determined by the service type. For example, for latency-sensitive services, the number of specified bandwidth portions is greater than 1, while for latency-insensitive services, the number of specified bandwidth portions is equal to 1.

[0070] The number of one or more specified bandwidth portions is determined by a predefined method. For example, it is predefined that only one bandwidth portion of scheduling is supported on a certain cell / carrier / component. For example, scheduling information received on a predefined cell / carrier / component is transmitted on only one bandwidth portion. Or, scheduling information received on a predefined cell / carrier / component is transmitted on multiple bandwidth portions.

[0071] The number of one or more specified bandwidth portions is determined by the indication of the second communication node. The second communication node can be indicated via higher-level parameters or DCI.

[0072] The DCI directly indicates the specified bandwidth portion. For example, if the scheduling DCI indicates several target bandwidth portions, then the number of specified bandwidth portions is the same.

[0073] The DCI indicates whether to activate or deactivate the multi-bandwidth portion transmission function. For example, if the DCI indicates activation of the multi-bandwidth portion transmission function at time 1, then after time 1, the first physical shared channel will transmit on multiple bandwidth portions. Conversely, if the DCI indicates deactivation of the multi-bandwidth portion transmission function at time 2, then after time 2, the first physical shared channel will transmit on one bandwidth portion.

[0074] In some implementations, the first communication node may determine the transmission of the first physical shared channel on one or more specified bandwidth portions in a frequency domain repetitive scheduling manner by at least one of the following methods: predefined, higher-layer parameters, signaling indication, transmission type, service type, and the type and capabilities of the first communication node.

[0075] The first communication node determines whether the first physical shared channel adopts frequency domain repetition scheduling in one or more specified bandwidth portions based on the higher layer configuration. That is, whether the physical shared physical channel adopts frequency domain repetition scheduling in one or more specified bandwidth portions is related to the higher layer parameters.

[0076] When a specified parameter is configured or its value is set to a preset value, the first communication node determines that the first physical shared channel transmits in a frequency-domain repetitive scheduling manner over one or more specified bandwidth portions. For example, the specified parameter may include one or more parameters, and any combination of the specified parameters may be the same parameter or different parameters. The value of the specified parameter may be a numeric type, a string, or an enumeration type (e.g., it may be configured to exist or not exist; or, for example, it may be configured to true).

[0077] The first communication node can also determine, based on the control information, whether the first physical shared channel is transmitted in a frequency-domain repetitive scheduling manner on one or more specified bandwidth portions. For example, the first communication node determines whether the first physical shared channel is transmitted in a frequency-domain repetitive scheduling manner on one or more specified bandwidth portions based on one or more fields in the control information.

[0078] This DCI can be a scheduling DCI. One or more of the aforementioned fields indicate the current data scheduling type, which is the transmission method of the first physical shared channel on one or more specified bandwidth portions. For example, a bit field in the DCI contains two bits, which are used to indicate the data scheduling type: "00" indicates self-scheduling, "01" indicates cross-component scheduling, "10" indicates that the first physical shared channel transmitted on one or more specified bandwidth portions uses frequency domain extended scheduling, and "11" indicates that the first physical shared channel transmitted on one or more specified bandwidth portions uses frequency domain repetition scheduling. Alternatively, the DCI may contain a field indicating whether frequency domain repetition scheduling is activated / started. For example, a bit field of "1" indicates that the scheduled first physical shared channel uses frequency domain repetition scheduling, and a bit field of "0" indicates that the scheduled first physical shared channel does not use frequency domain repetition scheduling.

[0079] The data scheduling type can also be indicated through the Media Access Control (MAC CE) element. The MAC CE indicates the data scheduling type semi-statically. That is, the first communication node uses the already indicated or default data scheduling type until it receives a new data scheduling type indication.

[0080] The first communication node can also jointly determine, based on the higher-level configuration and DCI indication, whether the first physical shared channel on one or more specified bandwidths adopts the frequency domain repetitive scheduling method.

[0081] One or more specified bandwidth portions are configured by higher-layer parameters, and the specific data scheduling type is indicated by the DCI. For example, one bit in the DCI is used to indicate the data scheduling type. Bit '0' indicates that the first physical shared channel uses frequency-domain repetitive scheduling for transmission on one or more specified bandwidth portions, and bit '1' indicates that the first physical shared channel uses frequency-domain extended scheduling for transmission on one or more specified bandwidth portions. When the higher-layer parameters configure only one specified bandwidth portion, the bit field used to indicate the data scheduling type is 0 bits or the indication of this bit field is ignored.

[0082] The first communication node determines whether to use frequency-domain repetitive scheduling for transmission of the first physical shared channel based on the transmission type. The transmission type can include initial transmission and retransmission. Initial transmission refers to the first transmission of the first physical shared channel, while retransmission refers to the retransmission of the first physical shared channel. For example, frequency-domain repetitive scheduling is selected for retransmission.

[0083] The first communication node determines whether to use frequency-domain repetitive scheduling for transmission on the first physical shared channel based on the service type. Service types can include latency-sensitive services, latency-insensitive services, and low-latency, high-reliability services. For example, frequency-domain repetitive scheduling is selected for latency-sensitive services or low-latency, high-reliability services.

[0084] Figure 5 illustrates a schematic diagram of a frequency domain repetitive scheduling method provided in an embodiment of this application. As shown in Figure 5, the DCI of the scheduling data is transmitted on component 1, and the scheduled first physical shared channel (or data) is transmitted on component 1, component 2, and component 3, and the data information transmitted on these three components is the same. Figure 6 illustrates another schematic diagram of a frequency domain repetitive scheduling method provided in an embodiment of this application. As shown in Figure 6, the DCI of the scheduling data is transmitted on component 1, and the scheduled first physical shared channel (or data) is transmitted on component 2 and component 3, and the data information transmitted on these two components is the same. Component 1 is the primary component, and the other components are secondary components; or, component 1 and the other components are both secondary components; or, component 1 is a secondary component, and one of the other components is the primary component. The components in Figures 5 and 6 can be active bandwidth portions, or bandwidth portions or frequency resources on a component.

[0085] When the first physical shared channel is transmitted using the frequency domain repetitive scheduling method, the first physical shared channel occupies the same time domain resources in one or more specified bandwidth portions, that is, the first physical shared channel is transmitted on the same symbols in the same time slot; or, the first physical shared channel occupies the same amount of time domain resources in one or more specified bandwidth portions, for example, the number of symbols occupied is equal, but the starting positions may be different.

[0086] The scheduled first physical shared channel is independently channel-coded and rate-matched on one or more designated bandwidth portions, and mapped onto physical resource blocks on one or more designated bandwidth portions. Identical data is transmitted on these corresponding physical resource blocks.

[0087] The first physical shared channel being scheduled employs independent interleaving methods on one or more specified bandwidth sections. That is, whether the scheduled data is interleaved and the interleaving pattern are configured independently on one or more specified bandwidth sections.

[0088] The first physical shared channel that is scheduled adopts a different Transmission Configuration Indication state (TCI state) on one or more specified bandwidth portions.

[0089] Frequency domain repetitive scheduling methods include at least one of the following: dynamic frequency domain repetitive scheduling method, semi-persistent frequency domain repetitive scheduling method, and semi-static frequency domain repetitive scheduling method.

[0090] Dynamic frequency domain repetition scheduling means that the first physical shared channel scheduled each time can be either frequency domain repetition scheduling or not. For example, using DCI to indicate frequency domain repetition scheduling is a dynamic frequency domain repetition scheduling method.

[0091] Semi-persistent frequency domain repetitive scheduling means that once triggered, the frequency domain repetitive scheduling mode is maintained for a period of time until it is stopped.

[0092] When a semi-persistent frequency domain repetitive scheduling method is used, one or more of the following parameters of the transport block size, time domain resource allocation, frequency domain resource allocation, and interleaving type of multiple scheduled data can be configured to be different (e.g., dynamically configurable / indicated).

[0093] Semi-static frequency domain repetitive scheduling refers to the frequency domain repetitive scheduling mode configured by RRC. Starting or stopping the frequency domain repetitive scheduling mode is accomplished through RRC configuration or reconfiguration.

[0094] Semi-static frequency-domain repetitive scheduling refers to scheduling in a frequency-domain repetitive manner, with updates to the scheduling method being semi-static. One or more of the following parameters of the scheduled data—transmit block size, time-domain resource allocation, frequency-domain resource allocation, and interleaving type—can be dynamically configured / indicated.

[0095] Enabling and / or stopping the frequency domain repetitive scheduling mode is achieved through at least one of the following methods: downlink control information indication, media access control element indication, radio resource management configuration / configuration update, timer or condition triggering.

[0096] The conditions for triggering the above conditions may include at least one of the following:

[0097] Method 1: If the first condition is met, the frequency domain repetitive scheduling mode is activated.

[0098] Initiating frequency-domain repetitive scheduling means starting to transmit the first physical shared channel on one or more specified bandwidth portions according to the frequency-domain repetitive scheduling method. The first condition includes at least one of the following: the measurement result of the first communication node (e.g., the Reference Signal Receiving Power (RSRP)) is less than a first threshold, the data transmission delay is greater than a second threshold, the decoding block error rate on one or more specified bandwidth portions is higher than a third threshold, the number of data transmission retransmissions is higher than a fourth threshold, the number of data transmission first transmission failures is higher than a fifth threshold, and the remaining data time is less than a sixth threshold.

[0099] Method 2: Stop the frequency domain repetitive scheduling method if the first condition is not met or the second condition is met.

[0100] Stopping frequency-domain repetitive scheduling means ceasing transmission of the first physical shared channel on one or more designated bandwidth portions according to the frequency-domain repetitive scheduling method. The second condition includes at least one of the following: the measurement result of the first communication node is greater than the seventh threshold, the decoding block error rate on one or more designated bandwidth portions is less than the eighth threshold, and the remaining data time is greater than the ninth threshold.

[0101] The remaining data time is the minimum time required to complete the transmission of the current data packet. The remaining data time is at least one of the following: the time the timer keeps running (if this time is exceeded, the timer times out): drx-onDurationTimer (active timer for discontinuous reception), discardTimer (discard timer), cellDTXDRX-onDurationTimer (active timer for discontinuous transmission and reception in the cell), drx-InactivityTimer (inactive timer for discontinuous reception).

[0102] The scheduled first physical shared channel has the same modulation and coding scheme and transport block size on one or more specified bandwidth portions. The transport block size is related to at least one of the following: the number of frequency domain resources on the specified time domain resources on the bandwidth portion with the smallest bandwidth in the specified bandwidth portion; the number of frequency domain resources on the specified time domain resources on the bandwidth portion with the largest bandwidth in the specified bandwidth portion; the transport block size is less than or equal to the maximum number of resource blocks on the specified time domain resources on any bandwidth portion in the specified bandwidth portion; the transport block size is less than or equal to the maximum number of resource blocks on the specified time domain resources on the bandwidth portion with the largest bandwidth in the specified bandwidth portion.

[0103] The specified time-domain resources include at least one of the following: a time slot, a symbol on a time slot that supports uplink (i.e., the first physical shared channel mentioned above is a physical uplink shared channel), a symbol on a time slot that supports downlink transmission (i.e., the first physical shared channel is a physical downlink shared channel), a symbol on a time slot that can be used to transmit the first physical shared channel, multiple time slots indicated / configured by the second communication node, multiple time slots indicated / configured by the second communication node that can be used to transmit the first physical shared channel, and scheduled time-domain resources.

[0104] The first physical shared channel, when scheduled, uses different redundant versions when transmitting over one or more specified bandwidth portions.

[0105] Redundant versions of data on one or more specified bandwidth portions are determined using predefined, higher-level configuration, or default methods. For example, by default, redundant versions of data on one or more specified bandwidth portions are transmitted with priority given to redundant versions that can be self-decoded.

[0106] Redundant versions of data on one or more specified bandwidth portions are provided by signaling instructions.

[0107] Redundant versions of data on one or more specified bandwidth sections are cyclically assigned based on the default redundancy version order of data retransmission. For example, the redundancy version of data on the first specified bandwidth section is indicated by signaling, while the redundancy versions of data on the remaining specified bandwidth sections are cyclically assigned based on the default redundancy version order of data retransmission. For instance, if the default redundancy version order of data retransmission is redundancy version A → redundancy version B → redundancy version C → redundancy version D, then when the redundancy version of data on the first specified bandwidth section is redundancy version A, the redundancy version of data on the second specified bandwidth section is redundancy version B, and so on. Similarly, if the redundancy version of data on the first specified bandwidth section is redundancy version C, the redundancy version of data on the second specified bandwidth section is redundancy version D, the redundancy version of data on the third specified bandwidth section is redundancy version A, and so on. This method saves signaling indication overhead while ensuring data transmission reliability.

[0108] In the case of periodic second physical shared channel transmissions on one or more specified bandwidth portions (e.g., a configured granted physical uplink shared channel (CG PUSCH) and / or a semi-persistent scheduling physical downlink shared channel (SPS PDSCH)), resources used for transmitting the aforementioned second physical shared channel may be used for transmitting a frequency-repeated first physical shared channel if at least one of the following conditions is met: the first physical shared channel has a higher priority than the second physical shared channel; the second communication node indicates that the aforementioned resources are used for the first physical shared channel; the first physical shared channel is transmitted when the two conflict; or the number of first-transmission failures exceeds a specified threshold.

[0109] In some embodiments, the first communication node listens to the first physical control channel to receive control information carried in the first physical control channel.

[0110] The aforementioned control information may include a first number of bit field blocks and a second number of common bit fields, each bit field block including a third number of bit field segments, wherein the first number, the second number, and the third number are all natural numbers.

[0111] As shown in Figure 7, one bit domain block corresponds to one scheduled component / bandwidth portion, and the first number is equal to the number of scheduled component / bandwidth portions. For example, the first bit domain block corresponds to the first scheduled component / bandwidth portion, the second bit domain block corresponds to the second scheduled component / bandwidth portion, and so on, with the last bit domain block corresponding to the last scheduled component / bandwidth portion. Different bit domain segments within a bit domain block correspond to information about a scheduled component / bandwidth portion, such as the time-domain resource allocation and frequency-domain resource allocation for that component / bandwidth portion.

[0112] Alternatively, as shown in Figure 8, each bit domain segment corresponds to a scheduled component / bandwidth portion, and the third number equals the number of scheduled component / bandwidth portions. For example, the first bit domain segment in each bit domain block corresponds to the first scheduled component / bandwidth portion, the second bit domain segment in each bit domain block corresponds to the second scheduled component / bandwidth portion, and so on, with the last bit domain segment in each bit domain block corresponding to the last scheduled component / bandwidth portion. Each bit domain block represents a type of DCI information; for example, the first bit domain block corresponds to the time-domain resource allocation of all scheduled component / bandwidth portions, the second bit domain block corresponds to the frequency-domain resource allocation of all scheduled component / bandwidth portions, and so on.

[0113] The common bit field is located before the bit field block, or after the bit field block, or both before and after the bit field block.

[0114] The first number of bit field blocks includes at least one of the following:

[0115] Content 1: Component Indicator Field.

[0116] The component indicator field is used to indicate the components being scheduled. The component indicator field consists of one or more segments, each segment indicating an index of a scheduled component.

[0117] By indicating the components to be scheduled, the first communication node can quickly identify the target resource and receive the first physical shared channel.

[0118] Content 2: Bandwidth indicator field.

[0119] The bandwidth segment indicator field is used to indicate the bandwidth segment being scheduled. When the bandwidth segment indicator and the indicated bandwidth segment index are different from the currently active bandwidth segment index (or the active bandwidth segment index on the component), a bandwidth segment switching operation is performed.

[0120] When the bandwidth portion indicator field is not present, the scheduled first physical shared channel transmits on the active bandwidth portion of the scheduled component.

[0121] There are multiple active bandwidth portions on a frequency resource. If the DCI does not include a component indication field, it includes a bandwidth portion indication field, which is used to indicate a specified bandwidth portion for transmitting the first physical shared channel.

[0122] A frequency resource has multiple components, and each component contains one or more bandwidth portions. If the DCI includes a component indication field but not a bandwidth portion indication field, then the specified bandwidth portion for transmitting the first physical shared channel is the active bandwidth portion on the component indicated by the aforementioned DCI.

[0123] A frequency resource has multiple components, and each component contains one or more bandwidth portions. If the DCI includes both a component indication field and a bandwidth portion indication field, the indicated bandwidth portion is the bandwidth portion on the corresponding indicated component.

[0124] Content 3: Time-domain resource allocation information on the scheduled components / bandwidth portions.

[0125] The time-domain resource allocation consists of one or more segments, and the value m of each segment indicates the (m+1)th row of the time-domain resource allocation table.

[0126] Each segment corresponds to a scheduled component / bandwidth portion. For example, each segment indicates the temporal resource allocation of the scheduled data on the corresponding scheduled component.

[0127] The scheduled component / bandwidth portions are mapped to one or more segments in ascending index order. For example, when component 0 and component 2 are scheduled, the first segment of the aforementioned time-domain resource allocation corresponds to the time-domain resource allocation on component 0, and the second segment of the aforementioned time-domain resource allocation corresponds to the time-domain resource allocation on component 2.

[0128] Content 4: Frequency domain resource allocation information on the scheduled components / bandwidth portions.

[0129] Frequency domain resource allocation consists of one or more segments, each segment corresponding to a specified bandwidth portion. For example, each segment indicates the frequency domain resource allocation of scheduled data within the corresponding specified bandwidth portion.

[0130] The scheduled specified bandwidth portion is mapped to one or more segments in ascending order of index or component index. For example, when component 1 and component 3 are scheduled, the first segment of the above frequency domain resource allocation corresponds to the frequency domain resource allocation on component 1, and the second segment of the above frequency domain resource allocation corresponds to the frequency domain resource allocation on component 3.

[0131] The time-frequency resource occupancy on the scheduled component / bandwidth portions varies, therefore, the resource distribution available for transmitting the first physical shared channel may also differ. By specifying the time-frequency domain resources on each component / bandwidth portion separately, the allocation of time-frequency domain resources can be adjusted more flexibly and dynamically, enabling better utilization of resources on a given component / bandwidth portion.

[0132] In some embodiments, a first number of bit domain blocks may include at least one of the following: a first bit mapping information, a second bit mapping information, a third bit mapping information, a fourth number of bandwidth portion indices, a fourth number of time domain resource allocation indications, a fourth number of indices of starting virtual resource blocks, and / or the length of the allocated resource blocks; wherein the fourth number is equal to the number of scheduled components / bandwidth portions.

[0133] Each bit in the first mapping information corresponds to a component or an active component. The length of the first mapping information is equal to the number of configured components or the number of active components. That is, the component indication field can use a bitmap to indicate the components. For example, a bit of '0' indicates that the component corresponding to the current bit is not scheduled, and a bit of '1' indicates that the component corresponding to the current bit is scheduled.

[0134] Each bit in the second bit mapping information corresponds to a bandwidth segment or an active bandwidth segment. The length of the second bit mapping information is equal to the number of configured bandwidth segments or the number of active bandwidth segments. That is, the bandwidth segment indication field can use a bitmap to indicate the bandwidth segment.

[0135] The third bit mapping information, each bit in the third bit mapping information, is used to indicate whether a group of resource blocks in a scheduled specified bandwidth portion has been allocated.

[0136] The fourth number of starting virtual resource blocks and / or the length of the allocated resource blocks. As shown in Figure 9, frequency domain resource allocation can indicate an index of a starting virtual resource block and the length of a fourth number of allocated resource blocks, wherein each allocated resource block length corresponds to a scheduled component / bandwidth portion, the index of the starting virtual resource block corresponds to the virtual index of the first scheduled resource block, and the first resource blocks on each scheduled component have the same virtual index. As shown in Figure 10, frequency domain resource allocation can also indicate a fourth number of starting virtual resource blocks and the length of an allocated resource block, wherein the index of the starting virtual resource block corresponds to the virtual index of the first scheduled resource block, and the number of scheduled resource blocks on each scheduled component is the same.

[0137] The second number of common bit fields include at least one of the following:

[0138] Content 1: Scheduling type indicator field.

[0139] The scheduling type indication field is used to indicate the scheduling type of the first physical shared channel. The scheduling type may include at least one of the following: self-scheduling, cross-component scheduling, frequency domain extended scheduling, and frequency domain repetitive scheduling.

[0140] In one case, the scheduling type indicator field contains one bit. For example, bit '0' and bit '1' are used to indicate whether the current scheduling type is self-scheduled or cross-component scheduling, respectively. As another example, bit '0' and bit '1' indicate frequency-domain extended scheduling or frequency-domain repetitive scheduling, respectively.

[0141] In another case, the scheduling type indicator field contains two bits. For example, bits '00', '01', '10', and '11' each correspond to a scheduling mode.

[0142] In another case, when the scheduling type is self-scheduled, the scheduling type indicator field has a length of 0 bits; when the scheduling type is cross-component scheduling, the scheduling type indicator field has a length of 1 or 2 bits, used to indicate the specific scheduling type, such as frequency domain extended scheduling or frequency domain repetitive scheduling.

[0143] Content 2: Time-domain resource allocation instructions.

[0144] For frequency domain repetitive scheduling, time domain resources are allocated identically across one or more specified bandwidth portions.

[0145] By adopting a unified time-domain resource allocation, the timeline of data transmission can be aligned, and the first communication node can determine the time-domain position of the mixed automatic repeat request response information based on the end time of data transmission. Furthermore, using the same time-domain allocation can effectively save the load of indication signaling and facilitate the merging and decoding by the first communication node, thereby obtaining more accurate decoding results.

[0146] Content 3: Mapping instructions from virtual resource blocks to physical resource blocks.

[0147] Content 4: Redundant Version Indicator.

[0148] The first designated bandwidth portion is transmitted using the redundant version indicated by the DCI, while the remaining designated bandwidth portions are transmitted according to the corresponding redundant version selection rules. The first designated bandwidth portion includes at least one of the following: the bandwidth portion for receiving the DCI, the main bandwidth portion, and the bandwidth portion on the main component.

[0149] By specifying the redundancy version selection rules and indicating the redundancy version on one of the bandwidth portions, the first communication node can accurately identify the redundancy versions on all specified bandwidth portions and effectively reduce the load of the indication signaling.

[0150] Content 5: Index of the starting virtual resource block on the specified bandwidth portion.

[0151] The indexes of the starting virtual resource blocks on the scheduled specified bandwidth portion are the same.

[0152] Content 6: The size of the transport block used for transmitting the first physical shared channel on the specified bandwidth portion.

[0153] In some implementations, the number of RBs indicated by the common bit field is used for all scheduled bandwidth portions, meaning that the transport block size of the first physical shared channel transmitted on all specified bandwidth portions is the same, occupying the same number of RBs.

[0154] Since the first physical shared channel transmitted on the specified bandwidth portion is in frequency domain repetition mode and has the same transport block size, the first physical shared channel occupies the same number of frequency domain resources on the specified bandwidth portion.

[0155] In other implementations, for the frequency-domain repetitive first physical shared channel scheduling method, the time-domain resource allocation, the starting RB index, and the number of RBs used for the first physical shared channel transmission are all the same on the specified bandwidth portion. Therefore, the second communication node only needs to indicate one set of time-frequency domain resource allocation, which can be applied to multiple specified bandwidth portions, thereby saving indication resources.

[0156] In some other implementations, for the frequency-domain repetitive first physical shared channel scheduling method, the time-domain resource allocation and the number of RBs used for the first physical shared channel transmission are the same in the specified bandwidth portion, but the starting RB index in the specified bandwidth portion may be different. This configuration method allows for adjustment of the mapping of the first physical shared channel according to the bandwidth and resource occupancy of different bandwidth portions, making resource configuration more flexible.

[0157] Content 7: Hybrid Automatic Repeat Request Process Number.

[0158] In some cases, the size of the Hybrid Automatic Repeat Request process number bit field is related to at least one of the following: data scheduling type, number of scheduled components / bandwidth portions, and one or more higher-level parameters.

[0159] In other cases, the number of mixed automatic repeat request process number bits is the same for components on the same frequency resource or subset of frequency resources. The number of mixed automatic repeat request process number bits for components on the same frequency resource or subset of frequency resources is equal to the number of mixed automatic repeat request process number bits for that frequency resource or subset of frequency resources.

[0160] In some other cases, the process numbers of the mixed automatic repeat request are the same on multiple components that are scheduled.

[0161] In some embodiments, the first communication node may send a hybrid automatic repeat request response based on the decoding result of the first physical shared channel. The first communication node may receive and decode one or more first physical shared channels on a specified bandwidth portion, or it may decode the received first physical shared channels separately on one or more specified bandwidth portions.

[0162] The hybrid automatic repeat request response information sent by the first communication node satisfies at least one of the following conditions: sent on the main component; sent on the component / bandwidth portion used for transmitting scheduling control information; sent on the component / bandwidth portion with the highest priority among the scheduled components / bandwidth portions; sent on the component / bandwidth portion that completed data scheduling first; sent on the component / bandwidth portion that allows the transmission of the second physical control channel; or sent on all scheduled components / bandwidth portions.

[0163] The frequency domain resources of the hybrid automatic repeat request response information sent by the first communication node include at least one of the following: uplink resources corresponding to the main component; uplink resources corresponding to the component / bandwidth portion used for transmitting scheduling control information; uplink resources corresponding to the component / bandwidth portion with the highest priority among the scheduled components / bandwidth portions; uplink resources corresponding to the component / bandwidth portion that completes data scheduling first; uplink resources corresponding to the component / bandwidth portion that completes data scheduling last; uplink resources that allow transmission of the second physical control channel; and uplink resources corresponding to all scheduled components / bandwidth portions.

[0164] The time-domain resources for the hybrid automatic repeat request response information sent by the first communication node are determined by at least one of the following: the time when the first physical shared channel transmission is completed first, the time when the first physical shared channel transmission is completed last, the time when the first physical shared channel transmission on the main component / bandwidth portion is completed, and the time when the first physical shared channel transmission on the component / bandwidth portion used for transmitting scheduling control information is completed.

[0165] The subcarrier spacing associated with the hybrid automatic repeat request response information includes at least one of the following: a subcarrier spacing for transmitting a component of the hybrid automatic repeat request response value; a subcarrier spacing for receiving the scheduling physical control channel; the minimum of the subcarrier spacing for receiving the scheduling physical control channel and the subcarrier spacing for transmitting the second physical control channel; and the minimum of the subcarrier spacing of the scheduled component / bandwidth portion.

[0166] The hybrid automatic repeat request response value fed back by the first communication node is determined by at least one of the following: if the first physical shared channel on any specified bandwidth portion is successfully received, the hybrid automatic repeat request response value is "ACK"; if the first physical shared channel on all specified bandwidth portions is not successfully received, the hybrid automatic repeat request response value is "NACK"; if the first physical shared channel on one or more specified bandwidth portions is successfully decoded, the hybrid automatic repeat request response value is "ACK".

[0167] The first communication node can also determine the transmission time of the hybrid automatic repeat request response information based on the transmission end time of the last first physical shared channel on one or more specified bandwidth portions.

[0168] The last first physical shared channel is the latest-ending first physical shared channel among one or more first physical shared channels transmitted over one or more specified bandwidth portions.

[0169] In this embodiment, a hybrid automatic repeat request response information is sent through the decoding results of the first physical shared channel on one or more specified bandwidth portions. For example, if the decoding of the first physical shared channel on all specified components fails, a request is made to retransmit the first physical shared channel, thereby improving the reliability of data transmission.

[0170] In some embodiments, a solution to resource conflicts is also provided, specifically:

[0171] When a resource conflict occurs on the scheduled time / frequency domain resources (if other signals or channels are being transmitted), the transmitted signal / channel is determined based on at least one of the following: scheduling type, transmission priority, predefined, signaling indication.

[0172] When resource conflicts occur on scheduled time / frequency domain resources, the signal / channel to be transmitted is determined according to the scheduling type. For example, when a self-scheduled first physical shared channel and a cross-component scheduled first physical shared channel simultaneously occur on the same time / frequency domain resources of a component, the self-scheduled first physical shared channel is transmitted first.

[0173] When resource conflicts occur on scheduled time / frequency domain resources, the transmitted signal is determined according to priority. For example, the Synchronization Signal Block (SSB) has the highest priority; when an SSB is being transmitted on a scheduled time / frequency domain resource, the SSB is transmitted first. As another example, when resource conflicts occur between two physical shared channels, the physical shared channel with the higher priority is transmitted first.

[0174] When resource conflicts occur on scheduled time / frequency domain resources, the signal / channel to be transmitted is determined according to a predefined method. For example, it is predefined that when the first physical shared channel conflicts with other signals / channels, the other signals / channels are transmitted first. As another example, when the initial transmission of the first physical shared channel and the retransmission of the first physical shared channel conflict, the initial transmission of the first physical shared channel is transmitted first.

[0175] When a resource conflict occurs on a scheduled time / frequency domain resource, a signaling indication is used to determine whether to transmit the first physical shared channel on that resource. This signaling is DCI. When the reserved resource indication is '1', the first physical shared channel can be transmitted on the corresponding resource. When the reserved resource indication is '0', the first physical shared channel cannot be transmitted on the corresponding resource.

[0176] Figure 11 is a schematic flowchart of another data scheduling method provided in an embodiment of this application. As shown in Figure 11, the method is applied to a second communication node and may include:

[0177] S1101, Send configuration information; the configuration information is used to configure the frequency domain resources available to the first communication node.

[0178] S1102. Based on the configuration information, perform at least one of the following operations: send control information; transmit / receive a first physical shared channel on one or more specified bandwidth portions; receive hybrid automatic repeat request response information; wherein the first physical shared channel is transmitted on one or more specified bandwidth portions according to a specified scheduling method, the specified scheduling method including frequency domain repetitive scheduling method.

[0179] The reception of a hybrid automatic repeat request response message satisfies at least one of the following conditions: received on the main component; received on the component / bandwidth portion used for transmitting scheduling control information; received on the component / bandwidth portion with the highest priority among the scheduled components / bandwidth portions; received on the component / bandwidth portion that completed data scheduling first; received on the component / bandwidth portion that allows transmission of the second physical control channel; or received on all scheduled components / bandwidth portions.

[0180] The frequency domain resources for the second communication node to receive the hybrid automatic repeat request response information include at least one of the following: uplink resources corresponding to the main component; uplink resources corresponding to the component / bandwidth portion used for transmitting scheduling control information; uplink resources corresponding to the component / bandwidth portion with the highest priority among the scheduled components / bandwidth portions; uplink resources corresponding to the component / bandwidth portion that completes data scheduling first; uplink resources corresponding to the component / bandwidth portion that completes data scheduling last; uplink resources that allow transmission of the second physical control channel; and uplink resources corresponding to all scheduled components / bandwidth portions.

[0181] The time-domain resources for the second communication node to receive the hybrid automatic repeat request response information are determined by at least one of the following: the time when the first physical shared channel transmission is completed first, the time when the first physical shared channel transmission is completed last, the time when the first physical shared channel transmission on the main component / bandwidth portion is completed, and the time when the first physical shared channel transmission on the component / bandwidth portion used for transmitting scheduling control information is completed.

[0182] The technical description in this embodiment is similar in principle, process and effect to the description in the embodiment for the first communication node side above, and will not be repeated here for the sake of brevity.

[0183] Figure 12 is a schematic diagram of a data scheduling device provided in an embodiment of this application. The device is integrated into a first communication node. As shown in Figure 12, the device may include a receiving module 1201 and a transmitting module 1202.

[0184] The receiving module 1201 is used to receive configuration information; the configuration information is used to configure the frequency domain resources that the first communication node can use; the receiving module 1201 is also used to perform at least one of the following operations according to the configuration information: listen to the first physical control channel to obtain control information; receive / transmit the first physical shared channel on one or more specified bandwidth portions; wherein the first physical shared channel is transmitted on one or more specified bandwidth portions according to a specified scheduling method, the specified scheduling method including frequency domain repetitive scheduling method; the sending module 1202 is used to send hybrid automatic repeat request response information.

[0185] Based on the above embodiments, the configuration information includes at least one of the following: one or more frequency resources, a subset of one or more frequency resources, one or more components, and bandwidth configuration; wherein, the components include at least one of the following: cell, carrier, frequency band, and bandwidth.

[0186] Based on the above embodiments, one or more designated bandwidth portions include at least one of the following: one or more active bandwidth portions on the same cell / carrier / carrier group; one or more active bandwidth portions on the same component; active bandwidth portions / frequency resources on one or more components; wherein each component corresponds to one active bandwidth portion / frequency resource.

[0187] Based on the above embodiments, the device further includes a processing module, which is used to determine, by at least one of the following methods, that the first physical shared channel is transmitted in a frequency domain repetitive scheduling manner over one or more specified bandwidth portions: predefined, higher layer parameters, signaling indication, transmission type, service type, type and capability of the first communication node.

[0188] Based on the above embodiments, the processing module is further configured to: determine that the first physical shared channel is transmitted in a frequency domain repetitive scheduling manner on one or more specified bandwidth portions when a specified parameter is configured or the value of the specified parameter is configured to a preset value; and determine that the first physical shared channel is transmitted in a frequency domain repetitive scheduling manner on one or more specified bandwidth portions according to control information.

[0189] Based on the above embodiments, the frequency domain repetitive scheduling method is used to indicate the repeated transmission of the first physical shared channel on one or more specified bandwidth portions.

[0190] Based on the above embodiments, when transmitting the first physical shared channel using a frequency domain repetitive scheduling method, it further includes at least one of the following: the first physical shared channel occupies the same time domain resources on one or more specified bandwidth portions; the first physical shared channel occupies the same amount of time domain resources on one or more specified bandwidth portions.

[0191] Based on the above embodiments, the frequency domain repetition scheduling method includes at least one of the following: dynamic frequency domain repetition scheduling method, semi-persistent frequency domain repetition scheduling method, and semi-static frequency domain repetition scheduling method.

[0192] Based on the above embodiments, the activation and / or deactivation of the frequency domain repetitive scheduling mode can be achieved through at least one of the following methods: downlink control information indication, media access control element indication, radio resource management configuration / configuration update, timer or condition triggering.

[0193] Based on the above embodiments, the condition triggering includes at least one of the following: if the first condition is met, the frequency domain repetitive scheduling mode is started; if the first condition is not met or the second condition is met, the frequency domain repetitive scheduling mode is stopped; wherein, the first condition includes at least one of the following: the measurement result of the first communication node is less than a first threshold, the data transmission delay is greater than a second threshold, the decoding block error rate on one or more specified bandwidth portions is higher than a third threshold, the number of data transmission retransmissions is higher than a fourth threshold, the number of data transmission first transmission failures is higher than a fifth threshold, and the remaining data time is less than a sixth threshold; the second condition includes at least one of the following: the measurement result of the first communication node is greater than a seventh threshold, the decoding block error rate on one or more specified bandwidth portions is lower than an eighth threshold, and the remaining data time is greater than a ninth threshold.

[0194] Based on the above embodiments, the first physical shared channel has the same modulation and coding scheme and transport block size on one or more specified bandwidth portions.

[0195] Based on the above embodiments, the size of the transport block is related to at least one of the following: the number of frequency domain resources on the specified time domain resources on the bandwidth portion with the smallest bandwidth in the specified bandwidth portion; the number of frequency domain resources on the specified time domain resources on the bandwidth portion with the largest bandwidth in the specified bandwidth portion; the size of the transport block is less than or equal to the maximum number of resource blocks on the specified time domain resources on any bandwidth portion in the specified bandwidth portion; the size of the transport block is less than or equal to the maximum number of resource blocks on the specified time domain resources on the bandwidth portion with the largest bandwidth in the specified bandwidth portion.

[0196] Based on the above embodiments, the first physical shared channel employs different redundancy versions when transmitting over one or more specified bandwidth portions.

[0197] Based on the above embodiments, the processing module is also used to determine the redundant version through at least one of the following methods: predefined, higher-level configuration, default method, default redundant version sequential loop based on data retransmission, and signaling indication.

[0198] Based on the above embodiments, the control information includes a first number of bit domain blocks and a second number of common bit domains, each bit domain block including a third number of bit domain segments; wherein, one bit domain block corresponds to one scheduled component / bandwidth portion, and the first number is equal to the number of scheduled component / bandwidth portions; or, wherein, one bit domain segment corresponds to one scheduled component / bandwidth portion, and the third number is equal to the number of scheduled component / bandwidth portions, and the first number, the second number, and the third number are all natural numbers.

[0199] Based on the above embodiments, the first number of bit domain blocks includes at least one of the following: a first bit mapping information, each bit in the first bit mapping information corresponding to a component or an active component, the length of the first bit mapping information being equal to the number of configured components or the number of active components; a second bit mapping information, each bit in the second bit mapping information corresponding to a bandwidth portion or an active bandwidth portion, the length of the second bit mapping information being equal to the number of configured bandwidth portions or the number of active bandwidth portions; a third bit mapping information, each bit in the third bit mapping information used to indicate whether a group of resource blocks in a scheduled specified bandwidth portion is allocated; a fourth number of bandwidth portion indices; a fourth number of time-domain resource allocation indications; a fourth number of indices of starting virtual resource blocks and / or the length of the allocated resource blocks; wherein, the fourth number is equal to the number of scheduled components / bandwidth portions.

[0200] Based on the above embodiments, the second number of common bit fields include at least one of the following: a scheduling type indicator field; the scheduling type indicator field is used to indicate the scheduling type of the first physical shared channel; time-domain resource allocation; a mapping indicator from virtual resource blocks to physical resource blocks; a redundancy version indicator; an index of the starting virtual resource block on the specified bandwidth portion; a transport block size used for transmitting the first physical shared channel on the specified bandwidth portion; and a hybrid automatic repeat request process number.

[0201] Based on the above embodiments, the frequency domain resources for the hybrid automatic repeat request response information include at least one of the following: uplink resources corresponding to the main component; uplink resources corresponding to the component / bandwidth portion used for transmitting scheduling control information; uplink resources corresponding to the component / bandwidth portion with the highest priority among the scheduled components / bandwidth portions; uplink resources corresponding to the component / bandwidth portion that completes data scheduling first; uplink resources corresponding to the component / bandwidth portion that completes data scheduling last; uplink resources that allow transmission of the second physical control channel; and uplink resources corresponding to all scheduled components / bandwidth portions.

[0202] Based on the above embodiments, the subcarrier spacing associated with the hybrid automatic repeat request response information includes at least one of the following: a subcarrier spacing for transmitting a component of the hybrid automatic repeat request response value; a subcarrier spacing for receiving the scheduling physical control channel; the minimum of the subcarrier spacing for receiving the scheduling physical control channel and the subcarrier spacing for transmitting the second physical control channel; and the minimum of the subcarrier spacing of the scheduled component / bandwidth portion.

[0203] Based on the above embodiments, when there is a second physical shared channel with periodic transmission on a specified bandwidth portion, the resources used for transmitting the second physical shared channel can be used to transmit the first physical shared channel if at least one of the following conditions is met: the first physical shared channel has a higher priority than the second physical shared channel; the second communication node indicates that the above resources are used for the first physical shared channel; the first physical shared channel is transmitted when the two conflict; the number of first transmission failures is higher than a specified threshold.

[0204] Based on the above embodiments, it further includes at least one of the following: the first physical shared channel on any specified bandwidth portion is successfully received, and the hybrid automatic repeat request response is 'ACK'; the first physical shared channel on one or more specified bandwidth portions is successfully decoded, and the hybrid automatic repeat request response is 'ACK'; the first physical shared channel on all specified components is not successfully received, and the hybrid automatic repeat request response is 'NACK'.

[0205] Figure 13 is a schematic diagram of another structure of the data scheduling device provided in an embodiment of this application. As shown in Figure 13, the device is integrated into the second communication node and includes a transmitting module 1301 and a receiving module 1302.

[0206] The sending module 1301 is used to send configuration information; the configuration information is used to configure the frequency domain resources that the first communication node can use; the sending module 1301 is also used to perform at least one of the following operations according to the configuration information: sending control information; transmitting / receiving a first physical shared channel on one or more specified bandwidth portions; wherein the first physical shared channel is transmitted on one or more specified bandwidth portions according to a specified scheduling method, the specified scheduling method including frequency domain repetitive scheduling method; the receiving module 1302 is used to receive hybrid automatic repeat request response information.

[0207] In one embodiment, a communication node is also provided, which can be a first communication node (such as a terminal) or a second communication node (such as a base station). The internal structure of the communication node is shown in Figure 14. The communication node includes a processor, memory, network interface, and database connected via a system bus. The processor of the communication node provides computing and control capabilities. The memory of the communication node includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the communication node stores data involved in the data scheduling process. The network interface of the communication node is used to communicate with external terminals via a network connection. When the computer program is executed by the processor, it implements a data scheduling method.

[0208] Those skilled in the art will understand that the structure shown in Figure 14 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the communication nodes to which the present application is applied. Specific communication nodes may include more or fewer components than those shown in the figure, or may combine certain components, or may have different component arrangements.

[0209] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the data scheduling method provided in any of the above embodiments.

[0210] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0211] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0212] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0213] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0214] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0215] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0216] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0217] Any block diagram of logical flow in the accompanying drawings of this application may represent program operations, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program operations and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A data scheduling method applied to a first communication node, comprising: receiving configuration information; the configuration information is used to configure frequency domain resources available to the first communication node; and performing at least one of the following operations according to the configuration information: monitoring a first physical control channel to obtain control information; receiving / transmitting a first physical shared channel on at least one designated bandwidth part; wherein the first physical shared channel is transmitted on the at least one designated bandwidth part according to a designated scheduling manner, and the designated scheduling manner comprises a frequency domain repetition scheduling manner; and transmitting a hybrid automatic repeat request acknowledgement information. The configuration information comprises at least one of the following: at least one frequency resource, a subset of at least one frequency resource, at least one component, and a bandwidth part configuration; wherein the component comprises at least one of the following: a cell, a carrier, a frequency band, and a bandwidth part. The at least one designated bandwidth part comprises at least one of the following: at least one activated bandwidth part on a same cell / carrier / carrier group; at least one activated bandwidth part on a same component; and an activated bandwidth part / frequency resource on at least one component; wherein each component corresponds to an activated bandwidth part / frequency resource. The first physical shared channel is transmitted on the at least one designated bandwidth part according to the frequency domain repetition scheduling manner by at least one of the following: predefinition, a high layer parameter, signaling indication, transmission type, service type, type and capability of the first communication node.

5. The method according to claim 4, further comprising at least one of the following: determining that the first physical shared channel is transmitted on the at least one designated bandwidth part according to the frequency domain repetition scheduling manner in a case that a designated parameter or a value of the designated parameter is configured as a preset value; and determining that the first physical shared channel is transmitted on the at least one designated bandwidth part according to the frequency domain repetition scheduling manner according to the control information. The frequency domain repetition scheduling manner is used to represent that the first physical shared channel is repeatedly transmitted on the at least one designated bandwidth part. In a case that the first physical shared channel is transmitted by using the frequency domain repetition scheduling manner, further comprising at least one of the following: the first physical shared channel occupies a same time domain resource on the at least one designated bandwidth part; and the first physical shared channel occupies a same size of time domain resource on the at least one designated bandwidth part. The frequency domain repetition scheduling manner comprises at least one of the following: a dynamic frequency domain repetition scheduling manner, a semi-persistent frequency domain repetition scheduling manner, and a semi-static frequency domain repetition scheduling manner. The starting and / or stopping of the frequency domain repetition scheduling manner is realized by at least one of the following: downlink control information indication, medium access control control element indication, radio resource management configuration / configuration update, timer, or condition triggering. The condition triggering comprises at least one of the following: starting the frequency domain repetition scheduling manner when a first condition is met; and stopping the frequency domain repetition scheduling manner when a first condition is not met or a second condition is met. ​ ​ ​ ​ ​ ​ 2. The method of claim 1, wherein, ​ ​ 3. The method of claim 1, wherein, ​ ​ ​ ​ 4. The method of claim 1, wherein, ​ ​ ​ ​ ​ 6. The method of claim 1, wherein, ​ 7. The method of claim 1, wherein, ​ ​ ​ 8. The method of claim 1, wherein, ​ ​ 9. The method of claim 1, wherein, ​ ​ 10. The method of claim 9, wherein, ​ ​ ​ The first condition comprises at least one of the following: a measurement result of the first communication node is less than a first threshold value, a time delay of data transmission is greater than a second threshold value, a block error rate of decoding on the at least one specified bandwidth part is higher than a third threshold value, a number of retransmissions of data transmission is higher than a fourth threshold value, a number of initial transmission failures of data transmission is higher than a fifth threshold value, and a data remaining time is less than a sixth threshold value. The second condition comprises at least one of the following: the measurement result of the first communication node is greater than a seventh threshold value, the block error rate of decoding on the at least one specified bandwidth part is lower than an eighth threshold value, and the data remaining time is greater than a ninth threshold value.

11. The method of claim 1, wherein, The first physical shared channel has the same modulation and coding scheme and transport block size on the at least one specified bandwidth part.

12. The method of claim 11, wherein, The size of the transport block is related to at least one of the following: a number of frequency domain resources on a specified time domain resource on a bandwidth part with the smallest bandwidth in the specified bandwidth parts; a number of frequency domain resources on a specified time domain resource on a bandwidth part with the largest bandwidth in the specified bandwidth parts; the size of the transport block is less than or equal to a maximum number of resource blocks on a specified time domain resource on one of the bandwidth parts in the specified bandwidth parts; the size of the transport block is less than or equal to a maximum number of resource blocks on a specified time domain resource on a bandwidth part with the largest bandwidth in the specified bandwidth parts.

13. The method of claim 1, wherein, The first physical shared channel uses different redundancy versions when transmitted on the at least one specified bandwidth part.

14. The method of claim 13, wherein, The redundancy version is determined in at least one of the following ways: predefined, high-layer configuration, default manner, default redundancy version sequence cycle based on data retransmission, and signaling indication.

15. The method of claim 1, wherein, The control information comprises a first number of bit field blocks and a second number of common bit fields, each bit field block comprising a third number of bit field segments; wherein one bit field block corresponds to one scheduled component / bandwidth part, and the first number is equal to the number of scheduled components / bandwidth parts; or wherein one bit field segment corresponds to one scheduled component / bandwidth part, and the third number is equal to the number of scheduled components / bandwidth parts, and the first number, the second number and the third number are natural numbers.

16. The method of claim 15, wherein, The first number of bit field blocks comprises at least one of the following: first bitmap information, each bit in the first bitmap information corresponding to one component or one activated component, and the length of the first bitmap information being equal to the number of configured components or the number of activated components; second bitmap information, each bit in the second bitmap information corresponding to one bandwidth part or one activated bandwidth part, and the length of the second bitmap information being equal to the number of configured bandwidth parts or the number of activated bandwidth parts; third bitmap information, each bit in the third bitmap information being used to indicate whether a resource block group in the one scheduled specified bandwidth part is allocated; a fourth number of bandwidth part indexes; a fourth number of time domain resource allocation indications; a fourth number of indexes of starting virtual resource blocks and / or lengths of allocated resource blocks; The fourth quantity is equal to the number of scheduled component parts / bandwidth parts.

17. The method of claim 15, wherein, The second number of common bit fields includes at least one of the following: a scheduling type indication field, which is used to indicate the scheduling type of the first physical shared channel; a time domain resource allocation indication; a virtual resource block to physical resource block mapping indication; a redundancy version indication; an index of a starting virtual resource block on the specified bandwidth part; a transport block size used for transmitting the first physical shared channel on the specified bandwidth part; a hybrid automatic repeat request process number.

18. The method of claim 1, wherein, The frequency domain resource of the hybrid automatic repeat request acknowledgement information includes at least one of the following: uplink resources corresponding to a primary component part; uplink resources corresponding to a component part / bandwidth part used for transmitting scheduling control information; uplink resources corresponding to a component part / bandwidth part with the highest priority among the scheduled component parts / bandwidth parts; uplink resources corresponding to a component part / bandwidth part that completes data scheduling first; uplink resources corresponding to a component part / bandwidth part that completes data scheduling last; uplink resources allowing transmission of a second physical control channel; uplink resources corresponding to all scheduled component parts / bandwidth parts.

19. The method of claim 1, wherein, The subcarrier spacing associated with the hybrid automatic repeat request acknowledgement information includes at least one of the following: a subcarrier spacing of a component part used for transmitting a hybrid automatic repeat request acknowledgement value; a subcarrier spacing used for receiving a scheduling physical control channel; a minimum value of a subcarrier spacing used for receiving a scheduling physical control channel and a subcarrier spacing used for transmitting a second physical control channel; a minimum value of a subcarrier spacing of a scheduled component part / bandwidth part.

20. The method of claim 1, wherein, In the case where there is a periodically transmitted second physical shared channel on the specified bandwidth part, the resource used for transmitting the second physical shared channel can be used for transmitting the first physical shared channel if at least one of the following conditions is met: the priority of the first physical shared channel is higher than that of the second physical shared channel; the second communication node indicates that the resource of the second physical shared channel is used for the first physical shared channel; the first physical shared channel is predefined to be transmitted when it conflicts with the second physical shared channel; the number of data transmission initial transmission failures is higher than a specified threshold.

21. The method of claim 1, further comprising at least one of the following: the first physical shared channel on a specified bandwidth part is successfully received, and the hybrid automatic repeat request acknowledgement is ‘ACK’; the first physical shared channel on at least one specified bandwidth part is successfully combined and decoded, and the hybrid automatic repeat request acknowledgement is ‘ACK’; the first physical shared channel on all specified component parts is not successfully received, and the hybrid automatic repeat request acknowledgement is ‘NACK’.

22. A data scheduling method applied to a second communication node, comprising: sending configuration information; the configuration information is used to configure the frequency domain resources available to a first communication node; according to the configuration information, at least one of the following operations is performed: sending control information; transmit / receive a first physical shared channel on at least one designated bandwidth part; wherein the first physical shared channel is transmitted on the at least one designated bandwidth part according to a designated scheduling manner, the designated scheduling manner comprising a frequency domain repetition scheduling manner; receive hybrid automatic repeat request acknowledgement information.

23. A communication node, comprising: A memory and a processor, the memory stores a computer program, and the processor implements the method in any one of claims 1-22 when executing the computer program. 24.A computer readable storage medium, the storage medium stores a computer program, and the computer program implements the method in any one of claims 1-22 when executed by a processor.

Images