Data scheduling method, device and computer-readable storage medium

Abstract

Provided in the present application are 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 frequency-domain resources available to a first communication node; and on the basis of the configuration information, executing at least one of the following operations: monitoring a first physical control channel, so as to acquire control information, receiving / transmitting a physical shared channel on one or more designated bandwidth parts, and sending hybrid automatic repeat request acknowledgment information, wherein the physical shared channel is transmitted on the designated bandwidth parts according to a designated scheduling mode, and the designated scheduling mode comprises a frequency-domain extension 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: listening to a first physical control channel to obtain control information; receiving / transmitting a physical shared channel on one or more specified bandwidth portions; wherein the 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 extended 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; sending / receiving a physical shared channel on one or more specified bandwidth portions; wherein the 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 extended 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 allocation method provided in an embodiment of this application;

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

[0012] Figure 5 is a schematic diagram of a data self-scheduling method provided in an embodiment of this application;

[0013] Figure 6 is a schematic diagram of a frequency spread scheduling method provided in an embodiment of this application;

[0014] Figure 7 is another schematic diagram of the frequency spread scheduling method provided in the embodiments of this application;

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

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

[0017] Figure 10 is a schematic diagram of another data scheduling method provided in an embodiment of this application;

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

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

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

[0021] 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.

[0022] 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."

[0023] 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.

[0024] 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.

[0025] 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:

[0026] S201, Receive configuration information.

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

[0028] 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 physical shared channel on one or more specified bandwidth portions, and send hybrid automatic repeat request response information; wherein the 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 extended scheduling method.

[0029] The physical shared channel includes the Physical Uplink Shared Channel (PUSCH) and / or the Physical Downlink Shared Channel (PDSCH).

[0030] Frequency domain spread scheduling is used to represent the transmission of a portion of the physical shared channel on multiple specified bandwidth portions. That is, a portion of the physical shared channel is transmitted on each specified bandwidth portion, and the portions transmitted on multiple specified bandwidth portions are combined to form the physical shared channel.

[0031] The scheduled physical shared channel is transmitted on one or more designated bandwidth portions through frequency domain extended scheduling. If some data transmission on a designated bandwidth portion fails, some data on other designated bandwidth portions can still be transmitted successfully, so that the physical shared channel is not completely lost. This method can improve the reliability of data transmission.

[0032] Furthermore, transmitting the physical shared channel in a frequency-domain-spread manner over one or more designated bandwidth portions is equivalent to expanding the available frequency domain resources. This enables faster data transmission, reduces data transmission latency, and is more beneficial for latency-sensitive services. Especially for large packet services, frequency-domain-spread transmission avoids packet splitting operations, reduces time-domain expansion, and significantly reduces transmission latency.

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

[0034] 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.

[0035] The components described 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.

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

[0037] 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.

[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] In one example, the aforementioned frequency resources or subsets of frequency resources are cells.

[0042] 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.

[0043] 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).

[0044] 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).

[0045] 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.

[0046] 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 are components).

[0047] 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.

[0048] 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.

[0049] 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.

[0050] The first communication node listens to the designated first physical control channel only on specific components / bandwidth portions, which effectively reduces blind detection of control channels on other components / bandwidth portions and reduces power consumption on other components / bandwidth portions, thereby achieving energy saving for the first communication node (such as a terminal). Similarly, 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.

[0051] Secondly, to ensure the transmission of any control channels that may be needed, resources must be reserved for control channel transmission. 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 transmit the designated first physical control channel only on that specific component / bandwidth portion. Thus, control channel transmission resources do not need to be reserved on the remaining component / bandwidth portions, and all resources can be used for data transmission. This effectively reduces resource waste.

[0052] The designated first physical control channel includes at least one of the following: scheduling control information, a 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 types on the secondary component. Figure 5 shows a schematic diagram of a data self-scheduling method provided in an embodiment of this application. As shown in Figure 5, self-scheduling type means that the control information for scheduling data and the data being scheduled are on the same component.

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

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

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

[0056] Multiple active bandwidth portions can be configured on the same cell / carrier. Scheduled physical shared channels (or scheduled data) can be transmitted on these multiple active bandwidth portions, thereby improving reliability, accelerating data transmission, and reducing transmission latency. Furthermore, the first communication node receives physical shared channels on multiple active bandwidth portions. If some data transmission fails on one specified bandwidth portion, some data transmission succeeds on others, preventing the complete loss of the physical shared channel. This method improves data transmission reliability.

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

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

