CN116723582A

CN116723582A - Communication method and device

Info

Publication number: CN116723582A
Application number: CN202210184934.XA
Authority: CN
Inventors: 周汉; 王丹; 魏鑫鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-02-28
Filing date: 2022-02-28
Publication date: 2023-09-08
Also published as: WO2023160116A1

Abstract

The embodiment of the application provides a communication method and a communication device, which are applied to the fields of data packet scheduling and service quality assurance. The method comprises the following steps: the application network element determines the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, wherein the data packets in the plurality of different types of data blocks are mapped to the same QoS flow, the application network element sends indication information to the policy control network element, the indication information is used for indicating the scheduling priority corresponding to each type of data block, the scheduling priority is used for indicating the scheduling of the data packets of the different types of data blocks, and each data block comprises at least one data packet. The application network element determines and issues a plurality of different scheduling priorities corresponding to the same QoS flow, so that the differentiated scheduling of the data packets of the data blocks of different types corresponding to the same QoS flow is realized, and the user experience is improved.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and more particularly, to a communication method and apparatus.

Background

In the fifth generation (5th generation,5G) system, quality of service (quality of service, qoS) flows (flows) are proposed in order to guarantee the end-to-end quality of service for traffic. For a terminal equipment (UE), when the UE has a service communication requirement, one or more Packet Data Unit (PDU) sessions may be established with the 5G network, and QoS flows of one or more bearer service data flows may be established (may also be referred to as configuration) in each PDU session.

Currently, the protocol specifies that each QoS flow is represented by a set of QoS parameters, including a 5G QoS identification (5G QoS identifier,5QI). The scheduling of the data flow takes QoS flow as granularity. Therefore, the same QoS flow cannot be differentially scheduled according to different importance of the data flow to the user experience.

Disclosure of Invention

The embodiment of the application provides a communication method, which is used for realizing differential scheduling of the same QoS flow by configuring a plurality of scheduling priorities corresponding to the same QoS flow.

In a first aspect, a communication method is provided, which may be performed by an application network element, or may also be performed by a component (e.g. a chip or a circuit) of the application network element, which is not limited, and for convenience of description, will be described below by taking an example of the implementation by the application network element.

The method comprises the following steps: the method comprises the steps that an application network element determines scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and data packets in the plurality of different types of data blocks are mapped to the same QoS flow; the application network element sends indication information to the policy control network element, where the indication information is used to indicate a scheduling priority corresponding to each type of data block, where each data block includes at least one data packet.

Based on the technical scheme, the application network element can determine the scheduling priority of the data blocks of different types corresponding to the same QoS flow, and inform the strategy control network element of the scheduling priority corresponding to each type of data block through the indication information, so that the strategy control network element can acquire that the same QoS flow has a plurality of different scheduling priorities, and the differential scheduling of the data packets of the data blocks of different types corresponding to the same QoS flow is expected to be realized.

It should be noted that, the mapping of the data packets in the plurality of different types of data blocks into the same QoS flow may be understood as:

a plurality of data blocks of different types correspond to the same quality of service QoS flow; alternatively, it is understood that a plurality of different types of data blocks are carried in the same QoS flow; or it may be further understood that the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks is 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 sending of the indication information by the application network element to the policy control network element may be that the application network element directly sends the indication information to the policy control network element, for example, the application network element sends the indication information to the policy control network element through a communication interface between the application network element and the policy control network element or through a service interface; the application network element may send the indication information to the policy control network element indirectly, for example, the application network element sends the indication information to the policy control network element through other functional network elements.

With reference to the first aspect, in certain implementations of the first aspect, the indication information is included in a quality of service, qoS, requirement for configuring parameters of the QoS flow, the method further comprising: the application network element receives a response message from the strategy control network element, wherein the response message is used for indicating that the parameter configuration of the QoS flow is completed; the application network element sends downlink data to the user plane network element, wherein the downlink data comprises a data packet and indication information for indicating the type of a data block to which the data packet belongs.

Based on the above technical solution, the application network element may carry the indication information in the QoS requirement, that is, the scheduling priority corresponding to each type of data block in the same QoS flow may be understood as a QoS requirement. The QoS requirements are used for configuring parameters of the QoS flow, and 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 application network element can start transmitting downlink data. Specifically, the downlink data includes, in addition to the data packet to be transmitted, indication information indicating the type of the data block to which the data packet belongs, so that a network element receiving the data packet determines the type of the data block to which the data packet belongs according to the indication information of the type, further determines the scheduling priority of the data packet according to the type of the data block to which the data packet belongs, and implements differential 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 certain implementations of the first aspect, the method further includes: the application network element sends the identification information of the data block to which the data packet belongs to the user plane network element.

Based on the technical scheme, 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 certain implementations of the first aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

The dividing modes of the data blocks of different types in the application can be various, so that the flexibility of the scheme is improved.

In a second aspect, a communication method is provided, which may be performed by a policy control network element, or may also be performed by a component (such as a chip or a circuit) of the policy control network element, which is not limited, and is described below as being performed by the policy control network element for convenience of description.

The communication method comprises the following steps: the method comprises the steps that a policy control network element receives indication information from an application network element, wherein the indication information is used for indicating scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and data packets in the different types of data blocks 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.

Based on the technical scheme, the application network element informs the strategy control network element of the scheduling priority corresponding to each type of data block through the indication information, so that the strategy control network element can acquire that the same QoS flow has a plurality of different scheduling priorities, and differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow is expected to be realized.

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 a policy and charging control rule PCC rule, where the PCC rule further includes information for indicating the scheduling priority of the QoS flow.

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

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the policy control network element receives a response message from the session management network element, wherein the response message is used for indicating 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 may be notified of the completion of the parameter configuration of the QoS flow through a response message, so as to facilitate the downstream data transmission by the subsequent application network element.

With reference to the second aspect, in certain implementations of the second aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

In a third aspect, a communication method is provided, which may be performed by a session management network element, or may also be performed by a component (e.g. a chip or a circuit) of the session management network element, which is not limited, and for convenience of description, will be described below with reference to the embodiment performed by the session management network element.

The communication method comprises the following steps: the method comprises the steps that a session management network element receives scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from a strategy control network element, and data packets in the different types of data blocks are mapped to the same QoS flow; the session management network element sends scheduling priority and encapsulation indication information corresponding to each type of data block to a user plane network element, wherein the encapsulation indication information is used for indicating the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet, and each data block comprises at least one data packet.

Based on the technical scheme, 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 plane network element can acquire that the same QoS stream has a plurality of different scheduling priorities, and differential scheduling of data packets of different types of data blocks corresponding to the same QoS stream is expected to be realized.

With reference to the third aspect, in some implementations of the third aspect, the scheduling priority corresponding to each type of data block is included in a policy and charging control rule PCC rule, where the PCC rule further includes information for indicating the scheduling priority of the QoS flow.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the session management network element configures 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 complete.

Based on the above technical solution, after the parameter configuration of the QoS flow is completed, the policy control network element can be notified of the completion of the parameter configuration of the QoS flow by the response message, so as to facilitate the downstream data transmission by the subsequent application network element.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the session management network element allocates a scheduling priority identifier for the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, wherein the scheduling priority identifier is used for identifying the scheduling priority corresponding to each type of data block; the session management network element sends the scheduling priority identifiers corresponding to the data blocks of each type and the corresponding relation to the user plane network element, wherein the corresponding relation comprises the scheduling priorities of the data blocks of different types and the corresponding relation of the scheduling priority identifiers.

Based on the above technical solution, the scheduling priority corresponding to each type of data block may be identified by a scheduling priority identifier, so that in order to enable the user plane network element to learn the scheduling priority corresponding to each type of data block, the scheduling priority identifier and the corresponding relationship corresponding to each type of data block may be sent to the user plane network element, so that the user plane network element determines the scheduling priorities of different types of data blocks according to the scheduling priority identifier and the corresponding relationship.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the session management network element sends the corresponding relation between the dispatching priorities of the data blocks of different types and the dispatching priority identifiers to the access network equipment.

Based on the technical scheme, the scheduling priority corresponding to each type of data block can be identified by the scheduling priority identifier, so that in order to enable the access network device to acquire the scheduling priority corresponding to each type of data block, the corresponding relation between the scheduling priorities of a plurality of different types of data blocks and the scheduling priority identifiers can be sent to the access network device, and the access network device can conveniently determine the scheduling priorities of the different types of data blocks according to the scheduling priority identifier and the corresponding relation.

With reference to the third aspect, in certain implementations of the third aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the session management network element sends encapsulation information to the user plane network element, where 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 a data block to which the data packet belongs.

In a fourth aspect, a communication method is provided, which may be performed by a user plane network element, or may also be performed by a component (such as a chip or a circuit) of the user plane network element, which is not limited, and for convenience of description, the following description will be given by taking the user plane network element as an example.

The communication method comprises the following steps: the user plane network element receives downlink data from the application network element, wherein the downlink data comprises a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, data packets of the plurality of data blocks of different types are mapped to the same QoS flow, and each data block comprises 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 one scheduling priority corresponding to each type of data block; the user plane network element sends the data packet to the access network device, and information indicating the scheduling priority of the data packet is encapsulated in the data packet.

