WO2020155940A1

WO2020155940A1 - Communication method and communication apparatus

Info

Publication number: WO2020155940A1
Application number: PCT/CN2019/127826
Authority: WO
Inventors: 应江威; 杨艳梅; 李濛
Original assignee: 华为技术有限公司
Priority date: 2019-01-28
Filing date: 2019-12-24
Publication date: 2020-08-06
Also published as: CN114466382A; CN111491313A; CN111491313B

Abstract

Provided in embodiments of the present application are a communication method and a communication apparatus, which may effectively save network resources. The method described in embodiments of the present application comprises: a first access network device acquiring a QoS flow set having an association relationship in a PDU session, the QoS flow set comprising at least two QoS flows; when a QoS flow that meets a QoS flow rejection condition is present in the QoS flow set, the first access network device rejecting all QoS flows in the QoS flow set. By means of the described mode, since an application corresponding to a QoS flow cannot run normally when any QoS flow meets a rejection condition, QoS flows having an association relationship are completely rejected, thus effectively saving network resources.

Description

Communication method and communication device

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on January 28, 2019, the application number is 201910083056.0, and the invention title is "a communication method and communication device", the entire content of which is incorporated into this application by reference .

Technical field

This application relates to the field of communication, and in particular to a communication method and communication device.

Background technique

In the 5G system, in order to ensure the end-to-end service quality of the service, a 5G QoS model based on the quality of service (QoS) flow is proposed. For a user equipment (User Equipment, UE), one or more protocol data unit (PDU) sessions can be established with the 5G network, and one or more QoS flows can be established in each PDU session. Each QoS flow Identified by a QoS Flow Identifier (QFI), QFI uniquely identifies a QoS flow in a PDU session.

In the process of the UE requesting activation of a certain service, or in the process of handover and service request due to the movement of the UE, the radio access network (RAN) node may reject a PDU due to the lack of available radio resources in the base station Some QoS flows in the session, or session management function (Session Management function, SMF) rejects a PDU session due to the unavailability of resources on the user plane function (User Plane Function, UPF) corresponding to the QoS flow in the PDU session Some of the QoS flows.

There are often some more complex applications in the network, which may trigger multiple QoS flows in a PDU session. These QoS flows are closely related. For example, for remote driving applications, the controller needs to receive the video stream of the vehicle in the first place. To observe driving conditions in real time; the second aspect needs to receive vehicle warning messages; the third aspect needs to send remote driving control instructions. These three types of data flows need to be carried in different QoS flows in the same PDU session. However, the RAN node or SMF may reject part of the QoS flow associated with each other. In this way, due to the lack of the QoS flow of some bearer applications, the application cannot operate normally, and the part of the QoS flow that is not rejected has no actual effect but is still occupied Network resources lead to a waste of network resources.

Summary of the invention

The embodiments of the present application provide a communication method and communication device, which can effectively save network resources.

In view of this, the first aspect of the present application provides a communication method, including: a first access network device obtains a set of QoS flows that have an association relationship in a PDU session, and the set of QoS flows includes at least two QoS flows. When there are QoS flows that meet the QoS flow rejection condition in the flow set, the first access network device rejects all QoS flows in the QoS flow set. When any QoS flow in the QoS flow set meets the QoS flow rejection condition, the application corresponding to the any QoS flow can no longer run normally, so all the associated QoS flows are rejected, which effectively saves network resources.

Optionally, in a possible implementation manner of the first aspect, the QoS flows in the set of associated QoS flows respectively correspond to different data services in the same application; or, the associated QoS flows The QoS flows in the set respectively correspond to different applications, and there is a preset association relationship between the different applications. It should be noted that the common feature between the QoS flows that have an association relationship may be associated with the same application, or may be associated with different applications with an association relationship, which improves the scalability of the solution.

Optionally, in a possible implementation manner of the first aspect, the QoS flow that meets the QoS flow rejection condition includes: the QoS flow that cannot be supported by the network resources that are allowed to be allocated in the first access network device The QoS requirements of the QoS flows in the set. The access network equipment can determine whether to reject the QoS flow according to the local network resources, which improves the feasibility of the solution.

Optionally, in a possible implementation manner of the first aspect, the QoS flow parameter of the QoS flow in the PDU session carries an association identifier, and the first access network device determines the corresponding QoS flow parameter with the same association identifier There is an association relationship between QoS flows. The first access network device obtains the specific implementation manner of the QoS flow set having the association relationship in the PDU session, and adds the association identifier for indicating the association relationship to the QoS parameter, so that the access network device can determine which QoS flows are associated.

Optionally, in a possible implementation manner of the first aspect, the first access network device may have multiple ways to obtain QoS flow parameters. Based on different application scenarios, the first access network device may receive data from the first access network device. 2. A handover request message of the access network device, the handover request message carries QoS flow parameters, or the first access network device can receive a handover request message from the AMF, and the handover request message also carries QoS flow parameters, Alternatively, the first access network device may receive a PDU session resource establishment request message from the SMF, where the PDU session resource establishment request message is used to request the first access network device to allocate air interface resources for the PDU session, and the PDU session resource establishment The request message carries QoS flow parameters.

Optionally, in a possible implementation manner of the first aspect, the first access network device may receive indication information used to indicate a QoS flow set, that is, the first access network device may directly determine that it has The QoS flow collection of the association relationship.

Optionally, in a possible implementation manner of the first aspect, the indication information may include an association list, and the association list includes QFI, wherein the QFI in the association list is related to the QoS in the QoS flow set having an association relationship. The streams correspond one to one. The indication information carries an association list, and the first access network device can determine the QoS flow set having an association relationship through the association list, which is different from the implementation manner of determining the QoS set by QoS flow parameters, which improves the flexibility of the solution.

Optionally, in a possible implementation manner of the first aspect, the first access network device may have multiple ways to obtain indication information. Based on different application scenarios, the first access network device may receive information from the second The handover request message of the access network device, the handover request message carries indication information, or the first access network device can receive the handover request message from the AMF, and the handover request message also carries the indication information, or, The first access network device may receive a PDU session resource establishment request message from the SMF. The PDU session resource establishment request message is used to request the first access network device to allocate air interface resources for the PDU session, and the PDU session resource establishment request message Carry instructions. Based on different application scenarios, multiple ways for the first access network device to obtain indication information are provided, which improves the scalability of the solution.

The second aspect of the present application provides a communication method, including: SMF acquires a set of QoS flows with an association in a PDU session, and then the SMF sends indication information to an access network device, and the indication information may indicate the set of QoS flows with an association .

Optionally, in a possible implementation manner of the second aspect, the indication information includes an association list, and the association list includes QFI, wherein the QFI in the association list is related to the QoS flow in the QoS flow set having an association relationship. One to one correspondence.

Optionally, in a possible implementation manner of the second aspect, the SMF receives a notification message from the PCF, where the notification message includes information used to indicate the PCC rule with the association relationship in the PDU session, Furthermore, the SMF can determine the QoS flow set according to the notification message.

Optionally, in a possible implementation of the second aspect, the notification message includes a list of PCC rule identifiers, where the list of PCC rule identifiers includes PCC rule identifiers of PCC rules that have an association relationship.

Optionally, in a possible implementation manner of the second aspect, the SMF may receive the PCC rule from the PCF, where the PCC rule may carry the association identifier, and the SMF may determine the PCC rule carrying the same association identifier If there is an association relationship between them, the SMF can determine that the QoS flows corresponding to these PCC rules also have an association relationship.

Optionally, in some possible implementation manners, the SMF sends a PDU session resource establishment request message carrying indication information to the access network device.

Optionally, in some possible implementation manners, if the SMF receives a response message from the access network device, the SMF stops initiating a request to establish a QoS flow in the QoS flow set according to the response message Or, if the SMF does not receive a response message from the access network device within a preset time, the SMF stops initiating a request to establish a QoS flow in the QoS flow set. In this method, if the SMF receives the message that the QoS flow is rejected from the access network device, or if the SMF does not receive the feedback from the access network device within the preset time, the SMF also defaults that the QoS flow is rejected. In the above case, because there are already rejected QoS flows in the QoS flow set, other QoS flows in the QoS flow set will also be rejected by the access network device, so SMF will not initiate the establishment of other QoS flow sets. The QoS flow saves the operation process of SMF.

The third aspect of the present application provides a communication method, including: SMF obtains a set of QoS flows that have an association relationship in a PDU session, and obtains a first association identifier, and then SMF carries the first association identifier in QoS flow parameters and sends it to the receiver. Network access equipment. In this method, the SMF can add the first association identifier to the QoS flow parameter, and issue the first association identifier to the access network device through the QoS flow parameter, and the access network device can determine that it is associated according to the first association identifier. The QoS flow of the relationship is different from the implementation of the SMF sending instruction information to the access network device, which improves the flexibility of the solution.

Optionally, in a possible implementation manner of the third aspect, the SMF receives a notification message from the PCF, where the notification message includes information used to indicate the PCC rule with the association relationship in the PDU session, Furthermore, the SMF can determine the QoS flow set according to the notification message.

Optionally, in a possible implementation manner of the third aspect, the SMF determines the QoS flow set according to the notification message, and generates the first association identifier for the QoS flow set.