[0059] 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.

[0060] 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.

[0061] 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).

[0062] 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.

[0063] 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.

[0064] 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 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.

[0065] One or more specified bandwidth portions can be determined by the resource occupancy on the component / activated BWP. For example, a component / activated BWP with unoccupied resources can be designated as the specified BWP, while a component / activated BWP with occupied resources cannot be designated as the specified BWP.

[0066] The aforementioned multiple designated bandwidth portions meet at least one of the following conditions: they belong to the same frequency band, the interval between the frequency bands is less than a first preset value, the interval between the frequency bands is an integer multiple of the subcarrier interval, the frequency bands support the same terminal capabilities, have the same interleaving parameter configuration, have the same resource block group size, have the same resource block binding type configuration, have the same resource allocation type, have the same automatic request backhaul processing number size, have the same modulation and coding table, and belong to the same bandwidth portion group.

[0067] When the scheduled physical shared channel is transmitted in a frequency domain spread manner on multiple components / bandwidth portions, the information transmitted on multiple specified components / bandwidth portions will be merged and decoded. Therefore, multiple specified components / bandwidth portions must meet one or more of the above conditions.

[0068] After being processed by a preset method, the physical shared channel is mapped to multiple designated bandwidth portions, and each designated bandwidth portion maps to a portion of the physical shared channel content. Figure 6 shows a schematic diagram of a frequency spread 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 physical shared channel (or data) is transmitted on component 1 and component 2. Component 1 and component 2 only transmit a portion of the physical shared channel content, i.e., the same physical shared channel is scheduled on multiple components. Similarly, Figure 7 shows another schematic diagram of a frequency spread scheduling method provided in an embodiment of this application. As shown in Figure 7, the DCI of the scheduling data is transmitted on component 1, and the scheduled physical shared channel (or data) is transmitted on component 2 and component 3. Component 2 and component 3 only transmit a portion of the physical shared channel content, i.e., the same physical shared channel is scheduled on multiple components. Here, 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 6 and 7 can be active BWPs, or BWPs or frequency resources on the components. The shaded areas in Figures 6 and 7 represent parts of the scheduled physical shared channels.

[0069] The aforementioned preset processing methods include: channel coding and / or rate matching.

[0070] The number of Physical Resource Blocks (PRBs) on multiple specified bandwidth sections is equal, or the number of PRBs on different specified bandwidth sections is determined by the second communication node, meaning the number of PRBs on different specified bandwidth sections may not be equal.

[0071] When a physical shared channel is transmitted over multiple specified bandwidth portions, it occupies the same time domain resources, that is, it is transmitted on the same symbols in the same time slot.

[0072] The physical shared channel is mapped onto the plurality of specified bandwidth portions according to at least one of the following:

[0073] Method 1: Perform interleaving mapping separately on multiple specified bandwidth sections according to the interleaving parameters on the multiple specified bandwidth sections.

[0074] When a physical shared channel is mapped onto n physical resources, interleaving mapping is performed on the n physical resources according to the interleaving parameters of the n physical resources, and no interleaving is performed between the n physical resources.

[0075] When a physical shared channel is mapped to n parts of physical resources, the mapping is performed in ascending order according to the component / bandwidth index corresponding to the n parts of physical resources.

[0076] Each part of physical resources corresponds to a specified bandwidth portion; that is, each part of physical resources belongs to a corresponding bandwidth portion. The physical resources here can include at least one of the following: Resource Element (RE), PRB, or Resource Block Group (RBG).

[0077] Method 2: Virtually map multiple specified bandwidth portions as a single physical resource set.

[0078] When a physical shared channel is mapped onto n parts of physical resources, these n parts of physical resources are virtualized into a single physical resource set for interleaving mapping. Virtualizing these n parts of physical resources into a single physical resource set means using the same mapping rules to support interleaving between physical resources.

[0079] Interleaving and mapping n parts of physical resources into a single physical resource set refers to uniformly mapping the n parts of physical resources. The n parts of physical resources are virtualized as a large bandwidth portion. The n parts of physical resources are virtualized into a single physical resource set in ascending order of their corresponding component / bandwidth portion indices. The n parts of physical resources are virtualized into a single physical resource set according to frequency domain order (e.g., low frequency first, then high frequency, or high frequency first, then low frequency).

