WO2023160116A1

WO2023160116A1 - Communication method and apparatus

Info

Publication number: WO2023160116A1
Application number: PCT/CN2022/137911
Authority: WO
Inventors: 周汉; 王丹; 魏鑫鹏
Original assignee: 华为技术有限公司
Priority date: 2022-02-28
Filing date: 2022-12-09
Publication date: 2023-08-31
Also published as: CN116723582A

Abstract

Provided in the embodiments of the present application are a communication method and apparatus, which are applied to the field of data packet scheduling and quality of service (QoS) assurance. The method comprises: an application network element determining a scheduling priority corresponding to each type of data block among a plurality of different types of data blocks, wherein data packets in the plurality of different types of data blocks are all mapped into the same QoS flow; and the application network element sending indication information to a policy control network element, wherein the indication information is used for indicating the scheduling priority corresponding to each type of data block, the scheduling priority is used for indicating that the data packets in the different types of data blocks are scheduled, and each data block comprises at least one data packet. An application network element determines and issues a plurality of different scheduling priorities corresponding to the same QoS flow, thereby realizing differentiated scheduling of data packets in different types of data blocks corresponding to the same QoS flow, and improving the user experience.

Description

Communication method and device

This application claims the priority of a Chinese patent application with application number 202210184934.X and application title "Communication Method and Apparatus" filed with the China Patent Office on February 28, 2022, the entire contents of which are incorporated herein by reference.

technical field

The present application relates to the communication field, and more specifically, to a communication method and device.

Background technique

In the fifth generation (5th generation, 5G) system, in order to ensure the end-to-end service quality of the business, a quality of service (quality of service, QoS) flow (flow) is proposed. For a terminal device (user equipment, UE), when the UE has business communication needs, it can establish one or more packet data unit (packet data unit, PDU) sessions with the 5G network, and each PDU session can be established (also It can be called configuration) one or more QoS flows that carry business data flows.

The current agreement stipulates that each QoS flow is expressed by a set of QoS parameters, and the QoS parameters include the 5G QoS identifier (5G QoS identifier, 5QI). The scheduling of data flow is based on QoS flow as the granularity. Therefore, it is impossible to perform differentiated scheduling on the same QoS flow according to the importance of the data flow to the user experience.

Contents of the invention

The embodiment of the present application provides a communication method, by configuring multiple scheduling priorities corresponding to the same QoS flow, in order to realize differentiated scheduling of the same QoS flow.

In the first aspect, a communication method is provided. The method may be executed by an application network element, or may also be executed by a component (such as a chip or a circuit) of the application network element. This is not limited. For the convenience of description, the following uses The execution of the application network element is taken as an example for description.

The method includes: applying a network element to determine the scheduling priority corresponding to each type of data block in multiple different types of data blocks, and the data packets in the multiple different types of data blocks are all mapped to the same quality of service (QoS) flow The application network element sends indication information to the policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, wherein each data block includes at least one data packet.

Based on the above technical solution, the application network element can determine the scheduling priority of different types of data blocks corresponding to the same QoS flow, and notify the policy to control the scheduling priority corresponding to each type of data block of the network element through the instruction information, so that the policy The control network element learns that the same QoS flow has multiple different scheduling priorities, so as to realize differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

It should be noted that the above data packets in multiple different types of data blocks are all mapped to the same quality of service QoS flow, which can be understood as:

Multiple different types of data blocks correspond to the same QoS flow; or, it can be understood as multiple different types of data blocks carried in the same QoS flow; or it can also be understood as each of multiple different types of data blocks The scheduling priorities corresponding to the types of data blocks are used to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

In addition, the above-mentioned application network element sending the instruction information to the policy control network element may be that the application network element directly sends the instruction information to the policy control network element, for example, the application network element uses the communication interface between the application network element and the policy control network element or Send the instruction information to the policy control network element through the service interface; it is also possible that the application network element indirectly sends the instruction information to the policy control network element, for example, the application network element sends the instruction information to the policy control network element through other functional network elements.

With reference to the first aspect, in some implementation manners of the first aspect, the indication information is included in the quality of service QoS requirement, and the QoS requirement is used to configure the parameters of the QoS flow, and the method further includes: the application network element receiving the A response message from the policy control network element, which is used to indicate that the parameter configuration of the QoS flow is completed; the application network element sends downlink data to the user plane network element, and the downlink data includes a data packet and a An indication of the type of data block.

Based on the above technical solution, the application network element can carry the indication information in the QoS requirement, that is, the above-mentioned scheduling priority corresponding to each type of data block in the same QoS flow can be understood as a kind of QoS requirement. The QoS requirement is used to configure the parameters of the QoS flow. After the parameter configuration of the QoS flow is completed, the application network element can be notified by a response message that the parameter configuration of the QoS flow is completed, so that the application network element can start to transmit downlink data. Specifically, in addition to the data packet to be transmitted, the downlink data also includes indication information indicating the type of the data block to which the data packet belongs, so that the network element receiving the data packet can determine the data packet belongs to according to the type of indication information. The type of the data block, and further determine the scheduling priority of the data packet according to the type of the data block to which the data packet belongs, and realize the differentiated scheduling of the data packets of different types of data blocks corresponding to the same quality of service QoS flow.

With reference to the first aspect, in some implementation manners of the first aspect, the method further includes: the application network element sending the identification information of the data block to which the data packet belongs to the user plane network element.

Based on the above technical solution, the application network element can send the identification information of the data block to which the data packet belongs to the user plane network element, so that the user plane network element can know the data block to which the data packet belongs according to the identification information.

With reference to the first aspect, in some implementations of the first aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

In this application, different types of data blocks can be divided in multiple forms, which improves the flexibility of the solution.

In the second aspect, a communication method is provided, and the method may be executed by a policy control network element, or may also be executed by a component (such as a chip or a circuit) of the policy control network element, which is not limited, and for ease of description, In the following, the execution of the network element controlled by the policy is taken as an example for description.

The communication method includes: the policy control network element receives indication information from the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the multiple data blocks of different types The data packets in the data block are all mapped to the same QoS flow; the policy control network element sends the scheduling priority corresponding to each type of data block to the session management network element.

Based on the above technical solution, the application network element notifies the policy control network element of the scheduling priority corresponding to each type of data block through the indication information, so that the policy control network element knows that the same QoS flow has multiple different scheduling priorities, in order to achieve Differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

With reference to the second aspect, in some implementations of the second aspect, the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.

Based on the above technical solution, the policy control network element can send the scheduling priority corresponding to each type of data block to the session management network element through the PCC rule, and the PCC rule includes information indicating the scheduling priority compared with other QoS flows , so as to determine the scheduling priority among QoS flows.

With reference to the second aspect, in some implementations of the second aspect, the method further includes: the policy control network element receiving a response message from the session management network element, where the response message is used to indicate that the parameter configuration of the QoS flow is completed; The policy control network element sends the response message to the application network element.

Based on the above technical solution, after the parameter configuration of the QoS flow is completed, the application network element can be notified of the completion of the parameter configuration of the QoS flow through a response message, so that the subsequent application network element can perform downlink data transmission.

With reference to the second aspect, in some implementations of the second aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

In the third aspect, a communication method is provided, and the method may be executed by a session management network element, or may also be executed by a component (such as a chip or a circuit) of the session management network element, which is not limited, and for the convenience of description, In the following, the implementation by the session management network element is taken as an example for description.

The communication method includes: the session management network element receives the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all Mapped to the same quality of service QoS flow; the session management network element sends the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate the user plane network element The scheduling priority corresponding to the received data packet is encapsulated in the data packet, wherein each data block includes at least one data packet.

Based on the above technical solution, the session management network element can receive the scheduling priority corresponding to each type of data block from the policy control network element, and send the scheduling priority corresponding to each type of data block to the user plane network element, so that the user The plane network element learns that the same QoS flow has multiple different scheduling priorities, so as to realize differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

In conjunction with the third aspect, in some implementations of the third aspect, the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.

In conjunction with the third aspect, in some implementations of the third aspect, the method further includes: the session management network element configures the parameters of the QoS flow according to the PCC rule; the session management network element sends a response message to the policy control network element , the response message is used to indicate that the parameter configuration of the QoS flow is completed.

Based on the above technical solution, after the parameter configuration of the QoS flow is completed, the policy control network element can be notified through the response message that the parameter configuration of the QoS flow is completed, so that the subsequent application network element can perform downlink data transmission.

With reference to the third aspect, in some implementations of the third aspect, the method further includes: the session management network element assigns a scheduling priority to each type of data block among the plurality of different types of data blocks A priority identifier, where the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block; the session management network element sends the user plane network element the scheduling priority identifier corresponding to each type of data block and A corresponding relationship, wherein the corresponding relationship includes a corresponding relationship between the scheduling priorities of the multiple different types of data blocks and multiple identifiers of the scheduling priorities.

Based on the above technical solution, the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier. In order for the user plane network element to know the scheduling priority corresponding to each type of data block, each type of data block can be The scheduling priority identifier and corresponding relationship corresponding to the data block are sent to the user plane network element, so that the user plane network element determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the session management network element sending multiple scheduling priorities of different types of data blocks and multiple scheduling priorities to the access network device Correspondence between level identifiers.

Based on the above technical solution, the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier. In order for the access network device to know the scheduling priority corresponding to each type of data block, multiple different types of The scheduling priority of the data block and the corresponding relationship between multiple scheduling priority identifiers are sent to the access network device, so that the access network device determines the scheduling priority of different types of data blocks according to the scheduling priority identifier and the corresponding relationship .

With reference to the third aspect, in some implementations of the third aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

With reference to the third aspect, in some implementation manners of the third aspect, the method further includes: the session management network element sending encapsulation information to the user plane network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information In the data packet, the identification information is used to identify the data block to which the data packet belongs.

In the fourth aspect, a communication method is provided, and the method may be executed by a user plane network element, or may also be executed by a component (such as a chip or a circuit) of the user plane network element, which is not limited, and for ease of description, The following takes the implementation by the user plane network element as an example for description.

The communication method includes: a user plane network element receives downlink data from an application network element, the downlink data includes a plurality of different types of data blocks, and each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority , the data packets in the plurality of data blocks of different types are all mapped to the same quality of service QoS flow, and each data block includes at least one data packet; the user plane network element according to the type corresponding to each data packet and each A scheduling priority corresponding to a data block of the type determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet is encapsulated with information indicating the scheduling priority of the data packet .

Based on the above technical solution, the user plane network element can encapsulate the indication information of the scheduling priority of different data packets in the data packet, so that the access network equipment can know the scheduling priority of different data packets in the same QoS flow, in order to achieve the same Differential scheduling of data packets of different types of data blocks corresponding to a QoS flow.

With reference to the fourth aspect, in some implementations of the fourth aspect, the method further includes: the user plane network element receives scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, the The encapsulation indication information is used to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.

