CN112088557B

CN112088557B - Resource scheduling method, terminal and network equipment

Info

Publication number: CN112088557B
Application number: CN201880093300.5A
Authority: CN
Inventors: 刘航; 李明超; 肖潇; 王和俊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-05-09
Filing date: 2018-05-09
Publication date: 2023-06-02
Anticipated expiration: 2038-05-09
Also published as: CN112088557A; WO2019213883A1

Abstract

A resource scheduling method, a terminal and a network device, the method comprises: the terminal receives configuration information from network equipment, wherein the configuration information comprises a first carrier frequency set and a second carrier frequency set; the terminal respectively determines carrier frequency sets for data transmission for the first logic channel and the second logic channel according to the configuration information; the terminal determines a first identifier according to attribute information of data to be transmitted; the terminal sends a resource scheduling request to the network device, wherein the resource scheduling request comprises a first identifier and a first data volume, the first data volume at least comprises the data volume of a first logic channel, and the resource scheduling request is used for requesting the network device to schedule the through link resource for the terminal.

Description

Resource scheduling method, terminal and network equipment

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a resource scheduling method, a terminal and network equipment.

Background

With the development of mobile communication technology, various innovative applications, such as mobile broadband, multimedia, machine type communication (machine type communication, abbreviated as MTC), industrial control, intelligent transportation system (intelligent transportation system, abbreviated as ITS), etc., will become the main use cases in the 5G era. Many of these applications involve direct link (sidelink) communications, more typically, for example, vehicle-to-everything (V2X) traffic, including Vehicle-to-Vehicle (Vehicle to Vehicle, V2V), vehicle-to-Infrastructure (V2I), vehicle-to-Network (V2N), and Vehicle-to-pedestrian (V2P) communications, etc., to improve reliability of information interaction between vehicles.

At present, in R15V2X defined by 3GPP, repeat transmission of a data packet of a direct link packet data convergence protocol (Packet Date Convergence Protocol, abbreviated as PDCP) is introduced, namely, a terminal copies the data packet in the same PDCP entity into two parts, and sends out the data packet through two logic channels at different transmission carrier frequencies respectively, and a receiving end receives the same data packet at different carrier frequencies so as to improve the reliability of the direct link data transmission. Wherein, two logical channels for packet retransmission need to transmit PDCP packets on different carrier frequencies to obtain frequency diversity gain at the receiving end. In the scenario that resources are scheduled for a terminal by a base station, in a through link, the terminal is responsible for establishing and maintaining a logic channel for through link communication, the base station does not sense the logic channel existing in the terminal, so the base station cannot perform corresponding configuration on a single logic channel, and at this time, how the base station acquires the data amount of the logic channel corresponding to different scheduling carrier frequencies existing at the terminal side to perform resource scheduling becomes critical.

Disclosure of Invention

The embodiment of the invention provides a resource scheduling method, a terminal and network equipment, which are beneficial to realizing resource scheduling of the network equipment to the terminal.

In one aspect, an embodiment of the present invention provides a resource scheduling method, where the method includes: the method comprises the steps that a terminal receives configuration information from network equipment, wherein the configuration information comprises a first carrier frequency set and a second carrier frequency set; the terminal respectively determines carrier frequency sets for data transmission for the first logic channel and the second logic channel according to the configuration information; the terminal determines a first identifier according to attribute information of data to be transmitted; the terminal sends a resource scheduling request to the network device, wherein the resource scheduling request comprises the first identifier and a first data volume, the first data volume at least comprises the data volume of the first logic channel, and the resource scheduling request is used for requesting the network device to schedule the through link resource for the terminal. This helps to achieve resource scheduling for the terminal by the network device.

In one possible design, the attribute information includes at least one of reliability information, latency information, communication distance information, data rate information, data priority information, and data traffic type information. The attribute information may be information identifying, indexing, or otherwise pointing to an attribute.

In one possible design, the method further comprises: the terminal receives first mapping information from the network device, where the first mapping information is used to indicate mapping relationships between different identifiers and attribute information of different data. Further, the terminal determines a first identifier according to attribute information of data to be transmitted, including: the terminal determines the first identifier according to the first mapping information and attribute information of the data. Therefore, the terminal can determine the reported identifier according to the mapping relation between the different identifiers and the attribute information of the different data.

In one possible design, the method further comprises: the terminal determines a second identifier according to the first mapping information and attribute information of the data; the first identifier corresponds to the first logic channel, the second identifier corresponds to the second logic channel, the resource scheduling request further comprises the second identifier and a second data volume, and the second data volume at least comprises the data volume of the second logic channel. Therefore, the terminal can distinguish the logic channels for repeated data transmission by reporting the first identifier and the second identifier, so that the network equipment can determine the data quantity of the logic channels corresponding to different carrier frequencies, and the resource scheduling of the network equipment to the terminal is realized.

In one possible design, the method further comprises: the terminal receives second mapping information from the network equipment, wherein the second mapping information is used for indicating mapping relations between different identifications and different carrier frequency sets; the terminal determines a second identifier according to attribute information of data to be transmitted and the second mapping information, wherein the resource scheduling request further comprises the second identifier and a second data volume, and the second data volume at least comprises the data volume of the second logic channel. Further, the determining, by the terminal, the first identifier according to attribute information of data to be transmitted includes: the terminal determines the first identifier according to attribute information of data to be transmitted and the second mapping information, wherein the first identifier corresponds to the first logic channel, and the second identifier corresponds to the second logic channel. Therefore, the terminal can determine the reported identification according to the attribute information of the data, the mapping relation between different identifications and different carrier frequency sets, and distinguish the logic channels for repeated data transmission, so that the network equipment can determine the data quantity of the logic channels corresponding to different carrier frequencies, and the resource scheduling of the network equipment to the terminal is realized.

In one possible design, the first identification may be a group identification of the first logical channel.

In one possible design, the second identification may be a group identification of the second logical channel.

In one possible design, the resource scheduling request further includes a second data volume, where the second data volume includes at least a data volume of a second logical channel, and an order of the first data volume and the second data volume in the resource scheduling request is the same as an order of the first carrier frequency set and the second carrier frequency set in the configuration information. So that the network device can distinguish the data amounts of the logical channels corresponding to different carrier frequencies according to the sequence of the different data amounts.

In one possible design, the data amount is the data amount of the buffer corresponding to the logical channel, e.g., the first data amount is the data amount of the buffer corresponding to the first logical channel, and the second data amount is the data amount of the buffer corresponding to the second logical channel. Alternatively, the data amount of the buffer may be the data amount of the PDCP entity buffer and/or the data amount of the RLC entity buffer.

In one possible design, the first amount of data may also include an amount of data for other logical channels than the first logical channel, and/or the second amount of data may also include an amount of data for other logical channels than the second logical channel. Therefore, the data quantity of a plurality of logic channels can be carried by one request message, so that the system overhead is saved.

In one possible design, a terminal receives resource scheduling information from a network device, the resource scheduling information including a first resource and a first characteristic corresponding to the first resource; the terminal encapsulates data of at least one logical channel into a medium access control layer protocol data unit (Media Access control Protocol Data Unit, abbreviated: MAC PDU), the at least one logical channel supporting the first characteristic; the terminal utilizes the first resource and transmits the MAC PDU over a pass-through link. Thereby facilitating the scheduling of resources by the network device to the terminal.

In one possible design, the first characteristic includes at least one of:

modulation coding mode information, retransmission times information, transmitting power information, access technology information, direct link control information SCI format information and version number information.

On the other hand, the embodiment of the invention also provides a resource scheduling method, which comprises the following steps: the network equipment sends configuration information to the terminal, wherein the configuration information comprises a first carrier frequency set and a second carrier frequency set; the network equipment receives a resource scheduling request from the terminal, wherein the resource scheduling request comprises a first identifier and a first data volume, the first data volume at least comprises the data volume of the first logic channel, and the resource scheduling request is used for requesting to schedule a through link resource for the terminal; the network equipment determines attribute information of data corresponding to the first identifier according to a preset mapping relation between different identifiers and attribute information of different data; and the network equipment schedules the direct link resource for the terminal according to the attribute information of the data and the first data quantity. This helps to achieve resource scheduling for the terminal by the network device.

In one possible design, the attribute information includes at least one of reliability information, latency information, communication distance information, data rate information, data priority information, and data traffic type information.

In one possible design, the resource scheduling request further includes a second identification and a second amount of data, the second amount of data including at least an amount of data of a second logical channel; the network device schedules a through link resource for the terminal according to the attribute information of the data, including: the network equipment respectively determines the first carrier frequency set corresponding to the first identifier and the second carrier frequency set corresponding to the second identifier according to the mapping relation between different identifiers and different carrier frequency sets; the network device schedules a through link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume and attribute information of the data. Therefore, the terminal can distinguish the logic channels for repeated data transmission by reporting the first identifier and the second identifier, so that the network equipment can determine the data quantity of the logic channels corresponding to different carrier frequencies, and the resource scheduling of the network equipment to the terminal is realized.

In one possible design, the resource scheduling request further includes a second amount of data including at least an amount of data of the second logical channel; the method further comprises the steps of: the network device determines the first carrier frequency set and the second carrier frequency set according to the sequence of the first data volume and the second data volume in the resource scheduling request, wherein the sequence of the first data volume and the second data volume in the resource scheduling request is the same as the sequence of the first carrier frequency set and the second carrier frequency set in the configuration information. Further, the network device schedules a through link resource for the terminal according to the attribute information of the data, including: the network device schedules a through link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume and attribute information of the data. The network device thus distinguishes the data amounts of the logical channels corresponding to the different carrier frequencies according to the order of the different data amounts.

In one possible design, the method further comprises: the network device sends first mapping information to the terminal, where the first mapping information is used to indicate mapping relationships between different identifiers and attribute information of different data.

In one possible design, the method further comprises: the network device sends second mapping information to the terminal, where the second mapping information is used to indicate mapping relationships between different identifiers and different carrier frequency sets.

In one possible design, a network device generates resource scheduling information including a first resource and a first characteristic corresponding to the first resource; the network device transmits the resource scheduling information to the terminal. Thereby facilitating the scheduling of resources by the network device to the terminal.

In one possible design, the first characteristic includes at least one of:

