WO2018218998A1 - Resource scheduling method, terminal device and network side device - Google Patents

Abstract

The present application provides a resource scheduling method, a terminal device and a network side device. The method comprises: a terminal device sending first user plane data to a network side device, the first user plane data carrying application state information concerning the terminal device, the application state information being used for characterizing the operation state of an application of the terminal device; and the terminal device acquiring, from the network side device, a time-frequency resource scheduled by the network side device for the terminal device according to the application state information. In the method of the present application, there is no need to transfer application state information across an RRC layer, improving the resource scheduling efficiency of a network side device, and meanwhile, there is no need for a terminal operating system or a terminal device and a baseband chip of the network side device to develop a version of a transmission channel or a transmission interface from the operating system to the RRC layer, reducing the development cost of the terminal device.

Description

Resource scheduling method, terminal device, and network side device

This application claims the priority of the Chinese Patent Application filed on May 27, 2017, the Chinese Patent Office, the application number is 201710391566.5, and the application is entitled "Resource Scheduling Method, Terminal Equipment and Network Side Equipment", the entire contents of which are incorporated by reference. In this application.

Technical field

The present application relates to communications technologies, and in particular, to a resource scheduling method, a terminal device, and a network side device.

Background technique

At present, the terminal and the network side device cooperate according to the capabilities and status of the two parties, which is an important way to improve the user experience and network resource utilization efficiency. In the case of the mobile internet service, the network side device can notify the terminal of the network capability and the resource usage, and the application (Application, abbreviated as APP) feeds the service application state information to the network side device, so that the network side device can The difference in service application status of different terminals enables differentiated scheduling of resources and improves the user application experience. For example, it is assumed that the video play APPs of the plurality of terminals respectively report information such as the amount of video buffer data and the code rate to the base station, and if the playable duration of the video buffer data amount of one of the plurality of terminals is low, The base station preferentially schedules the terminal in the resource scheduling process (that is, preferentially allocates resources to the terminal), thereby reducing the probability of the video carding of the terminal and improving the video viewing experience of the user.

In the prior art, when the resource scheduling is implemented, the information exchange between the terminal and the network side device is involved. The specific interaction process may include: taking the video playing APP as an example, the modem and the operating system of the terminal provide an interface to the application layer, and the application layer passes the The interface delivers service application state information to a Radio Resource Control (RRC) layer. Then, since the base station opens the coordinated interface of the RRC layer extension to the terminal, the terminal transmits the service application state information to the RRC layer of the base station through the RRC extension signaling. Then, the RRC layer of the base station transmits the service application state information to the Media Access Control (MAC) layer resource scheduler of the base station, so that the MAC layer resource scheduler of the base station performs differentiated resource scheduling on the terminal.

However, in the prior art, when the terminal and the network side device interact with the service application state information, the service application state information needs to be transmitted from the application layer to the RRC layer, and the cross-layer transmission is difficult, resulting in resource scheduling of the network side device to the terminal. low efficiency.

Summary of the invention

The present application provides a resource scheduling method, a terminal device, and a network side device, which are used to solve the problem that the service application state information needs to be transmitted from the application layer to the next layer when the terminal and the network side device are in the interactive service application state information in the prior art. In the RRC layer, cross-layer transmission is difficult, resulting in technical problems in that the resource scheduling of the terminal to the terminal is inefficient.

In a first aspect, the application provides a resource scheduling method, including:

The terminal device sends the first user plane data to the network side device, where the first user plane data carries the application state information of the terminal device; the application state information is used to represent the running state of the application of the terminal device;

The terminal device acquires, from the network side device, a time-frequency resource that the network side device schedules for the terminal device according to the application state information.

Optionally, the first user plane data is data that does not pass through the RRC layer when performing data transmission.

The resource scheduling method provided by the device, the terminal device carries the application state information of the terminal device in the first user plane data, and the network side device obtains the application state of the terminal device by parsing the first user plane data. The information is used to schedule the appropriate time-frequency resources for the terminal device according to the application state information, thereby enhancing the time-effectiveness of air interface transmission between the terminal device and the network-side device, and improving the application experience of the user. The application status information of the terminal device does not need to be transmitted across the RRC layer when it is transmitted from the application layer to the physical layer. Therefore, the problem that the application state information is difficult to be transmitted across layers in the prior art is solved, and the resource scheduling efficiency of the network side device is improved. The baseband chip in the terminal operating system or the terminal device and the network side device is also not required to develop a transmission channel or a transmission interface version from the operating system to the RRC layer, which reduces the development cost of the terminal device.

In a possible design, before the foregoing terminal device sends the first user plane data to the network side device, the method further includes:

The terminal device receives the second user plane data from the network side device, where the second user plane data carries the resource allocation coordination capability between the network side device and the network side device;

The foregoing terminal device sends the first user plane data to the network side device, including:

The terminal device sends the first user plane data to the network side device according to the resource allocation coordination capability between the network side device and the network side device.

In a possible design, the terminal device sends the first user plane data to the network side device according to the resource coordination capability between the network device and the network device, including:

When the application of the terminal device meets the preset triggering condition, the terminal device sends the first user plane data to the network side device according to the resource coordination capability between the network device and the network side device;

The preset triggering condition includes: the application of the terminal device is enabled, the running state of the application of the terminal device changes, the amount of cached data of the application of the terminal device is lower than a first preset threshold, and the application of the terminal device is cached. The amount of data is higher than any of the second predetermined thresholds.

The method provided in each of the foregoing possible designs, the network side device sends the second user plane data carrying the resource allocation coordination capability between the terminal device and the network side device to the terminal device, so that the terminal device can combine the The resource allocation coordination capability determines whether the first user plane data is sent to the network side device, avoids invalid transmission of the terminal device, and saves the erroneous transmission overhead of the terminal device. In addition, the terminal device refers to the network side device to the terminal device and On the basis of the resource allocation coordination capability between the network side devices, the terminal device further determines whether to send the first user plane data to the network side device by using the two triggering conditions, thereby making the terminal device to the network. The side device sends the first user plane data more accurately, improves the air interface transmission accuracy of the terminal device and the network side device, and saves the error transmission overhead of the terminal device.

In a second aspect, the application provides a resource scheduling method, including:

The network side device receives the first user plane data from the terminal device, where the first user plane data carries the application state information of the terminal device; the application state information is used to represent the running state of the application of the terminal device;

The network side device schedules time-frequency resources for the terminal device according to the application state information.

In a possible design, before the network side device receives the first user plane data from the terminal device, the method further includes:

The network side device sends the second user plane data to the terminal device, where the second user plane data carries the resource allocation coordination capability between the network side device and the network side device.

For the beneficial effects of the method provided in the above second aspect and the possible design of the second aspect, reference may be made to the first aspect and the method provided by each possible design of the first aspect, and details are not described herein again.