Based on the above technical solution, the session management network element can send the scheduling priority corresponding to each type of data block to the user plane network element, so that the user plane network element knows that the same QoS flow has multiple different scheduling priorities.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority, and the method further includes: receiving, by the user plane network element from The scheduling priority identifier and corresponding relationship of the session management network element, the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block, and the corresponding relationship includes the scheduling priorities of the multiple different types of data blocks Corresponding relationship with multiple scheduling priority identifiers.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the method further includes: receiving, by the user plane network element, identification information of a data block to which the data packet belongs from the application network element.

With reference to the fourth aspect, in some implementation manners of the fourth aspect, the identification information is encapsulated in the data packet, and the method further includes: the user plane network element receives the encapsulation information from the session management network element, and the encapsulation information It is used to instruct the user plane network element to encapsulate identification information in the data packet, where the identification information is used to identify the data block to which the data packet belongs.

Based on the above technical solution, the transmission of packet granularity is extended to the transmission of data block granularity through data block identification, so as to avoid waste of resources and improve transmission efficiency.

With reference to the fourth aspect, in some implementations of the fourth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

In the fifth aspect, a communication method is provided, and the method may be executed by an access network device, or may also be executed by a component (such as a chip or a circuit) of the access network device, which is not limited, and for the convenience of description, The following takes the implementation by the access network device as an example for description.

The communication method includes: the access network device receives a plurality of data packets from a user plane network element, each of the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet; the plurality of data packets The packet belongs to multiple different types of data blocks, each type of data block in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same service In the quality of QoS flow; the access network device processes the data packet according to the scheduling priority.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority, and the method further includes: the access network device receives the information from the session The corresponding relationship between the scheduling priorities of multiple different types of data blocks of the network element and the multiple scheduling priority identifiers is managed.

With reference to the fifth aspect, in some implementation manners of the fifth aspect, the data packet further encapsulates identification information of the data block to which the data packet belongs, and the method further includes: the access network device determines whether to Scheduling and this data packet belong to other data packets in the same data block except this data packet.

With reference to the fifth aspect, in some implementations of the fifth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

In a sixth aspect, a communication device is provided, and the communication device is used to execute the method provided in the first aspect above.

The device includes: a processing unit, configured to determine a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS In the stream; a sending unit, configured to send indication information to a policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, wherein each data block includes at least one data packet.

With reference to the sixth aspect, in some implementations of the sixth aspect, the indication information is included in the quality of service QoS requirement, and the QoS requirement is used to configure the parameters of the QoS flow, and the device further includes: a receiving unit configured to receive A response message from the policy control network element, the response message is used to indicate that the parameter configuration of the QoS flow is completed; the sending unit is also used to send downlink data to the user plane network element, the downlink data includes data packets and is used to indicate the An indication of the type of data block to which the packet belongs.

With reference to the sixth aspect, in some implementation manners of the sixth aspect, the sending unit is further configured to send the identification information of the data block to which the data packet belongs to the user plane network element.

With reference to the sixth aspect, in some implementations of the sixth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

For the beneficial effects of the methods shown in the sixth aspect and its possible designs above, refer to the beneficial effects of the first aspect and its possible designs.

In a seventh aspect, a communication device is provided, and the communication device is used to execute the method provided in the second aspect above.

The communication device includes: a receiving unit, configured to receive indication information from an application network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, the plurality of different types of data blocks The data packets in each type of data block are mapped to the same QoS flow; the sending unit is configured to send the scheduling priority corresponding to each type of data block to the session management network element.

With reference to the seventh aspect, in some implementations of the seventh aspect, the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes a parameter for indicating the Information about the scheduling priority of the QoS flow.

With reference to the seventh aspect, in some implementations of the seventh aspect, the receiving unit is further configured to receive a response message from the session management network element, where the response message is used to indicate that the parameter configuration of the QoS flow is completed; the sending unit is also configured to It is used to send the response message to the application network element.

With reference to the seventh aspect, in some implementations of the seventh aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

For the beneficial effects of the methods shown in the seventh aspect and its possible designs above, refer to the beneficial effects of the second aspect and its possible designs.

In an eighth aspect, a communication device is provided, and the communication device is used to execute the method provided in the third aspect above.

The communication device includes: a receiving unit, configured to receive the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS flow; the sending unit is used to send the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate that the user plane network The element encapsulates the scheduling priority corresponding to the received data packet into the data packet, wherein each data block includes at least one data packet.

With reference to the eighth aspect, in some implementations of the eighth aspect, the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes an indicator for indicating the Information about the scheduling priority of the QoS flow.

In conjunction with the eighth aspect, in some implementations of the eighth aspect, the device further includes: a processing unit configured to configure the parameters of the QoS flow according to the PCC rule; the sending unit is also used to send a response to the policy control network element message, the response message is used to indicate that the parameter configuration of the QoS flow is completed.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the apparatus further includes: a processing unit configured to allocate scheduling for a scheduling priority corresponding to each type of data block among the plurality of different types of data blocks A priority identifier, where the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block; the sending unit is also used to send the scheduling priority identifier corresponding to each type of data block to the user plane network element and a corresponding relationship, wherein the corresponding relationship includes a corresponding relationship between the scheduling priorities of the multiple different types of data blocks and multiple identifiers of the scheduling priorities.

With reference to the eighth aspect, in some implementation manners of the eighth aspect, the sending unit is further configured to send the scheduling priorities of multiple different types of data blocks and the correspondence between multiple scheduling priority identifiers to the access network device relation.

With reference to the eighth aspect, in some implementations of the eighth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

With reference to the eighth aspect, in some implementations of the eighth aspect, the sending unit is further configured to send encapsulation information to the user plane network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet In , the identification information is used to identify the data block to which the data packet belongs.

For the beneficial effects of the methods shown in the above eighth aspect and its possible designs, refer to the beneficial effects of the third aspect and its possible designs.

In a ninth aspect, a communication device is provided, and the communication device is used to execute the method provided in the fourth aspect above.

The communication device includes: a receiving unit, configured to receive downlink data from an application network element, the downlink data includes a plurality of different types of data blocks, and each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority level, the data packets in the multiple different types of data blocks are all mapped to the same quality of service QoS flow, and each of the data blocks includes at least one data packet; the processing unit is used for according to the type corresponding to each data packet and each A scheduling priority corresponding to each type of data block determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet is encapsulated with the scheduling priority indicating the data packet. information.

With reference to the ninth aspect, in some implementations of the ninth aspect, the receiving unit is further configured to receive scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, and the encapsulation indication information is used Instructing the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.

With reference to the ninth aspect, in some implementation manners of the ninth aspect, the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority, and the receiving unit is further configured to receive a message from the session management network element The scheduling priority identifier and corresponding relationship, the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block, the corresponding relationship includes the scheduling priorities of the multiple different types of data blocks and multiple of the Correspondence between scheduling priority identifiers.

With reference to the ninth aspect, in some implementation manners of the ninth aspect, the receiving unit is further configured to receive, from the application network element, identification information of the data block to which the data packet belongs.

With reference to the ninth aspect, in some implementation manners of the ninth aspect, the identification information is encapsulated in the data packet, and the receiving unit is further configured to receive encapsulation information from the session management network element, where the encapsulation information is used to indicate the The user plane network element encapsulates identification information in the data packet, and the identification information is used to identify the data block to which the data packet belongs.

With reference to the ninth aspect, in some implementations of the ninth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

For the beneficial effects of the methods shown in the ninth aspect and its possible designs above, refer to the beneficial effects of the fourth aspect and its possible designs.

In a tenth aspect, a communication device is provided, and the communication device is used to execute the method provided in the fifth aspect above.

The communication device includes: a receiving unit, configured to receive a plurality of data packets from a user plane network element, each of the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet; the plurality of The data packets belong to multiple different types of data blocks, and each type of data blocks in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same In the quality of service QoS flow; a processing unit, configured to process the data packet according to the scheduling priority.

With reference to the tenth aspect, in some implementation manners of the tenth aspect, the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority, and the receiving unit is further configured to receive a message from the session management network element The corresponding relationship between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers.

With reference to the tenth aspect, in some implementation manners of the tenth aspect, the data packet is further encapsulated with identification information of the data block to which the data packet belongs, and the processing unit is further configured to determine whether to schedule and the data block according to the identification information The packet belongs to other packets in the same data block than this one.

With reference to the tenth aspect, in some implementations of the tenth aspect, the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or data blocks of different levels , where the layer includes a base layer or an enhancement layer.

For the beneficial effects of the methods shown in the above tenth aspect and its possible designs, please refer to the beneficial effects of the fifth aspect and its possible designs.

In an eleventh aspect, a communication device is provided, and the device is used to execute the methods provided in the first aspect to the fifth aspect. Specifically, the communication device may include units and/or modules for performing the methods provided in the first aspect to the fifth aspect.

In an implementation manner, the transceiver unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input/output interface may be an input/output circuit.

In another implementation, the transceiver unit may be a chip, a chip system, or an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on a circuit; the processing unit may be at least one processor, Processing circuits or logic circuits, etc.

In a twelfth aspect, the present application provides a processor configured to execute the method provided in the foregoing aspects.

For the sending and obtaining/receiving operations involved in the processor, if there is no special description, or if it does not conflict with its actual function or internal logic in the relevant description, it can be understood as the processor's output and reception, input and other operations , can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.

In a thirteenth aspect, a computer-readable storage medium is provided, the computer-readable storage medium stores program code for execution by a device, and the program code includes any implementation manner for performing the first aspect to the fifth aspect above provided method.

In a fourteenth aspect, a computer program product containing instructions is provided, and when the computer program product is run on a computer, the computer is made to execute the method provided by any one of the implementation manners of the first aspect to the fifth aspect above.

A fifteenth aspect provides a chip, the chip includes a processor and a communication interface, the processor reads the instructions stored in the memory through the communication interface, and executes the method provided by any one of the above first to fifth aspects.

Optionally, as an implementation, the chip further includes a memory, in which computer programs or instructions are stored, and the processor is used to execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the processor is used to execute The method provided by any implementation manner of the first aspect to the fifth aspect above.

A sixteenth aspect provides a communication system, including the notification devices shown in the sixth to tenth aspects.

Description of drawings

(a) and (b) in FIG. 1 are schematic diagrams of application scenarios applicable to the embodiments of the present application.

Fig. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application.

FIG. 3 is a schematic block diagram of an apparatus 300 provided by an embodiment of the present application.

FIG. 4 is a schematic block diagram of an apparatus 400 provided by an embodiment of the present application.