In yet another aspect, an embodiment of the present invention further provides a resource scheduling method, including: the method comprises the steps that a terminal receives resource scheduling information from network equipment, wherein the resource scheduling information comprises first resources and first characteristics corresponding to the first resources; the terminal encapsulating data of at least one logical channel into a medium access control layer protocol data unit, MAC PDU, the at least one logical channel supporting the first characteristic; the terminal utilizes the first resource and transmits the MAC PDU over a pass-through link. Thereby facilitating the scheduling of resources by the network device to the terminal.

In one possible design, the first characteristic includes at least one of:

In yet another aspect, an embodiment of the present invention further provides a resource scheduling method, including: the network equipment generates resource scheduling information, wherein the resource scheduling information comprises first resources and first characteristics corresponding to the first resources; the network device transmits the resource scheduling information to the terminal. Thereby facilitating the scheduling of resources by the network device to the terminal.

In one possible design, the first characteristic includes at least one of:

In yet another aspect, an embodiment of the present invention further provides a terminal, where the terminal has some or all functions for implementing the terminal behavior in the foregoing method example, for example, the function of the terminal may be provided with the functions in some or all embodiments of the present application, or may be provided with the functions of implementing any one embodiment of the present application separately. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one possible design, the structure of the terminal may include a processing unit and a communication unit, where the processing unit is configured to support the terminal to perform the corresponding functions in the above method. The communication unit is used for supporting communication between the terminal and other devices. The terminal may further comprise a memory unit for coupling with the processing unit, which holds the program instructions and data necessary for the terminal. As an example, the processing unit may be a processor, the communication unit may be a transceiver, and the storage unit may be a memory.

In yet another aspect, an embodiment of the present invention provides a network device, where the network device has some or all of the functions that implement the behaviors of the network device in the foregoing method examples, for example, the functions of the network device may be provided with some or all of the functions in the embodiments of the present application, or may be provided with functions that implement any one of the embodiments of the present application separately. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

In one possible design, the network device includes a processing unit and a communication unit in a structure, where the processing unit is configured to support the network device to perform the corresponding functions in the method. The communication unit is used for supporting communication between the network equipment and other equipment. The network device may also include a storage unit for coupling with the processing unit, which holds the program instructions and data necessary for the network device. As an example, the processing unit may be a processor, the communication unit may be a transceiver, and the storage unit may be a memory.

In yet another aspect, an embodiment of the present invention provides a communication system, including the terminal and/or the network device of the above aspect. In another possible design, the system may further include other devices that interact with the terminal or the network device in the solution provided by the embodiments of the present invention.

In yet another aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for use with the above-described terminal, including a program designed to perform any one of the above-described methods.

In yet another aspect, an embodiment of the present invention provides a computer storage medium storing computer software instructions for use with the network device described above, including a program designed to perform any one of the methods described above.

In yet another aspect, the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

In yet another aspect, the present application provides a chip system comprising a processor for supporting a terminal to implement the functions involved in the above aspects, e.g. for determining or processing data and/or information involved in the above methods. In one possible design, the system on a chip further includes a memory for holding program instructions and data necessary for the terminal. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

In yet another aspect, the present application provides a chip system comprising a processor for supporting a network device to implement the functions involved in the above aspects, e.g. for generating or processing data and/or information involved in the above methods. In one possible design, the system-on-chip further includes a memory to hold program instructions and data necessary for the network device. The chip system can be composed of chips, and can also comprise chips and other discrete devices.

Compared with the prior art, in the scheme provided by the embodiment of the invention, the network equipment can determine the carrier frequency set for data transmission for the first logic channel and the second logic channel according to the configuration information by sending the configuration information comprising the first carrier frequency set and the second carrier frequency set to the terminal, so that when data transmission is required, the terminal can determine the first identifier according to the attribute information of the data to be transmitted, and send a resource scheduling request comprising the first identifier, the first data volume and other information to the network equipment, so that the network equipment can determine the attribute information of the data corresponding to the first identifier according to the preset mapping relation between different identifiers and the attribute information of different data, and schedule the direct link resource for the terminal according to the attribute information of the data and the first data volume. Thereby facilitating the scheduling of resources by the network device to the terminal.

Drawings

In order to more clearly describe the embodiments of the present invention or the technical solutions in the background art, the following description will describe the drawings that are required to be used in the embodiments of the present invention or the background art.

Fig. 1 is a schematic diagram of a communication system;

FIG. 2a is a schematic diagram of another communication system;

FIG. 2b is a schematic diagram of yet another communication system;

FIG. 3a is a schematic diagram of a structure for acquiring resources;

FIG. 3b is a schematic diagram of another configuration for acquiring resources;

fig. 4 is a schematic flow chart of a resource scheduling method according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a resource scheduling request according to an embodiment of the present invention;

FIG. 6 is a flowchart illustrating another resource scheduling method according to an embodiment of the present invention;

FIG. 7 is a flowchart of another resource scheduling method according to an embodiment of the present invention;

FIG. 8 is a flowchart of another resource scheduling method according to an embodiment of the present invention;

fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present invention;

fig. 10 is a schematic structural diagram of another terminal according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of still another terminal according to an embodiment of the present invention;

Fig. 12 is a schematic structural diagram of a network device according to an embodiment of the present invention;

fig. 13 is a schematic structural diagram of another network device according to an embodiment of the present invention;

fig. 14 is a schematic structural diagram of still another network device according to an embodiment of the present invention.

Detailed Description

Embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

It should be understood that the technical solution of the present application may be specifically applied to various communication systems, for example: the global system for mobile communications (global system for mobile communications, abbreviated as GSM), code division multiple access (code division multiple access, abbreviated as CDMA), wideband code division multiple access (wideband code division multiple access, abbreviated as WCDMA), time division synchronous code division multiple access (time division-synchronous code division multiple access, abbreviated as TD-SCDMA), universal mobile telecommunications system (universal mobile telecommunications system, abbreviated as UMTS), long term evolution (long term evolution, abbreviated as LTE) network, etc., with the development of communication technology, the technical solution of the present application may also be used in future networks, such as 5G networks, also referred to as new air interface or New Radio (NR) networks, or D2D (device to device) networks, M2M (machine to machine) networks, etc.

The network device referred to in the present application may refer to an entity on the network side for sending or receiving information, for example, may be a base station, or may be a transmission point (transmission point, abbreviated as TP), a transceiver point (transmission and receiver point, abbreviated as TRP), a relay device, a radio network controller in a cloud radio access network (cloud radio access network, abbreviated as CRAN), an access point, or an access network device in a public land mobile network (public land mobile network, abbreviated as PLMN) that evolves in the future, or other network devices with a base station function, or the like, which is not limited in the present application.

In the present application, a terminal is a device with a communication function, which may include a handheld device, an in-vehicle device, a wearable device, a computing device, or other processing device connected to a wireless modem, etc. with a wireless communication function. Terminals may be called different names in different networks, for example: a mobile terminal, user Equipment (UE), mobile station, subscriber unit, station, cellular telephone, personal digital assistant, wireless modem, wireless communication device, handheld device, laptop, cordless telephone, wireless local loop station, access terminal, subscriber station, mobile station, remote terminal, user agent, user device, vehicle or infrastructure, and the like. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, abbreviated: SIP) phone, a wireless local loop (wireless local loop, abbreviated: WLL) station, a personal digital assistant (personal digital assistant, abbreviated: PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in the internet of things, a virtual reality device, a terminal device in a future 5G network or a terminal device in a future evolved PLMN, etc., which may communicate with one or more core networks via a radio access network (e.g., RAN, radio access network).

In this application, a base station, which may also be referred to as a base station device, is a device deployed in a radio access network to provide wireless communication functionality. The names of base stations may vary in different radio access systems, e.g. in universal mobile telecommunications system UMTS networks called node bs (NodeB), in LTE networks called evolved NodeB (abbreviated eNB or eNodeB), in future 5G systems may be called transceiving node (transmission reception point) abbreviated TRP) network nodes or G NodeB (G-NodeB, gNB), or also called small stations, micro stations etc., not listed here.

Referring to fig. 1, fig. 1 is an architecture diagram of a communication system according to an embodiment of the present invention. Specifically, as shown in fig. 1, the communication system may include a network device and a terminal, where the terminal and the network device may use the above communication system to perform communication, for example, the terminal may obtain a scheduling resource from the network device, so as to perform transmission of a V2X message between the terminals based on the resource, that is, implement V2X communication.

In particular, V2X communications generally include two communication scenarios, namely a direct link communication scenario and a communication scenario in which messages are relayed through a network device, such as a base station. For example, as shown in fig. 2a, the direct link communication refers to direct communication between terminals such as vehicles, that is, a link for implementing direct communication between vehicles is called a direct link (SL), also called a side link, where resources for communication between vehicles come from a base station configuration or a pre-configuration. As another example, as shown in fig. 2b, forwarding a message through a base station means that data that a vehicle needs to transmit needs to be forwarded through the base station, the vehicle transmits data to the base station through an uplink with the base station, and the base station transmits data to other vehicles through a downlink with other vehicles.

In a through link, communication between terminals such as vehicles can be further divided into a plurality of modes including a base station scheduling mode and a mode in which the terminals autonomously select resources. As shown in fig. 3a, the base station scheduling mode is that the vehicle terminal sends a request to the base station, and the base station dynamically or semi-dynamically schedules resources (or referred to as "scheduled through link resources") for the through link of the terminal, such as dedicated resources (Dedicated Resource) or other resources, according to the request, and may send information of the resources to the terminal, such as by dedicated signaling (Dedicated Signaling) such as dedicated radio resource control signaling (Dedicated Radio Resource control, abbreviated: dedicated RRC), physical transport channels such as physical downlink control channels (Physical Downlink Control Channel, abbreviated: PDCCH), or other signals. In the base station scheduling mode, the terminal may be in an RRC CONNECTED (rrc_connected) state. As shown in fig. 3b, the mode of autonomous Resource selection by the terminal means that the base station configures at least one Resource Pool (Resource Pool) for the terminal through a system message block (System information Block, abbreviated SIB) message such as SIB21 and/or SIB22 message or dedicated signaling or other message, and the terminal autonomously selects resources from the at least one Resource Pool to communicate or the terminal acquires resources from the preconfigured at least one Resource Pool to communicate. Each resource pool contains a plurality of time-frequency resources, which can be used for the communication of the direct link. Where SIB and dedicated RRC signaling are collectively referred to as RRC signaling. In a mode in which a terminal autonomously selects resources, the terminal may be in an RRC IDLE state (rrc_idle) or an RRC CONNECTED state (rrc_connected). The pre-configuration may refer to that the terminal is pre-configured inside the terminal at the time of shipment, or pre-configured by a network side such as a network device, and the terminal is stored inside. The terminal may select resources from the resource pool by randomly selecting resources from the resource pool or based on a listening reservation mechanism, such as by listening to whether resources from the resource pool are free to select free resources for V2X communication.

