CN116887341A

CN116887341A - Communication method, communication device and communication system

Info

Publication number: CN116887341A
Application number: CN202210313833.8A
Authority: CN
Inventors: 周汉; 王丹; 魏鑫鹏
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-28
Filing date: 2022-03-28
Publication date: 2023-10-13
Also published as: WO2023185769A1

Abstract

The application discloses a communication method, a communication device and a communication system, relates to the field of communication, and is used for realizing dynamic adjustment of QoS parameters of QoS flows so as to improve user experience. The communication method comprises the following steps: the session management function network element obtains first parameter information for one quality of service QoS flow, the first parameter information including: a first set of QoS parameters of the QoS flow, the first set of QoS parameters corresponding to the first type of information, and a second set of QoS parameters corresponding to the second type of information; the first type information is used for indicating a first data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow; the session management function network element sends second parameter information for the QoS flow to the access network device, the second parameter information comprising the first set of QoS parameters and the second set of QoS parameters.

Description

Communication method, communication device and communication system

Technical Field

The present application relates to the field of communications, and in particular, to a communication method, a communication device, and a communication system.

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 one or more QoS flows carrying the service data flows may be established (may also be referred to as configuration) in each PDU session.

The QoS requirements (e.g., bandwidth requirements) of the service are embodied on QoS parameters of QoS flows of bearer services, and the QoS requirements of the same service are not always unchanged, so if the data packets mapped to the QoS flows are scheduled by always adopting the same QoS parameters, time-frequency resource waste or time-frequency resource shortage is easily caused, and user experience is affected.

Disclosure of Invention

The embodiment of the application provides a communication method, a communication device and a communication system, which are used for realizing dynamic adjustment of QoS parameters of QoS flows so as to improve user experience.

In order to achieve the above purpose, the embodiment of the present application adopts the following technical scheme:

in a first aspect, a communication method is provided, including: the session management function network element obtains first parameter information for one quality of service QoS flow, wherein the first parameter information comprises: a first set of QoS parameters of the QoS flow, the first set of QoS parameters corresponding to the first type of information, and a second set of QoS parameters corresponding to the second type of information; the first type information is used for indicating a first data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow; the session management function network element sends second parameter information for the QoS flow to the access network device, the second parameter information comprising the first set of QoS parameters and the second set of QoS parameters.

According to the communication method provided by the embodiment of the application, the session management function network element configures two groups of QoS parameters of one QoS flow to the access network equipment, so that the access network equipment adopts one group of QoS parameters to schedule the data packet mapped to the QoS flow, and the QoS parameters of the QoS flow are dynamically regulated, thereby improving the user experience.

In one possible implementation, the first data packet scheduled with the first set of QoS parameters and the second data packet scheduled with the second set of QoS parameters may be different types of data packets for the same data flow or may be different types of data packets for different data flows.

In one possible embodiment, the method further comprises: the session management function network element sends configuration information for QoS flow to the user plane function network element, wherein the configuration information comprises first type information and/or second type information; the first type information and the second type information sent to the user plane function network element are used for: the user plane function network element instructs the access network device to schedule either a first data packet mapped to the QoS flow with the first set of QoS parameters or a second data packet mapped to the QoS flow with the second set of QoS parameters.

In one possible implementation, the configuration information further includes: the first identification information corresponding to the first type information and/or the second identification information corresponding to the second type information, wherein the first identification information is different from the second identification information. The first identification information and the second identification information are used for: the user plane function network element instructs the access network device to schedule either a first data packet mapped to the QoS flow with the first set of QoS parameters or a second data packet mapped to the QoS flow with the second set of QoS parameters.

In one possible implementation, the second parameter information further includes: the first identification information and/or the second identification information. The technical effects are the same as the above.

In one possible implementation, the configuration information further includes: the first QoS parameter in the first group of QoS parameters and/or the second QoS parameter in the second group of QoS parameters are different values of the same QoS parameter. The first QoS parameter and the second QoS parameter are for: the user plane function network element instructs the access network device to schedule either a first data packet mapped to the QoS flow with the first set of QoS parameters or a second data packet mapped to the QoS flow with the second set of QoS parameters.

In a possible embodiment, the second parameter information further comprises a first type of information and/or a second type of information. The first type information and the second type information are used for: the user plane function network element instructs the access network device to schedule either a first data packet mapped to the QoS flow with the first set of QoS parameters or a second data packet mapped to the QoS flow with the second set of QoS parameters.

In a possible embodiment, the second parameter information further comprises default parameter information indicating which of the first set of QoS parameters and the second set of QoS parameters is the default set of QoS parameters. In this way, before the access network device receives the parameter change indication information from the user plane function network element for the first time, a default set of QoS parameters is adopted to schedule the data packet mapped to one QoS flow, and then each time the access network device receives the parameter change indication information from the user plane function network element, the access network device switches the set of QoS parameters between the first set of QoS parameters and the second set of QoS parameters to schedule the data packet mapped to the QoS flow.

In one possible implementation, the first type information and the second type information are frame types, or packet data unit set types. Taking the first type information and the second type information as frame types as examples, the first type information may refer to I frames, and the second type information may be P frames.

In a second aspect, a communication method is provided, which includes: the user plane function network element receives configuration information aiming at a QoS flow from the session management function network element, wherein the configuration information comprises first type information and/or second type information; the first type information is used for indicating a first data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow; the user plane function network element receives the data packet mapped to the QoS flow; the user plane function network element sends parameter indication information for the QoS flow to the access network device according to the type information of the data packet mapped to the QoS flow, wherein the parameter indication information is used for indicating the access network device to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters or schedule a second data packet mapped to the QoS flow by adopting a second group of QoS parameters.

In the communication method provided by the embodiment of the application, the session management function network element configures two types of information aiming at one QoS flow to the user plane function network element, the user plane function network element identifies which set of QoS parameters of two sets of QoS parameters corresponding to the two types of information is suitable for the data packet mapped to the QoS flow, and notifies the access network equipment, so that the access network equipment adopts one set of QoS parameters to schedule the data packet mapped to the QoS flow, and the QoS parameters of the QoS flow are dynamically regulated, thereby improving user experience.

In one possible implementation, if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information instructs the access network device to schedule the first data packet mapped to the QoS flow using the first set of QoS parameters; alternatively, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information instructs the access network device to schedule the second data packet mapped to the QoS flow using the second set of QoS parameters. The user plane function network element may instruct the access network device to schedule the first data packet mapped to the QoS flow using the first set of QoS parameters or schedule the second data packet mapped to the QoS flow using the second set of QoS parameters by identifying the type information of the data packet mapped to the QoS flow.

In one possible implementation, the configuration information further includes: first identification information corresponding to the first type information (i.e., corresponding to the first set of QoS parameters) and/or second identification information corresponding to the second type information (i.e., corresponding to the second set of QoS parameters), the first identification information being different from the second identification information; if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first identification information; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second identification information. Namely, the user plane function network element indicates by the self-defined identification information: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In one possible implementation, if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first type information; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second type information. I.e. the user plane function network element is indicated by the type information: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In one possible implementation, the configuration information further includes: a first QoS parameter in the first group of QoS parameters and/or a second QoS parameter in the second group of QoS parameters, wherein the first QoS parameter and the second QoS parameter are different values of the same QoS parameter; if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first QoS parameter; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second QoS parameter. I.e. the user plane functional network element indicates by different values of the same QoS parameter: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In one possible implementation manner, if the type information of the current data packet mapped to the QoS flow received by the user plane functional network element is different from the type information of the previous data packet mapped to the QoS flow, the parameter indication information is parameter change indication information, where the parameter change indication information is used to instruct the access network device to schedule the current data packet using another set of QoS parameters different from the previous set of QoS parameters, where the previous set of QoS parameters refers to a set of QoS parameters for scheduling the previous data packet; the previous set of QoS parameters and the other set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters. I.e. the parameter change indication information is used to instruct the access network device to switch a set of QoS parameters between a first set of QoS parameters and a second set of QoS parameters to schedule a data packet mapped to the QoS flow.

In one possible implementation, the parameter indication information is carried in a header of a data packet mapped to the QoS flow. Such as a general packet radio service tunneling protocol-user plane (general packet radio service tunnelling protocol user, GTP-U) header.

In a third aspect, a communication method is provided, including: the access network equipment receives second parameter information for one quality of service (QoS) flow from a session management function network element, wherein the second parameter information comprises a first group of QoS parameters and a second group of QoS parameters of the QoS flow; the access network equipment receives parameter indication information aiming at the QoS flow from a user plane functional network element, wherein the parameter indication information is used for indicating the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters or schedule a second data packet mapped to the QoS flow by adopting a second group of QoS parameters; the access network device schedules a first data packet mapped to the QoS flow with a first set of QoS parameters or a second data packet mapped to the QoS flow with a second set of QoS parameters according to the parameter indication information.

In the communication method provided by the embodiment of the application, the session management function network element configures two groups of QoS parameters of one QoS flow to the access network equipment, the user plane function network element identifies which group of QoS parameters the data packet mapped to the QoS flow is suitable for and notifies the access network equipment, and the access network equipment adopts one group of QoS parameters indicated by the user plane function network element to schedule the data packet mapped to the QoS flow, so that the QoS parameters of the QoS flow are dynamically regulated, and the user experience is improved.

In one possible implementation, the access network device schedules a first data packet mapped to the QoS flow with a first set of QoS parameters or a second data packet mapped to the QoS flow with a second set of QoS parameters according to the parameter indication information, including: if the parameter indication information indicates that the access network equipment adopts the first group of QoS parameters to schedule the first data packet mapped to the QoS flow, the access network equipment adopts the first group of QoS parameters to schedule the first data packet mapped to the QoS flow; alternatively, if the parameter indication information indicates that the access network device schedules a second data packet mapped to the QoS flow using a second set of QoS parameters, the access network device schedules a second data packet mapped to the QoS flow using the second set of QoS parameters.