Detailed ways

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency Division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solution of the embodiment of the present application can also be applied to device to device (device to device, D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (machine to machine, M2M) communication, machine Type communication (machine type communication, MTC), and Internet of things (internet of things, IoT) communication system or other communication systems.

In order to facilitate understanding of the embodiment of the present application, a communication system to which the embodiment of the present application is applicable is first briefly introduced in conjunction with (a) and (b) in FIG. 1 .

The technical solution of the embodiment of the present application can be applied to the 5G network architecture shown in (a) in Figure 1 and/or (b) in Figure 1, and of course can also be used in future network architectures, such as the sixth generation (6th generation generation, 6G) network architecture, etc., which are not specifically limited in this embodiment of the present application.

The 5G system to which the embodiment of the present application is applicable will be illustrated below with reference to (a) in FIG. 1 and (b) in FIG. 1 . It should be understood that the 5G system described herein is only an example, and should not constitute any limitation to this application.

It should also be understood that some network elements in the 5G system can use service interfaces or point-to-point interfaces for communication. The following introduces 5G based on point-to-point interfaces in combination with (a) in Figure 1 and (b) in Figure 1. System framework, and 5G system framework based on service interface.

As an exemplary illustration, (a) in FIG. 1 shows a schematic architecture diagram of a 5G system 200a to which the embodiment of the present application is applicable. (a) in Figure 1 is a schematic diagram of a 5G network architecture based on a point-to-point interface. As shown in (a) in Figure 1, the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):

User equipment (user equipment, UE), (wireless) access network equipment (radio access network, (R)AN), access and mobility management function (access and mobility management function, AMF) network element, session management function ( session management function (SMF) network element, user plane function (UPF) network element, policy control function (policy control function, PCF) network element, unified data management (unified data management, UDM) network element, application function (application function, AF) network element, data network (data network, DN), network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), unified data management (unified data management, UDM), network exposure function (network exposure function, NEF) network element, unified data repository (unified data repository, UDR), etc.

The network elements shown in (a) in FIG. 1 are briefly introduced below:

1. UE: A terminal that communicates with (R)AN can also be called terminal equipment, access terminal, subscriber unit, subscriber station, mobile station, mobile station (mobile station, MS), mobile terminal (mobile terminal) terminal, MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. A terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. At present, examples of some terminals can be: mobile phone (mobile phone), tablet computer (pad), computer with wireless transceiver function (such as notebook computer, palmtop computer, etc.), mobile internet device (mobile internet device, MID), virtual reality (virtual reality, VR) equipment, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self driving (self driving), wireless in remote medical (remote medical) Terminals, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless Telephones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or connected Other processing devices to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the 5G network or terminal devices in the future evolution of the public land mobile network (PLMN), etc.

In addition, the terminal device may also be a terminal device in an Internet of Things (Internet of things, IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, so as to realize the intelligent network of human-machine interconnection and object interconnection. IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrow band (NB) technology.

It should be understood that the terminal device may be any device that can access the network. A certain air interface technology may be used to communicate with each other between the terminal device and the access network device.

Optionally, the user equipment can be used as a base station. For example, a user equipment may act as a scheduling entity, which provides sidelink signals between user equipments in V2X or D2D, etc. For example, a cell phone and an automobile communicate with each other using sidelink signals. Communication between cellular phones and smart home devices without relaying communication signals through base stations.

2. (R)AN: It is used to provide network access functions for authorized user equipment in a specific area, and can use transmission tunnels with different service qualities according to the level of user equipment and business requirements.

(R)AN can manage wireless resources, provide access services for user equipment, and then complete the forwarding of control signals and user equipment data between user equipment and the core network. (R)AN can also be understood as a base station in a traditional network.

Exemplarily, the access network device in the embodiment of the present application may be any communication device with a wireless transceiver function for communicating with the user equipment. The access network equipment includes but not limited to: evolved Node B (evolved Node B, eNB), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (base transceiver station, BTS), home base station (home evolved Node B, HeNB, or home Node B, HNB), baseband unit (baseBand unit, BBU), wireless fidelity (wireless fidelity, WIFI ) system in the access point (access point, AP), wireless relay node, wireless backhaul node, transmission point (transmission point, TP) or transmission and reception point (transmission and reception point, TRP), etc., can also be 5G , such as, NR, gNB in the system, or, transmission point (TRP or TP), one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, can also be constituted gNB or transmission point network nodes, such as a baseband unit (BBU), or a distributed unit (distributed unit, DU).

In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and realizing the functions of radio resource control (radio resource control, RRC) and packet data convergence protocol (packet data convergence protocol, PDCP) layer. The DU is responsible for processing physical layer protocols and real-time services, realizing the functions of the radio link control (radio link control, RLC) layer, media access control (media access control, MAC) layer and physical (physical, PHY) layer. The AAU implements some physical layer processing functions, radio frequency processing and related functions of active antennas. Since the information of the RRC layer will eventually become the information of the PHY layer, or be transformed from the information of the PHY layer, under this architecture, high-level signaling, such as RRC layer signaling, can also be considered to be sent by the DU , or, sent by DU+AAU. It can be understood that the access network device may be a device including one or more of a CU node, a DU node, and an AAU node. In addition, the CU can be divided into access network devices in the access network (radio access network, RAN), and the CU can also be divided into access network devices in the core network (core network, CN). Do limited.

3. User plane network element: used for packet routing and forwarding and quality of service (QoS) processing of user plane data.

As shown in (a) in Figure 1, in the 5G communication system, the user plane network element may be a UPF network element, which may include an intermediate user plane function (intermediate user plane function, I-UPF) network element, an anchor user Plane function (PDU Session anchor user plane function, PSA-UPF) network element. In the future communication system, the user plane network element may still be a UPF network element, or may have other names, which are not limited in this application.

4. Data network: a network used to provide data transmission.

In future communication systems, the data network may still be a DN, or may have other names, which are not limited in this application.

In the 5G communication system, after the terminal equipment accesses the network, it can establish a protocol data unit (protocol data unit, PDU) session, and access the DN through the PDU session, and can communicate with the application function network element deployed in the DN (application function network element such as for the application server) interaction. As shown in (a) in Figure 1, according to the different DNs accessed by users, the network can select the UPF that accesses the DN as the PDU Session Anchor (PDU Session Anchor, PSA) according to the network policy, and access it through the N6 interface of the PSA Application function network element.

5. Access and mobility management network element: mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in the mobility management entity (MME) function, For example, functions such as lawful interception and access authorization/authentication.

As shown in (a) in FIG. 1 , in a 5G communication system, the access management network element may be an AMF network element. In the future communication system, the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.

6. Session management network element: mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, selection of manageable terminal equipment plane functions, termination points of policy control and charging function interfaces, and downlink Data Notification etc.

As shown in (a) in Figure 1, in the 5G communication system, the session management network element may be an SMF network element, and may include an intermediate session management function (intermediate session management function, I-SMF) network element, an anchor session Management function (anchor session management function, A-SMF) network element. In the future communication system, the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.

7. Policy control network element: a unified policy framework used to guide network behavior, and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

In the 4G communication system, the policy control network element may be a policy and charging rules function (policy and charging rules function, PCRF) network element. As shown in (a) in FIG. 1 , in a 5G communication system, the policy control network element may be a PCF network element. In the future communication system, the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.

8. Data management network element: used to process terminal device identification, access authentication, registration, and mobility management.

As shown in (a) of FIG. 1 , in a 5G communication system, the data management network element may be a UDM network element or a UDR network element. In the future communication system, the unified data management may still be UDM, UDR network element, or may have other names, which are not limited in this application.

The UDM or UDR network element in this embodiment of the present application may refer to a user database. Can exist as a single logical repository for storing user data.

9. Application function network elements: Application function network elements can interact with 5G systems through application function network elements, and are used to access network open function network elements or interact with policy frameworks for policy control, etc.

As shown in (a) in Figure 1, in the 5G communication system, the application function network element may be an application function, AF network element. In the future communication system, the application function network element may still be an AF network element, or may have other names, which are not limited in this application.

10. Network slice selection network element: mainly includes the following functions: select a group of network slice instances for the UE, determine the allowed network slice selection assistance information (network slice selection assistance information, NSSAI), and determine the AMF set that can serve the UE, etc.

As shown in (a) in FIG. 1 , in a 5G communication system, the network element selected for network slicing may be an NSSF network element. In the future communication system, the network element selected for network slicing may still be an NSSF network element, or may have other names, which are not limited in this application.

11. Authentication service network element: used for authentication services, generating keys to realize two-way authentication of terminal equipment, and supporting a unified authentication framework.

As shown in (a) of FIG. 1 , in a 5G communication system, the authentication service network element may be an AUSF network element. In the future communication system, the authentication service function network element may still be an AUSF network element, or may have other names, which are not limited in this application.

12. Network opening function network element: used to provide customized functions for network opening.

As shown in (a) in Figure 1, in the 5G communication system, the network exposure function network element may be a network exposure function (network exposure function, NEF) network element. In the future communication system, the network exposure function network element is still It may be an NEF network element, or may have other names, which are not limited in this application.

The 5G communication system can also open 5GC-supported capabilities to external application function network elements through NEF network elements, such as providing small data transmission capabilities.

It can be understood that the above-mentioned network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). The above-mentioned network elements or functions can be divided into one or more services, and further, there may also be services that exist independently of network functions. In this application, an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or a service instance existing independently of the network function may be referred to as a service instance.

Further, the AF network element may be referred to as AF, the NEF network element may be referred to as NEF, and the AMF network element may be referred to as AMF. That is, the AF described in the subsequent application can be replaced by an application function network element, the NEF can be replaced by a network opening function network element, and the AMF can be replaced by an access and mobility management network element.

It can be understood that the above-mentioned network element or functional network element may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform). The above-mentioned network elements or functions can be divided into one or more services, and further, there may also be services that exist independently of network functions. In this application, an instance of the above-mentioned function, or an instance of a service included in the above-mentioned function, or a service instance existing independently of the network function may be referred to as a service instance.

It can be seen from (a) in FIG. 1 that the interfaces between network elements of the control plane in (a) in FIG. 1 are point-to-point interfaces.

In the architecture shown in (a) in Figure 1, the interface names and functions between each network element are as follows:

1), N1: the interface between the AMF and the terminal, which can be used to transmit QoS control rules and the like to the terminal.

2), N2: the interface between the AMF and the RAN, which can be used to transfer radio bearer control information from the core network side to the RAN.

3), N3: the interface between the RAN and the UPF, mainly used to transfer the uplink and downlink user plane data between the RAN and the UPF.

4), N4: The interface between SMF and UPF, which can be used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. Information reporting.

5), N5: the interface between the AF and the PCF, which can be used for sending application service requests and reporting network events.

6), N6: the interface between UPF and DN, used to transfer the uplink and downlink user data flow between UPF and DN.

7), N7: the interface between PCF and SMF, which can be used to deliver protocol data unit (protocol data unit, PDU) session granularity and service data flow granularity control policy.

8), N8: The interface between AMF and UDM, which can be used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register terminal current mobility management related information with UDM.

9), N9: a user plane interface between UPF and UPF, used to transmit uplink and downlink user data flows between UPFs.

10), N10: the interface between SMF and UDM, which can be used for SMF to obtain session management-related subscription data from UDM, and for SMF to register terminal current session-related information with UDM.