For the scenario that the network device schedules resources for the terminal, in the base station scheduling mode described above, the resources for the terminal to perform the through link communication are scheduled by the base station. Therefore, the base station needs to know the data quantity of the logic channels corresponding to different scheduling carrier frequencies, so as to perform resource scheduling according to the data quantity of the logic channels of different scheduling carrier frequencies, and ensure that when the terminal performs repeated transmission of the data packet, the same data packet can be copied into two copies and then transmitted through two logic channels respectively at different transmission carrier frequencies. It should be understood that the repeated data transmission referred to in the present application may also refer to repeated transmission of more than two data, that is, one data packet is copied into multiple copies and then transmitted through multiple logical channels at different transmission carrier frequencies, where the number of copies of the data packet may be the same as the number of logical channels, and the copies may correspond to each other one by one. The present application describes an example in which the same data packet is duplicated into two packets and then transmitted through two logical channels with different transmission carrier frequencies.

In this application, carrier frequency may refer to a carrier frequency, or may also be referred to as a frequency band, frequency, spectrum, etc., which is not limited in this application.

The application discloses a resource scheduling method, a terminal and network equipment, which are beneficial to realizing resource scheduling of the network equipment to the terminal. Each of which is described in detail below.

Referring to fig. 4, fig. 4 is an interaction schematic diagram of a resource scheduling method according to an embodiment of the present invention. Specifically, as shown in fig. 4, the resource scheduling method in the embodiment of the present invention may include the following steps:

401. the network device sends configuration information to the terminal, the configuration information including a first carrier frequency set and a second carrier frequency set.

402. And the terminal respectively determines carrier frequency sets for data transmission for the first logic channel and the second logic channel according to the configuration information.

The network device may determine information for a set of carrier frequencies allocated to the terminal, generate configuration information indicating the set of carrier frequencies, such as a first set of carrier frequencies and a second set of carrier frequencies, and send the configuration information to the terminal. The terminal may receive configuration information from the network device to obtain a set of carrier frequencies allocated by the network device to the terminal, i.e., a first set of carrier frequencies and a second set of carrier frequencies. After the first carrier frequency set and the second carrier frequency set are obtained, the terminal can respectively correspond (correlate and bind) the first carrier frequency set and the second carrier frequency set with the first logic channel and the second logic channel of the terminal, namely, the carrier frequency sets for data transmission are respectively determined for the first logic channel and the second logic channel.

For example, the terminal determines that a carrier frequency set corresponding to a first logical channel and used for data transmission is a first carrier frequency set, determines that a carrier frequency set corresponding to a second logical channel and used for data transmission is a second carrier frequency set, that is, indicates that the terminal can use a transmission resource in the first carrier frequency set to transmit data in the first logical channel, and the terminal can use a transmission resource in the second carrier frequency set to transmit data in the second logical channel. For another example, the terminal determines that the carrier frequency set for performing data transmission corresponding to the first logical channel is a second carrier frequency set, determines that the carrier frequency set for performing data transmission corresponding to the second logical channel is a first carrier frequency set, that is, indicates that the terminal can use the transmission resource in the second carrier frequency set to transmit the data in the first logical channel, and the terminal can use the transmission resource in the first carrier frequency set to transmit the data in the second logical channel.

Wherein the first carrier frequency set includes at least one transmission carrier frequency, and the second carrier frequency set includes at least one transmission carrier frequency. Alternatively, the configuration information may indicate different carrier frequencies for transmission by different carrier frequency identifications.

Optionally, the first set of carrier frequencies is orthogonal to the second set of carrier frequencies, i.e. there are no common elements for both sets.

Optionally, the transmission resource in the first carrier frequency set may be a time-frequency resource on any one transmission carrier frequency in the first carrier frequency set.

Optionally, the transmission resource in the second carrier frequency set may be a time-frequency resource on any one transmission carrier frequency in the second carrier frequency set.

The configuration information may be carried in SIB messages, dedicated RRC signaling, physical transport channels, or other messages, which is not limited in this application.

403. And the terminal determines the first identifier according to the attribute information of the data to be transmitted.

Alternatively, the attribute information may include at least one of reliability information, latency information, communication distance information, data rate information, data priority information, and data traffic type information. Wherein the attribute information may be information identifying, indexing, or otherwise pointing to an attribute. It will be appreciated that the attribute information may also be the attribute itself. Taking reliability information as an example, the reliability information may be at least one of reliability identification, reliability index, reliability range, and reliability enumeration value. Other similarities, a detailed description is not given here.

Alternatively, the data may be a data packet.

The reliability information may be used to indicate the reliability of the data. The data on the terminal may have different reliabilities. The corresponding reliability of the data represents the transmission reliability requirement/level/constraint of the data. The reliability may be, but is not limited to, end-to-end transmission reliability, air interface transmission reliability, etc. By way of example, transmission reliability may be defined as a 1-bit error ratio, i.e., a 1-bit error rate; 1-symbol error ratio, i.e., 1-symbol error rate; or 1-packet error ratio, i.e., 1-packet error rate, etc.

The delay information may be used to indicate a delay corresponding to the data. The data at the terminal may have different latency requirements/constraints, which may be, but are not limited to, end-to-end transmission latency, air interface latency, latency budget, transmission time interval, etc.

The communication distance information may be used to indicate a communication distance or a communication range corresponding to the data. The data on the terminal may have different communication distances or communication ranges.

The data rate information may be used to indicate a transmission rate corresponding to the data. The data on the terminal may have different transmission rates. Alternatively, the transmission rate may be a modulation coding scheme, and the data on the terminal may have a different modulation coding scheme.

Wherein, the terminal may have a plurality of different types of services, and different service type information may be used to indicate different types of services. Illustratively, the traffic types may be distinguished by different application layer identifications (application IDs, abbreviations: AIDs), or at the access layer, the different traffic types may be distinguished by different destination address identifications (Destination layer 2 ID). Optionally, a mapping relationship exists between the destination address identifier and the application layer identifier.

Wherein different data may have different data priorities. Generally, different priority data have different transmission parameters in an access layer, and transmission of high priority data is preferentially guaranteed.

Alternatively, attribute information of data may be transferred from an upper layer (above an access layer) to the access layer in the form of primitives together with the data.

The terminal may store in advance mapping relationships (corresponding relationships) between attribute information of different data and different identifiers, where the mapping relationships include a one-to-one mapping relationship (i.e., one set of attribute information corresponds to one identifier), a one-to-many mapping relationship (i.e., one set of attribute information corresponds to multiple identifiers), and a many-to-one mapping relationship (i.e., multiple sets of attribute information corresponds to one identifier). And when data needs to be transmitted, the attribute information of the data, namely the data to be transmitted, can be obtained, and one or more identifiers corresponding to the attribute information of the data are determined according to the mapping relation between the attribute information of different data and different identifiers. The determined identity comprises at least a first identity. Alternatively, the mapping relationship may be preconfigured, or may be sent by the network device to the terminal.

The data to be transmitted may refer to data in the PDCP entity or data in a logical channel.

It should be noted that the present application does not limit the execution sequence of the step 402 and the step 403. Illustratively, the terminal may execute 402 first and then execute 403; or execute 403 before execute 402; or steps 402, 403 are performed simultaneously.

404. The terminal sends a resource scheduling request to the network device, wherein the resource scheduling request comprises the first identifier and the first data volume.

The resource scheduling request may be used to request the network device to schedule the through link resource for the terminal. The first data amount includes at least a data amount of the first logical channel.

Optionally, the resource scheduling request may further include a second data amount, where the second data amount includes at least a data amount of the second logical channel. Therefore, the terminal can report the data quantity of different logic channels corresponding to different carrier frequencies to the network equipment.

Alternatively, the scheduling resource request may be a buffer status report (Buffer Status Report, abbreviated: BSR). Which may be included in an uplink protocol data unit (Protocol Data Unit, abbreviated PDU) sent by the terminal to the network device.

If the uplink resource is insufficient, the resource scheduling request, such as the buffer status report, may have a truncated format, and the resource scheduling request may only include the first identifier and the first data amount, so that the network device may perform resource scheduling according to the first identifier and the first data amount in time.

Further alternatively, the first data amount may further include data amounts of other logical channels than the first logical channel, and/or the second data amount may further include data amounts of other logical channels than the second logical channel.

For example, it is assumed that a single PDCP entity delivers duplicate data to two logical channels, respectively, at the time of data retransmission, but since a terminal may simultaneously have a plurality of PDCP entities that need to perform data retransmission, at this time, there may be more than two logical channels. For example, assuming that there are a third logical channel and a fourth logical channel for data repetition transmission, where the terminal determines that a carrier frequency set for data transmission corresponding to the third logical channel is a first carrier frequency set, and determines that a carrier frequency set for data transmission corresponding to the fourth logical channel is a second carrier frequency set, at this time, the first data volume reported by the terminal may include a sum of data volumes of the first logical channel and the third logical channel, and the second data volume may include a sum of data volumes of the second logical channel and the fourth logical channel.

Alternatively, a single logical channel is traffic type dependent, and the first data volume and/or the second data volume only comprises the sum of the data volumes of one or more logical channels having the same traffic type (e.g., the same destination address identification or the same application layer identification).

Alternatively, the single PDCP entity delivers the copied data to two logical channels respectively, which means that the copied data is delivered to two RLC entities respectively, wherein the two RLC entities respectively correspond to the two logical channels one to one.

Alternatively, the data volume may be, but is not limited to, an index of the data volume, an identification, or the data volume itself.