[0080] The physical shared channel is mapped to the virtual physical resource set through interleaving, which is done by first interleaving in the frequency domain and then in the time domain.

[0081] Multiple specified bandwidth portions can be associated with the same Transmission Configuration Indicator (TCI) state when they are transmitted, and multiple specified bandwidth portions can also be associated with different TCI states when they are transmitted, that is, different quasi-co-address assumptions are adopted.

[0082] The first communication node receives data from multiple specified bandwidth portions and then merges and decodes them.

[0083] In this way, the second communication node can flexibly allocate the data that can be transmitted on different components / bandwidth sections, making rational use of the resources on multiple components / bandwidth sections. Furthermore, if data reception fails on one component / bandwidth section, the remaining data on the physically shared channel can still be transmitted on another component / bandwidth section, thereby improving the reliability of data transmission.

[0084] The first communication node can determine the transmission of the physical shared channel on one or more specified bandwidth portions in a frequency domain extended scheduling manner through 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.

[0085] The first communication node determines, based on the higher-layer configuration, whether one or more physical shared channels transmitted on a specified bandwidth portion belong to the same transport block. In other words, whether physical shared channels on one or more specified bandwidth portions belong to the same transport block is related to the higher-layer parameters.

[0086] For example, when a specified parameter is configured or the value of the specified parameter is configured to a second preset value, the first communication node determines that the physical shared channel transmits in a frequency domain extended 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).

[0087] In some implementations, the first communication node may also determine, based on one or more fields in the control information, that the physical shared channel will be transmitted in a frequency domain extended scheduling manner over one or more specified bandwidth portions.

[0088] This DCI can be a scheduling DCI. One or more of the above fields are used to indicate the current data scheduling type, which is the transmission method of the 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, such as "00" for self-scheduling, "01" for cross-component scheduling, "10" for indicating that the physical shared channel transmitted on one or more BWPs uses frequency-domain extended scheduling, and "11" for indicating that the physical shared channel content transmitted on one or more BWPs is the same. Alternatively, a bit field in the DCI may contain one bit, used to indicate whether the current data scheduling method is frequency-domain extended scheduling, such as "0" for indicating non-frequency-domain extended scheduling and "1" for indicating frequency-domain extended scheduling.

[0089] In some implementations, the data scheduling type can also be indicated by the control element of the Media Access Control (MAC CE).

[0090] In some implementations, the first communication node can also determine, based on higher-layer configuration and DCI indication, whether the physical shared channels on one or more specified bandwidths adopt frequency domain extended scheduling. For example, one or more specified bandwidths are configured by higher-layer parameters, and the specific data scheduling type is indicated by DCI.

[0091] The transport block size of a physical shared channel is less than or equal to the total number of frequency domain resources in a specified time domain for one or more specified bandwidth portions.

[0092] Frequency domain resources can be RE, RB, or RBG, etc. The number of physical shared channel resources mapped on one or more specified bandwidth portions is less than or equal to the total number of frequency domain resources on the specified time domain resources for one or more specified bandwidth portions. The specified time domain resources include at least one of the following: a timeslot, a symbol supporting uplink (i.e., the physical shared channel is a physical uplink shared channel) on a timeslot, a symbol supporting downlink transmission on a timeslot (the physical shared channel is a physical downlink shared channel), a symbol available for transmitting the physical shared channel on a timeslot, multiple timeslots indicated / configured by a second communication node, multiple timeslots indicated / configured by a second communication node available for transmitting the physical shared channel, scheduled time domain resources, etc.