In combination with the first aspect and the second aspect, in a possible design, the first user plane data includes an uplink network interconnection protocol IP packet.

In the possible design, the application state information is carried in the uplink IP packet, so that the terminal device does not need to transmit across the RRC layer when transmitting the application state information of the application of the terminal device to the network side device, thereby solving the existing In the technology, the application of state information is difficult to cross-layer transmission, and the resource scheduling efficiency of the network side device is improved, and the baseband chip in the terminal operating system or the terminal device and the network side device is not required to develop a transmission channel from the operating system to the RRC layer or The version of the transmission interface reduces the development cost of the terminal device.

In a possible design, the reserved bits in the service type TOS field in the header of the uplink IP packet carry application state information.

In this possible design, by extending the reserved bits in the uplink IP packet into bits carrying the application state information, the bit utilization of the existing IP packet is improved.

In a possible design, the uplink IP packet further includes a first identifier, where the first identifier is used to indicate the type of the application corresponding to the application state information.

In the possible design, the uplink IP packet is a packet customized by the terminal device, and the format of the application state information is not limited to the format of the existing IP packet.

In a possible design, the second user plane data includes a downlink IP packet.

In this possible design, when the network side device informs the terminal device of its own resource allocation cooperation capability, the resource allocation cooperation capability is carried in the downlink IP packet, and the transmission efficiency of the resource is further improved without trans-RRC layer transmission.

In a possible design, the reserved bits in the TOS field in the packet header of the downlink IP packet carry the resource allocation coordination capability between the network device and the network device.

In this possible design, the bit of the existing IP packet is improved by expanding the reserved bit in the downlink IP packet into a bit carrying the resource allocation coordination capability of the network side device.

In a possible design, the uplink IP packet further includes a second identifier, where the second identifier is used to indicate that the uplink IP packet is a packet carrying the application state information.

In the possible design, by carrying the second identifier in the uplink IP packet, the network side device can learn, according to the second identifier, whether the current uplink IP packet is a packet carrying the application state information, thereby Determining whether to parse the uplink IP packet, which avoids blind parsing of the network side device and improves the efficiency of packet parsing.

In a third aspect, in order to implement the resource scheduling method in the foregoing first aspect, the embodiment of the present application provides a terminal device, where the terminal device has a function of implementing the foregoing resource scheduling method. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the third aspect, the terminal device includes multiple function modules or units, and is used to implement any one of the resource scheduling methods in the foregoing first aspect.

In another possible implementation manner of the third aspect, the structure of the terminal device may include a processor and a transceiver. The processor is configured to support the device to perform a corresponding function in any of the resource scheduling methods of the first aspect above. The transceiver is used to support communication between the terminal device and other network devices or terminal devices, and may be, for example, a corresponding radio frequency module or a baseband module. The terminal device may further include a memory for coupling with the processor, which stores program instructions and data necessary for the terminal device to execute the resource scheduling method.

In a fourth aspect, in order to implement the resource scheduling method in the foregoing second aspect, the embodiment of the present application provides a network side device, where the device has the function of implementing the foregoing resource scheduling method. This function can be implemented in hardware or in hardware by executing the corresponding software. The hardware or software herein includes one or more modules corresponding to the functions described above.

In a possible implementation manner of the fourth aspect, the network side device includes multiple function modules or units, and is used to implement any one of the resource scheduling methods in the foregoing second aspect.

In another possible implementation manner of the fourth aspect, the processor and the transceiver may be included in the structure of the network side device. The processor is configured to support the device to perform a corresponding function in any of the resource scheduling methods of the second aspect above. The transceiver is configured to support communication between the network side device and other network devices or terminal devices, and may be, for example, a corresponding radio frequency module or a baseband module. The network side device may further include a memory configured to be coupled to the processor, where the program instructions and data necessary for the network side device to execute the resource scheduling method are saved.

In a fifth aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the terminal device, which includes a program designed to execute the first aspect.

In a sixth aspect, the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the network side device, which includes a program designed to execute the foregoing second aspect.

In a seventh aspect, an embodiment of the present application provides a computer program product, which includes instructions that, when executed by a computer, cause the computer to perform the functions performed by the terminal device in the above method.

In an eighth aspect, an embodiment of the present application provides a computer program product, which includes instructions that, when executed by a computer, cause the computer to perform the functions performed by the network side device in the above method.

In a ninth aspect, the embodiment of the present application further provides a chip system, where the chip system includes a processor for supporting a terminal device to implement functions involved in the foregoing aspects, for example, generating or processing data involved in the foregoing method. / or information. In a possible design, the chip system further comprises a memory for storing necessary program instructions and data of the terminal device. The chip system can be composed of chips, and can also include chips and other discrete devices.

In a tenth aspect, the embodiment of the present application further provides a chip system, where the chip system includes a processor, and is configured to support a network side device to implement the functions involved in the foregoing aspects, for example, generating or processing data involved in the foregoing method. And / or information. In a possible design, the chip system further includes a memory for storing necessary program instructions and data of the network side device. The chip system can be composed of chips, and can also include chips and other discrete devices.

Compared with the prior art, the resource scheduling method, the terminal device, and the network side device provided by the present application, the terminal device transmits the application state information of the terminal device to the network side device by using the first user plane data, and the network side device passes the device. The first user plane data is parsed to obtain the application state information of the terminal device, so that the appropriate time-frequency resource is scheduled for the terminal device according to the application state information, thereby enhancing the air interface transmission time-effectiveness between the terminal device and the network-side device, and improving the user. Application experience. The application status information of the terminal device does not need to be transmitted across the RRC layer when it is transmitted from the application layer to the physical layer. Therefore, the problem that the application state information is difficult to be transmitted across layers in the prior art is solved, and the resource scheduling efficiency of the network side device is improved. The baseband chip in the terminal operating system or the terminal device and the network side device is also not required to develop a transmission channel or a transmission interface version from the operating system to the RRC layer, which reduces the development cost of the terminal device.

DRAWINGS

1 is a schematic structural diagram of a communication system provided by the present application;

2 is a signaling flowchart of Embodiment 1 of a resource scheduling method provided by the present application;

3 is a schematic diagram of data layer transfer provided by the present application;

4 is a schematic structural diagram 1 of an uplink IP packet provided by the present application;

FIG. 5 is a schematic structural diagram 2 of an uplink IP packet provided by the present application;

FIG. 6 is a signaling flowchart of Embodiment 2 of a resource scheduling method provided by the present application;

FIG. 7 is a schematic structural diagram of a downlink IP packet provided by the present application;

FIG. 8 is a schematic flowchart of Embodiment 3 of a resource scheduling method provided by the present application;