Based on the technical scheme, the user plane network element can encapsulate the indication information of the scheduling priorities of the different data packets into the data packets, so that the access network equipment can obtain the scheduling priorities of the different data packets in the same QoS flow, and the differentiated scheduling of the data packets of the different types of data blocks corresponding to the same QoS flow is expected to be realized.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the user plane network element receives the scheduling priority and the encapsulation indication information corresponding to each type of data block from the session management network element, wherein the encapsulation indication information is used for indicating the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in 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 a plurality of different scheduling priorities.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority, and the method further includes: the user plane network element receives a scheduling priority identifier from the session management network element and a corresponding relation, wherein the scheduling priority identifier is used for identifying the scheduling priority corresponding to each type of data block, and the corresponding relation comprises the scheduling priorities of the plurality of different types of data blocks and the corresponding relation of the plurality of scheduling priority identifiers.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the user plane network element receives the identification information of the data block to which the data packet from the application network element belongs.

With reference to the fourth aspect, in some implementations of the fourth aspect, the identification information is encapsulated in the data packet, and the method further includes: the user plane network element receives encapsulation information from the session management network element, wherein the encapsulation information is used for indicating the user plane network element to encapsulate identification information in the data packet, and the identification information is used for identifying a data block to which the data packet belongs.

Based on the technical scheme, the transmission of the packet granularity is expanded into the transmission of the data block granularity through the data block identification, so that the resource waste is avoided, and the transmission efficiency is improved.

With reference to the fourth aspect, in some implementations of the fourth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

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

The communication method comprises the following steps: the access network equipment receives a plurality of data packets from a user plane network element, wherein each data packet in the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet; the data packets belong to a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, and the data packets of the plurality of data blocks of different types are mapped to the same QoS flow; and the access network equipment processes the data packet according to the scheduling priority.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority, and the method further includes: the access network device receives the corresponding relation between the dispatching priority of the data blocks of different types from the session management network element and the dispatching priority identifiers.

With reference to the fifth aspect, in some implementations of the fifth aspect, the data packet further encapsulates identification information of a data block to which the data packet belongs, and the method further includes: the access network device determines whether to schedule and schedule other data packets except the data packet in the same data block according to the identification information.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

In a sixth aspect, a communication device is provided for performing the method provided in the first aspect above.

The device comprises: a processing unit, configured to determine a scheduling priority corresponding to each of a plurality of different types of data blocks, where data packets in the plurality of different types of data blocks are mapped to the same QoS flow; and the sending unit is used for sending indication information to the strategy control network element, wherein the indication information is used for indicating the scheduling priority corresponding to each type of data block, and each data block comprises at least one data packet.

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

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

With reference to the sixth aspect, in certain implementations of the sixth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

The advantages of the method according to the above sixth aspect and possible designs thereof may be referred to the advantages of the first aspect and possible designs thereof.

In a seventh aspect, a communication device is provided for performing 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 a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, where data packets in the plurality of different types of data blocks are mapped to the same QoS flow; and the sending unit is used for sending 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 a policy and charging control rule PCC rule, where the PCC rule further includes information for indicating the scheduling priority of the QoS flow.

With reference to the seventh aspect, in certain 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 configured to indicate that the parameter configuration of the QoS flow is complete; the sending unit is further configured to send the response message to the application network element.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

The advantages of the method according to the above seventh aspect and possible designs thereof may be referred to the advantages of the second aspect and possible designs thereof.

In an eighth aspect, a communication device is provided for performing the method provided in the third aspect above.

The communication device includes: a receiving unit, configured to receive a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from a policy control network element, where data packets in the plurality of different types of data blocks are mapped to the same QoS flow; and the sending unit is used for sending the scheduling priority and the packaging indication information corresponding to each type of data block to the user plane network element, wherein the packaging indication information is used for indicating the user plane network element to package the scheduling priority corresponding to the received data packet in the data packet, and each data block comprises 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 a policy and charging control rule PCC rule, where the PCC rule further includes information for indicating the scheduling priority of the QoS flow.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the apparatus further includes: a processing unit, configured to configure parameters of the QoS flow according to the PCC rule; the sending unit is further configured to send 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 complete.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the apparatus further includes: a processing unit, configured to allocate a scheduling priority identifier to a scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, where the scheduling priority identifier is used to identify a scheduling priority corresponding to each type of data block; the sending unit is further configured to send, to a user plane network element, a scheduling priority identifier corresponding to each type of data block and a correspondence relationship, where the correspondence relationship includes a correspondence relationship between scheduling priorities of the plurality of different types of data blocks and the plurality of scheduling priority identifiers.

With reference to the eighth aspect, in some implementations of the eighth aspect, the sending unit is further configured to send, to the access network device, a correspondence between a scheduling priority of a plurality of data blocks of different types and a plurality of said scheduling priority identifiers.

With reference to the eighth aspect, in some implementations of the eighth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise 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 a user plane network element, where the encapsulation information 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 a data block to which the data packet belongs.

The advantages of the method according to the above eighth aspect and possible designs thereof may be referred to the advantages of the third aspect and possible designs thereof.

In a ninth aspect, there is provided a communication device for performing 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, where the downlink data includes a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, data packets in the plurality of data blocks of different types are mapped to the same QoS flow, and each data block includes at least one data packet; the processing unit is used for determining the scheduling priority of the data packet according to the type corresponding to each data packet and one scheduling priority corresponding to each type of data block; the user plane network element sends the data packet to the access network device, and information indicating the scheduling priority of the data packet is encapsulated in the data packet.

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, where the encapsulation indication information is used to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet.

With reference to the ninth aspect, in some implementations of the ninth aspect, the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority, and the receiving unit is further configured to receive a scheduling priority identifier from the session management network element and a corresponding relation, where the scheduling priority identifier is used to identify a scheduling priority corresponding to each type of data block, and the corresponding relation includes a scheduling priority of the plurality of different types of data blocks and a corresponding relation of the plurality of scheduling priority identifiers.

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

With reference to the ninth aspect, in some implementations of the ninth aspect, the data packet encapsulates the identification information, and the receiving unit 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, and the identification information is used to identify a data block to which the data packet belongs.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

The advantages of the method according to the above ninth aspect and possible designs thereof may be referred to the advantages of the fourth aspect and possible designs thereof.

In a tenth aspect, a communication device is provided for performing the method provided in the fifth aspect.

The communication device includes: a receiving unit, configured to receive a plurality of data packets from a user plane network element, where each data packet in the plurality of data packets encapsulates information indicating a scheduling priority corresponding to the data packet; the data packets belong to a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, and the data packets of the plurality of data blocks of different types are mapped to the same QoS flow; and the processing unit is used for processing the data packet according to the scheduling priority.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the information indicating the scheduling priority includes a scheduling priority identifier for identifying the scheduling priority, and the receiving unit is further configured to receive a correspondence between the scheduling priority of the plurality of different types of data blocks from the session management network element and the plurality of scheduling priority identifiers.

With reference to the tenth aspect, in some implementations of the tenth aspect, the data packet further encapsulates identification information of a data block to which the data packet belongs, and the processing unit is further configured to determine whether to schedule other data packets in the same data block except the data packet according to the identification information.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the different types of data blocks include any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

The advantages of the method according to the above tenth aspect and possible designs thereof may be referred to as advantages in the fifth aspect and possible designs thereof.

In an eleventh aspect, a communication device is provided, which is configured to perform the methods provided in the first to fifth aspects. In particular, the communication device may comprise means and/or modules for performing the methods provided in the first to fifth aspects.

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

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

In a twelfth aspect, the present application provides a processor for performing the method provided in the above aspects.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited by the present application.

In a thirteenth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for device execution, the program code comprising instructions for performing the method provided by any one of the implementations of the first to fifth aspects described above.

In a fourteenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method provided by any one of the implementations of the first to fifth aspects described above.

In a fifteenth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reading instructions stored on a memory through the communication interface, and executing the method provided by any implementation manner of the first aspect to the fifth aspect.

Optionally, as an implementation manner, the chip further includes a memory, where a computer program or an instruction is stored in the memory, and the processor is configured to execute the computer program or the instruction stored in the memory, and when the computer program or the instruction is executed, the processor is configured to perform a method provided in any implementation manner of the first aspect to the fifth aspect.

A sixteenth aspect provides a communication system comprising the notification apparatus of the sixth to tenth aspects.

Drawings

Fig. 1 (a) and (b) are schematic diagrams of application scenarios to which the embodiments of the present application are applied.

Fig. 2 is a schematic flow chart of a communication method provided in 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 Description

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: fifth generation (5th generation,5G) systems or New Radio (NR), long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD), and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The technical solution of the embodiment of the present application may also be applied to a device-to-device (D2D) communication, a vehicle-to-device (V2X) communication, a machine-to-machine (machine to machine, M2M) communication, a machine type communication (machine type communication, MTC), and an internet of things (internet of things, ioT) communication system or other communication systems.

To facilitate understanding of the embodiments of the present application, a communication system to which the embodiments of the present application are applicable will be briefly described with reference to (a) and (b) of fig. 1.

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