In one possible implementation, the second parameter information further includes: the first identification information corresponding to the first group of QoS parameters and/or the second identification information corresponding to the second group of QoS parameters; the parameter indication information is first identification information or second identification information; if the parameter indication information is first identification information, the first identification information indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; or if the parameter indication information is second identification information, the second identification information indicates the access network device to schedule a second data packet mapped to the QoS flow using a second set of QoS parameters. Namely, the user plane function network element indicates by the self-defined identification information: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In a possible embodiment, the second parameter information further comprises a first type of information and/or a second type of information; the first type information is used for indicating the data packets which are scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating the data packets which are scheduled by adopting a second group of QoS parameters in the QoS flow; the parameter indication information is first type information or second type information; if the parameter indication information is the first type information, the first type information indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; alternatively, if the parameter indication information is a second type of information, the second type of information indicates to the access network device to schedule a second data packet mapped to the QoS flow with a second set of QoS parameters. I.e. the user plane function network element is indicated by the type information: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In one possible implementation, the parameter indication information is a first QoS parameter in the first set of QoS parameters, or a second QoS parameter in the second set of QoS parameters, the first QoS parameter and the second QoS parameter being different values of the same QoS parameter; if the parameter indication information is a first QoS parameter, the first QoS parameter indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; or if the parameter indicating information is a second QoS parameter, the second QoS parameter indicates the access network device to schedule a second data packet mapped to the QoS flow using the second set of QoS parameters. I.e. the user plane functional network element indicates by different values of the same QoS parameter: the access network device schedules a first data packet mapped to the QoS flow using a first set of QoS parameters or schedules a second data packet mapped to the QoS flow using a second set of QoS parameters.

In one possible implementation, the parameter indication information is parameter change indication information, where the parameter change indication information is used to instruct the access network device to schedule the current data packet mapped to the QoS flow using another set of QoS parameters different from the previous set of QoS parameters, where the previous set of QoS parameters refers to a set of QoS parameters that schedule the previous data packet mapped to the QoS flow; the first set of QoS parameters and the other set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters; the access network device adopts the first group of QoS parameters or the second group of QoS parameters to schedule the data packet mapped to the QoS flow according to the parameter indication information, and comprises the following steps: the access network device schedules the current data packet with another set of QoS parameters. I.e. the parameter change indication information is used to instruct the access network device to switch a set of QoS parameters between a first set of QoS parameters and a second set of QoS parameters to schedule a data packet mapped to the QoS flow.

In one possible implementation, the parameter indication information is carried in a header of a data packet mapped to the QoS flow. Such as a GTP-U header.

In a fourth aspect, a communication method is provided, including: the core network element acquires first parameter information aiming at a QoS flow, wherein the first parameter information comprises a second value of QoS parameters of the QoS flow; the second value is used for indicating that the QoS parameter is changed from the first value to the second value, and the first value is different from the second value; the core network element sends the first parameter information to the access network device to indicate that when the preset condition is met, the access network device adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow. The core network element may be a session management function network element, an application function network element, a user plane function network element, or a network element formed by combining the user plane function network element and the mobile edge platform.

The embodiment of the application provides a communication method, wherein a core network element indicates access network equipment to adopt a second value scheduling of QoS parameters to map to a data packet of a QoS flow, and when a preset condition is met, the first value scheduling of the QoS parameters is adopted to map to the data packet of the QoS flow, so that the QoS parameters of the QoS flow are dynamically regulated, and the user experience is improved.

In a possible implementation manner, the first parameter information further includes a duration of the second value, or the second value of the QoS parameter is used to schedule the total data amount of the data packet mapped to the QoS flow; the total data volume is used for combining the second value to obtain the duration of the second value; meeting the preset condition means that the access network device adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow for reaching the duration. For example, dividing the total data amount by the target bandwidth may result in a second valued duration of the QoS parameter. And after the data packet mapped to the QoS flow reaches the duration time in the first parameter information, the access network equipment adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible embodiment, the method further comprises: the core network element sends monitoring indication information to the user plane functional network element, wherein the monitoring indication information is used for indicating the user plane functional network element to monitor the flow of the data packet of the QoS flow in the preset time, and when the flow of the data packet of the QoS flow in the preset time is changed from being higher than a threshold to being lower than the threshold or from being lower than the threshold to being higher than the threshold, the user plane functional network element sends recovery indication information to the access network equipment, and the recovery indication information is used for indicating the access network equipment to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter; the condition meeting the preset condition means that the access network equipment receives the recovery indication information. At this time, the core network element is not a user plane function network element, for example, the core network element is a session management function network element, so that after receiving the recovery instruction information from the user plane function network element, the access network device adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible embodiment, the method further comprises: the core network element monitors the flow of data packets of QoS flow within preset time; when the flow of the data packet of the QoS flow changes from higher than the threshold to lower than the threshold or from lower than the threshold to higher than the threshold in the preset time, the core network element sends recovery indication information to the access network equipment, wherein the recovery indication information is used for indicating the access network equipment to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter; the condition meeting the preset condition means that the access network equipment receives the recovery indication information. The core network element is a user plane function network element. After receiving the recovery instruction information from the user plane function network element, the access network device adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible embodiment, the method further comprises: the core network element receives parameter change request information from user equipment, wherein the parameter change request information is used for requesting to change QoS parameters of QoS flow; and the core network element obtains a second value of the QoS parameter according to the parameter change request information. The core network element may be an application function network element or a network element in which a user plane function network element and a mobile edge platform are combined.

In one possible implementation, the parameter change request information includes an event that occurs to change a QoS parameter of the QoS flow. The core network element determines a second value of the QoS parameter (e.g., the target bandwidth) based on the event.

In one possible implementation, the parameter change request information includes a second value of the QoS parameter (e.g., the target bandwidth).

In one possible implementation, the first parameter information sent to the access network device is carried in a header of a data packet mapped to the QoS flow. Such as a GTP-U header.

In a fifth aspect, a communication method is provided, including: the access network device adopts a first value of QoS parameter of a quality of service QoS flow to schedule the data packet mapped to the QoS flow; the access network equipment receives first parameter information aiming at the QoS flow, wherein the first parameter information comprises a second value of the QoS parameter; the second value is used for indicating that the QoS parameter is changed from the first value to the second value, and the first value is different from the second value; the access network equipment adopts a second value of the QoS parameter to schedule the data packet mapped to the QoS flow; when the preset condition is met, the access network equipment adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible implementation, the first parameter information further includes: a second valued duration, or a second valued scheduling of the total data amount of data packets mapped to the QoS flow using the QoS parameter; wherein the total data amount is used in combination with the second score for the duration; meeting the preset condition means that the access network device adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow for reaching the duration. For example, dividing the total data amount by the target bandwidth may result in a second valued duration of the QoS parameter. And after the data packet mapped to the QoS flow reaches the duration time in the first parameter information, the access network equipment adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible embodiment, the method further comprises: the access network device receiving recovery indication information from the user plane function network element when the preset condition is met, wherein the recovery indication information is used for indicating the access network device to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter. After receiving the recovery instruction information from the user plane function network element, the access network device adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

In one possible implementation, the first parameter information is carried in a header of a data packet mapped to the QoS flow. Such as a GTP-U header.

In a sixth aspect, there is provided a communications device comprising a processor and a transceiver for communicating with other communications devices, the method of the first aspect and any of its embodiments being performed when the processor executes instructions.

In a seventh aspect, there is provided a communications device comprising a processor and a transceiver for communicating with other communications devices, the method of the second aspect and any embodiment thereof being performed when the processor executes instructions.

In an eighth aspect, there is provided a communications device comprising a processor and a transceiver for communicating with other communications devices, the method of the third aspect and any of its embodiments being performed when the processor executes instructions.

In a ninth aspect, there is provided a communications device comprising a processor and a transceiver for communicating with other communications devices, the method of the fourth aspect and any of its embodiments being performed when the processor executes instructions.

In a tenth aspect, there is provided a communications device comprising a processor and a transceiver for communicating with other communications devices, the method of the fifth aspect and any of its embodiments being performed when the processor executes instructions.

In an eleventh aspect, a communication apparatus is provided that includes a processing module and a transceiver module. The processing module is used for acquiring first parameter information for one quality of service QoS flow. The transceiver module is configured to send second parameter information for the QoS flow to the access network device.

In a possible implementation, the transceiver module 202 is configured to send configuration information for QoS flows to the user plane functional network element.

In a twelfth aspect, a communication device is provided that includes a transceiver module. The receiving and transmitting module is used for receiving configuration information aiming at one QoS flow from the session management function network element; receiving a data packet mapped to a QoS flow; and sending parameter indication information for the QoS flow to the access network equipment according to the type information of the data packet mapped to the QoS flow.

In a thirteenth aspect, a communication device is provided that includes a transceiver module. The receiving and transmitting module is used for receiving second parameter information for one QoS flow from the session management function network element; receiving parameter indication information for QoS flow from user plane function network element; according to the parameter indication information, a first data packet mapped to the QoS flow is scheduled by using a first set of QoS parameters or a second data packet mapped to the QoS flow is scheduled by using a second set of QoS parameters.