Optionally, in a possible implementation of the third aspect, the SMF receives the PCC rule from the PCF, and the PCC rule may carry the second association identifier, and the SMF may determine the PCC rule carrying the second association identifier If there is an association relationship between them, the SMF can determine that the QoS flows corresponding to these PCC rules also have an association relationship.

Optionally, in a possible implementation of the third aspect, the SMF generates the first association identifier according to the second association identifier obtained from the PCC rules, where the first association identifier and the second association identifier may be the same or different.

Optionally, in a possible implementation manner of the third aspect, the QoS flow parameter may be carried in a PDU session resource establishment request message.

The fourth aspect of the present application provides a communication method, including: SMF obtains a set of QoS flows in a PDU session that has an association relationship, and when there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects the All QoS flows in the QoS flow set. In this method, the SMF obtains a set of QoS flows that have an association relationship in the PDU session, and when there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set. Through the above method, since any QoS flow meets the rejection condition, the application corresponding to the QoS flow cannot run normally, so all the associated QoS flows are rejected, which effectively saves network resources. In addition, SMF rejects The QoS flow set improves the flexibility of this application on the basis of the foregoing embodiment.

Optionally, in a possible implementation manner of the fourth aspect, the QoS flows in the set of associated QoS flows correspond to different data services in the same application; or, the QoS flows with associated relationship The QoS flows in the set respectively correspond to different applications, and there is a preset association relationship between the different applications. The common features between the QoS flows that have an association relationship are listed, that is, the QoS flows in a QoS set can be associated with the same application or different applications with an association relationship, which improves the scalability of the solution.

Optionally, in a possible implementation manner of the fourth aspect, the QoS flow that meets the QoS flow rejection condition includes: the resources on the user plane function UPF corresponding to the QoS flow in the QoS flow set cannot be used .

Optionally, in a possible implementation manner of the fourth aspect, the SMF receives a notification message from the PCF, where the notification message includes information used to indicate the PCC rule with the association relationship in the PDU session, Furthermore, the SMF can determine the QoS flow set according to the notification message.

Optionally, in a possible implementation manner of the fourth aspect, the SMF sends indication information including an association list to the access network device, where the indication information is used to indicate QoS flows with an association relationship, and the association list includes The QoS flow identifier QFI of the QoS flow in the QoS flow set.

Optionally, in some possible implementation manners, the SMF receives the PCC rules from the PCF, where the PCC rules may carry the first association identifier, and the SMF may determine that the PCC rules carrying the first association identifier have Association relationship, then SMF can determine that the QoS flows corresponding to these PCC rules also have an association relationship.

Optionally, in a possible implementation manner of the fourth aspect, the SMF generates a second association identifier according to the first association identifier, and sends the second association identifier to the access network device, where the first association identifier and The second association identifier can be the same or different.

The fifth aspect of the present application provides a communication method, including: PCF determines the PCC rules associated with the PDU session according to business requirements, and then the PCF sends a notification message to the SMF, where the notification message includes instructions for indicating the PDU session Information about the PCC rules with the association relationship in. In this method, the PCF can determine the PCC rules with the association relationship in the PDU session according to business requirements, and then the SMF can determine the QoS flow with the association relationship according to the notification message sent by the PCF, and then when there is a set of QoS flows that meets the QoS flow rejection condition When QoS flows, SMF or access network equipment can reject all QoS flows in the QoS flow set. When any QoS flow meets the rejection condition, the application corresponding to the QoS flow can no longer run normally, so all associated QoS flows are rejected, which effectively saves network resources.

Optionally, in a possible implementation manner of the fifth aspect, the ARPs in the PCC rules with the association relationship are the same. When network resources are limited, the access network device will preferentially reserve QoS flows with a high ARP level and reject QoS flows with a low ARP level. Then, because these PCC rules and the corresponding QoS flows are all related to each other, The associated QoS flows are either accepted or rejected at the same time, so ARP can be set to the same.

The sixth aspect of the present application provides a communication method, including: the PCF can determine the PCC rule with the association relationship in the PDU session according to business requirements, and then the PCF carries the association identifier in the PCC rule with the association relationship and sends it to the SMF The PCC rule carrying the association identifier.

Optionally, in a possible implementation manner of the sixth aspect, the ARPs in the PCC rules with the association relationship are the same.

A seventh aspect of the present application provides a communication device, including: an obtaining unit, configured to obtain a set of associated quality of service QoS flows in a protocol data unit PDU session, the set of QoS flows including at least two QoS flows; a processing unit, It is used to reject all QoS flows in the QoS flow set when there are QoS flows that meet the QoS flow rejection condition in the QoS flow set.

Optionally, in a possible implementation manner of the seventh aspect, the QoS flows in the set of associated QoS flows correspond to different data services in the same application; or, the associated QoS flows The QoS flows in the set respectively correspond to different applications, and there is a preset association relationship between the different applications.

Optionally, in a possible implementation manner of the seventh aspect, the QoS flow that meets the QoS flow rejection condition includes: the QoS flow that cannot be supported by the network resources allowed to be allocated in the first access network device The QoS requirements of the QoS flows in the set.

Optionally, in a possible implementation manner of the seventh aspect, the acquiring unit is specifically configured to: determine the QoS flow set according to the associated identifier in the QoS flow parameter of the QoS flow in the PDU session, so The QoS flow set includes QoS flows with the same association identifier in the PDU session.

Optionally, in a possible implementation manner of the seventh aspect, the acquiring unit is further configured to: receive a handover request message from a second access network device, where the handover request message includes the QoS flow parameter Or, receiving a handover request message from the access and mobility management function AMF, the handover request message including the QoS flow parameters; or, receiving a PDU session resource establishment request message from the session management function SMF, the PDU The session resource establishment request message includes the QoS flow parameter, and the PDU session resource establishment request message is used to request the first access network device to allocate air interface resources for the PDU session.

Optionally, in a possible implementation manner of the seventh aspect, the acquiring unit is specifically configured to receive indication information, where the indication information is used to indicate the QoS flow set.

Optionally, in a possible implementation manner of the seventh aspect, the indication information includes an association list, and the association list includes a QoS flow identifier QFI of a QoS flow in the QoS flow set; the QoS flow set includes : The QoS flow corresponding to the QFI in the PDU session.

Optionally, in a possible implementation manner of the seventh aspect, the acquiring unit is further configured to: receive a handover request message from a second access network device, where the handover request message includes the indication information; Or, receiving a handover request message from AMF, the handover request message including the indication information; or, receiving a PDU session resource establishment request message from SMF, the PDU session resource establishment request message including the indication information.

An eighth aspect of the present application provides a communication device, including: an acquiring unit, configured to acquire a set of QoS flows having an association relationship in a PDU session; and a sending unit, configured to send instruction information to an access network device, where the instruction information is used for Indicates the set of QoS flows.

Optionally, in a possible implementation manner of the eighth aspect, the association list includes a QoS flow identifier QFI of a QoS flow in the QoS flow set, and the QoS flow set includes the PDU session with the QoS flow corresponding to QFI.

Optionally, in a possible implementation manner of the eighth aspect, the acquiring unit is specifically configured to: receive a notification message from the PCF, where the notification message includes instructions for indicating that the PDU session has the association relationship Information about the PCC rules; determine the QoS flow set according to the notification message.

Optionally, in a possible implementation manner of the eighth aspect, the notification message includes a list of PCC rule identifiers, and the list of PCC rule identifiers includes PCC rule identifiers of the PCC rules having an association relationship.

Optionally, in a possible implementation manner of the eighth aspect, the acquiring unit is specifically configured to: receive a PCC rule of the PDU session from a PCF, where the PCC rule includes an association identifier; and according to the PCC rule , Determine the QoS flow set.

Optionally, in a possible implementation manner of the eighth aspect, the sending unit is specifically configured to send a PDU session resource establishment request message to the access network device, where the PDU session resource establishment request message includes The instruction information.

Optionally, in a possible implementation manner of the eighth aspect, the SMF further includes: a processing unit, configured to: if the SMF receives a response message from the access network device, use the response Message, stop initiating a request to establish a QoS flow in the QoS flow set, and the response message indicates that there is a rejected QoS flow in the QoS flow set; or, if the SMF does not receive a request from all The response message of the access network device stops initiating a request to establish a QoS flow in the QoS flow set.

A ninth aspect of the present application provides a communication device, including: an acquiring unit, configured to acquire a set of QoS flows having an association relationship in a PDU session; a processing unit, configured to acquire a first association identifier; The device sends the QoS flow parameter of the QoS flow in the PDU session, where the QoS flow parameter includes the first association identifier.

Optionally, in a possible implementation manner of the ninth aspect, the acquiring unit is specifically configured to: receive a notification message from the PCF, where the notification message includes instructions for indicating that the PDU session has the association relationship Information about the PCC rules; determine the QoS flow set according to the notification message.

Optionally, in a possible implementation manner of the ninth aspect, the processing unit is specifically configured to: generate the first association identifier according to the notification message.

Optionally, in a possible implementation manner of the ninth aspect, the acquiring unit is specifically configured to: receive a PCC rule of a PDU session from a PCF, where the PCC rule includes a second association identifier; according to the PCC rule , Determine the QoS flow set.