11), N11: the interface between SMF and AMF, which can be used to transfer PDU session tunnel information between RAN and UPF, transfer control messages sent to terminals, transfer radio resource control information sent to RAN, etc.

12), N12: the interface between AMF and AUSF, which can be used for AMF to initiate an authentication process to AUSF, which can carry SUCI as a subscription identifier;

13), N13: the interface between UDM and AUSF, which can be used for AUSF to obtain user authentication vector from UDM to execute the authentication process.

As an exemplary illustration, (b) in FIG. 1 shows a schematic architecture diagram of a 5G system 200b to which this embodiment of the present application applies. (b) in Figure 1 is a schematic diagram of a 5G network architecture based on a service interface. As shown in (b) in Figure 1, the network architecture may include but not limited to the following network elements (or called functional network elements, functional entities, nodes, devices, etc.):

UE, (R)AN, AMF network element, SMF network element, UPF network element, PCF network element, UDM network element, AF network element, DN, NSSF, AUSF, UDM, NEF network element, UDR, etc.

For the introduction of the functions of the network elements, reference may be made to the introduction of the functions of the corresponding network elements in (b) in FIG. 1 , and details are not repeated here. The main difference between (b) in Figure 1 and (a) in Figure 1 is that the interface between each control plane network element in (b) in Figure 1 is a service-oriented interface, and (a) in Figure 1 The interface between each control plane network element in ) is a point-to-point interface.

Nnssf, Nudr, Nausf, Nnef, Namf, Npcf, Nsmf, Nudm, and Naf in (b) in Figure 1 are the service interfaces provided by the above-mentioned NSSF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM, and AF, respectively , which is used to call the corresponding service-oriented operation. N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers may refer to the meanings defined in the third generation partnership project (3rd generation partnership project, 3GPP) standard agreement, and no limitation is made here.

It should be understood that the above-mentioned network architecture applicable to the embodiment of the present application is only an illustration, and the applicable network architecture of the embodiment of the present application is not limited thereto. Any network architecture that can implement the functions of the above-mentioned network elements is applicable to this application Application example.

It should also be understood that the AMF, SMF, UPF, PCF, NEF, etc. shown in (a) in Figure 1 or (b) in Figure 1 can be understood as network elements for implementing different functions, for example, they can be combined into Network slicing. These network elements can be independent devices, or can be integrated in the same device to achieve different functions, or can be network elements in hardware devices, or software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.

It should also be understood that the above names are only defined for the convenience of distinguishing different functions, and shall not constitute any limitation to the present application. This application does not exclude the possibility of using other names in the 5G network and other networks in the future. For example, in a 6G network, some or all of the above network elements may use the terms in 5G, or may use other names.

It should also be understood that the name of the interface between network elements in (a) or (b) in FIG. limited. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.

It should be understood that the method provided in this embodiment of the present application may be applied to a 5G communication system, for example, the communication system shown in (a) in FIG. 1 or (b) in FIG. 1 . However, this embodiment of the present application does not limit the applicable scenarios of the method, for example, it is also applicable to other network architectures including network elements capable of implementing corresponding functions. Also for example, the 6th generation communication (the 6th generation, 6G) system architecture, etc. Moreover, the names of the various network elements used above in the embodiments of the present application may keep the same function in the future communication system, but the names will be changed.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, some terms or concepts that may be involved in the embodiments of the present application are briefly described.

1. PDU session: an association between a terminal device and a data network (DN), used to provide a PDU connection service.

2. QoS flow mechanism: The current standard stipulates that QoS flow is the minimum QoS control granularity, and each QoS flow has a corresponding QoS configuration.

The QoS parameters included in the QoS configuration describe the specific QoS requirements. The QoS parameters mainly include:

QoS flow index (QoS flow index, QFI), service quality identifier (5G quality of service identifier, 5QI) under 5G network, allocation and reservation priority (allocation and retention priority, ARP), guaranteed flow bit rate (guaranteed flow bit rate, GFBR), maximum flow bit rate (maximum flow bit rate, MFBR).

Furthermore, the 5QI in the QoS parameter is a set of QoS feature combination indexes, and the QoS features include:

Resource type (resource type), priority (priority level, PL), packet delay budget (packet delay budget, PDB), packet error rate (packet error rate, PER), statistical period (averaging window) and maximum burst data volume (maximum data burst volume), etc.

Among them, resource types include: non-guaranteed bit rate (non-GRB), minimum guaranteed bit rate (guaranteed bit rate, GRB), delay-sensitive GRB (delay-critical GBR); the maximum burst data volume is Delay-sensitive GRB-specific parameters. The PDB is used to indicate the upper limit of the transmission delay from the UE to the UPF, and the PDB of the uplink and downlink data is the same. PER represents the upper bound of the packet loss rate. PL is used to indicate that a PDB that cannot satisfy multiple QoS flows, prioritizes the QoS requirements with high priority (for example, a small PL value), for example, in the case of congestion, when one or more QoS flows cannot satisfy all QoS When required, the QoS flow can be prioritized according to the priority level.

5QI is a scalar used to index to the corresponding 5G QoS feature. 5QI is divided into standardized 5QI, pre-configured 5QI and dynamically allocated 5QI. For a standardized 5QI, it corresponds to a set of standardized 5G QoS characteristic values; for a pre-configured 5QI, the corresponding 5G QoS characteristic value is pre-configured on the access network element; The characteristics are sent to the network elements of the access network by the core network equipment through the QoS profile (QoS profile).

QFI is used to identify the unique identifier of different QoS flows within a PDU session.

ARP includes priority level, preemption capability and preemption capability.

GFBR represents the bit rate expected to be provided to the guaranteed bit rate (guaranteed bit rate, GBR) QoS flow (flow).

MFBR limits the bit rate provided to GBR QoS flow, that is, the maximum bit rate provided to GBR QoS flow. Packets can be dropped if the bit rate is exceeded.

Specifically, the standard defines a part of 5QI QoS characteristic values, which can be used directly, and also allows operators and/or equipment manufacturers to allocate non-conflicting 5QIs and pre-set corresponding QoS characteristic values for use in operator networks.

After the QoS flow configuration is generated, the 5G control plane network elements AMF and SMF deliver the QoS flow configuration to UE, RAN, and UPF.

3. QoS model: In order to ensure the end-to-end service quality of the business, a QoS model based on QoS flow (flow) is proposed. The QoS model supports QoS flow with guaranteed bit rate (ie GBR QoS flow) and QoS flow without guaranteed bit rate (ie non-GBR (non-GBR) QoS flow). Packets controlled by the same QoS flow receive the same transmission processing (such as scheduling, admission threshold, etc.). For a terminal device, one or more data connection sessions (such as PDU sessions) can be established with the network; each data connection session can transmit data flows corresponding to one or more QoS flows. Each QoS flow is identified by a QoS flow identifier (QFI), which uniquely identifies a QoS flow in the same data connection session. In addition, each QoS flow corresponds to a data radio bearer (data radio bearer, DRB), and a DRB can correspond to one or more QoS flows.

Among them, whether a QoS flow is a GBR QoS flow or a Non-GBR QoS flow is determined by the corresponding QoS file (QoS profile).

For GBR QoS flow, the corresponding QoS file contains the following QoS parameters: 5QI, ARP, GFBR, MFBR, and/or QNC. According to whether the QoS file contains QNC, the GBR QoS flow is determined as the GRB QoS flow that needs notification control (notification control) and the GBR QoS flow that does not need notification control. For the GBR QoS flow that needs to be notified and controlled, when the access network element detects that the corresponding QoS flow resource cannot be satisfied, the access network element notifies the session management function SMF of the event (that is, the QoS flow resource corresponding to the GBR QoS flow cannot satisfied). Further SMF can initiate QoS flow deletion or QoS flow modification process (for example, modify QoS parameters of QoS flow).

For Non-GBR QoS flow, the corresponding QoS file contains the following QoS parameters: 5QI, ARP and/or RQA.

4. PL: Indicates the priority of scheduling resources in the QoS Flow, which can be used to identify the QoS Flow corresponding to the data flow of the same UE, and can also be used to identify the QoS Flow corresponding to the data flow of different UEs. In the case of congestion, when the current resources cannot support one or more QoS Flows to meet the corresponding QoS requirements (such as PDB, PER, etc.), PL is used to select which QoS Flows correspond to the QoS requirements.

5. General packet radio service tunneling protocol user (general packet radio service tunneling protocol user, GTP-U) tunnel: During the establishment of the PDU session, the connection between the RAN and the UPF will use the GTP-U tunnel, which will come from Data on the UE side or data destined for the UE side is added to the tunnel for transmission.

6. Tunnel Endpoint Identifier (TEID): It is the tunnel endpoint of the GTP-U protocol, which can uniquely determine a section of tunnel between two network elements.

7. Quality of Experience (QoE): In Extended Reality (XR) services, QoE is often the most intuitive and effective measure. Exemplarily, QoE can be reflected in that the data streams transmitted in the same QoS flow may have different importance to user experience, for example, I frames are more important than P frames, and those located in the center of the field of view are more important than those located at the edge of the field of view Important, base layer data is more important than enhancement layer data, and so on.

From the above description of the QoS parameters of the current QoS flow, it can be seen that each QoS flow is only expressed by a set of QoS parameters, and a QoS flow has only one parameter such as 5QI, that is, only one scheduling priority, which cannot be guaranteed when the network is blocked. For the QoS requirements of all data stream transmission, different data streams will not be scheduled differently according to the importance of data streams to QoE. For example, how to implement priority scheduling of data streams with high importance to QoE to meet the transmission of these data streams After the QoS requirements are met, the data flows with low importance to QoE are scheduled, and the differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow is realized.

In order to solve the shortcomings of the current data flow scheduling, this application provides a communication method, by configuring multiple scheduling priorities for different types of data packets mapped by a QoS flow, in order to achieve different types of data blocks corresponding to a single QoS flow Differentiated scheduling of packets.

The above describes the applicable scenarios of the embodiment of this application in conjunction with (a) in Figure 1 and (b) in Figure 1, and briefly introduces the defects of the current data flow scheduling method, and briefly introduces the application The basic concepts involved in the above, the communication method provided by this application will be introduced in detail below with reference to the accompanying drawings.

The embodiments shown below do not specifically limit the specific structure of the execution subject of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run to provide the method according to the embodiment of the present application. For example, the execution subject of the method provided by the embodiment of the present application may be a core network device, or a functional module in the core network device that can call a program and execute the program.

In order to facilitate understanding of the embodiments of the present application, the following descriptions are made.

First, in this application, "for indicating" can be understood as "enabling", and "enabling" can include direct enabling and indirect enabling. When describing a certain information for enabling A, it may include that the information directly enables A or indirectly enables A, but it does not mean that A must be carried in the information.