FIG. 9 is a signaling flowchart of Embodiment 4 of a resource scheduling method provided by the present application;

FIG. 10 is a schematic structural diagram of Embodiment 1 of a terminal device according to the present application;

FIG. 11 is a schematic structural diagram of Embodiment 1 of a network side device provided by the present application;

FIG. 12 is a schematic structural diagram of Embodiment 2 of a network side device provided by the present application;

FIG. 13 is a schematic structural diagram of Embodiment 2 of a terminal device according to the present application;

FIG. 14 is a schematic structural diagram of Embodiment 3 of a network side device provided by the present application;

FIG. 15 is a schematic structural diagram 1 of a computer program product according to an embodiment of the present application;

FIG. 16 is a schematic structural diagram 1 of a storage medium according to an embodiment of the present disclosure;

FIG. 17 is a second schematic structural diagram of a computer program product according to an embodiment of the present application;

FIG. 18 is a schematic structural diagram 2 of a storage medium according to an embodiment of the present application.

detailed description

The resource scheduling method and apparatus provided by the present application can be applied to the schematic diagram of the communication system architecture shown in FIG. 1. As shown in FIG. 1, the system includes: a network side device 01 and a terminal device 02. It should be noted that the communication system shown in FIG. 1 can be applied to different network standards. For example, it can be applied to Global System of Mobile communication (GSM) and Code Division Multiple Access (Code Division Multiple Access). CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), Frequency Division Duplex Long Term Evolution (Frequency Division) Dual Long Term Evolution (FDD LTE), Time Division Dual Long Term Evolution (TDD LTE) and future 5G network standards.

Therefore, optionally, the network side device 01 may be a base transceiver (Base Transceiver Station, BTS for short) and/or a base station controller in GSM or CDMA, or may be a base station (NodeB, NB for short) in WCDMA and/or A Radio Network Controller (RNC), which may also be an evolved Node B (eNB or eNodeB) in LTE, or a relay station or an access point, or a base station in a future 5G network, etc. The application is not limited here. Optionally, the network side device may be a network element in the core network that has resource scheduling and configuration functions.

The terminal device 02 may be a wireless terminal or a wired terminal. The wireless terminal can be a device that provides voice and/or other service data connectivity to the user, a handheld device with wireless connectivity, or other processing device that is connected to the wireless modem. The wireless terminal can communicate with one or more core networks via a Radio Access Network (RAN), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a mobile terminal. The computer, for example, can be a portable, pocket, handheld, computer built-in or in-vehicle mobile device that exchanges language and/or data with the wireless access network. For example, the wireless terminal may also be a personal communication service (PCS) phone, a cordless phone, a Session Initiation Protocol (SIP) phone, or a Wireless Local Loop (WLL) station. , Personal Digital Assistant (PDA) and other devices. The wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, and a remote terminal. The access terminal, the user terminal (User Terminal), the user agent (User Agent), and the user device (User Device or User Equipment) are not limited herein.

The technical solutions of the present application and the technical solutions of the present application are described in detail in the following specific embodiments to solve the above technical problems. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

FIG. 2 is a signaling flowchart of Embodiment 1 of a resource scheduling method provided by the present application. The embodiment relates to that the terminal device sends the application state information to the network side device by carrying the application state information in the first user plane data, and does not need to apply the application state information to the RRC layer from the application layer to the RRC layer, thereby solving the application state information from the application. Layer to RRC layer cross-layer delivery problems. As shown in FIG. 2, the method includes the following steps:

S101: The terminal device sends the first user plane data to the network side device, where the first user plane data carries the application state information of the terminal device, and the application state information is used to represent the running state of the application of the terminal.

For example, the terminal device may send the first user plane data carrying the application state information of the application to the network side device in combination with the running state of the application of the terminal device. Optionally, the application related to the application may be a video application, an audio application, an application for browsing a webpage, or another type of application. The type of the application is not limited. The application status information is used to characterize the operational status of the application of the terminal. Taking the video application as an example, the application state information may be used to represent at least one of an enabled state, a suspended state, a playback end state, and a cached data amount and a video playback rate of the video application.

For the foregoing first user plane data, optionally, refer to the inter-layer structure diagram of the terminal device shown in FIG. 3. The APP layer in FIG. 3 is an application (Application, referred to as APP) layer, and the OS is an operating system (OS) of the terminal device. The OS may include a kernel of a terminal device and a Transmission Control Protocol (Transmission Control Protocol). The TCP layer is referred to as the Internet Protocol (IP) layer, and the TCP layer operates on the IP layer. The NAS layer is a Non-Access Stratum (NAS), the RRC layer is a Radio Resource Control (RRC) layer, and the PDCP layer is a Packet Data Convergence Protocol (PDCP). The layer, the RLC layer is a Radio Link Control (RLC) layer, a MAC layer media access control (MAC) layer, and the PHY layer is a physical (Physical, PHY for short) layer.

Optionally, the first user plane data may include an uplink IP packet, where the application state information may be carried in the uplink IP packet. For example, after the application layer generates the application state information, it is delivered to the OS, and is encapsulated into an IP format packet by the TCP layer and the IP layer in the OS, and then the uplink IP packet is sequentially encapsulated by the PCDP layer, the RLC layer, and the MAC layer. A data packet of the MAC layer is obtained, and then the data packet of the MAC layer is processed by the encoding, modulation, and the like of the PHY layer, and then sent to the network side device through the air interface. Thereby, the transmission path of the first user plane data does not pass through the RRC layer. See the schematic diagram of the inter-data layer transfer shown in Figure 3. For the inter-layer structure of the network side device in FIG. 3, the inter-layer structure of the network side device corresponding to the inter-layer structure of the terminal device includes a PHY layer, a MAC layer, an RLC layer, a PDCP layer, an RRC layer, and an IP layer.

It can be seen from the above description that the first user plane data can be reported to the network side device without going through the RRC layer.

Returning to FIG. 2, step S102: the network side device receives the first user plane data from the terminal device.

S103: The network side device schedules time-frequency resources for the terminal device according to the application state information.

S104: The terminal device acquires, from the network side device, the time-frequency resource that the network side device schedules for the terminal device according to the application state information.

For example, as shown in FIG. 3, after the first user plane data reaches the PHY layer of the network side device, the depth detection by the network side device is performed by decapsulation of the PHY layer, the MAC layer, the RLC layer, and the PDCP layer (Deep Packet Inspection). The function of the first user plane is to detect the data carrying the application state information, and then the network side device schedules the appropriate time-frequency resource for the terminal device through the scheduler of the MAC layer. Therefore, after the network side device receives the first user plane data sent by the terminal device, the network side device may parse the first user plane data to obtain application state information in the first user plane data. Since different terminals send the first user plane data carrying different application state information to the network side device, the network side device can combine different application information of the terminal device to schedule different time-frequency resources for different terminal devices. Differentiated scheduling of resources can be implemented, thereby enhancing the timeliness of air interface transmission between the terminal device and the network side device, and improving the application experience of the user.