A 5G system to which the embodiment of the present application is applicable will be illustrated with reference to (a) in fig. 1 and (b) in fig. 1. It should be understood that the 5G system described herein is merely an example and should not be construed as limiting the application in any way.

It should also be understood that a service interface, or a point-to-point interface, may be used for communication between certain network elements in the 5G system, and a 5G system framework based on the point-to-point interface and a 5G system framework based on the service interface are described below in conjunction with (a) in fig. 1 and (b) in fig. 1, respectively.

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

User Equipment (UE), (radio) access network equipment (radio access network, (R) AN), access and mobility management functions (access and mobility management function, AMF) network elements, session management functions (session management function, SMF) network elements, user plane functions (user plane function, UPF) network elements, policy control functions (policy control function, PCF) network elements, unified data management (unified data management, UDM) network elements, application functions (application function, AF) network elements, data Networks (DN), network slice selection functions (network slice selection function, NSSF), authentication server functions (authentication server function, AUSF), unified data management (unified data management, UDM), capability opening functions (network exposure function, NEF) network elements, unified data storage (unified data repository, UDR), and the like.

The following briefly describes each network element shown in (a) in fig. 1:

1. UE: a terminal that is in communication with the (R) AN may also be referred to as a terminal device (terminal equipment), AN access terminal, a subscriber unit, a subscriber station, a Mobile Station (MS), a Mobile Terminal (MT), a remote station, a remote terminal, a mobile device, a subscriber terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may be a device providing voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, an in-vehicle device, etc. Currently, some examples of terminals may be: a mobile phone (mobile phone), a tablet (pad), a computer with wireless transceiver function (e.g., a notebook, a palm, etc.), a mobile internet device (mobile internet device, MID), a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in an industrial control (industrial control), a wireless terminal in an unmanned (self-drive), a wireless terminal in a telemedicine (remote medical), a wireless terminal in a smart grid (smart grid), a wireless terminal in a transportation security (transportation safety), a wireless terminal in a smart city (smart city), a wireless terminal in a smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a wireless terminal in a wearable device, a land-based device, a future-mobile terminal in a smart city (smart city), a public network (35G) or a future mobile communication device, etc.

Furthermore, the terminal device may also be a terminal device in an internet of things (Internet of things, ioT) system. IoT is an important component of future information technology development, and its main technical feature is to connect an item with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for object interconnection. IoT technology may enable massive connectivity, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

It should be understood that the terminal device may be any device that can access the network. And the terminal equipment and the access network equipment can communicate with each other by adopting a certain air interface technology.

Alternatively, the user equipment may be used to act as a base station. For example, the user equipment may act as a scheduling entity that provides side-uplink signals between user equipments in V2X or D2D, etc. For example, a cellular telephone and a car communicate with each other using side-link signals. Communication between the cellular telephone and the smart home device is accomplished without relaying communication signals through the base station.

2. (R) AN: the system is used for providing 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 the user equipment, the service requirements and the like.

The (R) AN can manage radio resources, provide access services for the ue, and further complete forwarding of control signals and ue data between the ue and the core network.

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 device includes, but is not limited to: an evolved Node B (eNB), a radio network controller (radio network controller, RNC), a Node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a home base station (home evolved Node B, heNB, or home Node B, HNB), a Base Band Unit (BBU), an Access Point (AP) in a wireless fidelity (wireless fidelity, WIFI) system, a wireless relay Node, a wireless backhaul Node, a transmission point (transmission point, TP), or a transmission reception point (transmission and reception point, TRP), etc., may also be 5G, e.g., NR, a gNB in a system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or may also be a network Node constituting a gNB or a transmission point, e.g., a baseBand unit (BBU), or a Distributed Unit (DU), etc.

In some deployments, the gNB may include a Centralized Unit (CU) and DUs. The gNB may also include an active antenna unit (active antenna unit, AAU). The CU implements part of the functionality of the gNB and the DU implements part of the functionality of the gNB. For example, the CU is responsible for handling non-real time protocols and services, implementing the functions of the radio resource control (radio resource control, RRC), packet data convergence layer protocol (packet data convergence protocol, PDCP) layer. The DUs are responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (radio link control, RLC), medium access control (media access control, MAC) and Physical (PHY) layers. The AAU realizes part of physical layer processing function, radio frequency processing and related functions of the active antenna. Since the information of the RRC layer may eventually become information of the PHY layer or be converted from the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, may also be considered to be transmitted by the DU or by the du+aau. It is understood that the access network device may be a device comprising one or more of a CU node, a DU node, an AAU node. In addition, the CU may be divided into access network devices in an access network (radio access network, RAN), or may be divided into access network devices in a Core Network (CN), which is not limited by the present application.

3. User plane network element: quality of service (quality of service, qoS) handling for packet routing and forwarding, user plane data, etc.

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

4. Data network: for providing a network for transmitting data.

In future communication systems, the data network may still be a DN, or may have other names, and the present application is not limited thereto.

In a 5G communication system, a protocol data unit (protocol data unit, PDU) session may be established after a terminal device accesses a network, and an application function network element (e.g., an application server) deployed in the DN may be interacted with by accessing the DN through the PDU session. As shown in fig. 1 (a), depending on the DN accessed by the user, the network may select the UPF accessing the DN as a PDU session anchor (PDU Session Anchor, PSA) according to the network policy and access the application function network element through the N6 interface of the PSA.

5. Access and mobility management network element: the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions besides session management, such as legal interception, access authorization/authentication and the like, in the functions of the mobility management network element (mobility management entity, MME).

As shown in (a) of fig. 1, in the 5G communication system, the access management network element may be an AMF network element. In future communication systems, the access management network element may still be an AMF network element, or may have other names, which is not limited by the present application.

6. Session management network element: the method is mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of the terminal equipment, terminal node selecting manageable terminal equipment plane functions, strategy control and charging function interfaces, downlink data notification and the like.

As shown in fig. 1 (a), 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, and an anchor session management function (anchor session management function, a-SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which is not limited by the present application.

7. Policy control network element: a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (e.g., AMF, SMF network elements, etc.), and the like.

In a 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) of fig. 1, in the 5G communication system, the policy control network element may be a PCF network element. In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which is not limited by the present application.

8. Data management network element: the method is used for processing the terminal equipment identification, access authentication, registration, mobility management and the like.

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

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

9. Application function network element: the application function network element can interact with the 5G system through the application function network element and is used for accessing the network open function network element or interacting with the policy framework to perform policy control and the like.

As shown in (a) of fig. 1, in the 5G communication system, the application function network element may be application function, AF network element. In future communication systems, the application function network element may still be an AF network element, or may have other names, which is not limited by the present application.

10. Network slice selection network element: mainly comprises the following functions: selecting a set of network slice instances for the UE, determining allowed network slice selection assistance information (network slice selection assistance information, NSSAI), and determining a set of AMFs that can serve the UE, etc.

As shown in (a) of fig. 1, in the 5G communication system, the network slice selection network element may be an NSSF network element. In future communication systems, the network slice selection network element may still be an NSSF network element, or may have other names, which is not limited by the present application.

11. Authentication service network element: the method is used for realizing the bidirectional authentication of the terminal equipment by the authentication service and the generation of the secret key, and supports a unified authentication framework.

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

12. Network element with open function: for providing network-open customization functionality.

As shown in fig. 1 (a), in the 5G communication system, the network element with the network open function may be a network open function (network exposure function, NEF) network element, and in a future communication system, the network element with the network open function may still be a NEF network element, or may have other names, which is not limited by the present application.

The 5G communication system may also open 5GC supported capabilities, such as providing small data transfer capabilities, etc., to external application function network elements through the NEF network elements.

It will be appreciated that the network elements or functions described above may be either network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). The network elements or functions may be divided into one or more services, and further, services that exist independently of the network functions may also occur. In the present application, an instance of the above-described function, or an instance of a service included in the above-described function, or an instance of a service existing independently of a network function may be referred to as a service instance.

Further, the AF network element may be abbreviated as AF, the NEF network element may be abbreviated as NEF, and the AMF network element may be abbreviated as AMF. Namely, the AF described later in the 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 will be appreciated that the network elements or functional network elements described above may be either network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). The network elements or functions may be divided into one or more services, and further, services that exist independently of the network functions may also occur. In the present application, an instance of the above-described function, or an instance of a service included in the above-described function, or an instance of a service existing independently of a network function may be referred to as a service instance.

As can be seen from fig. 1 (a), the interfaces between the individual control plane network elements in fig. 1 (a) are point-to-point interfaces.

In the architecture shown in fig. 1 (a), the interface names and functions between the network elements are as follows:

1) N1: the interface between the AMF and the terminal may be used to deliver QoS control rules, etc. to the terminal.

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

3) N3: the interface between the RAN and the UPF is mainly used for transmitting uplink and downlink user plane data between the RAN and the UPF.

4) N4: the interface between SMF and UPF can be used to transfer information between control plane and user plane, including control plane-oriented forwarding rule, qoS control rule, flow statistics rule, etc. and user plane information reporting.