The information enabled by the information is called the information to be enabled. In the specific implementation process, there are many ways to enable the information to be enabled. For example, but not limited to, the information to be enabled can be directly enabled. The enabling information itself or the index of the information to be enabled, etc. The to-be-enabled information may also be indirectly enabled by enabling other information, where there is an association relationship between the other information and the to-be-enabled information. It is also possible to enable only a part of the information to be enabled, while other parts of the information to be enabled are known or agreed in advance. For example, specific information can also be enabled by means of a pre-agreed (for example, protocol-specified) arrangement order of each information, thereby reducing the enabling overhead to a certain extent. At the same time, common parts of each information can be identified and enabled uniformly, so as to reduce the enabling overhead caused by enabling the same information separately.

Second, the first, second and various numbers shown in this application (for example, "#1", "#2", etc.) The scope of the application examples. For example, distinguishing between different messages, etc. It is not intended to describe a particular order or sequence. It is to be understood that the terms so described are interchangeable under appropriate circumstances in order to enable descriptions other than the embodiments of the application.

Third, in this application, "pre-configuration" may include pre-definition, for example, protocol definition. Wherein, "predefine" can be realized by pre-saving corresponding codes, tables or other methods that can be used to indicate related information in the device (for example, including each network element), and this application does not limit its specific implementation.

Fourth, the "storage" mentioned in the embodiment of the present application may refer to saving in one or more memories. The one or more memories may be provided independently, or may be integrated in an encoder or decoder, a processor, or a communication device. A part of the one or more memories may also be provided separately, and a part may be integrated in a decoder, a processor, or a communication device. The type of the storage may be any form of storage medium, which is not limited in this application.

Fifth, the term "and/or" in this article is only an association relationship describing associated objects, which means that there may be three relationships, for example, A and/or B, which can mean: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.

Sixth, the "protocol" involved in the embodiment of this application may refer to a standard protocol in the communication field, for example, it may include 5G protocol, new radio (new radio, NR) protocol and related protocols applied in future communication systems. Applications are not limited to this.

Hereinafter, without loss of generality, the communication method provided by the embodiment of the present application is described in detail by taking interaction between network elements as an example.

For ease of description, in the following, the access network device is RAN, the mobility management function network element is AMF, the application function network element is AF, the session management function network element is SMF, the user plane function network element is UPF, and the terminal is UE. Example to illustrate.

It should be noted that there is no limitation on the name of the device in this application.

Fig. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application, including the following steps:

S210, the AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks.

Specifically, the multiple data blocks of different types may be two or more data blocks of different types. The type of the data block involved in this embodiment of the present application may be a frame type such as an I frame, a P frame, a B frame, and the like. The type of the data block may also indicate the position of the user's field of vision, such as the center position and the edge position. The type of data block can also indicate the level corresponding to the data block, such as base layer, enhancement layer, etc.

Among them, data blocks with different levels can be understood as: data blocks have different functions. For example, some are to ensure that the basic video can be played smoothly, but the definition may not be high. These are the basic layers; Better definition, more details, better user experience, these are enhancement layers.

It should be understood that the above-mentioned types of data blocks are just examples. The protection scope of the present application is not limited in any way, and data blocks can also be classified in other ways, for example, original stream, error correction stream, and so on. Examples are not given here. In this embodiment of the present application, there is no limitation on the specific reasons for different types of data blocks. For example, the AF may arbitrarily indicate that the two data blocks are data blocks of different types, and the scheduling priorities of the two data blocks are different.

Exemplarily, multiple data blocks of different types correspond to different scheduling priorities. For example, I frame and P frame are data blocks of different types, and the scheduling priority corresponding to I frame is higher than the scheduling priority corresponding to P frame; The scheduling priority corresponding to the data block at the edge of the view is higher; for another example, the scheduling priority corresponding to the base layer data block is higher than the scheduling priority corresponding to the enhancement layer data block.

As a possible implementation manner, the AF may determine that different types of data blocks correspond to different scheduling priorities according to the configuration information.

As another possible implementation manner, the AF may determine that different types of data blocks correspond to different scheduling priorities according to an instruction of the network management device.

As yet another possible implementation manner, the AF may determine that different types of data blocks correspond to different scheduling priorities according to historical data transmission results.

It should be noted that the manner in which the above-mentioned AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks is only an example, and does not constitute any limitation on the protection scope of the present application. In this embodiment of the present application, there is no limitation on how the AF determines the scheduling priority corresponding to each type of data block among multiple different types of data blocks.

Specifically, the data block involved in this embodiment of the present application includes at least one data packet, for example, the data block may be a frame, a slice (slice), or a block (tile). In addition, it should be noted that the data packets in the above-mentioned multiple data blocks of different types are all mapped to the same QoS flow.

The data packets in the above-mentioned multiple different types of data blocks are all mapped to the same quality of service QoS flow, which can be understood as:

Multiple different types of data blocks correspond to the same quality of service QoS flow; or, it can be understood as multiple different types of data blocks carried in the same QoS flow; or it can also be understood as multiple different types of data blocks corresponding to multiple Different scheduling priorities are used to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

Further, after the AF determines the scheduling priority corresponding to each type of data block in multiple different types of data blocks, the configuration of the scheduling priority corresponding to each type of data block can be realized through the control plane through the instruction information, as shown in Figure 2 The method flow shown also includes:

S220, the AF sends indication information to the PCF.

The indication information is used to indicate the scheduling priority corresponding to each type of data block.

As a possible implementation, the AF sending the indication information to the PCF may be that the AF directly sends the indication information to the PCF, for example, the AF uses the communication interface between the AF and the PCF (for example, N5) or through the service interface (for example, Naf and Npcf) send indication information to the PCF.

As another possible implementation manner, the sending of the indication information by the AF to the PCF may be that the AF indirectly sends the indication information to the PCF, for example, the AF sends the indication information to the PCF through other functional network elements (eg, NEF, etc.).

Specifically, the indication information is used to indicate the scheduling priority corresponding to each type of data block. It can be understood that the AF sends indication information to the PCF, and the indication information indicates multiple scheduling priorities corresponding to multiple data blocks of different types. .

As a possible implementation, the indication information is included in the message currently sending the QoS requirement, and the scheduling priority corresponding to each type of data block can also be understood as a QoS requirement.

As another possible implementation manner, the indication information may be included in other messages (eg, existing or newly added messages between the AF and the PCF).

It should be noted that, the foregoing is only an example of a possible way for the AF to send the indication information to the PCF, and does not constitute any limitation to the protection scope of the present application. In this embodiment of the present application, there is no limitation on how the AF sends the indication information to the PCF.

Further, after the PCF receives the above indication information, it can send the scheduling priority corresponding to each type of data block to the SMF, and the method flow shown in FIG. 2 also includes:

S230. The PCF sends the scheduling priority corresponding to each type of data block to the SMF.

Exemplarily, the PCF sends the scheduling priority corresponding to each type of data block to the SMF, which may be implemented by sending multiple scheduling priorities and mapping relationships corresponding to multiple data blocks of different types, wherein the mapping relationship includes Mapping relationships between multiple different types of data blocks and multiple scheduling priorities.

For example, when the AF indicates the scheduling priority corresponding to each type of data block through the above indication information, the mapping relationship is used to indicate that the I frame corresponds to the scheduling priority #1, and the P frame corresponds to the scheduling priority #2. Wherein, scheduling priority #1 is higher than scheduling priority #2.

For another example, when the AF indicates that data blocks in different positions in the user's field of view correspond to different scheduling priorities through the above-mentioned indication information, the mapping relationship is used to indicate that the data block in the center of the user's field of view corresponds to scheduling priority #3, and the The data blocks at the edge of the user's field of view correspond to scheduling priority #4, wherein scheduling priority #3 is higher than scheduling priority #4.

It should be understood that the PCF sends the above mapping relationship to the SMF, so that the SMF configures the scheduling priority corresponding to the data block to the UPF.

As a possible implementation, the scheduling priority corresponding to each type of data block above can be sent to SMF through the policy and charging control rule (PCC rule), that is, each type of data block The corresponding scheduling priority is included in the PCC rule.

Optionally, the PCC rule also includes information for indicating the scheduling priority of the QoS flow.

In order to facilitate the distinction, the scheduling priority of the differential scheduling of data packets of different types of data blocks corresponding to the same QoS flow (that is, the scheduling priority corresponding to each type of data block mentioned above) can be called the first scheduling priority ; The scheduling priority of this QoS flow may be called the second scheduling priority.

As a possible implementation manner, the above-mentioned second scheduling priority may be included in the PCC rule. Specifically, multiple first scheduling priorities are within the QoS flow, and a second scheduling priority is responsible for external scheduling priority comparisons. The QoS is determined by comparing the second scheduling priority with other QoS flows. After the scheduling priorities between flows, the scheduling priorities of different types of data packets inside the QoS flow are determined through multiple first scheduling priorities.

As another possible implementation manner, the above-mentioned second scheduling priority may not be included in the PCC rule. The PCC rule includes multiple first scheduling priorities. Since the scheduling priority determination principles are the same, these multiple first scheduling priorities need to consider the scheduling priorities between QoS flows at the same time, which is equivalent to if the first scheduling priority It is QFI#1 packet 1 (scheduling priority is 1), QFI#1 packet 2 (scheduling priority is 3), but the scheduling priority of another QoS flow is QFI#2 packet 1 (scheduling priority is 2), Then the scheduling sequence is QFI#1 packet 1, QFI#2 packet 1, QFI#1 packet 2. In this case, the second scheduling priority may not be included in the PCC rule.

Further, after the SMF receives the PCC rule, it performs UPF configuration, and the method flow shown in Figure 2 also includes:

S240. The SMF configures the UPF.

In this embodiment, the SMF configuring the UPF includes: the SMF sends encapsulation indication information to the UPF, and the encapsulation indication information is used to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet into the data packet.

Optionally, encapsulating the scheduling priority corresponding to the data packet in the data packet includes: encapsulating the scheduling priority corresponding to the data packet in a header of the data packet, for example, encapsulating in a GTP-U header. Alternatively, the scheduling priority corresponding to the data packet may also be encapsulated in the payload of the data packet, which is not limited in this application.

It should be understood that in order to enable UPF to encapsulate the scheduling priority corresponding to the received data packet into the data packet, the SMF also needs to send the scheduling priority corresponding to each type of data block to the UPF during the process of configuring the UPF, so that After the UPF receives the data packet, it determines the scheduling priority of the data packet.

As a possible implementation, the SMF sends the scheduling priority corresponding to each type of data block to the UPF, which can be realized by sending multiple scheduling priorities and mapping relationships corresponding to multiple different types of data blocks, wherein the mapping The relationship includes a mapping relationship between multiple data blocks of different types and multiple scheduling priorities.

As another possible implementation, the SMF sends the scheduling priority corresponding to each type of data block to the UPF, which can be realized by sending the scheduling priority identifier and corresponding relationship corresponding to each type of data block, wherein the corresponding relationship includes The corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers. In this implementation, the SMF needs to assign a scheduling priority identifier to the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks. The method flow shown in FIG. 2 also includes:

S231. The SMF allocates a scheduling priority identifier.

The scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block.

Specifically, in the case where the SMF assigns a scheduling priority identifier, the SMF may notify the RAN of the scheduling priorities of multiple different types of data blocks and the correspondence between multiple scheduling priority identifiers. In this implementation, FIG. 2 The illustrated method flow may also include:

S232. The SMF sends the corresponding relationship to the RAN.

The corresponding relationship is used to indicate the correspondence between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers.

Optionally, in this embodiment, the SMF configuring the UPF may also include: the SMF also sends encapsulation information to the UPF, the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet, the identification The information is used to identify the data block to which the data packet belongs.

Optionally, the encapsulation indication information and the encapsulation information may be one indication information or multiple indication information.

Optionally, the identification information is encapsulated in the data packet, including: the identification information is encapsulated in the header of the data packet; or, the identification information may also be encapsulated in the payload of the data packet, which is not limited in this application.

After the above UPF configuration is completed, the SMF configures the parameters of the QoS flow according to the received PCC rule. The method flow shown in Figure 2 also includes:

S250, the SMF configures parameters of the QoS flow.

SMF configures the parameters of QoS flow based on the above-mentioned multiple different scheduling priorities. It can be understood that one QoS flow corresponds to multiple scheduling priorities. Among them, the parameters for configuring QoS flow can be understood as the strategy for configuring QoS flow.

Exemplarily, SMF configures the parameter of QoS flow (also can be referred to as policy), also can be referred to as the parameter that SMF sends QoS flow to UPF, RAN and/or UE. Include the following steps:

Step 1: SMF determines the information of QoS flow (also called QoS policy) according to the PCC rule sent by PCF.

Step 2: SMF issues corresponding QoS policies to UPF, RAN and UE respectively. For example, the SMF sends the first QoS policy to the UPF, the SMF sends the second QoS policy to the RAN, and the SMF sends the third QoS policy to the UE.

The SMF sends the first QoS policy to the UPF, including: the SMF sends packet detection rules (Packet Detection Rule, PDRs) to the UPF.

The SMF sends the second QoS policy to the RAN, including: the SMF sends the QoS file (profile) to the RAN through the AMF.

The SMF sends the third QoS policy to the UE, including: the SMF sends the QoS rule (QoS rule) to the UE through the AMF and the RAN, and the QoS rule includes QoS control information.

Further, after the UE, UE, RAN and UPF receive the QoS flow parameters, the RAN establishes the DRB of the air interface according to the QoS file, and stores the binding relationship between the QoS flow and the DRB. Optionally, the UE executes the uplink data packet according to the QoS rule The transmission. And the UPF performs QFI identification on the downlink data packet according to the PDRs, and performs QFI verification on the uplink data packet.

It should be understood that the above is simply a description of the process of SMF configuring the parameters of QoS flow and does not constitute any limitation on the protection scope of this application. The process of configuring the parameters of QoS flow can refer to the description of the parameters of currently configuring QoS flow, which will not be described in detail in this application.

Further, after the parameter configuration of the QoS flow is completed, the AF may be notified through a response message so as to facilitate the AF to perform downlink data transmission. The method flow shown in FIG. 2 also includes:

S251. The SMF sends a response message to the PCF.

The response message is used to indicate that the parameter configuration of the QoS flow is completed.

S252. The PCF sends a response message to the AF.

Specifically, after the AF receives the response message, it knows that the parameter configuration of the QoS flow is completed, and the downlink data transmission can be performed; or it is understood that the AF performs downlink data transmission in response to the response message, and the method flow shown in FIG. 2 also includes:

S260, the AF sends downlink data to the UPF.

The downlink data includes a data packet and indication information for indicating the type of the data block to which the data packet belongs.

Exemplarily, the indication information indicating the type of the data block to which the data packet belongs may be referred to as type indication information, and the type indication information may be used to indicate the type of the data block, for example, indicating whether the data block is an I frame or a P frame; For another example, indicate whether the data block is located at the center of the user's field of view or at the edge of the user's field of view; and for another example, indicate whether the data block is a base layer data block or an enhancement layer data block.

As a possible implementation, the data packet and the indication information used to indicate the type of the data block to which the data packet belongs can be transmitted separately, for example, the data packet and the type indication information are two independent information elements, included in the same message middle.

As another possible implementation, the data packet and the indication information used to indicate the type of the data block to which the data packet belongs can be transmitted at the same time, for example, the type indication information is encapsulated in the header of the data packet to indicate that the data packet The type of the data block it belongs to.

It should be noted that, in this application, there is no limitation on the name of the information. For example, the above-mentioned type indication information may be called first indication information, indication information, and so on.

Optionally, the downlink data may also include identification information of the data block to which the data packet belongs. Wherein, the identification information of the data block includes, but not limited to, an identification (identify, ID) of the data block, attribute information of the data block, and other information that can be used to identify the data block.

Exemplarily, the identification information of the data block and the above-mentioned data packet and type indication information may be included in the same message. For example, the application network element sends a message to the user plane network element, and the message includes a data packet, type indication information for indicating the data block to which the data packet belongs, and identification information of the data block to which the data packet belongs.

After the UPF receives the downlink data, it can determine the scheduling priority of the data packet according to the configuration of the above-mentioned SMF (refer to the description in the above-mentioned step S240), the received data packet and the type indication information, and the method flow shown in FIG. include:

S270, the UPF determines the scheduling priority of the data packet.

Specifically, the UPF determines the type corresponding to the data block to which the data packet belongs according to the type indication information, and determines the scheduling priority of the received data packet according to a scheduling priority corresponding to each type of data block configured in the above SMF.

Further, the UPF encapsulates the information indicating the scheduling priority of the data packet in the data packet, and the method flow shown in FIG. 2 also includes:

S280, the UPF encapsulates the data packet.

As a possible implementation manner, the UPF encapsulating the data packet includes: UPF encapsulating the scheduling priority of the data packet in the data packet.

For example, UPF encapsulates the scheduling priority of the data packet into the GTP-U packet header.

As another possible implementation manner, the UPF encapsulating the data packet includes: the UPF encapsulating the scheduling priority identifier used to identify the scheduling priority in the data packet.

For example, the UPF encapsulates the scheduling priority identifier of the scheduling priority of the data packet into the GTP-U packet header.

Optionally, in the case that the above-mentioned downlink data includes the identification information of the data block to which the data packet belongs, the UPF encapsulating the data packet includes: UPF encapsulating the identification information of the data block to which the data packet belongs in the data packet.

For example, UPF encapsulates the identification information of the data block to which the data packet belongs into the GTP-U packet header.

After the UPF completes the data packet encapsulation, the UPF can send the encapsulated data packet to the RAN, and the method flow shown in Figure 2 also includes:

S290, the UPF sends the data packet to the RAN.

Exemplarily, the UPF sends the GTP-U data packet to the RAN.

Further, the RAN may process the received data packet, and the method flow shown in FIG. 2 also includes:

S291, the RAN processes the data packet.

Specifically, the RAN processing the data packet includes the following steps 1 to 4:

Step 1: The RAN decapsulates the data packet to determine the scheduling priority of the data packet.

For example, the RAN determines the scheduling priority of the data packet according to the information indicating the scheduling priority corresponding to the data packet encapsulated in the data packet (eg, GTP-U header).

As a possible implementation manner, the scheduling priority corresponding to the data packet is encapsulated in the data packet, and the RAN can obtain the scheduling priority corresponding to the data packet after decapsulating the data packet.

As another possible implementation, the data packet encapsulates the scheduling priority identifier of the scheduling priority corresponding to the data packet, and after the RAN decapsulates the data packet, obtains the scheduling priority of the scheduling priority corresponding to the data packet identification, and further determine the scheduling priority corresponding to the data packet according to the corresponding relationship received from the SMF (refer to the description of the above step S232).

Optionally, in the case that the identification information of the data block to which the data packet belongs is encapsulated in the data packet (for example, the GTP-U packet header), the RAN also performs the following step 2.

Step 2: The RAN decapsulates the data packet to determine the identification information of the data block to which the data packet belongs.

After the RAN determines the scheduling priority of the data packet, or determines the scheduling priority of the data packet and the identification information of the data block to which the data packet belongs, it can map the data packet according to the scheduling priority of the data packet and other parameters of the QoS flow of the data packet ( For example, the 5QI specified in the current agreement) performs QoS processing; or, in the case of determining the identification information of the data block to which the data packet belongs, the data with the same identification information can be determined according to the identification information of the data block to which the data packet belongs Packet processing, including determining the scheduling of data packets with the same identification information.

Step 3: RAN schedules the data packets.

It can be understood that, compared to the QoS flow mechanism specified in the current protocol, performing QoS processing on the data packet in this embodiment is in addition to considering other parameters of the QoS flow that maps the data packet (such as the QoS parameters specified in the current protocol) , it is also necessary to consider the scheduling priority of the packet. Wherein, the scheduling priority of the data packet can also be understood as a kind of QoS parameter, which is a newly added QoS parameter.