Optionally, in a possible implementation manner of the ninth aspect, the processing unit is specifically configured to: generate the first association identifier according to the second association identifier.

Optionally, in a possible implementation manner of the ninth aspect, the QoS flow parameter is carried in a PDU session resource establishment request message.

A tenth aspect of the present application provides a communication device, including: an acquiring unit, configured to acquire a set of QoS flows that have an association relationship in a PDU session; and a processing unit, configured to: When streaming, reject all QoS flows in the QoS flow set.

Optionally, in a possible implementation manner of the tenth aspect, the QoS flows in the set of associated QoS flows correspond to different data services in the same application; or, the associated QoS flows The QoS flows in the set respectively correspond to different applications, and there is a preset association relationship between the different applications.

Optionally, in a possible implementation manner of the tenth aspect, the QoS flow that meets the QoS flow rejection condition includes: resources on the user plane function UPF corresponding to the QoS flow in the QoS flow set cannot be used .

Optionally, in a possible implementation manner of the tenth aspect, the acquiring unit is specifically configured to:

Receiving a notification message from the PCF, the notification message including information used to indicate the PCC rule having the association relationship in the PDU session; and determining the QoS flow set according to the notification message.

Optionally, in a possible implementation manner of the tenth aspect, the communication device further includes: a sending unit, configured to send instruction information including an association list to the access network device, where the instruction information is used for Indicate QoS flows having an association relationship, and the association list includes the QoS flow identifier QFI of the QoS flow in the QoS flow set.

Optionally, in a possible implementation manner of the tenth aspect, the acquiring unit is specifically configured to: receive a PCC rule of the PDU session from a PCF, where the PCC rule includes a first association identifier; according to the The PCC rule determines the QoS flow set.

Optionally, in a possible implementation manner of the tenth aspect, the sending unit is further configured to send a second association identifier generated according to the first association identifier to the access network device, where the first association identifier and the first association identifier The two association identifiers can be the same or different.

An eleventh aspect of the present application provides a communication device, including: a determining unit, configured to determine the PCC rules associated with a PDU session according to business requirements; and a sending unit, configured to send a notification message to the SMF, the notification message including Information used to indicate the PCC rule having the association relationship in the PDU session.

Optionally, in some possible implementation manners, the ARPs in the PCC rules with the association relationship are the same.

A twelfth aspect of the present application provides a communication device, including: a determining unit, configured to determine the PCC rule with an association relationship in a PDU session according to business requirements; and a processing unit, configured to carry an association identifier in the associated relationship In the PCC rule; the sending unit is used to send the PCC rule carrying the association identifier to the SMF.

A thirteenth aspect of the present application provides a communication device, including: a processor and a memory, the memory is stored with program code, and when the processor calls the program code in the memory, it executes the above-mentioned first to sixth aspects. The method described in any optional embodiment of the aspect.

The fourteenth aspect of the present application provides a computer-readable storage medium, including instructions, when the instructions are run on a computer, the computer executes as described in any optional implementation manner of the first to sixth aspects of the present application Methods.

The fifteenth aspect of the present application provides a computer program product, which when it runs on a computer, causes the computer to execute the method described in any optional implementation manner of the first to sixth aspects of the present application.

It can be seen from the above technical solutions that the embodiments of this application have the following advantages:

In the embodiment of the present application, the first access network device obtains the associated QoS flow set in the PDU session, and when any QoS flow in the QoS flow set meets the QoS flow rejection condition, the first access network device rejects the QoS All QoS flows in the flow set. Through the above method, when any QoS flow meets the rejection condition, the application corresponding to the QoS flow can no longer run normally, so all the QoS flows that have an association relationship are rejected, which effectively saves network resources.

Description of the drawings

Figure 1 is a system architecture diagram of the application;

Figure 2 is a QoS flow model diagram under a 5G network;

FIG. 3 is a schematic diagram of an embodiment of a communication method based on an access network device in an embodiment of this application;

FIG. 4 is a schematic diagram of an embodiment of a communication method based on SMF in an embodiment of the application;

FIG. 5 is a schematic diagram of another embodiment of a communication method based on SMF in an embodiment of this application;

6 is a schematic diagram of an embodiment of a PCF-based communication method in an embodiment of this application;

FIG. 7 is a schematic diagram of a flow of acquiring a QoS flow set by an access network device and SMF in an embodiment of the application;

FIG. 8 is a schematic flowchart of an application scenario of the communication method in an embodiment of the application;

FIG. 9 is a schematic flowchart of another application scenario of the communication method in an embodiment of this application;

10 is a schematic flowchart of another application scenario of the communication method in an embodiment of this application;

FIG. 11 is a schematic diagram of an embodiment of a communication device in an embodiment of this application;

FIG. 12 is a schematic diagram of another embodiment of a communication device in an embodiment of this application;

FIG. 13 is a schematic diagram of another embodiment of a communication device in an embodiment of this application;

FIG. 14 is a schematic diagram of another embodiment of a communication device in an embodiment of this application;

15 is a schematic diagram of a structure of a communication device in an embodiment of the application;

FIG. 16 is a schematic diagram of a communication system in an embodiment of this application.

detailed description

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of this application.

The terms "first", "second", "third", "fourth", etc. (if any) in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and do not have to be used To describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any variations of them are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to the clearly listed Those steps or units may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

The upgrading of mobile communication technology is bound to bring many innovative applications to all walks of life. Mobile broadband, multimedia, machine type communication (MTC), industrial control, and intelligent transportation system (ITS, intelligent transportation system) will Become the main use case in the 5G era. In order to meet widely changing service requirements, 5G networks will be constructed in a flexible manner. Therefore, 5G introduces Network Slice technology. Network slice technology cuts a physical network into multiple virtual end-to-end networks. The virtual networks, including the equipment, access technology, transmission path and core network within the network, are logically independent. Each network slice is constituted by an independent network function or function combination instantiation, with different functional characteristics, and facing different needs and services. The separation of network slicing allows different users and user groups to flexibly and dynamically define and customize network capabilities according to their different application scenarios and needs, without affecting each other.

The system architecture or scenario of the main application of this application is shown in Figure 1. The functions of the main network elements in the system architecture are as follows:

Access network equipment: Realize physical layer functions, resource scheduling management, access control, and mobility management functions. The access network equipment is connected to the UPF through the user plane interface N3 to transmit data from the terminal equipment; the access network equipment establishes the control plane through the control plane interface N2 and access and mobility management function (AMF) Signaling connection is used to implement functions such as access bearer control.

It should be noted that the access network equipment in this application may be a long-term evolution (LTE) system or an evolution type in an authorized auxiliary access long-term evolution (LAA-LTE) system Base station (evolutional Node B, which can be referred to as eNB or e-NodeB for short), macro base station, micro base station (also known as "small base station"), pico base station, access point (AP), transmission point (transmission point, TP) or a base station in a new radio (NR) system, for example, a new generation Node B (gNodeB), etc.

AMF: Mainly responsible for user equipment (User Equipment, UE) authentication, UE mobility management, network slice selection, session management function (session management function, SMF) selection and other functions. AMF serves as the anchor point of the N1 and N2 signaling connection SMF provides routing of session management messages and maintains and manages UE status information.

SMF: Mainly responsible for all control plane functions of UE session management, including PF selection, Internet Protocol (Internet Protocol, IP) address allocation, session QoS management, and obtaining policy and charging control from the policy control function (PCF) (policy and charging control, PCC) rules, etc.

UPF: As the anchor point of the protocol data unit (PDU) session connection, it is responsible for data message filtering, data transmission/forwarding, rate control, and charging information generation for user equipment.

Refer to Figure 2. In the 5G system, in order to ensure the end-to-end service quality of the service, a 5G QoS model based on the quality of service (QoS) flow is proposed. For a user equipment (User Equipment, UE), one or more protocol data unit (PDU) sessions can be established with the 5G network, and one or more QoS flows can be established in each PDU session. Each QoS flow Identified by a QoS Flow Identifier (QFI), QFI uniquely identifies a QoS flow in a PDU session.

This 5G QoS model supports QoS flows with guaranteed bit rate and QoS flows with no guaranteed bit rate. A QoS flow can be a QoS flow with a guaranteed bit rate or a QoS flow with no bit rate guaranteed.

For a QoS flow with a guaranteed bit rate, the following QoS parameters can be included: 5G QoS identifier (5G QoS Identifier, 5QI), allocation and retention priority (ARP), guaranteed flow bit rate (guaranteed flow bit) rate, GFBR) and maximum flow bit rate (MFBR), optionally including notification control (notification control).

For a QoS flow that does not guarantee a bit rate, the following QoS parameters can be included: 5QI, ARP; optionally, a reverse QoS attribute (Reflective QoS Attribute, RQA) can be included.

The meanings of the above QoS parameters are as follows:

5QI: is a scalar quantity used to index the corresponding 5G QoS features. 5QI is divided into standardized 5QI, pre-configured 5QI, and dynamically allocated 5QI. For the standardized 5QI, there is a one-to-one correspondence with a set of standardized 5G QoS characteristic values; for the pre-configured 5QI, the corresponding 5G QoS characteristic values are pre-configured in the access network node (access network, AN); for the dynamically allocated 5QI, The corresponding 5G QoS features are included in the QoS configuration file and sent to the AN.