[0093] In the presence of periodically transmitted physical shared channels on one or more specified bandwidth portions (e.g., the periodically transmitted physical shared channel may be a configured grant physical uplink shared channel (CG PUSCH) and / or a semi-persistent scheduling physical downlink shared channel (SPS PDSCH)), resources used for transmitting the aforementioned periodically transmitted physical shared channel (here referred to as the second physical shared channel) may be used for transmitting a frequency-domain extended physical shared channel (here referred to as 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 aforementioned resources are used for the first physical shared channel; the first physical shared channel is transmitted when the two conflict; and the number of first-transmission failures exceeds a specified threshold.

[0094] 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.

[0095] 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.

[0096] As shown in Figure 8, 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.

[0097] Alternatively, as shown in Figure 9, 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.

[0098] 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.

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

[0100] Content 1: Component Indicator Field; The component indicator field is used to indicate the components being scheduled.

[0101] The component indication field includes one or more segments, each segment indicating an index of a scheduled component.

[0102] Content 2: Bandwidth Part Indicator Field; The bandwidth part indicator field is used to indicate the bandwidth part that is scheduled.

[0103] When the bandwidth component indicator and the indicated bandwidth component index are different from the currently active bandwidth component index (or the active bandwidth component index on the component), a bandwidth component switching operation is performed.

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

[0105] There are multiple active bandwidth portions on a frequency resource. If the DCI does not include a component indication field, it does include a bandwidth portion indication field, which is used to indicate a specified bandwidth portion of the physical shared channel being transmitted.

[0106] 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, the specified bandwidth portion for transmitting the physical shared channel is the active bandwidth portion on the component indicated by the aforementioned DCI.

[0107] 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.

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

[0109] 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.

[0110] 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.

[0111] 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.

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

[0113] 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.

[0114] 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.

[0115] The time-frequency resource occupancy varies across different components / bandwidth segments, therefore, the resource distribution available for transmitting a specified physical shared channel may also differ. By specifying the time-frequency domain resources for each component / bandwidth segment separately, the allocation of time-frequency domain resources can be adjusted more flexibly and dynamically, enabling better utilization of resources on a specified component / bandwidth segment.

[0116] Allocating different numbers of bits and occupying different frequency domain resources on different components / bandwidths can better match the characteristics of different components / bandwidths, increasing transmission reliability and timeliness.

[0117] The first number of bit domain blocks includes at least one of the following: first bit mapping information, second bit mapping information, third bit mapping information, fourth number of bandwidth portion indices, fourth number of time domain resource allocation indications, 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.

[0118] 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.

[0119] 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.

[0120] 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.

[0121] The virtual index of the first resource block contained in the specified bandwidth portion can be 0.

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

[0123] Content 1: Scheduling type indicator field.

[0124] The scheduling type indicator field is used to indicate the scheduling type of the 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.

[0125] 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.

[0126] 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.

[0127] 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.

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

[0129] For frequency domain extended scheduling, time domain resources are allocated equally across one or more specified bandwidth portions.

[0130] Since the same physical shared channel is transmitted on different components / bandwidth sections, the same time domain resource allocation can ensure that the start and end times of data transmission are the same. This makes it easier for the first communication node / second communication node to merge and decode the information received on different components / bandwidth sections without buffering or waiting, thus improving data transmission efficiency and saving overhead.

[0131] 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.

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

[0133] Content 4: Hybrid Automatic Repeat Request Process Number.

[0134] 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.

[0135] In some cases, physical shared channels transmitted on one or more specified bandwidth portions belong to the same transport block, and therefore, physical shared channels transmitted on one or more specified bandwidth portions have the same hybrid automatic repeat request process number.

[0136] In some embodiments, the first communication node may send a hybrid automatic retransmission request response based on the merged decoding result of the physical shared channel.

[0137] 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.

[0138] 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; and uplink resources that allow transmission of the second physical control channel.

[0139] 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 physical shared channel transmission is completed first, the time when the physical shared channel transmission is completed last, the time when the physical shared channel transmission on the main component / bandwidth portion is completed, and the time when the physical shared channel transmission on the component / bandwidth portion used for transmitting scheduling control information is completed.

[0140] 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.

[0141] The first communication node can determine the hybrid automatic repeat request response value based on the combined decoding results of one or more physical shared channels on a specified bandwidth portion. Specifically, if the combined decoding of the physical shared channels on one or more specified bandwidth portions is successful, the hybrid automatic repeat request response value is "ACK"; if the combined decoding of the physical shared channels on one or more specified bandwidth portions fails, the hybrid automatic repeat request response value is "NACK".

[0142] 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 physical shared channel on one or more specified bandwidth portions.

[0143] The last physical shared channel mentioned above is the latest physical shared channel to end among one or more physical shared channels transmitted over one or more specified bandwidth portions.

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

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

[0146] 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.

[0147] 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 both a self-scheduled physical shared channel and a cross-component scheduled physical shared channel occur simultaneously on the same time / frequency domain resources of a component, the self-scheduled physical shared channel is transmitted first.

[0148] 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.

[0149] 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 a physical shared channel conflicts with other signals / channels, the other signals / channels are transmitted first. As another example, when an initial physical shared channel and a retransmission physical shared channel conflict, the initial physical shared channel is transmitted first.

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

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

[0152] S1001, Send configuration information.

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

[0154] S1002. Based on the configuration information, perform at least one of the following operations: send control information; send / receive physical shared channels on one or more specified bandwidth portions; receive hybrid automatic repeat request response information; wherein the physical shared channels are transmitted on one or more specified bandwidth portions according to a specified scheduling method, and the specified scheduling method includes frequency domain extended scheduling method.

[0155] 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.

[0156] 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.

[0157] Figure 11 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 11, the device may include a receiving module 1101 and a transmitting module 1102.

[0158] The receiving module 1101 is used to receive configuration information; the configuration information is used to configure the frequency domain resources available to the first communication node; the receiving module 1101 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 a physical shared channel on one or more specified bandwidth portions; wherein the 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 extended scheduling method; the sending module 1102 is used to send hybrid automatic repeat request response information according to the configuration information.

[0159] Based on the above embodiments, the configuration information includes at least one of the following: 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.

[0160] Based on the above embodiments, the designated bandwidth portion includes at least one of the following: one or more active bandwidth portions on the same cell / carrier; 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.

[0161] Based on the above embodiments, the plurality of designated bandwidth portions satisfy at least one of the following conditions: they belong to the same frequency band; the interval between the frequency bands is less than a first preset value; the interval between the frequency bands is an integer multiple of the subcarrier interval; the frequency bands support the same terminal capabilities; they have the same interleaving parameter configuration; they have the same resource block group size; they have the same resource block binding type configuration; they have the same resource allocation type; they have the same automatic request backhaul processing number size; they have the same modulation and coding table; and they belong to the same bandwidth portion group.

[0162] Based on the above embodiments, the frequency domain extended scheduling method is used to indicate that a portion of the content of the physical shared channel is transmitted on the multiple specified bandwidth portions respectively.

[0163] Based on the above embodiments, the physical shared channel is processed by a preset processing method and then mapped to multiple specified bandwidth portions, and the multiple specified bandwidth portions respectively map to a portion of the physical shared channel content.

[0164] Based on the above embodiments, the device further includes a processing module, which is configured to map the physical shared channel onto the plurality of specified bandwidth portions according to at least one of the following: performing interleaving mapping on the plurality of specified bandwidth portions according to the interleaving parameters on the plurality of specified bandwidth portions respectively; and interleaving mapping the plurality of specified bandwidth portions as a virtual physical resource set.

[0165] Based on the above embodiments, the processing module is further configured to determine, through at least one of the following methods, that the physical shared channel is transmitted on the one or more designated bandwidth portions in a frequency domain extended scheduling manner: predefined, higher layer parameters, signaling indication, transmission type, service type, and the type and capability of the first communication node.

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

[0167] Based on the above embodiments, the transport block size of the physical shared channel is less than or equal to the total number of frequency domain resources of the one or more specified bandwidth portions on the specified time domain resources.

[0168] Based on the above embodiments, the control information includes a first number of bit field blocks and a second number of common bit fields, and each bit field block includes a third number of bit field segments;

[0169] One bit field block corresponds to one scheduled component / bandwidth portion, the first quantity is equal to the number of scheduled component / bandwidth portions, or, wherein each bit field segment corresponds to one scheduled component / bandwidth portion, the third quantity is equal to the number of scheduled component / bandwidth portions, and the first quantity, the second quantity and the third quantity are all natural numbers.

[0170] Based on the above embodiments, the first number of bit domain blocks includes at least one of the following: a component indication field; the component indication field is used to indicate a scheduled component; a bandwidth portion indication field; the bandwidth portion indication field is used to indicate a scheduled bandwidth portion; time domain resource allocation information on the scheduled component / bandwidth portion; and frequency domain resource allocation information on the scheduled component / bandwidth portion.

[0171] Based on the above embodiments, the first number of bit field blocks includes at least one of the following:

[0172] The first mapping information, where each bit corresponds to a component or an active component, and the length of the first mapping information is equal to the number of configured components or the number of active components; the second mapping information, where each bit corresponds to a bandwidth segment or an active bandwidth segment, and the length of the second mapping information is equal to the number of configured bandwidth segments or the number of active bandwidth segments; the third mapping information, where each bit is used to indicate whether a group of resource blocks in a scheduled specified bandwidth segment has been allocated; a fourth number of bandwidth segment 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 segments.

[0173] Based on the above embodiments, the second number of common bit fields includes at least one of the following: a scheduling type indication field; the scheduling type indication field is used to indicate the scheduling type of the physical shared channel; a time-domain resource allocation indication; a virtual resource block to physical resource block mapping indication; and a hybrid automatic repeat request process number.

[0174] Based on the above embodiments, the frequency domain resources of 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; and uplink resources that allow transmission of the second physical control channel.

[0175] 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.

[0176] Based on the above embodiments, the processing module is further configured to: determine a hybrid automatic repeat request response value based on the combined decoding result of the physical shared channels on the one or more specified bandwidth portions; and determine the transmission time of the hybrid automatic repeat request response information based on the transmission end time of the last physical shared channel on the one or more specified bandwidth portions.

[0177] Figure 12 is a schematic diagram of another structure of the data scheduling device provided in an embodiment of this application. The device is integrated into the second communication node. As shown in Figure 12, the device includes a transmitting module 1201 and a receiving module 1202.

[0178] The sending module 1201 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 1201 is also used to perform at least one of the following operations according to the configuration information: sending control information; sending / receiving a physical shared channel on one or more specified bandwidth portions; wherein the physical shared channel is transmitted on the specified bandwidth portions according to a specified scheduling method, the specified scheduling method including a frequency domain extended scheduling method; the receiving module 1202 is used to receive hybrid automatic repeat request response information.

[0179] 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 13. 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.

[0180] Those skilled in the art will understand that the structure shown in Figure 13 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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).