Exemplarily, when the RAN receives multiple data packets (eg, data packet #1, data packet #2 and data packet #3) mapped to the same QoS flow. The scheduling priorities corresponding to the plurality of data packets are different. For example, data packet #1 corresponds to scheduling priority #1, data packet #2 corresponds to scheduling priority #2, and data packet #3 corresponds to scheduling priority #3. Priority #1 is higher than scheduling priority #2, and scheduling priority #2 is higher than scheduling priority #3. Processing the data packets by the RAN includes: sending each data packet according to the scheduling priority corresponding to each data packet. For example, data packet #1 is scheduled (or sent) first, then data packet #2 is scheduled, and data packet #3 is finally scheduled to implement differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow.

Optionally, in the case where the identification information of the data block to which the data packet belongs is encapsulated in the data packet (eg, GTP-U header), the RAN processing the data packet further includes:

The RAN expands the transmission granularity according to the identification information of the data block, from packet granularity transmission to data block (frame, tile or slice) granularity transmission. For example, if some data packets in a data block cannot be successfully received due to reasons such as discarding during transmission, the RAN may not schedule resources for other data packets with the same identification information of the data block. The scheduling of the association relationship between them can avoid the problem that although the data packet is successfully transmitted, it cannot be decoded to a certain extent, thereby improving the transmission efficiency.

For another example, if the RAN has successfully received some data packets in a certain data block, then the RAN can schedule resources in advance for other data packets with the identification information of the same data block to which the successfully received data packets belong, which can reduce the number of data packets to a certain extent. transmission delay.

Among them, the resource scheduling of the data packet by the RAN can be understood as allocating resources for the data packet, and the priority scheduling can be understood as prioritizing the allocation of RAN-related resources to the data packet according to the QoS requirements of the data packet, so that the data packet can be successfully sent . Further, the RAN may send the received data packet to the UE, and perform step 4.

Step 4: When the RAN receives the downlink data packet, according to the QFI in the data packet header and the binding relationship between the corresponding QoS flow and the DRB, the downlink data packet is placed on the corresponding DRB for transmission.

It should be noted that the above is just the downlink data as an example to illustrate the differential scheduling of data packets of different types of data blocks corresponding to the same QoS flow. For uplink data transmission, after completing the configuration of different scheduling priorities in the same QoS flow (After the above-mentioned step S252), when the terminal device determines to send the uplink data packet, the QoS flow is determined according to the QoS rule, in order to realize the differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow, the terminal device is sending Before the uplink data packet, when informing the access network device that there is uplink data to be sent through the Physical Uplink Control Channel (PUCCH), the type of the data block to which the uplink data packet belongs must be informed at the same time, and the uplink scheduler according to the data The block type allocates the resources required for sending data packets to the terminal device. Different data block types may allocate different resources (size, location, etc.), so as to realize the data packets of different types of data blocks corresponding to the same QoS flow of uplink data. differentiated scheduling.

It should be understood that the specific example shown in FIG. 2 in the embodiment of the present application is only to help those skilled in the art better understand the embodiment of the present application, but not to limit the scope of the embodiment of the present application. It should also be understood that the sequence numbers of the above processes do not mean the order of execution, and the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

It should also be understood that in each embodiment of the present application, if there is no special explanation and logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments New embodiments can be formed by combining them according to their inherent logical relationships.

It should also be understood that in some of the above embodiments, the network elements in the existing network architecture are mainly used as examples for illustration (such as AF, AMF, SMF, etc.), and it should be understood that the specific form of the network element The application examples are not limited. For example, network elements that can implement the same function in the future are applicable to this embodiment of the application.

It can be understood that, in the above method embodiments, the methods and operations implemented by network equipment (such as various network elements, access network equipment, etc.) can also be implemented by components (such as chips or circuits) that can be used in network equipment.

Above, the communication method provided by the embodiment of the present application is described in detail with reference to FIG. 2 . The foregoing communication method is mainly introduced from the perspective of interaction between various network elements. It can be understood that, in order to realize the above functions, each network element includes a corresponding hardware structure and/or software module for performing each function.

Those skilled in the art should be aware that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.

Hereinafter, the communication device provided by the embodiment of the present application will be described in detail with reference to FIG. 3 and FIG. 4 . It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments. Therefore, for content that is not described in detail, reference may be made to the method embodiments above. For brevity, some content will not be repeated here.

The embodiment of the present application can divide the functional modules of the transmitting end device or the receiving end device according to the above method example, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module middle. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. In the following, description will be made by taking the division of each functional module corresponding to each function as an example.

FIG. 3 is a schematic block diagram of an apparatus 300 provided by an embodiment of the present application. The device 300 includes a transceiver unit 310 and a processing unit 320 . The transceiver unit 310 can implement a corresponding communication function, and the processing unit 320 is used for data processing. The transceiver unit 310 may also be called a communication interface or a communication unit.

Optionally, the device 300 may further include a storage unit, which may be used to store instructions and/or data, and the processing unit 320 may read the instructions and/or data in the storage unit, so that the device implements the aforementioned method embodiments .

The apparatus 300 can be used to execute the actions performed by the network equipment (such as each network element, access network equipment, etc.) in the above method embodiments. At this time, the apparatus 300 can be a network equipment or a component that can be configured in the network equipment The transceiving unit 310 is configured to perform transceiving-related operations on the network device side in the above method embodiments, and the processing unit 320 is configured to perform processing-related operations on the network device side in the above method embodiments.

As a design, the apparatus 300 is configured to perform the actions performed by the AF in the above method embodiments.

The processing unit 320 is configured to determine a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS flow; The transceiver unit 310 is configured to send indication information to the policy control network element, where the indication information is used to indicate the scheduling priority corresponding to each type of data block, where each data block includes at least one data packet.

Optionally, the indication information is included in the quality of service QoS requirements, the QoS requirements are used to configure the parameters of the QoS flow, and the transceiver unit 310 is also used to receive a response message from the policy control network element, the response message is used to indicate The parameter configuration of the QoS flow is completed; the transceiver unit 310 is also configured to send downlink data to the user plane network element, the downlink data includes a data packet and indication information for indicating the type of the data block to which the data packet belongs.

The apparatus 300 may implement steps or processes corresponding to the AF execution method in the method embodiment according to the embodiment of the present application, and the apparatus 600 may include a unit for executing the AF execution method in the method embodiment. Moreover, each unit in the apparatus 600 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in AF in the method embodiment.

Wherein, when the device 300 is used to execute the method in FIG. 2 , the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S220, S252 and S260; the processing unit 320 can be used to execute the processing steps in the method, such as step S210.

It should be understood that the specific process for each unit to perform the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, details are not repeated here.

As another design, the apparatus 300 is configured to perform the actions performed by the PCF in the above method embodiments.

The transceiver unit 310 is configured to receive indication information from the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and the plurality of data blocks of different types The data packets in are mapped to the same QoS flow; the transceiver unit 310 is configured to send the scheduling priority corresponding to each type of data block to the session management network element.

Optionally, the transceiving unit 310 is also configured to receive a response message from the session management network element, the response message is used to indicate that the parameter configuration of the QoS flow is completed; the transceiving unit 310 is also configured to send the response to the application network element information.

The apparatus 300 may implement the steps or processes corresponding to the PCF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the PCF execution method in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in the PCF in the method embodiment.

Wherein, when the apparatus 300 is used to execute the method in FIG. 2 , the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S220, S230 and S251; the processing unit 320 can be used to execute the processing steps in the method.

As yet another design, the apparatus 300 is configured to perform the actions performed by the SMF in the above method embodiments.

The transceiver unit 310 is configured to receive the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from the policy control network element, and the data packets in the plurality of different types of data blocks are all mapped to the same In a quality of service QoS flow; the transceiver unit 310 is configured to send the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate that the user plane network element will receive The scheduling priority corresponding to the received data packet is encapsulated in the data packet, wherein each data block includes at least one data packet.

Optionally, the processing unit 320 is configured to configure the parameters of the QoS flow according to the PCC rule; the sending unit is also configured to send a response message to the policy control network element, and the response message is used to indicate that the parameter configuration of the QoS flow is completed.

Optionally, the processing unit 320 is configured to assign a scheduling priority identifier to the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, and the scheduling priority identifier is used to identify each type The scheduling priority corresponding to the data block; the sending unit is also used to send the scheduling priority identifier and corresponding relationship corresponding to each type of data block to the user plane network element, wherein the corresponding relationship includes the plurality of different types of The corresponding relationship between the scheduling priority of the data block and multiple identifiers of the scheduling priority.

Optionally, the transceiving unit 310 is further configured to send the correspondence between multiple scheduling priorities of different types of data blocks and multiple scheduling priority identifiers to the access network device.

Optionally, the transceiver unit 310 is also configured to send encapsulation information to the user plane network element, the encapsulation information is used to instruct the user plane network element to encapsulate identification information in the data packet, and the identification information is used to identify the data packet The data block it belongs to.

The apparatus 300 may implement the steps or processes corresponding to the SMF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the SMF execution method in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions mentioned above are respectively for realizing the corresponding process of the method embodiment in the SMF in the method embodiment.

Wherein, when the device 300 is used to execute the method in FIG. 2 , the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S230, S232 and S251; the processing unit 320 can be used to execute the processing steps in the method, such as step S231, S240 and S250.

As yet another design, the apparatus 300 is configured to perform actions performed by the UPF in the above method embodiments.

The transceiver unit 310 is configured to receive downlink data from the application network element, the downlink data includes a plurality of different types of data blocks, each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority, and the plurality of different types of data blocks corresponds to a scheduling priority. The data packets in the different types of data blocks are all mapped to the same QoS flow, and each of the data blocks includes at least one data packet; the processing unit 320 is used for according to the corresponding type of each data packet and the value of each type A scheduling priority corresponding to the data block determines the scheduling priority of the data packet; the user plane network element sends the data packet to the access network device, and the data packet encapsulates information indicating the scheduling priority of the data packet.

Optionally, the transceiving unit 310 is also configured to receive scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, where the encapsulation indication information is used to indicate the user plane network element to receive The scheduling priority corresponding to the data packet is encapsulated in the data packet.

Optionally, the information indicating the scheduling priority includes a scheduling priority identifier used to identify the scheduling priority, and the transceiver unit 310 is further configured to receive the scheduling priority identifier and the corresponding relationship from the session management network element, the scheduling The priority identifier is used to identify the scheduling priority corresponding to each type of data block, and the corresponding relationship includes the corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers.

Optionally, the transceiving unit 310 is further configured to receive, from the application network element, identification information of the data block to which the data packet belongs.

Optionally, the identification information is encapsulated in the data packet, and the transceiver unit 310 is further configured to receive encapsulation information from the session management network element, where the encapsulation information is used to instruct the user plane network element to encapsulate the identification information in the data packet In a packet, the identification information is used to identify the data block to which the data packet belongs.

The apparatus 300 may implement the steps or processes corresponding to the UPF execution in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the UPF execution method in the method embodiment. In addition, each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding procedures of the method embodiment in the UPF in the method embodiment.

Wherein, when the device 300 is used to execute the method in FIG. 2, the transceiver unit 310 can be used to execute the transceiver steps in the method, such as steps S260 and S290; the processing unit 320 can be used to execute the processing steps in the method, such as steps S240, S270 and S280.

As yet another design, the apparatus 300 is configured to perform the actions performed by the RAN in the above method embodiments.

The transceiver unit 310 is configured to receive a plurality of data packets from the user plane network element, each of the plurality of data packets is encapsulated with information indicating the scheduling priority corresponding to the data packet; the plurality of data packets belong to Multiple different types of data blocks, each type of data block in the multiple different types of data blocks corresponds to a scheduling priority, and the data packets in the multiple different types of data blocks are all mapped to the same quality of service QoS flow Middle; the processing unit 320 is configured to process the data packet according to the scheduling priority.

Optionally, the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority, and the transceiver unit 310 is further configured to receive scheduling priority of multiple different types of data blocks from the session management network element The corresponding relationship between a level and multiple scheduling priority identifiers.

Optionally, the data packet is also encapsulated with identification information of the data block to which the data packet belongs, and the processing unit 320 is also configured to determine whether to schedule a data block belonging to the same data block as the data packet according to the identification information. Packets other than packets.

The apparatus 300 may implement the steps or procedures corresponding to the execution of the RAN in the method embodiment according to the embodiment of the present application, and the apparatus 300 may include a unit for executing the method executed by the RAN in the method embodiment. Moreover, each unit in the apparatus 300 and other operations and/or functions described above are respectively for realizing the corresponding process of the method embodiment in the RAN in the method embodiment.

Wherein, when the apparatus 300 is used to execute the method in FIG. 2 , the transceiving unit 310 can be used to execute the transceiving steps in the method, such as steps S232 and S290; the processing unit 320 can be used to execute the processing steps in the method, such as step S291.

The processing unit 320 in the above embodiments may be implemented by at least one processor or processor-related circuits. The transceiver unit 310 may be implemented by a transceiver or transceiver-related circuits. The storage unit can be realized by at least one memory.

As shown in FIG. 4 , the embodiment of the present application further provides an apparatus 400 . The apparatus 400 includes a processor 410 and may further include one or more memories 420 . The processor 410 is coupled with the memory 420, and the memory 420 is used to store computer programs or instructions and/or data, and the processor 410 is used to execute the computer programs or instructions and/or data stored in the memory 420, so that the methods in the above method embodiments be executed. Optionally, the apparatus 400 includes one or more processors 410 .

Optionally, the memory 420 may be integrated with the processor 410, or set separately.

Optionally, as shown in FIG. 4 , the apparatus 400 may further include a transceiver 430, and the transceiver 430 is used for receiving and/or sending signals. For example, the processor 410 is configured to control the transceiver 430 to receive and/or send signals.

As a solution, the apparatus 400 is used to implement operations performed by devices (such as network elements, access network devices, etc.) in the above method embodiments.

The embodiment of the present application also provides a computer-readable storage medium, on which computer instructions for implementing the method performed by the network device (such as each network element, access network device, etc.) in the above method embodiment are stored.

For example, when the computer program is executed by a computer, the computer can implement the method performed by the network device in the foregoing method embodiments.

The embodiments of the present application also provide a computer program product containing instructions, which when executed by a computer enable the computer to implement the method performed by the network device (such as each network element, access network device, etc.) in the above method embodiment.

The embodiment of the present application also provides a communication system, the communication system includes the network devices (such as network elements, access network devices, etc.) in the above embodiments, such as access network devices and core network devices.

For explanations and beneficial effects of relevant content in any of the devices provided above, reference may be made to the corresponding method embodiments provided above, and details are not repeated here.

It should be understood that the processor mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and/or a nonvolatile memory. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. The volatile memory may be random access memory (RAM). For example, RAM can be used as an external cache. As an example and not limitation, RAM may include the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM) , double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (synchlink DRAM, SLDRAM) and Direct memory bus random access memory (direct rambus RAM, DR RAM).