ARP: Contains priority, preemptive ability, and preemptive ability.

RQA: Used to indicate that the service that uses the corresponding QoS stream transmission uses reverse QoS.

notification control: Used to indicate whether the access network device will notify the network when the GFBR cannot be satisfied during the QoS flow usage period.

GFBR: Represents the bit rate expected to be provided to a QoS stream with a guaranteed bit rate.

MFBR: Limit the bit rate provided to a QoS stream with a guaranteed bit rate, that is, the maximum bit rate provided to a QoS stream with a guaranteed bit rate. If the bit rate is exceeded, the data packet can be discarded.

During the establishment of the QoS flow, the SMF determines the establishment of the QoS flow according to the local policy or the PCC rules sent by the PCF. Specifically, in the first aspect, the SMF sends service data flow (SDF) information to the UPF, which includes QoS control Information; In the second aspect, SMF sends the QoS profile of the QoS flow to the AN through AMF; in the third aspect, SMF sends QoS rules to the UE through AMF and AN. After that, the UE, AN, and UPF can establish a QoS flow connection for the QoS flow. Specifically, the AN establishes a data radio bearer (DRB) for the air interface according to the QoS configuration file, and stores the QoS flow and the DBR. Binding relationship. For downlink transmission, when UPF receives a downlink data packet, it executes QoS control according to the SDF information sent by SMF, including the QFI in the data packet. When AN receives the downlink data packet, it is based on the QFI in the packet header and the corresponding QoS flow and The binding relationship of the DRB is to place the data packet on the corresponding DRB for transmission; for uplink transmission, when the UE determines to send the uplink data packet, it determines the QoS flow according to the QoS rules, and carries the QFI in the header, according to the binding of the QoS flow and the DBR Relation, put the data packet on the corresponding DRB for transmission, when AN receives the uplink data packet, according to the QFI in the packet header, the data packet header between AN and UPF contains QFI, and UPF verifies when it receives the data packet sent by AN Whether the data packets are transmitted using the correct QoS flow.

In the process of the UE requesting activation of a certain service, or in the process of handover and service request due to the movement of the UE, the access network equipment may reject some QoS flows in a PDU session due to the lack of available radio resources in the base station, or The SMF rejects some QoS flows in a certain PDU session because the resources on the UPF corresponding to the QoS flows in the PDU session are not available. However, there are often some more complex applications in the network, which may trigger multiple QoS flows in a PDU session. There are close connections between these QoS flows. For example, in remote driving applications, the controller needs to receive the vehicle’s Video streaming to observe driving conditions in real time; the second aspect needs to receive vehicle warning messages; the third aspect needs to send remote driving control instructions. These three types of data flows need to be carried in different QoS flows in the same PDU session. However, the access network equipment or SMF may reject part of the QoS flows associated with each other. In this way, the application cannot run normally due to the lack of some QoS flows that carry the application, and the part of the QoS flows that are not rejected have no actual effect but still Occupy network resources or make the network resources unavailable for other services, resulting in a waste of network resources.

In order to solve the foregoing problem, an embodiment of the present application provides a communication method, which will be introduced below.

Please refer to FIG. 3, an embodiment of the communication method in this application includes:

301. The access network device obtains a set of QoS flows in a PDU session that have an association relationship.

In this embodiment, the access network device can obtain an associated QoS flow set in an established PDU session. It can be understood that the QoS flow set includes at least two QoS flows.

Among them, the QoS flows in the set of associated QoS flows may correspond to different data services in the same application, or the QoS flows in the set of associated QoS flows may correspond to different applications, and these different applications There is a preset relationship between.

It should be noted that the PCF can receive a service request from an application function (AF). The service request can correspond to multiple types of service data flow (service data flow, SDF), and the successful operation of the service requires it. All corresponding types of SDFs can run successfully. Therefore, these SDFs corresponding to the same service are associated with each other. In addition, each type of SDF has its corresponding policy and charging control (policy and charging control). , PCC) rules, then the PCF can determine that these PCC rules also have an association relationship, and then the SMF can determine that the QoS flows established according to these associated PCC rules also have an association relationship. For example, for remote driving services, the controller needs to receive the video stream of the vehicle to observe the driving conditions in real time, the second aspect needs to receive vehicle warning messages, and the third aspect needs to send remote driving control commands. Types of SDF correspond to the same service, that is, the three types of SDFs have an association relationship, and these three types of SDFs need to be carried in different QoS flows in the same PDU session, so they are used to carry the above three types respectively. There is an association relationship between the QoS flows of the type of SDF.

Optionally, there are multiple implementation ways for the access network device to obtain the associated QoS flow set, which will be introduced separately as follows:

Manner 1: The access network device determines the QoS flow set according to the associated identifier in the QoS flow parameter of the QoS flow in the PDU session.

Exemplarily, the access network device receives a handover request message from another access network device, and the handover request message includes the above-mentioned QoS flow parameters; or, the access network device receives a handover request message from AMF, the handover request message Or, the access network device receives the PDU session resource establishment request message from the SMF, and the PDU session resource establishment request message includes the above QoS flow parameters, where the PDU session resource establishment request message can be used for Request the first access network device to allocate air interface resources for the PDU session.

Further, the access network device regards QoS flows that include the same association identifier in the QoS flow parameters as a set of QoS flows having an association relationship.

It can be understood that each QoS flow in the PDU session has corresponding QoS flow parameters.

For example, the QoS flow parameters corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 all include association identifier 1, and the QoS flow parameters corresponding to QoS flow 4, QoS flow 5, and QoS flow 6 all include association identifiers. 2. It can be seen that QoS flow 1, QoS flow 2 and QoS flow 3 have an association relationship, and QoS flow 4, QoS flow 5 and QoS flow 6 have an association relationship.

It should be noted that the QoS flow parameters may also include other information such as a QoS configuration file. In addition, the message names mentioned in this application are only exemplary descriptions, and the details are not limited here.

Manner 2: The access network device can determine the QoS flow set according to the indication information used in the PDU session to indicate the QoS flow with the association relationship. Specifically, the indication information may include an association list, and the association list may include QFIs having an association relationship.

Since each QoS flow has a unique corresponding QFI, the QoS flows corresponding to the QFIs in the association list have an association relationship. For example, if the association list includes QFI1, QFI2, and QFI3, then the access network equipment It can be determined that there is an association relationship between QoS flow 1, QoS flow 2, and QoS flow 3 respectively corresponding to QFI1, QFI2, and QFI3.

Exemplarily, the access network device receives a handover request message from another access network device, and the handover request message includes the foregoing indication information; or, the access network device receives a handover request message from the AMF, and the handover request message includes The above indication information is included; or, the access network device receives the PDU session resource establishment request message from the SMF, and the PDU session resource establishment request message includes the above indication information.

302. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the access network device rejects all QoS flows in the QoS flow set.

In step 302, the access network may determine that there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, that is, there is an unacceptable QoS flow in the QoS flow set, or that any QoS flow in the QoS flow set meets QoS Flow rejection condition, the access network device will reject all QoS flows in the QoS flow set together.

Exemplarily, the access network device may determine, according to local network resources, that there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, that is, if the network resources allowed in the access network device cannot support part of the QoS flow set Or all QoS flows, the access network device determines that there are QoS flows that meet the QoS flow rejection condition in the QoS flow set.

For rejected QoS flows, the access network device sends a list of rejected QoS flows to the corresponding SMF to trigger the SMF to initiate the process of deleting the rejected QoS flows; or to trigger the SMF to initiate deletion or deactivation of the rejected QoS flows The QoS parameter information on the corresponding UPF, but the SMF retains the parameter information of the QoS flow. It should be noted that the access network device will save the parameter information of the QoS flow (for example, QFI, ARP, 5QI, etc.). In addition, the access network device will also establish a mapping relationship with the DRB for the QoS flow; For a certain QoS flow that cannot be accepted, the access network device will not save the parameter information of the QoS flow, nor will it establish a mapping relationship with the DRB for the QoS flow. It is understandable that for accepted QoS flows, the access network device will also send a list of accepted QoS flows to the corresponding SMF.

In this embodiment, the access network device obtains the associated QoS flow set in the PDU session. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the access network device rejects all QoS in the QoS flow set. flow. Through the above method, when any QoS flow meets the rejection condition, the application corresponding to the QoS flow can no longer run normally, so all the QoS flows that have an association relationship are rejected, which effectively saves network resources.

Please refer to Figure 4, this application provides another communication method, including:

401. The SMF acquires a set of QoS flows that have an association relationship in the PDU session.

In this embodiment, the SMF can determine a set of QoS flows with an association relationship according to an instruction from the PCF, and there can be multiple specific implementation manners, which are respectively introduced below.

Method 1: The SMF receives a notification message from the PCF. The notification message includes information indicating the PCC rules with the association in the PDU session. After receiving the notification message, the SMF can learn the PCC rules with the association. Each PCC rule has a corresponding QoS flow, and then SMF can determine the set of QoS flows with the association relationship according to the PCC rules with the association relationship. It should be noted that the PCC rule can correspond to the QoS flow one-to-one, or it can be multiple PCCs. The rule corresponds to a QoS flow, which is not specifically limited here.