Alternatively, the data amount may be a data amount of a buffer corresponding to a logical channel, for example, the first data amount may be a data amount of a buffer corresponding to a first logical channel, and the second data amount may be a data amount of a buffer corresponding to a second logical channel. Further alternatively, the data amount of the buffer may be the data amount of a PDCP entity buffer and/or the data amount of a radio link control protocol (Radio Link Control, abbreviated RLC) entity buffer.

405. The network equipment determines the attribute information of the data corresponding to the first identifier according to the preset mapping relation between different identifiers and the attribute information of different data, and schedules the direct link resource for the terminal according to the attribute information of the data and the first data volume.

The network device may store in advance mapping relationships between attribute information of different data and different identifiers, where the mapping relationships include a one-to-one mapping relationship, a one-to-many and a many-to-one mapping relationship. Generally, the mapping is network device configured. Alternatively, the mapping relationship may be sent to the terminal through RRC signaling. Alternatively, the mapping relationship may be explicit or implicit.

For example, the following will take as an example a logical channel group identifier (Logical Channel Group ID: abbreviated LCGID, reliability information is reliability identifier).

In one possible implementation, the mapping relationship may be explicitly indicated. The mapping information generated by the network device may include at least one LCGID and at least one reliability identifier, for example, including LCGID1, reliability identifier 1, LCGID2, and reliability identifier 2, where LCGID1 corresponds to reliability identifier 1, LCGID2 corresponds to reliability identifier 2, and the network device may send the mapping information to the terminal. After receiving the mapping information, the terminal can determine that the LCGID1 has a corresponding relation with the reliability identifier 1 through the mapping information, and that the LCGID2 has a corresponding relation with the reliability identifier 2.

In another possible implementation, the mapping relationship may be implicitly indicated. The mapping information may not include the LCGID but only include at least one reliability information, but the terminal may determine the LCGID corresponding to the at least one reliability information according to a predetermined order or rule. Wherein the order may be protocol-specified or agreed upon by the network device with the terminal. Illustratively, since the LCGID may be a number, both parties may agree that the LCGIDs are arranged in a small to large order. For example, the LCGID numbers are 0,1,2, and 3 in order, and the mapping information may not include LCGID but include at least one reliability information. The terminal can determine the logical channel group identification corresponding to the at least one reliability information according to the sequence of the at least one reliability information.

For example, the mapping information includes only { reliability flag 1}, { reliability flag 2, reliability flag 3}, { reliability flag 4}, { reliability flag 5, reliability flag 6}. The LCGIDs agreed by both parties are arranged in order from small to large, and after receiving the mapping information, the terminal can determine that { reliability identification 1} corresponds to the logical channel group identification numbered 0, { reliability identification 2, reliability identification 3} corresponds to the logical channel group identification numbered 1, { reliability identification 4}, { reliability identification 5, and reliability identification 6} respectively corresponds to the logical channel group identifications numbered 2 and 3.

For another example, the mapping information includes { reliability flag 1}, { reliability flag 2}, reliability flag 3}, and { reliability flag 4}. Meanwhile, the mapping information also comprises { data priority identifier 1}, { data priority identifier 2}, then it can be understood that when the two parties agree that the LCGIDs are arranged in order from small to large, after receiving the mapping information, the terminal can determine that { reliability identifier 1 and data priority identifier 1} corresponds to a logic channel group identifier with the number 0, { reliability identifier 2 and data priority identifier 2}, { reliability identifier 3 and data priority identifier 2} corresponds to a logic channel group identifier with the number 1, { reliability identifier 4 and data priority identifier 2} corresponds to a logic channel group identifier with the number 2.

For another example, the mapping information includes { reliability identifier 1, data priority identifier 1}, { reliability identifier 2, data priority identifier 1}, and at this time, it can be understood that, when the two parties agree with LCGIDs and arrange in order from small to large, the terminal can determine that { reliability identifier 1 and data priority identifier 1} corresponds to logical channel group identifier with number 0 and { reliability identifier 2 and data priority identifier 1} corresponds to logical channel group identifier with number 1 after receiving the mapping information.

It should be noted that, the attribute information corresponding to the data may include multiple items of reliability information, delay information, communication distance information, data rate information, data priority information, and data service type information, and the mapping information configured by the network device may only relate to at least one item of attribute information corresponding to the data, and does not necessarily include items in all data attributes.

For example, the attribute information of the data may include reliability information and data priority information, and the mapping information may include only the mapping relationship between the different identifiers and the data priority information.

Alternatively, the mapping relationship may be preconfigured. The network device may receive the resource scheduling request from the terminal, and further determine, according to the mapping relationship between the different identifiers and the attribute information of the different data, attribute information corresponding to the first identifier, such as reliability information, delay information, communication distance information, data rate information, data priority information, data service type information, and so on, so that the network device may schedule resources, such as through link resources, for the terminal according to the data attribute information corresponding to the first identifier, that is, attribute information of the data to be transmitted, and the first data amount carried by the resource scheduling request.

Further optionally, the resource scheduling request may further carry a second amount of data. In some optional embodiments, the identifier determined by the terminal according to the attribute information of the data to be transmitted may include only the first identifier, that is, determine an identifier, where the first identifier may be carried in the resource scheduling request, and an order of the first data amount and the second data amount in the resource scheduling request is the same as an order of the first carrier frequency set and the second carrier frequency set in the configuration information. The network device can determine the first carrier frequency set and the second carrier frequency set according to the sequence of the first data amount and the second data amount in the resource scheduling request, the sequence of the first data amount and the second data amount in the resource scheduling request is the same as the sequence of the first carrier frequency set and the second carrier frequency set in the configuration information, that is, the corresponding carrier frequency set is determined according to the sequence (position) of different data amounts in the resource scheduling request, and then the through link resource can be scheduled for the terminal according to the attribute information of the first carrier frequency set, the second carrier frequency set, the first data amount, the second data amount and the data.

For example, the network device configures the mapping relationship: { reliability identification 1}, reliability identification 2}. It is understood that it corresponds to LCGID0 and LCGID1, respectively. Meanwhile, the network equipment configures { a first carrier frequency set } { a second carrier frequency set }, when the reliability identifier corresponding to the data to be transmitted is 2, the terminal determines that the first identifier is LCGID1, and if the terminal corresponds the first logic channel to the first carrier frequency set and corresponds the second logic channel to the second carrier frequency set, the resource scheduling request sent by the terminal to the network equipment comprises LCGID1, the first data volume and the second data volume.

Otherwise, if the terminal corresponds the first logic channel to the second carrier frequency set and corresponds the second logic channel to the first carrier frequency set, the resource scheduling request sent by the terminal to the network device includes LCGID1, a second data volume, and a first data volume.

In some alternative embodiments, the terminal may further determine the second identifier according to a mapping relationship between the different identifiers and attribute information of different data and attribute information of the data. That is, the terminal determines that the identifier corresponding to the attribute information of the data to be transmitted includes the first identifier and the second identifier according to the mapping relationship between the different identifiers and the attribute information of the different data. The first identifier and the second identifier may be carried in the resource scheduling request. Optionally, the determined identifier may correspond to a logical channel according to a preset rule, for example, the first identifier corresponds to the first logical channel, and the second identifier corresponds to the second logical channel. For example, a smaller numbered identification corresponds to a smaller numbered logical channel (logical channel identification), or vice versa.

Alternatively, the determined identifier may correspond to a carrier frequency set (the correspondence may be explicit or implicit) according to a preset rule (order or position), for example, the first identifier corresponds to the first carrier frequency set, and the second identifier corresponds to the second carrier frequency set. Since the terminal determines carrier frequency sets for data transmission for the first logical channel and the second logical channel, respectively, the terminal determines a first identification and a second identification corresponding to the first logical channel and the second logical channel, respectively. It may be understood that, at this time, the resource scheduling request may only include the first identifier and the first data amount, so that the network device performs resource scheduling for the terminal according to the first identifier and the first data amount, or at this time, the resource scheduling request includes the first identifier, the first data amount, the second identifier and the second data amount, so that the network device performs resource scheduling for the terminal according to the first identifier and the first data amount, and the second identifier and the second data amount.

For example, the network device configures the mapping relationship: { reliability identification 1, data priority identification 1}, { reliability identification 2, data priority identification 2}, { reliability identification 1, data priority identification 1}. It is understood that it corresponds to LCGID0, LCGID1, LCGID2, respectively. Assuming that the reliability of the data to be transmitted is identified by 1 and the priority of the data is identified by 1, the terminal determines that LCGID0 and LCGID2 are optional. Further, the network device may configure { the first carrier frequency set } { the second carrier frequency set }, which may be agreed according to a preset rule (sequence or position) such as a protocol, and the same two items in the mapping relationship sequentially correspond to the two sets configured by the network device, so that the terminal may determine that LCGID0 corresponds to the first carrier frequency set and LCGID2 corresponds to the second carrier frequency set. Assuming that the terminal corresponds the first logic channel to the first carrier frequency set and corresponds the second logic channel to the second carrier frequency set, the terminal determines that the LCGID0 corresponds to the first logic channel and the LCGID2 corresponds to the second logic channel, and the resource scheduling request sent by the terminal to the network device includes the LCGID0, the first data volume, or the LCGID2, the second data volume, or includes the LCGID0, the first data volume, the LCGID2, and the second data volume at the same time.

Otherwise, if the terminal corresponds the first logic channel to the second carrier frequency set and corresponds the second logic channel to the first carrier frequency set, the terminal determines that the LCGID0 corresponds to the second logic channel and the LCGID2 corresponds to the first logic channel, and the resource scheduling request sent by the terminal to the network device includes the LCGID2 and the first data volume, or includes the LCGID2, the first data volume, the LCGID0 and the second data volume at the same time.

In some optional embodiments, the terminal may determine the first identifier and the second identifier according to the attribute information of the data to be transmitted, the mapping relationship between the different identifiers and the different carrier frequency sets, and in particular may determine the first identifier and the second identifier according to the mapping relationship between the different identifiers and the attribute information of the different data, and the mapping relationship between the different identifiers and the different carrier frequency sets, for example, determining that the first identifier corresponds to the first logical channel, and the second identifier corresponds to the second logical channel. The network equipment can respectively determine the first carrier frequency set corresponding to the first identifier according to the mapping relation between different identifiers and different carrier frequency sets, and further performs resource scheduling for the terminal according to the first carrier frequency set, the first identifier and the first data volume. Or the network device can respectively determine the first carrier frequency set corresponding to the first identifier and the second carrier frequency set corresponding to the second identifier according to the mapping relation between different identifiers and different carrier frequency sets, and further schedule the direct link resource for the terminal according to the first carrier frequency set, the first identifier, the first data amount, the second carrier frequency set, the second identifier, the second data amount and the data attribute of the data.