5) N5: the interface between AF and PCF can be used for application service request issue and network event report.

6) N6: and the interface of the UPF and the DN is used for transmitting uplink and downlink user data streams between the UPF and the DN.

7) N7: the interface between PCF and SMF may be used to deliver protocol data unit (protocol data unit, PDU) session granularity and traffic data flow granularity control policies.

8) N8: the interface between the AMF and the UDM can be used for the AMF to acquire subscription data and authentication data related to access and mobility management from the UDM, register current mobility management related information of the terminal from the AMF to the UDM, and the like.

9) N9: the user interface between UPF and UPF is used to transfer the uplink and downlink user data flow between UPF.

10 N10): the interface between the SMF and the UDM may be used for the SMF to obtain session management related subscription data from the UDM, and the SMF registers current session related information of the terminal to the UDM.

11 N11), N11: the interface between the SMF and the AMF may be used to convey PDU session tunnel information between the RAN and the UPF, control messages sent to the terminal, radio resource control information sent to the RAN, etc.

12 N12): the interface between the AMF and the AUSF can be used for initiating an authentication flow to the AUSF by the AMF, wherein the authentication flow can carry SUCI as a subscription identifier;

13 N13): the interface between the UDM and the AUSF may be used for the AUSF to obtain the user authentication vector from the UDM to execute the authentication procedure.

As an exemplary illustration, fig. 1 (b) shows a schematic architecture diagram of a 5G system 200b to which an embodiment of the present application is applicable. Fig. 1 (b) is a schematic diagram of a 5G network architecture based on a server interface. As shown in (b) of fig. 1, the network architecture may include, but is not limited to, the following network elements (alternatively referred to as 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.

The description of the functions of the network elements may refer to the description of the functions of the corresponding network elements in (b) in fig. 1, which is not repeated. The main difference between (b) in fig. 1 and (a) in fig. 1 is that: the interfaces between the individual control plane network elements in (b) in fig. 1 are served interfaces, and the interfaces between the individual control plane network elements in (a) in fig. 1 are point-to-point interfaces.

Nnssf, nudr, nausf, nnef, namf, npcf, nsmf, nudm, naf in fig. 1 (b) provides service interfaces for NSSF, UDR, AUSF, NEF, AMF, PCF, SMF, UDM and AF, respectively, for invoking corresponding service operations. N1, N2, N3, N4, and N6 are interface serial numbers. The meaning of these interface serial numbers may be found in the third generation partnership project (3rd generation partnership project,3GPP) standard protocol, and is not limited herein.

It should be understood that the network architecture to which the above embodiments of the present application can be applied is only an exemplary illustration, and the network architecture to which the embodiments of the present application are applicable is not limited to this, and any network architecture including the functions capable of implementing the respective network elements described above is applicable to the embodiments of the present application.

It should also be understood that AMF, SMF, UPF, PCF, NEF shown in fig. 1 (a) or fig. 1 (b), etc. can be understood as network elements for implementing different functions, for example, can be combined into network slices as required. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform), where the specific form of the network elements is not limited by the present application.

It should also be understood that the above designations are merely intended to facilitate distinguishing between different functions and should not be construed as limiting the application in any way. The application does not exclude the possibility of using other designations in 5G networks as well as in other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

It should also be understood that the names of interfaces between the network elements in fig. 1 (a) or fig. 1 (b) are only an example, and the names of interfaces in the specific implementation may be other names, which are not specifically limited by the present application. Furthermore, the names of the transmitted messages (or signaling) between the various network elements described above are also merely an example, and do not constitute any limitation on the function of the message itself.

It should be understood that the method provided by the embodiment of the present application may be applied to a 5G communication system, for example, a communication system shown in fig. 1 (a) or fig. 1 (b). However, the embodiment of the present application is not limited to the scenario where the method can be applied, and for example, other network architectures including network elements capable of implementing corresponding functions are equally applicable. Also for example, the6th generation (6G) system architecture, etc. In addition, the names of the network elements used in the embodiments of the present application may remain the same in future communication systems, but the names may change.

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

1. PDU session: an association between the terminal device and a Data Network (DN) is provided for providing a PDU connection service.

2. QoS flow mechanism: the QoS flows are specified in the current standards as minimum QoS control granularity, each QoS flow having a corresponding QoS configuration.

QoS parameters included in QoS configuration describe specific QoS requirements, and QoS parameters mainly include:

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

Further, 5QI in QoS parameters is a set of QoS feature combination indexes, and QoS features include:

resource type (resource type), priority Level (PL), packet delay budget (packet delay budget, PDB), packet error rate (packet error rate, PER), statistics period (scheduling window), and maximum burst data amount (maximum data burst volume), etc.

Wherein, the resource types include: non-minimum guaranteed rate (non guaranteed bit rate, non-GRB), minimum guaranteed rate (guaranteed bit rate, GRB), delay-sensitive GRB (delay-critical GBR); the maximum burst data size is a delay sensitive GRB specific parameter. The PDB is used to represent the upper limit of the transmission delay from the UE to the UPF, and the PDBs of the uplink and downlink data are the same. PER represents the upper bound for packet loss rate. PL is used to indicate that when PDBs that cannot meet multiple QoS flows, qoS requirements with high priority (e.g., small PL values) are preferentially met, e.g., in case of congestion, when one or more QoS flows cannot meet all QoS requirements, qoS flows may be prioritized according to priority level.

5QI is a scalar used to index into the corresponding 5G QoS feature. The 5 QIs are classified into standardized 5 QIs, preconfigured 5 QIs and dynamically allocated 5 QIs. For standardized 5QI, one-to-one correspondence with a set of standardized 5G QoS feature values; for the preconfigured 5QI, the corresponding 5G QoS characteristic value is preconfigured on the access network element, and for the dynamically allocated 5QI, the corresponding 5G QoS characteristic is sent to the access network element by the core network device through a QoS file (QoS profile).

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

ARP contains priority, preemption capability and preempted capability.

GFBR represents the bit rate that is desired to be provided to guaranteed bit rate (guaranteed bit rate, GBR) QoS flows.

MFBR limits the bit rate provided to GBR QoS flow, i.e., the maximum bit rate provided to GBR QoS flow. If the bit rate is exceeded, the data packet may be discarded.

Specifically, the standard defines a portion of the QoS feature values of 5QI, which can be used directly, and also allows operators and/or device manufacturers to allocate non-conflicting 5QI and preset corresponding QoS feature values for use in the operator network.

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

3. QoS model: in order to guarantee the end-to-end quality of service of a service, a QoS model based on QoS flows (flows) is proposed. The QoS model supports guaranteed bit rate QoS flows (i.e., GBR QoS flows) and non-guaranteed bit rate QoS flows (i.e., non-GBR QoS flows). Data packets using the same QoS flow control receive the same transmission process (e.g., scheduling, admission threshold, etc.). For a terminal device, one or more data connection sessions (such as PDU sessions) may be established with the network; data flows corresponding to one or more QoS flows may be transmitted in each data connection session. Each QoS flow is identified by a QoS flow identifier (QoS flow identifier, QFI), which uniquely identifies a QoS flow in the same data connection session. In addition, each QoS flow corresponds to one data radio bearer (data radio bearer, DRB), and one DRB may correspond to one or more QoS flows.

One of the QoS flows is GBR QoS flow or Non-GBR QoS flow, and is determined by a 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. The GBR QoS flows are determined as GRB QoS flows requiring notification control (notification control) and GBR QoS flows not requiring notification control according to whether the QoS file contains QNC. For GBR QoS flows requiring notification control, 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 (i.e., the QoS flow resource corresponding to GBR QoS flow cannot be satisfied). Further SMFs may initiate QoS flow deletion or QoS flow modification procedures (e.g., modify QoS parameters of QoS flows).

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

4. PL: the priority of the scheduling resource in the QoS Flow is indicated, and the priority can be used for identifying the QoS Flow corresponding to the data Flow of the same UE, and can also be used for identifying the QoS flows corresponding to the data flows of different UEs. In the case of congestion, where the current resources cannot support one or more QoS flows to meet the corresponding QoS requirements (e.g., PDB, PER, etc.) cannot be met, PL is used to select which QoS flows to meet the corresponding QoS requirements preferentially.

5. General packet radio service tunneling protocol-user plane (general packet radio service tunnelling protocol user, GTP-U) tunnel: in the PDU session establishment process, the connection between the RAN and the UPF can use a GTP-U tunnel, and data from the UE side or data sent to the UE side is added into the tunnel for transmission.

6. Tunnel endpoint identification (Tunnel Endpoint Identifier, TEID): a tunnel segment between two network elements may be uniquely determined for the tunnel endpoint of the GTP-U protocol.

7. User experience (Quality of Experience, qoE): qoE is often the most intuitive and effective measure in Extended Reality (XR) services. For example, qoE may be embodied in that the importance of data flows transmitted in the same QoS flow to the user experience is likely not the same, e.g., I-frames are more important than P-frames, centrally located in the field of view than at the edges of the field of view, base layer data is more important than enhancement layer data, etc.