For example, the notification message used to indicate the information of the PCC rules associated in the PDU session may be a list of PCC rule identifiers. The list of PCC rule identifiers includes PCC rule ID1, PCC rule ID2, and PCC rule ID3. Then the SMF can determine which PCC rule ID1, PCC rule ID2, and PCC rule ID3 corresponding to QoS flow 1, QoS flow 2, and QoS flow 3 have an association relationship. Or, PCC rule ID1 and PCC rule ID2 correspond to QoS flow 1, and PCC rule ID3 corresponds to QoS flow 2, so there is an association relationship between QoS flow 1 and QoS flow 2.

Method 2: SMF receives PCC rules carrying association identifiers from PCF, where PCC rules carrying the same association identifiers have an association relationship, and then SMF can determine a set of QoS flows with an association relationship according to the PCC rules with association relationship .

For example, PCC rule 1, PCC rule 2, and PCC rule 3 all carry association identifier 1, then SMF can determine that PCC rule 1, PCC rule 2 and PCC rule 3 have an association relationship, and then respectively with PCC rule 1, PCC QoS flow 1, QoS flow 2, and QoS flow 3 corresponding to rule 2 and PCC rule 3 also have an association relationship.

It should be noted that the description of the QoS set with the association relationship is similar to the description of step 301 in the embodiment shown in FIG. 3, and details are not repeated here.

402. The SMF sends indication information and/or QoS flow parameters to the access network device.

In this embodiment, after the SMF obtains the associated QoS flow set, the SMF sends instruction information to the access network device, and may also send QoS flow parameters to the access network device.

Specifically, step 402 may correspond to the two implementation manners in which the access network device obtains a set of QoS flows having an association relationship described in step 301 in the embodiment shown in FIG. 3.

Exemplarily, the SMF receives the notification message from the PCF, can generate indication information including the association list, and send the indication information to the access network device; or, if the SMF receives the PCC rule carrying the association identifier from the PCF, it can Obtain the QoS flow with the association relationship, then generate the indication information containing the association list, and send the indication information to the access network device; or, if the SMF receives the PCC rule carrying the association identifier from the PCF, then the SMF can directly The association identifier of the PCC rule is used as the association identifier of the QoS flow, and then it is added to the QoS flow parameters, and the QoS flow parameter carrying the association identifier is sent to the access network device; or, the SMF receives the notification message from the PCF, then the SMF can Generate the association identifier of the QoS flow according to the notification message, add the association identifier of the QoS flow to the QoS flow parameters, and send the QoS flow parameter carrying the association identifier of the QoS flow to the access network device.

It should be noted that the association identifier carried in the PCC rules and the association identifier carried in the QoS flow parameters can be the same or different. That is, the SMF can directly add the second association identifier issued by the PCF to the QoS flow parameters, or it can be A new first association identifier is allocated to the QoS flow set with an association relationship, and the new first association identifier is added to the QoS flow parameters.

Optionally, the SMF carries the indication information and/or QoS flow parameters in the PDU session resource establishment request message and sends it to the access network device.

Optionally, the above method further includes: if the SMF receives a response message from the access network device, the response message indicates that there is a rejected QoS flow in the QoS flow set, then the SMF may stop initiating a request to establish a QoS flow according to the response message The QoS flows in the set, or, if the SMF does not receive a response message from the access network device within the preset time, the SMF can stop initiating a request to establish a QoS flow in the QoS flow set.

The above describes the situation in which all QoS flows in the QoS flow set are rejected by the access network device when there are QoS flows that meet the QoS flow rejection conditions in the QoS flow set. In addition, the SMF can also reject QoS flows, as described below.

Please refer to Figure 5. This application provides another communication method, including:

501. The SMF obtains a set of QoS flows that have an association relationship in a PDU session.

In this embodiment, step 501 is similar to step 401 in the embodiment shown in FIG. 4, and details are not repeated here.

502. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set.

Specifically, the SMF can determine that there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, and the SMF will reject all QoS flows in the QoS flow set.

Exemplarily, if the resources on the UPF corresponding to some or all of the QoS flows in the QoS flow set cannot be used, it means that some or all of the QoS flows meet the QoS flow rejection condition, and the SMF rejects all QoS flows in the QoS flow set. .

Specifically, for example, the PCF will initiate a request to establish a QoS flow to the SMF. If a certain QoS flow is rejected by the SMF, it means that the establishment of the QoS flow has failed. The SMF will not store the context of the QoS flow, and the SMF will not The access network device initiates a request to establish the QoS flow.

For another example, during the UE handover process, the SMF will receive a list of QoS flows that request handover from the access network device. For the QoS flows rejected and accepted by the SMF, the SMF will return the rejected QoS flows to the access network device. List and/or accepted QoS flow list; further optional, SMF initiates the process of deleting the rejected QoS flow, or SMF initiates the deletion or deactivation of the QoS parameter information of the rejected QoS flow on the corresponding UPF, but the SMF The parameter information of the QoS flow is retained.

For another example, SMF receives a request from AMF to activate a PDU session. The PDU session contains a set of QoS flows, thereby triggering the establishment of QoS flows. If a certain QoS flow is rejected by SMF, SMF will not initiate the establishment to the access network device. The request for this QoS flow.

In this embodiment, the SMF obtains a set of QoS flows that have an association relationship in the PDU session. When there are QoS flows that meet the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set. Through the above method, since any QoS flow meets the rejection condition, the application corresponding to the QoS flow cannot run normally, so all the associated QoS flows are rejected, which effectively saves network resources. In addition, SMF rejects The QoS flow set improves the flexibility of this application on the basis of the foregoing embodiment.

As can be seen from the above description, the association relationship between QoS flows comes from the association relationship between PCC rules, and the association relationship between PCC rules is generated by PCF. The following further introduces this application from the PCF side:

Please refer to Figure 6, this application provides another communication method, including:

601. The PCF determines the associated PCC rules in the PDU session according to business requirements.

In this step 601, the PCF can receive the service request from the AF. The service request can correspond to multiple types of SDFs. Since the successful operation of the service requires all types of SDFs corresponding to it to be able to operate successfully, these are the same There is an association relationship between SDFs corresponding to a business, and each type of SDF has a corresponding PCC rule, then the PCF can determine that these PCC rules are also associated, that is, the PCF can determine the PDU according to the business needs PCC rules that have an association relationship in the session.

602. The PCF sends a notification message and/or PCC rules to the SMF.

Among them, the PCF can send a notification message to the SMF, and can also send a PCC rule to the SMF. The notification message can be used to indicate a PCC rule with an association relationship in the PDU session, and the PCC rule may carry an association identifier.

Specifically, SMF can directly determine the PCC rules that have an association relationship according to the instructions of the notification message. SMF can also find which PCC rules include the same association identifier in the received PCC rules, and the SMF can determine the PCC rules that include the same association identifier. There is an association relationship between.

It should be noted that the PCF can add each PCC rule to a different message and send it to the SMF. In addition, the PCF can also add multiple PCC rules to the same message and send it to the SMF. The specifics are not limited here.

Optionally, the above method further includes: the PCF sets the ARPs in the PCC rules with the association relationship to be the same. For example, when network resources are limited, the access network device will preferentially reserve QoS flows with a high ARP level and reject QoS flows with a low ARP level. Then, because these PCC rules and the corresponding QoS flows are related to each other , QoS flows related to each other are either accepted or rejected at the same time, so ARP can be set to the same.

In this embodiment, the PCF can determine the PCC rules that have an association relationship in the PDU session according to the business requirements, and then the SMF can determine the QoS flow with the association relationship according to the notification message sent by the PCF or the PCC rule, and then when there is a set of QoS flows that meets the QoS When the flow rejects the conditional QoS flow, the SMF or the access network device can reject all QoS flows in the QoS flow set. When any QoS flow meets the rejection condition, the application corresponding to the QoS flow can no longer run normally, so all the QoS flows that have an association relationship are rejected, which effectively saves network resources.

The following describes the related QoS flow set in the SMF and the access network device acquiring the PDU session in this application in combination with specific scenarios.

Please refer to Figure 7. This application provides another communication method, including:

701. The PCF sends a notification message and/or PCC rules to the SMF.

Among them, when the UE initiates a certain service, the PCF can be triggered to initiate a QoS flow establishment process. In this process, the PCF can send notification messages and/or PCC rules to the SMF. The detailed description is the same as in the embodiment shown in Figure 6 above. Step 602 of is similar, and will not be repeated here.

702. The SMF obtains a set of QoS flows that have an association relationship in the PDU session.

Wherein, step 702 may be similar to step 401 in the embodiment shown in FIG. 4, and will not be repeated here.

703. The SMF sends a N1 and N2 interface information transmission message to the AMF.

Among them, the N1 and N2 interface information transmission messages may carry indication information and/or QoS flow parameters containing an associated identifier. Exemplarily, the SMF may request the AMF to send the indication information and/or the QoS flow parameter containing the association identifier to the access network device through the N1 and N2 interface information transmission messages.