For example: network device configuration mapping relationship: { reliability identification 1, data priority identification 1}, { reliability identification 2, data priority identification 2}, { reliability identification 1, data priority identification 1}. It is understood that it corresponds to LCGID0, LCGID1, LCGID2, respectively. Assuming that the reliability of the data to be transmitted is identified by 1 and the priority of the data is identified by 1, the terminal determines that LCGID0 and LCGID2 are optional. Further, the network device configures mapping relation between different identifications and different carrier frequency sets: LCGID0, { first carrier frequency set }, LCGID2, { second carrier frequency set }. Assuming that the terminal corresponds the first logical channel to the first carrier frequency set and corresponds the second logical channel to the second carrier frequency set, the terminal determines that the LCGID0 corresponds to the first logical channel and that the LCGID2 corresponds to the second logical channel, and the resource scheduling request sent by the terminal to the network device includes the LCGID0, the first data volume, or includes the LCGID0, the first data volume, the LCGID2 and the second data volume at the same time.

Otherwise, if the terminal corresponds the first logic channel to the second carrier frequency set and corresponds the second logic channel to the first carrier frequency set, the terminal determines that the LCGID0 corresponds to the second logic channel and the LCGID2 corresponds to the first logic channel, and the resource scheduling request sent by the terminal to the network device includes the LCGID0, the second data volume, or the LCGID2 and the first data volume, or includes the LCGID0, the second data volume, the LCGID2 and the first data volume at the same time.

Alternatively, the mapping relationship between the different identifiers and the different carrier frequency sets may be sent to the terminal by the network device. Further optionally, the order of the first data amount and the second data amount in the resource scheduling request is the same as the order of the first carrier frequency set and the second carrier frequency set in the configuration information.

Alternatively, the mapping relationship between the different identifications and the different data attribute information may also be included in the configuration information.

Alternatively, the mapping relationship between the different identities and the different carrier frequency sets may be included in the configuration information.

Alternatively, the mapping relationship between the different identities and the different carrier frequency sets may be explicit or implicit.

Alternatively, the mapping relationship between the different identifiers and the different carrier frequency sets may only include the different identifiers, that is, the mapping relationship between the different identifiers and the different carrier frequency sets is indicated by the different identifiers.

Alternatively, the first identifier may be a group identifier of the first logical channel, such as a first LCGID. Further alternatively, the second identifier may be a group identifier of the second logical channel, such as a second LCGID. Further optionally, the resource scheduling request may further include information of each identifier or Destination (Destination) address corresponding to each data amount, for example, an index of the Destination address, where the Destination address index points to the Destination address identifier.

For example, the configuration information sent by the network device to the terminal includes carrier frequency sets { f1, f2} and { f3, f4}, assuming that the terminal determines that logical channel 1 corresponds to carrier frequency { f1, f2}, logical channel 2 corresponds to carrier frequency { f3, f4}, i.e., data in logical channel 1 is allowed to be transmitted on scheduled resources on f1 and/or f2, and data in logical channel 2 is allowed to be transmitted on scheduled resources on f3 and/or f 4. The terminal may send a resource scheduling request including at least a first identifier and a first data amount, and/or a second identifier and a second data amount to the network device according to attribute information of the data to be transmitted.

As shown in fig. 5, an example of a format of a resource scheduling request including N sets of information, each set of information including an index (Destination index) of a destination address, an identification such as LCGID, and a data amount (Buffer Size). The network device is responsible for scheduling resources for the terminal, and if the network device schedules resources on carrier frequency f1 for the terminal according to the resource scheduling request, the terminal is allowed to transmit data in logical channel 1 using carrier frequency f 1. If the network device schedules the resource on carrier frequency f2 for the terminal according to the resource scheduling request, the terminal is allowed to transmit data in logical channel 1 using carrier frequency f 2.

It should be noted that, in the single scheduling, the network device schedules the resource on the carrier frequency f1, which does not mean that the data in the logical channel 1 is necessarily transmitted. Since there may be multiple logical channels in the terminal, all of the multiple logical channels may utilize the resources on f1 to transmit, where the multiple logical channels may have different priorities, and since the total amount of scheduled resources is fixed, how much data can be transmitted in each logical channel may be determined according to the priorities until the scheduled resources are exhausted. At this point it may be difficult for some of the low priority logical channels to get an opportunity to transmit the data in their logical channels.

In the embodiment of the invention, the network equipment can determine the carrier frequency set for data transmission for the first logic channel and the second logic channel according to the configuration information by sending the configuration information comprising the first carrier frequency set and the second carrier frequency set to the terminal, so that when the data transmission is required, the terminal can determine the first identifier according to the attribute information of the data to be transmitted, and send a resource scheduling request comprising the first identifier, the first data volume and other information to the network equipment, so that the network equipment can determine the attribute information of the data corresponding to the first identifier according to the mapping relation of preset different identifiers and the attribute information of different data, and schedule the through link resource for the terminal according to the attribute information of the data and the first data volume, thereby being beneficial to realizing the resource scheduling of the network equipment to the terminal.

Referring to fig. 6, fig. 6 is an interaction schematic diagram of another resource scheduling method according to an embodiment of the present invention. Specifically, as shown in fig. 6, the resource scheduling method in the embodiment of the present invention may include the following steps:

601. the network device sends configuration information to the terminal, the configuration information including a first carrier frequency set and a second carrier frequency set.

602. And the terminal respectively determines carrier frequency sets for data transmission for the first logic channel and the second logic channel according to the configuration information.

The steps 601-602 may refer to the related descriptions of the steps 401-402 in the embodiment shown in fig. 4, which are not repeated herein.

603. The network device sends first mapping information to the terminal, wherein the first mapping information is used for indicating mapping relations of different identifications and attribute information of different data.

Optionally, the mapping relationship between the different identifiers and the attribute information of the different data may be completed through one RRC signaling, may be completed through a plurality of RRC signaling, or may be sent through other signaling, which is not limited in this application.

Alternatively, the mapping relationship indicated by the first mapping information may be indicated explicitly or implicitly, and may specifically refer to the related description of the embodiment shown in fig. 4, which is not described herein.

Optionally, the mapping relationship between the identifier and the data attribute information in the first mapping information may be one-to-one, one-to-many, many-to-one, and the application is not limited.

Alternatively, the configuration information and the first mapping information may be included in the same RRC signaling.

It should be noted that, the present application does not limit the execution sequence of step 603 and step 601. Illustratively, the network device may execute 601 first and then execute 603; or execute 603 first and then execute 601; or step 601 and step 603 are performed simultaneously.

604. And the terminal determines the first identifier and the second identifier according to the first mapping information and the attribute information of the data. The terminal can receive the first mapping information from the network device, and further determine an identifier corresponding to the attribute information of the data to be transmitted according to the mapping relation corresponding to the first mapping information. In this embodiment, the determined identifier includes a first identifier and a second identifier. For example, the terminal may determine the first identifier and the second identifier according to the first mapping information and attribute information of the data, respectively, and correspond the first identifier to the first logical channel, and correspond the second identifier to the second logical channel. For another example, the terminal may determine the first identifier and the second identifier according to the first mapping information, attribute information of the data, and a correspondence between an element in the first mapping information agreed by a protocol and a carrier frequency set, and correspond the first identifier to the first logical channel, and correspond the second identifier to the second logical channel. For another example, the terminal may further receive second mapping information from the network device, where the second mapping information is used to indicate mapping relationships between different identifiers and different carrier frequency sets, and further the terminal may determine, according to the first mapping information, the second mapping information, and attribute information of the data to be transmitted, a first identifier and a second identifier, where the first identifier corresponds to the first logical channel, and the second identifier corresponds to the second logical channel. Reference is made in particular to the relevant description of the embodiment shown in fig. 4, which is not repeated here.

Alternatively, the first identifier may be a group identifier of the first logical channel, such as LCGID, and the second identifier may be a group identifier of the second logical channel, such as LCGID.

Optionally, the mapping relationship indicated by the second mapping information may be explicitly indicated or implicitly indicated, which is similar to the first mapping information described above and is not described herein.

Optionally, the mapping relationship between the identifier and the carrier frequency set in the second mapping information may be one-to-one, one-to-many, many-to-one, and the application is not limited.

Alternatively, the configuration information, the first mapping information, and the second mapping information may be included in the same RRC signaling.

605. The terminal sends a resource scheduling request to the network device, wherein the resource scheduling request comprises the first identifier, the second identifier, the first data volume and the second data volume.

Wherein the first data amount at least includes a data amount of the first logical channel, the second data amount at least includes a data amount of the second logical channel, and the resource scheduling request is operable to request the network device to schedule a through link resource for the terminal.

It should be understood that, when the terminal sends the resource scheduling request, the resource scheduling request may include only the first identifier, the first data amount, or only the second identifier, the second data amount, or include the first identifier, the second identifier, the first data amount, and the second data amount. For example, when the uplink resource is not enough, the reporting can be cut off, and only partial information can be reported, for example, only the first identifier and the first data volume are reported in the current resource scheduling request, and then the second identifier and the second data volume are reported in the next resource scheduling request. The present embodiment is described taking the example that the resource scheduling request includes the first identifier, the second identifier, the first data amount and the second data amount.

606. The network equipment determines attribute information of data corresponding to the first identifier according to preset mapping relations between different identifiers and attribute information of different data, and the network equipment determines the first carrier frequency set corresponding to the first identifier and the second carrier frequency set corresponding to the second identifier according to mapping relations between different identifiers and different carrier frequency sets.

607. And the network equipment schedules the direct link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume and the attribute information of the data.