In addition, since the application state information of the terminal device does not need to be transmitted across the RRC layer, the transmission efficiency when reporting to the network side device is high, thereby improving the resource scheduling efficiency of the network side device; at the same time, the terminal operating system or the terminal device is not required. The baseband chip in the network side device develops a transmission channel or a transmission interface version from the operating system to the RRC layer, which reduces the development cost of the terminal device.

The resource scheduling method provided by the present application, the terminal device sends the application state information of the terminal device to the network side device by using the first user plane data, and the network side device obtains the application state of the terminal device by parsing the first user plane data. The information is used to schedule the appropriate time-frequency resources for the terminal device according to the application state information, thereby enhancing the time-effectiveness of air interface transmission between the terminal device and the network-side device, and improving the application experience of the user. The application status information of the terminal device does not need to be transmitted across the RRC layer when it is transmitted from the application layer to the physical layer. Therefore, the problem that the application state information is difficult to be transmitted across layers in the prior art is solved, and the resource scheduling efficiency of the network side device is improved. The baseband chip in the terminal operating system or the terminal device and the network side device is also not required to develop a transmission channel or a transmission interface version from the operating system to the RRC layer, which reduces the development cost of the terminal device.

As can be seen from the description of the first embodiment, the first user plane data may include an uplink IP packet. Optionally, the uplink IP packet may be in the format of a traditional IP packet, or may be in the format of a new IP packet. That is, the application state information of the terminal device is generated by the application layer, encapsulated into an uplink IP packet by the IP layer in the OS system, and then transmitted to the PDCP layer, the RLC layer, the MAC layer, and the PHY layer to form the first user plane data. , sent to the network side device. The following describes two possible implementations of delivering an application state through the uplink IP packet.

The first possible implementation:

In this embodiment, the uplink IP packet may be in the format of a traditional IP packet, and the present application uses the reserved bits of the Type of Service (TOS) domain in the packet header of the uplink IP packet to carry Application status information of the terminal device.

Optionally, the application state information of the terminal device may be carried by a reserved bit in the TOS domain, or the application state information of the terminal device may be carried by two reserved bits in the TOS domain.

When the application state information of the terminal device is carried through a reserved bit in the TOS domain, different bit values of the reserved bit represent different application state information of the terminal device. For example, taking the video APP as an example, the video buffer amount is one type of information in the application state information of the terminal device. The video buffer level of the terminal device can be characterized as 1 by setting the value of a reserved bit of the TOS field to 1, or the video of the terminal device can be characterized by setting the value of a reserved bit of the TOS field to 0. The buffer level is 2. Different video buffer levels correspond to different video buffers. Therefore, based on the value of the reserved bit in the TOS domain, the network side device can learn the application state information of the terminal device.

Optionally, when the application state information of the terminal device is carried by two reserved bits in the TOS domain, similarly, different bit values of the two reserved bits represent different application state information of the terminal device, for example, by video. For example, the APP can characterize the video buffer level of the terminal device by 1 by setting the value of two reserved bits of the TOS field to 00, or by setting the value of two reserved bits of the TOS field to 01. To characterize the video buffer level of the terminal device is 2; or, the video buffer level of the terminal device can be characterized by setting the value of two reserved bits of the TOS field to 10; or, by The value of the two reserved bits is set to 11 to characterize the video buffer level of the terminal device to be 4.

For the uplink IP packet in the possible implementation manner, the two reserved bits in the TOS domain of the foregoing IP packet carry the application state information as an example. For the format of the uplink IP packet, refer to FIG. 4 . The TOS field is 8 bits and there are two reserved bits. For the meanings of other fields in the format of the uplink IP packet, refer to the description of the prior art, and details are not described herein again.

The second possible implementation:

In this embodiment, the uplink IP packet is in the format of a new IP packet, and the uplink IP packet can carry not only the application state information of the terminal device but also the first identifier, the first identifier. It is used to indicate the type of the application corresponding to the above application state information. For example, the first identifier is a 4-bit identifier. For the video APP, the terminal device can identify the current uplink IP packet to the network side device by setting the first identifier in the uplink IP packet to 1111. The application state information carried in the information is the application state information of the video service. Optionally, the terminal device may set, by using the first identifier in the uplink IP packet, the application status information carried in the current uplink IP packet to the network side device as the application state information of the web browsing service. Certainly, the present application does not limit the number of bits of the first identifier, and also defines how the first identifier identifies the type of the application corresponding to the application state information.

Further, it should be noted that, when the uplink IP packet is in the format of a new IP packet, the format of the new IP packet is not limited, as long as it carries the application status information, or It can carry the above application state information and the first identifier. Optionally, refer to the format of the new IP packet shown in FIG. 5, where the video APP is used as an example, and the new IP packet format includes a 4-bit first identifier and a 4-bit playback status indication. , 8-bit video buffer amount indication and 8-bit video playback rate indication. The play status, the video buffer amount, and the video play rate are all application status information of the video APP.

Optionally, the uplink IP packet may further include a second identifier, where the uplink IP packet is in the foregoing one of the possible implementation manners, where the second identifier is used to indicate that the uplink IP packet is A packet carrying application status information. After receiving the uplink IP packet, the network side device first identifies the uplink IP packet as the packet carrying the application state information by using the second identifier, and the network side device further parses the uplink IP packet to obtain the uplink IP packet. The application status information of the terminal device avoids the blind resolution of the network side device and reduces the processing overhead of the network side device.

FIG. 6 is a signaling flowchart of Embodiment 2 of a resource scheduling method provided by the present application. The network side device of the present embodiment informs the terminal device of the resource allocation coordination capability between the terminal device and the network side device, so that the terminal device sends the first user plane data to the network side device in combination with the resource allocation cooperation capability. The specific process. As shown in FIG. 6, before the above S101, the method includes the following steps:

S201: The network side device sends the second user plane data to the terminal device, where the second user plane data carries the resource allocation coordination capability between the terminal device and the network side device.

S202: The terminal device receives the second user plane data from the network side device.

The above S101 can be implemented by the following steps of S203:

S203: The terminal device sends the first user plane data to the network side device according to the resource allocation collaboration capability between the network side device and the network side device.

The process of S201 to S203 described above is specifically described as follows:

In some scenarios, the terminal device sends the first user plane data to the network side device, but the network side device cannot perform resource scheduling for the terminal device because the resource allocation coordination capability between the terminal device and the network side device is relatively low. The network side device may discard the first user plane data, thereby causing the first user plane data to be sent to be invalid. In this embodiment, the network side device sends the second user plane data to the terminal device, where the second user plane data carries the network side device to the terminal device and the network side device. The ability to allocate resources between resources.