From the above description of QoS parameters for current QoS flow, it is known that: each QoS flow is only expressed by a set of QoS parameters, and one QoS flow has only one parameter such as 5QI, that is, only one scheduling priority, when the network is blocked and the QoS requirements of all data flow transmission cannot be guaranteed, different data flows cannot be scheduled differently according to the difference of the importance degree of the data flows to the QoE, for example, how to realize the priority scheduling of the data flows with high importance degree to the QoE, and after the QoS requirements of the data flow transmission are met, the data flows with low importance degree to the QoE are scheduled again, so that the differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow is realized.

In order to solve the defects of the current data flow scheduling, the application provides a communication method, which is used for configuring multiple scheduling priorities for different types of data packets mapped by one QoS flow so as to realize the differentiated scheduling of the data packets of different types of data blocks corresponding to a single QoS flow.

The scenario in which the embodiment of the present application can be applied is described above in conjunction with (a) in fig. 1 and (b) in fig. 1, and the defects existing in the current data stream scheduling method are briefly described, and the basic concept involved in the present application is also briefly described, and the communication method provided by the present application will be described in detail below in conjunction with the accompanying drawings.

The embodiments shown below are not particularly limited to the specific structure of the execution body of the method provided by the embodiment of the present application, as long as the communication can be performed by the method provided according to the embodiment of the present application by running the program recorded with the code of the method provided by the embodiment of the present application, and for example, the execution body 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 the program and execute the program.

In order to facilitate understanding of the embodiments of the present application, the following description is made.

First, in the present application, "for indicating" may be understood as "enabling" which may include direct enabling and indirect enabling. When describing that a certain information is used to enable a, it may be included that the information directly enables a or indirectly enables a, and does not necessarily represent that a is carried in the information.

In the specific implementation process, the information to be enabled may be enabled in various ways, for example, but not limited to, the information to be enabled may be directly enabled, such as the information to be enabled itself or an index of the information to be enabled. The information to be enabled may also be indirectly enabled by enabling other information, where an association exists between the other information and the information to be enabled. 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, the enabling of specific information may also be implemented by means of a pre-agreed (e.g., protocol-specified) arrangement sequence of the respective information, thereby reducing the enabling overhead to some extent. And meanwhile, the universal parts of the information can be identified and enabled uniformly, so that the enabling expense caused by independently enabling the same information is reduced.

Second, the first, second, and various numerical numbers (e.g., "#1", "#2", etc.) shown in the present application are for convenience of description only, and are not intended to limit the scope of the embodiments of the present application. For example, distinguishing between different messages, etc. Rather than to describe a particular order or sequence. It is to be understood that the objects so described may be interchanged under appropriate circumstances so as to be able to describe aspects other than the embodiments of the application.

Third, in the present application, "pre-configuration" may include pre-definition, e.g., protocol definition. Where "predefined" may be implemented by pre-storing corresponding codes, tables, or other means that may be used to indicate relevant information in the device (e.g., including the respective network elements), the application is not limited to a specific implementation thereof.

Fourth, references to "save" in embodiments of the present application may refer to saving in one or more memories. The one or more memories may be provided separately or may be integrated in an encoder or decoder, processor, or communication device. The one or more memories may also be provided separately in part, and integrated in the decoder, processor, or communication device. The type of memory may be any form of storage medium, and the application is not limited in this regard.

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

Sixth, the "protocol" referred to in the embodiments of the present application may refer to a standard protocol in the field of communications, and may include, for example, a 5G protocol, a New Radio (NR) protocol, and related protocols applied in future communication systems, which is not limited in this aspect of the present application.

In the following, the method for communication provided by the embodiment of the present application will be described in detail by taking interaction between network elements as an example without losing generality.

For convenience of description, the following description will take an access network device as RAN, a mobility management function network element as AMF, an application function network element as AF, a session management function network element as SMF, a user plane function network element as UPF, and a terminal as UE as an example.

The name of the device is not limited in the present application.

Fig. 2 is a schematic flow chart of a communication method according to an embodiment of the present application, including the following steps:

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

In particular, the plurality of different types of data blocks may be two or more different types of data blocks. The type of data block involved in the embodiments of the present application may be a frame type such as I-frame, P-frame, B-frame, etc. The type of data block may also be indicative of a user field of view location, such as a center location, an edge location. The type of data block may also indicate the level to which the data block corresponds, such as a base layer, enhancement layer, etc.

Wherein hierarchically different data blocks can be understood as: the data blocks are different, for example, some are to ensure that the basic video can be played smoothly, but the definition may not be high, and these are the base layers; some are responsible for enhancement, so that the definition of the image is better, more details are provided, and the user experience is better, which belong to the enhancement layer.

It should be appreciated that the types of data blocks described above are merely examples. The protection scope of the present application is not limited in any way, and the data blocks may be classified in other ways, for example, original stream, error correction stream, etc. This is not illustrated here. The embodiment of the application does not limit the types of the data blocks of different types, particularly for what reason. For example, it may be that the AF arbitrarily indicates that two data blocks are different types of data blocks, which differ in scheduling priority.

Illustratively, a plurality of different types of data blocks respectively correspond to different scheduling priorities. For example, the I-frames and the P-frames are different types of data blocks, and the scheduling priority corresponding to the I-frames is higher than the scheduling priority corresponding to the P-frames; for example, the scheduling priority corresponding to the data block located at the center of the user field of view is higher than the scheduling priority corresponding to the data block located at the edge of the user field of view; 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, the AF may determine that different types of data blocks correspond to different scheduling priorities according to the configuration information.

As another possible implementation, 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, 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 above manner of determining the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks by the AF is merely an example, and the scope of the present application is not limited in any way. In the embodiment of the application, how the AF determines the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks is not limited.

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

The above-mentioned data packets in a plurality of data blocks of different types are all mapped into the same QoS flow, which can be understood as:

a plurality of data blocks of different types correspond to the same quality of service QoS flow; alternatively, it is understood that a plurality of different types of data blocks are carried in the same QoS flow; or may be further understood as that a plurality of different scheduling priorities corresponding to a plurality of different 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.

Further, after the AF determines the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, the configuration of the scheduling priority corresponding to each type of data block may be implemented by the indication information via the control plane, and the method flow shown in fig. 2 further includes:

s220, the AF sends indication information to the PCF.

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

As one possible implementation, the AF sending the indication information to the PCF may be that the AF sends the indication information directly to the PCF, e.g., the AF sends the indication information to the PCF through a communication interface (e.g., N5) between the AF and the PCF or through a serviced interface (e.g., naf and Npcf).

As another possible implementation, the AF sending the indication information to the PCF may be that the AF indirectly sends the indication information to the PCF, e.g., the AF sends the indication information to the PCF through other functional network elements (e.g., NEF, etc.).

Specifically, the indication information is used to indicate the scheduling priority corresponding to each type of data block, which may be understood as that the AF sends the indication information to the PCF, and the indication information indicates a plurality of scheduling priorities corresponding to a plurality of different types of data blocks respectively.

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

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

It should be noted that the foregoing is merely illustrative of possible manners in which the AF sends the indication information to the PCF, and the scope of the present application is not limited in any way. In the embodiment of the application, no limitation is made on how the AF sends the indication information to the PCF.

Further, after the PCF receives the indication information, the PCF may send the scheduling priority corresponding to each type of data block to the SMF, and the method flow shown in fig. 2 further includes:

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

The PCF may send the scheduling priority corresponding to each type of data block to the SMF, by sending a plurality of scheduling priorities corresponding to a plurality of different types of data blocks, and a mapping relationship, where the mapping relationship includes a mapping relationship between the plurality of different types of data blocks and the plurality of scheduling priorities.

For example, in the case where the AF indicates the scheduling priority corresponding to each type of data block through the above-mentioned 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, where the scheduling priority #1 is higher than the scheduling priority #2.

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

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

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

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

For convenience of distinction, the scheduling priority of differentiated scheduling of data packets of different types of data blocks corresponding to the same QoS flow (i.e., the scheduling priority corresponding to each type of data block described above) may be referred to as a first scheduling priority; the scheduling priority of the present QoS flow may be referred to as a second scheduling priority.

As a possible implementation, the above-mentioned second scheduling priority may be included in the PCC rule. Specifically, the first scheduling priorities are in the QoS flows, one second scheduling priority is responsible for comparing the external scheduling priorities, the second scheduling priorities are compared with other QoS flows, and after determining the scheduling priorities among QoS flows, the scheduling priorities of different types of data packets in the QoS flows are determined by the first scheduling priorities.

As another possible implementation, the above-mentioned second scheduling priority may not be included in the PCC rule. The PCC rule includes a plurality of first scheduling priorities, and since the scheduling priority determination rules are the same, the plurality of first scheduling priorities need to consider the scheduling priorities among QoS flows at the same time, which is equivalent to if the first scheduling priority is qfi#12packet 1 (scheduling priority is 1) and qfi#1packet 2 (scheduling priority is 3), but the scheduling priority of another QoS flow is qfi#2packet 1 (scheduling priority is 2), then the scheduling order is qfi#1packet 1, qfi#2packet 1, and qfi#1packet 2. In this case the second scheduling priority may not be included in the PCC rule.

