[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2024074095A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2024074095A1
WO2024074095A1 PCT/CN2023/120642 CN2023120642W WO2024074095A1 WO 2024074095 A1 WO2024074095 A1 WO 2024074095A1 CN 2023120642 W CN2023120642 W CN 2023120642W WO 2024074095 A1 WO2024074095 A1 WO 2024074095A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
information
charging control
quality
policy
Prior art date
Application number
PCT/CN2023/120642
Other languages
English (en)
French (fr)
Inventor
魏鑫鹏
朱奋勤
王丹
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024074095A1 publication Critical patent/WO2024074095A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the present application relates to the field of communication technology, and in particular to a communication method and device.
  • QoS control is a technology used to solve problems such as network delay, congestion, packet loss, jitter, etc., to provide better service capabilities for specified network communications.
  • the finest granularity of QoS control is QoS flow.
  • the service flow of application services is carried by QoS flow. Among them, multiple service flows with the same QoS requirements can be mapped to the same QoS flow.
  • An application service can correspond to multiple service flows, such as video data flows and audio data flows corresponding to game applications.
  • the QoS requirements of these service flows can be different, which means that multiple service flows of the same application service can be mapped to different QoS flows, that is, one application service can correspond to multiple QoS flows.
  • the QoS flows corresponding to an application service need to be managed collaboratively to ensure the normal operation of the service flows of the application service. For example, if some of the multiple QoS flows corresponding to the application service cannot be transmitted due to transmission resources and other reasons, then there is no need to continue to transmit the remaining QoS flows, and the transmission of the remaining QoS flows can be interrupted.
  • a QoS flow can be mapped to multiple service flows with the same QoS requirements and belonging to different application services.
  • Multiple QoS flows corresponding to an application service may carry service flows of other application services. Then, when multiple QoS flows corresponding to the application service are collaboratively managed, the normal transmission of service flows of other application services carried by the multiple QoS flows will be affected.
  • the embodiments of the present application provide a communication method and apparatus for avoiding the problem that the service flows of other application services cannot be transmitted normally due to the collaborative management of multiple QoS flows corresponding to one application service.
  • an embodiment of the present application provides a communication method, which can be executed by a session management function network element, or by a component of the session management function network element.
  • the session management function network element receives a first policy and charging control rule from a policy control function network element, the first policy and charging control rule includes first information, and the first information is used to associate one or more policies and charging control rules corresponding to a first application service; binds the first policy and charging control rule to a first quality of service flow, the first quality of service flow is not bound to the policy and charging control rule that does not include the first information; and sends information of the first quality of service flow to the first network element.
  • the session management function network element receives a first policy and charging control rule from a policy control function network element, the first policy and charging control rule including first information, the first information being used to associate one or more policy and charging control rules corresponding to a first application service; binds the first policy and charging control rule to a first quality of service flow; determines that the first quality of service flow is not bound to a policy and charging control rule that does not include the first information; and sends information about the first quality of service flow to the first network element.
  • the first network element is an access network element or a user plane function network element.
  • the embodiment of the present application does not limit the execution order of the session management function network element sending the information of the first service quality flow to the first network element and the session management function network element determining that the first service quality flow is not bound to the policy and charging control rule that does not include the first information.
  • the session management function network element may send the information of the first service quality flow to the first network element after binding the first policy and charging control rule to the first service quality flow.
  • the first application service is an application service used on a terminal.
  • the first quality of service flow is not bound to a policy and charging control rule that does not include the first information, and the first information is used to associate one or more policies and charging control rules corresponding to the first application service.
  • the first information may also indicate that the first quality of service flow established according to the policy and charging control rule including the first information is not bound to the policy and charging control corresponding to other application services.
  • the policy and charging control rule bound to the first quality of service flow only corresponds to the first application service, that is, the first quality of service flow carries the service flow of the first application service, and does not carry the service flow of other application services, so that one or more quality of service flows of the multiple service flows carrying the first application service do not carry the service flow of other application services. Since one or more quality of service flows of the multiple service flows carrying the first application service do not carry the service flow of other application services, the normal transmission of the service flow of other application services will not be affected when the multiple service flows of the first application service are collaboratively managed.
  • the first information can also be used to associate multiple policies and charging control rules corresponding to the first application service, it is also possible to allow service flows with the same QoS requirements in the same application service to be carried through the same QoS, thereby reducing the number of QoS flows.
  • each of the multiple policies and charging control rules corresponding to the first application service includes first information.
  • the QoS flow created for the multiple service flows of the first application service is not bound to the policies and charging control corresponding to other application services. Therefore, the management of the multiple QoS flows of the first application will not affect the transmission of service flows of other applications, thereby improving the accuracy of QoS management and improving user experience.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the application service corresponding to the policy and billing control rules that do not include the first information is a different application service from the first application service, which can avoid binding the service flows of other applications to the QoS flow corresponding to the first application, so that the management of multiple QoS flows of the first application will not affect the transmission of service flows of other applications, thereby improving the accuracy of QoS management and improving user experience.
  • the method may further include: the session management function network element determines, according to the first information in the PCC rule, that the first quality of service flow is not bound to the policy and charging control rule that does not include the first information.
  • the session management function network element does not bind the policy and charging control rule of the application service to the first quality of service flow, so that the quality of service flow carrying the first service flow does not carry the service flow of other application services.
  • the method may also include: before binding the first policy and charging control rule to the first quality of service flow, the session management function network element creates the first quality of service flow; or, the first information is used to associate multiple policies and charging control rules corresponding to the first application service, and before binding the first policy and charging control rule to the first quality of service flow, the session management function network element determines that the first quality of service flow has been created based on a policy and charging control rule that has the same binding parameters as the first policy and charging control rule and includes the first information.
  • a quality of service flow can be bound to a policy and charging control rule, or the flow can be bound to multiple policies and charging control rules corresponding to the same application service and having the same binding parameters.
  • the first policy and charging control rule may further include second information
  • the second information may be used to indicate that the first policy and charging control rule is bound to a quality of service flow, and the quality of service flow is not bound to a policy and charging control rule that includes the first information and has the same binding parameters as the first policy and charging control rule;
  • the second information may be used to indicate that the first policy and charging control rule and the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule are bound to the same service quality flow.
  • the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule is bound to the same service quality flow, which can be understood as the policy and charging control rule corresponding to the service flow that has the same service quality requirement as the service flow corresponding to the first policy and charging control rule and belongs to the first application service.
  • a service quality flow can be bound to a policy and charging control rule by explicit indication, or a service quality flow can be bound to multiple policies and charging control rules corresponding to the same application service and having the same binding parameters, and the implementation method is flexible.
  • the method may further include: the session management function network element determines the association relationship between the multiple service flows of the first application service according to the first information.
  • the session management function network element may maintain or store the association relationship between the multiple service flows of the first application service.
  • the session management function network element may determine the multiple service flows belonging to the first application service according to the first information.
  • multiple measurement and charging control rules corresponding to the first application service are bound to multiple service quality flows, and the first network element is an access network element; the method may also include: a session management function network element receives a first message from the access network element, the first message is used to indicate that the first service quality flow is released; and, releasing the unreleased service flows in the multiple service flows of the first application service from at least one service quality flow, wherein at least one service quality flow is a service quality flow in the multiple service quality flows other than the first service quality flow.
  • the session management function network element can realize the collaborative management of the multiple service flows of the first application service.
  • the session management function network element may release the unreleased service flow among the multiple service flows of the first application service from the at least one quality of service flow in the following manner:
  • the session management function network element determines an association relationship between multiple service flows of a first application service, determines an unreleased service flow among the multiple service flows of the first application service based on an association relationship between the service flow corresponding to the first quality of service flow and the multiple service flows of the first application service, and releases the unreleased service flows among the multiple service flows of the first application service from at least one quality of service flow based on the unreleased service flows among the multiple service flows of the first application service.
  • the session management function network element may also send a second message to the policy control function network element, and the second message is used to request to deactivate multiple policies and charging control rules corresponding to the first application service.
  • the second message can be understood as one message or as multiple messages.
  • the second message is one message, and the one message can be used to request to deactivate all policies and charging control rules corresponding to the first application service.
  • the second message is multiple messages, one of which is used to request to deactivate one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the session management function network element may send a third message to the policy control function network element, the third message being used to request deactivation of the policy and charging control rules bound to the first quality of service flow; receive a fourth message from the policy control function network element, the fourth message being used to indicate deactivation of multiple policy and charging control rules corresponding to the first application service, or the fourth message being used to request release of unreleased service flows in multiple service flows of the first application service; determine multiple service flows of the first application service according to the fourth message; and release the unreleased service flows in multiple service flows of the first application service from at least one quality of service flow.
  • the session management function network element may determine the unreleased service flows in multiple service flows of the first application service according to the service flows of the first application service corresponding to the first QoS flow and the multiple service flows of the first application service, and release the unreleased service flows in multiple service flows of the first application service from at least one quality of service flow according to the unreleased service flows in multiple service flows of the first application service.
  • the fourth message may be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message may be used to indicate deactivation of all policy and charging control rules corresponding to the first application service.
  • the fourth message is a plurality of messages, one of which is used to indicate deactivation of one of a plurality of policies and charging control rules corresponding to the first application service, and the plurality of messages correspond one-to-one to the plurality of policies and charging control rules corresponding to the first application service.
  • the session management function network element can trigger itself to release the unreleased service flows from the multiple service flows of the first application service from at least one service quality flow, or can respond to the fourth message of the policy control function network element to release the unreleased service flows from the multiple service flows of the first application service from at least one service quality flow, and the implementation method is flexible.
  • multiple policies and charging control rules corresponding to the first application service are bound to multiple service quality flows, and the information of the first service quality flow may include third information; or the session management function network element may send third information to the first network element; wherein the third information is used to indicate the association of multiple service quality flows corresponding to the first application service.
  • the first network element can determine, based on the third information, that multiple service flows corresponding to the multiple service quality flows belong to the same application service.
  • an embodiment of the present application provides another communication method, which can be executed by a policy control function network element, or by a component of a policy control function network element.
  • the policy control function network element receives a request message from an application function network element, the request message is used to request to provide quality service for a first service flow, wherein the request message includes fourth information, the first information is used to associate multiple service flows of a first application service, and the first service flow is one of the multiple service flows of the first application service; according to the request message, a first policy and charging control rule is generated, wherein the first policy and charging control rule includes first information, and the first information is used to associate one or more policies and charging control rules corresponding to the first application service; and the first policy and charging control rule is sent to a session management function network element.
  • the policy and charging control rule including the first information is not bound to the policy and charging control rule not including the first information.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the method further includes: a policy control function network element determining the first information according to the fourth information.
  • the first policy and charging control rule may further include second information
  • the second information may be used to indicate that the first policy and charging control rule is bound to a quality of service flow, and the quality of service flow is not bound to a policy and charging control rule that includes the first information and has the same binding parameters as the first policy and charging control rule;
  • the second information may be used to indicate that the first policy and charging control rule and the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule are bound to the same service quality flow.
  • the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule is bound to the same service quality flow, which can be understood as the policy and charging control rule corresponding to the service flow that has the same service quality requirement as the service flow corresponding to the first policy and charging control rule and belongs to the first application service.
  • the method may further include: the session management function network element determines the association relationship between multiple service flows of the first application service according to the first information.
  • the session management function network element may maintain or store the association relationship between multiple service flows of the first application service.
  • the method may also include: the policy control function network element receives a third message from the session management function network element, the third message is used to request deactivation of the policy and billing control rules bound to the first service quality flow; according to the policy and billing control rules bound to the first service quality flow including the first information and fourth information, determine multiple policies and billing control rules corresponding to the first application service; and, deactivate the multiple policies and billing control rules corresponding to the first application service.
  • the method may also include: the policy control function network element sends a fourth message to the session management function network element, the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message is used to request the release of unreleased service flows among multiple service flows of the first application service.
  • the fourth message can be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the method may also include: the policy control function network element receives a second message from the session management function network element, the second message is used to request to deactivate multiple policies and charging control rules corresponding to the first application service; and, according to the second message, deactivate multiple policies and charging control rules corresponding to the first application service.
  • the second message can be understood as one message, and can also be understood as multiple messages.
  • the second message is one message, and the one message can be used to request to deactivate all policies and charging control rules corresponding to the first application service.
  • the second message is multiple messages, one of which is used to request to deactivate one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • an embodiment of the present application provides another communication method, which can be executed by an access network element or by a component of an access network element.
  • the access network element receives information about a first quality of service flow from a session management function element, the information about the first quality of service flow includes third information, and the third information is used to associate multiple quality of service flows corresponding to a first application service; when the first quality of service flow is created, at least one quality of service flow is created according to the third information; or when the first quality of service flow is released, at least one quality of service flow is released according to the third information; wherein the at least one quality of service flow is a quality of service flow among the multiple quality of service flows corresponding to the first application service except the first quality of service flow.
  • the method may further include: the access network element determining the at least one quality of service flow according to the first quality of service flow and the third information.
  • an embodiment of the present application provides another communication method, which can be executed by a session management function network element, or by a component of the session management function network element.
  • the session management function network element receives a fifth message from an access network network element, the fifth message is used to indicate that the second quality of service flow is released; and, releases the unreleased service flow in multiple service flows of the first application service from at least one quality of service flow, wherein the at least one quality of service flow is a quality of service flow other than the second quality of service flow in the multiple quality of service flows corresponding to the first application service.
  • the session management function network element releases the unreleased service flows from the multiple service flows of the first application service from at least one service quality flow, thereby realizing the coordinated management of multiple service flows of an application service with service flow as the granularity. Since the session management function network element releases with service flow as the granularity, compared with releasing the entire service quality flow, the transmission of service flows of other application services carried by the same service quality flow will not be terminated, thereby avoiding affecting the normal transmission of service flows of other application services carried by the same service quality flow.
  • the method may further include: before receiving the fifth message from the access network element, the session management function element receives a first policy and charging control rule from the policy control function element, the first policy and charging control rule including first information, the first information being used to associate multiple policies and charging control rules corresponding to the first application service; binding the first policy and charging control rule to the second quality of service flow; and sending information of the second quality of service flow to the first network element.
  • the session management function element may bind the policy and charging control rule corresponding to the first service flow to the second quality of service flow, and the second quality of service flow may carry service flows of other application services in addition to the first service flow.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the method may further include: the session management function network element determines the association relationship between the multiple service flows of the first application service according to the first information.
  • the session management function network element may maintain or store the association relationship between the multiple service flows of the first application service.
  • the session management function network element may determine the multiple service flows belonging to the first application service according to the first information.
  • the method may further include: the session management function network element determines the association relationship between multiple service flows of the first application service, and determines the unreleased service flows in the multiple service flows of the first application service according to the association relationship between the service flow corresponding to the first quality of service flow and the multiple service flows of the first application service.
  • the session management function network element can determine the unreleased service flows in the multiple service flows of the first application service by itself, and based on the determined unreleased service flows in the multiple service flows of the first application service, release the unreleased service flows in the multiple service flows of the first application service from at least one quality of service flow, thereby realizing the collaborative management of the multiple service flows of the first application service with the service flow as the granularity.
  • the method may also include: the session management function network element sends a second message to the policy control function network element, and the second message is used to request to deactivate multiple policies and charging control rules corresponding to the first application service, so that the policy control function network element can respond to the second message and deactivate the multiple policies and charging control rules corresponding to the first application service.
  • the second message can be understood as one message or as multiple messages.
  • the second message is one message, and the one message can be used to request to deactivate all policies and charging control rules corresponding to the first application service.
  • the second message is multiple messages, one of which is used to request to deactivate one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the method may also include: the session management function network element sends a sixth message to the policy control function network element, the sixth message is used to request to deactivate the policy and charging control rules bound to the second service quality flow; and, receiving a fourth message from the policy control function network element, the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message can be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the method may also include: the session management function network element determines the service flow of the first application service based on the fourth message, and determines the service flow that has not been released among the multiple service flows of the first application service based on the service flow corresponding to the second service quality flow and the multiple service flows of the first application service.
  • the session management function network element can determine the unreleased service flows among the multiple service flows of the first application service in response to the fourth message of the policy control function network element, and based on the determined unreleased service flows among the multiple service flows of the first application service, release the unreleased service flows among the multiple service flows of the first application service from at least one service quality flow, thereby realizing collaborative management of the multiple service flows of the first application service with the service flow as the granularity.
  • an embodiment of the present application provides another communication method, which can be executed by a policy control function network element or by a component of the policy control function network element.
  • the policy control function network element receives a sixth message from a session management function network element, the sixth message is used to request to deactivate the policy and charging control rules bound to the second quality of service flow, the first service flow corresponding to the second quality of service flow is one of the multiple service flows of the first application service; determine the multiple policies and charging control rules corresponding to the first application service; and deactivate the multiple policies and charging control rules corresponding to the first application service.
  • the method may also include: a policy control function network element receives a request message from an application function network element, the request message being used to request quality of service for a first service flow, wherein the request message includes fourth information, and the fourth information is used to associate multiple service flows of the first application service; based on the request message, generating a first policy and billing control rule, wherein the first policy and billing control rule includes first information, and the first information is used to associate multiple policies and billing control rules corresponding to the first application service; and sending the first policy and billing control rule to a session management function network element.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the method may further include: a policy control function network element determines the first information according to the fourth information.
  • the method may further include: the policy control function network element determines the association relationship between the multiple service flows of the first application service.
  • the policy control function network element may maintain or store the association relationship between the multiple service flows of the first application service.
  • the method may also include: the policy control function network element determines the multiple policies and charging control rules corresponding to the first application service, which may be: the policy control function network element determines the multiple policies and charging control rules corresponding to the first application service based on the fourth information and the PCC rules bound to the second service quality flow.
  • the method may further include: the policy control function network element sends a fourth message to the session management function network element, the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message can be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • an embodiment of the present application provides a communication device.
  • the communication device is used to execute the method described in the first aspect and any possible implementation of the first aspect, or to execute the method described in the fourth aspect and any possible implementation of the fourth aspect.
  • the communication device is, for example, a session management function network element, or a functional module in a session management function network element, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module).
  • the transceiver unit can implement a sending function and a receiving function.
  • a sending unit sometimes also referred to as a sending module
  • a receiving unit sometimes also referred to as a receiving module
  • the sending unit and the receiving unit can be the same functional unit, which is called a transceiver unit, and the functional unit can implement a sending function and a receiving function; or, the sending unit and the receiving unit can be different functional units, and the transceiver unit is a general term for these functional units.
  • an embodiment of the present application provides another communication device.
  • the communication device is used to execute the method described in the second aspect and any possible implementation of the second aspect, or to execute the method described in the fifth aspect and any possible implementation of the fifth aspect.
  • the communication device is, for example, a policy control function network element, or a functional module in a policy control function network element, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module).
  • the transceiver unit can implement a sending function and a receiving function.
  • a sending unit sometimes also referred to as a sending module
  • a receiving unit sometimes also referred to as a receiving module
  • the sending unit and the receiving unit can be the same functional unit, which is called a transceiver unit, and the functional unit can implement a sending function and a receiving function; or, the sending unit and the receiving unit can be different functional units, and the transceiver unit is a general term for these functional units.
  • an embodiment of the present application provides another communication device.
  • the communication device is used to execute the method described in the third aspect and any possible implementation of the third aspect.
  • the communication device is, for example, an access network element, or a functional module in an access network element, such as a baseband device or a chip system.
  • the communication device includes a baseband device and a radio frequency device.
  • the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module).
  • the transceiver unit can implement a sending function and a receiving function.
  • a sending unit sometimes also referred to as a sending module
  • a receiving unit sometimes also referred to as a receiving module
  • the sending unit and the receiving unit can be the same functional unit, which is called a transceiver unit, and the functional unit can implement a sending function and a receiving function; or, the sending unit and the receiving unit can be different functional units, and the transceiver unit is a general term for these functional units.
  • an embodiment of the present application provides a communication device.
  • the communication device may include one or more processors.
  • the communication device may also include a memory.
  • the memory is used to store one or more computer programs or instructions.
  • the one or more processors are used to execute the one or more computer programs or instructions stored in the memory, so that the communication device executes the method described in the first aspect and any possible implementation of the first aspect, or executes the fourth aspect and any possible implementation of the fourth aspect. The method described in the possible implementation.
  • an embodiment of the present application provides another communication device.
  • the communication device may include one or more processors.
  • the communication device may also include a memory.
  • the memory is used to store one or more computer programs or instructions.
  • the one or more processors are used to execute the one or more computer programs or instructions stored in the memory, so that the communication device executes the method described in the second aspect and any possible implementation of the second aspect, or executes the method described in the fifth aspect and any possible implementation of the fifth aspect.
  • an embodiment of the present application provides another communication device.
  • the communication device may include one or more processors.
  • the communication device may also include a memory.
  • the memory is used to store one or more computer programs or instructions.
  • the one or more processors are used to execute the one or more computer programs or instructions stored in the memory, so that the communication device performs the method described in the third aspect and any possible implementation of the third aspect.
  • an embodiment of the present application further provides a communication system, wherein the communication system comprises at least one of the communication device described in the sixth aspect, the communication device described in the seventh aspect, or the communication device described in the eighth aspect.
  • an embodiment of the present application provides a computer-readable storage medium, which is used to store computer programs or instructions.
  • the computer-readable storage medium is executed, the method described in the first aspect and any possible implementation of the first aspect is implemented, or the method described in the fourth aspect and any possible implementation of the fourth aspect is implemented.
  • an embodiment of the present application provides a computer-readable storage medium, which is used to store computer programs or instructions.
  • the computer-readable storage medium is executed, the method described in the second aspect and any possible implementation of the second aspect is implemented, or the method described in the fifth aspect and any possible implementation of the fifth aspect is implemented.
  • an embodiment of the present application provides a computer-readable storage medium, which is used to store computer programs or instructions.
  • the computer-readable storage medium is executed, the method described in the above-mentioned third aspect and any possible implementation method of the third aspect is implemented.
  • an embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the method described in the above-mentioned first aspect and any possible implementation method of the first aspect to be implemented, or enables the method described in the above-mentioned fourth aspect and any possible implementation method of the fourth aspect to be implemented.
  • an embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the method described in the above-mentioned second aspect and any possible implementation of the second aspect to be implemented, or enables the method described in the above-mentioned fifth aspect and any possible implementation of the fifth aspect to be implemented.
  • an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the method described in the third aspect and any possible implementation method of the third aspect to be implemented.
  • an embodiment of the present application also provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory, so that the device where the chip is located implements the method described in the above-mentioned first aspect and any possible implementation method of the first aspect, or implements the above-mentioned fourth aspect and any possible implementation method of the fourth aspect.
  • an embodiment of the present application further provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory, so that the device where the chip is located implements the method described in the second aspect and any possible implementation of the second aspect, or implements the method described in the fifth aspect and any possible implementation of the fifth aspect.
  • an embodiment of the present application further provides a chip, which is coupled to a memory and is used to read and execute program instructions in the memory, so that the device where the chip is located implements the method described in the above-mentioned third aspect and any possible implementation method of the third aspect.
  • FIG1 is a schematic diagram of a 5G network architecture in an embodiment of the present application.
  • FIG2 is a schematic diagram of a service flow in which a QoS flow carries different application services in an embodiment of the present application
  • FIG3 is a flow chart of a communication method provided in an embodiment of the present application.
  • FIG4 is a flow chart of another communication method provided in an embodiment of the present application.
  • FIG5A is a schematic diagram of a QoS flow carrying at least one service flow of an application service provided by an embodiment of the present application
  • FIG5B is a schematic diagram of a service flow of an application service carried by a QoS flow provided by an embodiment of the present application
  • FIG6 is a flow chart of another communication method provided in an embodiment of the present application.
  • FIG7 is a flow chart of another communication method provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of collaborative management of multiple service flows of application service 1 provided in an embodiment of the present application.
  • FIG9 is a flow chart of another communication method provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of a communication device provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of another communication device provided in an embodiment of the present application.
  • “Multiple” refers to two or more than two. In view of this, in the embodiments of the present application, “multiple” can also be understood as “at least two". "At least one” can be understood as one or more, for example, one, two or more. For example, including at least one means including one, two or more, and there is no limit on which ones are included. For example, including at least one of A, B and C, then A, B, C, A and B, A and C, B and C, or A and B and C. Similarly, the understanding of descriptions such as "at least one" is also similar.
  • At least one of the following or its similar expressions refers to any combination of these items, including any combination of single items or plural items.
  • at least one of A, B and C includes A, B, C, AB, AC, BC or ABC.
  • And/or describes the association relationship of associated objects, indicating that three relationships can exist.
  • a and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character “/”, unless otherwise specified, generally indicates that the previous and next associated objects are in an “or” relationship.
  • the word "exemplary” is used to indicate an example, illustration or description. Any embodiment or design described as “exemplary” in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of the word “exemplary” is intended to present concepts in a concrete way.
  • PLMN public land mobile network
  • MNO mobile network operators
  • 3GPP third generation partnership project
  • 3GPP networks generally include but are not limited to fifth-generation mobile communication (5th-generation, 5G) networks (referred to as 5G networks), fourth-generation mobile communication (4th-generation, 4G) networks (referred to as 4G networks) and other future communication systems such as 6G networks.
  • 5G networks fifth-generation mobile communication
  • 4th-generation, 4G networks fourth-generation mobile communication (4th-generation, 4G) networks
  • 6G networks other future communication systems
  • 5G networks fifth-generation mobile communication
  • 5G networks fourth-generation mobile communication (4th-generation, 4G) networks
  • 4G networks fourth-generation mobile communication systems
  • 6G networks future communication systems
  • FIG1 is a schematic diagram of a network architecture of an embodiment of the present application, which takes the 5G network architecture based on the service-oriented architecture in the non-roaming scenario defined in the 3GPP standardization process as an example.
  • the network architecture may include three parts, namely, the terminal device part, the data network (DN) part and the PLMN part.
  • the terminal device part may include a terminal device, which can establish a connection with the operator network through an interface provided by the operator network (such as N1, etc.), and use data and/or voice services provided by the operator network.
  • the terminal device can also access the data network through the operator network, use the operator services deployed on the data network, and/or services provided by a third party.
  • the above-mentioned third party may be a service provider other than the operator network and the terminal device, and can provide other data and/or voice services to the terminal device.
  • the specific form of expression of the above-mentioned third party can be determined according to the actual application scenario, and is not limited here.
  • Terminal equipment also known as terminal, is a device with wireless transceiver function. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water (such as ships); it can also be deployed in the air (such as airplanes, balloons and satellites).
  • the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, an extended reality (XR) terminal (such as a virtual reality (VR) terminal, an augmented reality (AR) terminal, etc.), a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a user equipment (UE), a terminal device adapted for the Internet of Things (IoT) (such as a terminal device in a smart factory, a terminal device in the smart manufacturing industry, etc.), etc.
  • XR extended reality
  • VR virtual reality
  • AR augmented reality
  • a wireless terminal in industrial control such as a virtual reality (VR) terminal, an augmented reality (AR) terminal, etc.
  • a wireless terminal in industrial control such as a virtual reality (VR) terminal, an augmented reality (AR) terminal, etc.
  • a data network also known as a packet data network (PDN)
  • PDN packet data network
  • An operator network can access multiple data networks, and a variety of services can be deployed on the data network, which can provide data and/or voice services to terminal devices.
  • a data network can be a private network of a smart factory, and the sensors installed in the workshop of the smart factory can be terminal devices.
  • the control server of the sensors is deployed in the data network, and the control server can provide services for the sensors.
  • the sensor can communicate with the control server, obtain instructions from the control server, and transmit the collected sensor data to the control server according to the instructions.
  • the data network can be the internal office network of a company, and the mobile phones or computers of the company's employees can be terminal devices. The employees' mobile phones or computers can access information, data resources, etc. on the company's internal office network.
  • the PLMN may include, but is not limited to: network slice selection function (NSSF) network element, authentication server function (AUSF) network element, network exposure function (NEF) network element, network repository function (NRF) network element, access and mobility management function (AMF) network element, policy control function (PCF) network element, unified data management (UDM) network element, session management function (SMF) network element, access network (AN) or radio access network (RAN), and user plane function (UPF) network element, etc.
  • NSF network slice selection function
  • AUSF authentication server function
  • NEF network exposure function
  • NRF network repository function
  • AMF access and mobility management function
  • PCF policy control function
  • UDM unified data management
  • SMF session management function
  • AN access network
  • RAN radio access network
  • UPF user plane function
  • FIG. 1 also involves other network elements, which will not be introduced in detail here.
  • Radio AN also known as Radio AN
  • Radio AN can be regarded as a sub-network of the operator network. It is the implementation system between the service nodes and terminal devices in the operator network.
  • the terminal device To access the operator network, the terminal device first passes through (R)AN, and then can connect to the service nodes of the operator network through (R)AN.
  • the access network equipment (RAN equipment) in the embodiment of the present application is a device that provides wireless communication functions for terminal equipment, and may also be referred to as network equipment, access network element, etc.
  • the RAN equipment includes but is not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (e.g., home evolved node B, or home node B, HNB), the base band unit (BBU), the transmission point (TRP), the transmitting point (TP), the small base station equipment (pico), the mobile switching center, or the network equipment in the future network, etc.
  • the name of the equipment with the access network equipment function may be different.
  • access network devices For the convenience of description, in all embodiments of the present application, the above-mentioned apparatuses providing wireless communication functions for terminal devices are collectively referred to as access network devices or RAN or AN for short. It should be understood that the specific type of access network devices is not limited herein.
  • the application function is a control plane function deployed on the application service side. It can be deployed by the operator or by an external third party.
  • the application function supports services such as traffic routing control, policy control function interaction, and access network function opening by interacting with other network functions of the core network.
  • the application function may be AF, as shown in Figure 1; in future communication systems, such as 6G communication systems, the application function may still be AF, or may have other names, which are not limited in the embodiments of the present application.
  • the network open function is responsible for providing some network-related status information before applying services.
  • the network open function may be NEF, as shown in FIG1 ; in future communication systems, such as a 6G communication system, the network open function may still be NEF, or may have other names, which are not limited in the embodiments of the present application.
  • the policy control function is a control plane function provided by the operator, which supports a unified policy framework to govern network behavior, provide policy rules to other control functions, contract information related to policy decisions, etc.
  • the policy control function may be a PCF, as shown in FIG1 ; in future communication systems, such as a 6G communication system, the policy control function may still be a PCF, or may have other names, which are not limited in the embodiments of the present application.
  • the session management function is a control plane network function provided by the PLMN, responsible for managing the protocol data unit (protocol Data unit (PDU).
  • PDU protocol Data unit
  • a PDU session is a channel for transmitting PDU, and the terminal device needs to transmit data to and from the DN through the PDU session.
  • the PDU session can be created, maintained, and deleted by the session management function.
  • the session management function includes session management (such as session creation, modification, and release, including tunnel maintenance between user plane functions and AN, etc.), selection and control of user plane functions, service and session continuity (SSC) mode selection, roaming, and other session-related functions.
  • session management such as session creation, modification, and release, including tunnel maintenance between user plane functions and AN, etc.
  • SSC service and session continuity
  • the session management function may be an SMF, as shown in FIG1 ; in future communication systems, such as a 6G communication system, the session management function may still be an SMF, or may have other names, which are not limited in the embodiments of the present application.
  • the user plane function is a gateway provided by the PLMN to communicate with the data network DN.
  • the user plane function includes data packet routing and transmission, data packet detection, service usage reporting, quality of service (QoS) processing, legal monitoring, uplink data packet detection, downlink data packet storage and other user plane related functions.
  • QoS quality of service
  • the user plane function may be UPF, as shown in FIG1 ; in future communication systems, such as a 6G communication system, the user plane function may still be UPF, or may have other names, which are not limited in the embodiments of the present application.
  • the access and mobility management function is a control plane network function provided by the PLMN, which is responsible for the access control and mobility management of the terminal device accessing the PLMN, including, for example, mobile state management, allocation of user temporary identity, authentication and authorization of users, etc.
  • the access and mobility management function may be AMF, as shown in Figure 1; in future communication systems, such as 6G communication systems, the access and mobility management function may still be AMF, or may have other names, which are not limited in the embodiments of the present application.
  • each network function in the PLMN can be a network element implemented on dedicated hardware, or a software instance running on dedicated hardware, or an instance of a virtualized function on an appropriate platform, for example, the above-mentioned virtualization platform can be a cloud platform.
  • each network function in the PLMN can also be called a network element, a functional entity or a device, for example, the policy control function can also be called a policy control function network element, a policy control function entity or a policy control function device, etc.
  • the session management function can also be called a session management function network element, a session management function entity or a session management function device, etc., which will not be listed one by one here.
  • the network functions in the PLMN shown in FIG. 1 may also include other network functions.
  • the PLMN also includes a unified data repository (UDR) and the like (not shown in FIG. 1 ).
  • UDR unified data repository
  • the embodiments of the present application do not limit other network functions included in the PLMN.
  • the names of the network functions shown in FIG. 1 are only used as an example here and are not used as a limitation on the network functions included in the network architecture to which the method of the embodiments of the present application is applicable.
  • the names of devices that implement network functions in systems with different access technologies may be different, and the embodiments of the present application do not limit this.
  • Nnssf, Nausf, Nnef, Nnrf, Namf, Npcf, Nsmf, Nudm, Naf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • the meanings of these interface serial numbers can be found in the meanings defined in the standard protocol of the 3rd Generation Partnership Project (3GPP), and are not limited here.
  • 3GPP 3rd Generation Partnership Project
  • the interface names between the various network functions in Figure 1 are only examples. In specific implementations, the interface names of the system architecture may also be other names, which are not limited in this application.
  • the network architecture shown in FIG1 does not constitute a limitation on the communication system to which the embodiments of the present application can be applied.
  • the network architecture shown in FIG1 is a 5G system architecture.
  • the technical solution provided in the embodiments of the present application can be applied to the 4th generation mobile communication technology (4G) system, such as the LTE system, in addition to the 5G system, or can also be applied to the next generation mobile communication system or other similar communication systems, without specific limitation.
  • 4G 4th generation mobile communication technology
  • PCC rules can be used to perform policy control on the service flow of application services.
  • the PCC rule is generated by the PCF network element and sent to the SMF network. After the SMF network element receives the PCC rule from the PCF network element, it binds the PCC rule to the corresponding QoS flow through the QoS flow binding mechanism. After that, the service flow corresponding to the PCC rule can be carried by the QoS flow bound to the PCC rule.
  • the principle of the QoS flow binding mechanism is: if the binding parameters of the PCC rule (such as 5G QoS identifier (5G QoS identifier, 5QI), priority, etc.) are consistent with the parameters of the QoS flow, the PCC rule can be bound to the QoS flow. In the current QoS flow binding mechanism, multiple PCC rules with the same binding parameters can be bound to the same QoS flow.
  • 5G QoS identifier 5G QoS identifier, 5QI), priority, etc.
  • the PCF may generate a PCC rule for one service flow, that is, one service flow corresponds to one PCC rule; or may generate a PCC rule for multiple service flows, that is, multiple service flows correspond to one PCC rule. That is, multiple service flows may correspond to one or more PCC rules.
  • the following text takes one service flow corresponding to one PCC rule as an example without special explanation.
  • binding the PCC rule with the QoS flow in the embodiment of the present application can be understood as associating the PCC rule with the QoS flow, or can also be understood as mapping the PCC rule to the QoS flow.
  • multiple PCC rules with corresponding binding parameters can be understood as multiple PCC rules having one or more identical binding parameters.
  • the binding parameters may include, for example, at least one of the following parameters: 5G QoS identifier (5G QoS identifier, 5QI), allocation and retention priority (allocation and retention priority, ARP), QoS notification control (QoS notification control, QNC), priority (priority level), averaging window, and maximum data burst volume, etc.
  • multiple PCC rules with the same binding parameters can be understood as multiple service flows corresponding to the multiple PCC rules having the same QoS requirements. Accordingly, multiple PCC rules with the same binding parameters can be bound to the same QoS flow, which can be understood as multiple service flows with the same QoS requirements can be mapped to the same QoS flow, or can also be understood as multiple service flows with the same QoS requirements can be carried by one QoS flow.
  • the application service involved in the embodiment of the present application may be an XR service used on the terminal, or may be a game service used on the terminal, etc.
  • the embodiment of the present application does not limit the specific implementation method of the application service.
  • the service flow involved in the embodiment of the present application may be a video data stream, an audio data stream, and/or a sensor data stream, etc. sent to the terminal, or may be a video data stream, an audio data stream, and/or a sensor data stream, etc. sent by the terminal to the server.
  • the embodiment of the present application does not limit the specific implementation method of the service flow.
  • the service flow involved in the embodiment of the present application may be an IP stream with an independent Internet protocol (IP) quintuple, and different service flows may also have the same IP quintuple.
  • IP Internet protocol
  • the I frame in the video data stream identified by an IP quintuple constitutes one service flow
  • the P frame in the video data stream constitutes another service flow.
  • An application service can correspond to multiple service flows.
  • a game application can generate not only video data but also audio data.
  • the QoS requirements of these service flows can be different, which means that multiple PCC rules corresponding to the same application service are bound to different QoS flows, that is, multiple service flows of the same application service can be mapped to different QoS flows, that is, an application service including multiple service flows can correspond to multiple QoS flows.
  • Figure 2 takes application service 1, application service 2 and application service 3 as examples.
  • Application service 1 includes three service flows, which are respectively recorded as service flow 1, service flow 2 and service flow 3; application service 2 includes one service flow, which is recorded as service flow 4; application service 3 includes one service flow, which is recorded as service flow 5.
  • service flows 1, service flow 2 and service flow 4 have the same QoS requirements.
  • Service flows 1, service flow 2 and service flow 4 are mapped to QoS flow 1, that is, QoS flow 1 carries the service flow of application service 1 and the service flow of application service 2; service flows 3 and service flow 5 have the same QoS requirements.
  • Service flows 3 and service flow 5 are mapped to QoS flow 2, that is, QoS flow 2 carries the service flow of application service 1 and the service flow of application service 3.
  • QoS flow 2 carries part of the service flow of application service 1, so there is no need to transmit service flow 1 and service flow 2 of application service 1, and there is no need to reserve resources for service flow 1 and service flow 2.
  • QoS flow 1 can be released, but QoS flow 1 also carries service flow 4 of application service 2. Releasing QoS flow 1 will affect the normal transmission of service flow 4 of application service 2.
  • an embodiment of the present application provides a communication method and apparatus, in which multiple PCC rules having the same binding parameters but corresponding to different application services are not bound to the same QoS flow, that is, one QoS flow carries one or more service flows of an application service, so that each QoS flow in the multiple QoS flows corresponding to one application service does not carry the service flows of other application services, which means that when the multiple QoS flows corresponding to the one application service are collaboratively managed, the normal transmission of the service flows of other application services will not be affected, thereby avoiding the problem that the service flows of other application services cannot be transmitted normally due to the collaborative management of the multiple QoS flows corresponding to the one application service.
  • the access network element, application function network element, network open function network element, policy control function network element, session management function network element, user plane function network element, and access and mobility management function network element involved in the embodiment of the present application can be the RAN, AF network element, NEF network element, PCF network element, SMF network element, UPF network element, and AMF network element in Figure 1, respectively, or it can be a network element with the functions of the above-mentioned RAN, AF network element, NEF network element, PCF network element, SMF network element, UPF network element, and AMF network element in future communications such as the sixth generation (6th generation, 6G) network.
  • 6G sixth generation
  • the embodiment of the present application is described by taking the access network element, application function element, network open function element, policy control function element, session management function element, user plane function element, access and mobility management function element as the above-mentioned RAN, AF element, NEF element, PCF element, SMF element, UPF element, and AMF element as an example.
  • the terminal device involved in the embodiment of the present application may be the UE in Figure 1.
  • Fig. 3 shows a schematic diagram of a process flow of a communication method provided in an embodiment of the present application. As shown in Fig. 3, the process may include the following contents.
  • the AF network element sends a request message 1 to the PCF network element; correspondingly, the PCF network element receives the request message 1 from the AF network element.
  • the request message 1 can be used to request that quality service be provided for the first service flow.
  • the request message 1 includes fourth information.
  • the fourth information can be used to associate one or more service flows of the first application service.
  • the first application service corresponds to one or more service flows.
  • the first service flow is one of the multiple service flows of the first application service.
  • the AF network element can send a request message 1 to the PCF network element to request that quality service be provided for the first service flow during the process of the UE registering the first application service or during the process of the UE running the first application service.
  • the AF network element sends a request message 1 to the PCF network element to request that quality service be provided for the first service flow.
  • the AF network element may send multiple request messages to the PCF network element to request that quality service be provided for multiple service flows of the first application service, that is, the AF network element sends a request message to the PCF network element for each service flow of the multiple service flows of the first application service to request that quality service be provided.
  • the multiple request messages include request message 1.
  • the multiple request messages may be sent one by one or together, and this is not limited in the embodiments of the present application.
  • the multiple service flows associated with the first application service involved in the embodiment of the present application can be understood as the multiple service flows belonging to the same application service, or as the QoS requirements of the multiple service flows need to be guaranteed at the same time.
  • the fourth information is associated with a service flow of the first application service, it indicates that the one service flow belongs to the service flow of the first application service, and the first application service does not have other service flows.
  • the fourth information involved in the embodiment of the present application is used to associate multiple business flows of the first application business. It can be understood that the fourth information is used to indicate the association relationship between multiple business flows of the first application business; or it can also be understood that the fourth information is used to indicate that multiple business flows belong to the same application business; or it can also be understood that the fourth information is used to indicate that the first business flow is one of the multiple business flows of the first application business.
  • the fourth information may be identification information.
  • the fourth information may be identification information of the first application service, used to indicate the first application service; or the fourth information may also be pre-configured or defined identification information, in which case, multiple service flows of the same application service correspond to the same identification information.
  • the AF network element sends multiple request messages to the PCF network element to request that quality services be provided for multiple service flows of the first application service, and each of the multiple request messages includes the fourth information. After the PCF network element receives the multiple request messages, it can determine that the multiple service flows corresponding to the multiple request messages belong to the same application service based on the fact that each of the multiple request messages carries the fourth information.
  • the request message 1 may also include at least one of the identification information of the first service flow and the QoS parameter corresponding to the first service flow.
  • the identification information of the first service flow may be used to identify the first service flow, for example, it may be IP five-tuple information, or three-tuple information.
  • the QoS parameter corresponding to the first service flow is a parameter corresponding to the QoS requirement of the first service flow, for example, it may include but is not limited to packet loss rate, bandwidth requirement, or delay requirement.
  • the request message 1 sent by the AF network element to the PCF network element may reach the PCF network element through the NEF network element or not through the NEF network element.
  • Figure 3 takes the case where the request message 1 does not pass through the NEF network element as an example.
  • the AF network element may send the request message 1 to the NEF network element, and after receiving the request message 1, the NEF network element forwards the request message 1 to the PCF network element.
  • the first PCC rule includes the first information.
  • the first information can be used to associate one or more PCC rules corresponding to the first application service.
  • the multiple PCC rules corresponding to the first application service include the first PCC rule.
  • the PCF network element can generate a first PCC rule for the first service flow in response to the request message 1.
  • the first PCC rule can be used to perform policy control on the first service flow.
  • the PCF network element can generate the first PCC rule based on the fourth information, the identification information of the first service flow, and the QoS parameters corresponding to the first service flow in response to the request message 1.
  • the first application service involved in the embodiment of the present application corresponds to one or more service flows. If the first application service corresponds to one service flow, the first application service may correspond to one PCC rule. If the first application service corresponds to multiple service flows, the first application service may correspond to one or more PCC rules. That is, the first application service involved in the embodiment of the present application corresponds to one or more PCC rules. In the embodiment of the present application, unless otherwise specified, the following text takes the case where a first application service corresponds to multiple PCC rules as an example.
  • the first information involved in the embodiment of the present application is used to associate multiple PCC rules corresponding to the first application service, which can be understood as the first information being used to indicate the association relationship between the multiple PCC rules corresponding to the application service; or it can also be understood as using the first information to indicate that multiple PCC rules correspond to the same application service; or it can also be understood as the first information being used to indicate that the first PCC rule is one of the multiple PCC rules corresponding to the first application service.
  • the multiple PCC rules corresponding to the first application service can be replaced by PCC rules corresponding to multiple service flows of the first application service.
  • the PCF network element may determine the first information according to the fourth information.
  • the PCF network element may determine the first information according to the association relationship between multiple service flows of the first application service.
  • the first information may be, for example, identification information, such as identification information of the first application service, or pre-configured or predetermined identification information.
  • the specific implementation method may refer to the implementation method of the fourth information, which will not be described in detail here.
  • each of the multiple PCC rules corresponding to the first application service may include the first information, and the PCC rules corresponding to other application services do not include the first information, that is, the application service corresponding to the PCC rule that does not include the first information is a different application service from the first application service.
  • the SMF network element receives the multiple PCC rules corresponding to the first application service from the PCF network element, it can be determined that the service flows corresponding to the multiple PCC rules are associated based on the fact that each of the multiple PCC rules includes the first information.
  • the first PCC rule may also include a binding parameter of the first PCC rule, where the binding parameter is used to bind the first PCC rule to the QoS flow. Please refer to the above description for the binding parameter, which will not be repeated here.
  • the first PCC rule may further include at least one of identification information of the first service flow and QoS parameters corresponding to the first service flow.
  • identification information of the first service flow and the QoS parameters corresponding to the first service flow please refer to the content of S301, which will not be repeated here.
  • the first PCC rule may further include second information, where the second information may be used to indicate that the first PCC rule is bound to one or more QoS flows.
  • the second information can be used to indicate that the first PCC rule is bound to a QoS flow, and the QoS flow is no longer bound to other PCC rules, which is equivalent to the first PCC rule being bound to a QoS, and the QoS flow is only bound to the first PCC rule.
  • the other PCC rule and the first PCC rule can correspond to the same application service, or can also correspond to different application services.
  • the binding parameters of the other PCC rules can be the same as or different from the binding parameters of the first PCC rule.
  • the first information can be used to indicate that the first PCC rule is bound to a QoS flow, and the QoS flow is not bound to the PCC rule that has the same binding parameters as the first PCC rule and includes the first information, so that multiple PCC rules corresponding to the same application service and having the same binding parameters are not bound to the same QoS flow.
  • the PCF network element determines that the first application service corresponds to a service flow based on the fourth information, and generates the second information to indicate that the first PCC rule is bound to a QoS flow, and the QoS flow is no longer bound to other PCC rules.
  • the second information and the first information can be one information, in which case the first information is used to associate multiple PCC rules corresponding to the first application service, and to indicate that the first PCC rule is bound to a QoS flow, and the one QoS flow is no longer bound to other PCC rules; or they can be two different information, which is not limited in the embodiments of the present application.
  • the second information can be used to indicate that the PCC rule having the same binding parameters as the first PCC rule and including the first information is bound to the same QoS flow as the first PCC rule, so that multiple PCC rules corresponding to the same application service and having the same binding parameters can be bound to the same QoS flow.
  • the PCF network element can determine that the QoS requirement of at least one service flow other than the first service flow in the first application service is the same as the QoS of the first service flow based on the QoS requirements of multiple service flows of the first application service, and generate the second information to indicate that the first PCC rule can be bound to a QoS flow with other PCC rules including the first information and having the same binding parameters as the first PCC rule.
  • the second information and the first information can be one information, in which case the first information is used to associate multiple PCC rules corresponding to the first application service, and indicate that the PCC rule having the same binding parameters as the first PCC rule and including the first information is bound to the same QoS flow as the first PCC rule; or it can be two different information, which is not limited in the embodiments of the present application.
  • the PCF network element sends the first PCC rule to the SMF network element; correspondingly, the SMF network element receives the first PCC rule from the PCF network element.
  • the SMF network element may execute the content of S304a or the content of S304b. That is, S304a and S304b are two parallel steps, which are indicated by dotted lines in FIG3 .
  • S304a The SMF network element determines a first QoS flow that has been created according to a PCC rule that has the same binding parameters as the first PCC rule and includes the first information.
  • the first QoS flow is not bound to the PCC rule that does not include the first information.
  • the SMF determines that the first QoS flow is not bound to the PCC rule that does not include the first information based on the first information.
  • the first application service corresponding to the PCC rule that does not include the first information is a different application service from the first application service.
  • the binding parameters of the PCC rule that does not include the first information may be the same as or different from the binding parameters of the first PCC rule, and the embodiment of the present application does not limit this.
  • the SMF network element may determine that the QoS flow that has been created according to the PCC rule that includes the first information is not bound to the PCC rule that does not include the first information, that is, the SMF network element may determine that the QoS flow that has been created according to the PCC rule that includes the first information is not bound to the PCC rule that does not include the first information, that is, the SMF network element may determine that the QoS flow that has been created according to the PCC rule that includes the first information is not bound to the PCC rule corresponding to other application services.
  • the SMF network element binds the PCC rule to the QoS flow based on the QoS flow binding mechanism, and maintains or stores the binding relationship between the PCC rule and the QoS flow, and the binding relationship between the PCC rule and the QoS flow may include the PCC rule and the QoS flow created based on the PCC rule or bound to the PCC rule.
  • the SMF network element can determine the QoS flow that has been created according to the PCC rule including the first information based on the association relationship between the multiple PCC rules corresponding to the first application and the binding relationship between the PCC rule and the QoS flow. Please refer to the above description for the QoS flow binding mechanism, which will not be repeated here.
  • the SMF network element determines the association relationship between the multiple PCC rules corresponding to the first application service based on the first information, and maintains or stores the association relationship between the multiple PCC rules corresponding to the first application service.
  • the SMF network element may determine the association relationship between the multiple QoS flows corresponding to the first application service based on the association relationship between the multiple PCC rules corresponding to the first application service and the binding relationship between the PCC rules and the QoS flows, and maintain or store the association relationship between the multiple PCC rules corresponding to the first application service.
  • the SMF network element may determine the association relationship of the first application service based on the association relationship between the multiple PCC rules corresponding to the first application service or the multiple PCC rules corresponding to the first application service, and maintain or store the association relationship of the first application service.
  • the SMF network element can determine, based on the first information, whether there is a first QoS flow that has been created based on a PCC rule that has the same binding parameters as the first PCC rule and includes the first information. In this example, the SMF network element determines that there is a first QoS flow that has been created based on a PCC rule that has the same binding parameters as the first PCC rule and includes the first information, and further the SMF network element can determine the first QoS flow, such as obtaining information, parameters, etc. of the first QoS flow.
  • the first PCC rule includes second information
  • the second information can be used to indicate that the PCC rule having the same binding parameters as the first PCC rule and including the first information is bound to the same QoS flow as the first PCC rule.
  • the SMF network element can determine whether there is a first QoS flow that has been created according to the PCC rule having the same binding parameters as the first PCC rule and including the first information based on the second information.
  • the SMF network element determines that there is a first QoS flow that has been created according to the PCC rule having the same binding parameters as the first PCC rule and including the first information, and further the SMF network element can determine the first QoS flow.
  • S304b The SMF network element creates a first QoS flow according to the first PCC rule.
  • the SMF network element can determine, according to the first information, that the first application service corresponds to a service flow. In this case, the SMF network element creates a first QoS flow according to the first PCC rule.
  • the SMF network element can determine, based on the first information, whether there is a first QoS flow that has been created based on a PCC rule that has the same binding parameters as the first PCC rule and includes the first information. In this example, the SMF network element determines that there is no first QoS flow that has been created based on a PCC rule that has the same binding parameters as the first PCC rule and includes the first information, and further the SMF network element can create a first QoS flow based on the first PCC rule.
  • the first PCC rule includes second information
  • the second information can be used to indicate that a PCC rule having the same binding parameters as the first PCC rule and including the first information is bound to the same QoS flow as the first PCC rule.
  • the SMF network element can determine, based on the second information, whether there is a first QoS flow that has been created based on a PCC rule having the same binding parameters as the first PCC rule and including the first information.
  • the SMF network element determines that there is no first QoS flow that has been created based on a PCC rule having the same binding parameters as the first PCC rule and including the first information, and further the SMF network element can create a first QoS flow based on the first PCC rule.
  • the first PCC rule includes second information, which can be used to indicate that the first PCC rule is bound to a QoS flow, and the QoS flow is no longer bound to other PCC rules.
  • the SMF network element responds to the second information and creates a first QoS flow according to the first PCC rule.
  • creating a first QoS flow can be understood as generating a first QoS flow, or can be understood as configuring network resources for the first QoS flow.
  • S305 The SMF network element binds the first PCC rule to the first QoS flow.
  • the SMF network element binds the first PCC rule to the first QoS flow, indicating that the first service flow corresponding to the first PCC rule is bound by the first QoS Flow carrying.
  • the first QoS flow can carry a service flow of the first application service, that is, only carry the first service flow.
  • the first QoS flow is only bound to the first PCC rule.
  • the second information included in the first PCC rule is used to indicate that the first PCC rule is bound to a QoS flow, and the one QoS flow is no longer bound to other PCC rules.
  • the first application service corresponds to a service flow.
  • the first QoS flow may carry the first service flow and a service flow that has the same QoS requirement as the first service flow and belongs to the first application service.
  • the first QoS flow in addition to being bound to the first PCC rule, is also bound to a PCC rule corresponding to the first application service and having the same binding parameters as the first PCC rule.
  • the first PCC rule includes second information, which can be used to indicate that a PCC rule that has the same binding parameters as the first PCC rule and includes the first information is bound to the same QoS flow as the first PCC rule.
  • the SMF network element may send information about the first QoS flow to the first network element.
  • the first network element is the RAN, or the UPF network element.
  • the information about the first QoS flow sent by the SMF network element to the RAN may be different from the information about the first QoS flow sent by the SMF network element to the UPF network element.
  • the information about the first QoS flow sent by the SMF network element to the RAN is recorded as information 1 of the first QoS flow
  • the information about the first QoS flow sent by the SMF network element to the UPF network element is recorded as information 2 of the first QoS flow.
  • the QoS flow information involved in the embodiments of the present application may include but is not limited to one or more of the following information: QoS flow identity (QFI), 5QI, IP quintuple information, or triplet information, etc.
  • QFI QoS flow identity
  • 5QI IP quintuple information
  • IP quintuple information IP quintuple information, or triplet information, etc.
  • the SMF network element sends information 1 of the first QoS flow to the RAN; correspondingly, the RAN receives information 1 of the first QoS flow from the SMF network element.
  • the SMF network element sends information 1 of the first QoS flow to the RAN, so that the RAN creates a QoS flow for carrying the first service flow according to the information 1 of the first QoS flow.
  • multiple PCC rules corresponding to the first application service are bound to multiple QoS flows, one of which is bound to at least one PCC rule among the multiple PCC rules corresponding to the first application service, that is, multiple service flows of the first application service are carried by multiple QoS flows.
  • the information 1 of the first QoS flow may include third information; or, the SMF network element may send the third information to the RAN, such as the third information and the information 1 of the first QoS flow are carried in one message.
  • the third information can be used to associate the association relationship between the multiple QoS flows bound to the multiple PCC rules corresponding to the first application service.
  • the multiple QoS flows bound to the multiple PCC rules corresponding to the first application service can be replaced with the multiple QoS flows corresponding to the first application service, or replaced with the multiple QoS flows used to carry the multiple service flows of the first application service, or can be replaced with the multiple QoS flows corresponding to the multiple service flows of the first application service.
  • the third information can be used to associate the association relationship between the multiple QoS flows bound to the multiple PCC rules corresponding to the first application service; it can be understood that the third information is used to indicate the association relationship between the multiple QoS flows corresponding to the first application service; or it can also be understood that the third information is used to indicate that the first QoS flow is one of the multiple QoS flows corresponding to the first application service; or it can also be understood that the third information is used to indicate that the multiple QoS flows correspond to the same application service.
  • the information of each QoS flow in the information of the multiple QoS flows corresponding to the first application service sent by the SMF network element to the RAN includes the third information.
  • the third information may be the fourth information, or may be information different from the fourth information, which is not limited in the present embodiment.
  • S304a For the determination of the association relationship between the multiple QoS flows corresponding to the first application service, please refer to the relevant description of S304a, which will not be repeated here.
  • the SMF network element sends information 2 of the first QoS flow to the UPF network element; correspondingly, the UPF network element receives information 2 of the first QoS flow from the SMF network element.
  • the SMF network element sends information 1 of the first QoS flow to the UPF network element, so that the UPF network element creates a QoS flow for carrying the first service flow according to the information 1 of the first QoS flow.
  • the information 2 of the first QoS flow may include third information; or, the SMF network element may send the third information to the UPF network element, such as the third information and the information 2 of the first QoS flow are carried in one message.
  • the SMF network element may first send information 1 of the first QoS flow to the RAN, and then send information 2 of the first QoS flow to the UPF network element; or it may first send information 2 of the first QoS flow to the UPF network element and then send information 1 of the first QoS flow to the RAN; or it may simultaneously send information 1 of the first QoS flow to the RAN and send information 2 of the first QoS flow to the UPF network element.
  • the SMF network element sends information 1 of the first QoS flow to the RAN and sends information 2 of the first QoS flow to the RAN.
  • the RAN can create the first QoS flow according to the information 1 of the first QoS flow, so that the first service flow of the UE can be carried by the first QoS flow and transmitted to the AF network element.
  • the UPF network element can create the information of the first QoS flow according to the information 2 of the first QoS flow, so that the first service flow from the AF network element can be carried by the first QoS flow and transmitted to the UE.
  • the following describes the implementation process of the first QoS flow carrying the first service flow from the uplink transmission direction and the downlink transmission direction respectively in conjunction with FIG. 4 .
  • Fig. 4 shows a schematic flow chart of another communication method provided in an embodiment of the present application. As shown in Fig. 4, the method further includes a flow chart. Among them, S401 to 404 are uplink transmission directions, and S405 to S409 are downlink transmission directions.
  • the SMF network element sends information 1 of a first QoS flow to the RAN; accordingly, the RAN receives information 1 of the first QoS flow from the SMF network element.
  • the first QoS flow is bound to a first PCC rule corresponding to a first service flow.
  • the first service flow is one of multiple service flows of a first application service.
  • S402 RAN creates a first QoS flow according to information 1 of the first QoS flow.
  • S403 The UE maps the first service flow to the first QoS flow.
  • the UE may map the first service flow to the first QoS flow based on the service flow information of the first service flow.
  • the service flow information of the first service flow may come from the RAN, or from the SMF network element, which is not shown in FIG4 .
  • the UE runs a first application service, generates a first service flow, and maps the first service flow to a first QoS flow.
  • the first application service corresponds to multiple service flows
  • the UE runs the first application service, which may generate multiple service flows, and map the multiple service flows to multiple QoS flows bound to multiple PCC rules corresponding to the multiple service flows, and the multiple service flows include the first service flow.
  • the UE may also map the service flow in the first application service that has a corresponding QoS requirement with the first service flow to the first QoS flow.
  • the first QoS flow is also bound to a PCC rule corresponding to the first application service and having the same binding parameters as the first PCC rule.
  • the first QoS flow can also be used to carry the service flow in the first application service that has a corresponding QoS requirement with the first service flow.
  • the service flow information involved in the embodiment of the present application may include but is not limited to at least one of the following information: a quintuple, a triplet, or a data packet filtering rule, etc.
  • S404 The UE uses the first QoS flow to carry the first service flow, and sends the first service flow to the AF network element.
  • the specific implementation process of the UE sending the first service flow to the AF network element through the first QoS flow may be: the UE sends the first service flow to the RAN through the first QoS flow; after the RAN receives the first service flow, it sends the first service flow to the UPF network element through the first QoS flow; after the UPF network element receives the first service flow, it sends the first service flow to the AF network element; the AF network element receives the first service flow.
  • the first QoS flow can carry at least one service flow in the first application service, and does not carry service flows that do not belong to the first application service.
  • S405 The SMF network element sends information 2 of the first QoS flow to the UPF network element; correspondingly, the UPF network element receives information 2 of the first QoS flow from the SMF network element.
  • the UPF network element creates a first QoS flow according to the information 2 of the first QoS flow.
  • the AF network element sends the first service flow to the UPF network element; correspondingly, the UPF network element receives the first service flow from the AF network element.
  • the AF network element may generate a first service flow in response to the first application service running on the UE, and send the first service flow to the UPF network element.
  • the first application service corresponds to multiple service flows
  • the AF network element may generate multiple service flows and send the multiple service flows to the UPF network element, and the multiple service flows include the first service flow.
  • the AF network element may send the multiple service flows to the UPF network element one by one, or may send the multiple service flows to the UPF network element together, which is not limited in the embodiments of the present application.
  • the UPF network element maps the first service flow to the first QoS.
  • the UPF may map the first service flow to the first QoS flow based on the service flow information of the first service flow.
  • the service flow information of the first service flow may come from the SMF network element, which is not shown in FIG4. It should be understood that if the UPF network element receives multiple service flows of the first application service from the AF network element, the UPF network element may map the multiple service flows to the QoS flows bound by the PCC rules corresponding to the multiple service flows, and the multiple service flows include the first service flow.
  • the UPF network element may also map the service flow in the first application service that has a corresponding QoS requirement with the first service flow to the first QoS flow.
  • the first QoS flow is also bound to a PCC rule corresponding to the first application service and having the same binding parameters as the first PCC rule.
  • the first QoS flow can also be used to carry the service flow in the first application service that has a corresponding QoS requirement with the first service flow.
  • the UPF network element uses the first QoS flow to carry the first service flow and sends the first service flow to the UE.
  • the specific implementation process of the UPF network element sending the first service flow to the UE through the first QoS flow may be: the UPF network element sends the first service flow to the RAN through the first QoS flow; after the RAN receives the first service flow, it sends the first service flow to the UE through the first QoS flow; the UE receives the first service flow.
  • the first QoS flow may also carry service flows with corresponding QoS requirements as the first service flow among multiple service flows of the first application service, but does not carry service flows that do not belong to the first application service.
  • the PCC rule corresponding to service flow 1 and the PCC rule of service flow 3 are bound to the same QoS flow (such as recorded as QoS flow 1), and the PCC rule corresponding to service flow 2 is bound to QoS flow 2, so that QoS flow 1 can carry service flow 1 and service flow 3, and QoS flow 2 can carry service flow 2, as shown in Figure 5A.
  • the PCC rule corresponding to service flow 1 is bound to QoS flow 1
  • the PCC rule corresponding to service flow 2 is bound to QoS flow 2
  • the PCC rule corresponding to service flow 3 is bound to QoS flow 3, so that QoS flow 1 can carry service flow 1, QoS flow 2 can carry service flow 2, and QoS flow 3 can carry service flow 3, as shown in Figure 5B.
  • the RAN may create a first QoS flow according to information 1 of the first QoS flow.
  • the RAN may release the first QoS flow, for example, due to insufficient network resources or other reasons.
  • the first service flow corresponding to the first QoS flow is one of multiple service flows of the first application service.
  • the RAN may collaboratively manage the multiple service flows of the first application service, as shown in FIG6 .
  • Fig. 6 shows a schematic diagram of a process flow of another communication method provided in an embodiment of the present application. As shown in Fig. 6, the process may include the following contents.
  • the SMF network element sends information 1 of the first QoS flow to the RAN; correspondingly, the RAN receives information 1 of the first QoS flow.
  • the first QoS flow is bound to the first PCC rule corresponding to the first service flow, and is used to carry the first service flow.
  • the first service flow is one of multiple service flows of the first application service.
  • the information 1 of the first QoS flow includes third information.
  • the third information can be used to indicate the association information between the multiple QoS flows corresponding to the first application service.
  • the multiple QoS flows corresponding to the first application service include the first QoS flow.
  • the information 1 of the first QoS flow may not include the third information, such as the SMF network element sending the third information to the RAN.
  • the third information please refer to the relevant content of S306, which will not be repeated here.
  • the RAN may determine the association relationship between the multiple QoS flows corresponding to the first application service based on the third information, that is, the multiple QoS flows correspond to the same application service. Further, the RAN may also maintain or store the association relationship between the multiple QoS flows corresponding to the first application service, that is, maintain or store the multiple QoS flows corresponding to the first application service.
  • the RAN may maintain at least one QoS flow corresponding to the same application service in a table format, such as each row in the table represents at least one QoS flow corresponding to the same application service, or each column in the table represents at least one QoS flow corresponding to the same application service.
  • Table 1 takes the example that each row of the table represents at least one QoS flow corresponding to the same application service. As shown in Table 1, QoS flow 1, QoS flow 2 and QoS flow 3 correspond to the same application service; QoS flow 4 and QoS flow 5 correspond to the same application service; QoS flow 6 corresponds to an application service.
  • the at least one QoS flow is a QoS flow other than the first QoS flow among the multiple QoS flows corresponding to the first application service.
  • the RAN may create the first QoS flow according to information 1 of the first QoS flow.
  • the RAN may create at least one QoS flow according to the third information.
  • the RAN may determine the at least one QoS flow according to the association between the first QoS flow and the multiple QoS flows corresponding to the first application service, and create the at least one QoS flow, so that resources can be allocated to multiple service flows of the first application service at the same time. Source or reserved resources to ensure that multiple service flows of the first application service can be sent or received synchronously.
  • the at least one QoS flow is a QoS flow other than the first QoS flow among the multiple QoS flows corresponding to the first application service.
  • the RAN releases the first QoS flow due to insufficient network resources or other reasons.
  • the RAN can release the at least one QoS flow according to the third information.
  • the RAN can determine the at least one QoS flow and release the at least one QoS flow according to the association between the first QoS flow and the multiple QoS flows corresponding to the first application service, so that the resources of the multiple QoS flows corresponding to the first application service can be released, ensuring that the transmission of the multiple service flows of the first application service can be synchronously interrupted.
  • S604 RAN sends the seventh message to the SMF network element; correspondingly, the SMF network element receives the seventh message from RAN.
  • the seventh message can be used to indicate that multiple QoS flows corresponding to the first application service are released.
  • the seventh message can be understood as one message, and can also be understood as multiple messages.
  • the seventh message is one message, and the one message can be used to indicate that all QoS flows corresponding to the first application service are released.
  • the seventh message is multiple messages, one of which is used to indicate that one QoS flow among the multiple QoS flows corresponding to the first application service is released, and the multiple messages correspond one-to-one to the corresponding multiple QoS flows of the first application service.
  • RAN can collaboratively manage multiple QoS flows corresponding to the first application service based on the association relationship between the multiple QoS flows corresponding to the first application service. Since the service flow carried by each QoS flow in the multiple QoS flows belongs to the first application service and does not carry service flows of other application services, the normal transmission of service flows of other application services will not be affected during the collaborative management process.
  • the service flows of different application services are mapped to different QoS flows, and one QoS flow carries one service flow or carries multiple service flows of the same application service, so that when multiple service flows of an application service are collaboratively managed at the granularity of QoS, the normal transmission of service flows of other application services will not be affected.
  • the SMF network element can collaboratively manage multiple service flows of the first application service at the granularity of service flow, and the normal transmission of service flows of other application services will not be affected. This implementation is introduced below in conjunction with Figures 7 to 8.
  • Fig. 7 shows a schematic flow chart of another communication method provided in an embodiment of the present application. As shown in Fig. 7, the flow chart may include the following contents.
  • S701, S702, S703 are substantially the same as S301, S302, S303 in FIG3 , except that:
  • S704 The SMF network element maintains or stores the association relationship between multiple service flows of the first application service.
  • FIG7 takes the SMF network element maintaining the association relationship between multiple service flows of the first application service as an example.
  • the SMF network element may determine the association relationship between multiple service flows of the first application service, and maintain or store the association relationship between multiple service flows of the first application service. For example, the SMF network element may receive multiple PCC rules corresponding to the first application service from the PCF network element, determine that multiple service flows corresponding to the multiple PCC rules belong to the same application service based on each of the multiple PCC rules including the first information, and maintain or store the association relationship that the multiple service flows belong to the same application service.
  • the SMF network element may maintain the service flows of the same application service in a table format, such as each row in the table represents at least one service flow of the same application service, or each column in the table represents at least one service flow of the same application service. It should be understood that the specific implementation method of the SMF network element maintaining the service flows of the same application service in the embodiment of the present application is not limited to this.
  • Table 2 takes the example that each row of the table represents at least one service flow of the same application service. As shown in Table 2, service flow 1, service flow 2 and service flow 3 belong to the same application service; service flow 4 and service flow 5 belong to the same application service; service flow 6 belongs to an application service.
  • the SMF network element may also maintain the association relationship between multiple PCC rules corresponding to the first application service.
  • the SMF network element may also maintain the association relationship between multiple QoS flows corresponding to the first application service.
  • For the specific implementation process please refer to the relevant content shown in the aforementioned S304a, which will not be repeated here.
  • S705 The SMF network element binds the first PCC rule to the second QoS flow.
  • the SMF network element can bind the first PCC rule to the second QoS flow in the following two ways.
  • Method 1 The SMF network element binds the first PCC rule to the second QoS flow, and the second QoS flow is not bound to the PCC rules corresponding to other application services.
  • the second QoS flow may be the first QoS flow in the above embodiment, that is, the second QoS flow in FIG7 may be replaced by the first QoS flow.
  • the second QoS flow may be QoS flow 1 or QoS flow 2 as shown in FIG5A, or QoS flow 1 or QoS flow 2 as shown in FIG5B.
  • the SMF network element binds the first PCC rule to the second QoS flow, and the PCC rules corresponding to other service flows can be bound to the second QoS flow.
  • the other service flow and the first service flow can belong to the same application service, or they can belong to different application services.
  • the other service flow has the same QoS requirement as the first service flow, that is, the PCC rule corresponding to the other service flow has the same binding parameters as the first PCC rule.
  • the second QoS flow can also be bound to a PCC rule that does not include the first information and has the same binding parameters as the first PCC rule.
  • the second QoS flow can also carry service flows that do not belong to the first application service.
  • the second QoS flow can be QoS flow 1 or QoS flow 2 shown in Figure 2.
  • the SMF network element sends information 1 of the second QoS flow to the RAN; correspondingly, the RAN receives information 1 of the second QoS flow.
  • RAN releases the second QoS flow. For example, RAN releases the second QoS flow due to insufficient network resources or other reasons.
  • S708 RAN sends the fifth message to the SMF network element; correspondingly, the SMF network element receives the fifth message from RAN.
  • the fifth message may be used to indicate or notify that the second QoS flow is released.
  • the fifth message may include the QFI of the second QoS flow.
  • the SMF network element determines a service flow that has not been released among multiple service flows of the first application service.
  • the SMF network element determines the unreleased service flows in the multiple service flows of the first application service based on the association relationship between the service flow of the first application service corresponding to the first QoS flow and the multiple service flows of the first application service.
  • the unreleased service flows in the multiple service flows of the first application service are service flows in the multiple service flows of the first application service except for the service flow of the first application service carried by the first QoS flow.
  • the first QoS flow can carry a service flow of the first application service (i.e., the first service flow); or carry multiple service flows of the first application service, and the multiple service flows include the first service flow.
  • the second QoS flow can also carry service flows of other application services.
  • the SMF network element releases the unreleased service flows among multiple service flows of the first application service from at least one QoS flow.
  • the at least one QoS flow is a QoS flow other than the second QoS flow among the multiple QoS flows corresponding to the first application service.
  • the RAN releases QoS flow 1, and service flows 1, 2, and 4 carried by the QoS flow 1 terminate transmission, and send a notification message that QoS flow 1 is released to the SMF network element; the SMF network element responds to the notification message, determines that the service flow among the multiple service flows of the application service 1 that has not been released is service flow 3 based on the association relationship between the multiple service flows of the locally maintained application service 1, and releases service flow 3 from QoS flow 2, as shown in Figure 8.
  • releasing a service flow from a QoS flow can be understood as releasing or deleting network resources of the service flow.
  • the second QoS flow is QoS flow 1 shown in FIG. 5A
  • the first application service is application service 1 shown in FIG. 5A
  • the first service flow is service flow 1 shown in FIG. 5A
  • the RAN releases QoS flow 1, service flow 1 and service flow 3 carried by the QoS flow 1 terminate transmission, and sends a notification message of QoS flow 1 being released to the SMF network element;
  • the SMF network element responds to the notification message, and determines that the service flow of the multiple service flows of the application service 1 that has not been released is service flow 2 based on the association relationship between the multiple service flows of the locally maintained application service 1, and releases service flow 2 from QoS flow 2. Since the QoS flow 2 carries a service flow, the SMF network element releases service flow 2 from QoS flow 2, which can also be understood as the SMF network element releasing QoS flow 2.
  • the RAN releases QoS flow 1, the service flow 1 carried by the QoS flow 1 terminates transmission, and sends a notification message that QoS flow 1 is released to the SMF network element; the SMF network element responds to the notification message, determines that the service flows of the multiple service flows of the application service 1 that have not been released are service flow 2 and service flow 3 based on the association relationship between the multiple service flows of the locally maintained application service 1, and releases service flow 2 from QoS flow 2 and releases service flow 3 from QoS flow 3.
  • the SMF network element sends a second message to the PCF network element; correspondingly, the PCF network element receives the second message from the SMF network element.
  • the second message may be used to request deactivation of multiple PCC rules corresponding to the first application service.
  • the second message may be understood as one message or as multiple messages.
  • the second message is one message, and the one message may be used to request deactivation of all PCC rules corresponding to the first application service.
  • the second message is multiple messages, one of which is used to request deactivation of one PCC rule among multiple PCC rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple PCC rules corresponding to the first application service.
  • the SMF network element may deactivate multiple PCC rules of the first application service.
  • the SMF network element can carry indication information 1, indication information 2 and indication information 3 in one message and send it to the PCF network element.
  • the indication information 2 is used to request the deactivation of the PCC rule corresponding to service flow 1
  • the indication information 3 is used to request the deactivation of the PCC rule corresponding to service flow 3.
  • the SMF network element releases service flow 1, and sends a message to the PCF network element for requesting the deactivation of the PCC rule corresponding to service flow 1; the SMF network element releases service flow 2, and sends a message to the PCF network element for requesting the deactivation of the PCC rule corresponding to service flow 2; the SMF network element releases service flow 3, and sends a message to the PCF network element for requesting the deactivation of the PCC rule corresponding to service flow 3.
  • deactivating a PCC rule may be understood as releasing the PCC rule, or as releasing resources corresponding to the PCC rule, or as deleting the PCC rule.
  • the PCF network element deactivates multiple PCC rules corresponding to the first application service according to the second message.
  • the PCF network element may respond to the plurality of messages and deactivate the plurality of PCC rules corresponding to the first application service one by one.
  • the PCC rule corresponding to the first application service in Figure 7 may be bound to the PCC rule of other application services, or may not be bound to the PCC rule of other application services.
  • the second QoS flow in Figure 7 can be replaced with the first QoS flow.
  • the RAN may send a first message to the SMF network element, and the first message is used to indicate that the first QoS flow is released.
  • the SMF network element releases the unreleased service flow from multiple service flows of the first application service from at least one QoS flow, which can be replaced by the SMF network element releasing the at least one QoS flow.
  • the SMF network element maintains the association relationship between multiple service flows of the first application service, and determines the service flows that have not been released in the multiple service flows of the first application service based on the association relationship.
  • the PCF network element maintains the association relationship between multiple service flows of the first application service, and determines the service flows that have not been released in the multiple service flows of the first application service based on the association relationship, as shown in FIG9 .
  • Fig. 9 shows a flow chart of another communication method provided in an embodiment of the present application.
  • the association relationship between multiple PCC rules corresponding to the first application service is maintained by a PCF network element.
  • S901, S902, S904, S905, S906 to S908 are substantially the same as S701, S702, S703, S705, S706 to S708 in FIG. 7 , except that:
  • the PCF network element maintains or stores the association relationship between multiple PCC rules corresponding to the first application service.
  • FIG9 takes the case where the PCF network element maintains the association relationship between multiple PCC rules corresponding to the first application service as an example.
  • the PCF network element may determine the association relationship between multiple PCC rules corresponding to the first application service based on the first information, and maintain or store the association relationship between multiple PCC rules corresponding to the first application service.
  • the PCF network element may also maintain or store the association relationship between multiple service flows of the first application service.
  • the SMF network element sends the sixth message to the PCF network element; correspondingly, the PCF network element receives the sixth message from the SMF network element.
  • the sixth message can be used to request deactivation of the PCC rules bound to the second QoS flow.
  • the SMF network element sends the sixth message to the PCF network element in response to the second QoS flow being released, to request deactivation of the PCC rules bound to the second QoS flow.
  • the PCC rules bound to the second QoS flow include the first PCC rules.
  • the PCC rules bound to the second QoS flow may also include PCC rules corresponding to other service flows, and the other service flows and the first service flow may belong to the same application service flow, or may belong to different application services.
  • the sixth message may include identification information of the PCC rules bound to the second QoS flow.
  • the PCF network element determines multiple PCC rules corresponding to the first application service.
  • the PCF network element may determine multiple PCC rules corresponding to the first application service according to the correspondence between the PCC rule bound to the second QoS flow and including the first information and multiple PCC rules corresponding to the first application service.
  • the PCF network element may determine the service flows that have not been released among the multiple service flows of the first application service, and determine the multiple PCC rules corresponding to the first application service, based on the association relationship between the service flows corresponding to the PCC rules bound to the second QoS flow and including the first information and the multiple service flows corresponding to the first application service.
  • the PCF network element determines the multiple PCC rules corresponding to the first application service based on the multiple service flows of the first application service, and the multiple service flows of the first application service include the service flows corresponding to the PCC rules bound to the second QoS flow and including the first information and the service flows that have not been released among the multiple service flows of the first application service determined.
  • the PCF network element may determine the multiple PCC rules corresponding to the first application service based on the PCC rules bound to the second QoS flow and including the first information and the fourth information.
  • the PCF network element deactivates multiple PCC rules corresponding to the first application service.
  • the PCF network element may deactivate multiple PCC rules corresponding to the first application service one by one, but the embodiment of the present application does not Limited to this.
  • the PCF network element sends the fourth message to the SMF network element; correspondingly, the SMF network element receives the fourth message from the PCF network element.
  • the fourth message may be used to indicate the deactivation of multiple PCC rules corresponding to the first application service, or the fourth message may be used to request the release of unreleased service flows among multiple service flows of the first application service.
  • FIG9 takes the fourth message indicating the deactivation of multiple PCC rules corresponding to the first application service as an example.
  • the fourth message may be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message may be used to indicate the deactivation of all PCC rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one PCC rule among multiple PCC rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple PCC rules corresponding to the first application service.
  • the PCF network element can carry indication information 4, indication information 5 and indication information 6 in one message and send it to the SMF network element, where indication information 4 is used to indicate the deactivation of the PCC rule corresponding to service flow 1, indication information 5 is used to indicate the deactivation of the PCC rule corresponding to service flow 2, and indication information 6 is used to indicate the deactivation of the PCC rule corresponding to service flow 3.
  • the PCF network element deactivates the PCC rule corresponding to service flow 1, and sends a message to the SMF network element to indicate the deactivation of the PCC rule corresponding to service flow 1; the PCF network element deactivates the PCC rule corresponding to service flow 2, and sends a message to the SMF network element to indicate the deactivation of the PCC rule corresponding to service flow 2; the PCF network element deactivates the PCC rule corresponding to service flow 3, and sends a message to the SMF network element to indicate the deactivation of the PCC rule corresponding to service flow 3.
  • the SMF network element releases the unreleased service flows among the multiple service flows of the first application service from at least one QoS flow according to the fourth message.
  • the at least one QoS flow is a QoS flow other than the second QoS flow among the multiple QoS flows corresponding to the first application service.
  • the SMF network element releases the unreleased service flows among the multiple service flows of the first application service from at least one QoS flow in response to the fourth message.
  • the SMF network element determines the multiple service flows of the first application service according to the fourth message, and releases the unreleased service flows among the multiple service flows of the first application service from at least one QoS flow according to the service flow of the first application service corresponding to the first QoS flow and the multiple service flows of the first application service.
  • the SMF network element may determine the multiple QoS flows corresponding to the first application service and determine the at least one QoS flow according to the fourth message.
  • the SMF network element may deactivate multiple PCC rules corresponding to the first application service, which is not shown in FIG. 9 .
  • the PCC rule corresponding to the first application service in FIG9 may be bound to the PCC rule of other application services, or may not be bound to the PCC rule of other application services.
  • the second QoS flow in FIG9 may be replaced with the first QoS flow.
  • the SMF network element may send a third message to the PCF network element, and the third message is used to request to deactivate the PCC rule bound to the first QoS flow.
  • the SMF network element can realize the coordinated management of multiple service flows of an application service based on the service flow. Since the SMF network element releases based on the service flow, compared to releasing the entire QoS flow, it can avoid affecting the normal transmission of service flows of other application services carried by the same QoS flow.
  • the methods provided by the embodiments of the present application are introduced from the perspective of the interaction between the SMF network element, the PCF network element and the RAN.
  • the SMF network element, the PCF network element or the RAN may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG10 shows a schematic diagram of the structure of a communication device 1000.
  • the communication device 1000 can implement the functions or steps implemented by the SMF network element, PCF network element or RAN in the above-mentioned various method embodiments.
  • the communication device may include a processing unit 1001 and a transceiver unit 1002.
  • the communication device 1000 may also include a storage unit 1003 (indicated by a dotted line in FIG10), and the storage unit 1003 may be used to store instructions (codes or programs) and/or data.
  • the processing unit 1001 and the transceiver unit 1002 may be coupled to the storage unit 1003.
  • the processing unit 1001 may read the instructions (codes or programs) and/or data in the storage unit 1003 to implement the corresponding method.
  • the above-mentioned units may be independently arranged or partially or fully integrated.
  • the transceiver unit 1002 may include a sending unit and a receiving unit.
  • the communication device 1000 can implement the functions or steps implemented by the SMF network element in the above-mentioned method embodiments.
  • the transceiver unit 1002 is used to receive a first policy and charging control rule from a policy control function network element, wherein the first policy and charging control rule includes first information, and the first information is used to associate one or more policy and charging control rules corresponding to the first application service. but.
  • the processing unit 1001 is configured to bind a first policy and charging control rule to a first quality of service flow, where the first quality of service flow is not bound to a policy and charging control rule that does not include the first information.
  • the transceiver unit 1002 is further configured to send information about the first quality of service flow to the first network element.
  • the transceiver unit 1002 is used to receive a first policy and charging control rule from a policy control function network element, where the first policy and charging control rule includes first information, and the first information is used to associate multiple policies and charging control rules corresponding to the first application service.
  • the processing unit 1001 is configured to bind a first policy and charging control rule to a first quality of service flow; and determine that the first quality of service flow is not bound to a policy and charging control rule that does not include the first information.
  • the transceiver unit 1002 is further configured to send information about the first quality of service flow to the first network element.
  • each of the multiple policies and charging control rules corresponding to the first application service includes first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the processing unit 1001 is further configured to determine that the first quality of service flow is not bound to a policy and charging control rule that does not include the first information.
  • the processing unit 1001 is further used to create the first quality of service flow before binding the first policy and billing control rule to the first quality of service flow; or, the first information is used to associate multiple policies and billing control rules corresponding to the first application service, and the processing unit 1001 is further used to determine the first quality of service flow that has been created based on the policy and billing control rule that has the same binding parameters as the first policy and billing control rule and includes the first information before binding the first policy and billing control rule to the first quality of service flow.
  • the first policy and charging control rule may further include second information
  • the second information may be used to indicate that the first policy and charging control rule is bound to a quality of service flow, and the quality of service flow is not bound to a policy and charging control rule that includes the first information and has the same binding parameters as the first policy and charging control rule;
  • the second information may be used to indicate that the first policy and charging control rule and the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule are bound to the same service quality flow.
  • the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule is bound to the same service quality flow, which can be understood as the policy and charging control rule corresponding to the service flow that has the same service quality requirement as the service flow corresponding to the first policy and charging control rule and belongs to the first application service.
  • the processing unit 1001 is further configured to determine the association relationship between multiple service flows of the first application service according to the first information.
  • the storage unit 1003 is configured to maintain or store the association relationship between multiple service flows of the first application service.
  • multiple measurement and charging control rules corresponding to the first application service are bound to multiple service quality flows, and the first network element is an access network network element; the transceiver unit 1002 is also used to receive a first message from the access network network element, and the first message is used to indicate that the first service quality flow is released; and the processing unit 1001 is also used to release the unreleased service flows in the multiple service flows of the first application service from at least one service quality flow, wherein the at least one service quality flow is a service quality flow other than the first service quality flow in the multiple service quality flows.
  • the processing unit 1001 may release the unreleased service flow from the multiple service flows of the first application service from the at least one quality of service flow in the following manner:
  • Determine the association relationship between multiple business flows of the first application service determine the unreleased business flows among the multiple business flows of the first application service based on the association relationship between the business flow corresponding to the first service quality flow and the multiple business flows of the first application service, and release the unreleased business flows among the multiple business flows of the first application service from at least one service quality flow based on the unreleased business flows among the multiple business flows of the first application service.
  • control transceiver unit 1002 sends a second message to the policy control function network element, where the second message is used to request deactivation of multiple policies and charging control rules corresponding to the first application service.
  • the control transceiver unit 1002 sends a third message to the policy control function network element, the third message is used to request to deactivate the policy and charging control rules bound to the first service quality flow; receive a fourth message from the policy control function network element, the fourth message is used to indicate to deactivate multiple policies and charging control rules corresponding to the first application service, or the fourth message is used to request to release the unreleased service flows in the multiple service flows of the first application service; determine the multiple service flows of the first application service according to the fourth message; and, from at least one service
  • the fourth message may be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message may be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • multiple policies and charging control rules corresponding to the first application service are bound to multiple service quality flows, and the information of the first service quality flow may include third information; or, the transceiver unit 1002 is also used to send third information to the first network element; wherein the third information is used to indicate the association of multiple service quality flows corresponding to the first application service.
  • the communication device 1000 can implement the functions or steps implemented by the PCF network element in the above-mentioned various method embodiments.
  • the transceiver unit 1002 is used to receive a request message from an application function network element, the request message is used to request to provide quality service for the first service flow, wherein the request message includes fourth information, the first information is used to associate multiple service flows of the first application service, and the first service flow is one of the multiple service flows of the first application service.
  • the processing unit 1001 is used to generate a first policy and charging control rule according to a request message, wherein the first policy and charging control rule includes first information, and the first information is used to associate one or more policies and charging control rules corresponding to the first application service.
  • the transceiver unit 1002 is further configured to send the first policy and charging control rule to the session management function network element.
  • the policy and charging control rule including the first information is not bound to the policy and charging control rule not including the first information.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the processing unit 1001 is further configured to determine the first information according to the fourth information.
  • the first policy and charging control rule may further include second information
  • the second information may be used to indicate that the first policy and charging control rule is bound to a quality of service flow, and the quality of service flow is not bound to a policy and charging control rule that includes the first information and has the same binding parameters as the first policy and charging control rule;
  • the second information may be used to indicate that the first policy and charging control rule and the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule are bound to the same service quality flow.
  • the policy and charging control rule including the first information and having the same binding parameters as the first measurement and charging control rule is bound to the same service quality flow, which can be understood as the policy and charging control rule corresponding to the service flow that has the same service quality requirement as the service flow corresponding to the first policy and charging control rule and belongs to the first application service.
  • the processing unit 1001 is further configured to determine the association relationship between multiple service flows of the first application service according to the first information.
  • the storage unit 1003 is configured to maintain or store the association relationship between multiple service flows of the first application service.
  • the transceiver unit 1002 is also used to receive a third message from a session management function network element, where the third message is used to request deactivation of the policy and charging control rules bound to the first quality of service flow; the processing unit 1001 is also used to determine multiple policies and charging control rules corresponding to the first application service based on the policy and charging control rules bound to the first quality of service flow including the first information and fourth information; and, deactivate the multiple policies and charging control rules corresponding to the first application service.
  • the transceiver unit 1002 is further used to send a fourth message to the session management function network element, where the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message is used to request the release of unreleased service flows among multiple service flows of the first application service.
  • the fourth message can be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the transceiver unit 1002 is further used to receive a second message from the session management function network element, and the second message is used to request to deactivate multiple policies and charging control rules corresponding to the first application service; the processing unit 1001 is further used to deactivate multiple policies and charging control rules corresponding to the first application service according to the second message.
  • the second message can be understood as one message or multiple messages.
  • the second message is one message, and the one message can be used to request to deactivate all policies and charging control rules corresponding to the first application service. Policy and charging control rules.
  • the second message is a plurality of messages, one of which is used to request deactivation of one of the plurality of policies and charging control rules corresponding to the first application service, and the plurality of messages correspond one-to-one to the plurality of policies and charging control rules corresponding to the first application service.
  • the communication device 1000 may implement the functions or steps implemented by the RAN in the above-mentioned various method embodiments.
  • the transceiver unit 1002 is used to receive information about a first quality of service flow from a session management function network element, where the information about the first quality of service flow includes third information, and the third information is used to associate multiple quality of service flows corresponding to the first application service.
  • Processing unit 1001 is used to create at least one quality of service flow according to the third information when the first quality of service flow is created; or to release at least one quality of service flow according to the third information when the first quality of service flow is released; wherein the at least one quality of service flow is a quality of service flow among the multiple quality of service flows corresponding to the first application service except the first quality of service flow.
  • the processing unit 1001 is further configured to determine the at least one quality of service flow according to the first quality of service flow and the third information.
  • the communication device 1000 can implement the functions or steps implemented by the SMF network element in the above-mentioned method embodiments.
  • the transceiver unit 1002 is used to receive a fifth message from an access network element, where the fifth message is used to indicate that the second quality of service flow is released.
  • the processing unit 1001 is used to release the unreleased service flows in multiple service flows of the first application service from at least one service quality flow, wherein the at least one service quality flow is a service quality flow other than the second service quality flow in the multiple service quality flows corresponding to the first application service.
  • the transceiver unit 1002 is also used to receive a first policy and charging control rule from a policy control function network element before receiving a fifth message from an access network network element, the first policy and charging control rule including first information, and the first information is used to associate multiple policies and charging control rules corresponding to a first application service; the processing unit 1001 is also used to bind the first policy and charging control rule to a second quality of service flow; the transceiver unit 1002 is also used to send information about the second quality of service flow to the first network element.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the transceiver unit 1002 is further configured to determine the association relationship between multiple service flows of the first application service according to the first information.
  • the storage unit 1003 is configured to maintain or store the association relationship between multiple service flows of the first application service.
  • the processing unit 1001 is also used to determine the association relationship between multiple business flows of the first application service, and determine the business flows that have not been released among the multiple business flows of the first application service based on the association relationship between the business flow corresponding to the first service quality flow and the multiple business flows of the first application service.
  • the transceiver unit 1002 is also used to send a second message to the policy control function network element, and the second message is used to request to deactivate multiple policies and charging control rules corresponding to the first application service.
  • the second message can be understood as one message, and can also be understood as multiple messages.
  • the second message is one message, and the one message can be used to request to deactivate all policies and charging control rules corresponding to the first application service.
  • the second message is multiple messages, one of which is used to request to deactivate one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the transceiver unit 1002 is also used to send a sixth message to the policy control function network element, the sixth message is used to request to deactivate the policy and charging control rules bound to the second service quality flow; and, receive a fourth message from the policy control function network element, the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message can be understood as one message, and can also be understood as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • the processing unit 1001 is further configured to determine the service flow of the first application service according to the fourth message, and The service flow corresponding to the service quality flow and the multiple service flows of the first application service are used to determine the service flow that has not been released among the multiple service flows of the first application service.
  • the communication device 1000 can implement the functions or steps implemented by the PCF network element in the above-mentioned method embodiments.
  • the transceiver unit 1002 is used to receive a sixth message from the session management function network element, and the sixth message is used to request to deactivate the policy and charging control rules bound to the second service quality flow, and the first service flow corresponding to the second service quality flow is one of the multiple service flows of the first application service.
  • the processing unit 1001 is configured to determine a plurality of policies and charging control rules corresponding to the first application service; and deactivate the plurality of policies and charging control rules corresponding to the first application service.
  • the transceiver unit 1002 is also used to receive a request message from an application function network element, where the request message is used to request to provide quality service for a first service flow, wherein the request message includes fourth information, and the fourth information is used to associate multiple service flows of the first application service; the processing unit 1001 is also used to generate a first policy and billing control rule based on the request message, wherein the first policy and billing control rule includes first information, and the first information is used to associate multiple policies and billing control rules corresponding to the first application service; the transceiver unit 1002 is also used to send the first policy and billing control rule to the session management function network element.
  • each of the multiple policies and charging control rules corresponding to the first application service includes the first information.
  • the application service corresponding to the policy and charging control rule that does not include the first information is a different application service from the first application service.
  • the processing unit 1001 is further configured to determine the first information according to fourth information.
  • the processing unit 1001 is further configured to determine the association relationship between multiple service flows of the first application service.
  • the storage unit 1003 is configured to maintain or store the association relationship between multiple service flows of the first application service.
  • the processing unit 1001 may determine multiple policies and charging control rules corresponding to the first application service in the following manner: determine multiple policies and charging control rules corresponding to the first application service according to the fourth information and the PCC rules bound to the second service quality flow.
  • the transceiver unit 1002 is further used to send a fourth message to the session management function network element, and the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message is used to indicate the deactivation of multiple policies and charging control rules corresponding to the first application service, or the fourth message can be used to request the release of unreleased service flows in multiple service flows of the first application service.
  • the fourth message can be understood as one message or as multiple messages.
  • the fourth message is one message, and the one message can be used to indicate the deactivation of all policies and charging control rules corresponding to the first application service.
  • the fourth message is multiple messages, one of which is used to indicate the deactivation of one of the multiple policies and charging control rules corresponding to the first application service, and the multiple messages correspond one-to-one to the multiple policies and charging control rules corresponding to the first application service.
  • processing unit 1001 the transceiver unit 1002 and the storage unit 1003 can be directly obtained by referring to the relevant description in the method embodiments shown in any one of Figures 3, 4, 6, 7, and 9, and will not be repeated here.
  • a communication device 1100 provided in an embodiment of the present application is shown, wherein the communication device 1100 may be an SMF network element, capable of implementing the functions of the SMF network element in the method provided in an embodiment of the present application, or the communication device 1100 may be a PCF network element, capable of implementing the functions of the PCF network element in the method provided in an embodiment of the present application, or the communication device 1100 may be a RAN, capable of implementing the functions of the RAN in the method provided in an embodiment of the present application; or the communication device 1100 may also be a device capable of supporting the SMF network element to implement the corresponding functions in the method provided in an embodiment of the present application, or a device capable of supporting the PCF network element to implement the corresponding functions in the method provided in an embodiment of the present application, or a device capable of supporting the RAN to implement the corresponding functions in the method provided in an embodiment of the present application.
  • the communication device 1100 may be a chip system. In an embodiment of the present application, the
  • the communication device 1100 includes at least one processor 1120, which is used to implement or support the communication device 1100 to implement the functions of the SMF network element, PCF network element or RAN in the method provided in the embodiment of the present application. Please refer to the detailed description in the method example for details, which will not be repeated here.
  • the communication device 1100 may further include at least one memory 1130 for storing program instructions and/or data.
  • the memory 1130 is coupled to the processor 1120.
  • the coupling in the embodiment of the present application is an indirect coupling or communication connection between devices, units or modules, which may be electrical, mechanical or other forms, for information exchange between devices, units or modules.
  • the processor 1120 may be coupled to the memory 1130. Collaborative operation.
  • the processor 1120 may execute program instructions and/or data stored in the memory 1130 so that the communication device 1100 implements the corresponding method.
  • At least one of the at least one memory may be included in the processor.
  • the memory 1130 may be an independent existence, such as an off-chip memory, connected to the processor 1120 via a communication bus (represented by a thick line 1140 in FIG. 11).
  • the memory 1130 may also be integrated with the processor 1120.
  • the communication device 1100 may further include a communication interface 1110, which is used to communicate with other devices through a transmission medium, so that the device in the communication device 1100 can communicate with other devices.
  • a communication interface 1110 which is used to communicate with other devices through a transmission medium, so that the device in the communication device 1100 can communicate with other devices.
  • the communication device is an SMF network element
  • the other device is a PCF network element or a RAN, etc.
  • the processor 1120 can use the communication interface 1110 to send and receive data.
  • the communication interface 1110 can specifically be a transceiver.
  • the transceiver unit 1002 may be a transceiver, which is integrated into the communication device 1100 to form a communication interface 1110 .
  • the specific connection medium between the communication interface 1110, the processor 1120 and the memory 1130 is not limited in the embodiment of the present application.
  • the memory 1130, the processor 1120 and the communication interface 1110 are connected through the communication bus 1140, and the connection mode between other components is only for schematic illustration and is not limited thereto.
  • the communication bus 1140 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in FIG. 11, but it does not mean that there is only one communication bus or one type of communication bus.
  • the processor 1120 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiment of the present application.
  • the general-purpose processor may be a microprocessor or any conventional processor, etc.
  • the steps of the method disclosed in the embodiment of the present application may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.
  • the memory 1130 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as a random-access memory (RAM).
  • the memory is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.
  • the memory in the embodiment of the present application may also be a circuit or any other device that can realize a storage function, for storing program instructions and/or data.
  • An embodiment of the present application also provides a communication system.
  • the communication system includes at least one of an SMF network element, a PCF network element or a RAN.
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions, which, when executed on a computer, enable the computer to execute the methods in the above embodiments.
  • An embodiment of the present application also provides a computer program product, including instructions, which, when executed on a computer, enables the computer to execute the methods in the above embodiments.
  • the embodiment of the present application provides a chip system, which includes a processor and may also include a memory, for implementing the functions of the SMF network element, PCF network element or RAN in the above method.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physically separate.
  • the unit may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请实施例提供一种通信方法及装置，用于避免因对一个应用业务的多个业务流进行协同管理而导致其它应用业务的业务流不能正常传输的问题。在该方法中，SMF网元接收来自PCF网元的第一PCC规则，该第一PCC规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个QoS流；将第一PCC规则与第一QoS流绑定，该第一QoS流不与不包括第一信息的PCC规则绑定；以及，向第一网元发送第一QoS流的信息。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2022年10月03日提交中国国家知识产权局、申请号为202211217390.9、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