[0186] 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.

[0187] 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.

[0188] 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.

[0189] 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: Receive configuration information; The configuration information is used to configure the frequency domain resources available to the first communication node; 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 a physical shared channel on at least one specified bandwidth portion; wherein the physical shared channel is transmitted on the at least one specified bandwidth portion according to a specified scheduling method, the specified scheduling method including a frequency domain spread scheduling method; Send a mixed automatic repeat request response message.

2. The method according to claim 1, wherein, The configuration information includes at least one of the following: At least one frequency resource, at least one component, and a bandwidth portion configuration; wherein the component includes at least one of the following: cell, carrier, frequency band, and bandwidth portion.

3. The method according to claim 1, wherein, The at least one specified bandwidth portion includes at least one of the following: At least one active bandwidth portion on the same cell / carrier; At least one active bandwidth portion on the same component; An active bandwidth portion / frequency resource on at least one component; wherein each component corresponds to one active bandwidth portion / frequency resource.

4. The method according to claim 1, wherein, When the at least one specified bandwidth portion is a plurality of specified bandwidth portions, the plurality of specified bandwidth portions satisfy at least one of the following conditions: They belong to the same frequency band; The interval between the frequency bands is less than a first preset value; The spacing between the frequency bands is an integer multiple of the subcarrier spacing; The same frequency band supports the same terminal capabilities; They have the same interleaving parameter configuration; They have the same resource block group size; They have the same resource block binding type configuration; They have the same resource allocation type; They have the same automatic request return processing number size; They have the same modulation and coding table; They belong to the same bandwidth group.