The network device may receive the resource scheduling request from the terminal, and further determine attribute information corresponding to the first identifier and/or the second identifier, such as reliability information, delay information, communication distance information, data rate information, data priority information, data service type information, and the like, according to the mapping relationship between the different identifiers and attribute information of different data; further, the network device may further determine carrier frequency sets corresponding to the first identifier and the second identifier according to mapping relationships between different identifiers and different carrier frequency sets, so that the network device may schedule resources, such as through link resources, for the terminal according to data attribute information corresponding to the first identifier, that is, attribute information of data to be transmitted, first data amount and second data amount of a logical channel corresponding to different carrier frequencies carried by the resource scheduling request, and the determined carrier frequency sets.

In the embodiment of the invention, the network equipment can determine the carrier frequency set for data transmission for the first logic channel and the second logic channel according to the configuration information by sending the configuration information comprising the first carrier frequency set and the second carrier frequency set to the terminal, so that when the data transmission is required, the terminal can determine the first identifier and the second identifier according to the attribute information of the data to be transmitted and various mapping information, and send a resource scheduling request comprising the first identifier, the second identifier, the first data volume and the second data volume to the network equipment, so that the network equipment can determine the attribute information of the data corresponding to the first identifier according to the preset mapping information, and schedule the direct link resource for the terminal according to the attribute information of the data, the first data volume and the second data volume. That is, the terminal can distinguish the logic channels for repeated data transmission by reporting the first identifier and the second identifier, so that the network device can determine the data quantity of the logic channels corresponding to different carrier frequencies, thereby being beneficial to realizing the resource scheduling of the network device to the terminal.

Referring to fig. 7, fig. 7 is an interaction schematic diagram of another resource scheduling method according to an embodiment of the present invention. Specifically, as shown in fig. 7, the resource scheduling method in the embodiment of the present invention may include the following steps:

701. The network device sends configuration information to the terminal, the configuration information including a first carrier frequency set and a second carrier frequency set.

702. And the terminal respectively determines carrier frequency sets for data transmission for the first logic channel and the second logic channel according to the configuration information.

The steps 701-702 may refer to the related descriptions of the steps 401-402 in the embodiment shown in fig. 4, which are not repeated herein.

703. The network device sends first mapping information to the terminal, wherein the first mapping information is used for indicating mapping relations of different identifications and attribute information of different data.

Optionally, the mapping relationship indicated by the first mapping information may be explicitly indicated or implicitly indicated, which is not described herein.

It should be noted that, the present application does not limit the execution sequence of step 703 and step 701. Illustratively, the network device may execute 701 first and then execute 703; or execute 703 first and then 701; or step 701 and step 703 are performed simultaneously.

704. And the terminal determines the first identification according to the first mapping information and the attribute information of the data.

The terminal can receive the first mapping information from the network device, and further determine an identifier corresponding to the attribute information of the data to be transmitted according to the mapping relation corresponding to the first mapping information. In this embodiment, the determined identifier includes only one identifier, i.e., the first identifier.

705. The terminal sends a resource scheduling request to the network device, the resource scheduling request comprising the first identification, the first data amount and the second data amount.

The resource scheduling request is used for requesting the network equipment to schedule the through link resource for the terminal. The first data volume includes at least a data volume of the first logical channel, and the second data volume includes at least a data volume of the second logical channel. In this embodiment, the order of the first data amount and the second data amount in the resource scheduling request may be the same as the order of the first carrier frequency set and the second carrier frequency set in the configuration information, so that the network device distinguishes the data amounts of the logical channels corresponding to different carrier frequencies.

Alternatively, the first identifier may be a group identifier of the first logical channel, such as an LCGID.

706. The network equipment determines attribute information of data corresponding to the first identifier according to a preset mapping relation between different identifiers and attribute information of different data, and determines the first carrier frequency set and the second carrier frequency set according to the sequence of the first data volume and the second data volume in the resource scheduling request.

707. And the network equipment schedules the direct link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume and the attribute information of the data.

The network device may receive the resource scheduling request from the terminal, and further determine attribute information corresponding to the first identifier, such as reliability information, delay information, communication distance information, data rate information, data priority information, data service type information, and so on, according to the mapping relationship between the different identifiers and attribute information of different data. Further, the network device may determine, according to the order of the first data amount and the second data amount in the resource scheduling request, a carrier frequency set corresponding to the first data amount and the second data amount, for example, the first data amount is before the second data amount is after the first data amount in the resource scheduling request, the first carrier frequency set is before the second carrier frequency set is after the second carrier frequency set in the configuration information, and then the network device may determine that the carrier frequency set corresponding to the first data amount is the first carrier frequency set, and the carrier frequency set corresponding to the second data amount is the second carrier frequency set. The network device can schedule resources, such as through link resources, for the terminal according to the data attribute information corresponding to the first identifier, namely attribute information of the data to be transmitted, the first data volume and the second data volume of the logic channels corresponding to different carrier frequencies carried by the resource scheduling request, and the determined carrier frequency set.

In the embodiment of the invention, the network equipment can determine the carrier frequency set for data transmission for the first logic channel and the second logic channel according to the configuration information by sending the configuration information comprising the first carrier frequency set and the second carrier frequency set to the terminal, so that when the data transmission is required, the terminal can determine the first identifier according to the attribute information of the data to be transmitted and various mapping information, and send a resource scheduling request comprising the first identifier, the first data volume and the second data volume to the network equipment, so that the network equipment can determine the attribute information of the data corresponding to the first identifier according to the preset mapping information, and schedule the direct link resource for the terminal according to the attribute information of the data, the first data volume and the second data volume. That is, the terminal can distinguish the logic channels for repeated data transmission according to the sequence of the first data volume and the second data volume in the resource scheduling request by reporting the first identifier, so that the network device can determine the data volumes of the logic channels corresponding to different carrier frequencies, thereby being beneficial to realizing the resource scheduling of the network device to the terminal.

Referring to fig. 8, fig. 8 is an interaction schematic diagram of another resource scheduling method according to an embodiment of the present invention. Specifically, as shown in fig. 8, the resource scheduling method in the embodiment of the present invention may include the following steps:

801. the network device generates resource scheduling information including a first resource and a first characteristic corresponding to the first resource.

802. The network device sends the resource scheduling information to the terminal.

In some embodiments, the network device may configure resources, i.e., transmit resource scheduling information, for the terminal through a system information block (System Information Block, abbreviated SIB) or dedicated radio resource control information (Dedicated Radio Resource Control); or, the network device may configure resources for the terminal through a downlink physical control channel (Physical Downlink Control Channel, abbreviated PDCCH); alternatively, the network device may configure resources for the terminal through a control element MAC control element (abbreviated as CE) of the medium access control layer, etc., which is not limited in this application.

Alternatively, the scheduling resource, i.e. the first resource, may be a resource dynamically or semi-statically scheduled by the network device for the terminal, or the resource scheduling information is sent to the terminal by the network device in a dynamic or semi-static manner.

Optionally, the terminal may send a resource scheduling request to the network device, and the network device sends the resource scheduling information to the terminal after receiving the resource scheduling request. Alternatively, the network device may actively send the resource scheduling information to the terminal, such as dynamically or semi-statically, i.e. the network device may send the resource scheduling information directly to the terminal without the terminal having to send a resource scheduling request to the network device.

Alternatively, the resource scheduling information may be included in a plurality of RRC signaling, which is not limited in the present application.

Optionally, the correspondence between the first resource and the first characteristic may be explicit or implicit.

803. The terminal encapsulates data of at least one logical channel supporting the first characteristic into a medium access control layer protocol data unit (Media Access control Protocol Data Unit, abbreviated: MAC PDU).

Wherein the supporting of the first characteristic by the logical channel may mean that data in the logical channel may be carried on resources having the first characteristic. The at least one logical channel supporting the first characteristic is a logical channel capable of using the first resource.

804. The terminal utilizes the first resource and transmits the MAC PDU over the pass-through link.

The terminal may receive resource scheduling information from the network device, and may further encapsulate data of at least one logical channel supporting the first characteristic into a MAC PDU, and transmit the MAC PDU through the through link and using the first resource.

Optionally, the first characteristic includes at least one of: modulation coding scheme information, retransmission number information, transmission power information, access technology information, through link control information (Sidelink Control Information, abbreviated SCI) format information, version number information, and the like.

Taking the first characteristic as an example, modulation coding scheme information is included. The modulation and coding scheme information may be used to indicate a modulation and coding scheme that is allowed or not allowed to be used on the first resource. Since the service included in a part of the logical channels may have a high requirement on transmission reliability, in order to ensure transmission reliability, the data in the logical channels may be required to be performed in a low modulation and coding manner. For example, the modulation coding mode corresponding to the logical channel 1 is binary phase shift keying (Binary Phase Shift Keying, abbreviated: BPSK), quadrature phase shift keying (Quadrature Phase Shift Keying, abbreviated: QPSK), and the coding mode corresponding to the logical channel 2 is 16 quadrature amplitude modulation (Quadrature Amplitude Modulation, abbreviated: QAM), if the modulation coding mode information points to 16QAM, the logical channel supports the first characteristic at this time, and may be carried on the scheduling resource, i.e., the first resource.

It can be appreciated that the first resource includes a plurality of time-frequency resources, which can be used for data transmission.

For another example, if the modulation coding scheme information indicates that 16QAM is not allowed to be used, it indicates that logical channel 2 does not support the first characteristic.

Alternatively, the modulation coding scheme information may be a modulation coding scheme index, an indication (such as indicating whether to allow use of one or more modulation coding schemes), or other information pointing to the modulation coding scheme, which is not limited in this application.

Alternatively, for a certain modulation coding scheme, whether to allow or not may be indicated by different values, for example, 1/True indicates allowing, 0/False indicates disallowing, or vice versa.

Alternatively, the modulation coding scheme information may also point to a set of modulation coding schemes, for example, the modulation coding scheme information may point to BSPK, QPSK, and 16QAM, and then the data in both logical channel 1 and logical channel 2 may be carried by using the scheduling resource.

Wherein the retransmission number information may be used to indicate the number of retransmissions allowed or not allowed using the hybrid automatic repeat request (Hybrid Automatic Repeat Request, abbreviated: HAQR) on the first resource.

Wherein the transmit power information may be used to indicate a maximum transmit power, a minimum transmit power, or a range of transmit powers allowed to be used on the first resource, or may be used to indicate a power not allowed to be used on the first resource.