In one possible implementation, if the parameter indication information indicates that the access network device schedules a first data packet mapped to the QoS flow with the first set of QoS parameters, the transceiver module is configured to schedule the first data packet mapped to the QoS flow with the first set of QoS parameters; alternatively, if the parameter indication information indicates that the access network device schedules a second data packet mapped to the QoS flow with a second set of QoS parameters, the transceiver module is configured to schedule the second data packet mapped to the QoS flow with the second set of QoS parameters.

In a fourteenth aspect, a communication device is provided that includes a processing module and a transceiver module. The processing module is used for acquiring first parameter information aiming at one QoS flow, wherein the first parameter information comprises a second value of QoS parameters of the QoS flow; the second value is used for indicating that the QoS parameter is changed from the first value to the second value, and the first value is different from the second value; the transceiver module is used for sending the first parameter information to the access network equipment so as to indicate that the access network equipment adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow when the preset condition is met.

In a possible implementation manner, the transceiver module is further configured to send monitoring indication information to the user plane functional network element, where the monitoring indication information is used to instruct the user plane functional network element to monitor a flow of a data packet of the QoS flow within a preset time, and when the flow of the data packet of the QoS flow within the preset time changes from above a threshold to below the threshold, or changes from below the threshold to above the threshold, the user plane functional network element sends recovery indication information to the access network device, where the recovery indication information is used to instruct the access network device to use the first value scheduling of the QoS parameter to map to the data packet of the QoS flow; the condition meeting the preset condition means that the access network equipment receives the recovery indication information.

In a fifteenth aspect, a communications apparatus is provided that includes a transceiver module. The receiving and transmitting module is used for scheduling the data packet mapped to the QoS flow by adopting a first value of the QoS parameter of the QoS flow; receiving first parameter information for a QoS flow; scheduling the data packet mapped to the QoS flow by adopting a second value of the QoS parameter; and when the preset condition is met, scheduling the data packet mapped to the QoS flow by adopting the first value of the QoS parameter.

A sixteenth aspect provides a communication system comprising a communication device as claimed in the sixth aspect, a communication device as claimed in the seventh aspect and a communication device as claimed in the eighth aspect; alternatively, the communication device according to the ninth aspect is included; or comprises a communication device according to the eleventh aspect, a communication device according to the twelfth aspect, and a communication device according to the thirteenth aspect; alternatively, the communication device according to the fourteenth aspect and the communication device according to the fifteenth aspect are included.

In a seventeenth aspect, there is provided a computer readable storage medium comprising instructions which, when run on a communication device as described above, cause the communication device to perform a method as described in the first aspect and any of its embodiments, or to perform a method as described in the second aspect and any of its embodiments, or to perform a method as described in the third aspect and any of its embodiments.

In an eighteenth aspect, there is provided a computer program product comprising instructions which, when run on a communication device as described above, cause the communication device to perform a method as described in the first aspect and any of its embodiments, or to perform a method as described in the second aspect and any of its embodiments, or to perform a method as described in the third aspect and any of its embodiments, or to perform a method as described in the fourth aspect and any of its embodiments, or to perform a method as described in the fifth aspect and any of its embodiments.

Technical effects of the sixth to eighteenth aspects refer to technical effects of the first to fifth aspects, and are not described in detail herein.

Drawings

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic flow chart of a communication method according to an embodiment of the present application;

fig. 3 is a second flow chart of a communication method according to an embodiment of the present application;

fig. 4 is a flow chart diagram III of a communication method according to an embodiment of the present application;

fig. 5 is a flow chart diagram of a communication method according to an embodiment of the present application;

fig. 6 is a flow chart diagram of a communication method according to an embodiment of the present application;

Fig. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a chip system according to 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 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, sixth generation communication (the 6th generation,6G) system architecture, and the like. 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 specified in the current standards are 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 flow bit rate (guaranteed flow bit rate, GFBR), and/or maximum flow 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/or 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 a PDB of multiple QoS flows cannot be met, qoS demands with high priority (e.g., PL values are small) are preferentially met, e.g., in case of congestion, when one or more QoS flows cannot meet all QoS demands, 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 device, and for the dynamically allocated 5QI, the corresponding 5G QoS characteristic is sent to the access network device 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 desired to be provided to a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow.

MFBR limits the bit rate provided to GBR QoS flows, i.e., the maximum bit rate provided to GBR QoS flows. 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 stream configuration is generated, the 5G control plane network element AMF and SMF issue QoS stream 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). 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.

Wherein, whether one QoS flow is a GBR QoS flow or a Non-GBR QoS flow is determined by a corresponding QoS file (QoS profile).