The description of the indication information and the QoS flow parameters containing the associated identifier is similar to step 301 in the embodiment shown in FIG. 3, and will not be repeated here.

704. The AMF sends an N2 interface PDU session request to the access network device.

Among them, the AMF may send an N2 interface PDU session request (N2PDU Session Request) to the access network device, and the N2 interface PDU session request may carry indication information and/or QoS flow parameters containing an associated identifier.

705. The access network device obtains an associated QoS flow set in the PDU session.

Wherein, step 705 may be similar to step 301 in the embodiment shown in FIG. 3, and will not be repeated here.

The embodiment shown in FIG. 7 above specifically describes the implementation manner in which SMF and the access network device obtain the associated QoS flow set in the PDU session. The following further combines multiple different application scenarios on the basis of the embodiment shown in FIG. 7 The process of rejecting QoS flows in this application is introduced.

Scenario 1. Scenarios for handover between base stations based on the Xn interface.

Referring to Figure 8, this application provides another communication method. The method is based on the above scenario 1. In the following, the UE is handed over from the second access network device (which can be called the source base station) to the first access network device (which can be called the source base station). The target base station) is described as an example, and the details are as follows.

801. The second access network device sends a handover request message to the first access network device.

Exemplarily, in a handover scenario caused by the movement of the UE, the second access network device triggers a handover based on the Xn interface, and the second access network device sends a handover request message to the first access network device.

Wherein, the handover request message may carry indication information and/or QoS flow parameters containing an associated identifier.

802. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the first access network device rejects all QoS flows in the QoS flow set.

Wherein, step 802 may be similar to step 302 in the embodiment shown in FIG. 3, and will not be repeated here.

803. The first access network device sends a handover response message to the second access network device.

804. The first access network device sends a path switching request to the AMF.

The path switching request may be used to request the establishment of a signaling connection on the N2 interface between the first access network device and the AMF. The path switching request may carry the access network tunnel information of the PDU session, the list of accepted QoS flows and/or the list of rejected QoS flows.

805. The AMF sends a session management context update request to the SMF for the PDU session.

The update session management context request can be used to update the PDU session context information of the UE.

806. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set.

It should be noted that both step 806 and step 802 may be optional steps, and 802 may be selected to be executed, or 806 may be selected to be executed, or 802 may be executed as well as 806. The details are not limited here. For example, if the first access network device performs step 802, SMF may perform step 806 or not perform step 806. If the SMF performs step 806, the final decision on rejecting the QoS flow is based on the subsequent step 806, and if the first access network does not perform step 802, it means that the SMF does not indicate the indication information or the QoS flow containing the associated identifier. The parameters are sent to the second access network device, so the first access network device cannot obtain the associated QoS flow set. In this case, only accept or reject all QoS flow sets through SMF .

807. The SMF initiates an N4 interface session modification process to the UPF for the PDU session.

808. The SMF sends an update session management context response to the AMF.

Wherein, the update session management context response may carry the core network tunnel information of the PDU session, the list of accepted QoS flows and/or the list of rejected QoS flows.

809. The AMF sends a path switching response to the first access network device.

The path switching response may carry core network tunnel information of the PDU session, a list of accepted QoS flows and/or a list of rejected QoS flows.

810. The first access network device sends a resource release message to the second access network device.

Wherein, the release resource message may be used to indicate that the handover is successful and trigger the second access network device to release the network resources prepared for the UE.

Scenario 2: A scenario where base stations are handed over based on the N2 interface.

Referring to FIG. 9, another embodiment of the communication method in this application includes:

901. The second access network device sends a handover request message to the AMF.

In this embodiment, the second access network device (the source base station) triggers the handover based on the N2 interface. Specifically, the second access network device sends a handover request message to the AMF, and the handover request message contains the PDU session identifier of the western medicine handover. . It is understandable that the QoS flow has been successfully established for the first access network device, and the second access network device is currently required to start to establish the QoS flow. Therefore, the handover request message carries indication information and/or contains an association identifier. QoS flow parameters, where the description of the indication information and the QoS flow parameters containing the associated identifier is similar to step 301 in the embodiment shown in FIG. 3, and will not be repeated here.

902. The AMF sends a session management context update request to the SMF according to the PDU session identifier to request to update the PDU session context information of the UE.

903. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set.

In this embodiment, step 903 is similar to step 502 in the embodiment shown in FIG. 5, and the details will not be repeated here.

904. The SMF sends an update session management context response to the AMF, which carries the core network tunnel information of the PDU session, the list of accepted QoS flows and/or the list of rejected QoS flows.

905. The AMF sends a handover request message to the first access network device, where the handover request message carries core network tunnel information of the PDU session, a list of accepted QoS flows and/or a list of rejected QoS flows. It can be understood that the handover request message may also carry indication information and/or QoS flow parameters containing an associated identifier.

906. When there is a QoS flow meeting the QoS flow rejection condition in the QoS flow set, the first access network device rejects all QoS flows in the QoS flow set.

In this embodiment, step 906 is similar to step 302 in the embodiment shown in FIG. 3, and will not be repeated here. In addition, both step 906 and step 903 may be optional steps. You can choose to execute 903, or you can choose to execute 906, or you can execute 903 and execute 906, which is not specifically limited here. If 903 is executed and 906 is executed, then the final decision on rejecting the QoS flow is based on the subsequent step 906.

907. The first access network device replies to the AMF with a handover response message, which includes the PDU session identifier, the access network tunnel information of the PDU session, the list of accepted QoS flows and/or the list of rejected QoS flows.

908. The AMF sends a session management context update request to the SMF for the PDU session.

909. The SMF initiates an N4 interface session modification process to the UPF for the PDU session.

910. The SMF replies an update session management context response to the AMF.

Scenario 3: A scenario where the UE initiates a request to activate a PDU session.

Referring to FIG. 10, another embodiment of the communication method in this application includes:

1001. The UE sends a service request message to the AMF through an access network device, which carries PDU session indication information, which is used to request the network to activate the PDU session.

1002. For the PDU session indicated in the service request, the AMF sends a session management context update request to the SMF to request activation of the PDU session.

1003. The SMF obtains a set of QoS flows that have an association relationship in the PDU session.

In this embodiment, step 1003 is similar to step 401 in the embodiment shown in FIG. 4, and will not be repeated here.

1004. The SMF sends a PDU session resource establishment request message to the access network device through the AMF, where the PDU session resource establishment request message may carry indication information and/or QoS flow parameters containing an associated identifier, where the indication information and The description of the QoS flow parameter containing the associated identifier is similar to step 301 in the embodiment shown in FIG. 3, and will not be repeated here.

1005. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the access network device rejects all QoS flows in the QoS flow set.

In this embodiment, step 1005 is similar to step 302 in the embodiment shown in FIG. 3, and will not be repeated here.

1006. The access network device replies to the AMF with a PDU session resource establishment response message, which may include the access network tunnel information of the PDU session, the list of accepted QoS flows and/or the list of rejected QoS flows.

1007. The AMF sends a session management context update request to the SMF for the PDU session.

1008. When there is a QoS flow that meets the QoS flow rejection condition in the QoS flow set, the SMF rejects all QoS flows in the QoS flow set.

In this embodiment, both step 1008 and step 1005 may be optional steps. You can choose to execute 1008, or you can choose to execute 1005, or you can execute 1005 and 1008, which is not specifically limited here. If both 1005 and 1008 are executed, then the final decision on rejecting the QoS flow is based on the subsequent step 1008. It is understandable that if the PDU session resource establishment request message sent by the SMF to the access network does not contain indication information and/or QoS flow parameters with an association identifier, the access network device cannot obtain the associated QoS flow. Collection, in this case, only the QoS flow collection can be fully accepted or rejected through SMF.

1009. The SMF initiates an N4 interface session modification process to the UPF for the PDU session.

1010. The SMF replies an update session management context response to the AMF.

The communication method in the embodiment of the present application is described above, and the related device in the embodiment of the present application is described below:

Referring to FIG. 11, an embodiment of the present application provides a communication device. The device may be an access network device, or a chip or a system on a chip located on the access network device. The communication device may include: an acquiring unit 1101 and Processing unit 1102.

The obtaining unit 1101 is configured to obtain a set of associated quality of service QoS flows in a protocol data unit PDU session, where the set of QoS flows includes at least two QoS flows;

The processing unit 1102 is configured to reject all QoS flows in the QoS flow set when there are QoS flows meeting the QoS flow rejection condition in the QoS flow set.

Optionally, the QoS flows in the set of associated QoS flows correspond to different data services in the same application; or,

The QoS flows in the set of associated QoS flows correspond to different applications, and there are preset associations between different applications.

Optionally, the obtaining unit 1101 is specifically configured to:

The QoS flow set is determined according to the correlation identifier in the QoS flow parameters of the QoS flow in the PDU session, and the QoS flow set includes QoS flows with the same correlation identifier in the PDU session.

Optionally, the obtaining unit 1101 is also used for:

Receive a handover request message from the second access network device, where the handover request message includes QoS flow parameters; or,

Receive a handover request message from AMF, and the handover request message includes QoS flow parameters; or,