Wherein the version number information may be used to point to one or more different 3GPP defined protocol versions. As 3GPP protocols continue to evolve, there are a number of different versions. Different versions of the protocol may include different characteristics or transmission techniques, and the different versions may be identified by version numbers. Taking V2X as an example, the earliest version of the 3GPP definition that supports V2X features is the R14 version, and the current R15 version is being standardized, and there may be different versions of R16, R17, etc. in the following. Where the R14 version is one that does not support higher order modulation (e.g., 64 QAM) and the R15 version supports higher order modulation (e.g., 64 QAM). Therefore, when the version number information indicates the R15 version, if data in a certain logical channel does not support data transmission using high order modulation (64 QAM), the data in the logical channel cannot be carried on the scheduling resource at this time.

Where access technology information may be used to indicate different access technologies, e.g., where there are multiple different access technologies, e.g., GSM, CDMA, LTE, NR, etc., different access technology physical layers may employ disparate frame formats. Therefore, when the access technology information indicates a certain access technology, only the data supporting the logical channel corresponding to the access technology is allowed to be transmitted by using the scheduling resource, i.e., the first resource. For example, when the access technology information indicates LTE, only data of a logical channel supporting LTE is allowed to be transmitted using the first resource.

The SCI format information may be used to indicate the through link control information included in a physical through link control channel (Physical Sidelink Control Channel, abbreviated PSCCH), which is also referred to as a PSCCH transmission format, and the receiving end may obtain the time-frequency location and other transmission parameters of the through link data packet according to the SCI information, so as to obtain the transmission data packet. For example, the SCI may include information such as priority of current data, resource reservation period, retransmission number, time-frequency location of resource, etc. The physical layer may define a number of different SCI formats to meet various types of through link scheduling or configuration requirements. For example, different SCI formats may be defined in order to support different transmission characteristics. Illustratively, if the Sidelink supports transmit diversity (Tx diversity), then there must be a field (explicit or implicit) in the SCI format to indicate whether the Tx diversity is used for the current transmission. Further, the SCI format information may include parameters related to Tx diversity, so that the receiving end may obtain the information, and thus perform corresponding processing. For another example, in order to support 64QAM, the modulation coding scheme field in the SCI format may include information about whether 64QAM is supported, such as an index indicating 64QAM, indicating that 64QAM is supported for the SCI format. It will be appreciated that for a field in both SCI formats (e.g., a field indicating modulation and coding schemes), it is considered a different SCI format if the same value indicates a different physical meaning. The first characteristic may be SCI format information, and only a logical channel supporting the transmission format may use the first resource for data transmission.

It should be noted that, for a certain logical channel supporting the first characteristic, it does not mean that, in each scheduling, data in the logical channel can be transmitted by using the scheduling resource. Since the terminal may have multiple logical channels, which are all supported by the first characteristic, the multiple logical channels may have different priorities, and since the total amount of scheduling resources is constant, a certain amount of data may be sequentially encapsulated into the MAC PDU according to the priorities until the scheduling resources are exhausted. At this point it may be difficult for some low priority logical channels to get an opportunity to encapsulate data, i.e., there is no opportunity to utilize the scheduling resources to transmit data in the logical channels. Alternatively, the priority of the logical channels may be pre-configured.

Optionally, when the first characteristic includes a plurality of choices, the terminal may perform data transmission according to one of the characteristics corresponding to the plurality of choices. For example, when the multiple choices are not available at the same time, the terminal may autonomously determine one of them and then encapsulate the logical channel data supporting the selected characteristic into a MAC PDU. Taking the example that the first characteristic includes version number information, assuming that the resource scheduling information includes the first characteristic as R14 or R15, assuming that R14 and R15 have different data formats and cannot be simultaneously used, at this time, it is obvious that the terminal can only use one of them, and then the terminal can determine whether to use R14 or R15 by itself, for example, the terminal determines R14, and the terminal encapsulates at least one logical channel data supporting R14 into a MAC PDU and transmits the MAC PDU using the first resource.

Optionally, the first characteristic may be a combination of modulation coding scheme information, retransmission number information, transmission power information, access technology information, SCI format information, and version number information. That is, a plurality of information in modulation coding scheme information, retransmission times information, transmission power information, access technology information, SCI format information, and version number information are simultaneously embodied by a single information element. For example, the first characteristic may be modulation and coding scheme information of R15, and the logical channel supporting the modulation and coding scheme of R15 allows the first resource to be used.

In the embodiment of the invention, the network equipment sends the resource scheduling information for indicating the scheduling resource of the terminal and the characteristic corresponding to the scheduling resource to the terminal, so that the terminal can package the data of at least one logic channel supporting the characteristic into the MAC PDU and send the MAC PDU through the through link by utilizing the scheduling resource, thereby being beneficial to realizing the resource scheduling of the network equipment to the terminal.

It is to be understood that each embodiment of the present application may be implemented independently or in combination with other embodiments, and the present application is not limited thereto.

The foregoing method embodiments are all illustrative of the resource scheduling method of the present application, and the descriptions of the embodiments are all focused, and for the part of a certain embodiment that is not described in detail, reference may be made to the related descriptions of other embodiments.

Fig. 9 shows a schematic diagram of a possible structure of the terminal according to the above embodiment, and referring to fig. 9, the terminal 900 may include: a communication unit 901 and a processing unit 902. Wherein these units may perform the respective functions of the terminal in the method examples described above, e.g. a communication unit 901 for receiving configuration information from a network device, the configuration information comprising a first set of carrier frequencies and a second set of carrier frequencies; a processing unit 902, configured to determine a carrier frequency set for performing data transmission for the first logical channel and the second logical channel according to the configuration information; the processing unit 902 is further configured to determine a first identifier according to attribute information of data to be transmitted, where the attribute information includes at least one of reliability information, delay information, communication distance information, data rate information, data priority information, and data service type information; the communication unit 901 is further configured to send a resource scheduling request to a network device, where the resource scheduling request includes the first identifier and a first data volume, where the first data volume includes at least a data volume of the first logical channel, and the resource scheduling request is used to request the network device to schedule a through link resource for the terminal.

Optionally, the communication unit 901 is further configured to receive first mapping information from the network device, where the first mapping information is used to indicate a mapping relationship between different identifiers and attribute information of different data;

the processing unit 902 is specifically configured to determine the first identifier according to the first mapping information and attribute information of the data.

Optionally, the processing unit 902 is further configured to determine a second identifier according to the first mapping information and attribute information of the data;

the first identifier corresponds to the first logic channel, the second identifier corresponds to the second logic channel, the resource scheduling request further comprises the second identifier and a second data volume, and the second data volume at least comprises the data volume of the second logic channel.

Optionally, the communication unit 901 is further configured to receive second mapping information from the network device, where the second mapping information is used to indicate mapping relationships between different identifiers and different carrier frequency sets;

the processing unit 902 is further configured to determine a second identifier according to attribute information of data to be transmitted and the second mapping information, where the resource scheduling request further includes the second identifier and a second data amount, and the second data amount includes at least a data amount of the second logical channel;

The processing unit 902 is specifically configured to determine the first identifier according to attribute information of data to be transmitted and the second mapping information, where the first identifier corresponds to the first logical channel, and the second identifier corresponds to the second logical channel.

Optionally, the first identifier is a group identifier of the first logical channel.

Optionally, the second identifier is a group identifier of the second logical channel.

Optionally, the resource scheduling request further includes a second data volume, where the second data volume includes at least a data volume of a second logical channel, and an order of the first data volume and the second data volume in the resource scheduling request is the same as an order of the first carrier frequency set and the second carrier frequency set in the configuration information.

And/or the communication unit 901 is configured to receive resource scheduling information from a network device, where the resource scheduling information includes a first resource and a first characteristic corresponding to the first resource;

the processing unit 902 is configured to encapsulate data of at least one logical channel into a media access control layer protocol data unit MAC PDU, where the at least one logical channel supports the first characteristic;

The communication unit 901 is further configured to send the MAC PDU using the first resource and through a through link.

Wherein the first characteristic comprises at least one of:

The terminal may implement some or all of the steps performed by the terminal in the resource scheduling method in the embodiments shown in fig. 4 to 8 through the unit. It should be understood that the embodiments of the present invention are apparatus embodiments corresponding to the method embodiments, and the description of the method embodiments also applies to the embodiments of the present invention.

It should be noted that, in the embodiment of the present invention, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. The functional units in the embodiment of the invention can be integrated in one processing unit, or each unit can exist alone physically, or two or more units are integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

In the case of using an integrated unit, fig. 10 shows another possible structural schematic diagram of the terminal involved in the above embodiment, and as shown in fig. 10, the terminal 1000 may include: a processing unit 1002, and a communication unit 1003. The processing unit 1002 may be configured to control and manage actions of the terminal, e.g., the processing unit 1002 may be configured to support the terminal to perform the processes 402, 403 in fig. 4, the processes 602, 604 in fig. 6, the processes 702, 704 in fig. 7, the process 803 in fig. 8, and/or other processes for the techniques described herein. The communication unit 1003 may be used to support communication between the terminal and other network entities, such as with the network entities shown in fig. 4-8, such as network devices, for example, the communication unit 1003 is used to support the terminal to perform the processes 401, 404 in fig. 4, the processes 601, 603, 605 in fig. 6, the processes 701, 703, 705 in fig. 7, the processes 802, 804 in fig. 8, etc., and/or other processes for the techniques described herein. The terminal may further comprise a storage unit 1001 for storing program code and data of the terminal.

The processing unit 1002 may be a processor or controller, such as a central processing unit (Central Processing Unit, abbreviated as CPU), a general purpose processor, a digital signal processor (digital signal processor, abbreviated as DSP), an application-specific integrated circuit (application-specific integrated circuit, abbreviated as ASIC), a field programmable gate array (field programmable gate array, abbreviated as FPGA) or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication unit 1003 may be a transceiver. The storage unit 1001 may be a memory.

Referring to fig. 11, in another embodiment, the terminal 1100 may include: a processor 1102, a transceiver 1103 and a memory 1101. Wherein the transceiver 1103, the processor 1102 and the memory 1101 are interconnected. Wherein the processor may perform the functions of the processing unit 1002, the transceiver may function similarly to the communication unit 1003, and the memory may function similarly to the storage unit 1001. The transceiver 1103 may include or be integrated with a receiver and a transmitter, and is not limited in this application. Optionally, the terminal 1100 may further include a bus 1104, where the bus 1104 may be a peripheral component interconnect standard (peripheral component interconnect, abbreviated: PCI) bus or an extended industry standard architecture (extended industry standard architecture, abbreviated: EISA) bus, etc. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in FIG. 11, but not only one bus or one type of bus.