For GBR QoS flows, the corresponding QoS file contains the following QoS parameters: 5QI, ARP, GFBR, MFBR, and/or QNC. The GBR QoS flows are determined as a GRB QoS flow requiring notification control (notification control) and a GBR QoS flow 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 resources cannot be met, the access network device notifies the session management function SMF of the event (i.e. that the QoS flow resources corresponding to the GBR QoS flow cannot be met). Further SMFs may initiate QoS flow deletion or QoS flow modification procedures (e.g., modifying 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 current resources cannot support one or more QoS flows to reach a corresponding QoS requirement (e.g., PDB, PER, etc.) cannot be met, PL is used to select which QoS flows to preferentially meet the corresponding QoS requirement.

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 the data streams transmitted in the same QoS stream to the user experience is likely not the same, e.g., intra-coded picture (I) frames are more important than forward-predictive-coded picture (P) frames, more important in the center of the field than at the edges of the field, base layer data more important than enhancement layer data, etc.

From the above description of QoS parameters for the 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 flows cannot be guaranteed, different data flows cannot be scheduled differently according to the difference of the importance degree of the QoS for the data flows, for example, how to realize the priority scheduling of the data flows with high importance degree of the QoE, and after meeting the QoS requirements of the data flows, the data flows with low importance degree of the QoE are scheduled again, so as to realize the differentiated scheduling of the data packets of different types of data blocks corresponding to the same QoS flow.

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.

QoS requirements for the same service are not always constant, e.g., qoS streaming packets for video services include I-frames and P-frames, and I-frames and P-frames are transmitted alternately. The I frame is an intra-frame coding image frame, is an independent frame with all information, can be independently decoded without referring to other images, and is a key frame. P frame is the forward predictive coding image frame, which represents the difference between the current frame image and the previous frame image, and the difference between the current frame image and the previous frame image is overlapped by the previous frame image when decoding, so as to generate the current frame image. The amount of data for I frames is greater than the amount of data for P frames and the QoS requirements for I frames are different from P frames. If QoS parameters of QoS flows are set according to QoS requirements of I frames, time-frequency and other resource waste is easily caused when P frames are transmitted; if the QoS parameters of the QoS flow are set according to the QoS requirement of the P frame, the time-frequency resources are easily insufficient when the I frame is transmitted, and the problems of increased transmission delay, increased packet loss rate and the like are caused, so that the user experience is reduced.

To this end, an embodiment of the present application provides a communication method, where an SMF configures one or more sets of QoS parameters (such as two sets of QoS parameters) of a QoS flow to a RAN, a UPF identifies which set of QoS parameters the data packet of the QoS flow is applicable to, and notifies the RAN of the QoS parameters, and the RAN uses the set of QoS parameters indicated by the UPF to schedule the data packet mapped to the QoS flow, so as to dynamically adjust the QoS parameters of the QoS flow, so as to improve user experience.

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

s101, AF sends first parameter information for one QoS flow to PCF.

The AF may determine the first parameter information of the QoS flow according to information such as a service type of the data flow to which the data packet belongs. The first parameter information includes: a first set of QoS parameters and a second set of QoS parameters for the QoS flow. The first set of QoS parameters corresponds to the first type of information and the second set of QoS parameters corresponds to the second type of information. The first set of QoS parameters is different from the second set of QoS parameters and the first type of information is different from the second type of information. That is, packets that map to the same QoS flow may be scheduled with either the first set of QoS parameters or the second set of QoS parameters.

The present application relates to a first type information indicating a type of a first packet of a QoS flow and a second type information indicating a type of a second packet of a QoS flow. The first type information and/or the second type information is carried in a data packet of one QoS flow, and the type information used for the UPF to identify the data packet as the first type information or the second type information, thereby indicating the RAN to schedule the first data packet mapped to the QoS flow with the first set of QoS parameters or schedule the second data packet mapped to the QoS flow with the second set of QoS parameters. The first type information is used for indicating a first data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow.

The first data packet scheduled with the first set of QoS parameters and the second data packet scheduled with the second set of QoS parameters may be different types of data packets of the same data flow or may be different types of data packets of different data flows. The application is not limited.

The type information of the data packet mapped to the QoS flow may be a frame type of the data packet, a PDU set (set) type of the data packet, or other information. Taking the first type information and the second type information AS examples of frame types, if the UPF identifies that the frame type of a data packet mapped to one QoS flow from the AS is a first frame type, the UPF instructs the RAN to schedule the first data packet mapped to the QoS flow using a first set of QoS parameters; if the UPF identifies that the frame type of the packet from the AS that maps to one QoS flow is a second frame type, the UPF instructs the RAN to schedule a second packet that maps to the QoS flow using a second set of QoS parameters, wherein the first frame type is different from the second frame type.

For example, for an extended reality (XR) application scenario, the frame types of packets mapped to one QoS stream (e.g., packets of a video stream) issued by the AS may include intra-coded picture (I) frames and forward predictive-coded picture (P) frames. And I frames and P frames are alternately issued according to a certain rule, for example IPPPIPPP, i.e. every third P frame is separated by one I frame. Assuming that the first frame type is an I-frame and the second frame type is a P-frame, if the UPF identifies that the frame type of a packet from the AS mapped to a QoS flow is an I-frame, the UPF instructs the RAN to schedule the packet mapped to the QoS flow using the first set of QoS parameters; if the UPF identifies that the frame type of the packet from the AS that maps to one QoS flow is a P-frame, the UPF instructs the RAN to schedule the packet that maps to the QoS flow using a second set of QoS parameters. I.e. I frames correspond to a first set of QoS parameters and P frames correspond to a second set of QoS parameters.

It should be noted that, the present application is not limited to the first parameter information of one QoS flow, and only includes two sets of QoS parameters, i.e., the first set of QoS parameters and the second set of QoS parameters, and may also include more sets of QoS parameters. Accordingly, the present application does not limit that the first parameter information of one QoS flow only includes the first type information and the second type information, and may also include type information corresponding to more sets of QoS parameters.

Likewise, for the configuration information and the second parameter information in the following steps, the present application does not limit that the configuration information and the second parameter information of one QoS flow only include two sets of QoS parameters including a first set of QoS parameters and a second set of QoS parameters, and may further include more sets of QoS parameters, and correspondingly, the present application does not limit that the configuration information and the second parameter information of one QoS flow only include the first type information and the second type information, and may further include type information corresponding to more sets of QoS parameters.

In addition, step S101 is optional.

S102, the PCF generates policy and charging control rules (policy and charging control rule, PCC rule) and sends the PCC rule to the SMF.

If the PCF receives the first parameter information of one QoS flow from the AF, the PCF generates a corresponding PCC rule according to the first parameter information of the QoS flow. If the PCF does not receive the first parameter information of the QoS flow from the AF, the PCF may generate PCC rule according to subscription data of the UE, local configuration of the PCF, and/or policy of an operator. Finally, the first parameter information of the QoS flow is included in one PCC rule. The description of the first parameter information may be referred to the description of step 101.

S103, the SMF sends configuration information for the QoS flow to the UPF.

The configuration information is used to indicate the UPF: determining the type information of the data packet of the QoS flow, and sending parameter indication information for the QoS flow to the access network equipment according to the type information of the data packet of the QoS flow. The parameter indication information is used to instruct the RAN to schedule a first data packet mapped to the QoS flow with a first set of QoS parameters or to schedule a second data packet mapped to the QoS flow with a second set of QoS parameters. It should be noted that, the data packet herein may refer to a received current data packet, or a current data packet and a subsequent data packet, and for a scenario in which the data packet refers to the current data packet and the subsequent data packet, it is not necessary to carry indication information in each data packet, so that overhead of the indication information may be reduced, for example, the indication information is carried only in the first data packet of each type of information, or the indication information is carried in every fixed number of data packets, or the like. Wherein the parameter indication information may be encapsulated in a header (e.g., GTP-U header) of the data packet mapped to the QoS flow. Specifically, if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information indicates the RAN to schedule the data packet mapped to the QoS flow using the first set of QoS parameters; if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information indicates that the RAN schedules the data packet mapped to the QoS flow using the second set of QoS parameters.

The configuration information at least comprises first type information and/or second type information.

When the UPF receives a packet from the AS mapped to one QoS flow: if the UPF determines that the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first type information to indicate the RAN to schedule the first data packet mapped to the QoS flow using the first set of QoS parameters. If the UPF determines that the type information of the data packet mapped to the QoS flow is a second type information, the UPF transmits the second type information to the RAN to instruct the RAN to schedule the second data packet mapped to the QoS flow using a second set of QoS parameters.

Alternatively, when the UPF receives packets from the AS mapped to one QoS flow: if the UPF determines that the type information of the packet mapped to the QoS flow changes, i.e., the type information of the current packet mapped to the QoS flow received by the UPF is different from the type information of the previous packet mapped to the QoS flow received by the UPF, for example, from the first type information to the second type information, or the second type information to the first type information, the parameter indication information is parameter change indication information, which is used to indicate that the RAN changes a set of QoS parameters used when scheduling the packet mapped to the QoS flow, i.e., the parameter change indication information is used to indicate that the RAN schedules the current packet using another set of QoS parameters different from the previous set of QoS parameters, wherein the previous set of QoS parameters refers to a set of QoS parameters scheduling the previous packet mapped to the QoS flow, and the another set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters. For example, when the frame type of the data packet mapped to the QoS flow changes from the first frame type to the second frame type, the parameter change indication information indicates that a set of QoS parameters employed by the RAN in scheduling the data packet mapped to the QoS flow changes from the first set of QoS parameters to the second set of QoS parameters; when the frame type of the data packet mapped to the QoS flow changes from the second frame type to the first frame type, the parameter change indication information indicates that a set of QoS parameters employed by the RAN in scheduling the data packet mapped to the QoS flow changes from the second set of QoS parameters to the first set of QoS parameters.

Optionally, in a possible embodiment, the configuration information may further include first identification information corresponding to the first type of information (i.e. corresponding to the first set of QoS parameters) and/or second identification information corresponding to the second type of information (i.e. corresponding to the second set of QoS parameters), where the first identification information is different from the second identification information.

When the UPF receives a packet from the AS mapped to one QoS flow: if the UPF determines that the type information of the data packet of the QoS flow is the first type information, the parameter indication information is the first identification information to indicate the RAN to schedule the first data packet mapped to the QoS flow by adopting the first group of QoS parameters. If the UPF determines that the type information of the data packet mapped to the QoS flow is second type information, the parameter indication information is second identification information to indicate the RAN to schedule the second data packet mapped to the QoS flow using a second set of QoS parameters.

Optionally, in a possible implementation manner, the configuration information may further include a first QoS parameter in the first set of QoS parameters, and/or a second QoS parameter in the second set of QoS parameters, where the first QoS parameter and the second QoS parameter are different values of the same QoS parameter (e.g. scheduling priority, bit rate, etc.), and where the same QoS parameter may refer to one or more QoS parameters.

When the UPF receives a packet from the AS mapped to one QoS flow: if the UPF determines that the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is a first QoS parameter for indicating the RAN to schedule the first data packet mapped to the QoS flow using the first set of QoS parameters. If the UPF determines that the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is a second QoS parameter for indicating the RAN to schedule the second data packet mapped to the QoS flow using the second set of QoS parameters.

It should be noted that, the manner in which the UPF determines the type information of the packet mapped to the QoS flow to be the first type information or the second type information may include, but is not limited to: the AS directly indicates that the type information of the data packet mapped to one QoS flow is first type information or second type information when the AS issues the data packet mapped to the QoS flow; alternatively, the UPF may determine that the type information of the packet mapped to the QoS flow is first type information or second type information according to the traffic (e.g., the size of the packet) of the packet mapped to the QoS flow, for example, the traffic of the I frame is greater than the traffic of the P frame, if the traffic of the packet mapped to one QoS flow received by the UPF from the AS during the first period is greater than the threshold, the UPF may determine that the frame type of the packet mapped to the QoS flow at this time is the I frame (i.e., the type information is the first type information), otherwise the UPF may determine that the frame type of the packet mapped to the QoS flow at this time is the P frame (i.e., the type information is the second type information).

S104, the SMF sends second parameter information for the QoS flow to the RAN.

The second parameter information includes a first set of QoS parameters and a second set of QoS parameters for one QoS flow, and is applicable to at least two scenarios: the parameter indication information is a scene of the first QoS parameter or the second QoS parameter, or the parameter indication information is a scene of the parameter change indication information.

For the scenario where the parameter indication information is a first QoS parameter and/or a second QoS parameter, when the RAN receives a packet from the UPF that carries the first QoS parameter that is mapped to one QoS flow, the RAN schedules the packet that is mapped to that QoS flow with the first set of QoS parameters. When the RAN receives a packet from the UPF that is mapped to one QoS flow that carries a second QoS parameter, the RAN schedules the packet mapped to that QoS flow with the second set of QoS parameters.

For the scenarios that the parameter indication information is parameter change indication information, the RAN also determines which QoS parameter of the first set of QoS parameters and the second set of QoS parameters is the default set of QoS parameters. For example, the RAN may use the set of QoS parameters in the second parameter information that are located in front as a default set of QoS parameters, or further include default parameter information in the second parameter information, where the default parameter information indicates which set of QoS parameters in the first set of QoS parameters and the second set of QoS parameters is the default set of QoS parameters. Thus, the RAN adopts a default set of QoS parameters to schedule packets mapped to one QoS flow before receiving the parameter change indication information from the UPF for the first time, and then switches the set of QoS parameters between the first set of QoS parameters and the second set of QoS parameters to schedule packets mapped to the QoS flow each time the RAN receives the parameter change indication information from the UPF. That is, a previous packet received by the RAN that is mapped to one QoS flow is scheduled using a previous set of QoS parameters, and when the parameter change indication information is received, a current packet received that is mapped to the QoS flow is scheduled using another set of QoS parameters.

Optionally, for a scenario in which the parameter indication information is first type information corresponding to the first set of QoS parameters and/or second type information corresponding to the second set of QoS parameters, the second parameter information includes, in addition to the first set of QoS parameters and the second set of QoS parameters, first type information corresponding to the first set of QoS parameters and/or second type information corresponding to the second set of QoS parameters. When the RAN receives a packet mapped to one QoS flow from the UPF carrying a first type of information, the RAN schedules the packet mapped to the QoS flow with a first set of QoS parameters; when the RAN receives packets from the UPF that are mapped to one QoS flow that carry the second type of information, the RAN schedules the packets mapped to that QoS flow using the second set of QoS parameters.

Or, optionally, for a scenario in which the parameter indication information is first identification information corresponding to the first set of QoS parameters and/or second identification information corresponding to the second set of QoS parameters, the second parameter information includes, in addition to the first set of QoS parameters and the second set of QoS parameters, the first identification information corresponding to the first set of QoS parameters and/or the second identification information corresponding to the second set of QoS parameters. When the RAN receives a data packet mapped to one QoS flow carrying first identification information from the UPF, the RAN adopts a first group of QoS parameters to schedule the data packet mapped to the QoS flow; when the RAN receives a packet from the UPF that is mapped to one QoS flow carrying the second identification information, the RAN schedules the packet mapped to the QoS flow using the second set of QoS parameters.

It should be noted that the second parameter information may be located in the same QoS file (profiles), for example, the first set of QoS parameters, the first type information corresponding to the first set of QoS parameters, and/or the first identification information may be located in one QoS file (profiles), and the second set of QoS parameters, the second type information corresponding to the second set of QoS parameters, and/or the second identification information may be located in another QoS file (profiles). Or, the first set of QoS parameters, the first type information and/or the first identification information corresponding to the first set of QoS parameters, the second set of QoS parameters, and the second type information and/or the second identification information corresponding to the second set of QoS parameters are all located in the same QoS file (profile).

In addition, the step S104 and the step S103 may be performed first after the step S104 is performed, or the step S103 may be performed first and then the step S104 may be performed, without a requirement of a sequential execution sequence.

S105, the RAN sends a response message to the SMF, the SMF sends a response message to the PCF, and the PCF sends a response message to the AF.

S106, the AS transmits the packet mapped to the QoS flow to the UPF.

S107, the UPF sends a packet mapped to the QoS flow to the RAN, and sends parameter indication information for the QoS flow.

The parameter indication information may be carried in a data packet mapped to the QoS flow (e.g., encapsulating the parameter indication information into a GTP-U header). Specific reference is made to the description of the UPF in step S103, and details are not repeated here.

And S108, the RAN schedules the data packet mapped to the QoS flow by adopting the first group of QoS parameters or the second group of QoS parameters according to the parameter indication information so as to send the data packet mapped to the QoS flow to the UE.

The description of the RAN in step S104 is specifically referred to, and will not be repeated here.

According to the communication method provided by the embodiment of the application, the SMF configures two groups of QoS parameters of one QoS flow to the RAN, the UPF identifies which group of QoS parameters the data packet mapped to the QoS flow is suitable for and informs the RAN, and the RAN adopts one group of QoS parameters indicated by the UPF to schedule the data packet mapped to the QoS flow, so that the QoS parameters of the QoS flow are dynamically regulated, and the user experience is improved.

In an extended reality (XR) application scenario, the QoS requirements of the same service are not always constant. For example, when a user wears a Virtual Reality (VR) device to experience VR live or VR video, the user rotates the head to change a field of view (FoV), and at this time, the network side needs to send downlink data corresponding to the new FoV to the VR device, so that the downlink data is greatly increased in a short time, which easily causes problems of increased transmission delay, increased packet loss rate, and the like, thereby reducing user experience. In addition, after the downlink data is greatly increased in a short time, the subsequent flow can be restored to the normal level, and if the subsequent scheduling is still carried out according to the second value of the QoS parameter, the time-frequency and other resource waste can be caused. Therefore, it is necessary to provide a restoration mechanism that enables the RAN to restore the QoS parameters to the first value of the QoS parameters, so as to fully utilize resources such as time-frequency.

For this reason, as shown in fig. 3, the embodiment of the present application provides a communication method, when a UE requests to change a QoS parameter of one QoS flow, a core network element instructs a RAN to schedule a data packet mapped to the one QoS flow by using a second value of the QoS parameter, and when a preset condition is satisfied, the data packet mapped to the one QoS flow is scheduled by using a first value of the QoS parameter, so as to dynamically adjust the QoS parameter of the QoS flow, thereby improving user experience.

S201, the RAN adopts a first value of QoS parameter of a QoS flow to schedule data packets mapped to the QoS flow.

S202, the core network element receives the parameter change request information from the UE, and obtains a second value of the QoS parameter according to the parameter change request information.

The parameter change request information is used to request a change of QoS parameters of the QoS flow. The parameter change request information comprises an event that occurs to change a QoS parameter of the QoS flow, from which event a second value of the QoS parameter (e.g. the target bandwidth) is determined by the core network element. Alternatively, the parameter change request information may include a second value of the QoS parameter (e.g., the target bandwidth). The second value of the QoS parameter is used to instruct the RAN to change the QoS parameter of the QoS flow from the first value to the second value.

At this time, the core network element may be an AF, UPF/mobile edge platform (mobile edge platform, MEP) (network element where the UPF and the MEP are combined).

S203, the core network element acquires the first parameter information aiming at the QoS flow.

The first parameter information includes a second value of the QoS parameter. Optionally, the first parameter information further includes: the duration of the second value of the QoS parameter, or the total data amount of the data packets mapped to one QoS flow is scheduled with the second value of the QoS parameter; wherein the total data amount is used in combination with the duration of the second value of the QoS parameter, e.g., dividing the total data amount by the target bandwidth may result in the duration of the second value of the QoS parameter.

At this time, the core network element may be AF, SMF, UPF, UPF/MEP. When the core network element is an SMF or a UPF, the core network element may receive first parameter information for the QoS flow from the AF. When the core network element is AF or UPF/MEP, the core network element can generate the first parameter information for the QoS flow by itself.

S204, the core network element sends the first parameter information to the RAN to indicate: when the preset condition is met, the RAN adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

Accordingly, the RAN receives the first parameter information. The first parameter information may be forwarded to the RAN via other core network elements.

Optionally, when the core network element is not a UPF (for example, when the core network element is an SMF), the core network element may further send monitoring indication information to the UPF, where the monitoring indication information is used to instruct the UPF to monitor the traffic of the data packet mapped to the QoS flow within a preset time, and when the traffic of the data packet mapped to the QoS flow within the preset time changes from above the threshold to below the threshold, or from below the threshold to above the threshold, the UPF sends restoration indication information to the RAN, where the restoration indication information is used to instruct the RAN to schedule the data packet mapped to the QoS flow using the first value of the QoS parameter.

Optionally, when the core network element is a UPF, the core network element monitors the flow of the data packet mapped to the QoS flow in a preset time; and when the flow of the data packet mapped to the QoS flow in the preset time is changed from being higher than the threshold to being lower than the threshold, or from being lower than the threshold to being higher than the threshold, the core network element sends recovery indication information to the RAN.

It should be noted that, through the second value (for example, the target bandwidth) of the QoS parameter in the obtained first parameter information, the core network element calculates the preset time and the threshold in proportion (for example, the bandwidth is 1Gbps, the preset time may be set to 5ms, the threshold is 5M), and the preset time may be set to be less than the time of sending a frame of data packet.

In one possible embodiment, meeting the preset condition means: the RAN schedules packets mapped to the QoS flow for the duration using the second value of the QoS parameter.

In another possible embodiment, the satisfaction of the preset condition means: the RAN receives recovery indication information from the UPF.

The first parameter information may be carried in a header (e.g., GTP-U header) of a data packet mapped to the QoS flow.

S205, the RAN schedules the data packet mapped to the QoS flow using the second value of the QoS parameter.

The RAN may determine whether a received packet belongs to a QoS flow by the five-tuple (source IP address, source port, destination IP address, destination port, and transport layer protocol) of the packet, thereby changing QoS parameters of scheduling packets mapped to the QoS flow.

S206, when the preset condition is met, the RAN adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

According to the communication method provided by the embodiment of the application, the core network element indicates the RAN to schedule the data packet mapped to the QoS flow by adopting the second value of the QoS parameter, and when the preset condition is met, the RAN schedules the data packet mapped to the QoS flow by adopting the first value of the QoS parameter, so that the QoS parameter of the QoS flow is dynamically regulated, and the user experience is improved.

The embodiment of the application provides a communication method, when UE requests to change the QoS parameter of a QoS flow, SMF indicates RAN to adopt the second value of the QoS parameter to schedule the data packet mapped to the QoS flow, when the preset condition is met, the first value of the QoS parameter is adopted to schedule the data packet mapped to the QoS flow, so as to realize dynamic adjustment of the QoS parameter of the QoS flow and improve user experience.

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

s301, UE, RAN, SMF, UPF, PCF establishes a PDU session.

At this time, the RAN schedules a packet mapped to the QoS flow using the first value of the QoS parameter of the QoS flow.

S302, the UE sends parameter change request information to the AF.

The parameter change request information refers to step S202 and is not repeated here.

As in the previous example, when the user wears the VR device to experience VR live broadcast or VR video, the user rotates the head to cause the FoV to change, and the UE requests the AF for downlink data corresponding to the new FoV, where the downlink data corresponding to the new FoV may generate burst large bandwidth traffic, and the QoS requirement (e.g., the target bandwidth) needs to be changed correspondingly, which may easily cause problems such as increase in transmission delay and increase in packet loss rate. At this time, the UE may transmit parameter change request information to the AF through the application layer to request a change of QoS parameters of the QoS flow.

S303, the AF sends the PCF first parameter information mapped to the QoS flow.

The first parameter information is referred to in step S203 and is not repeated here.

S304, PCF generates policy and charging control rule (policy and charging control rule, PCC rule) according to the first parameter information, and sends PCC rule to SMF.

I.e. the PCC rule comprises first parameter information.

S305, the SMF sends the first parameter information to the RAN.

S306, the SMF sends monitoring indication information to the UPF.

For example, taking the example shown in step S302 as an example, the monitoring indication information may indicate that the UPF sends recovery indication information to the RAN when the traffic of the data packet mapped to the QoS flow changes from above the threshold to below the threshold within a preset time.

The monitoring instruction information and the restoration instruction information may refer to step S204, and are not repeated here.

In addition, step S306 is optional. Step S306 may be performed when the first parameter information does not include the duration of the second value of the QoS parameter and the total data amount of the data packet mapped to one QoS flow is scheduled with the second value of the QoS parameter. Step S306 may not be performed when the first parameter information includes a duration of the second value of the QoS parameter or schedules a total data amount of data packets mapped to one QoS flow with the second value of the QoS parameter.

S307, the RAN sends a response message to the SMF, the SMF sends a response message to the PCF, and the PCF sends a response message to the AF.

S308, the AS sends a packet mapped to the QoS flow to the UPF.

S309, the UPF sends the RAN a packet mapped to the QoS flow.

If the UPF receives the monitoring indication information from the SMF, the UPF starts to monitor the traffic of the data packet mapped to the QoS flow within a preset time.

When the flow of the data packet mapped to the QoS flow in the preset time is changed from being higher than a threshold to being lower than the threshold, or from being lower than the threshold to being higher than the threshold, the UPF sends recovery indication information to the RAN, wherein the recovery indication information is used for indicating the RAN to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter.

For example, taking the example shown in step S302 as an example, when the flow of the data packet in the preset time changes from being higher than the threshold to being lower than the threshold, the restoration instruction information instructs the RAN to schedule the data packet mapped to the QoS flow using the first value of the QoS parameter.

S310, the RAN adopts a second value of the QoS parameter to schedule the data packet mapped to the QoS flow so as to send the data packet data mapped to the QoS flow to the UE.

The RAN needs to store the first value of the QoS parameters before scheduling the data packets mapped to the QoS flow with the second value of the QoS parameters.

And S311, when the preset condition is met, the RAN adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

The QoS requirements of the same service are not always kept unchanged, for example, taking the example shown in step S302 as an example, when the user turns, the sudden large bandwidth traffic is only generated in a short time, the latter traffic can be restored to the normal level, and if the scheduling is still performed according to the second value of the QoS parameter, the time-frequency resource waste is caused. Therefore, it is necessary to provide a restoration mechanism that enables the RAN to restore the QoS parameters to the first value of the QoS parameters, so as to fully utilize resources such as time-frequency.

The step S204 is referred to for satisfying the preset condition, and will not be described herein.

In one possible implementation, the RAN schedules packets mapped to the QoS flow with the second value of the QoS parameter for a duration in the first parameter information and schedules packets mapped to the QoS flow with the first value of the QoS parameter.

In another possible implementation, after the RAN receives the recovery indication information from the UPF, the first valued of the QoS parameter is used to schedule the data packet mapped to the QoS flow.

The embodiment of the application provides a communication method, when UE requests to change the QoS parameter of one QoS flow, UPF/MEP indicates RAN to adopt the second value scheduling of the QoS parameter to map to the data packet of the QoS flow, when the preset condition is met, the first value scheduling of the QoS parameter is adopted to map to the data packet of the QoS flow, so as to realize dynamic adjustment of the QoS parameter of the QoS flow and improve user experience.

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

s401, UE, RAN, UPF/MEP establishes a PDU session.

At this time, the RAN schedules packets mapped to one QoS flow using the first value of the QoS parameter of the QoS flow.

S402, the UE sends parameter change request information to the UPF/MEP.

As in the previous example, when the user wears the VR device to experience VR live broadcast or VR video, the user rotates the head to cause the FoV to change, and the UE requests the UPF/MEP for downlink data corresponding to the new FoV, where the downlink data corresponding to the new FoV may generate burst large bandwidth traffic, and QoS requirements (e.g. bandwidth) of the new FoV need to be changed correspondingly, which may easily cause problems such as increase in transmission delay and increase in packet loss rate. At this point the UE may send an indication to the UPF/MEP via the application layer to request a change in QoS parameters for the QoS flow.

S403, the UPF/MEP sends first parameter information for the QoS flow to the RAN.

The first parameter information refers to step S203, and is not described herein.

The first parameter information may be carried in a New GTP-U message, which may be named a New QoS request (New QoS request) or other name, and is issued to the RAN via path signaling of the user plane.

S404, the UPF/MEP sends the RAN a packet mapped to the QoS flow.

If the duration of the second value of the QoS parameter is not included in the first parameter information and the total data amount of the data packet mapped to the QoS flow is scheduled by adopting the second value of the QoS parameter, the UPF/MEP monitors the flow of the data packet mapped to the QoS flow within a preset time.

And when the flow of the data packet mapped to the QoS flow in the preset time is changed from being higher than the threshold to being lower than the threshold, or from being lower than the threshold to being higher than the threshold, the UPF/MEP sends recovery indication information to the RAN, wherein the recovery indication information is used for indicating the RAN to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter.

S405, the RAN schedules the data packet mapped to the QoS flow using the second value of the QoS parameter, so as to send the data packet data mapped to the QoS flow to the UE.

Similar to step S310, the RAN needs to store the first value of the QoS parameter before scheduling the data packet mapped to the QoS flow with the second value of the QoS parameter.

S406, when the preset condition is met, the RAN adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

This step refers to step S311, and will not be described in detail herein.

The embodiment of the application provides a communication method, when UE requests to change the QoS parameter of one QoS flow, UPF indicates RAN to adopt the second value of the QoS parameter to schedule the data packet mapped to the QoS flow, when the preset condition is met, the first value of the QoS parameter is adopted to schedule the data packet mapped to the QoS flow, so as to realize dynamic adjustment of the QoS parameter of the QoS flow and improve user experience.

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

s501, UE, RAN, UPF, AF/AS establishes a PDU session.

S502, the UE sends parameter change request information to the AF.

S503, AF sends the first parameter information for the QoS flow to UPF.

S504, the UPF sends the first parameter information to the RAN.

The step refers to step S403, and thus will not be described in detail.

S505, the AS transmits the packet mapped to the QoS flow to the UPF.

S506, the UPF sends the RAN a packet mapped to the QoS flow.

This step refers to step S404, and will not be described in detail herein.

S507, the RAN adopts a second value of the QoS parameter to schedule the data packet mapped to the QoS flow so as to send the data packet data mapped to the QoS flow to the UE.

This step refers to step S405, and will not be described in detail herein.

And S508, when the preset condition is met, the RAN adopts the first value of the QoS parameter to schedule the data packet mapped to the QoS flow.

This step refers to step S311, and will not be described in detail herein.

It will be appreciated that in the various embodiments above, the methods and/or steps implemented by the SMF may also be implemented by a component (e.g., a chip or circuit) of the SMF. The methods and/or steps implemented by the UPF may also be implemented by a component (e.g., a chip or circuit) of the UPF. The methods and/or steps implemented by the RAN may also be implemented by a component (e.g., a chip or circuit) of the RAN. The methods and/or steps implemented by the core network element may also be implemented by a component (e.g. a chip or a circuit) of the core network element.

The embodiment of the application also provides a communication device. The communication device may be an SMF in the above method embodiment, or a device including the SMF, or a chip or a functional module in the SMF. Alternatively, the communication device may be a UPF in the above method embodiment, or a device including the above UPF, or a chip or a functional module of the UPF. Alternatively, the communication device may be a RAN in the above method embodiment, or a device including the RAN, or a chip or a functional module in the RAN. Alternatively, the communication device may be a core network element in the above method embodiment, or a device including the core network element, or a chip or a functional module in the core network element. Thereby realizing the various methods.

It will be appreciated that the communication device, in order to achieve the above-described functions, comprises corresponding hardware structures and/or software modules performing the respective functions. Those of skill in the art will readily 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 embodiment of the application can divide the functional modules of the communication device according to the embodiment of the method, for example, each functional module can be divided corresponding to each function, or 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.

Fig. 7 shows a schematic structural diagram of a communication device 20. The communication device 20 comprises a processing module 201 and a transceiver module 202. The communication device 20 may be the aforementioned SMF, UPF, RAN or core network element. The processing module 201 may also be referred to as a processing unit, for implementing the processing functions of SMF, UPF, RAN or the core network element in the above method embodiment. The transceiver module 202, which may also be referred to as a transceiver unit, is configured to implement the transceiver function of SMF, UPF, RAN or the core network element in the above method embodiment. Transceiver module 202 may be referred to as a transceiver circuit, transceiver, or communication interface.

Take the communication device 20 as an example of the SMF in the above-described method embodiment.

In a possible implementation, the processing module 201 is configured to obtain first parameter information for one quality of service QoS flow. The transceiver module 202 is configured to send second parameter information for the QoS flow to the access network device.

In one possible implementation, the configuration information further includes: the first identification information corresponding to the first type information and/or the second identification information corresponding to the second type information, wherein the first identification information is different from the second identification information.

In one possible implementation, the second parameter information further includes: the first identification information and/or the second identification information. .

In one possible implementation, the configuration information further includes: the first QoS parameter in the first group of QoS parameters and/or the second QoS parameter in the second group of QoS parameters are different values of the same QoS parameter.

In a possible embodiment, the second parameter information further comprises a first type of information and/or a second type of information.

In a possible embodiment, the second parameter information further comprises default parameter information indicating which of the first set of QoS parameters and the second set of QoS parameters is the default set of QoS parameters.

In one possible implementation, the first type information and the second type information are frame types, or packet data unit set types.

Take the UPF in the above method embodiment as an example of the communication device 20.

In a possible implementation, the transceiver module 202 is configured to receive configuration information for one quality of service QoS flow from a session management function network element; receiving a data packet mapped to a QoS flow; and sending parameter indication information for the QoS flow to the access network equipment according to the type information of the data packet mapped to the QoS flow.

If the type information of the data packet mapped to the QoS flow is first type information, the parameter indication information indicates the access network device to schedule the first data packet mapped to the QoS flow by adopting a first group of QoS parameters; alternatively, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information instructs the access network device to schedule the second data packet mapped to the QoS flow using the second set of QoS parameters.

In one possible implementation, the configuration information further includes: first identification information corresponding to the first type information (i.e., corresponding to the first set of QoS parameters) and/or second identification information corresponding to the second type information (i.e., corresponding to the second set of QoS parameters), the first identification information being different from the second identification information; if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first identification information; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second identification information.

In one possible implementation, if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first type information; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second type information.

In one possible implementation, the configuration information further includes: a first QoS parameter in the first group of QoS parameters and/or a second QoS parameter in the second group of QoS parameters, wherein the first QoS parameter and the second QoS parameter are different values of the same QoS parameter; if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first QoS parameter; or, if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second QoS parameter.

In one possible implementation manner, if the type information of the current data packet mapped to the QoS flow received by the user plane functional network element is different from the type information of the previous data packet mapped to the QoS flow, the parameter indication information is parameter change indication information, where the parameter change indication information is used to instruct the access network device to schedule the current data packet using another set of QoS parameters different from the previous set of QoS parameters, where the previous set of QoS parameters refers to a set of QoS parameters for scheduling the previous data packet; the previous set of QoS parameters and the other set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters.

In one possible implementation, the parameter indication information is carried in a header of a data packet mapped to the QoS flow.

Take the communication device 20 as an example of the RAN in the above-described method embodiment.

In a possible implementation, the transceiver module 202 is configured to receive second parameter information for one quality of service QoS flow from the session management function network element; receiving parameter indication information for QoS flow from user plane function network element; according to the parameter indication information, a first data packet mapped to the QoS flow is scheduled by using a first set of QoS parameters or a second data packet mapped to the QoS flow is scheduled by using a second set of QoS parameters.

In one possible implementation, if the parameter indication information indicates that the access network device schedules a first data packet mapped to the QoS flow using the first set of QoS parameters, the transceiver module 202 is configured to schedule the first data packet mapped to the QoS flow using the first set of QoS parameters; alternatively, if the parameter indication information indicates that the access network device schedules a second data packet mapped to the QoS flow with a second set of QoS parameters, the transceiver module 202 is configured to schedule the second data packet mapped to the QoS flow with the second set of QoS parameters.

In one possible implementation, the second parameter information further includes: the first identification information corresponding to the first group of QoS parameters and/or the second identification information corresponding to the second group of QoS parameters; the parameter indication information is first identification information or second identification information; if the parameter indication information is first identification information, the first identification information indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; or if the parameter indication information is second identification information, the second identification information indicates the access network device to schedule a second data packet mapped to the QoS flow using a second set of QoS parameters.

In a possible embodiment, the second parameter information further comprises a first type of information and/or a second type of information; the first type information is used for indicating the data packets which are scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating the data packets which are scheduled by adopting a second group of QoS parameters in the QoS flow; the parameter indication information is first type information or second type information; if the parameter indication information is the first type information, the first type information indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; alternatively, if the parameter indication information is a second type of information, the second type of information indicates to the access network device to schedule a second data packet mapped to the QoS flow with a second set of QoS parameters.

In one possible implementation, the parameter indication information is a first QoS parameter in the first set of QoS parameters, or a second QoS parameter in the second set of QoS parameters, the first QoS parameter and the second QoS parameter being different values of the same QoS parameter; if the parameter indication information is a first QoS parameter, the first QoS parameter indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting a first group of QoS parameters; or if the parameter indicating information is a second QoS parameter, the second QoS parameter indicates the access network device to schedule a second data packet mapped to the QoS flow using the second set of QoS parameters.

In one possible implementation, the parameter indication information is parameter change indication information, where the parameter change indication information is used to instruct the access network device to schedule the current data packet mapped to the QoS flow using another set of QoS parameters different from the previous set of QoS parameters, where the previous set of QoS parameters refers to a set of QoS parameters that schedule the previous data packet mapped to the QoS flow; the first set of QoS parameters and the other set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters; the access network device adopts the first group of QoS parameters or the second group of QoS parameters to schedule the data packet mapped to the QoS flow according to the parameter indication information, and comprises the following steps: the access network device schedules the current data packet with another set of QoS parameters.

Taking the communication device 20 as a core network element in the above method embodiment as an example.

In a possible implementation manner, the processing module 201 is configured to obtain first parameter information for one quality of service QoS flow, where the first parameter information includes a second value of a QoS parameter of the QoS flow; the second value is used for indicating that the QoS parameter is changed from the first value to the second value, and the first value is different from the second value; the transceiver module 202 is configured to send the first parameter information to the access network device, so as to instruct the access network device to schedule the data packet mapped to the QoS flow by using the second value of the QoS parameter when the preset condition is met.

In a possible implementation manner, the first parameter information further includes a duration of the second value, or the second value of the QoS parameter is used to schedule the total data amount of the data packet mapped to the QoS flow; the total data volume is used for combining the second value to obtain the duration of the second value; meeting the preset condition means that the access network device adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow for reaching the duration.

In a possible implementation manner, the transceiver module 202 is further configured to send monitoring indication information to the user plane function network element, where the monitoring indication information is used to instruct the user plane function network element to monitor the traffic of the data packet of the QoS flow within a preset time, and when the traffic of the data packet of the QoS flow within the preset time changes from above the threshold to below the threshold, or changes from below the threshold to above the threshold, the user plane function network element sends recovery indication information to the access network device, where the recovery indication information is used to instruct the access network device to use the first value of the QoS parameter to schedule the data packet mapped to the QoS flow; the condition meeting the preset condition means that the access network equipment receives the recovery indication information.

In one possible embodiment, the method further comprises: the core network element monitors the flow of data packets of QoS flow within preset time; when the flow of the data packet of the QoS flow changes from higher than the threshold to lower than the threshold or from lower than the threshold to higher than the threshold in the preset time, the core network element sends recovery indication information to the access network equipment, wherein the recovery indication information is used for indicating the access network equipment to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter; the condition meeting the preset condition means that the access network equipment receives the recovery indication information.

In one possible embodiment, the method further comprises: the core network element receives parameter change request information from user equipment, wherein the parameter change request information is used for requesting to change QoS parameters of QoS flow; and the core network element obtains a second value of the QoS parameter according to the parameter change request information.

In one possible implementation, the parameter change request information includes an event that occurs to change a QoS parameter of the QoS flow.

In one possible implementation, the first parameter information sent to the access network device is carried in a header of a data packet mapped to the QoS flow.

In one possible implementation, the transceiver module 202 is configured to schedule data packets mapped to a QoS flow using a first value of a QoS parameter of the QoS flow; receiving first parameter information for a QoS flow; scheduling the data packet mapped to the QoS flow by adopting a second value of the QoS parameter; and when the preset condition is met, scheduling the data packet mapped to the QoS flow by adopting the first value of the QoS parameter.

In one possible implementation, the first parameter information further includes: a second valued duration, or a second valued scheduling of the total data amount of data packets mapped to the QoS flow using the QoS parameter; wherein the total data amount is used in combination with the second score for the duration; meeting the preset condition means that the access network device adopts the second value of the QoS parameter to schedule the data packet mapped to the QoS flow for reaching the duration.

In one possible embodiment, the method further comprises: the access network device receiving recovery indication information from the user plane function network element when the preset condition is met, wherein the recovery indication information is used for indicating the access network device to schedule the data packet mapped to the QoS flow by adopting the first value of the QoS parameter.

In one possible implementation, the first parameter information is carried in a header of a data packet mapped to the QoS flow.

As shown in fig. 8, the embodiment of the application further provides a communication device. The communication device 30 comprises a processor 301, a memory 302 and a transceiver 303, the processor 301 being coupled to the memory 302 and the transceiver 303, the transceiver 303 being for supporting the communication device to communicate with other communication devices. When the processor 301 executes the computer program or instructions in the memory 302, a corresponding method of SMF, UPF, RAN or core network element in fig. 2-6 is performed.

As shown in fig. 9, the embodiment of the application further provides a chip system. The chip system 40 includes at least one processor 401 and at least one interface circuit 402. The at least one processor 401 and the at least one interface circuit 402 may be interconnected by wires. For example, at least one interface circuit 402 may be used to receive signals from other devices (e.g., memory) or to transmit signals to other communication devices (e.g., communication interfaces). Thereby performing the method corresponding to SMF, UPF, RAN or core network element in fig. 2-6.

Embodiments of the present application also provide a computer readable storage medium comprising instructions which, when run on the above-described communication device, cause the communication device to perform the functions or steps performed by SMF, UPF, RAN or core network element in the above-described method embodiments, for example performing the methods shown in fig. 2-6.

Embodiments of the present application also provide a computer program product comprising instructions which, when run on the above-described communication device, cause the communication device to perform the functions or steps performed by SMF, UPF, RAN or core network element in the above-described method embodiments, e.g. to perform the methods shown in fig. 2-6.

Technical effects concerning the communication apparatus, the computer-readable storage medium, the computer program product refer to technical effects of the previous method embodiments.

The processor referred to in the embodiments of the present application may be a chip. For example, it may be a field programmable gate array (field programmable gate array, FPGA), an application specific integrated chip (application specific integrated circuit, ASIC), a system on chip (SoC), a central processor (central processor unit, CPU), a network processor (network processor, NP), a digital signal processing circuit (digital signal processor, DSP), a microcontroller (micro controller unit, MCU), a programmable controller (programmable logic device, PLD), or other integrated chip.

The memory to which embodiments of the present application relate may be volatile memory or nonvolatile memory, or may include both volatile and 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) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as 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 the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

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

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

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and module may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

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