Further, after the SMF receives the PCC rule, the UPF configuration is performed, and the method flow shown in fig. 2 further includes:

s240, the SMF configures UPF.

The SMF configuration UPF in this embodiment includes: and the SMF sends encapsulation indication information to the UPF, wherein the encapsulation indication information is used for indicating the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet.

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

It should be understood that, in order to implement that the UPF encapsulates the scheduling priority corresponding to the received data packet in the data packet, the SMF needs to send the scheduling priority corresponding to each type of data block to the UPF in the process of configuring the UPF, so that the UPF determines the scheduling priority of the data packet after receiving the data packet.

As a possible implementation manner, the SMF may send, to the UPF, a scheduling priority corresponding to each type of data block, by sending a plurality of scheduling priorities corresponding to a plurality of different types of data blocks, respectively, and a mapping relationship, where the mapping relationship includes a mapping relationship between the plurality of different types of data blocks and the plurality of scheduling priorities.

As another possible implementation manner, the SMF sends the scheduling priority corresponding to each type of data block to the UPF, which may be implemented by sending the scheduling priority identifier corresponding to each type of data block and a correspondence relationship, where the correspondence relationship includes a correspondence relationship between the scheduling priorities of the plurality of different types of data blocks and a plurality of the scheduling priority identifiers. In this implementation, the SMF needs to assign a scheduling priority identifier to a scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, and the method flow shown in fig. 2 further includes:

S231, the SMF allocates a scheduling priority identification.

The scheduling priority identification is used for identifying the scheduling priority corresponding to each type of data block.

Specifically, in the case where the SMF allocates a scheduling priority identifier, the SMF may notify the RAN of a correspondence between scheduling priorities of a plurality of different types of data blocks and a plurality of scheduling priority identifiers, and in this implementation, the method flow shown in fig. 2 may further include:

s232, the SMF sends the correspondence to the RAN.

The correspondence is used to indicate a correspondence of a scheduling priority of a plurality of different types of data blocks and a plurality of said scheduling priority identifications.

Optionally, the SMF configuration UPF in this embodiment may further include: the SMF also transmits encapsulation information to the UPF, wherein the encapsulation information is used for indicating the user plane network element to encapsulate identification information in the data packet, and the identification information is used for identifying a data block to which the data packet belongs.

Alternatively, the package indication information and the package information may be one indication information or a plurality of 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; alternatively, the identification information may be encapsulated in the payload of the data packet, which is not limited in this regard by the present application.

After completing the above-mentioned UPF configuration, the SMF configures QoS flow parameters according to the received PCC rule, and the method flow shown in fig. 2 further includes:

s250, SMF configures parameters of QoS flow.

The SMF configures parameters of QoS flow based on the above-described plurality of different scheduling priorities. It is understood that the one QoS flow corresponds to a plurality of scheduling priorities. The parameters for configuring QoS flow may be understood as policies for configuring QoS flow.

Illustratively, the SMF configures parameters of QoS flows (also referred to as policies), which may also be referred to as SMF sends the parameters of QoS flows to the UPF, RAN and/or UE:

the first step: the SMF determines QoS flow information (also referred to as QoS policy) from the PCC rule sent by the PCF.

And a second step of: the SMF issues corresponding QoS policies to the UPF, RAN, and UE, respectively. For example, the SMF sends a first QoS policy to the UPF, the SMF sends a second QoS policy to the RAN, and the SMF sends a third QoS policy to the UE.

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

The SMF sends a second QoS policy to the RAN comprising: the SMF transmits a QoS file (profile) to the RAN through the AMF.

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

Further, after the UE, the RAN and the UPF receive the parameters of the QoS flow, the RAN establishes a DRB of the air interface according to the QoS file, and stores the QoS flow in an optional binding relationship with the DRB.

It should be understood that the above flow simply illustrates the parameter of the SMF configured QoS flow, and the protection scope of the present application is not limited in any way, and the flow of configuring the parameter of the QoS flow may refer to the description of the parameter of the QoS flow at present, which is not repeated in the present application.

Further, after the parameter configuration of the QoS flow is completed, the AF may be notified by a response message to facilitate the AF to perform downlink data transmission, and the method flow shown in fig. 2 further 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 complete.

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

Specifically, after receiving the response message, the AF knows that the parameter configuration of the QoS flow is completed, and can transmit downlink data; or the AF performs downlink data transmission in response to the response message, the method flow shown in fig. 2 further includes:

S260, the AF sends downlink data to the UPF.

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

For example, 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, whether the data block is an I frame or a P frame; also for example, indicating whether the data block is a data block located in the center of the user's field of view or a data block located at the edge of the user's field of view; as another example, whether the data block is a base layer data block or an enhancement layer data block is indicated.

As a possible implementation, the data packet and the indication information for indicating the type of the data block to which the data packet belongs may be transmitted separately, e.g. the data packet and the type indication information are two separate cells, which are included in the same message.

As another possible implementation manner, the data packet and the indication information for indicating the type of the data block to which the data packet belongs may be transmitted simultaneously, for example, the type indication information is encapsulated in a header of the data packet, and is used for indicating the type of the data block to which the data packet belongs.

In the present application, the information name is not limited, and for example, the type indication information may be referred to as first indication information, or the like.

Optionally, the downlink data may further include identification information of a data block to which the data packet belongs. The identification information of the data block includes, but is not limited to, identification (ID) of the data block, attribute information of the data block, and the like, which can be used to identify the data block.

The identification information of the data block and the data packet and the type indication information described above may be included in the same message, for example. For example, the application network element sends a message to the user plane network element, where the message includes a data packet, type indication information for indicating a 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, the scheduling priority of the data packet may be determined according to the configuration of the SMF (refer to the description in step S240), the received data packet, and the type indication information, and the method flow shown in fig. 2 further includes:

s270, the UPF determines the scheduling priority of the packet.

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

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

s280, packaging the data packet by UPF.

As one possible implementation, the UPF encapsulation packet includes: the UPF encapsulates the scheduling priority of the data packet in the data packet.

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

As another possible implementation, the UPF encapsulation packet includes: the UPF encapsulates a schedule priority identification identifying the schedule priority in a data packet.

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

Optionally, when the downlink data includes identification information of a data block to which the data packet belongs, the UPF encapsulation data packet includes: the UPF encapsulates identification information of a data block to which the data packet belongs in the data packet.

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

After the UPF finishes encapsulating the packet, the UPF may send the encapsulated packet to the RAN, where the method flow shown in fig. 2 further includes:

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

Illustratively, the UPF sends GTP-U packets to the RAN.

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

s291, the RAN processes the data packet.

Specifically, the RAN processes the data packet including the following steps one to four:

step one: the RAN decapsulates the data packet and determines the scheduling priority of the data packet.

For example, the RAN determines the scheduling priority of a data packet (e.g., GTP-U header) according to information encapsulated in the data packet that indicates the scheduling priority corresponding to the data packet.

As a possible implementation manner, the scheduling priority corresponding to the data packet is encapsulated in the data packet, and after the RAN decapsulates the data packet, the scheduling priority corresponding to the data packet may be obtained.

As another possible implementation manner, the scheduling priority identifier of the scheduling priority corresponding to the data packet is encapsulated in the data packet, after the RAN decapsulates the data packet, the RAN obtains the scheduling priority identifier of the scheduling priority corresponding to the data packet, and further determines the scheduling priority corresponding to the data packet according to the correspondence relationship received from the SMF (see description of step S232 above).

Optionally, in the case that the data packet (e.g., GTP-U header) encapsulates the identification information of the data block to which the data packet belongs, the RAN further performs step two described below.

Step two: the RAN decapsulates the data packet and determines identification information of the data block to which the data packet belongs.

After determining the scheduling priority of the data packet or determining the scheduling priority of the data packet and the identification information of the data block to which the data packet belongs, the RAN may perform QoS processing according to the scheduling priority of the data packet and other parameters (for example, 5QI specified in the current protocol) for mapping the QoS flow of the data packet; alternatively, in the case of determining the identification information of the data block to which the data packet belongs, the processing manner of the data packet having the same identification information may be determined according to the identification information of the data block to which the data packet belongs, including determining the schedule of the data packet having the same identification information.

Step three: the RAN schedules the data packets.

It will be appreciated that QoS processing of a packet in this embodiment requires consideration of the scheduling priority of the packet in addition to other parameters of the QoS flow mapping the packet (e.g., qoS parameters specified in the current protocol) in comparison to the QoS flow mechanism specified in the current protocol. The scheduling priority of the data packet may be understood as one QoS parameter, which is a new QoS parameter.