It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, the memory (storage module) may be integrated in the processor.

It should also be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

Those skilled in the art can appreciate that the units and steps of each example described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Professionals may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the protection scope of the present application.

In the several embodiments provided in this application, it should be understood that the disclosed devices and methods may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to implement the solutions provided in this application.

In addition, each functional unit in each embodiment of the present application may be integrated into one unit, each unit may exist separately physically, or two or more units may be integrated into one unit.

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it 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 the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. For example, the computer may be a personal computer, a server, or a network device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, 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 such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a solid state disk (solid state disk, SSD) etc. For example, the aforementioned available medium may include But not limited to: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program codes.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A communication method, characterized in that, comprising:

The application network element determines the scheduling priority corresponding to each type of data block in multiple different types of data blocks, and the data packets in the multiple different types of data blocks are mapped to the same quality of service QoS flow;

The application network element sends indication information to the policy control network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block; the scheduling priority is used to indicate the priority of different types of data blocks Data packets are scheduled, each of said data blocks comprising at least one data packet.
The method according to claim 1, wherein the indication information is included in a quality of service (QoS) requirement, and the QoS requirement is used to configure parameters of the QoS flow, and the method further comprises:

The application network element receives a response message from the policy control network element, and the response message is used to indicate that the parameter configuration of the QoS flow is completed;

The application network element sends downlink data to the user plane network element, and the downlink data includes a data packet and indication information for indicating the type of the data block to which the data packet belongs.
The method according to claim 2, further comprising:

The application network element sends the identification information of the data block to which the data packet belongs to the user plane network element.
The method according to any one of claims 1 to 3, wherein the different types of data blocks include any of the following: data blocks of different frame types, data blocks at different positions in the user's field of view, or different types of data blocks. A data block of a hierarchy, wherein the hierarchy includes a base layer or an enhancement layer.
A communication method, characterized in that, comprising:

The policy control network element receives indication information from the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block in multiple different types of data blocks, and the multiple data blocks of different types Packets in a block are mapped to the same QoS flow;

The policy control network element sends the scheduling priority corresponding to each type of data block to the session management network element, and the scheduling priority is used to indicate to schedule data packets of different types of data blocks.
The method according to claim 5, wherein the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes a Information about the scheduling priority of the QoS flow.
The method according to claim 6, further comprising:

The policy control network element receives a response message from the session management network element, and the response message is used to indicate that the parameter configuration of the QoS flow is completed;

The policy control network element sends the response message to the application network element.
A communication method, characterized in that, comprising:

The session management network element receives the scheduling priority corresponding to each type of data block in multiple different types of data blocks from the policy control network element, and the data packets in the multiple different types of data blocks are mapped to the same Quality of service QoS flow;

The session management network element sends the scheduling priority and encapsulation indication information corresponding to each type of data block to the user plane network element, and the encapsulation indication information is used to indicate the data packets to be received by the user plane network element The corresponding scheduling priority is encapsulated in the data packet,

Wherein, each of the data blocks includes at least one data packet, and the scheduling priority is used to indicate to schedule data packets of different types of data blocks.
The method according to claim 8, wherein the scheduling priority corresponding to each type of data block is included in the policy and charging control rule PCC rule, and the PCC rule also includes a Information about the scheduling priority of the QoS flow.
The method according to claim 9, characterized in that the method further comprises:

The session management network element configures the parameters of the QoS flow according to the PCC rule;

The session management network element sends a response message to the policy control network element, where the response message is used to indicate that the parameter configuration of the QoS flow is completed.
The method according to claim 10, characterized in that the method further comprises:

The session management network element assigns a scheduling priority identifier to the scheduling priority corresponding to each type of data block among the plurality of different types of data blocks, and the scheduling priority identifier is used to identify each type of The scheduling priority corresponding to the data block;

The session management network element sends the scheduling priority identifier and corresponding relationship corresponding to each type of data block to the user plane network element,

Wherein, the corresponding relationship includes the corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers.
The method according to claim 11, characterized in that the method further comprises:

The session management network element sends the corresponding relationship between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers to the access network device.
The method according to any one of claims 9 to 12, further comprising:

The session management network element sends encapsulation information to the user plane network element, the encapsulation information is used to instruct the user plane network element to encapsulate identification information in the data packet, and the identification information is used to identify the data packet The data block it belongs to.
A communication method, characterized in that, comprising:

The user plane network element receives downlink data from the application network element, the downlink data includes a plurality of different types of data blocks, each type of data block in the plurality of different types of data blocks corresponds to a scheduling priority, and the Data packets in a plurality of different types of data blocks are mapped to the same quality of service QoS flow, and each of the data blocks includes at least one data packet;

The user plane network element determines the scheduling priority of the data packet according to the type corresponding to each data packet and the scheduling priority corresponding to each type of data block;

The user plane network element sends the data packet to the access network device, the data packet is encapsulated with information indicating the scheduling priority of the data packet, and the scheduling priority is used to indicate different types of data blocks The data packets are scheduled.
The method according to claim 14, characterized in that the method further comprises:

The user plane network element receives scheduling priority and encapsulation indication information corresponding to each type of data block from the session management network element, and the encapsulation indication information is used to indicate that the data packet received by the user plane network element corresponds to The scheduling priority is encapsulated in the packet.
The method according to claim 14 or 15, wherein the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority,

The method also includes:

The user plane network element receives the scheduling priority identifier and the corresponding relationship from the session management network element, the scheduling priority identifier is used to identify the scheduling priority corresponding to each type of data block, and the corresponding relationship includes the The corresponding relationship between the scheduling priorities of the multiple different types of data blocks and the multiple scheduling priority identifiers.
The method according to any one of claims 14 to 16, further comprising:

The user plane network element receives from the application network element the identification information of the data block to which the data packet belongs.
The method according to claim 17, wherein the identification information is encapsulated in the data packet,

The method also includes:

The user plane network element receives encapsulation information from the session management network element, the encapsulation information is used to instruct the user plane network element to encapsulate identification information in the data packet, and the identification information is used to identify the The data block to which the above packet belongs.
A communication method, characterized in that, comprising:

The access network device receives multiple data packets from the user plane network element, each of the multiple data packets is encapsulated with information indicating the scheduling priority corresponding to the data packets, and the multiple data packets belong to For multiple different types of data blocks, each type of data block in the multiple different types of data blocks corresponds to a scheduling priority, and the scheduling priority is used to indicate the scheduling of data packets of different types of data blocks , the data packets in the plurality of different types of data blocks are all mapped to the same quality of service QoS flow;

The access network device processes the data packet according to the scheduling priority.
The method according to claim 19, wherein the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority,

The method also includes:

The access network device receives the correspondences between the scheduling priorities of multiple different types of data blocks and the multiple scheduling priority identifiers from the session management network element.
The method according to claim 19 or 20, wherein the data packet is further encapsulated with identification information of the data block to which the data packet belongs, and the method further comprises:

The access network device determines whether to schedule other data packets except the data packet belonging to the same data block as the data packet according to the identification information.
A communication device, characterized by comprising:

A unit or module for performing the method as claimed in any one of claims 1 to 4.
A communication device, characterized by comprising:

A unit or module for performing the method as claimed in any one of claims 5 to 7.
A communication device, characterized by comprising:

A unit or module for performing the method as claimed in any one of claims 8 to 13.
A communication device, characterized by comprising:

A unit or module for performing a method as claimed in any one of claims 14 to 18.
A communication device, characterized by comprising:

A unit or module for performing a method as claimed in any one of claims 19 to 21.
A computer-readable storage medium, characterized in that computer instructions are stored in the computer-readable storage medium, and when the computer instructions are run on a computer, the method according to any one of claims 1 to 21 be executed.
A communication system, characterized by comprising at least one communication device as claimed in claim 22, at least one communication device as claimed in claim 23, at least one communication device as claimed in claim 24, and at least one communication device as claimed in claim 24 A communication device as claimed in claim 25 and at least one communication device as claimed in claim 26 .
A communication method, characterized in that, comprising:

The application network element determines the scheduling priority corresponding to each type of data block in multiple different types of data blocks, and the data packets in the multiple different types of data blocks are mapped to the same quality of service QoS flow;

The policy control network element receives the indication information sent by the application network element, the indication information is used to indicate the scheduling priority corresponding to each type of data block; the scheduling priority is used to indicate the priority of different types of data blocks Data packets are scheduled, each of said data blocks comprising at least one data packet.
The method according to claim 29, characterized in that the method further comprises:

The policy control network element sends the scheduling priority corresponding to each type of data block to the session management network element, and the scheduling priority is used to indicate to schedule data packets of different types of data blocks.