The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physically separate, i.e., may be located in one device, or may be distributed over multiple devices. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional module in the embodiments of the present application may be integrated in one device, or each module may exist alone physically, or two or more modules may be integrated in one device.

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

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:

the session management function network element obtains first parameter information for one quality of service QoS flow, wherein the first parameter information comprises: a first set of QoS parameters and a second set of QoS parameters of the QoS flow, the first set of QoS parameters corresponding to the first type of information and the second set of QoS parameters corresponding to the second type of information; the first type information is used for indicating a first data packet which is scheduled by adopting the first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting the second group of QoS parameters in the QoS flow;

the session management function network element sends second parameter information for the QoS flow to an access network device, the second parameter information including the first set of QoS parameters and the second set of QoS parameters.

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

the session management function network element sends configuration information for the QoS flow to a user plane function network element, wherein the configuration information comprises the first type information and/or the second type information;

the first type information and/or the second type information sent to the user plane function network element are used for: the user plane function network element instructs the access network device to schedule a first data packet mapped to the QoS flow with the first set of QoS parameters or to schedule a second data packet mapped to the QoS flow with the second set of QoS parameters.

3. The method of claim 2, wherein the configuration information further comprises: the first identification information corresponding to the first type information and/or the second identification information corresponding to the second type information, wherein the first identification information is different from the second identification information.