Optionally, the network side device may have different resource allocation coordination capabilities in different scenarios, where the resource allocation collaboration capability may include: a first resource allocation collaboration capability, a second resource allocation collaboration capability, or a third resource allocation. Synergy. The first resource allocation coordination capability refers to that the network side device can perform differentiated scheduling of resources on the terminal device regardless of application state information. The foregoing second resource allocation cooperation capability refers to that the network side device implements differentiated scheduling of resources on the terminal device only after the application state information of the terminal device meets certain conditions. The third resource allocation cooperation capability refers to that the network side device can perform differentiated scheduling of resources on the terminal device only in combination with the application state information of the terminal device in an idle state. Certainly, the network side device may also have other types of resource allocation coordination capabilities. The type of the resource allocation coordination capability between the network side device and the network side device is not limited.

After the terminal device receives the second user plane data sent by the network side device, the terminal device may parse the second user plane data to obtain the resource allocation coordination capability between the network side device and the network side device. Based on the resource allocation coordination capability, the terminal device sends the first user plane data to the network side device. The types of resource allocation coordination capabilities described above include the first resource allocation coordination capability, the second resource allocation coordination capability, and the third resource allocation coordination capability as an example:

If the network side device allocates the cooperation capability of the resource allocation between the terminal device and the network side device to the first resource, the terminal device may send the first user plane data to the network side device at any time;

If the network side device allocates the collaboration capability of the resource allocation between the terminal device and the network device to the second resource, the terminal device needs to determine whether the application state information meets the preset sending condition, and if yes, the terminal device Sending the first user plane data to the network side device, if not, the terminal device temporarily does not send the first user plane data to the network side device;

If the network side device allocates the collaboration capability between the terminal device and the network side device to the third resource, and the network device also informs the terminal device of the current busy state, the terminal device learns the network side device. When the terminal device is in a busy state, the terminal device temporarily does not send the first user plane data to the network side device; if the terminal device learns that the network side device is currently in the idle state, the terminal device may send the first user plane data to the network side device.

It should be noted that the foregoing second user plane data is similar to the first user plane data, and the transmission path when the network side device and the terminal device perform data transmission does not pass through the RRC layer.

Optionally, the second user plane data may include a downlink IP packet, and the resource allocation coordination capability between the network device and the network device may be carried in the downlink IP packet. For example, the resource allocation coordination capability between the network device and the network device is encapsulated into a downlink IP packet, and then the downlink IP packet passes through the PCDP layer, the RLC layer, the MAC layer, and the PHY layer. Encapsulation, obtaining the second user plane data, and transmitting to the terminal device through the air interface.

Optionally, the downlink IP packet may be in the format of a traditional IP packet. The application uses the reserved bit of the TOS field in the packet header of the downlink IP packet to carry the network side device to the terminal device and the network side device. The resource allocation coordination capability between the resources is that the reserved bits of the TOS domain are resource allocation coordination capability indication bits, and the values indicating the different bits correspond to different resource allocation coordination capabilities. Optionally, the network side device may carry the resource allocation coordination capability between the terminal device and the network side device by using a reserved bit in the TOS domain, or may carry the network side device by using two reserved bits in the TOS domain. A resource allocation synergy between the terminal device and the network side device.

When a reserved bit of the TOS domain carries the resource allocation coordination capability between the terminal device and the network side device by the network side device, different bit values of the reserved bit represent different resource allocation cooperation capabilities. For example, when the value of the reserved bit is 1, it indicates that the resource allocation cooperation capability between the network device and the network device is the first resource allocation cooperation capability. When the value of the reserved bit is 0, the network side device is indicated. The resource allocation synergy capability between the terminal device and the network side device is a third resource allocation coordination capability.

When the network side device carries the resource allocation coordination capability between the terminal device and the network side device by the two reserved bits in the TOS domain, the different bit values of the two reserved bits represent different resource allocation coordination. ability. For example, when the value of the reserved bit is 11, the network side device indicates that the resource allocation cooperation capability between the terminal device and the network side device is the first resource allocation cooperation capability. When the value of the reserved bit is 01, the network side device is indicated. The resource allocation coordination capability between the terminal device and the network side device is a third resource allocation coordination capability. When the value of the reserved bit is 10, it indicates that the network side device has a resource allocation coordination capability between the terminal device and the network side device. The second resource allocates synergy.

For the format of the format of the downlink IP packet, the format of the downlink IP packet can be as shown in FIG. 7 above. The TOS field is 8 bits, and there are two reserved bits. One or both of the reserved bits are resource allocation coordination capability indication bits. For the meanings of other fields in the format of the downlink IP packet, refer to the description of the prior art, and details are not described herein again.

Optionally, the downlink IP packet may be in the format of a new IP packet. When the downlink IP packet is in the format of a new IP packet, the format of the new IP packet is not limited, as long as it carries the resource allocation coordination capability between the network device and the network device. Just fine.

Optionally, in the foregoing S203, in order to further prevent the terminal device from transmitting the invalid first user plane data, refer to the third embodiment shown in FIG.

S301: The terminal device determines whether the application of the terminal device meets a preset trigger condition.

The preset triggering condition includes: the application of the terminal device is enabled, the running state of the application of the terminal device changes, the amount of cached data of the application of the terminal device is lower than the first preset threshold, and the cached data of the application of the terminal device The amount is higher than any of the second predetermined thresholds.

Optionally, for the trigger condition, the application of the terminal device is enabled, and the application may be turned on for the terminal device triggered by the user's operation or automatically turned on at a predetermined time. For example, when the user clicks on the video app, the application state information of the video APP is in a Prepare state, and the terminal device carries the application state information in the first user plane data, and combines the network side device with the terminal device and the network. The resource allocation coordination capability between the side devices determines whether the first user plane data is sent to the network side device.

The running status of the application of the terminal device is changed, and the video APP is taken as an example. The running state may include a start, a play, a play, a pause, an end, and the like.

The amount of cached data of the application of the terminal device is the amount of data cached locally by the terminal device.

When the application of the terminal device meets the preset triggering condition, the terminal device performs the following step S302; when the application of the terminal device does not meet the preset triggering condition, the terminal device temporarily does not send the first user plane data, that is, The steps of S302 described below are not performed.

S302: When the application of the terminal device meets the preset triggering condition, the terminal device sends the first user to the network side device according to the resource allocation collaboration capability between the network side device and the network side device. Face data.

In combination with the processes of the foregoing S301 and S302, the terminal device may determine whether to send the first to the network side device by combining the information about the application of the terminal device and the resource allocation cooperation capability between the network device and the network device. The user plane data, so that the terminal device sends the first user plane data to the network side device more accurately, improves the air interface transmission accuracy of the terminal device and the network side device, and saves the error transmission overhead of the terminal device.