5. The method according to claim 1, wherein, When the at least one specified bandwidth portion is multiple specified bandwidth portions, the frequency domain extension scheduling method is used to indicate that portions of the physical shared channel are transmitted on the multiple specified bandwidth portions respectively.

6. The method according to claim 1, wherein, After being processed by a preset processing method, the physical shared channel is mapped to multiple specified bandwidth portions, and each of the multiple specified bandwidth portions maps to a portion of the content of the physical shared channel.

7. The method according to claim 1, wherein, In the case where at least one specified bandwidth portion is multiple specified bandwidth portions, the physical shared channel is mapped onto the multiple specified bandwidth portions according to at least one of the following: Interleaving mapping is performed on the plurality of specified bandwidth portions according to the interleaving parameters on the plurality of specified bandwidth portions respectively; The multiple specified bandwidth portions are virtualized as a single physical resource set and then interleaved and mapped.

8. The method according to claim 1, wherein, The physical shared channel is determined to be transmitted in a frequency-domain extended scheduling manner on the at least one specified bandwidth portion by at least one of the following methods: Predefined parameters, higher-level parameters, signaling indications, transmission type, service type, and the type and capabilities of the first communication node.

9. The method of claim 8, further comprising at least one of the following: When a specified parameter is configured or the value of the specified parameter is configured to a second preset value, it is determined that the physical shared channel transmits in the frequency domain extended scheduling method on the at least one specified bandwidth portion. The physical shared channel is determined to be transmitted on the at least one specified bandwidth portion according to the frequency domain extended scheduling method based on at least one domain in the control information.