4. A method according to claim 3, wherein the second parameter information further comprises: the first identification information and/or the second identification information.

5. The method of claim 2, wherein the configuration information further comprises: a first QoS parameter of the first set of QoS parameters and/or a second QoS parameter of the second set of QoS parameters, the first QoS parameter and the second QoS parameter being different values of the same QoS parameter.

6. The method according to any of claims 1-2, wherein the second parameter information further comprises the first type of information and/or the second type of information.

7. The method of any of claims 1-2, wherein the second parameter information further comprises default parameter information indicating which of the first set of QoS parameters and the second set of QoS parameters is a default set of QoS parameters.

8. The method according to any of claims 1-7, wherein the first type information and the second type information are frame types or packet data unit set types.

9. A method of communication, comprising:

the user plane function network element receives configuration information aiming at a QoS flow from the session management function network element, wherein the configuration information comprises first type information and/or second type information; the first type information is used for indicating a first data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating a second data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow;

The user plane function network element receives the data packet mapped to the QoS flow;

and the user plane function network element sends parameter indication information for the QoS flow to access network equipment according to the type information of the data packet mapped to the QoS flow, wherein the parameter indication information is used for indicating the access network equipment to schedule a first data packet mapped to the QoS flow by adopting the first group of QoS parameters or schedule a second data packet mapped to the QoS flow by adopting the second group of QoS parameters.