A PDU session resource establishment request message is received from the SMF. The PDU session resource establishment request message includes QoS flow parameters. The PDU session resource establishment request message is used to request the first access network device to allocate air interface resources for the PDU session.

Optionally, the obtaining unit 1101 is specifically configured to:

Receive indication information, which is used to indicate a QoS flow set.

Optionally, the indication information includes an association list, and the association list includes the QoS flow identifier QFI of the QoS flow in the QoS flow set;

The QoS flow set includes: the QoS flow corresponding to the QFI in the PDU session.

Optionally, the obtaining unit 1101 is also used for:

Receive a handover request message from the second access network device, where the handover request message includes indication information; or,

Receive a handover request message from AMF, and the handover request message includes indication information; or,

Receive the PDU session resource establishment request message from the SMF. The PDU session resource establishment request message includes indication information.

In the embodiment of the present application, each unit module in the communication device can be used to perform all or part of the actions performed by the first access network device or the access network device in the embodiments shown in FIG. 3 and FIG. 7 to FIG. 10. The details are not repeated here.

In this embodiment, the obtaining unit 1101 obtains the associated QoS flow set in the PDU session. When there is a QoS flow meeting the QoS flow rejection condition in the QoS flow set, the processing unit 1102 rejects all QoS flows in the QoS flow set. Through the above method, when any QoS flow meets the rejection condition, the application corresponding to the QoS flow can no longer run normally, so all the QoS flows that have an association relationship are rejected, which effectively saves network resources.

Referring to FIG. 12, an embodiment of the present application provides a communication device, which may be an SMF, or a chip or a system on a chip located on the SMF. The communication device may include: an acquisition unit 1201, a sending unit 1202, and a processing unit 1203.

The obtaining unit 1201 is configured to obtain a set of QoS flows having an association relationship in a PDU session;

The sending unit 1202 is configured to send indication information to the access network device, where the indication information is used to indicate the QoS flow set.

Optionally, the association list includes the QoS flow identifier QFI of the QoS flow in the QoS flow set.

Optionally, the obtaining unit 1201 is specifically configured to:

Receive a notification message from the PCF, where the notification message includes information used to indicate PCC rules that have an association relationship in the PDU session;

According to the notification message, determine the QoS flow set.

Optionally, the obtaining unit 1201 is specifically configured to:

PCC rules for receiving PDU sessions from PCF, the PCC rules include the associated identifier;

According to PCC rules, determine the QoS flow set.

Optionally, the sending unit 1202 is specifically configured to:

Send a PDU session resource establishment request message to the access network device, and the PDU session resource establishment request message includes indication information.

Optionally, SMF also includes:

The processing unit 1203 is configured to, if the SMF receives a response message from the access network device, stop initiating a request to establish a QoS flow in the QoS flow set according to the response message, and the response message indicates that there is a rejected QoS flow in the QoS flow set; or,

If the SMF does not receive a response message from the access network device within the preset time, it stops initiating a request to establish a QoS flow in the QoS flow set.

Another embodiment in which the communication device is an SMF in the embodiment of the present application includes:

The processing unit 1203 is configured to obtain the first association identifier;

The sending unit 1202 is configured to send QoS flow parameters of the QoS flow in the PDU session to the access network device, where the QoS flow parameters include the first association identifier.

Optionally, the obtaining unit 1201 is specifically configured to:

Receiving a notification message from the PCF, the notification message including information used to indicate the PCC rule with the association relationship in the PDU session;

According to the notification message, the QoS flow set is determined.

Optionally, the processing unit 1203 is specifically configured to:

The first association identifier is generated according to the notification message.

Optionally, the obtaining unit 1201 is specifically configured to:

Receiving a PCC rule for a PDU session from a PCF, where the PCC rule includes a second association identifier;

Determine the QoS flow set according to the PCC rule.

Optionally, the processing unit 1203 is specifically configured to:

The first association identifier is generated according to the second association identifier.

Optionally, the QoS flow parameters are carried in the PDU session resource establishment request message.

The processing unit 1203 is configured to reject all QoS flows in the QoS flow set when there are QoS flows meeting the QoS flow rejection condition in the QoS flow set.

Optionally, the QoS flow that meets the QoS flow rejection condition includes: the resource on the UPF corresponding to the QoS flow in the QoS flow set cannot be used.

Optionally, the obtaining unit 1201 is specifically configured to:

Receive a notification message from the PCF, the notification message includes information used to indicate PCC rules that have an association relationship in the PDU session;

According to the notification message, determine the QoS flow set.

Optionally, the obtaining unit 1201 is specifically configured to:

According to PCC rules, determine the QoS flow set.

In the above embodiment where the communication device is an SMF, each unit module in the SMF can specifically perform all or part of the actions performed by the SMF in the embodiments shown in FIG. 4, FIG. 5, and FIG. 7 to FIG. 10. The details are not repeated here. .

Referring to FIG. 13, an embodiment of the present application provides a communication device. The device may be a PCF, or a chip or a system on a chip located on the PCF. The communication device may include a determining unit 1301 and a sending unit 1302.

The determining unit 1301 is configured to determine the PCC rules that have an association relationship in the PDU session according to business requirements;

The sending unit 1302 is configured to send a notification message to the SMF, where the notification message includes information used to indicate the PCC rules having an association relationship in the PDU session.

Optionally, the ARPs in the PCC rules with the association relationship are the same.

In the embodiments of the present application, each unit module in the PCF can specifically perform all or part of the actions performed by the PCF in the embodiments shown in FIG. 6 and FIG. 7, and details are not described herein again.

Referring to FIG. 14, another embodiment in which the communication device in the embodiment of the present application is a PCF includes:

The determining unit 1401 is configured to determine the PCC rules that have an association relationship in the PDU session according to business requirements;

The processing unit 1402 is configured to carry the association identifier in the PCC rule with the association relationship;

The sending unit 1403 is configured to send the PCC rule carrying the association identifier to the SMF.

The above describes the case where the communication devices in the embodiments of the present application are access network equipment, SMF and PCF respectively from the perspective of modular functions, and the following describes the communication equipment in the embodiments of the present application from the perspective of hardware processing:

Please refer to FIG. 15, the communication device in the present application includes one or more central processing units 1501, memory 1502, and communication interface 1503. The central processing unit 1501, memory 1502, and communication interface 1503 are connected to each other through a bus.

The memory 1502 may be short-term storage or persistent storage, for storing related instructions and data, and the communication interface 1503 for receiving and sending data. Furthermore, the central processing unit 1501 may be configured to communicate with the memory 1502 and execute a series of instruction operations in the memory 1502.

The communication devices in the above embodiments may all be based on the structure shown in FIG. 15.

Referring to FIG. 16, an embodiment of the present application also provides a communication system, which includes a communication device. Specifically, the communication device may include the access network device shown in FIG. 11, and the communication device shown in FIG. SMF and the PCF shown in Figures 13 and 14 above, where the access network device can be used to execute the first access network device or the access network device in the embodiment shown in Figure 3 and Figures 7 to 10 All or part of the actions, SMF can perform all or part of the actions performed by the SMF in the embodiments shown in Figure 4, Figure 5, and Figures 7 to 10, and PCF can perform all or part of the actions performed by the PCF in the embodiments shown in Figure 6 and Figure 7 All or part of the action.

Those skilled in the art can clearly understand that, for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

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

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), magnetic disk or optical disk and other media that can store program code .

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, a person of ordinary skill in the art should understand that: The technical solutions recorded in the embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A communication method, characterized in that it comprises:

Acquiring, by the first access network device, a set of associated quality of service QoS flows in a protocol data unit PDU session, the set of QoS flows including at least two QoS flows;

When there is a QoS flow meeting the QoS flow rejection condition in the QoS flow set, the first access network device rejects all QoS flows in the QoS flow set.
The method according to claim 1, wherein the QoS flows in the set of associated QoS flows respectively correspond to different data services in the same application; or,

The QoS flows in the set of QoS flows with an association relationship respectively correspond to different applications, and there is a preset association relationship between the different applications.
The method according to claim 1 or 2, wherein the first access network device acquiring a set of associated quality of service QoS flows in a protocol data unit PDU session comprises:

The first access network device determines the QoS flow set according to the correlation identifier in the QoS flow parameters of the QoS flow in the PDU session, and the QoS flow set includes QoS with the same correlation identifier in the PDU session flow.
The method according to claim 3, wherein the method further comprises:

The first access network device receives a handover request message from a second access network device, where the handover request message includes the QoS flow parameter; or,

The first access network device receives a handover request message from the access and mobility management function AMF, where the handover request message includes the QoS flow parameter; or,

The first access network device receives a PDU session resource establishment request message from a session management function SMF, the PDU session resource establishment request message includes the QoS flow parameter, and the PDU session resource establishment request message is used to request all The first access network device allocates air interface resources for the PDU session.
The method according to claim 1 or 2, wherein the first access network device acquiring a set of associated quality of service QoS flows in a protocol data unit PDU session comprises:

The first access network device receives indication information, where the indication information is used to indicate the QoS flow set.
The method according to claim 5, wherein the indication information includes an association list, and the association list includes a QoS flow identifier QFI of a QoS flow in the QoS flow set;