10. The method according to claim 1, wherein, The transport block size of the physical shared channel is less than or equal to the total frequency domain resources of the at least one specified bandwidth portion on the specified time domain resources.

11. The method according to claim 1, wherein, The control information includes a first number of bit field blocks and a second number of common bit fields, and each bit field block includes a third number of bit field segments. Wherein, one bit field block corresponds to one scheduled component / bandwidth portion, and the first quantity is equal to the number of scheduled component / bandwidth portions, or, Each bit field segment corresponds to a scheduled component / bandwidth portion, and the third quantity is equal to the number of scheduled component / bandwidth portions. The first quantity, the second quantity, and the third quantity are all natural numbers.

12. The method according to claim 11, wherein, The first number of bit field blocks includes at least one of the following: Component indication field; the component indication field is used to indicate the component being scheduled; Bandwidth portion indication field; the bandwidth portion indication field is used to indicate the scheduled bandwidth portion; Temporal resource allocation information on the scheduled components / bandwidth portions; Frequency domain resource allocation information on the scheduled component / bandwidth portion.

13. The method according to claim 11, wherein, The first number of bit field blocks includes at least one of the following: The first bit of mapping information, each bit in the first bit of mapping information corresponds to a component or an active component, and the length of the first bit of mapping information is equal to the number of configured components or the number of active components. The second bit mapping information, each bit in the second bit mapping information corresponds to a bandwidth portion or an active bandwidth portion, and the length of the second bit mapping information is equal to the number of configured bandwidth portions or the number of active bandwidth portions. The third bit mapping information, each bit in the third bit mapping information is used to indicate whether the resource block group in the scheduled specified bandwidth portion is allocated; The fourth number of bandwidth portion indices; The fourth number of time-domain resource allocation instructions; The index of the fourth number of initial virtual resource blocks and / or the length of the allocated resource blocks; The fourth quantity is equal to the number of components / bandwidth portions that are scheduled.

14. The method according to claim 11, wherein, The second number of common bit fields includes at least one of the following: Scheduling type indication field; the scheduling type indication field is used to indicate the scheduling type of the physical shared channel; Time-domain resource allocation instructions; A mapping indicator from virtual resource blocks to physical resource blocks; Hybrid Automatic Repeat Request process number.

15. The method according to any one of claims 1 to 14, wherein, The frequency domain resources of the hybrid automatic repeat request response information include at least one of the following: The upstream resources corresponding to the main components; Uplink resources corresponding to the components / bandwidth portion used for transmitting scheduling control information; The uplink resources corresponding to the highest priority component / bandwidth portion among the scheduled components / bandwidth portions; The uplink resources corresponding to the component / bandwidth portion that completes data scheduling first; Finally, the uplink resources corresponding to the components / bandwidth portion of the data scheduling are completed. Uplink resources for transmitting the second physical control channel are permitted.

16. The method according to any one of claims 1 to 14, wherein, The subcarrier spacing associated with the hybrid automatic repeat request response information includes at least one of the following: Subcarrier spacing used to transmit components of the hybrid automatic repeat request response value; The subcarrier spacing used to receive and schedule the physical control channel; The minimum value between the subcarrier spacing for receiving the physical control channel and the subcarrier spacing for transmitting the second physical control channel; The minimum value of the subcarrier spacing in the scheduled component / bandwidth portion.

17. The method according to any one of claims 1 to 14, further comprising at least one of the following: Based on the combined decoding results of the physical shared channel on at least one specified bandwidth portion, determine the hybrid automatic repeat request response value; The transmission time of the hybrid automatic repeat request response information is determined based on the transmission end time of the last physical shared channel on the at least one or more specified bandwidth portions.

18. A data scheduling method, applied to a second communication node, comprising: Send configuration information; The configuration information is used to configure the frequency domain resources available to the first communication node; Based on the configuration information, perform at least one of the following operations: Send control information; Transmit / receive a physical shared channel on at least one specified bandwidth portion; wherein the physical shared channel is transmitted on the at least one specified bandwidth portion according to a specified scheduling method, the specified scheduling method including a frequency domain spread scheduling method; Receive the response information for the Hybrid Automatic Repeat Request.

19. A communication node, comprising: A memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the method of any one of claims 1-18.

20. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the method of any one of claims 1-18.

Images