10. The method of claim 9, wherein the step of determining the position of the substrate comprises,

if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information indicates the access network device to schedule a first data packet mapped to the QoS flow by adopting the first group of QoS parameters;

or,

if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information indicates the access network device to schedule a second data packet mapped to the QoS flow by adopting the second set of QoS parameters.

11. The method of claim 10, wherein the configuration information further comprises: first identification information corresponding to the first type information and/or second identification information corresponding to the second type information, wherein the first identification information is different from the second identification information;

If the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first identification information;

or,

and if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second identification information.

12. The method of claim 10, wherein the step of determining the position of the first electrode is performed,

if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first type information;

or,

and if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indication information is the second type information.

13. The method of claim 10, wherein the configuration information further comprises: a first QoS parameter of the first set of QoS parameters and/or a second QoS parameter of the second set of QoS parameters, the first QoS parameter and the second QoS parameter being different values of the same QoS parameter;

if the type information of the data packet mapped to the QoS flow is the first type information, the parameter indication information is the first QoS parameter;

Or,

if the type information of the data packet mapped to the QoS flow is the second type information, the parameter indicating information is the second QoS parameter.

14. The method according to claim 9, wherein if the type information of the current packet mapped to the QoS flow received by the user plane function network element is different from the type information of the previous packet mapped to the QoS flow, the parameter indication information is parameter change indication information, the parameter change indication information being used to instruct the access network device to schedule the current packet using another set of QoS parameters different from the previous set of QoS parameters, the previous set of QoS parameters being a set of QoS parameters for scheduling the previous packet; the previous set of QoS parameters and the further set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters.