The QoS flow set includes: the QoS flow corresponding to the QFI in the PDU session.
The method according to claim 6, wherein the method further comprises:

The first access network device receives a handover request message from a second access network device, where the handover request message includes the indication information; or,

The first access network device receives a handover request message from AMF, where the handover request message includes the indication information; or,

The first access network device receives a PDU session resource establishment request message from an SMF, and the PDU session resource establishment request message includes the indication information.
A communication method, characterized in that it comprises:

SMF obtains the set of associated QoS flows in the PDU session of the protocol data unit;

The SMF sends indication information to the access network device, where the indication information is used to indicate the QoS flow set.
The method according to claim 8, wherein the indication information includes an association list, the association list includes a QoS flow identifier QFI of a QoS flow in the QoS flow set, and the QoS flow set includes the PDU session with the QoS flow corresponding to QFI.
The method according to claim 9, wherein said SMF acquiring a set of QoS flows having an association relationship in a PDU session comprises:

The SMF receives a notification message from a PCF, where the notification message includes information used to indicate the policy and charging control PCC rules that have the association relationship in the PDU session;

The SMF determines the QoS flow set according to the notification message.
The method according to claim 10, wherein the notification message includes a list of PCC rule identifiers, and the list of PCC rule identifiers includes PCC rule identifiers of the associated PCC rules.
According to the method of claim 8, the SMF acquiring a set of QoS flows with an association relationship includes:

The SMF receives the PCC rule of the PDU session from the PCF, and the PCC rule includes an association identifier;

The SMF determines the QoS flow set according to the PCC rule.
The method according to any one of claims 8 to 12, wherein the SMF sending instruction information to an access network device includes:

The SMF sends a PDU session resource establishment request message to the access network device, and the PDU session resource establishment request message includes the indication information.
The method according to any one of claims 8 to 12, the method further comprising:

If the SMF receives a response message from the access network device, the SMF stops initiating a request to establish a QoS flow in the QoS flow set according to the response message, and the response message indicates the QoS flow There are rejected QoS flows in the set; or,

If the SMF does not receive a response message from the access network device within a preset time, the SMF stops initiating a request to establish a QoS flow in the QoS flow set.
A communication method, characterized in that it comprises:

SMF obtains a set of QoS flows that have an association relationship in a PDU session;

The SMF obtains the first association identifier;

The SMF sends the QoS flow parameter of the QoS flow in the PDU session to the access network device, where the QoS flow parameter includes the first association identifier.
The method according to claim 15, wherein the SMF acquiring a set of QoS flows having an association relationship in a PDU session comprises:

Receiving, by the SMF, a notification message from a PCF, the notification message including information used to indicate the PCC rule having the association relationship in the PDU session;

The SMF determines the QoS flow set according to the notification message.
The method according to claim 16, wherein said SMF acquiring the first association identifier comprises:

The SMF generates the first association identifier according to the notification message.
The method according to claim 15, wherein the SMF acquiring a set of associated QoS flows in a PDU session comprises:

The SMF receives the PCC rule of the PDU session from the PCF, and the PCC rule includes a second association identifier;

The SMF determines the QoS flow set according to the PCC rule.
The method according to claim 18, wherein said SMF acquiring the first association identifier comprises:

The SMF generates the first association identifier according to the second association identifier.
The method according to any one of claims 15 to 19, wherein the QoS flow parameter is carried in a PDU session resource establishment request message.
A communication method, characterized in that it comprises:

The PCF determines the PCC rules that are associated in the PDU session according to business requirements;

The PCF sends a notification message to the SMF, where the notification message includes information used to indicate the PCC rule with the association relationship in the PDU session.
The method according to claim 21, wherein the ARPs in the PCC rules with the association relationship are the same.
A communication device, characterized by comprising:

An acquiring unit, configured to acquire a set of associated quality of service QoS flows in a protocol data unit PDU session, the set of QoS flows including at least two QoS flows;

The processing unit is configured to reject all QoS flows in the QoS flow set when there are QoS flows meeting the QoS flow rejection condition in the QoS flow set.
The communication device according to claim 23, wherein the QoS flows in the set of associated QoS flows respectively correspond to different data services in the same application; or,

The QoS flows in the set of QoS flows with an association relationship respectively correspond to different applications, and there is a preset association relationship between the different applications.
The communication device according to claim 23 or 24, wherein the acquiring unit is specifically configured to:

The QoS flow set is determined according to the correlation identifier in the QoS flow parameter of the QoS flow in the PDU session, and the QoS flow set includes QoS flows with the same correlation identifier in the PDU session.
The communication device according to claim 25, wherein the acquiring unit is further configured to:

Receiving a handover request message from an access network device, where the handover request message includes the QoS flow parameter; or,

Receive a handover request message from the access and mobility management function AMF, where the handover request message includes the QoS flow parameter; or,

Receive a PDU session resource establishment request message from the session management function SMF, where the PDU session resource establishment request message includes the QoS flow parameter, and the PDU session resource establishment request message is used to request the first access network device to be The PDU session allocates air interface resources.
The communication device according to claim 23 or 24, wherein the acquiring unit is specifically configured to:

Receiving indication information, where the indication information is used to indicate the QoS flow set.
The communication device according to claim 27, wherein the indication information includes an association list, and the association list includes a QoS flow identifier QFI of a QoS flow in the QoS flow set;

The QoS flow set includes: the QoS flow corresponding to the QFI in the PDU session.
The communication device according to claim 28, wherein the acquiring unit is further configured to:

Receiving a handover request message from an access network device, where the handover request message includes the indication information; or,

Receive a handover request message from AMF, where the handover request message includes the indication information; or,

Receive a PDU session resource establishment request message from the SMF, where the PDU session resource establishment request message includes the indication information.
A communication device, characterized by comprising:

The acquiring unit is used to acquire a set of associated quality of service QoS flows in the protocol data unit PDU session;

The sending unit is configured to send indication information to the access network device, where the indication information is used to indicate the QoS flow set.
The communication device according to claim 30, wherein the association list includes the QoS flow identifier QFI of the QoS flow in the QoS flow set, and the QoS flow set includes the QFI corresponding to the QFI in the PDU session. QoS flow.
The communication device according to claim 31, wherein the acquiring unit is specifically configured to:

Receiving a notification message from the PCF, the notification message including information used to indicate the policy and charging control PCC rule with the association relationship in the PDU session;

According to the notification message, the QoS flow set is determined.
The communication device according to claim 32, wherein the notification message includes a list of PCC rule identifiers, and the list of PCC rule identifiers includes PCC rule identifiers of the associated PCC rules.
The communication device according to claim 30, wherein the acquiring unit is specifically configured to:

Receiving the PCC rule of the PDU session from the PCF, where the PCC rule includes an association identifier;

Determine the QoS flow set according to the PCC rule.
The communication device according to any one of claims 30 to 34, wherein the sending unit is specifically configured to:

Send a PDU session resource establishment request message to the access network device, where the PDU session resource establishment request message includes the indication information.
The communication device according to any one of claims 30 to 34, wherein the communication device further comprises:

The processing unit is configured to, if the SMF receives a response message from the access network device, stop initiating a request to establish a QoS flow in the QoS flow set according to the response message, and the response message indicates the There are rejected QoS flows in the QoS flow set; or,

If the SMF does not receive a response message from the access network device within the preset time, stop initiating a request to establish a QoS flow in the QoS flow set.
A communication device, characterized by comprising:

The acquiring unit is used to acquire a set of QoS flows with an association relationship in the PDU session;

A processing unit for obtaining the first association identifier;

The sending unit is configured to send QoS flow parameters of the QoS flow in the PDU session to the access network device, where the QoS flow parameters include the first association identifier.
The communication device according to claim 37, wherein the acquiring unit is specifically configured to:

Receiving a notification message from the PCF, the notification message including information used to indicate the PCC rule with the association relationship in the PDU session;

According to the notification message, the QoS flow set is determined.
The communication device according to claim 38, wherein the processing unit is specifically configured to:

The first association identifier is generated according to the notification message.
The communication device according to claim 37, wherein the acquiring unit is specifically configured to:

Receiving a PCC rule for a PDU session from a PCF, where the PCC rule includes a second association identifier;

Determine the QoS flow set according to the PCC rule.
The communication device according to claim 40, wherein the processing unit is specifically configured to:

The first association identifier is generated according to the second association identifier.
The communication device according to any one of claims 37 to 41, wherein the QoS flow parameter is carried in a PDU session resource establishment request message.
A communication device, characterized by comprising:

The determining unit is used to determine the PCC rules associated with the PDU session according to business requirements;

The sending unit is configured to send a notification message to the SMF, where the notification message includes information used to indicate the PCC rule with the association relationship in the PDU session.
The communication device according to claim 43, wherein the ARPs in the PCC rules with the association relationship are the same.
A communication device, characterized by comprising a processor and a memory, the memory is stored with program code, and when the processor calls the program code in the memory, the program code as described in any one of claims 1 to 22 is executed step.
A computer-readable storage medium, comprising instructions, which when run on a computer, cause the computer to execute the method according to any one of claims 1-22.
A computer program product containing instructions that, when run on a computer, causes the computer to execute the method according to any one of claims 1 to 22.