服务质量(quality of service，QoS)控制是用来解决网络延迟、拥塞、丢包、抖动等问题的一种技术，以为指定的网络通信提供更好的服务能力。QoS控制的最细粒度是QoS流(QoS flow)。应用业务的业务流通过QoS流进行承载。其中，具有相同QoS需求的多个业务流可以被映射到同一个QoS流中。
一个应用业务可对应多个业务流，如游戏应用对应视频数据流、音频数据流等，这些业务流的QoS需求可以不同，这就意味着同一个应用业务的多个业务流可以被映射到不同的QoS流中，即一个应用业务可对应多个QoS流。一个应用业务对应的QoS流之间需要进行协同管理，以确保该应用业务的业务流的正常运行。例如，应用业务对应的多个QoS流中的部分QoS流因传输资源等原因导致不能传输，那么剩余部分QoS流没有继续传输的必要，可中断该剩余部分QoS流的传输。而一个QoS流又可以被多个具有相同QoS需求、且属于不同应用业务的业务流映射。一个应用业务对应的多个QoS流可能承载其它应用业务的业务流。那么在对应用业务对应的多个QoS流进行协同管理时，会影响该多个QoS流所承载的其它应用业务的业务流的正常传输。
发明内容
本申请实施例提供一种通信方法及装置，用于避免因对一个应用业务对应的多个QoS流进行协同管理而导致其它应用业务的业务流不能正常传输的问题。
第一方面，本申请实施例提供一种通信方法，该方法可由会话管理功能网元执行，或者由会话管理功能网元的部件执行。在该方法中，会话管理功能网元接收来自策略控制功能网元的第一策略与计费控制规则，该第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；将第一策略与计费控制规则与第一服务质量流绑定，该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定；以及，向第一网元发送第一服务质量流的信息。
或者，会话管理功能网元接收来自策略控制功能网元的第一策略与计费控制规则，该第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；将第一策略与计费控制规则与第一服务质量流绑定；确定该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定；以及，向第一网元发送第一服务质量流的信息。
其中，该第一网元为接入网网元或用户面功能网元。本申请实施例对会话管理功能网元向第一网元发送第一服务质量流的信息以及会话管理功能网元确定第一服务质量流不与不包括第一信息的策略与计费控制规则绑定的执行顺序不作限定。例如，会话管理功能网元可以在将第一策略与计费控制规则与第一服务质量流绑定之后，向第一网元发送第一服务质量流的信息。
在本申请实施例中，第一应用业务为在终端上使用的应用业务。第一服务质量流不与不包括第一信息的策略与计费控制规则绑定，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则。第一信息也可以指示根据所述包括第一信息的策略与计费控制规则建立的第一服务质量流不与其它应用业务对应的策略与计费控制绑定。即第一服务质量流所绑定的策略与计费控制规则只对应于第一应用业务，也就是说该第一服务质量流承载第一应用业务的业务流，不承载其它应用业务的业务流，从而可以使得该承载第一应用业务的多个业务流的一个或多个服务质量流不承载其它应用业务的业务流。由于承载该第一应用业务的多个业务流的一个或多个服务质量流不承载其它应用业务的业务流，那么在对该第一应用业务的多个业务流进行协同管理时就不会影响到其它应用业务的业务流的正常传输。此外，由于第一信息还可以用于关联第一应用业务对应的多个策略与计费控制规则，还可以使得将同一应用业务中具有相同QoS需求的业务流通过同一QoS承载，从而减少QoS流的数量。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括第一信息。
通过在第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则中包括第一信息，使得在为第一应就业务的多个业务流创建的QoS流不与其它应用业务对应的策略与计费控制绑定。从而使得对第一应用的多个QoS流的管理不会影响到其它的应用的业务流的传输，从而提高QoS管理的精准度，提高用户体验。
在一种可能的实现方式中，不包括第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
不包括第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务，可以避免将其它应用的业务流绑定到对应于第一应用的QoS流，从而使得对第一应用的多个QoS流的管理不会影响到其它的应用的业务流的传输，从而提高QoS管理的精准度，提高用户体验。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元根据PCC规则中的第一信息确定该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定。通过上述实现方式，会话管理功能网元不将应用业务的策略与计费控制规则与第一服务质量流，能够使得承载第一业务流的服务质量流不承载其它应用业务的业务流。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元在将第一策略与计费控制规则与第一服务质量流绑定之前，创建该第一服务质量流；或者，第一信息用于关联第一应用业务对应的多个策略与计费控制规则，该会话管理功能网元在将第一策略与计费控制规则与第一服务质量流绑定之前，确定已经根据与该第一策略与计费控制规则具有相同绑定参数、且包括该第一信息的策略与计费控制规则创建的第一服务质量流。通过上述实现方式，一个服务质量流可以绑定一个策略与计费控制规则，或者流绑定同一个应用业务对应的、具有相同绑定参数的多个策略与计费控制规则。
在一种可能的实现方式中，该第一策略与计费控制规则还可以包括第二信息；
该第二信息可用于指示第一策略与计费控制规则与一个服务质量流绑定，该一个服务质量流不与包括第一信息、且与该第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；
或者，该第二信息可用于指示第一策略与计费控制规则与包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。其中，该包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流，可理解为与该第一策略与计费控制规则对应的业务流具有相同服务质量需求、且属于第一应用业务的业务流对应的策略与计费控制规则。
通过上述实现方式，可以通过显式指示的方式实现一个服务质量流绑定一个策略与计费控制规则，或者实现一个服务质量流绑定同一个应用业务对应的、具有相同绑定参数的多个策略与计费控制规则，实现方式灵活。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元根据第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，会话管理功能网元可以维护或存储该第一应用业务的多个业务流之间的关联关系。通过上述实现方式，会话管理功能网元可根据该第一信息，确定属于第一应用业务的多个业务流。
在一种可能的实现方式中，第一应用业务对应的多个测量与计费控制规则与多个服务质量流绑定，第一网元为接入网网元；该方法还可以包括：会话管理功能网元接收来自接入网网元的第一消息，第一消息用于指示第一服务质量流被释放；以及，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，至少一个服务质量流是该多个服务质量流中除了第一服务质量流之外的服务质量流。通过上述实现方式，会话管理功能网元可以实现对第一应用业务的多个业务流之间进行协同管理。
在一种可能的实现方式中，会话管理功能网元可通过如下方式从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流：
会话管理功能网元确定第一应用业务的多个业务流之间的关联关系，根据第一服务质量流对应的业务流和该第一应用业务的多个业务流之间的关联关系，确定该确定第一应用业务的多个业务流中未被释放的业务流，以及根据该第一应用业务的多个业务流中未被释放的业务流，从至少一个服务质量流中释放该第一应用业务的多个业务流中未被释放的业务流。
可选的，该会话管理功能网元还可以向策略控制功能网元发送第二消息，该第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
或者，会话管理功能网元可以向策略控制功能网元发送第三消息，该第三消息用于请求去激活第一服务质量流绑定的策略与计费控制规则；接收来自策略控制功能网元的第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息用于请求释放该第一应用业务的多个业务流中未被释放的业务流；根据该第四消息，确定第一应用业务的多个业务流；以及，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流。例如，会话管理功能网元可以根据第一QoS流对应的第一应用业务的业务流和该第一应用业务的多个业务流，确定第一应用业务的多个业务流中未被释放的业务流，以及根据该第一应用业务的多个业务流中未被释放的业务流，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
通过上述实现方式，会话管理功能网元可以自身触发从至少一个服务质量流中是释放第一应用业务的多个业务流中未被释放的业务流，或者可以响应于策略控制功能网元的第四消息从至少一个服务质量流中是释放第一应用业务的多个业务流中未被释放的业务流，实现方式灵活。
在一种可能的实现方式中，第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定，第一服务质量流的信息中可以包括第三信息；或者，会话管理功能网元可以向第一网元发送第三信息；其中，该第三信息用于指示关联该第一应用业务对应的多个服务质量流。通过上述实现方式，第一网元可根据该第三信息，确定多个服务质量流对应的多个业务流属于同一个应用业务。
第二方面，本申请实施例提供又一种通信方法，该方法可以由策略控制功能网元执行，或者由策略控制功能网元的部件执行。在该方法中，策略控制功能网元接收来自应用功能网元的请求消息，请求消息用于请求为第一业务流提供质量服务，其中，请求消息包括第四信息，第一信息用于关联第一应用业务的多个业务流，第一业务流是该第一应用业务的多个业务流中的一个；根据请求消息，生成第一策略与计费控制规则，其中，第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；以及，向会话管理功能网元发送该第一策略与计费控制规则。
在一种可能的实现方式中，包括该第一信息的策略与计费控制规则不与不包括第一信息的策略与计费控制规则绑定。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括该第一信息。
在一种可能的实现方式中，不包括第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
在一种可能的实现方式中，该方法还包括：策略控制功能网元根据该第四信息，确定该第一信息。
在一种可能的实现方式中，第一策略与计费控制规则还可以包括第二信息；
该第二信息可用于指示第一策略与计费控制规则与一个服务质量流绑定，该一个服务质量流不与包括第一信息、且与该第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；
或者，该第二信息可用于指示第一策略与计费控制规则与包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。其中，该包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流，可理解为与该第一策略与计费控制规则对应的业务流具有相同服务质量需求、且属于第一应用业务的业务流对应的策略与计费控制规则。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元根据第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，会话管理功能网元可以维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元接收来自会话管理功能网元的第三消息，第三消息用于请求去激活第一服务质量流绑定的策略与计费控制规则；根据第一服务质量流绑定包括该第一信息的策略与计费控制规则和第四信息，确定第一应用业务对应的多个策略与计费控制规则；以及，去激活第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元向会话管理功能网元发送第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元接收来自会话管理功能网元的第二消息，第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则；以及，根据第二消息，去激活第一应用业务对应的多个策略与计费控制规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
上述第二方面及第二方面各个可能的实现方式的有益效果，请参考第一方面及第一方面各个可能的实现方式的有益效果，此处不再赘述。
第三方面，本申请实施例提供又一种通信方法，该方法可以由接入网网元执行，或者由接入网网元的部件执行。在该方法中，接入网网元接收来自会话管理功能网元的第一服务质量流的信息，第一服务质量流的信息中包括第三信息，第三信息用于关联第一应用业务对应的多个服务质量流；在所述第一服务质量流被创建时，根据所述第三信息创建至少一个服务质量流；或者在第一服务质量流被释放时，根据第三信息释放至少一个服务质量流；其中，该至少一个服务质量流是该第一应用业务对应的多个服务质量流中除了该第一服务质量流的服务质量流。
在一种可能的实现方式中，该方法还可以包括：接入网网元根据第一服务质量流和第三信息，确定该至少一个服务质量流。
上述第三方面及第三方面各个可能的实现方式的有益效果，请参考第一方面及第一方面各个可能的实现方式的有益效果，此处不再赘述。
第四方面，本申请实施例提供再一种通信方法，该方法可以由会话管理功能网元执行，或者由该会话管理功能网元的部件执行。在该方法中，会话管理功能网元接收来自接入网网元的第五消息，第五消息用于指示第二服务质量流被释放；以及，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，该至少一个服务质量流是所述第一应用业务对应的多个服务质量流中除了第二服务质量流之外的服务质量流。
在本申请实施例中，会话管理功能网元从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，实现了以业务流为粒度对一个应用业务的多个业务流的协同管理。由于会话管理功能网元是以业务流为粒度进行释放的，相较于释放整个服务质量流而言，不会终止同一个服务质量流所承载的其它应用业务的业务流的传输，从而能够避免影响同一个服务质量流所承载其它应用业务的业务流的正常传输。
在一种可能的实现方式中，该方法还可以包括：在接收来自接入网网元的第五消息之前，会话管理功能网元接收来自策略控制功能网元的第一策略与计费控制规则，第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的多个策略与计费控制规则；将第一策略与计费控制规则与第二服务质量流绑定；以及，向第一网元发送第二服务质量流的信息。通过该实现方式，会话管理功能网元可将第一业务流对应的策略与计费控制规则与第二服务质量流绑定，该第二服务质量流除了承载第一业务流之外还可以承载其它应用业务的业务流。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
在一种可能的实现方式中，不包括该第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元根据该第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，会话管理功能网元可以维护或存储该第一应用业务的多个业务流之间的关联关系。通过上述实现方式，会话管理功能网元可根据该第一信息，确定属于第一应用业务的多个业务流。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元确定第一应用业务的多个业务流之间的关联关系，以及根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。通过上述实现方式，会话管理功能网元可自身确定该第一应用业务的多个业务流中未被释放的业务流，并基于确定出的该第一应用业务的多个业务流中未被释放的业务流，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，从而实现以业务流为粒度对第一应用业务的多个业务流的协同管理。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元向策略控制功能网元发送第二消息，该第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则，这样策略控制功能网元可响应于该第二消息，去激活该第一应用业务对应的多个策略与计费控制规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
在一种可能的实现方式中，该方法还可以包括：会话管理功能网元向策略控制功能网元发送第六消息，第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则；以及，接收来自策略控制功能网元的第四消息，该第四消息用于指示去激活该第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
可选的，该方法还可以包括：会话管理功能网元根据第四消息，确定第一应用业务的业务流，以及根据该第二服务质量流对应的业务流和该第一应用业务的多个业务流，确定该第一应用业务的多个业务流中未被释放的业务流。
通过上述实现方式，会话管理功能网元可响应于策略控制功能网元的第四消息确定该第一应用业务的多个业务流中未被释放的业务流，并基于确定出的该第一应用业务的多个业务流中未被释放的业务流，从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，从而实现以业务流为粒度对第一应用业务的多个业务流的协同管理。
第五方面，本申请实施例提供又一种通信方法，该方法可以由策略控制功能网元执行，或者由策略控制功能网元的部件执行。在该方法中，策略控制功能网元接收来自会话管理功能网元的第六消息，第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则，该第二服务质量流对应的第一业务流是第一应用业务的多个业务流中的一个；确定该第一应用业务对应的多个策略与计费控制规则；以及，去激活该第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元接收来自应用功能网元的请求消息，该请求消息用于请求为第一业务流提供质量服务，其中，请求消息包括第四信息，第四信息用于关联第一应用业务的多个业务流；根据请求消息，生成第一策略与计费控制规则，其中，第一策略与计费控制规则包括第一信息，所述第一信息用于关联该第一应用业务对应的多个策略与计费控制规则；以及，向会话管理功能网元发送第一策略与计费控制规则。
在一种可能的实现方式中，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
在一种可能的实现方式中，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元根据所述第四信息，确定所述第一信息。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元确定第一应用业务的多个业务流之间的关联关系。可选的，策略控制功能网元可以维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元确定该第一应用业务对应的多个策略与计费控制规则可以为：策略控制功能网元根据第四信息和第二服务质量流所绑定的PCC规则，确定第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，该方法还可以包括：策略控制功能网元向会话管理功能网元发送第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息用于指示去激活该第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
上述第五方面及第五方面各个可能的实现方式的有益效果，请参考第四方面及第四方面各个可能的实现方式的有益效果，此处不再赘述。
第六方面，本申请实施例提供一种通信装置。所述通信装置用于执行为上述第一方面及第一方面任一项可能的实现方式中所述的方法，或者用于执行上述第四方面及第四方面任一项可能的实现方式中所述的方法。该通信装置例如为会话管理功能网元，或为会话管理功能网元中的功能模块，例如基带装置或芯片系统等。一种可能的实现方式中，所述通信装置包括基带装置和射频装置。
另一种可能的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能单元，该功能单元称为收发单元，该功能单元能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能单元，收发单元是对这些功能单元的统称。
第七方面，本申请实施例提供又一种通信装置。所述通信装置用于执行为上述第二方面及第二方面任一项可能的实现方式中所述的方法，或者用于执行上述第五方面及第五方面任一项可能的实现方式中所述的方法。该通信装置例如为策略控制功能网元，或为策略控制功能网元中的功能模块，例如基带装置或芯片系统等。一种可能的实现方式中，所述通信装置包括基带装置和射频装置。
另一种可能的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能单元，该功能单元称为收发单元，该功能单元能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能单元，收发单元是对这些功能单元的统称。
第八方面，本申请实施例提供再一种通信装置。所述通信装置用于执行为上述第三方面及第三方面任一项可能的实现方式中所述的方法。该通信装置例如为接入网网元，或为接入网网元中的功能模块，例如基带装置或芯片系统等。一种可能的实现方式中，所述通信装置包括基带装置和射频装置。
另一种可能的实现方式中，所述通信装置包括处理单元(有时也称为处理模块)和收发单元(有时也称为收发模块)。收发单元能够实现发送功能和接收功能，在收发单元实现发送功能时，可称为发送单元(有时也称为发送模块)，在收发单元实现接收功能时，可称为接收单元(有时也称为接收模块)。发送单元和接收单元可以是同一个功能单元，该功能单元称为收发单元，该功能单元能实现发送功能和接收功能；或者，发送单元和接收单元可以是不同的功能单元，收发单元是对这些功能单元的统称。
第九方面，本申请实施例提供一种通信装置。所述通信装置可以包括一个或多个处理器。可选地，该通信装置还可以包括存储器。其中，所述存储器用于存储一个或多个计算机程序或指令。所述一个或多个处理器用于执行所述存储器存储的所述一个或多个计算机程序或指令，以使得所述通信装置执行上述第一方面及第一方面任一项可能的实现方式中所述的方法，或者执行上述第四方面及第四方面任一项 可能的实现方式中所述的方法。
第十方面，本申请实施例提供又一种通信装置。所述通信装置可以包括一个或多个处理器。可选地，该通信装置还可以包括存储器。其中，所述存储器用于存储一个或多个计算机程序或指令。所述一个或多个处理器用于执行所述存储器存储的所述一个或多个计算机程序或指令，以使得所述通信装置执行上述第二方面及第二方面任一项可能的实现方式中所述的方法，或者执行上述第五方面及第五方面任一项可能的实现方式中所述的方法。
第十一方面，本申请实施例提供再一种通信装置。所述通信装置可以包括一个或多个处理器。可选地，该通信装置还可以包括存储器。其中，所述存储器用于存储一个或多个计算机程序或指令。所述一个或多个处理器用于执行所述存储器存储的所述一个或多个计算机程序或指令，以使得所述通信装置执行上述第三方面及第三方面任一项可能的实现方式中所述的方法。
第十二方面，本申请实施例还提供一种通信系统。所述通信系统包括上述第六方面所述的通信装置，上述第七方面所述的通信装置，或上述第八方面所述的通信装置中的至少一项。
第十三方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当其被运行时，使得上述第一方面及第一方面任一项可能的实现方式中所述的方法被实现，或者使得上述第四方面及第四方面任一项可能的实现方式中所述的方法被实现。
第十四方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当其被运行时，使得上述第二方面及第二方面任一项可能的实现方式中所述的方法被实现，或者使得上述第五方面及第五方面任一项可能的实现方式中所述的方法被实现。
第十五方面，本申请实施例提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序或指令，当其被运行时，使得上述第三方面及第三方面任一项可能的实现方式中所述的方法被实现。
第十六方面，本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述第一方面及第一方面任一项可能的实现方式中所述的方法被实现，或者使得上述第四方面及第四方面任一项可能的实现方式中所述的方法被实现。
第十七方面，本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述第二方面及第二方面任一项可能的实现方式中所述的方法被实现，或者使得上述第五方面及第五方面任一项可能的实现方式中所述的方法被实现。
第十八方面，本申请实施例还提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得上述第三方面及第三方面任一项可能的实现方式中所述的方法被实现。
第十九方面，本申请实施例还提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中的程序指令，以使得所述芯片所在装置实现上述第一方面及第一方面任一项可能的实现方式中所述的方法，或实现上述第四方面及第四方面任一项可能的实现方式中所述的方法。
第二十方面，本申请实施例还提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中的程序指令，以使得所述芯片所在装置实现上述第二方面及第二方面任一项可能的实现方式中所述的方法，或实现上述第五方面及第五方面任一项可能的实现方式中所述的方法。
第二十一方面，本申请实施例还提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中的程序指令，以使得所述芯片所在装置实现上述第三方面及第三方面任一项可能的实现方式中所述的方法。
附图说明
图1为本申请实施例中5G网络架构的一种示意图；
图2为本申请实施例中QoS流承载不同应用业务的业务流的示意图；
图3为本申请实施例提供的一种通信方法的流程示意图；
图4为本申请实施例提供的又一种通信方法的流程示意图；
图5A为本申请实施例提供的一个QoS流承载一个应用业务的至少一个业务流的示意图；
图5B为本申请实施例提供的一个QoS流承载一个应用业务的一个业务流的示意图；
图6为本申请实施例提供的又一种通信方法的流程示意图；
图7为本申请实施例提供的再一种通信方法的流程示意图；
图8为本申请实施例提供的对应用业务1的多个业务流进行协同管理的示意图；
图9为本申请实施例提供的再一种通信方法的流程示意图；
图10为本申请实施例提供的一种通信装置的示意图；
图11为本申请实施例提供的又一种通信装置的示意图。
具体实施方式
为了使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例中的术语“系统”和“网络”可被互换使用。“多个”是指两个或两个以上，鉴于此，本申请实施例中也可以将“多个”理解为“至少两个”。“至少一个”，可理解为一个或多个，例如理解为一个、两个或更多个。例如，包括至少一个，是指包括一个、两个或更多个，而且不限制包括的是哪几个。例如，包括A、B和C中的至少一个，那么包括的可以是A、B、C，A和B，A和C，B和C，或A和B和C。同理，对于“至少一种”等描述的理解，也是类似的。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如“A，B和C中的至少一个”包括A，B，C，AB，AC，BC或ABC。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
除非有特别说明，本申请实施例提及“第一”、“第二”等序数词用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度，并且“第一”、“第二”的描述也并不限定对象一定不同。
另外，在本申请实施例中，“示例性的”一词用于表示作例子、例证或说明。本申请中被描述为“示例性的”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”一词旨在以具体方式呈现概念。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
前面介绍了本申请实施例涉及的部分术语，接下来介绍本申请实施例适用的通信系统。
需要说明的是，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例的技术方案可以应用于各种通信系统。一个通信系统中，由运营者运营的部分可称为公共陆地移动网络(public land mobile network，PLMN)(也可以称为运营商网络、移动通信网络等)。PLMN是由政府或其所批准的经营者，为公众提供陆地移动通信业务目的而创建和经营的网络，主要是移动网络运营商(mobile network operator，MNO)为用户提供移动宽带接入服务的公共网络。本申请中所描述的PLMN，具体可以为符合第三代合作伙伴项目(3rd generation partnership project，3GPP)标准要求的网络，简称3GPP网络。3GPP网络通常包括但不限于第五代移动通信(5th-generation，5G)网络(简称5G网络)、第四代移动通信(4th-generation，4G)网络(简称4G网络)以及未来的其它通信系统如6G网络等。为了方便描述，本申请实施例中将以PLMN或5G网络为例进行说明。
图1是本申请实施例的一种网络架构示意图，它以3GPP标准化过程中定义的非漫游场景下基于服务化架构的5G网络架构为例。该网络架构可以包括三部分，分别是终端设备部分、数据网络(data network，DN)部分和PLMN部分。
终端设备部分可以包括终端设备，可通过运营商网络提供的接口(例如N1等)与运营商网络创建连接，使用运营商网络提供的数据和/或语音等服务。终端设备还可通过运营商网络访问数据网络，使用数据网络上部署的运营商业务，和/或第三方提供的业务。其中，上述第三方可为运营商网络和终端设备之外的服务方，可为终端设备提供其它数据和/或语音等服务。其中，上述第三方的具体表现形式，具体可根据实际应用场景确定，在此不做限制。
终端设备可简称为终端，是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。所 述终端设备可以是手机(mobile phone)、平板电脑(pad)、带无线收发功能的电脑、扩展现实(extended reality，XR)终端(如虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端等)、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、用户设备(user equipment，UE)、适应于物联网(Internet of Things，IoT)的终端设备(如智能工厂的终端设备、智能制造业的终端设备等)等。
数据网络，也可以称为分组数据网络(packet data network，PDN)，通常是位于运营商网络之外的网络，例如第三方网络。运营商网络可以接入多个数据网络，数据网络上可部署多种业务，可为终端设备提供数据和/或语音等服务。例如，数据网络可以是某智能工厂的私有网络，智能工厂安装在车间的传感器可以是终端设备，数据网络中部署了传感器的控制服务器，控制服务器可为传感器提供服务。传感器可与控制服务器通信，获取控制服务器的指令，根据指令将采集的传感器数据传送给控制服务器等。又例如，数据网络可以是某公司的内部办公网络，该公司员工的手机或者电脑可为终端设备，员工的手机或者电脑可以访问公司内部办公网络上的信息、数据资源等。
PLMN可以包括但不限于：网络切片选择功能(network slice selection function，NSSF)网元、鉴权服务器功能(authentication server function，AUSF)网元、网络开放功能(network exposure function，NEF)网元、网络存储功能(network repository function，NRF)网元、接入与移动性管理功能(access and mobility management function，AMF)网元、策略控制功能(policy control function，PCF)网元、统一数据管理(unified data management，UDM)网元、会话管理功能(session management function，SMF)网元、接入网(access network，AN)或无线接入网(radioaccess network，RAN)、以及用户面功能(user plane function，UPF)网元等等。上述PLMN中，除(无线)接入网部分之外的部分可以称为核心网(core network，CN)部分。
示例性的，下面对本申请的各个实施例可能涉及的网络功能进行简要介绍，另外图1还涉及其它网元，在此不做过多介绍。
AN，也称无线(Radio)AN，可以看作是运营商网络的子网络，是运营商网络中业务节点与终端设备之间的实施系统。终端设备要接入运营商网络，首先是经过(R)AN，进而可通过(R)AN与运营商网络的业务节点连接。本申请实施例中的接入网设备(RAN设备)，是一种为终端设备提供无线通信功能的设备，也可以称为网络设备、接入网网元等，RAN设备包括但不限于：5G系统中的下一代基站节点(next generation node base station，gNB)、长期演进(long term evolution，LTE)中的演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(base band unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、小基站设备(pico)、移动交换中心，或者未来网络中的网络设备等。采用不同无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同。为方便描述，本申请所有实施例中，上述为终端设备提供无线通信功能的装置统称为接入网设备或简称为RAN或AN。应理解，本文对接入网设备的具体类型不作限定。
应用功能，是一个控制面功能，部署在应用业务侧，可以由运营商部署也可以是外部第三方部署。应用功能通过与核心网的其它网络功能的交互，来支持流量路由控制、策略控制功能交互、接入网功能开放等服务。例如，在5G通信系统中，应用功能可以是AF，如图1所示；在未来通信系统，如6G通信系统中，应用功能仍可以是AF，或可能有其它的名称，本申请实施例不做限定。
网络开放功能，负责先应用业务提供网络相关的一些状态信息。例如，在5G通信系统中，网络开放功能可以是NEF，如图1所示；在未来通信系统，如6G通信系统中，网络开放功能仍可以是NEF，或可能有其它的名称，本申请实施例不做限定。
策略控制功能，是由运营商提供的控制面功能，它支持统一的策略框架来治理网络行为、向其它控制功能提供策略规则、策略决策相关的签约信息等。例如，在5G通信系统中，策略控制功能可以是PCF，如图1所示；在未来通信系统，如6G通信系统中，策略控制功能仍可以是PCF，或可能有其它的名称，本申请实施例不做限定。
会话管理功能，是由PLMN提供的控制面网络功能，负责管理终端设备的协议数据单元(protocol  data unit，PDU)。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传输数据。PDU会话可以由会话管理功能负责创建、维护和删除等。会话管理功能包括会话管理(如会话创建、修改和释放，包含用户面功能和AN之间的隧道维护等)、用户面功能的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。例如，在5G通信系统中，会话管理功能可以是SMF，如图1所示；在未来通信系统，如6G通信系统中，会话管理功能仍可以是SMF，或可能有其它的名称，本申请实施例不做限定。
用户面功能，是由PLMN提供的与数据网络DN进行通信的网关。用户面功能包括数据包路由和传输、数据包检测、业务用量上报、服务质量(quality of service，QoS)处理、合法监听、上行数据包检测、下行数据包存储等用户面相关的功能。例如，在5G通信系统中，用户面功能可以是UPF，如图1所示；在未来通信系统，如6G通信系统中，用户面功能仍可以是UPF，或可能有其它的名称，本申请实施例不做限定。
接入与移动性管理功能，是由PLMN提供的控制面网络功能，负责终端设备接入PLMN的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。例如，在5G通信系统中，接入与移动性管理功能可以是AMF，如图1所示；在未来通信系统，如6G通信系统中，接入与移动性管理功能仍可以是AMF，或可能有其它的名称，本申请实施例不做限定。
其中，PLMN中的各个网络功能既可以是在专用硬件上实现的网络元件，也可以是在专用硬件上运行的软件实例，或者是在适当平台上虚拟化功能的实例，例如，上述虚拟化平台可以为云平台。以及，该PLMN中的各个网络功能也可以称为网元、功能实体或者设备，例如，策略控制功能也可以称为策略控制功能网元、策略控制功能实体或策略控制功能设备等，会话管理功能也可以称为会话管理功能网元、会话管理功能实体或会话管理功能设备等，这里不再一一列举。
图1所示的PLMN中的网络功能还可以包括其它网络功能，例如，PLMN还包括统一数据存储(unified data repository，UDR)等(图1中未示出)，本申请实施例对于PLMN中包括的其它网络功能不作限定。另外，图1中所示的网络功能的名称在这里仅作为一种示例说明，并不作为对本申请实施例的方法适用的网络架构中包括的网络功能的限定。不同接入技术的系统中实现网络功能的设备名称可以不同，本申请实施例并不对此进行限定。
图1中Nnssf、Nausf、Nnef、Nnrf、Namf、Npcf、Nsmf、Nudm、Naf、N1、N2、N3、N4、以及N6为接口序列号。这些接口序列号的含义可参见第三代合作伙伴计划(3rd generation partnership project，3GPP)标准协议中定义的含义，在此不做限制。需要说明的是，图1中的各个网络功能之间的接口名称也仅仅是一个示例，在具体实现中，该系统架构的接口名称还可能为其它名称，本申请对此不作限定。
需要说明的是，图1所示的网络架构并不构成本申请实施例能够适用的通信系统的限定。图1所示的网络架构为5G系统架构，可选地，本申请实施例提供的技术方案除了可应用于5G系统外，还可以应用于第四代移动通信技术(the 4th generation，4G)系统中，例如LTE系统，或者还可以应用于下一代移动通信系统或其它类似的通信系统，具体的不做限制。
接下来介绍与本申请实施例相关的技术特征。
策略与计费控制(policy and charging control rule，PCC规则)规则，可用于对应用业务的业务流进行策略控制。该PCC规则由PCF网元生成，并发送给SMF网。SMF网元接收到来自PCF网元的PCC规则后，通过QoS流绑定(QoS flow binding)机制将该PCC规则绑定(binding)到相应的QoS流，之后该PCC规则对应的业务流可通过该PCC规则所绑定的QoS流承载。QoS流绑定机制的原理为：若PCC规则的绑定参数(如5G QoS标识符(5G QoS identifier，5QI)，优先级等)与QoS流的参数一致时，该PCC规则可与该QoS流绑定。目前的QoS流绑定机制中，具有相同绑定参数的多个PCC规则可以与同一个QoS流绑定。
需要说明的是，PCF可为一个业务流生成一个PCC规则，即一个业务流对应一个PCC规则；或者也可以为多个业务流生成一个PCC规则，即多个业务流对应一个PCC规则。即，多个业务流可对应一个或多个PCC规则。为了便于理解本申请实施例，后文在不作特殊说明的情况下以一个业务流对应一个PCC规则为例。
其中，本申请实施例中的将PCC规则与QoS流绑定，可以理解为将PCC规则与QoS流关联，或者也可以理解为将PCC规则映射到QoS流。
本申请实施例中的具有相应绑定参数的多个PCC规则，可理解为多个PCC规则具有一个或多个相同的绑定参数。绑定参数例如可以包括如下参数中的至少一项：5G QoS标识符(5G QoS identifier，5QI)，分配保留优先级(allocation and retention priority，ARP)，QoS通知控制(QoS notification control，QNC)，优先级(priority level)，平均窗口(averaging window)，以及最大数据突发量(maximum data burst volume)等。
本申请实施例中的具有相同绑定参数的多个PCC规则，可理解为多个PCC规则对应的多个业务流具有相同的QoS需求。相应的，具有相同绑定参数的多个PCC规则可以与同一个QoS流绑定，可理解为具有相同QoS需求的多个业务流可以被映射到同一个QoS流中，或者也可以理解为具有相同QoS需求的多个业务流可通过一个QoS流承载。
本申请实施例涉及的应用业务，可以是在终端上使用的XR业务，或者也可以是在终端上使用的游戏业务等，本申请实施例对应用业务的具体实现方式不作限定。本申请实施例涉及的业务流可以是发送给终端视频数据流，频数据流，和/或传感数据流等，还可以是终端发送给服务器端的视频数据流，音频数据流，和/或传感数据流等，本申请实施例对业务流的具体实现方式不作限定。另外，本申请实施例涉及的业务流可以是具有独立网际互连协议(internet protocol，IP)五元组的IP流，不同业务流也可以具有相同IP五元组，例如一个IP五元组所标识的视频数据流中的I帧构成一个业务流，该视频数据流中的P帧构成另外一个业务流。
一个应用业务可对应多个业务流，如游戏应用不仅会产生视频数据，还可以产生音频数据等，这些业务流的QoS需求可以不同，意味着同一个应用业务对应的多个PCC规则与不同的QoS流绑定，也就是同一个应用业务的多个业务流可以被映射到不同的QoS流中，即包括多个业务流的一个应用业务可对应多个QoS流。图2以应用业务1、应用业务2和应用业务3为例，应用业务1包括三个业务流，分别记为业务流1、业务流2和业务流3；应用业务2包括一个业务流，记为业务流4；应用业务3包括一个业务流，记为业务流5。如图2所示，业务流1、业务流2和业务流4的QoS需求相同，该业务流1、业务流2和业务流4被映射到QoS流1，即该QoS流1承载有应用业务1的业务流和应用业务2的业务流；业务流3和业务流5的QoS需求相同，该业务流3和业务流5被映射到QoS流2，即该QoS流2承载有应用业务1的业务流和应用业务3的业务流。
为了确保多个业务流所属的一个应用业务能够正常运行，需要对该应用业务的多个业务流进行协同管理。例如，应用业务对应的多个QoS流中的部分QoS流因传输资源等原因导致不能被传输，那么剩余部分QoS流没有继续传输的必要，可中断该剩余部分QoS流的传输，即释放剩余部分QoS流。但是一个QoS流又可以被多个相同QoS需求、且属于不同应用业务的业务流映射，那么在释放剩余部分QoS流时，会影响该剩余部分QoS流所承载的其它应用业务的业务流的正常传输。
以图2为例，假设QoS流1承载的业务流可以被传输，但QoS流2因传输资源等原因导致该QoS流2承载的业务流不能被传输，该QoS流2被释放。该QoS流2承载了应用业务1的部分业务流，那么应用业务1的业务流1和业务流2没有传输的必要，无需为该业务流1和业务流2预留资源，可以释放QoS流1，但是该QoS流1还承载有应用业务2的业务流4，释放QoS流1就会影响该应用业务2的业务流4的正常传输。
鉴于此，本申请实施例提供一种通信方法及装置，在该方法中通过不将具有相同绑定参数、但对应于不同应用业务的多个PCC规则绑定到同一个QoS流中，即一个QoS流中承载一个应用业务的一个或多个业务流，这样一个应用业务对应的多个QoS流中的每个QoS流不承载其它应用业务的业务流，意味着在对该一个应用业务对应的多个QoS流进行协同管理时不会影响到其它应用业务的业务流的正常传输，从而能够避免因对一个应用业务对应的多个QoS流进行协同管理而导致其它应用业务的业务流不能正常传输的问题。
接下来结合附图介绍本申请实施例提供的一种通信方法及装置。该方法可以应用于图1所示的通信系统中。为了便于理解，下文以本申请实施例应用于图1所示的通信系统为例进行描述。本申请实施例涉及的接入网网元、应用功能网元、网络开放功能网元、策略控制功能网元、会话管理功能网元、用户面功能网元、接入与移动性管理功能网元可以分别是图1中的RAN、AF网元、NEF网元、PCF网元、SMF网元、UPF网元、AMF网元，也可以是未来通信如第六代(6th generation，6G)网络中具有上述RAN、AF网元、NEF网元、PCF网元、SMF网元、UPF网元、AMF网元的功能的网元，本申请实施 例对此不限定。为方便说明，本申请实施例以接入网网元、应用功能网元、网络开放功能网元、策略控制功能网元、会话管理功能网元、用户面功能网元、接入与移动性管理功能网元分别为上述RAN、AF网元、NEF网元、PCF网元、SMF网元、UPF网元、AMF网元为例进行说明。以及，本申请实施例涉及的终端设备可以是图1中的UE。
图3示出了本申请实施例提供的通信方法的流程示意图。如图3所示，该流程可包括如下内容。
S301：AF网元向PCF网元发送请求消息1；相应的，PCF网元接收来自AF网元的请求消息1。
该请求消息1可用于请求为第一业务流提供质量服务。该请求消息1中包括第四信息。该第四信息可用于关联第一应用业务的一个或多个业务流。本申请实施例中第一应用业务对应一个或多个业务流，为了便于理解本申请实施例，后文在没有说明的情况下以第一应用业务对应多个业务流为例进行描述。其中，第一业务流是该第一应用业务的多个业务流中的一个业务流。其中有关应用业务和业务流的描述请参考前面相关的技术特征的描述，此处不再赘述。例如，AF网元可以在UE注册第一应用业务的过程中，或者在UE运行该第一应用业务的过程中等，向PCF网元发送请求消息1，以请求为第一业务流提供质量服务。
在S301中，AF网元向PCF网元发送请求消息1，以请求为第一业务流提供质量服务。应理解的是，AF网元可以向PCF网元发送用于请求为该第一应用业务的多个业务流提供质量服务的多个请求消息，即AF网元针对第一应用业务的多个业务流中的每个业务流向PCF网元用于请求提供质量服务的请求消息。这多个请求消息中包括请求消息1。该多个请求消息可以逐一发送，也可以一起发送，本申请实施例对此不作限定。
本申请实施例涉及的关联第一应用业务的多个业务流，可理解为该多个业务流属于同一个应用业务，或者理解为该多个业务流的QoS需求需要同时得到保障。而当第四信息关联第一应用业务的一个业务流时，表明该一个业务流属于第一应用业务的业务流，且该第一应用业务不存在其它业务流。
本申请实施例涉及的第四信息用于关联第一应用业务的多个业务流，可理解为该第四信息用于指示第一应用业务的多个业务流之间的关联关系；或者也可以理解为使用该第四信息指示多个业务流属于同一个应用业务；或者还可以理解为该第四信息用于指示该第一业务流是第一应用业务的多个业务流中的一个业务流。
一种实现方式中，该第四信息可以是一个标识信息。例如，该第四信息可以是第一应用业务的标识信息，用于指示该第一应用业务；或者该第四信息也可以是预先配置或定义的一个标识信息，在此情况下，同一应用业务的多个业务流对应相同的标识信息。例如，AF网元向PCF网元发送用于请求为该第一应用业务的多个业务流提供质量服务的多个请求消息，该多个请求消息中的每个请求消息皆包括该第四信息，这样PCF网元接收到该多个请求消息后，根据该多个请求消息中的每个请求消息皆携带第四信息，可以确定该多个请求消息对应的多个业务流属于同一个应用业务。
在一种示例中，该请求消息1还可以包括第一业务流的标识信息和第一业务流对应的QoS参数中的至少一项。第一业务流的标识信息可用于标识第一业务流，例如可以是IP五元组信息、或三元组信息等。第一业务流对应的QoS参数，是该第一业务流的QoS需求所对应的参数，例如可包括但不限定于丢包率、带宽需求、或时延需求等。
在S301中，AF网元向PCF网元发送的请求消息1可经过NEF网元中转到达PCF网元，也可以不经过NEF网元中转，图3中以请求消息1不经过NEF网元中转为例。例如，AF网元可以向NEF网元发送请求消息1，NEF网元接收到该请求消息1后，将请求消息1转发给PCF网元。
S302：PCF网元根据该请求消息1，生成第一PCC规则。
其中，第一PCC规则包括第一信息。该第一信息可用于关联第一应用业务对应的一个或多个PCC规则。该第一应用业务对应的多个PCC规则包括该第一PCC规则。在S302中，PCF网元响应于请求消息1，可以为第一业务流生成第一PCC规则。该第一PCC规则可用于对第一业务流进行策略控制。例如，PCF网元响应于请求消息1，可以根据第四信息、第一业务流的标识信息和第一业务流对应的QoS参数，生成该第一PCC规则。
前述提到本申请实施例涉及的第一应用业务对应一个或多个业务流，若第一应用业务对应一个业务流，该第一应用业务可对于一个PCC规则，若第一应用业务对应多个业务流，该第一应用业务可对应一个或多个PCC规则。即，本申请实施例涉及的第一应用业务对应一个或多个PCC规则。为了便于理 解本申请实施例，后文在不作特殊说明的情况下以第一应用业务对应多个PCC规则为例。
本申请实施例涉及的第一信息用于关联第一应用业务对应的多个PCC规则，可理解为第一信息用于指示该一应用业务对应的多个PCC规则之间的关联关系；或者也可以理解为使用第一信息指示多个PCC规则对应于同一个应用业务；或者还可以理解为第一信息用于指示第一PCC规则是第一应用业务对应的多个PCC规则中的一个PCC规则。其中，第一应用业务对应的多个PCC规则可替换为第一应用业务的多个业务流对应的PCC规则。
示例性的，PCF网元可根据第四信息，确定第一信息。例如，PCF网元可根据第一应用业务的多个业务流之间的关联关系，确定该第一信息。该第一信息例如可以是一个标识信息，如是第一应用业务的标识信息，或者是预先配置或预定的一个标识信息，具体实现方式可参考第四信息的实现方式，此处不再赘述。
在本申请实施例中，第一应用业务对应的多个PCC规则中的每个PCC规则可包括该第一信息，其它应用业务对应的PCC规则中不包括该第一信息，即不包括第一信息的PCC规则对应的应用业务与第一应用业务是不同的应用业务。这样，SMF网元接收到来自PCF网元的第一应用业务对应的多个PCC规则后，根据该多个PCC规则中的每个PCC规则皆包括第一信息，可以确定该多个PCC规则对应的业务流相关联。
该第一PCC规则还可以包括第一PCC规则的绑定参数，该绑定参数用于第一PCC规则绑定到QoS流。该绑定参数请参考前述描述，此处不再赘述。
可选的，该第一PCC规则还可以包括第一业务流的标识信息和第一业务流对应的QoS参数中的至少一项。有关第一业务流的标识信息和第一业务流对应的QoS参数的描述请参考S301的内容，此处不再赘述。
在一种可能的实现方式中，第一PCC规则还可以包括第二信息，该第二信息可用于指示该第一PCC规则与一个或多个QoS流绑定。
在一种示例中，该第二信息可用于指示该第一PCC规则与一个QoS流绑定，该一个QoS流不再与其它PCC规则绑定，相当于第一PCC规则与一个QoS绑定，且该一个QoS流仅与该第一PCC规则绑定。其中，该其它PCC规则与第一PCC规则可以对应于同一个应用业务，或者也可以对应于不同的应用业务。该其它PCC规则的绑定参数与第一PCC规则的绑定参数可以相同，也可以不同。例如，该第一信息可用于指示第一PCC规则与一个QoS流绑定，该一个QoS流不绑定与第一PCC规则具有相同绑定参数、且包括第一信息的PCC规则，这样可以实现同一应用业务对应的、且具有相同绑定参数的多个PCC规则不绑定到同一个QoS流。例如，PCF网元根据第四信息确定第一应用业务对应于一个业务流，生成该第二信息以指示该第一PCC规则与一个QoS流绑定，该一个QoS流不再与其它PCC规则绑定。另外，该第二信息与第一信息可以是一个信息，在此情况下，该第一信息用于关联第一应用业务对应的多个PCC规则，以及指示第一PCC规则与一个QoS流绑定，且该一个QoS流不在与其它PCC规则绑定；或者也可以是不同的两个信息，本申请实施例对此不做限定。
在另一种示例中，该第二信息可用于指示与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则与该第一PCC规则绑定到同一个QoS流，这样可以实现同一个应用业务对应的、具有相同绑定参数的多个PCC规则可以绑定到同一个QoS流。例如，PCF网元可根据第一应用业务的多个业务流的QoS需求，确定该第一应用业务中除了第一业务流之外的至少一个业务流的QoS需求与第一业务流的QoS相同，生成该第二信息以指示该第一PCC规则可以与其它包括第一信息、且与第一PCC规则具有相同绑定参数的PCC规则绑定到一个QoS流。另外，该第二信息与第一信息可以是一个信息，在此情况下，该第一信息用于关联第一应用业务对应的多个PCC规则，以及指示与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则与该第一PCC规则绑定到同一个QoS流；或者也可以是不同的两个信息，本申请实施例对此不做限定。
S303：PCF网元向SMF网元发送第一PCC规则；相应的，SMF网元接收来自PCF网元的第一PCC规则。
SMF网元接收到来自PCF网元的第一PCC规则后，可以执行S304a的内容，或者也可以执行S304b的内容。即S304a和S304b为两个并列的步骤，图3中用虚线表示。
S304a：SMF网元确定已经根据与第一PCC规则具有相同绑定参数、且包括第一信息的PCC规则创建的第一QoS流。
其中，第一QoS流不与不包括第一信息的PCC规则绑定。例如，SMF根据第一信息确定第一QoS流不与不包括第一信息的PCC规则绑定。该不包括第一信息的PCC规则对应的第一应用业务与第一应用业务是不同的应用业务。不包括第一信息的PCC规则的绑定参数与第一PCC规则的绑定参数可以相同，也可以不同，本申请实施例对此不作限定。例如，SMF网元可以确定已经根据包括第一信息的PCC规则创建好的QoS流，并确定该已经根据包括第一信息的PCC规则创建好的QoS流不与不包括第一信息的PCC规则绑定，即SMF网元可以确定已经根据包括第一信息的PCC规则创建好的QoS流不与其它应用业务对应的PCC规则绑定。例如，SMF网元基于QoS流绑定机制，将PCC规则与QoS流绑定，并维护或存储PCC规则与QoS流之间的绑定关系，该PCC规则与QoS流之间的绑定关系可包括PCC规则以及基于该PCC规则创建好或该PCC规则绑定的QoS流。进一步，SMF网元可以根据第一应用对应的多个PCC规则之间的关联关系以及PCC规则与QoS流之间的绑定关系，确定已经根据包括第一信息的PCC规则创建好的QoS流。其中的QoS流绑定机制请参考前述描述，此处不再赘述。
可选的，SMF网元根据该第一信息，确定该第一应用业务对应的多个PCC规则之间的关联关系，以及维护或存储该第一应用业务对应的多个PCC规则之间的关联关系。可选的，SMF网元可根据第一应用业务对应的多个PCC规则之间的关联关系和PCC规则与QoS流之间的绑定关系，确定第一应用业务对应的多个QoS流之间的关联关系，以及维护或存储该第一应用业务对应的多个PCC规则之间的关联关系。可选的，SMF网元可根据该第一应用业务对应的多个PCC规则之间的关联关系或第一应用业务对应的多个PCC规则，确定第一应用业务的关联关系，以及维护或存储该第一应用业务的关联关系。
在一种示例中，SMF网元接收到第一PCC规则后，可以根据第一信息确定是否存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流。在本示例中，SMF网元确定存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流，进一步该SMF网元可以确定该第一QoS流，如获取该第一QoS流的信息、参数等。
在又一种示例中，第一PCC规则包括第二信息，该第二信息可用于指示与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则与该第一PCC规则绑定到同一个QoS流，在此情况下，SMF网元根据该第二信息，可以确定是否存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流。在本示例中，SMF网元确定存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流，进一步该SMF网元可以确定该第一QoS流。
S304b：SMF网元根据第一PCC规则创建第一QoS流。
在一种示例中，SMF网元接收到第一PCC规则后，可以根据第一信息确定第一应用业务对应于一个业务流。在此情况下，SMF网元根据该第一PCC规则创建第一QoS流。
在一种示例中，SMF网元接收到第一PCC规则后，可以根据第一信息确定是否存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流。在本示例中，SMF网元确定不存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流，进一步该SMF网元可以根据该第一PCC规则，创建第一QoS流。
在又一种示例中，第一PCC规则包括第二信息，该第二信息可用于指示与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则与该第一PCC规则绑定到同一个QoS流。在此情况下，SMF网元根据该第二信息，可以确定是否存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流。在本示例中，SMF网元确定不存在已经根据与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则创建好的第一QoS流，进一步该SMF网元可以根据该第一PCC规则，创建第一QoS流。
在又一种示例中，第一PCC规则包括第二信息，该第二信息可用于指示该第一PCC规则与一个QoS流绑定，该一个QoS流不再与其它PCC规则绑定，在此情况下，SMF网元响应于该第二信息，根据该第一PCC规则，创建第一QoS流。
本申请实施例中创建第一QoS流，可理解为生成第一QoS流，或者可理解为配置第一QoS流的网络资源。
S305：SMF网元将第一PCC规则与第一QoS流绑定。
SMF网元将第一PCC规则与第一QoS流绑定，指该第一PCC规则对应的第一业务流由第一QoS 流承载。
其中，该第一QoS流可承载第一应用业务的一个业务流，即仅承载第一业务流，在此情况下，该第一QoS流仅与第一PCC规则绑定。例如，第一应用业务中不存在与第一业务流具有相同QoS需求的业务流。又例如，第一PCC规则包括的第二信息用于指示该第一PCC规则与一个QoS流绑定，该一个QoS流不再与其它PCC规则绑定。再例如，第一应用业务对应于一个业务流。
或者，该第一QoS流可承载第一业务流和与第一业务流具有相同QoS需求、且属于第一应用业务的业务流，在此情况下，该第一QoS流除了与第一PCC规则绑定之外还与第一应用业务对应的、且与该第一PCC规则具有相同绑定参数的PCC规则。例如，第一应用业务中存在与第一业务流具有相同QoS需求的业务流。又例如，第一PCC规则包括的第二信息，该第二信息可用于指示与第一PCC规则具有相同绑定参数、且包括该第一信息的PCC规则与该第一PCC规则绑定到同一个QoS流。
SMF网元将第一PCC规则与第一QoS流绑定之后，SMF网元可以向第一网元发送第一QoS流的信息。其中的第一网元为RAN，或者为UPF网元。考虑到SMF网元向RAN发送的第一QoS流的信息与SMF网元向UPF网元发送的第一QoS流的信息可以不同。为了便于区别，本申请实施例中，将SMF网元向RAN发送的第一QoS流的信息记为第一QoS流的信息1，以及将SMF网元向UPF网元发送的第一QoS流的信息记为第一QoS流的信息2。
本申请实施例涉及的QoS流的信息可包括但不限定于如下信息中的一项或多项：QoS流标识(QoS flow identity，QFI)、5QI、IP五元组信息、或三元组信息等。
S306：SMF网元向RAN发送第一QoS流的信息1；相应的，RAN接收来自SMF网元的第一QoS流的信息1。
SMF网元向RAN发送第一QoS流的信息1，以便RAN根据该第一QoS流的信息1创建用于承载第一业务流的QoS流。
本申请实施例中第一应用业务对应的多个PCC规则与多个QoS流绑定，其中的一个QoS流与该第一应用业务对应的多个PCC规则中的至少一个PCC规则绑定，即该第一应用业务的多个业务流由多个QoS流承载。
可选的，该第一QoS流的信息1可包括第三信息；或者，SMF网元可向RAN发送第三信息，如该第三信息与第一QoS流的信息1承载在一个消息中。该第三信息可用于关联该第一应用业务对应的多个PCC规则所绑定的多个QoS流之间的关联关系。其中，该第一应用业务对应的多个PCC规则所绑定的多个QoS流可替换为第一应用业务对应的多个QoS流，或者替换为用于承载第一应用业务的多个业务流的多个QoS流，或者可替换为第一应用业务的多个业务流对应的多个QoS流。该第三信息可用于关联该第一应用业务对应的多个PCC规则所绑定的多个QoS流之间的关联关系；可理解为该第三信息用于指示第一应用业务对应的多个QoS流之间的关联关系；或者也可以理解为该第三信息用于指示第一QoS流是第一应用业务对应的多个QoS流中的一个；或者还可以理解为使用第三信息指示该多个QoS流对应于同一个应用业务。例如，SMF网元向RAN发送的第一应用业务对应的多个QoS流的信息中的每个QoS流的信息包括该第三信息。另外，该第三信息可以是第四信息，或者也可以是不同于第四信息的信息，本申请实施例对此不作限定。其中，第一应用业务对应的多个QoS流之间的关联关系的确定请参考S304a的相关描述，此处不再赘述。
S307：SMF网元向UPF网元发送第一QoS流的信息2；相应的，UPF网元接收来自SMF网元的第一QoS流的信息2。
SMF网元向UPF网元发送第一QoS流的信息1，以便UPF网元根据该第一QoS流的信息1创建用于承载第一业务流的QoS流。
可选的，该第一QoS流的信息2可包括第三信息；或者，SMF网元可向UPF网元发送第三信息，如该第三信息与第一QoS流的信息2承载在一个消息中。
其中，图3中S306和S307的执行顺序仅为一种示例，本申请实施例对此不作限定。例如，SMF网元可以先向RAN发送第一QoS流的信息1，再向UPF网元发送第一QoS流的信息2；或者也可以先向UPF网元发送第一QoS流的信息2再向RAN发送第一QoS流的信息1；或者还可以同时向RAN发送第一QoS流的信息1和向UPF网元发送第一QoS流的信息2。
在图3所示的流程中，SMF网元将第一QoS流的信息1发送给RAN，将第一QoS流的信息2发 送给UPF。之后，在上行传输方式上，RAN可以根据该第一QoS流的信息1创建第一QoS流，以使得UE的第一业务流可使用该第一QoS流承载传输至AF网元。或者，在下行传输方向上，UPF网元可以根据第一QoS流的信息2创建第一QoS流的信息，以使得来自AF网元的第一业务流可使用该第一QoS流承载传输至UE。
下面结合图4分别从上行传输方向和下行传输介绍第一QoS流承载第一业务流的实现过程。
图4示出了本申请实施例提供的又一种通信方法的流程示意图。如图4所示，该方法还包括流程。其中，S401至404为上行传输方向，S405至S409为下行传输方向。
S401：SMF网元向RAN发送第一QoS流的信息1；相应的，RAN接收来自SMF网元的第一QoS流的信息1。该第一QoS流与第一业务流对应的第一PCC规则绑定。第一业务流是第一应用业务的多个业务流中的一个。
S402：RAN根据第一QoS流的信息1创建第一QoS流。
S403：UE将第一业务流映射到第一QoS流。
示例性的，UE可以根据第一业务流的业务流信息，将该第一业务流映射到第一QoS流。该第一业务流的业务流信息可以来自于RAN，或者来自于SMF网元，图4中未示出。例如，UE运行第一应用业务，产生第一业务流，并将第一业务流映射到第一QoS流。应理解的是，第一应用业务对应多个业务流，UE运行该第一应用业务，可产生多个业务流，以及将该多个业务流映射到该多个业务流对应的多个PCC规则所绑定的多个QoS流，该多个业务流包括第一业务流。
可选的，UE可以将该第一应用业务中与第一业务流具有相应QoS需求的业务流也映射到第一QoS流。例如，第一QoS流除了与第一PCC规则绑定之外还与第一应用业务对应的、与该第一PCC规则具有相同绑定参数的PCC规则。在此情况下，该第一QoS流除了用于承载第一业务之外还可以用于承载第一应用业务中与第一业务流具有相应QoS需求的业务流。
本申请实施例涉及的业务流信息可包括但不限定于如下信息中的至少一项：五元组、三元组、或数据包过滤规则等。
S404：UE使用第一QoS流承载第一业务流，向AF网元发送该第一业务流。
在S404中，UE通过第一QoS流向AF网元发送该第一业务流的具体实现过程可以为：UE通过第一QoS流向RAN发送第一业务流；RAN接收到第一业务流后，通过该第一QoS流向UPF网元发送第一业务流；UPF网元接收到第一业务流后，将该第一业务流发送给AF网元；AF网元接收该第一业务流。
本申请实施例中，该第一QoS流可承载该第一应用业务中的至少一个业务流，不承载不属于第一应用业务的业务流。
至此，上行传输完成。
S405：SMF网元向UPF网元发送第一QoS流的信息2；相应的，UPF网元接收来自SMF网元的第一QoS流的信息2。
S406：UPF网元根据第一QoS流的信息2创建第一QoS流。
S407：AF网元向UPF网元发送第一业务流；相应的，UPF网元接收来自AF网元的第一业务流。
例如，AF网元可响应于UE运行的第一应用业务，产生第一业务流，并向UPF网元送该第一业务流。应理解的是，第一应用业务对应多个业务流，AF网元可产生多个业务流，以及向UPF网元发送该多个业务流，该多个业务流包括第一业务流。AF网元可以逐一向UPF网元发送该多个业务流，或者也可以一起向UPF网元发送该多个业务流，本申请实施例不作限定。
S408：UPF网元将第一业务流映射到第一QoS。
示例性的，UPF可以根据第一业务流的业务流信息，将该第一业务流映射到第一QoS流。该第一业务流的业务流信息可以来自于SMF网元，图4中未示出。应理解的是，若UPF网元接收到来自AF网元的该第一应用业务的多个业务流，UPF网元可将该多个业务流映射到该多个业务流对应的PCC规则所绑定的QoS流，该多个业务流包括第一业务流。
可选的，UPF网元可以将该第一应用业务中与第一业务流具有相应QoS需求的业务流也映射到第一QoS流。例如，第一QoS流除了与第一PCC规则绑定之外还与第一应用业务对应的、与该第一PCC规则具有相同绑定参数的PCC规则。在此情况下，该第一QoS流除了用于承载第一业务之外还可以用于承载第一应用业务中与第一业务流具有相应QoS需求的业务流。
S409：UPF网元使用第一QoS流承载第一业务流，向UE发送该第一业务流。
在S409中，UPF网元通过第一QoS流向UE发送该第一业务流的具体实现过程可以为：UPF网元通过第一QoS流向RAN发送第一业务流；RAN接收到第一业务流后，通过该第一QoS流向UE发送第一业务流；UE接收第一业务流。
其中，该第一QoS流还可以承载该第一应用业务的多个业务流中与第一业务流具有相应QoS需求的业务流，但不承载不属于第一应用业务的业务流。
至此，下行传输完成。
通过图3和图4的流程，可实现一个QoS流承载一个应用业务的一个或多个业务流，不承载其它应用业务的业务流。举例而言，假设应用业务1的三个业务流分别记为业务流1、业务流2、和业务流3，其中业务流1和业务流3的QoS需求相同，即业务流1对应的PCC规则和业务流3的PCC规则具有相同的绑定参数。在一种示例中，业务流1对应的PCC规则和业务流3的PCC规则与同一个QoS流(如记为QoS流1)绑定，业务流2对应的PCC规则与QoS流2绑定，这样QoS流1可承载业务流1和业务流3，QoS流2可承载业务流2，如图5A所示。在另一种示例中，业务流1对应的PCC规则与QoS流1绑定，业务流2对应的PCC规则与QoS流2绑定，业务流3对应的PCC规则与QoS流3绑定，这样QoS流1可承载业务流1，QoS流2可承载业务流2，QoS流3可承载业务流3，如图5B所示。
图4中RAN可以根据第一QoS流的信息1创建第一QoS流。在一种可能的实现方式中，RAN可以释放该第一QoS流，例如网络资源不足等原因。第一QoS流对应的第一业务流是第一应用业务的多个业务流中的一个，为了确保第一应用业务的业务流的正常运行，RAN可以对该第一应用业务的多个业务流进行协同管理，如图6所示。
图6示出了本申请实施例提供的又一种通信方法的流程示意图。如图6所示，该流程可包括如下内容。
S601：SMF网元向RAN发送第一QoS流的信息1；相应的，RAN接收该第一QoS流的信息1。
其中，第一QoS流与第一业务流对应的第一PCC规则绑定，用于承载第一业务流。第一业务流是第一应用业务的多个业务流中的一个。在本实施例中，第一QoS流的信息1包括第三信息。该第三信息可用于指示第一应用业务对应的多个QoS流之间的关联信息。第一应用业务对应的多个QoS流包括第一QoS流。应理解的是，该第一QoS流的信息1也可以不包括第三信息，如SMF网元向RAN发送该第三信息。有关第三信息的描述请参考S306的相关内容，此处不再赘述。
可选的，RAN可以根据第三信息，确定第一应用业务对应的多个QoS流间的关联关系，即该多个QoS流对应于同一个应用业务。进一步，RAN还可以维护或存储该第一应用业务对应的多个QoS流之间的关联关系，即维护或存储该第一应用业务对应的多个QoS流。
示例性的，RAN可采用表格形式维护同一个应用业务对应的至少一个QoS流，如表格中的每一行表示同一个应用业务对应的至少一个QoS流，或者表格中的每一列表示同一个应用业务对应的至少一个QoS流。应理解的是，本申请实施例对RAN维护同一个应用业务对应的至少一个QoS流的具体实现方式并不限定于此。表1中以表格的每一行表示同一个应用业务对应的至少一个QoS流为例。如表1所示，QoS流1、QoS流2和QoS流3对应于同一个应用业务；QoS流4和QoS流5对应于同一个应用业务；QoS流6对应一个应用业务。
表1
S602：在第一QoS流被创建时，RAN根据第三信息创建至少一个QoS流。
该至少一个QoS流是第一应用业务对应的多个QoS流中除了第一QoS流之外的QoS流。例如，RAN可根据第一QoS流的信息1创建第一QoS流，在此情况下，RAN可以根据第三信息创建至少一个QoS流。例如，RAN可以根据第一QoS流和第一应用业务对应的多个QoS流之间的关联关系，确定该至少一个QoS流，并创建该至少一个QoS流，这样能够为第一应用业务的多个业务流同时分配资 源或预留资源，确保能够同步发送或同步接收该第一应用业务的多个业务流。
S603：在第一QoS流被释放时，RAN根据第三信息释放至少一个QoS流。
该至少一个QoS流是第一应用业务对应的多个QoS流中除了第一QoS流之外的QoS流。例如，RAN因网络资源不足等原因释放第一QoS流，在此情况下，RAN可以根据第三信息释放至少一个QoS流。例如，RAN可以根据第一QoS流和第一应用业务对应的多个QoS流之间的关联关系，确定该至少一个QoS流，并释放该至少一个QoS流，这样能够释放该第一应用业务对应的多个QoS流的资源，确保能够同步中断该第一应用业务的多个业务流的传输。
S604：RAN向SMF网元发送第七消息；相应的，SMF网元接收来自RAN的第七消息。
S604为可选步骤，图6中以虚线表示。该第七消息可用于指示第一应用业务对应的多个QoS流被释放。该第七消息可理解为一个消息，也可以理解为多个消息。例如，该第七消息为一个消息，该一个消息可用于指示第一应用业务对应的所有QoS流被释放。又例如，该第七消息为多个消息，其中的一个消息用于指示第一应用业务对应的多个QoS流中的一个QoS流被释放，该多个消息与第一应用业务的对应的多个QoS流一一对应。
在图6所示的流程中，RAN可根据第一应用业务对应的多个QoS流之间的关联关系，对该第一应用业务对应的多个QoS流进行协同管理，由于该多个QoS流中的每个QoS流中所承载的业务流属于第一应用业务，未承载其它应用业务的业务流，因此在协同管理过程中不会影响其它应用业务的业务流的正常传输。
在上述图3、图4、图5A、图5B、以及图6所示的流程中，不同应用业务的业务流映射到不同的QoS流，一个QoS流承载一个业务流或承载同一个应用业务的多个业务流，这样在以QoS为粒度对一个应用业务的多个业务流进行协同管理时不会影响其它应用业务的业务流的正常传输。在另一种可能的实现方式中，SMF网元能够以业务流为粒度对第一应用业务的多个业务流进行协同管理，也不会影响其它应用业务的业务流的正常传输。下面结合图7至图8对该实现方式进行介绍。
图7示出了本申请实施例提供的再一种通信方法的流程示意图。如图7所示，该流程可包括如下内容。
其中，S701、S702、S703与图3中的S301、S302、S303实质相同，不同之处在于：
S704：SMF网元维护或存储第一应用业务的多个业务流之间的关联关系。图7中以SMF网元维护第一应用业务的多个业务流之间的关联关系为例。
示例性的，SMF网元可以确定该第一应用业务的多个业务流之间的关联关系，以及维护或存储该第一应用业务的多个业务流之间的关联关系。例如，SMF网元可接收来自PCF网元的第一应用业务对应的多个PCC规则，根据该多个PCC规则中的每个PCC规则皆包括第一信息，确定该多个PCC规则对应的多个业务流属于同一个应用业务，并维护或存储该多个业务流属于同一个应用业务的关联关系。
示例性的，SMF网元可采用表格形式维护同一个应用业务的业务流，如表格中的每一行表示同一个应用业务的至少一个业务流，或者表格中的每一列表示同一个应用业务的至少一个业务流。应理解的是，本申请实施例对SMF网元维护同一个应用业务的业务流的具体实现方式并不限定于此。表2中以表格的每一行表示同一个应用业务的至少一个业务流为例。如表2所示，业务流1、业务流2和业务流3属于同一个应用业务；业务流4和业务流5属于同一个应用业务；业务流6属于一个应用业务。
表2
可选的，该SMF网元还可以维护第一应用业务对应的多个PCC规则之间的关联关系。可选的，该SMF网元还可以维护第一应用业务对应的多个QoS流之间的关联关系。具体实现过程，请参考前述S304a所示的相关内容，此处不再赘述。
S705：SMF网元将第一PCC规则与第二QoS流绑定。
在本实施例中，SMF网元可通过如下两种方式将第一PCC规则与第二QoS流绑定。
方式一：SMF网元将第一PCC规则与第二QoS流绑定，该第二QoS流不与其它应用业务对应的PCC规则绑定。具体实现方式请参考图3中S304a、S304b以及S305所示的内容，此处不再赘述。在 此情况下，该第二QoS流可以是上述实施例中的第一QoS流，即图7中的第二QoS流可替换为第一QoS流。例如，该第二QoS流可以为图5A所示的QoS流1、或QoS流2，或者为图5B所示的QoS流1、或QoS流2。
方式二：SMF网元将第一PCC规则与第二QoS流绑定，其它业务流对应的PCC规则可绑定到该第二QoS流。该其它业务流与第一业务流可以属于同一个应用业务，也可以属于不同应用业务。该其它业务流与第一业务流具有相同的QoS需求，即该其它业务流对应的PCC规则与第一PCC规则具有相同的绑定参数。例如，该第二QoS流除了与第一PCC规则绑定之外，还可以与不包括第一信息、且与该第一PCC规则具有相同绑定参数的PCC规则绑定。在此情况下，该第二QoS流中除了承载第一业务流之外还可以承载不属于第一应用业务的业务流。例如，该第二QoS流可以为图2所示的QoS流1、或QoS流2。
S706：SMF网元向RAN发送第二QoS流的信息1；相应的，RAN接收第二QoS流的信息1。
S707：RAN释放第二QoS流。例如，RAN因网络资源不足等原因释放第二QoS流。
S708：RAN向SMF网元发送第五消息；相应的，SMF网元接收来自RAN的第五消息。
该第五消息可用于指示或通知该第二QoS流被释放。例如，该第五消息可以包括第二QoS流的QFI。
S709：SMF网元确定第一应用业务的多个业务流中未被释放的业务流。
例如，SMF网元根据第一QoS流对应的第一应用业务的业务流和第一应用业务的多个业务流之间的关联关系，确定第一应用业务的多个业务流中未被释放的业务流。该第一应用业务的多个业务流中未被释放的业务流是第一应用业务的多个业务流中除了第一QoS流所承载的第一应用业务的业务流之外的业务流。其中，该第一QoS流可承载第一应用业务的一个业务流(即第一业务流)；或承载第一应用业务的多个业务流，该多个业务流包括第一业务流。可选的，该第二QoS流还可以承载其它应用业务的业务流。
S710：SMF网元从至少一个QoS流中释放第一应用业务的多个业务流中未被释放的业务流。
该至少一个QoS流是第一应用业务对应的多个QoS流中除了第二QoS流之外的QoS流。
作为一个示例，假设第二QoS流是图2所示的QoS流1，第一应用业务是图2所示的应用业务1，第一业务流是图2所示的业务流1，RAN释放QoS流1，该QoS流1所承载的业务流1、业务流2和业务流4终止传输，并向SMF网元发送QoS流1被释放的通知消息；SMF网元响应于该通知消息，根据本地维护的应用业务1的多个业务流之间的关联关系，确定该应用业务1的多个业务流未被释放的业务流是业务流3，并从QoS流2中释放该业务流3，如图8所示。
本申请实施例中从QoS流中释放业务流，可以理解为释放或删除该业务流的网络资源。
作为另一个示例，假设第二QoS流是图5A所示的QoS流1，第一应用业务是图5A所示的应用业务1，第一业务流是图5A所示的业务流1，RAN释放QoS流1，该QoS流1所承载的业务流1和业务流3终止传输，并向SMF网元发送QoS流1被释放的通知消息；SMF网元响应于该通知消息，根据本地维护的应用业务1的多个业务流之间的关联关系，确定该应用业务1的多个业务流未被释放的业务流是业务流2，并从QoS流2中释放该业务流2。由于该QoS流2承载一个业务流，SMF网元从QoS流2中释放该业务流2，也可以理解为SMF网元释放QoS流2。
作为再一个示例，假设第二QoS流是图5B所示的QoS流1，第一应用业务是图5B所示的应用业务1，第一业务流是图5B所示的业务流1，RAN释放QoS流1，该QoS流1所承载的业务流1终止传输，并向SMF网元发送QoS流1被释放的通知消息；SMF网元响应于该通知消息，根据本地维护的应用业务1的多个业务流之间的关联关系，确定该应用业务1的多个业务流未被释放的业务流是业务流2和业务流3，并从QoS流2中释放该业务流2以及从QoS流3中释放该业务流3。
S711：SMF网元向PCF网元发送第二消息；相应的，PCF网元接收来自SMF网元的第二消息。
第二消息可用于请求去激活第一应用业务对应的多个PCC规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有PCC规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个PCC规则中的一个PCC规则，该多个消息与第一应用业务对应的多个PCC规则一一对应。可选的，SMF网元可去激活第一应用业务的多个PCC规则。
以第一应用业务对应三个业务流，该三个业务流分别记为业务流1、业务流2和业务流3为例，SMF网元可以将指示信息1、指示信息2和指示信息3携带在一个消息中发送给PCF网元，该指示信息1 用于请求去激活业务流1对应的PCC规则，该指示信息2用于请求去激活业务流2对应的PCC规则，该指示信息3用于在请求去激活业务流3对应的PCC规则。或者，SMF网元释放业务流1，向PCF网元发送用于请求去激活业务流1对应的PCC规则的消息；SMF网元释放业务流2，向PCF网元发送用于请求去激活业务流2对应的PCC规则的消息；SMF网元释放业务流3，向PCF网元发送用于请求去激活业务流3对应的PCC规则的消息。
本申请实施例中去激活PCC规则，可以理解为释放该PCC规则，或者理解为释放该PCC规则对应的资源，或者理解为删除该PCC规则。
S712：PCF网元根据第二消息，去激活第一应用业务对应的多个PCC规则。
如果第二消息为多个消息，在S712中，PCF网元可响应于该多个消息，逐一去激活该第一应用业务对应的多个PCC规则。
需要说明的是，图7中第一应用业务对应的PCC规则可以与其它应用业务的PCC规则绑定，也可以不与其它应用业务的PCC规则绑定。在第一应用业务对应的PCC规则不与其它应用业务的PCC规则绑定的情况下，图7中的第二QoS流可替换到第一QoS流。相应的，S708中，RAN可以向SMF网元发送第一消息，该第一消息用于指示第一QoS流被释放。由于第一应用业务对应的PCC规则不与其它应用业务的PCC规则绑定，在S710中SMF网元从至少一个QoS流中释放第一应用业务的多个业务流中未被释放的业务流，可替换为SMF网元释放该至少一个QoS流。
在图7所示的流程，SMF网元维护第一应用业务的多个业务流之间的关联关系，基于该关联关系确定第一应用业务的多个业务流中未被释放的业务流。在另一种可能的实现方式中，PCF网元维护第一应用业务的多个业务流之间的关联关系，基于该关联关系确定第一应用业务的多个业务流中未被释放的业务流，如图9所示。
图9示出了本申请实施例提供的再一种通信方法的流程示意图。在本实施例中，第一应用业务对应的多个PCC规则的关联关系由PCF网元维护。
其中，S901、S902、S904、S905、S906至S908分别与图7中的S701、S702、S703、S705、S706至S708实质相同，不同之处在于：
S903：PCF网元维护或存储第一应用业务对应的多个PCC规则之间的关联关系。图9中以PCF网元维护第一应用业务对应的多个PCC规则之间的关联关系为例。例如，PCF网元可根据第一信息，确定该第一应用业务对应的多个PCC规则之间的关联关系，以及维护或存储该第一应用业务对应的多个PCC规则之间的关联关系。可选的，该PCF网元还可以维护或存储第一应用业务的多个业务流之间的关联关系。
S909：SMF网元向PCF网元发送第六消息；相应的，PCF网元接收来自SMF网元的第六消息。
该第六消息可用于请求去激活第二QoS流所绑定的PCC规则。例如，SMF网元在接收到来自RAN的第六消息后，响应于第二QoS流被释放，向PCF网元发送第六消息，以请求去激活该第二QoS流所绑定的PCC规则。该第二QoS流所绑定的PCC规则包括第一PCC规则。可选的，该第二QoS流所绑定的PCC规则中还可以包括其它业务流对应的PCC规则，该其它业务流与第一业务流可以属于同一个应用业务流，也可以属于不同的应用业务。其中，该第六消息可包括第二QoS流所绑定的PCC规则的标识信息。
S910：PCF网元确定第一应用业务对应的多个PCC规则。
例如，PCF网元可根据第二QoS流所绑定的、且包括第一信息的PCC规则和第一应用业务对应的多个PCC规则之间的对应关系，确定该第一应用业务对应的多个PCC规则。
又例如，若PCF网元维护或存储第一应用业务的多个业务流之间的关联关系，PCF网元可根据第二QoS流所绑定的、且包括第一信息的PCC规则对应的业务流和第一应用业务对应的多个业务流之间的关联关系，确定该第一应用业务的多个业务流中未被释放的业务流，以及确定该第一应用业务对应的多个PCC规则。例如，PCF网元根据第一应用业务的多个业务流，确定该第一应用业务对应的多个PCC规则，该第一应用业务的多个业务流包括第二QoS流所绑定的、且包括第一信息的PCC规则对应的业务流和确定出的该第一应用业务的多个业务流中未被释放的业务流。再例如，PCF网元可根据第二QoS流所绑定、且包括第一信息的PCC规则和第四信息，确定该第一应用业务对应的多个PCC规则。
S911：PCF网元去激活第一应用业务对应的多个PCC规则。
示例性的，PCF网元可以逐一去激活该第一应用业务对应的多个PCC规则，但本申请实施例并不 限定于此。
S912：PCF网元向SMF网元发送第四消息；相应的，SMF网元接收来自PCF网元的第四消息。
第四消息可用于指示去激活第一应用业务对应的多个PCC规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。图9中以第四消息指示去激活第一应用业务对应的多个PCC规则为例。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有PCC规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个PCC规则中的一个PCC规则，该多个消息与第一应用业务对应多个PCC规则一一对应。
以第一应用业务对应三个业务流，该三个业务流分别记为业务流1、业务流2和业务流3为例，PCF网元可以将指示信息4、指示信息5和指示信息6携带在一个消息中发送给SMF网元，该指示信息4用于指示去激活业务流1对应的PCC规则，该指示信息5用于指示去激活业务流2对应的PCC规则，该指示信息6用于指示去激活业务流3对应的PCC规则。或者，PCF网元去激活业务流1对应的PCC规则，向SMF网元发送用于指示去激活业务流1对应的PCC规则的消息；PCF网元去激活业务流2对应的PCC规则，向SMF网元发送用于指示去激活业务流2对应的PCC规则的消息；PCF网元去激活业务流3对应的PCC规则，向SMF网元发送用于指示去激活业务流3对应的PCC规则的消息。
S913：SMF网元根据第四消息，从至少一个QoS流中释放第一应用业务的多个业务流中未被释放的业务流。
该至少一个QoS流是第一应用业务对应的多个QoS流中除了第二QoS流之外的QoS流。例如，SMF网元接收到第四消息后，响应于该第四消息，从至少一个QoS流中释放第一应用业务的多个业务流中未被释放的业务流。例如，SMF网元根据第四消息，确定第一应用业务的多个业务流，根据第一QoS流对应的第一应用业务的业务流和该第一应用业务的多个业务流，从至少一个QoS流中释放第一应用业务的多个业务流中未被释放的业务流。例如，SMF网元可根据第四消息，确定第一应用业务对应的多个QoS流，以及确定该至少一个QoS流。可选的，SMF网元可以去激活第一应用业务对应的多个PCC规则，图9中未示出。
需要说明的是，图9中第一应用业务对应的PCC规则可以与其它应用业务的PCC规则绑定，也可以不与其它应用业务的PCC规则绑定。在第一应用业务对应的PCC规则不与其它应用业务的PCC规则绑定的情况下，图9中的第二QoS流可替换到第一QoS流。相应的，S909中，SMF网元可以向PCF网元发送第三消息，该第三消息用于请求去激活第一QoS流所绑定的PCC规则。
在图7至图9所示的实施例中，SMF网元能够以业务流为粒实现对一个应用业务的多个业务流的协同管理，由于SMF网元是以业务流为粒度进行释放的，相较于释放整个QoS流而言，能够避免影响同一个QoS流所承载的其它应用业务的业务流的正常传输。
上述本申请提供的实施例中，分别从SMF网元、PCF网元以及RAN之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，SMF网元、PCF网元或RAN可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。
下面结合附图介绍本申请实施例中用来实现上述方法的通信装置。因此，上文中的内容均可以用于后续实施例中，重复的内容不再赘述。
图10示出了一种通信装置1000的结构示意图。该通信装置1000可以对应实现上述各个方法实施例中由SMF网元、PCF网元或RAN实现的功能或者步骤。该通信装置可以包括处理单元1001和收发单元1002。可选地，通信装置1000还可以包括存储单元1003(图10中以虚线表示)，该存储单元1003可以用于存储指令(代码或者程序)和/或数据。处理单元1001和收发单元1002可以与该存储单元1003耦合，例如，处理单元1001可以读取存储单元1003中的指令(代码或者程序)和/或数据，以实现相应的方法。上述各个单元可以独立设置，也可以部分或者全部集成。例如收发单元1002可包括发送单元和接收单元。
作为一个示例，通信装置1000可实现上述各个方法实施例中由SMF网元实现的功能或步骤。
其中，收发单元1002，用于接收来自策略控制功能网元的第一策略与计费控制规则，该第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规 则。
处理单元1001，用于将第一策略与计费控制规则与第一服务质量流绑定，该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定。
收发单元1002，还用于向第一网元发送第一服务质量流的信息。
或者，收发单元1002，用于接收来自策略控制功能网元的第一策略与计费控制规则，该第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的多个策略与计费控制规则。
处理单元1001，用于将第一策略与计费控制规则与第一服务质量流绑定；以及确定该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定。
收发单元1002，还用于向第一网元发送第一服务质量流的信息。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括第一信息。
在一种可能的实现方式中，不包括第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
在一种可能的实现方式中，处理单元1001，还用于确定该第一服务质量流不与不包括第一信息的策略与计费控制规则绑定。
在一种可能的实现方式中，处理单元1001，在将第一策略与计费控制规则与第一服务质量流绑定之前，还用于创建该第一服务质量流；或者，该第一信息用于关联第一应用业务对应的多个策略与计费控制规则，处理单元1001，在将第一策略与计费控制规则与第一服务质量流绑定之前，还用于确定已经根据与该第一策略与计费控制规则具有相同绑定参数、且包括该第一信息的策略与计费控制规则创建的第一服务质量流。
在一种可能的实现方式中，该第一策略与计费控制规则还可以包括第二信息；
该第二信息可用于指示第一策略与计费控制规则与一个服务质量流绑定，该一个服务质量流不与包括第一信息、且与该第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；
或者，该第二信息可用于指示第一策略与计费控制规则与包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。其中，该包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流，可理解为与该第一策略与计费控制规则对应的业务流具有相同服务质量需求、且属于第一应用业务的业务流对应的策略与计费控制规则。
在一种可能的实现方式中，处理单元1001，还用于根据第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，存储单元1003，用于维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，第一应用业务对应的多个测量与计费控制规则与多个服务质量流绑定，第一网元为接入网网元；收发单元1002，还用于接收来自接入网网元的第一消息，第一消息用于指示第一服务质量流被释放；以及，处理单元1001，还用于从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，至少一个服务质量流是该多个服务质量流中除了第一服务质量流之外的服务质量流。
在一种可能的实现方式中，处理单元1001可通过如下方式从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流：
确定第一应用业务的多个业务流之间的关联关系，根据第一服务质量流对应的业务流和该第一应用业务的多个业务流之间的关联关系，确定该确定第一应用业务的多个业务流中未被释放的业务流，以及根据该第一应用业务的多个业务流中未被释放的业务流，从至少一个服务质量流中释放该第一应用业务的多个业务流中未被释放的业务流。
可选的，控制收发单元1002向策略控制功能网元发送第二消息，该第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则。
或者，控制收发单元1002向策略控制功能网元发送第三消息，该第三消息用于请求去激活第一服务质量流绑定的策略与计费控制规则；接收来自策略控制功能网元的第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息用于请求释放该第一应用业务的多个业务流中未被释放的业务流；根据该第四消息，确定第一应用业务的多个业务流；以及，从至少一个服 务质量流中释放第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
在一种可能的实现方式中，第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定，第一服务质量流的信息中可以包括第三信息；或者，收发单元1002还用于向第一网元发送第三信息；其中，该第三信息用于指示关联该第一应用业务对应的多个服务质量流。
作为又一个示例，通信装置1000可实现上述各个方法实施例中由PCF网元实现的功能或步骤。
其中，收发单元1002，用于接收来自应用功能网元的请求消息，请求消息用于请求为第一业务流提供质量服务，其中，请求消息包括第四信息，第一信息用于关联第一应用业务的多个业务流，第一业务流是该第一应用业务的多个业务流中的一个。
处理单元1001，用于根据请求消息，生成第一策略与计费控制规则，其中，第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则。
该收发单元1002，还用于向会话管理功能网元发送第一策略与计费控制规则。
在一种可能的实现方式中，包括该第一信息的策略与计费控制规则不与不包括第一信息的策略与计费控制规则绑定。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括该第一信息。
在一种可能的实现方式中，不包括第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
在一种可能的实现方式中，处理单元1001，还用于根据该第四信息，确定该第一信息。
在一种可能的实现方式中，第一策略与计费控制规则还可以包括第二信息；
该第二信息可用于指示第一策略与计费控制规则与一个服务质量流绑定，该一个服务质量流不与包括第一信息、且与该第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；
或者，该第二信息可用于指示第一策略与计费控制规则与包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。其中，该包括第一信息、且与该第一测量与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流，可理解为与该第一策略与计费控制规则对应的业务流具有相同服务质量需求、且属于第一应用业务的业务流对应的策略与计费控制规则。
在一种可能的实现方式中，处理单元1001，还用于根据第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，存储单元1003，用于维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，收发单元1002，还用于接收来自会话管理功能网元的第三消息，第三消息用于请求去激活第一服务质量流绑定的策略与计费控制规则；处理单元1001，还用于根据第一服务质量流绑定包括该第一信息的策略与计费控制规则和第四信息，确定第一应用业务对应的多个策略与计费控制规则；以及，去激活第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，收发单元1002，还用于向会话管理功能网元发送第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
在一种可能的实现方式中，收发单元1002，还用于接收来自会话管理功能网元的第二消息，第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则；处理单元1001，还用于根据第二消息，去激活第一应用业务对应的多个策略与计费控制规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有 策略与计费控制规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
作为又一个示例，通信装置1000可实现上述各个方法实施例中由RAN实现的功能或步骤。
其中，收发单元1002，用于接收来自会话管理功能网元的第一服务质量流的信息，第一服务质量流的信息中包括第三信息，第三信息用于关联第一应用业务对应的多个服务质量流。
处理单元1001，用于在所述第一服务质量流被创建时，根据所述第三信息创建至少一个服务质量流；或者在第一服务质量流被释放时，根据第三信息释放至少一个服务质量流；其中，该至少一个服务质量流是该第一应用业务对应的多个服务质量流中除了该第一服务质量流的服务质量流。
在一种可能的实现方式中，处理单元1001，还用于根据第一服务质量流和第三信息，确定该至少一个服务质量流。
作为再一个示例，通信装置1000可实现上述各个方法实施例中由SMF网元实现的功能或步骤。
其中，收发单元1002，用于接收来自接入网网元的第五消息，第五消息用于指示第二服务质量流被释放。
处理单元1001，用于从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，该至少一个服务质量流是所述第一应用业务对应的多个服务质量流中除了第二服务质量流之外的服务质量流。
在一种可能的实现方式中，收发单元1002，还用于在接收来自接入网网元的第五消息之前，接收来自策略控制功能网元的第一策略与计费控制规则，第一策略与计费控制规则包括第一信息，该第一信息用于关联第一应用业务对应的多个策略与计费控制规则；处理单元1001，还用于将第一策略与计费控制规则与第二服务质量流绑定；收发单元1002，还用于向第一网元发送第二服务质量流的信息。
在一种可能的实现方式中，该第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
在一种可能的实现方式中，不包括该第一信息的策略与计费控制规则对应的应用业务与该第一应用业务是不同的应用业务。
在一种可能的实现方式中，收发单元1002，还用于根据该第一信息，确定第一应用业务的多个业务流之间的关联关系。可选的，存储单元1003，用于维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，处理单元1001，还用于确定第一应用业务的多个业务流之间的关联关系，以及根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。
在一种可能的实现方式中，收发单元1002，还用于向策略控制功能网元发送第二消息，该第二消息用于请求去激活第一应用业务对应的多个策略与计费控制规则。该第二消息可理解为一个消息，也可以理解为多个消息。例如，该第二消息为一个消息，该一个消息可用于请求去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第二消息为多个消息，其中的一个消息用于请求去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
在一种可能的实现方式中，收发单元1002，还用于向策略控制功能网元发送第六消息，第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则；以及，接收来自策略控制功能网元的第四消息，该第四消息用于指示去激活该第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
可选的，处理单元1001，还用于根据第四消息，确定第一应用业务的业务流，以及根据该第二服 务质量流对应的业务流和该第一应用业务的多个业务流，确定该第一应用业务的多个业务流中未被释放的业务流。
作为再一个示例，通信装置1000可实现上述各个方法实施例中由PCF网元实现的功能或步骤。
其中，收发单元1002，用于接收来自会话管理功能网元的第六消息，第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则，该第二服务质量流对应的第一业务流是第一应用业务的多个业务流中的一个。
处理单元1001，用于确定该第一应用业务对应的多个策略与计费控制规则；以及，去激活该第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，收发单元1002，还用于接收来自应用功能网元的请求消息，该请求消息用于请求为第一业务流提供质量服务，其中，请求消息包括第四信息，第四信息用于关联第一应用业务的多个业务流；处理单元1001，还用于根据请求消息，生成第一策略与计费控制规则，其中，第一策略与计费控制规则包括第一信息，所述第一信息用于关联该第一应用业务对应的多个策略与计费控制规则；收发单元1002，还用于向会话管理功能网元发送第一策略与计费控制规则。
在一种可能的实现方式中，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
在一种可能的实现方式中，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
在一种可能的实现方式中，处理单元1001，还用于根据第四信息，确定所述第一信息。
在一种可能的实现方式中，处理单元1001，还用于确定第一应用业务的多个业务流之间的关联关系。可选的，存储单元1003，用于维护或存储该第一应用业务的多个业务流之间的关联关系。
在一种可能的实现方式中，处理单元1001可通过如下方式确定该第一应用业务对应的多个策略与计费控制规则：根据第四信息和第二服务质量流所绑定的PCC规则，确定第一应用业务对应的多个策略与计费控制规则。
在一种可能的实现方式中，收发单元1002，还用于向会话管理功能网元发送第四消息，第四消息用于指示去激活第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息用于指示去激活该第一应用业务对应的多个策略与计费控制规则，或者该第四消息可用于请求释放该第一应用业务的多个业务流中未被释放的业务流。该第四消息可理解为一个消息，也可以理解为多个消息。例如，该第四消息为一个消息，该一个消息可用于指示去激活第一应用业务对应的所有策略与计费控制规则。又例如，该第四消息为多个消息，其中的一个消息用于指示去激活第一应用业务对应的多个策略与计费控制规则中的一个，该多个消息与第一应用业务对应的多个策略与计费控制规则一一对应。
有关上述处理单元1001、收发单元1002和存储单元1003更详细的描述可以直接参考图3、图4、图6、图7、以及图9中任一项所示的方法实施例中相关描述直接得到，这里不加赘述。
如图11所示为本申请实施例提供的通信装置1100，其中，通信装置1100可以是SMF网元，能够实现本申请实施例提供的方法中SMF网元的功能，或者，通信装置1100可以是PCF网元，能够实现本申请实施例提供的方法中PCF网元的功能，或者，通信装置1100可以是RAN，能够实现本申请实施例提供的方法中RAN的功能；或者，通信装置1100也可以是能够支持SMF网元实现本申请实施例提供的方法中对应的功能的装置，或者能够支持PCF网元实现本申请实施例提供的方法中对应的功能的装置，或者能够支持RAN实现本申请实施例提供的方法中对应的功能的装置。其中，该通信装置1100可以为芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其它分立器件。
通信装置1100包括至少一个处理器1120，用于实现或用于支持通信装置1100实现本申请实施例提供的方法中SMF网元、PCF网元或RAN的功能。具体参见方法示例中的详细描述，此处不做赘述。
可选地，通信装置1100还可以包括至少一个存储器1130，用于存储程序指令和/或数据。存储器1130和处理器1120耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1120可能和存储器1130 协同操作。处理器1120可能执行存储器1130中存储的程序指令和/或数据，以使得通信装置1100实现相应的方法。所述至少一个存储器中的至少一个可以包括于处理器中。该存储器1130可以是独立存在，例如片外存储器，通过通信总线(图11中以粗线1140表示)与处理器1120相连接。该存储器1130也可以和处理器1120集成在一起。
可选地，通信装置1100还可以包括通信接口1110，用于通过传输介质和其它设备进行通信，从而用于通信装置1100中的装置可以和其它设备进行通信。示例性的，当该通信装置为SMF网元时，该其它设备为PCF网元或RAN等。处理器1120可以利用通信接口1110收发数据。通信接口1110具体可以是收发器。
在硬件实现上，上述收发单元1002可以为收发器，收发器集成在通信装置1100中构成通信接口1110。
本申请实施例中不限定上述通信接口1110、处理器1120以及存储器1130之间的具体连接介质。本申请实施例在图11中以存储器1130、处理器1120以及通信接口1110之间通过通信总线1140连接，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述通信总线1140可以分为地址总线、数据总线、控制总线等。为便于表示，图11中仅用一条粗线表示，但并不表示仅有一根通信总线或一种类型的通信总线。
在本申请实施例中，处理器1120可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器1130可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
本申请实施例还提供一种通信系统，具体的，通信系统包括SMF网元、PCF网元或RAN中的至少一项。
本申请实施例中还提供一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行上述各个实施例中的方法。
本申请实施例中还提供一种计算机程序产品，包括指令，当其在计算机上运行时，使得计算机执行上述各个实施例中的方法。
本申请实施例提供了一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述方法中SMF网元、PCF网元或RAN的功能。该芯片系统可以由芯片构成，也可以包含芯片和其它分立器件。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或 者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请实施例的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请实施例揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应所述以权利要求的保护范围为准。

Claims (88)

  1. 一种通信方法，其特征在于，应用于会话管理功能网元，所述方法包括：
    接收来自策略控制功能网元的第一策略与计费控制规则，所述第一策略与计费控制规则包括第一信息，其中，所述第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；
    将所述第一策略与计费控制规则与所述第一服务质量流绑定，其中，所述第一服务质量流不与不包括所述第一信息的策略与计费控制规则绑定；
    向第一网元发送所述第一服务质量流的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    确定所述第一服务质量流不与不包括所述第一信息的策略与计费控制规则绑定。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，在将所述第一策略与计费控制规则与所述第一服务质量流绑定之前，所述方法还包括：
    根据所述第一策略与计费控制规则，创建所述第一服务质量流。
  6. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一信息用于关联第一应用业务对应的多个策略与计费控制规则；
    在将所述第一策略与计费控制规则与所述第一服务质量流绑定之前，所述方法还包括：
    确定已经根据与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则创建的所述第一服务质量流。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述第一策略与计费控制规则还包括第二信息；
    所述第二信息用于指示所述第一策略与计费控制规则与一个服务质量流绑定，所述一个服务质量流不与包括第一信息、且与所述第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；或者，
    所述第二信息用于指示所述第一策略与计费控制规则与包括所述第一信息、且与所述第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定，所述第一网元为接入网网元，所述方法还包括：
    接收来自所述接入网网元的第一消息，所述第一消息用于指示所述第一服务质量流被释放；
    从至少一个服务质量流中释放所述第一应用业务的多个业务流中未被释放的业务流，其中，所述至少一个服务质量流是所述多个服务质量流中除了所述第一服务质量流之外的服务质量流。
  9. 根据权利要求8所述的方法，其特征在于，在所述从至少一个服务质量流中释放所述第一应用业务的多个业务流中未被释放的业务流之前，所述方法还包括：
    确定所述第一应用业务的多个业务流之间的关联关系；
    根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    向所述策略控制功能网元发送第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则。
  11. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    向所述策略控制功能网元发送第三消息，所述第三消息用于请求去激活所述第一服务质量流绑定的策略与计费控制规则；
    接收来自所述策略控制功能网元的第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  12. 根据权利要求11所述的方法，其特征在于，在所述从至少一个服务质量流中释放所述第一应用 业务的多个业务流中未被释放的业务流之前，所述方法还包括：
    根据所述第四消息，确定所述第一应用业务的多个业务流；
    根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流，确定所述第一应用业务的多个业务流中未被释放的业务流。
  13. 根据权利要求1至12中任一项所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定；
    所述第一服务质量流的信息中包括第三信息；或者，
    向所述第一网元发送第三信息；
    其中，所述第三信息用于关联所述多个服务质量流。
  14. 一种通信方法，其特征在于，应用于策略控制功能网元，所述方法包括：
    接收来自应用功能网元的请求消息，所述请求消息用于请求为第一业务流提供质量服务，其中，所述请求消息包括第四信息，所述第四信息用于关联第一应用业务的多个业务流，所述第一业务流是所述第一应用业务的多个业务流中的一个；
    根据所述请求消息，生成第一策略与计费控制规则，其中，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的一个或多个策略与计费控制规则；
    向会话管理功能网元发送所述第一策略与计费控制规则。
  15. 根据权利要求14所述的方法，其特征在于，包括所述第一信息的策略与计费控制规则不与不包括所述第一信息的策略与计费控制规则绑定。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第四信息，确定所述第一信息。
  19. 根据权利要求14至18中任一项所述的方法，其特征在于，所述第一策略与计费控制规则还包括第二信息；
    所述第二信息用于指示所述第一策略与计费控制规则与一个服务质量流绑定，所述一个服务质量流不绑定与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则；或者，
    所述第二信息用于指示与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则与所述第一策略与计费控制规则绑定到同一个服务质量流。
  20. 根据权利要求14至19中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述会话管理功能网元的第三消息，所述第三消息用于请求去激活所述第一服务质量流绑定的策略与计费控制规则；
    根据所述第一服务质量流绑定包括所述第一信息的策略与计费控制规则和所述第四信息，确定所述第一应用业务对应的多个策略与计费控制规则；
    去激活所述第一应用业务对应的多个策略与计费控制规则。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    向所述会话管理功能网元发送第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  22. 根据权利要求14至19中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述会话管理功能网元的第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则；
    根据所述第二消息，去激活所述多个策略与计费控制规则。
  23. 一种通信方法，其特征在于，应用于接入网网元，所述方法包括：
    接收来自会话管理功能网元的第一服务质量流的信息，所述第一服务质量流的信息中包括第三信息，所述第三信息用于关联所述第一应用业务对应的多个服务质量流；
    在所述第一服务质量流被创建时，根据所述第三信息创建至少一个服务质量流；或者，在所述第一 服务质量流被释放时，根据所述第三信息释放至少一个服务质量流；其中，所述至少一个服务质量流是所述多个服务质量流中除了所述第一服务质量流之外的服务质量流。
  24. 根据权利要求23所述的方法，其特征在于，所述方法还包括：
    根据所述第三信息和所述第一服务质量流，确定所述至少一个服务质量流。
  25. 一种通信方法，其特征在于，应用于会话管理功能网元，所述方法包括：
    接收来自接入网网元的第五消息，所述第五消息用于指示第二服务质量流被释放；
    从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，所述至少一个服务质量流是所述第一应用业务对应的多个服务质量流中除了所述第二服务质量流之外的服务质量流。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    在接收来自接入网网元的第五消息之前，接收来自策略控制功能网元的第一策略与计费控制规则，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的多个策略与计费控制规则；
    将所述第一策略与计费控制规则与所述第二服务质量流绑定；
    向第一网元发送所述第二服务质量流的信息。
  27. 根据权利要求26所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  28. 根据权利要求26或27所述的方法，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  29. 根据权利要求26至28中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第一信息，确定所述第一应用业务的多个业务流之间的关联关系。
  30. 根据权利要求26至29中任一项所述的方法，其特征在于，所述方法还包括：
    确定所述第一应用业务的多个业务流之间的关联关系；
    根据所述第二服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。
  31. 根据权利要求26至30中任一项所述的方法，其特征在于，所述方法还包括：
    向所述策略控制功能网元发送第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则。
  32. 根据权利要求26至31中任一项所述的方法，其特征在于，所述方法还包括：
    向所述策略控制功能网元发送第六消息，所述第六消息用于请求去激活所述第二服务质量流绑定的策略与计费控制规则；
    接收来自所述策略控制功能网元的第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  33. 根据权利要求32所述的方法，其特征在于，所述方法还包括：
    根据所述第四消息，确定所述第一应用业务的业务流；
    根据所述第二服务质量流对应的业务流和所述第一应用业务的多个业务流，确定所述第一应用业务的多个业务流中未被释放的业务流。
  34. 一种通信方法，其特征在于，应用于策略控制功能网元，所述方法包括：
    接收来自会话管理功能网元的第六消息，所述第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则，所述第二服务质量流对应的第一业务流是第一应用业务的多个业务流中的一个；
    确定所述第一应用业务对应的多个策略与计费控制规则；
    去激活所述第一应用业务对应的多个策略与计费控制规则。
  35. 根据权利要求34所述的方法，其特征在于，所述方法还包括：
    接收来自应用功能网元的请求消息，所述请求消息用于请求为所述第一业务流提供质量服务，其中，所述请求消息包括第四信息，所述第四信息用于关联所述第一应用业务的多个业务流；
    根据所述请求消息，生成第一策略与计费控制规则，其中，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的多个策略与计费控制规则；
    向所述会话管理功能网元发送第一策略与计费控制规则。
  36. 根据权利要求35所述的方法，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  37. 根据权利要求35或36所述的方法，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  38. 根据权利要求35至37中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述第四信息，确定所述第一信息。
  39. 根据权利要求35至38中任一项所述的方法，其特征在于，所述方法还包括：
    确定所述第一应用业务的多个业务流之间的关联关系。
  40. 根据权利要求35至39中任一项所述的方法，其特征在于，所述确定所述第一应用业务对应的多个策略与计费控制规则，包括：
    根据所述第四信息和所述第二服务质量流所绑定的策略与计费控制规则，确定所述第一应用业务对应的多个策略与计费控制规则。
  41. 根据权利要求35至40中任一项所述的方法，其特征在于，所述方法还包括：
    向所述会话管理功能网元发送第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  42. 一种通信装置，其特征在于，所述装置包括处理单元和收发单元，其中：
    所述收发单元，用于接收来自策略控制功能网元的第一策略与计费控制规则，所述第一策略与计费控制规则包括第一信息，其中，所述第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；
    所述处理单元，用于将所述第一策略与计费控制规则与所述第一服务质量流绑定，其中，所述第一服务质量流不与不包括所述第一信息的策略与计费控制规则绑定；
    所述收发单元，还用于向第一网元发送所述第一服务质量流的信息。
  43. 根据权利要求42所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  44. 根据权利要求42或43所述的装置，其特征在于，所述不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  45. 根据权利要求42至44中任一项所述的装置，其特征在于，所述处理单元还用于：
    确定所述第一服务质量流不与不包括所述第一信息的策略与计费控制规则绑定。
  46. 根据权利要求42至45中任一项所述的装置，其特征在于，在将所述第一策略与计费控制规则与所述第一服务质量流绑定之前，所述处理单元还用于：
    根据所述第一策略与计费控制规则，创建所述第一服务质量流。
  47. 根据权利要求42至45中任一项所述的装置，其特征在于，所述第一信息用于关联第一应用业务对应的多个策略与计费控制规则；
    在将所述第一策略与计费控制规则与所述第一服务质量流绑定之前，所述处理单元还用于：
    确定已经根据与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则创建的所述第一服务质量流。
  48. 根据权利要求42至47中任一项所述的装置，其特征在于，所述第一策略与计费控制规则还包括第二信息；
    所述第二信息用于指示所述第一策略与计费控制规则与一个服务质量流绑定，所述一个服务质量流不与包括第一信息、且与所述第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定；或者，
    所述第二信息用于指示所述第一策略与计费控制规则与包括所述第一信息、且与所述第一策略与计费控制规则具有相同绑定参数的策略与计费控制规则绑定到同一个服务质量流。
  49. 根据权利要求42至48中任一项所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定，所述第一网元为接入网网元；
    所述收发单元还用于接收来自所述接入网网元的第一消息，所述第一消息用于指示所述第一服务质量流被释放；
    所述处理单元还用于从至少一个服务质量流中释放所述第一应用业务的多个业务流中未被释放的 业务流，其中，所述至少一个服务质量流是所述多个服务质量流中除了所述第一服务质量流之外的服务质量流。
  50. 根据权利要求49所述的装置，其特征在于，在所述从至少一个服务质量流中释放所述第一应用业务的多个业务流中未被释放的业务流之前，所述处理单元还用于：
    确定所述第一应用业务的多个业务流之间的关联关系；
    根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。
  51. 根据权利要求49或50所述的装置，其特征在于，所述收发单元还用于：
    向所述策略控制功能网元发送第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则。
  52. 根据权利要求49所述的装置，其特征在于，所述收发单元还用于：
    向所述策略控制功能网元发送第三消息，所述第三消息用于请求去激活所述第一服务质量流绑定的策略与计费控制规则；
    接收来自所述策略控制功能网元的第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  53. 根据权利要求52所述的装置，其特征在于，在所述从至少一个服务质量流中释放所述第一应用业务的多个业务流中未被释放的业务流之前，所述处理单元还用于：
    根据所述第四消息，确定所述第一应用业务的多个业务流；
    根据所述第一服务质量流对应的业务流和所述第一应用业务的多个业务流，确定所述第一应用业务的多个业务流中未被释放的业务流。
  54. 根据权利要求42至53中任一项所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则与多个服务质量流绑定；
    所述第一服务质量流的信息中包括第三信息；或者，
    所述收发单元还用于向所述第一网元发送第三信息；
    其中，所述第三信息用于关联所述多个服务质量流。
  55. 一种通信装置，其特征在于，所述装置包括处理单元和收发单元，其中：
    所述收发单元，用于接收来自应用功能网元的请求消息，所述请求消息用于请求为第一业务流提供质量服务，其中，所述请求消息包括第四信息，所述第四信息用于关联第一应用业务的多个业务流，所述第一业务流是所述第一应用业务的多个业务流中的一个；
    所述处理单元，用于根据所述请求消息，生成第一策略与计费控制规则，其中，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的一个或多个策略与计费控制规则；
    所述收发单元，还用于向会话管理功能网元发送所述第一策略与计费控制规则。
  56. 根据权利要求55所述的装置，其特征在于，包括所述第一信息的策略与计费控制规则不与不包括所述第一信息的策略与计费控制规则绑定。
  57. 根据权利要求55或56所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  58. 根据权利要求55至57中任一项所述的装置，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  59. 根据权利要求55至58中任一项所述的装置，其特征在于，所述处理单元还用于：
    根据所述第四信息，确定所述第一信息。
  60. 根据权利要求55至59中任一项所述的装置，其特征在于，所述第一策略与计费控制规则还包括第二信息；
    所述第二信息用于指示所述第一策略与计费控制规则与一个服务质量流绑定，所述一个服务质量流不绑定与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则；或者，
    所述第二信息用于指示与所述第一策略与计费控制规则具有相同绑定参数、且包括所述第一信息的策略与计费控制规则与所述第一策略与计费控制规则绑定到同一个服务质量流。
  61. 根据权利要求55至60中任一项所述的装置，其特征在于，
    所述收发单元，还用于接收来自所述会话管理功能网元的第三消息，所述第三消息用于请求去激活所述第一服务质量流绑定的策略与计费控制规则；
    所述处理单元，还用于根据所述第一服务质量流绑定包括所述第一信息的策略与计费控制规则和所述第四信息，确定所述第一应用业务对应的多个策略与计费控制规则；以及，去激活所述第一应用业务对应的多个策略与计费控制规则。
  62. 根据权利要求61所述的装置，其特征在于，所述收发单元还用于：
    向所述会话管理功能网元发送第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  63. 根据权利要求55至60中任一项所述的装置，其特征在于，
    所述收发单元，还用于接收来自所述会话管理功能网元的第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则；
    所述处理单元，还用于根据所述第二消息，去激活所述多个策略与计费控制规则。
  64. 一种通信装置，其特征在于，所述装置包括处理单元和收发单元，其中：
    所述收发单元，用于接收来自会话管理功能网元的第一服务质量流的信息，所述第一服务质量流的信息中包括第三信息，所述第三信息用于关联所述第一应用业务对应的多个服务质量流；
    所述处理单元，用于在所述第一服务质量流被创建时，根据所述第三信息创建至少一个服务质量流；或者，在所述第一服务质量流被释放时，根据所述第三信息释放至少一个服务质量流；其中，所述至少一个服务质量流是所述多个服务质量流中除了所述第一服务质量流之外的服务质量流。
  65. 根据权利要求64所述的装置，其特征在于，所述处理单元还用于：
    根据所述第三信息和所述第一服务质量流，确定所述至少一个服务质量流。
  66. 一种通信装置，其特征在于，所述装置包括处理单元和收发单元，其中：
    所述收发单元，用于接收来自接入网网元的第五消息，所述第五消息用于指示第二服务质量流被释放；
    所述处理单元，用于从至少一个服务质量流中释放第一应用业务的多个业务流中未被释放的业务流，其中，所述至少一个服务质量流是所述第一应用业务对应的多个服务质量流中除了所述第二服务质量流之外的服务质量流。
  67. 根据权利要求66所述的装置，其特征在于，
    在接收来自接入网网元的第五消息之前，所述收发单元还用于接收来自策略控制功能网元的第一策略与计费控制规则，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的多个策略与计费控制规则；
    所述处理单元还用于将所述第一策略与计费控制规则与所述第二服务质量流绑定；
    所述收发单元还用于向第一网元发送所述第二服务质量流的信息。
  68. 根据权利要求67所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  69. 根据权利要求67或68所述的装置，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  70. 根据权利要求67至69中任一项所述的装置，其特征在于，所述处理单元还用于：
    根据所述第一信息，确定所述第一应用业务的多个业务流之间的关联关系。
  71. 根据权利要求67至70中任一项所述的装置，其特征在于，所述处理单元还用于：
    确定所述第一应用业务的多个业务流之间的关联关系；
    根据所述第二服务质量流对应的业务流和所述第一应用业务的多个业务流之间的关联关系，确定所述第一应用业务的多个业务流中未被释放的业务流。
  72. 根据权利要求67至71中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述策略控制功能网元发送第二消息，所述第二消息用于请求去激活所述第一应用业务对应的多个策略与计费控制规则。
  73. 根据权利要求67至72中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述策略控制功能网元发送第六消息，所述第六消息用于请求去激活所述第二服务质量流绑定的 策略与计费控制规则；
    接收来自所述策略控制功能网元的第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  74. 根据权利要求73所述的装置，其特征在于，所述处理单元还用于：
    根据所述第四消息，确定所述第一应用业务的业务流；
    根据所述第二服务质量流对应的业务流和所述第一应用业务的多个业务流，确定所述第一应用业务的多个业务流中未被释放的业务流。
  75. 一种通信装置，其特征在于，所述装置包括处理单元和收发单元，其中：
    所述收发单元，用于接收来自会话管理功能网元的第六消息，所述第六消息用于请求去激活第二服务质量流绑定的策略与计费控制规则，所述第二服务质量流对应的第一业务流是第一应用业务的多个业务流中的一个；
    所述处理单元，用于确定所述第一应用业务对应的多个策略与计费控制规则；以及，去激活所述第一应用业务对应的多个策略与计费控制规则。
  76. 根据权利要求75所述的装置，其特征在于，
    所述收发单元还用于接收来自应用功能网元的请求消息，所述请求消息用于请求为所述第一业务流提供质量服务，其中，所述请求消息包括第四信息，所述第四信息用于关联所述第一应用业务的多个业务流；
    所述处理单元还用于根据所述请求消息，生成第一策略与计费控制规则，其中，所述第一策略与计费控制规则包括第一信息，所述第一信息用于关联所述第一应用业务对应的多个策略与计费控制规则；
    所述收发单元还用于向所述会话管理功能网元发送第一策略与计费控制规则。
  77. 根据权利要求76所述的装置，其特征在于，所述第一应用业务对应的多个策略与计费控制规则中的每个策略与计费控制规则包括所述第一信息。
  78. 根据权利要求76或77所述的装置，其特征在于，不包括所述第一信息的策略与计费控制规则对应的应用业务与所述第一应用业务是不同的应用业务。
  79. 根据权利要求76至78中任一项所述的装置，其特征在于，所述处理单元还用于：
    根据所述第四信息，确定所述第一信息。
  80. 根据权利要求76至79中任一项所述的装置，其特征在于，所述装置还包括：
    确定所述第一应用业务的多个业务流之间的关联关系。
  81. 根据权利要求76至80中任一项所述的装置，其特征在于，在确定所述第一应用业务对应的多个策略与计费控制规则时，所述处理单元具体用于：
    根据所述第四信息和所述第二服务质量流所绑定的策略与计费控制规则，确定所述第一应用业务对应的多个策略与计费控制规则。
  82. 根据权利要求76至81中任一项所述的装置，其特征在于，所述收发单元还用于：
    向所述会话管理功能网元发送第四消息，所述第四消息用于指示去激活所述第一应用业务对应的多个策略与计费控制规则。
  83. 一种通信装置，其特征在于，包括一个或多个处理器和存储器，所述一个或多个处理器与所述存储器耦合；
    所述存储器，用于存储计算机程序；
    所述一个或多个处理器，用于执行所述存储器中存储的计算机程序，以使得所述通信装置执行如权利要求1至13中任一项所述的方法，或执行如权利要求14至22中任一项所述的方法，或执行如权利要求23或24所述的方法，或执行如权利要求25至33中任一项所述的方法，或执行如权利要求34至41中任一项所述的方法。
  84. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以执行如权利要求1至13中任一项所述的方法，或者执行如权利要求14至22中任一项所述的方法，或者执行如权利要求23或24所述的方法，或者执行如权利要求25至33中任一项所述的方法，或者执行如权利要求34至41中任一项所述的方法。
  85. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，执行如权利要求1至13中任一项所述的方法，或者执行如权利要求14至22中任一项所述的方法， 或者执行如权利要求23或24所述的方法，或者执行如权利要求25至33中任一项所述的方法，或者执行如权利要求34至41中任一项所述的方法。
  86. 一种通信系统，其特征在于，包括如权利要求42至54中任一项所述的通信装置、如权利要求55至63中任一项所述的通信装置、和如权利要求64或65所述的通信装置；或者包括如权利要求66至74中任一项所述的通信装置和如权利要求75至82中任一项所述的通信装置。
  87. 一种计算机程序产品，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，如权利要求1至13中任一项所述的方法被执行，或者如权利要求14至22中任一项所述的方法被执行，或者如权利要求23或24所述的方法被执行，或者执行如权利要求25至33中任一项所述的方法，或者执行如权利要求34至41中任一项所述的方法。
  88. 一种通信方法，其特征在于，应用于会话管理功能网元，所述方法包括：
    略控制功能网元发送第一策略与计费控制规则，所述第一策略与计费控制规则包括第一信息，其中，所述第一信息用于关联第一应用业务对应的一个或多个策略与计费控制规则；
    会话管理功能网元将所述第一策略与计费控制规则与所述第一服务质量流绑定，其中，所述第一服务质量流不与不包括所述第一信息的策略与计费控制规则绑定；
    向第一网元发送所述第一服务质量流的信息。
PCT/CN2023/120642 2022-10-03 2023-09-22 一种通信方法及装置 WO2024074095A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211217390.9A CN117835175A (zh) 2022-10-03 2022-10-03 一种通信方法及装置
CN202211217390.9 2022-10-03

Publications (1)

Publication Number Publication Date
WO2024074095A1 true WO2024074095A1 (zh) 2024-04-11

Family

ID=90519642

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/120642 WO2024074095A1 (zh) 2022-10-03 2023-09-22 一种通信方法及装置

Country Status (2)

Country Link
CN (1) CN117835175A (zh)
WO (1) WO2024074095A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111565422A (zh) * 2019-02-13 2020-08-21 华为技术有限公司 策略控制方法、装置及系统
CN112437122A (zh) * 2020-11-08 2021-03-02 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备
CN114205839A (zh) * 2020-09-02 2022-03-18 华为技术有限公司 多流关联传输的方法、装置及系统
WO2022069931A1 (en) * 2020-10-01 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing consolidation of policies and related network nodes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111565422A (zh) * 2019-02-13 2020-08-21 华为技术有限公司 策略控制方法、装置及系统
CN114205839A (zh) * 2020-09-02 2022-03-18 华为技术有限公司 多流关联传输的方法、装置及系统
WO2022069931A1 (en) * 2020-10-01 2022-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Methods providing consolidation of policies and related network nodes
CN112437122A (zh) * 2020-11-08 2021-03-02 腾讯科技（深圳）有限公司 通信方法、装置、计算机可读介质及电子设备

Also Published As

Publication number Publication date
CN117835175A (zh) 2024-04-05

Similar Documents

Publication Publication Date Title
US11909652B2 (en) Method, device and storage medium for quality of service (QoS) flow management of time sensitive data for transmission of ethernet packet filter sets
EP3879879B1 (en) Time sensitive networking communication method and apparatus thereof
WO2020220747A1 (zh) 一种tsn业务的处理方法、装置及系统
WO2020019764A1 (zh) 信息传输方法、设备及计算机可读存储介质
WO2021037175A1 (zh) 一种网络切片的管理方法及相关装置
WO2020200066A1 (zh) 获取数据包延迟参数的方法、系统和装置
EP3869855A1 (en) Information transmission method and apparatus thereof
WO2021032131A1 (zh) 一种用户面信息上报方法及装置
WO2021135187A1 (zh) 一种切片控制方法及装置
WO2022033558A1 (zh) 一种中继管理方法及通信装置
WO2021017669A1 (zh) 一种通信方法及设备
US20210112437A1 (en) User Plane QOS Bearer Control Method for 5G Fixed Access
CN114365527A (zh) 用于无线通信系统中的网络自动化的装置和方法
WO2020220799A1 (zh) 一种通信方法、装置及系统
JP7543914B2 (ja) ネットワーク配置制御装置、通信システム、および、その制御方法
CN112087777B (zh) 一种mdbv的确定方法、装置及系统
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
US20240284243A1 (en) Quality of service processing method and apparatus and communication system
CN114697999A (zh) 一种冗余路径创建方法、装置及系统
WO2024074095A1 (zh) 一种通信方法及装置
WO2023116355A1 (zh) 通信方法、装置、相关设备及存储介质
EP4325929A1 (en) Wireless communication method, communication apparatus and communication system
WO2021057342A1 (zh) 一种网络切片的计费方法及装置
WO2021057020A1 (zh) 一种网络切片的计费方法及装置
WO2021103009A1 (zh) 上行pdr的生成方法、装置及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23874287

Country of ref document: EP

Kind code of ref document: A1