The resource scheduling method provided by the present application, the network side device sends the second user plane data carrying the resource allocation coordination capability between the terminal device and the network side device to the terminal device, so that the terminal device can combine the resource allocation coordination The capability determines whether the first user plane data is sent to the network side device, avoids invalid transmission of the terminal device, and saves the erroneous transmission overhead of the terminal device. In addition, the terminal device refers to the network side device to the terminal device and the network side device. On the basis of the resource allocation coordination capability, the terminal device further determines whether to send the first user plane data to the network side device by using the two triggering conditions, so that the terminal device sends the network device to the network side device. The first user plane data is more accurate, which improves the air interface transmission accuracy of the terminal device and the network side device, and saves the error transmission overhead of the terminal device.

In order to introduce the present application more clearly, FIG. 9 provides another embodiment of the present application. The following is an example in which the network side device is a base station and the application is a video APP. Referring to the fourth embodiment shown in FIG. Including the following steps:

S401: The base station sends the second user plane data to the terminal device by using a main processing and transmission (MPT) main control board.

The second user plane data carries the resource allocation coordination capability between the terminal device and the base station, and the second user plane data includes the downlink IP packet.

S402: The terminal device receives the second user plane data from the base station, and parses out the resource allocation coordination capability between the base station and the base station and the base station.

S403: The terminal device determines whether the application of the terminal device meets a preset trigger condition.

The preset triggering condition includes: the application of the terminal device is enabled, the running state of the application of the terminal device changes, the amount of cached data of the application of the terminal device is lower than the first preset threshold, and the cached data of the application of the terminal device The amount is higher than any of the second predetermined thresholds.

S404: When the application of the terminal device meets the preset triggering condition, the terminal device sends the first user plane data to the MPT main control board of the base station according to the resource allocation coordination capability between the base station and the base station, where the first user The face data includes uplink IP packets.

S405: After the PDTP encapsulation of the first user plane data is decapsulated by the MPT main control board of the base station, the second identifier of the uplink IP packet in the first user plane data is detected by the packet, and the first user plane data is determined. The uplink IP packet is a packet carrying the application state information, and the application state information in the uplink IP packet is further parsed.

S406: The MPT main control board of the base station transmits the acquired application state information to the baseband board resource scheduler.

S407: The baseband card resource scheduler of the base station performs differentiated scheduling of resources on the terminal device according to the application state information.

Optionally, if the application state information of the terminal device indicates that the base station needs to speed up data transmission with the terminal device, the baseband card resource scheduler increases the scheduling weight of the user, and schedules more time-frequency resources for the terminal device. On the contrary, the scheduling weight of the user is reduced. In this manner, the baseband card resource scheduler of the base station can obtain a higher scheduling gain, thereby increasing the timeliness of air interface transmission between the base station and different terminal devices.

For the specific process of the foregoing S401 to S407, refer to the embodiment shown in FIG. 1 to FIG. 8 above, and the implementation principle and the beneficial effects are similar, and details are not described herein again.

FIG. 10 is a schematic structural diagram of Embodiment 1 of a terminal device provided by the present application. As shown in FIG. 10, the terminal device includes: a sending module 11 and an obtaining module 12.

The sending module 11 is configured to send, to the network side device, first user plane data, where the first user plane data carries application state information of the terminal device; and the application state information is used to perform operation of the terminal application. status;

The obtaining module 12 is configured to acquire, from the network side device, a time-frequency resource that the network side device schedules for the terminal device according to the application state information.

Optionally, the sending module 11 may correspond to a transmitter in the terminal device, and the acquiring module 12 may correspond to a receiver or a processing chip in the terminal device. The processing chip may be a radio frequency processing chip or a baseband processing chip.

Optionally, the first user plane data includes an uplink network interconnection protocol IP packet.

Optionally, the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information.

Optionally, the uplink IP packet further includes a first identifier, where the first identifier is used to indicate a type of the application corresponding to the application state information.

Further, the acquiring module 12 is further configured to: before the sending module 11 sends the first user plane data to the network side device, receive second user plane data, the second user plane data from the network side device. Carrying a resource allocation synergy capability between the terminal device and the network side device by the network side device;

The sending module 11 is specifically configured to send the first user plane data to the network side device according to the resource allocation cooperation capability between the terminal device and the network side device.

Optionally, the second user plane data includes a downlink IP packet.

Optionally, the reserved bit in the TOS field in the packet header of the downlink IP packet carries the resource allocation coordination capability between the terminal device and the network side device.

Further, the sending module 11 is specifically configured to: when the application of the terminal device meets a preset triggering condition, send the first user plane to the network side device according to the resource cooperation capability of the network side device data;

The preset triggering condition includes: the application of the terminal device is enabled, the running state of the application of the terminal device changes, and the amount of cached data of the application of the terminal device is lower than a first preset threshold, The amount of cached data of the application of the terminal device is higher than any one of the second preset thresholds.

Optionally, the uplink IP packet further includes a second identifier.

The second identifier is used to indicate that the uplink IP packet is a packet carrying the application state information.

The terminal device provided by the present application may also perform the operations of the terminal device in the foregoing method embodiment of FIG. 2 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.

FIG. 11 is a schematic structural diagram of Embodiment 1 of a network side device provided by the present application. As shown in FIG. 11, the network side device includes: a receiving module 21 and a processing module 22. The processing chip may be a radio frequency processing chip or a baseband processing chip.

The receiving module 21 is configured to receive first user plane data from the terminal device, where the first user plane data carries application state information of the terminal device, and the application state information is used to perform operation of the terminal application. status;

The processing module 22 is configured to schedule time-frequency resources for the terminal device according to the application state information.

Optionally, the receiving module 21 may correspond to a receiver in the terminal device, where the acquiring module may correspond to a processing chip or the like in the terminal device.

Optionally, the first user plane data includes an uplink network interconnection protocol IP packet.

Optionally, the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information.

Optionally, the uplink IP packet further includes a first identifier.

The first identifier is used to indicate a type of an application corresponding to the application state information.

For further reference, refer to the structural schematic diagram of Embodiment 2 of the network side device shown in FIG. On the basis of the above-mentioned embodiment shown in FIG. 11, the network side device may further include: a sending module 23;

The sending module 23 is configured to send second user plane data to the terminal device before the receiving module 21 receives the first user plane data from the terminal device, where the second user plane data carries the network side The device allocates a synergistic capability to resources between the terminal device and the network side device.

Optionally, the second user plane data includes a downlink IP packet.

Optionally, the reserved bit in the TOS field in the packet header of the downlink IP packet carries the resource allocation coordination capability between the terminal device and the network side device.

Optionally, the uplink IP packet further includes a second identifier.