Illustratively, when the RAN receives multiple packets (e.g., packet #1, packet #2, and packet # 3) that map to the same QoS flow. The scheduling priorities corresponding to the plurality of data packets are different, for example, the scheduling priority #1 corresponding to the data packet #1, the scheduling priority #2 corresponding to the data packet #2, and the scheduling priority #3 corresponding to the data packet #3, wherein the scheduling priority #1 is higher than the scheduling priority #2, and the scheduling priority #2 is higher than the scheduling priority #3. The RAN processing the data packets includes: and sending each data packet according to the scheduling priority corresponding to each data packet. For example, the data packet #1 is scheduled (or transmitted) preferentially, then the data packet #2 is scheduled, and finally the data packet #3 is scheduled, so as to implement differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow.

Optionally, in the case that the data packet (for example, GTP-U header) encapsulates the identification information of the data block to which the data packet belongs, the RAN processes the data packet further includes:

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

Also for example, the RAN has successfully received some of the data packets in a certain data block, and the RAN may schedule resources in advance for other data packets of the same data block to which the successfully received data packet belongs, which may reduce the delay of data packet transmission to some extent.

The RAN performs resource scheduling on the data packet, which may be understood as allocating a use resource for the data packet, and priority scheduling may be understood as allocating RAN related resources to the data packet preferentially according to the QoS requirement of the data packet, so that the data packet may be successfully sent. Further, the RAN may send the received data packet to the UE, performing step four.

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

It should be noted that, the foregoing only illustrates the differential scheduling of the data packets of different types of data blocks corresponding to the same QoS flow by using the downlink data as an example, after the different scheduling priority configuration in the same QoS flow is completed for the uplink data transmission (after step S252 described above), when the terminal device determines to send the uplink data packet, the QoS flow is determined according to the QoS rule, in order to implement the differential scheduling of the data packets of different types of data blocks corresponding to the same QoS flow, before sending the uplink data packet, the terminal device informs, through a physical uplink control channel (Physical Uplink Control Channel, PUCCH), the access network device that the uplink data packet needs to be sent, and needs to simultaneously notify the type of the data block to which the uplink data packet belongs, and the uplink scheduler allocates resources (size, location, etc.) possibly allocated by the different data block types to the terminal device, so as to implement the differential scheduling of the data packets of different types of data blocks corresponding to the same QoS flow of the uplink data.

It should be understood that the specific example shown in fig. 2 in the embodiments of the present application is only for helping those skilled in the art to better understand the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application. It should be further understood that the sequence numbers of the above processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic of the processes, and should not be construed as limiting the implementation process of the embodiments of the present application.

It is also to be understood that in the various embodiments of the application, where no special description or logic conflict exists, the terms and/or descriptions between the various embodiments are consistent and may reference each other, and features of the various embodiments may be combined to form new embodiments in accordance with their inherent logic 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 embodiments of the present application are not limited to specific forms of network elements. For example, network elements that can achieve the same function in the future are suitable for use in the embodiments of the present application.

It will be appreciated that in the foregoing embodiments of the methods and operations implemented by a network device (e.g., a respective network element, an access network device, etc.), the methods and operations may also be implemented by a component (e.g., a chip or circuit) that may be used in the network device.

The communication method provided by the embodiment of the application is described in detail above with reference to fig. 2. The above communication method is mainly described in terms of interaction between the network elements. It will be appreciated that each network element, in order to implement the above-described functions, includes corresponding hardware structures and/or software modules that perform each function.

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

The following describes in detail the communication device provided in the embodiment of the present application with reference to fig. 3 and 4. It should be understood that the descriptions of the apparatus embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details not shown may be referred to the above method embodiments, and for the sake of brevity, some parts of the descriptions are omitted.

The embodiment of the application can divide the function modules of the transmitting end equipment or the receiving end equipment according to the method example, for example, each function module can be divided corresponding to each function, and two or more functions can be integrated in one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation. The following description will take an example of dividing each functional module into corresponding functions.

Fig. 3 is a schematic block diagram of an apparatus 300 provided by an embodiment of the present application. The apparatus 300 comprises a transceiver unit 310 and a processing unit 320. The transceiver unit 310 may implement a corresponding communication function, and the processing unit 320 is configured to perform data processing. The transceiver unit 310 may also be referred to as a communication interface or a communication unit.

Optionally, the apparatus 300 may further include a storage unit, where the storage unit 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 apparatus implements the foregoing method embodiments.

The apparatus 300 may be configured to perform actions performed by network devices (such as each network element, access network device, etc.) in the above method embodiment, where the apparatus 300 may be a network device or a component that may be configured in a network device, the transceiver unit 310 is configured to perform operations related to transceiver on a network device side in the above method embodiment, and the processing unit 320 is configured to perform operations related to processing on a network device side in the above method embodiment.

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

A processing unit 320, configured to determine a scheduling priority corresponding to each of a plurality of different types of data blocks, where data packets in the plurality of different types of data blocks are mapped to the same QoS flow; and a transceiver unit 310, configured to send indication information to the policy control network element, where the indication information is used to indicate a 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 a quality of service QoS requirement, the QoS requirement being used for configuring parameters of the QoS flow, and the transceiver unit 310 is further configured to receive a response message from the policy control network element, where the response message is used for indicating that parameter configuration of the QoS flow is completed; the transceiver unit 310 is further configured to send downlink data to the user plane network element, where the downlink data includes a data packet and indication information for indicating a type of a data block to which the data packet belongs.

The apparatus 300 may implement steps or processes corresponding to AF execution in method embodiments according to embodiments of the present application, and the apparatus 600 may include means for performing the method of AF execution in method embodiments. And, each unit in the apparatus 600 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method embodiment in the AF in the method embodiment.

When the apparatus 300 is used for performing the method in fig. 2, the transceiving unit 310 may be used for performing transceiving steps in the method, such as steps S220, S252 and S260; the processing unit 320 may be used to perform the processing steps in the method, as in step S210.

It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

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

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

Optionally, the transceiver unit 310 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 transceiver unit 310 is further configured to send the response message to the application network element.

The apparatus 300 may implement steps or flows corresponding to those performed by the PCF in the method embodiment according to the present application, and the apparatus 300 may include means for performing the method performed by the PCF in the method embodiment. And, each unit in the apparatus 300 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method embodiment in the PCF in the method embodiment.

When the apparatus 300 is used for performing the method in fig. 2, the transceiving unit 310 may be used for performing transceiving steps in the method, such as steps S220, S230 and S251; the processing unit 320 may be used to perform 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 method embodiments above.

A transceiver unit 310, configured to receive a scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from a policy control network element, where data packets in the plurality of different types of data blocks are mapped to the same QoS flow; and a transceiver unit 310, configured to send, to a user plane network element, scheduling priority and encapsulation indication information corresponding to each type of data block, where the encapsulation indication information is configured to instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet, and each data block includes at least one data packet.

Optionally, a processing unit 320 is configured to configure parameters of the QoS flow according to the PCC rule; the sending unit is further configured to send 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 complete.

Optionally, the processing unit 320 is configured to allocate a scheduling priority identifier to a scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, where the scheduling priority identifier is used to identify a scheduling priority corresponding to each type of data block; the sending unit is further configured to send, to a user plane network element, a scheduling priority identifier corresponding to each type of data block and a correspondence relationship, where the correspondence relationship includes a correspondence relationship between scheduling priorities of the plurality of different types of data blocks and the plurality of scheduling priority identifiers.

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

Optionally, the transceiver unit 310 is further configured to send encapsulation information to a user plane network element, where 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 a data block to which the data packet belongs.

The apparatus 300 may implement steps or processes corresponding to those performed by the SMF in the method embodiment according to the present application, and the apparatus 300 may include a unit for performing the method performed by the SMF in the method embodiment. And, each unit in the apparatus 300 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method embodiment in the SMF in the method embodiment.

When the apparatus 300 is used for performing the method in fig. 2, the transceiving unit 310 may be used for performing transceiving steps in the method, such as steps S230, S232 and S251; the processing unit 320 may be used to perform the processing steps in the method, as in steps S231, S240 and S250.

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

A transceiver unit 310, configured to receive downlink data from an application network element, where 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, data packets in the plurality of different types of data blocks are mapped to the same QoS flow, and each data block includes at least one data packet; a processing unit 320, configured to determine a scheduling priority of the data packet according to a type corresponding to each data packet and a scheduling priority corresponding to each type of data block; the user plane network element sends the data packet to the access network device, and information indicating the scheduling priority of the data packet is encapsulated in the data packet.

Optionally, the transceiver unit 310 is further 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 instruct the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet.

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 a scheduling priority identifier from the session management network element and a corresponding relationship, where the scheduling priority identifier is used to identify a scheduling priority corresponding to each type of data block, and the corresponding relationship includes a corresponding relationship of the scheduling priorities of the plurality of different types of data blocks and the plurality of scheduling priority identifiers.

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

Optionally, the data packet encapsulates the identification information, 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, and the identification information is used to identify a data block to which the data packet belongs.

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

When the apparatus 300 is used for performing the method in fig. 2, the transceiving unit 310 may be used for performing transceiving steps in the method, as shown in steps S260 and S290; the processing unit 320 may be used to perform the processing steps in the method, as in steps S240, S270 and S280.

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

A transceiver 310, configured to receive a plurality of data packets from a user plane network element, where each data packet in the plurality of data packets encapsulates information indicating a scheduling priority corresponding to the data packet; the data packets belong to a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, and the data packets of the plurality of data blocks of different types are mapped to the same QoS flow; and a processing unit 320, 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 a correspondence between the scheduling priority of the plurality of different types of data blocks from the session management network element and a plurality of the scheduling priority identifiers.

Optionally, the data packet further encapsulates identification information of a data block to which the data packet belongs, and the processing unit 320 is further configured to determine whether to schedule other data packets in the same data block except the data packet according to the identification information.

The apparatus 300 may implement steps or flows corresponding to those performed by the RAN in the method embodiment according to the present application, and the apparatus 300 may include means for performing the method performed by the RAN in the method embodiment. And each unit in the apparatus 300 and the other operations and/or functions described above are respectively for implementing the corresponding flow of the method embodiment in the RAN in the method embodiment.

When the apparatus 300 is used for performing the method in fig. 2, the transceiving unit 310 may be used for performing transceiving steps in the method, as shown in steps S232 and S290; the processing unit 320 may be used to perform the processing steps in the method, 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 memory unit may be implemented by at least one memory.

As shown in fig. 4, an embodiment of the present application further provides an apparatus 400. The apparatus 400 includes a processor 410 and may also include one or more memories 420. Processor 410 is coupled to memory 420, memory 420 for storing computer programs or instructions and/or data, and processor 410 is for executing the computer programs or instructions and/or data stored by memory 420, such that the methods in the above method embodiments are performed. Optionally, the apparatus 400 includes one or more processors 410.

Alternatively, the memory 420 may be integrated with the processor 410 or provided separately.

Optionally, as shown in fig. 4, the apparatus 400 may further comprise a transceiver 430, the transceiver 430 being used for receiving and/or transmitting signals. For example, the processor 410 is configured to control the transceiver 430 to receive and/or transmit signals.

As an aspect, the apparatus 400 is configured to implement operations performed by devices (e.g., respective network elements, access network devices, etc.) in the above method embodiments.

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

For example, the computer program, when executed by a computer, enables the computer to implement the method performed by the network device in the method embodiments described above.

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

The embodiment of the application also provides a communication system, which comprises the network equipment (such as each network element, access network equipment and the like) in the embodiment, such as the access network equipment and core network equipment.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

It should be appreciated that the processors referred to in embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. 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 referred to in embodiments of the present application may be volatile memory and/or nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM may include the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

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

It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

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

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to realize the scheme provided by the application.

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable medium may include, but is not limited to, a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk or an optical disk, etc. various media that can store program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

an application network element determines the scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, wherein the data packets in the plurality of different types of data blocks are mapped to the same QoS flow;

the application network element sends indication information to the strategy 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 scheduling of data packets of different types of data blocks, and each data block comprises at least one data packet.

2. The method of claim 1, wherein the indication information is included in a quality of service, qoS, requirement for configuring parameters of the QoS flow, the method further comprising:

The application network element receives a response message from the strategy control network element, wherein the response message is used for indicating that the parameter configuration of the QoS flow is completed;

the application network element sends downlink data to the user plane network element, wherein the downlink data comprises a data packet and indication information for indicating the type of a data block to which the data packet belongs.

3. The method according to claim 2, wherein the method further comprises:

and the application network element sends the identification information of the data block to which the data packet belongs to the user plane network element.

4. A method according to any one of claims 1 to 3, wherein the different types of data blocks comprise any one of: data blocks of different frame types, data blocks in different locations of the user's view, or data blocks of different levels, wherein the levels comprise a base layer or an enhancement layer.

5. A method of communication, comprising:

the method comprises the steps that a policy control network element receives indication information from an application network element, wherein the indication information is used for indicating scheduling priority corresponding to each type of data block in a plurality of different types of data blocks, and data packets in the plurality of different types of data blocks 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, wherein the scheduling priority is used for indicating to schedule the data packets of the data blocks of different types.

6. The method of claim 5, wherein the scheduling priority for each type of data block is included in a policy and charging control rule, PCC rule, the PCC rule further comprising information indicating the scheduling priority for the QoS flow.

7. The method of claim 6, wherein the method further comprises:

the policy control network element receives a response message from the session management network element, wherein the response message is used for indicating that the parameter configuration of the QoS flow is completed;

and the strategy control network element sends the response message to the application network element.

8. A method of communication, comprising:

the method comprises the steps that a session management network element receives scheduling priority corresponding to each type of data block in a plurality of different types of data blocks from a strategy control network element, wherein data packets in the data blocks of the different types are mapped into the same QoS flow;

the session management network element sends the scheduling priority and the encapsulation indication information corresponding to each type of data block to the user plane network element, the encapsulation indication information is used for indicating the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet,

Wherein each data block comprises at least one data packet, and the scheduling priority is used for indicating scheduling of the data packets of the data blocks of different types.

9. The method of claim 8, wherein the scheduling priority for each type of data block is included in a policy and charging control rule PCC rule, the PCC rule further including information indicating the scheduling priority for the QoS flow.

10. The method according to claim 9, wherein the method further comprises:

the session management network element configures 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 parameter configuration of the QoS flow is completed.

11. The method according to claim 10, wherein the method further comprises:

the session management network element allocates a scheduling priority identifier for the scheduling priority corresponding to each type of data block in the plurality of different types of data blocks, wherein the scheduling priority identifier is used for identifying the scheduling priority corresponding to each type of data block;

the session management network element sends the scheduling priority identification and the corresponding relation corresponding to each type of data block to the user plane network element,

The corresponding relation comprises the corresponding relation between the scheduling priority of the data blocks of different types and the scheduling priority identifiers.

12. The method of claim 11, wherein the method further comprises:

and the session management network element sends the corresponding relation between the scheduling priorities of the data blocks of different types and the scheduling priority identifiers to the access network equipment.

13. 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, wherein the encapsulation information is used for indicating the user plane network element to encapsulate identification information in the data packet, and the identification information is used for identifying a data block to which the data packet belongs.

14. A method of communication, comprising:

the user plane network element receives downlink data from the application network element, wherein the downlink data comprises a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to a scheduling priority, data packets of the plurality of data blocks of different types are mapped to the same QoS (quality of service) flow, and each data block comprises 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 access network equipment, wherein the data packet is encapsulated with information indicating the scheduling priority of the data packet, and the scheduling priority is used for indicating to schedule the data packets of different types of data blocks.

15. The method of claim 14, wherein the method further comprises:

the user plane network element receives the scheduling priority and the encapsulation indication information corresponding to each type of data block from the session management network element, wherein the encapsulation indication information is used for indicating the user plane network element to encapsulate the scheduling priority corresponding to the received data packet in the data packet.

16. The method according to claim 14 or 15, wherein the information indicating the scheduling priority comprises a scheduling priority identification for identifying the scheduling priority,

the method further comprises the steps of:

the user plane network element receives a scheduling priority identifier from the session management network element and a corresponding relation, wherein the scheduling priority identifier is used for identifying the scheduling priority corresponding to each type of data block, and the corresponding relation comprises the scheduling priorities of the plurality of different types of data blocks and the corresponding relation of the plurality of scheduling priority identifiers.

17. The method according to any one of claims 14 to 16, further comprising:

and the user plane network element receives the identification information of the data block to which the data packet from the application network element belongs.

18. The method of claim 17, wherein the data packet is encapsulated with the identification information,

the method further comprises the steps of:

the user plane network element receives encapsulation information from the session management network element, wherein the encapsulation information is used for indicating the user plane network element to encapsulate identification information in the data packet, and the identification information is used for identifying a data block to which the data packet belongs.

19. A method of communication, comprising:

an access network device receives a plurality of data packets from a user plane network element, wherein each data packet in the plurality of data packets is encapsulated with information indicating a scheduling priority corresponding to the data packet, the plurality of data packets belong to a plurality of data blocks of different types, each data block of the plurality of data blocks of different types corresponds to one scheduling priority, the scheduling priority is used for indicating to schedule the data packet of the data block of different type, and the data packets in the data blocks of different types are mapped to the same QoS flow;

And the access network equipment processes the data packet according to the scheduling priority.

20. The method of claim 19, wherein the information indicating the scheduling priority comprises a scheduling priority identification for identifying the scheduling priority,

the method further comprises the steps of:

the access network device receives the corresponding relation between the dispatching priority of the data blocks of different types from the session management network element and the dispatching priority identifiers.

21. The method according to claim 19 or 20, wherein the data packet further encapsulates identification information of a data block to which the data packet belongs, the method further comprising:

and the access network equipment determines whether to schedule and judge whether the data packet belongs to other data packets except the data packet in the same data block according to the identification information.

22. A communication device, comprising:

a unit or module for performing the method as claimed in any one of claims 1 to 4.

23. A communication device, comprising:

a unit or module for performing the method as claimed in any one of claims 5 to 7.

24. A communication device, comprising:

A unit or module for performing the method as claimed in any one of claims 8 to 13.

25. A communication device, comprising:

a unit or module for performing the method as claimed in any one of claims 14 to 18.

26. A communication device, comprising:

a unit or module for performing the method as claimed in any one of claims 19 to 21.

27. A computer readable storage medium having stored therein computer instructions which, when run on a computer, perform the method of any of claims 1 to 21.

28. A communication system comprising at least one communication device according to claim 22, at least one communication device according to claim 23, at least one communication device according to claim 24, at least one communication device according to claim 25 and at least one communication device according to claim 26.