It should be understood that, in the present application, each unit (communication unit, processing unit, etc.) or device (transceiver, processor, etc.) in the above-mentioned terminal may jointly implement a step or an action of the terminal in some or all embodiments in the present application, or may implement a step or an action of the terminal in any embodiment in the present application alone, which is not limited in this application.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware, or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in random access memory (random access memory, abbreviated as RAM), flash memory, read Only Memory (ROM), erasable programmable read only memory (erasable programmable ROM, abbreviated as EPROM), electrically erasable programmable read only memory (electrically ePROM, abbreviated as EEPROM), registers, hard disk, a removable disk, a compact disc read only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a terminal. The processor and the storage medium may reside as discrete components in a terminal.

Fig. 12 shows a schematic diagram of a possible architecture of the network device involved in the above embodiment, and referring to fig. 12, the network device 1200 may include: a communication unit 1201 and a processing unit 1202. Wherein these units may perform the respective functions of the network device in the above method example, e.g. the communication unit 1201 for sending configuration information to the terminal, the configuration information comprising a first set of carrier frequencies and a second set of carrier frequencies; the communication unit 1201 is further configured to receive a resource scheduling request from the terminal, where the resource scheduling request includes a first identifier and a first data volume, where the first data volume includes at least a data volume of the first logical channel, and the resource scheduling request is used to request to schedule a through link resource for the terminal; a processing unit 1202, configured to determine attribute information of data corresponding to the first identifier according to a preset mapping relationship between different identifiers and attribute information of different data, where the attribute information includes at least one of reliability information, delay information, communication distance information, data rate information, data priority information, and data service type information; the processing unit 1202 is further configured to schedule a through link resource for the terminal according to the attribute information of the data and the first data amount.

Optionally, the resource scheduling request further includes a second identifier and a second data volume, where the second data volume includes at least a data volume of a second logical channel;

the processing unit 1202 is specifically configured to determine, according to mapping relationships between different identifiers and different carrier frequency sets, the first carrier frequency set corresponding to the first identifier and the second carrier frequency set corresponding to the second identifier; and scheduling a through link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume and the attribute information of the data.

Optionally, the resource scheduling request further includes a second data amount, where the second data amount includes at least a data amount of a second logical channel;

the processing unit 1202 is further configured to determine the first carrier frequency set and the second carrier frequency set according to an order of the first data amount and the second data amount in the resource scheduling request, where the order of the first data amount and the second data amount in the resource scheduling request is the same as an order of the first carrier frequency set and the second carrier frequency set in the configuration information;

The processing unit 1202 is specifically configured to schedule a through link resource for the terminal according to the first carrier frequency set, the second carrier frequency set, the first data volume, the second data volume, and attribute information of the data.

Optionally, the communication unit 1201 is further configured to send first mapping information to the terminal, where the first mapping information is used to indicate a mapping relationship between different identifiers and attribute information of different data.

Optionally, the communication unit 1201 is further configured to send second mapping information to the terminal, where the second mapping information is used to indicate a mapping relationship between different identifiers and different carrier frequency sets.

And/or the processing unit 1202 is configured to generate resource scheduling information, where the resource scheduling information includes a first resource and a first characteristic corresponding to the first resource;

the communication unit 1201 is configured to send the resource scheduling information to a terminal.

Wherein the first characteristic comprises at least one of:

The network device may implement, through the unit, part or all of the steps performed by the network device, such as a base station, in the resource scheduling method in the embodiments shown in fig. 4 to 8. It should be understood that the embodiments of the present invention are apparatus embodiments corresponding to the method embodiments, and the description of the method embodiments also applies to the embodiments of the present invention.

In the case of an integrated unit, fig. 13 shows another possible structural schematic diagram of the network device involved in the above embodiment, and as shown in fig. 13, the network device 1300 may include: a processing unit 1302, and a communication unit 1303. The processing unit 1302 may be configured to control and manage actions of the network device, e.g., the processing unit 1302 may be configured to support the network device to perform the process 405 of fig. 4, the processes 606, 607 of fig. 6, the processes 706, 707 of fig. 7, the process 801 of fig. 8, etc., and/or other processes for the techniques described herein. The communication unit 1303 is configured to support communication between the network device and other network entities, such as the network entities like terminals shown in fig. 4-8, e.g., the communication unit 1303 is configured to support the network device to perform the processes 401, 404 in fig. 4, the processes 601, 603, 605 in fig. 6, the processes 701, 703, 705 in fig. 7, the processes 802, 804 in fig. 8, etc., and/or other processes for the techniques described herein. The network device may also include a storage unit 1301 for storing program code and data of the network device.

The processing unit 1302 may be a processor or controller, such as a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware components, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication unit 1303 may be a transceiver. The storage unit 1301 may be a memory.

Referring to fig. 14, in another embodiment, the network device 1400 may include: a processor 1402, a transceiver 1403 and a memory 1401. Wherein the transceiver 1403, the processor 1402 and the memory 1401 are connected to each other. Wherein the processor may perform the functions of the processing unit 1302, the transceiver may function similarly to the communication unit 1303, and the memory may function similarly to the storage unit 1301. The transceiver 1403 may include or be integrated with a receiver and a transmitter, which is not limited in this application. Optionally, the network device 1400 may also include a bus 1404, where the bus 1404 may be a PCI bus or an EISA bus, etc. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 14, but not only one bus or one type of bus.

It should be understood that, in the present application, each unit (communication unit, processing unit, etc.) or device (transceiver, processor, etc.) in the above network device may jointly implement a step or an action of the network device in some or all embodiments in the present application, or may implement a step or an action of the network device in any embodiment in the present application alone, which is not limited in the present application.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied in hardware, or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, a removable disk, a read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may reside in a network device. The processor and the storage medium may reside as discrete components in a network device.

The application further provides a communication system, which comprises the terminal and the network device, wherein the terminal and the network device can adopt the resource scheduling method for communication, and the details are omitted here. Optionally, the system may further include other devices that interact with the terminal and/or the network device in the solution provided by the embodiment of the present invention.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method. To avoid repetition, a detailed description is not provided herein.

It should also be understood that the first, second, third, fourth and various numerical numbers referred to herein are merely descriptive convenience and are not intended to limit the scope of embodiments of the present invention.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

Those of ordinary skill in the art will appreciate that the various illustrative logical blocks (illustrative logical block) and steps (steps) described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

Claims

1. A method for scheduling resources, comprising:

receiving resource scheduling information from a network device, the resource scheduling information comprising a first resource and a first characteristic for indicating one or more of a first version and a second version;

determining a format in which the first version is employed;

encapsulating data of at least one logical channel corresponding to the format of the first version into a medium access control layer protocol data unit;

and transmitting the media access control layer protocol data unit by using the first resource through a through link.

2. The method of claim 1, wherein the first characteristic comprises at least one of:

3. The method according to claim 1 or 2, wherein the medium access control layer protocol data unit does not comprise data of a logical channel corresponding to the format of the second version.

4. The method of claim 1 or 2, the first version being R14 and the second version being R15.

5. A method for scheduling resources, comprising:

Generating resource scheduling information, the resource scheduling information including a first resource and a first characteristic for indicating one or more of a first version and a second version; the first resource is used for transmitting a media access control layer protocol data unit which encapsulates data of at least one logical channel corresponding to the format of the first version or the second version;

and sending the resource scheduling information to the terminal.

6. The method of claim 5, wherein the first characteristic comprises at least one of:

7. The method of claim 5 or 6, the first version being R14 and the second version being R15.

8. A terminal, comprising: a communication unit and a processing unit;

the communication unit is configured to receive resource scheduling information from a network device, the resource scheduling information including a first resource and a first characteristic indicating one or more of a first version and a second version;

the processing unit is configured to determine that the format of the first version is adopted, and encapsulate data of at least one logical channel corresponding to the format of the first version into a media access control layer protocol data unit;

The communication unit is further configured to send the medium access control layer protocol data unit by using the first resource and through a through link.

9. The terminal of claim 8, wherein the first characteristic comprises at least one of:

10. A terminal according to claim 8 or 9, wherein the medium access control layer protocol data unit does not include data of a logical channel corresponding to the format of the second version.

11. The terminal of claim 8 or 9, wherein the first version is R14 and the second version is R15.

12. A network device, comprising: a processing unit and a communication unit;

the processing unit is configured to generate resource scheduling information, where the resource scheduling information includes a first resource and a first characteristic that indicates one or more of a first version and a second version; the first resource is used for transmitting a media access control layer protocol data unit which encapsulates data of at least one logical channel corresponding to the format of the first version or the second version;

The communication unit is configured to send the resource scheduling information to a terminal.

13. The network device of claim 12, wherein the first characteristic comprises at least one of:

14. The network device of claim 12 or 13, wherein the first version is R14 and the second version is R15.

15. A resource scheduling apparatus, comprising:

means for receiving resource scheduling information from a network device, the resource scheduling information comprising a first resource and a first characteristic for indicating one or more of a first version and a second version;

means for determining a format in the first version;

means for encapsulating data of at least one logical channel corresponding to the first version of format into a medium access control layer protocol data unit;

and means for transmitting the medium access control layer protocol data unit over a through link using the first resource.

16. The apparatus of claim 15, wherein the first characteristic comprises at least one of:

17. The apparatus according to claim 15 or 16, wherein the medium access control layer protocol data unit does not include data of a logical channel corresponding to the format of the second version.

18. The apparatus of claim 15 or 16, wherein the first version is R14 and the second version is R15.

19. A resource scheduling apparatus, comprising:

means for generating resource scheduling information comprising a first resource and a first characteristic indicative of one or more of a first version and a second version; the first resource is used for transmitting a media access control layer protocol data unit which encapsulates data of at least one logical channel corresponding to the format of the first version or the second version;

and a module for sending the resource scheduling information to the terminal.

20. The apparatus of claim 19, wherein the first characteristic comprises at least one of:

21. The apparatus of claim 19 or 20, wherein the first version is R14 and the second version is R15.