The second identifier is used to indicate that the uplink IP packet is a packet carrying the application state information.

The network side device provided by the present application may also perform the operations of the network side device in the foregoing method embodiment of FIG. 2 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.

FIG. 13 is a schematic structural diagram of Embodiment 2 of a terminal device provided by the present application. As shown in FIG. 13, the terminal device may include a memory 31, a processor 32, at least one communication bus 33, and a transmitter 34. The communication bus 33 is used to implement a communication connection between components. The memory 31 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment. In this embodiment, the transmitter 34 may be a radio frequency processing module or a baseband processing module in the terminal device. Optionally, the terminal device may further include a receiver 35, where the receiver 35 may be a radio frequency processing module or a baseband processing module in the terminal device. The transmitter 34 and the receiver 35 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 34 and the receiver 35 may be coupled to the processor 32.

In this embodiment, the sender 34 is configured to send the first user plane data to the network side device, where the first user plane data carries application state information of the terminal device; the application state information is used to represent the The operating state of the application of the terminal device;

The processor 32 is configured to acquire, from the network side device, a time-frequency resource that the network side device schedules for the terminal device according to the application state information.

Optionally, the first user plane data includes an uplink network interconnection protocol IP packet.

Optionally, the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information.

Optionally, the uplink IP packet further includes a first identifier.

The first identifier is used to indicate a type of an application corresponding to the application state information.

Optionally, the receiver 35 is configured to receive second user plane data from the network side device before the sender 34 sends the first user plane data to the network side device, where the second user plane data carries The network side device allocates a synergistic capability to resources between the terminal device and the network side device;

The sender 34 is configured to send the first user plane data to the network side device according to the resource allocation cooperation capability between the terminal device and the network side device by the network side device.

Optionally, the second user plane data includes a downlink IP packet.

Optionally, the reserved bit in the TOS field in the packet header of the downlink IP packet carries the resource allocation coordination capability between the terminal device and the network side device.

Further, the transmitter 34 is configured to send the first user plane to the network side device according to the resource cooperation capability of the network side device when the application of the terminal device meets a preset trigger condition. data;

The preset triggering condition includes: the application of the terminal device is enabled, the running state of the application of the terminal device changes, and the amount of cached data of the application of the terminal device is lower than a first preset threshold, The amount of cached data of the application of the terminal device is higher than any one of the second preset thresholds.

Optionally, the uplink IP packet further includes a second identifier, where the second identifier is used to indicate that the uplink IP packet is a packet that carries the application state information.

The terminal device provided by the present application may also perform the operations of the terminal device in the foregoing method embodiment of FIG. 2 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.

FIG. 14 is a schematic structural diagram of Embodiment 3 of a network side device provided by the present application. As shown in FIG. 14, the terminal device may include a memory 41, a processor 42, at least one communication bus 43, and a receiver 44. Communication bus 43 is used to implement a communication connection between the components. The memory 41 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment. In this embodiment, the receiver 44 may be a radio frequency processing module or a baseband processing module in the terminal device. Optionally, the terminal device may further include a transmitter 45, where the transmitter 45 may be a radio frequency processing module or a baseband processing module in the terminal device. The transmitter 45 and the receiver 44 described above may be provided separately, and may also be integrated to form a transceiver, and both the transmitter 45 and the receiver 44 may be coupled to the processor 42.

In this embodiment, the receiver 44 is configured to receive the first user plane data from the terminal device, where the first user plane data carries application state information of the terminal device; the application state information is used to represent the The operating state of the application of the terminal;

The processor 42 is configured to schedule time-frequency resources for the terminal device according to the application state information.

Optionally, the first user plane data includes an uplink network interconnection protocol IP packet.

Optionally, the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information.

Optionally, the uplink IP packet further includes a first identifier, where the first identifier is used to indicate a type of the application corresponding to the application state information.

Further, the transmitter 45 is configured to send second user plane data to the terminal device before the receiver 44 receives the first user plane data from the terminal device, where the second user plane data carries The network side device allocates a synergistic capability to resources between the terminal device and the network side device.

Optionally, the second user plane data includes a downlink IP packet.

Optionally, the reserved bit in the TOS field in the packet header of the downlink IP packet carries the resource allocation coordination capability between the terminal device and the network side device.

Optionally, the uplink IP packet further includes a second identifier, where the second identifier is used to indicate that the uplink IP packet is a packet that carries the application state information.

The network side device provided by the present application may also perform the operations of the network side device in the foregoing method embodiment of FIG. 2 to FIG. 9 , and the implementation principle and technical effects thereof are similar, and details are not described herein again.

Optionally, the embodiment of the present application further provides a computer program product. FIG. 15 is a schematic structural diagram 1 of a computer program product according to an embodiment of the present application. As shown in FIG. 15, computer program product 1100 can include program code 1101.

The program code 1101 may be a program code corresponding to the resource scheduling method executed by the terminal device described in any of FIG. 2 to FIG. 9 in the embodiment of the present application.

The program code 1101 in the computer program product 1100 can be executed, for example, by the processor 32 of the terminal device shown in Fig. 13 described above.

Optionally, the embodiment of the present application further provides a storage medium. FIG. 16 is a schematic structural diagram 1 of a storage medium according to an embodiment of the present disclosure. As shown in FIG. 16, storage medium 1200 can be used to store computer program product 1201. Computer program product 1201 can include program code 1202.

The program code 1202 may be a program code corresponding to the resource scheduling method executed by the terminal device described in any of FIG. 2 to FIG. 9 in the embodiment of the present application.

The storage medium 1200 may be the memory 31 in the terminal device shown in FIG. 13 described above, or may be an external memory connected to the terminal device shown in FIG. 13 described above. The program code 1202 in the computer program product 1201 can be executed, for example, by the processor 32 in the terminal device shown in FIG. 13 described above.

The terminal device, the computer program product, and the storage medium provided by the embodiments of the present application may perform the resource scheduling method performed by the terminal device according to any one of the foregoing FIG. 2 to FIG. 9, and the specific implementation process and beneficial effects thereof may be referred to the above. The embodiment is not described here.

Optionally, the embodiment of the present application further provides a computer program product. FIG. 17 is a schematic structural diagram 2 of a computer program product according to an embodiment of the present application. As shown in FIG. 17, computer program product 1400 can include program code 1401.

The program code 1401 may be a program code corresponding to the resource scheduling method executed by the network side device described in any of FIG. 2 to FIG. 9 in the embodiment of the present application.

The program code 1401 in the computer program product 1400 can be executed, for example, by the processor 42 of the network side device shown in FIG. 14 described above.

Optionally, the embodiment of the present application further provides a storage medium. FIG. 18 is a schematic structural diagram 2 of a storage medium according to an embodiment of the present application. As shown in FIG. 18, storage medium 1500 can be used to store computer program product 1501. The computer program product 1501 can include program code 1502.