15. The method according to any of claims 9-14, wherein the first type information and the second type information are frame types or packet data unit set types.

16. The method according to any of claims 9-15, wherein the parameter indication information is carried in a header of a data packet mapped to the QoS flow.

17. A method of communication, comprising:

the access network equipment receives second parameter information for one QoS flow from a session management function network element, wherein the second parameter information comprises a first group of QoS parameters and a second group of QoS parameters of the QoS flow;

the access network device receives parameter indication information for the QoS flow from a user plane function network element, wherein the parameter indication information is used for indicating the access network device to schedule a first data packet mapped to the QoS flow by adopting the first group of QoS parameters or schedule a second data packet mapped to the QoS flow by adopting the second group of QoS parameters;

and the access network equipment adopts the first set of QoS parameters to schedule a first data packet mapped to the QoS flow or adopts the second set of QoS parameters to schedule a second data packet mapped to the QoS flow according to the parameter indication information.

18. The method of claim 17, wherein the access network device schedules either a first data packet mapped to the QoS flow with the first set of QoS parameters or a second data packet mapped to the QoS flow with the second set of QoS parameters based on the parameter indication information, comprising:

If the parameter indication information indicates that the access network device adopts the first set of QoS parameters to schedule a first data packet mapped to the QoS flow, the access network device adopts the first set of QoS parameters to schedule the first data packet mapped to the QoS flow;

or,

if the parameter indication information indicates that the access network device schedules a second data packet mapped to the QoS flow using the second set of QoS parameters, the access network device schedules a second data packet mapped to the QoS flow using the second set of QoS parameters.

19. The method of claim 18, wherein the second parameter information further comprises: the first identification information corresponding to the first group of QoS parameters and/or the second identification information corresponding to the second group of QoS parameters; the parameter indication information is the first identification information or the second identification information;

if the parameter indication information is the first identification information, the first identification information indicates the access network equipment to schedule a first data packet mapped to the QoS flow by adopting the first group of QoS parameters;

or,

and if the parameter indication information is the second identification information, the second identification information indicates the access network equipment to schedule a second data packet mapped to the QoS flow by adopting the second group of QoS parameters.

20. The method according to claim 18, wherein the second parameter information further comprises a first type of information and/or a second type of information; the first type information is used for indicating the data packet which is scheduled by adopting a first group of QoS parameters in the QoS flow, and the second type information is used for indicating the data packet which is scheduled by adopting a second group of QoS parameters in the QoS flow; the parameter indication information is the first type information or the second type information;

if the parameter indication information is the first type information, the first type information indicates the access network device to schedule a first data packet mapped to the QoS flow by adopting the first group of QoS parameters;

or,

and if the parameter indication information is the second type information, the second type information indicates the access network equipment to schedule a second data packet mapped to the QoS flow by adopting the second set of QoS parameters.

21. The method of claim 18, wherein the parameter indication information is a first QoS parameter of the first set of QoS parameters or a second QoS parameter of the second set of QoS parameters, the first QoS parameter and the second QoS parameter being different values of the same QoS parameter;

If the parameter indication information is the first QoS parameter, the first QoS parameter indicates the access network device to schedule a first data packet mapped to the QoS flow using the first set of QoS parameters;

or,

and if the parameter indication information is the second QoS parameter, the second QoS parameter indicates the access network equipment to schedule a second data packet mapped to the QoS flow by adopting the second group of QoS parameters.

22. The method of claim 17, wherein the parameter indication information is parameter change indication information, the parameter change indication information being used to instruct the access network device to schedule a current data packet mapped to the QoS flow using another set of QoS parameters different from a previous set of QoS parameters, wherein the previous set of QoS parameters refers to a set of QoS parameters that scheduled a previous data packet mapped to the QoS flow; the previous set of QoS parameters and the further set of QoS parameters belong to the first set of QoS parameters and the second set of QoS parameters; the access network device adopts the first group of QoS parameters or the second group of QoS parameters to schedule the data packet mapped to the QoS flow according to the parameter indication information, and comprises the following steps:

The access network device schedules the current data packet using the other set of QoS parameters.

23. The method according to any of claims 17-22, wherein the second parameter information further comprises default parameter information indicating which of the first set of QoS parameters and the second set of QoS parameters is the default set of QoS parameters.

24. The method of claim 20, wherein the first type information and the second type information are frame types or packet data unit set types.

25. The method according to any of claims 17-24, wherein the parameter indication information is carried in a header of a data packet mapped to the QoS flow.

26. A communication device comprising a processor and a transceiver for communicating with other communication devices, the method of any of claims 1-8 being performed when the processor executes instructions.

27. A communication device comprising a processor and a transceiver for communicating with other communication devices, the method of any of claims 9-16 being performed when the processor executes instructions.

28. A communication device comprising a processor and a transceiver for communicating with other communication devices, the method of any of claims 17-25 being performed when the processor executes instructions.

29. A communication system comprising a communication device according to claim 26, a communication device according to claim 27 and a communication device according to claim 28.

30. A computer readable storage medium comprising instructions which, when executed on a communications device, cause the communications device to perform the method of any one of claims 1 to 8, or to perform the method of any one of claims 9 to 16, or to perform the method of any one of claims 17 to 25.