The program code 1502 may be a program code corresponding to the resource scheduling method executed by the network side device described in any of FIG. 2 to FIG. 9 in the embodiment of the present application.

The storage medium 1500 may be the memory 41 in the network side device shown in FIG. 14 described above, or may be an external memory connected to the network side device shown in FIG. 14 described above. The program code 1502 in the computer program product 1501 can be executed, for example, by the processor 42 in the network side device shown in FIG. 14 described above.

The network side device, the computer program product, and the storage medium provided in the embodiments of the present application may perform the resource scheduling method executed by the network side device described in any one of the foregoing FIG. 2 to FIG. 9 , and the specific implementation process and beneficial effects thereof. For details, refer to the foregoing embodiments, and details are not described herein again.

The steps of the method or algorithm described in connection with the disclosure of the present application may be implemented in a hardware manner, or may be implemented by a processor executing a software instruction, or may be implemented by a computer program product. The software instructions may be comprised of corresponding software modules that may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage well known in the art. In the medium. An exemplary storage medium is coupled to the processor to enable the processor to read information from, and write information to, the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in the user equipment. Of course, the processor and the storage medium may also reside as discrete components in the user equipment.

In one or more examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. Computer readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A storage medium may be any available media that can be accessed by a general purpose or special purpose computer.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners without departing from the scope of the present application. For example, the embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined. Or it can be integrated into another system, or some features can be ignored or not executed. The units described as separate components may or may not be physically separated, and the components displayed as the unit may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. . Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

Claims (30)

A resource scheduling method, comprising: The terminal device sends the first user plane data to the network side device, where the first user plane data carries the application state information of the terminal device; the application state information is used to represent the running state of the application of the terminal device; The terminal device acquires, from the network side device, the time-frequency resource that the network-side device schedules for the terminal device according to the application state information. The method according to claim 1, wherein the first user plane data comprises an uplink network interconnection protocol IP packet. The method according to claim 2, wherein the reserved bits in the service type TOS field in the header of the uplink IP packet carry the application state information. The method according to claim 2, wherein the uplink IP packet further includes a first identifier; The first identifier is used to indicate a type of an application corresponding to the application state information. The method according to any one of claims 1-4, wherein before the sending, by the terminal device, the first user plane data to the network side device, the method further includes: The terminal device receives the second user plane data from the network side device, and the second user plane data carries the resource allocation coordination capability between the terminal device and the network side device by the network side device; Sending, by the terminal device, the first user plane data to the network side device, including: The terminal device sends the first user plane data to the network side device according to the resource allocation coordination capability between the terminal device and the network side device. The method according to claim 5, wherein the second user plane data comprises a downlink IP packet. The method according to claim 6, wherein the reserved bit in the TOS field in the packet header of the downlink IP packet carries the network side device between the terminal device and the network side device Resource allocation synergy. The method according to any one of claims 2-7, wherein the uplink IP packet further includes a second identifier; The second identifier is used to indicate that the uplink IP packet is a packet carrying the application state information. A resource scheduling method, comprising: The network side device receives the first user plane data from the terminal device, where the first user plane data carries the application state information of the terminal device; the application state information is used to represent the running state of the application of the terminal device; The network side device schedules time-frequency resources for the terminal device according to the application state information. The method according to claim 9, wherein the first user plane data comprises an uplink network interconnection protocol IP packet. The method according to claim 10, wherein the reserved bits in the service type TOS field in the header of the uplink IP packet carry the application state information. The method according to claim 10, wherein the uplink IP packet further includes a first identifier; The first identifier is used to indicate a type of an application corresponding to the application state information. The method according to any one of claims 9 to 12, wherein before the network side device receives the first user plane data from the terminal device, the method further includes: The network side device sends the second user plane data to the terminal device, where the second user plane data carries the resource allocation coordination capability between the terminal device and the network side device. The method according to claim 13, wherein the second user plane data comprises a downlink IP packet. The method according to claim 14, wherein the reserved bit in the TOS field in the header of the downlink IP packet carries the network side device between the terminal device and the network side device Resource allocation synergy. A terminal device, comprising: a sending module, configured to send the first user plane data to the network side device, where the first user plane data carries application state information of the terminal device; the application state information is used to represent an operation of the application of the terminal device status; And an obtaining module, configured to acquire, from the network side device, a time-frequency resource that is sent by the network side device to the terminal device according to the application state information. The terminal device according to claim 16, wherein the first user plane data comprises an uplink network interconnection protocol IP packet. The terminal device according to claim 17, wherein the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information. The terminal device according to claim 17, wherein the uplink IP packet further includes a first identifier; The first identifier is used to indicate a type of an application corresponding to the application state information. The terminal device according to any one of claims 16 to 19, wherein the acquiring module is further configured to: before the sending module sends the first user plane data to the network side device, from the network side device Receiving the second user plane data, where the second user plane data carries the resource allocation coordination capability between the terminal device and the network side device by the network side device; The sending module is configured to send the first user plane data to the network side device according to the resource allocation collaboration capability between the terminal device and the network side device. The terminal device according to claim 20, wherein the second user plane data comprises a downlink IP packet. The terminal device according to claim 21, wherein the reserved bit in the TOS field in the packet header of the downlink IP packet carries the network side device to the terminal device and the network side device Resource allocation synergy between resources. The terminal device according to any one of claims 17 to 22, wherein the uplink IP packet further includes a second identifier; The second identifier is used to indicate that the uplink IP packet is a packet carrying the application state information. A network side device, comprising: a receiving module, configured to receive first user plane data from the terminal device, where the first user plane data carries application state information of the terminal device; and the application state information is used to perform operation of the terminal device status; And a processing module, configured to schedule a time-frequency resource for the terminal device according to the application state information. The network side device according to claim 24, wherein the first user plane data comprises an uplink network interconnection protocol IP packet. The network side device according to claim 25, wherein the reserved bit in the service type TOS field in the packet header of the uplink IP packet carries the application state information. The network side device according to claim 25, wherein the uplink IP packet further includes a first identifier; The first identifier is used to indicate a type of an application corresponding to the application state information. The network side device according to any one of claims 24 to 27, wherein the network side device further comprises: a sending module; The sending module is configured to send second user plane data to the terminal device before the receiving module receives the first user plane data from the terminal device, where the second user plane data carries the network side device pair Resource allocation coordination capability between the terminal device and the network side device. The network side device according to claim 28, wherein the second user plane data comprises a downlink IP packet. The network side device according to claim 29, wherein the reserved bit in the TOS field in the packet header of the downlink IP packet carries the network side device to the terminal device and the network side device The ability to allocate resources between resources.

Images