CN117545023A

CN117545023A - Communication method, communication device, and communication system

Info

Publication number: CN117545023A
Application number: CN202210922949.1A
Authority: CN
Inventors: 周晓云; 朱奋勤
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-08-02
Filing date: 2022-08-02
Publication date: 2024-02-09

Abstract

A communication method, a communication device and a communication system. The method comprises the following steps: the control plane network element sends first indication information to the first access network device, and the indication access network device sends the first indication information to the user plane network element and the control plane network element: informing whether the QoS of the first QoS flow can be ensured and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the control surface network element receives first notification information from first access network equipment and information of first candidate QoS files, wherein the first notification information notifies that QoS of a first QoS flow cannot be guaranteed, and the first candidate QoS files are candidate QoS files of the first QoS flow which can be supported by the first access network equipment; the control plane network element sends QoS parameters corresponding to the first candidate QoS file to the terminal equipment. In the application, the control plane network element sends the QoS parameters of the candidate QoS file to the terminal equipment, and the terminal equipment can acquire the candidate QoS file which is being executed by the first access network equipment.

Description

Communication method, communication device, and communication system

Technical Field

The embodiments of the present application relate to the field of communications, and more particularly, to a communication method, a communication device, and a communication system.

Background

In some systems, such as the fifth generation (5th generation,5G) system, a user establishes a protocol data unit (protocol data unit, PDU) session after accessing the network and interacts with an application server deployed in the data network by accessing an external data network through the PDU session. For applications accessed by users, information of quality of service (quality of service, qoS) flows is important, such as may be used by the application layer to perform corresponding policy adjustments, etc. The problem of the transfer of information about QoS is considerable.

Disclosure of Invention

The application provides a communication method, a communication device and a communication system, so that a network can acquire QoS information of QoS flows of users, and the users can also acquire the QoS information through a control surface network element.

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

The method may include: the control plane network element sends first indication information to the first access network device, and the first indication information indicates the access network device to send to the user plane network element and the control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the control surface network element receives first notification information from first access network equipment and information of first candidate QoS files, wherein the first notification information notifies that QoS of a first QoS flow cannot be guaranteed, and the first candidate QoS files are candidate QoS files of the first QoS flow which can be supported by the first access network equipment; the control plane network element sends a first QoS parameter corresponding to the first candidate QoS file to the terminal equipment.

Illustratively, the method further comprises: the control plane network element sends information of the QoS file of the first QoS flow to the first access network device.

Illustratively, the method further comprises: the control plane network element sends information of at least one candidate QoS file to the first access network device, the information of the at least one candidate QoS file comprising information of the first candidate QoS file.

Illustratively, the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, indicating: the first notification information notifies that QoS of the QoS file of the first QoS flow cannot be guaranteed.

Based on the above technical solution, the control plane network element sends the first indication information to the first access network device, so that the first access network device may send a notification for notifying whether the QoS of the first QoS flow can be guaranteed to the control plane network element, and in the case that the QoS of the first QoS flow cannot be guaranteed, the first access network device may send the candidate QoS file of the first QoS flow that the first access network device can support to the control plane network element. In this way, the control plane network element may learn QoS information of the QoS flow of the terminal device, such as information of candidate QoS files of the first QoS flow that the first access network device can support. In addition, the control plane network element can also send the QoS parameters corresponding to the first candidate QoS file to the terminal device, so that the terminal device can acquire the candidate QoS file currently being executed by the first access network device, and further communication between the terminal device and the network side can be realized based on the QoS parameters of the candidate QoS file currently being executed by the first access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control surface network element receives second indication information from the policy control network element, wherein the second indication information indicates to inform the terminal equipment of QoS parameters of QoS flows which can be supported by the access network equipment, or the second indication information indicates to send to the user surface network element and the control surface network element by the access network equipment: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the control plane network element sends first indication information to the first access network device, including: based on the second indication information, the control plane network element sends first indication information to the first access network device. In particular, the second indication information may be carried in policy rules.

Based on the above technical solution, if the control plane network element receives an indication informing the terminal device of the QoS parameters of the QoS flows that the access network device can support, in order to inform the terminal device of the QoS parameters of the QoS flows that the access network device can support, the control plane network element first obtains the information of the corresponding QoS flows, so that the control plane network element sends the first indication information to the first access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control surface network element receives a policy rule from the policy control network element, wherein the policy rule does not comprise third indication information, and the third indication information indicates that QoS parameters of QoS flows which can be supported by the access network equipment are not notified to the terminal equipment; the control plane network element sends first indication information to the first access network device, including: based on the policy rules, the control plane network element sends first indication information to the first access network device.

For example, the third indication information indicates that the terminal device is not informed of QoS parameters of QoS flows that the access network device can support may be replaced with: the third indication information indicates that the access network device does not send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

Based on the above technical solution, when the control plane network element does not receive an indication that does not notify the terminal device of the QoS parameters of the QoS flows that can be supported by the access network device, the control plane network element notifies the terminal device of the QoS parameters of the QoS flows supported by the access network device by default, and in order to notify the terminal device of the QoS parameters of the QoS flows that can be supported by the access network device, the control plane network element first obtains information of the corresponding QoS flows, so that the control plane network element sends first indication information to the first access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control surface network element sends a QoS file of a first QoS flow to first access network equipment; the control surface network element receives second notification information from the first access network device, and the second notification information notifies that the QoS of the first QoS flow can be ensured; and responding to the second notification information, and sending a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment by the control surface network element.

Based on the above technical solution, in the case that the QoS of the first QoS flow can be guaranteed, that is, in the case that the QoS corresponding to the QoS file of the first QoS flow can be guaranteed, the control plane network element sends the second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal device, so that the terminal device and the network side can communicate based on the QoS parameter of the QoS file currently being executed by the first access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control surface network element receives third notification information from the second access network device, and the third notification information notifies that the QoS of the first QoS flow can be ensured; responding to the third notification information, and transmitting a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment by the control surface network element; the first access network device is access network device accessed before terminal device switching, the second access network device is access network device accessed after terminal device switching, and the QoS file of the first QoS flow is sent by the control plane network element to the first access network device.

Based on the above technical solution, if the terminal device performs handover, for example, from the first access network device to the second access network device, the second access network device may inform the control plane network element whether the QoS of the first QoS flow can be guaranteed. Further, in the case that the QoS of the first QoS flow can be guaranteed, that is, in the case that the QoS corresponding to the QoS file of the first QoS flow can be guaranteed, the second access network device notifies the control plane network element that the QoS of the first QoS flow can be guaranteed, and after receiving the notification, the control plane network element sends the second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal device, so that it is possible that the terminal device and the network side can communicate based on the QoS parameter of the QoS file currently being executed by the second access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control surface network element receives fourth known information from the second access network device and information of a second candidate QoS file, wherein the fourth known information informs that the QoS of the first QoS flow cannot be guaranteed, and the second candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the second access network device; the control surface network element sends a third QoS parameter corresponding to the second candidate QoS file to the terminal equipment; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

Based on the above technical solution, if the terminal device performs handover, for example, from the first access network device to the second access network device, the second access network device may inform the control plane network element whether the QoS of the first QoS flow can be guaranteed. Further, in the case that the QoS of the first QoS flow cannot be guaranteed, that is, in the case that the QoS corresponding to the QoS file of the first QoS flow cannot be guaranteed, the second access network device notifies the control plane network element that the QoS of the first QoS flow cannot be guaranteed and the candidate QoS file of the first QoS flow that the second access network device can support, after receiving the notification, the control plane network element sends, to the terminal device, the QoS parameter corresponding to the candidate QoS file of the first QoS flow that the second access network device can support, so that the terminal device and the network side can communicate based on the QoS parameter of the candidate QoS file currently being executed by the second access network device.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the control plane network element receives at least one QoS flow identification from the second access network device that is accepted by the second access network device, the at least one QoS flow identification comprising an identification of the first QoS flow.

Based on the above technical solution, the control plane network element may further determine, based on that the at least one QoS flow identifier accepted by the second access network device includes an identifier of the first QoS flow, that the second access network device accepts or supports the first QoS flow.

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

The method may include: the control plane network element sends first indication information to the user plane network element, and the first indication information indicates the user plane network element to send to the control plane network element: informing whether the QoS of the first QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the control plane network element receives first notification information from the user plane network element and information of a first candidate QoS file, wherein the first notification information notifies that QoS of a first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by first access network equipment; the control plane network element sends a first QoS parameter corresponding to the first candidate QoS file to the terminal equipment.

Based on the above technical solution, the control plane network element sends the first indication information to the user plane network element, so that the user plane network element can send a notification for notifying whether the QoS of the first QoS flow can be guaranteed to the control plane network element, and the user plane network element can send the information of the candidate QoS file of the first QoS flow that can be supported by the first access network device to the control plane network element when the QoS of the first QoS flow cannot be guaranteed. In this way, the control plane network element may learn QoS information of the QoS flow of the terminal device, such as a candidate QoS file of the first QoS flow that the first access network device can support. In addition, the control plane network element can also send the QoS parameters corresponding to the first candidate QoS file to the terminal device, so that the terminal device can acquire the candidate QoS file currently being executed by the first access network device, and further communication between the terminal device and the network side can be realized based on the QoS parameters of the candidate QoS file currently being executed by the first access network device.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control plane network element receives second indication information from the policy control network element, wherein the second indication information indicates to inform the terminal equipment of QoS parameters of QoS flows which can be supported by the access network equipment, or the second indication information indicates to the user plane network element to send to the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the control plane network element sends first indication information to the user plane network element, including: based on the second indication information, the control plane network element sends the first indication information to the user plane network element. In particular, the second indication information may be carried in policy rules.

Based on the above technical solution, if the control plane network element receives an indication informing the terminal device of the QoS parameters of the QoS flow that the access network device can support, in order to inform the terminal device of the QoS parameters of the QoS flow that the access network device can support, the control plane network element first obtains the information of the corresponding QoS flow, so that the control plane network element sends the first indication information to the user plane network element.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control surface network element receives a policy rule from the policy control network element, wherein the policy rule does not comprise third indication information, and the third indication information indicates that QoS parameters of QoS flows which can be supported by the access network equipment are not notified to the terminal equipment; the control plane network element sends first indication information to the user plane network element, including: based on the policy rules, the control plane network element sends first indication information to the user plane network element.

For example, the third indication information indicates that the terminal device is not informed of QoS parameters of QoS flows that the access network device can support may be replaced with: the third indication information indicates that the user plane network element does not send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

Based on the above technical solution, when the control plane network element does not receive an indication that does not notify the terminal device of the QoS parameters of the QoS flows that can be supported by the access network device, the control plane network element notifies the terminal device of the QoS parameters of the QoS flows supported by the access network device by default, and in order to notify the terminal device of the QoS parameters of the QoS flows that can be supported by the access network device, the control plane network element first obtains information of the corresponding QoS flows, so that the control plane network element sends first indication information to the user plane network element.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control surface network element receives second notification information from the user surface network element, and the second notification information notifies that the QoS of the first QoS flow can be ensured; and responding to the second notification information, and sending a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment by the control surface network element.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control surface network element receives third notification information from the second access network device, and the third notification information notifies that the QoS of the first QoS flow can be ensured; responding to the third notification information, and transmitting a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment by the control surface network element; the first access network device is access network device accessed before terminal device switching, the second access network device is access network device accessed after terminal device switching, and the QoS file of the first QoS flow is sent by the control plane network element to the first access network device.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control surface network element receives fourth known information from the second access network device and information of a second candidate QoS file, wherein the fourth known information informs that the QoS of the first QoS flow cannot be guaranteed, and the second candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the second access network device; the control surface network element sends a third QoS parameter corresponding to the second candidate QoS file to the terminal equipment; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the control plane network element receives at least one QoS flow identification from the second access network device that is accepted by the second access network device, the at least one QoS flow identification comprising an identification of the first QoS flow.

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

The method may include: the first access network equipment receives first indication information from the control plane network element, and the first indication information indicates the access network equipment to send to the user plane network element and the control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; under the condition that the QoS of the first QoS flow cannot be guaranteed, the first access network equipment sends first notification information and information of a first candidate QoS file to the control plane network element and the user plane network element, wherein the first notification information notifies that the QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the first access network equipment.

Illustratively, the method further comprises: the first access network device receives information of a QoS file of a first QoS flow from a control plane network element.

Based on the above technical solution, the first access network device receives the first indication information from the control plane network element, and in the case that the QoS of the first QoS flow cannot be guaranteed, the first access network device may send, to the control plane network element and the user plane network element, a notification for notifying that the QoS of the first QoS flow cannot be guaranteed, and information of the candidate QoS file of the first QoS flow that the first access network device can support, based on the first indication information. In this way, the control plane network element may learn QoS information of the QoS flow of the terminal device, such as information of candidate QoS files of the first QoS flow that the first access network device can support.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first access network device receives information of at least one candidate QoS file for a first QoS flow from a control plane network element, the information of the at least one candidate QoS file comprising information of the first candidate QoS file.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first access network device sends second notification information to the control plane network element, and the second notification information notifies that the QoS of the first QoS flow can be guaranteed.

Based on the above technical solution, in the case that the QoS of the first QoS flow can be guaranteed, that is, in the case that the QoS corresponding to the QoS file of the first QoS flow can be guaranteed, the first access network device sends a notification that the QoS of the first QoS flow can be guaranteed to the control plane network element, so that the control plane network element can learn that the QoS file is currently being executed by the first access network device.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first access network device sends fourth indication information to the second access network device, the fourth indication information is determined according to the first indication information, and the fourth indication information indicates the access network device to send to the user plane network element and the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. The first access network device is the access network device accessed before the terminal device is switched, and the second access network device is the access network device accessed after the terminal device is switched.

Based on the above technical solution, if the terminal device is switched from the first access network device to the second access network device, based on the first indication information, the first access network device may send fourth indication information to the second access network device, so that the second access network device may learn to send to the user plane network element and the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the second access network device can support. In this way, even if a handover occurs, information of QoS flows may be able to be reported.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the first access network device sends the identification of the first QoS flow and the information of the first candidate QoS file to the second access network device.

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

The method may include: the user plane network element receives first indication information from the control plane network element, wherein the first indication information indicates the user plane network element to send to the control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the user plane network element sends first notification information and information of a first candidate QoS file to the control plane network element, wherein the first notification information notifies that QoS of a first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the first access network device.

Based on the above technical solution, the user plane network element receives the first indication information sent by the control plane network element, and based on the first indication information, the user plane network element may send a notification for notifying whether the QoS of the first QoS flow can be guaranteed to the control plane network element, and in the case that the QoS of the first QoS flow cannot be guaranteed, the user plane network element may send, to the control plane network element, information of the candidate QoS file of the first QoS flow that can be supported by the first access network device. In this way, the control plane network element may learn QoS information of the QoS flow of the terminal device, such as information of candidate QoS files of the first QoS flow that the first access network device can support.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the user plane network element receives first notification information and information of a first candidate QoS file from a first access network device.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the user plane network element receives second notification information from the first access network device, and the second notification information notifies that the QoS of the first QoS flow can be ensured; the user plane network element sends second notification information to the control plane network element.

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

The method may include: the policy control network element sends second indication information to the control plane network element, wherein the second indication information indicates to inform the terminal equipment of QoS parameters of QoS flows which can be supported by the access network equipment, or the second indication information indicates to send the access network equipment to the user plane network element and the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In particular, the second indication information may be carried in policy rules.

Alternatively, the method may comprise: the policy control network element sends policy rules to the control plane network element, the policy rules do not include third indication information, and the third indication information indicates that QoS parameters of QoS flows which can be supported by the access network device are not notified to the terminal device.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes: the policy control network element receives fifth indication information from the application network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates that the access network device sends to the user plane network element and the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the policy control network element sends second indication information to the control plane network element, including: based on the fifth indication information, the policy control network element sends second indication information to the control plane network element. In particular, the second indication information may be carried in policy rules.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes: the policy control network element receives fifth indication information from the application network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates that the access network device sends to the user plane network element and the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the policy control network element sends policy rules to the control plane network element, the policy rules not including third indication information, including: based on the fifth indication information, the policy control network element sends policy rules to the control plane network element, the policy rules not including the third indication information.

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

The method may include: the policy control network element sends second indication information to the control plane network element, where the second indication information indicates to inform the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the second indication information indicates to the user plane network element to send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In particular, the second indication information may be carried in policy rules.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the policy control network element receives fifth indication information from the application network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates to the user plane network element to send to the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the policy control network element sends second indication information to the control plane network element, including: based on the fifth indication information, the policy control network element sends second indication information to the control plane network element. In particular, the second indication information may be carried in policy rules.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the policy control network element receives fifth indication information from the application network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates to the user plane network element to send to the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the policy control network element sends policy rules to the control plane network element, the policy rules not including third indication information, including: based on the fifth indication information, the policy control network element sends policy rules to the control plane network element, the policy rules not including the third indication information.

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

The method may include: the application network element sends fifth indication information to the policy control network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates to the access network device to send to the user plane network element and the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

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

The method may include: the application network element sends fifth indication information to the policy control network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates to the user plane network element to send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

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

The method may include: the second access network device receives fourth indication information from the first access network device, and the fourth indication information indicates the access network device to send to the user plane network element and the control plane network element: and informing whether the QoS of the first QoS flow can be ensured and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment, wherein the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after the terminal equipment is switched.

Based on the above technical solution, if the terminal device is switched from the first access network device to the second access network device, the second access network device receives the fourth indication information from the first access network device, so that the second access network device can learn to send to the user plane network element and the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the second access network device can support. In this way, even if a handover occurs, information of QoS flows may be able to be reported.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the method further includes: and under the condition that the QoS of the first QoS flow can be ensured, the second access network equipment sends third notification information to the control plane network element and the user plane network element, and the third notification information notifies that the QoS of the first QoS flow can be ensured.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the method further includes: and under the condition that the QoS of the first QoS flow cannot be ensured, the second access network equipment sends fourth known information and information of second candidate QoS files to the control plane network element and the user plane network element, the fourth known information informs that the QoS of the first QoS flow cannot be ensured, and the second candidate QoS files are candidate QoS files of the first QoS flow which can be supported by the second access network equipment.

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

The method may include: the second access network equipment receives information of a first candidate QoS file from the first access network equipment, wherein the first candidate QoS file is a candidate QoS file of a first QoS flow which can be supported by the first access network equipment; in the case that the QoS of the first QoS flow cannot be guaranteed, and the candidate QoS file of the first QoS flow that can be supported by the second access network device does not include the first candidate QoS file, the second access network device sends fourth notification information and information of the second candidate QoS file to the control plane network element, where the second candidate QoS file is the candidate QoS file of the first QoS flow that can be supported by the second access network device, and the fourth notification information notifies that the QoS of the first QoS flow cannot be guaranteed; under the condition that the QoS of the first QoS flow can be ensured, the second access network equipment sends third notification information to the control plane network element, and the third notification information notifies that the QoS of the first QoS flow can be ensured; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

Wherein the QoS of the first QoS flow can be guaranteed, and the QoS in the QoS file representing the first QoS flow can be guaranteed. The QoS of the first QoS flow cannot be guaranteed, meaning that the QoS in the QoS file of the first QoS flow cannot be guaranteed.

Based on the above technical solution, if the terminal device is switched from the first access network device to the second access network device, the second access network device receives the first candidate QoS file of the first QoS flow that can be supported by the first access network device from the first access network device, so that the second access network device can determine whether the QoS of the QoS file of the first QoS flow can be guaranteed or not according to the actual communication situation, or whether the candidate QoS file corresponding to the first QoS flow is updated or not. In the case that the QoS of the QoS file of the first QoS flow cannot be guaranteed, and the candidate QoS file of the first QoS flow that can be supported by the second access network device does not include the first candidate QoS file, the second access network device sends fourth notification information and the second candidate QoS file to the control plane network element and/or the user plane network element, where the second candidate QoS file is the candidate QoS file of the first QoS flow that can be supported by the second access network device, and the fourth notification information notifies that the QoS of the first QoS flow cannot be guaranteed; and under the condition that the QoS of the first QoS flow can be ensured, the second access network equipment sends third notification information to the control plane network element and/or the user plane network element, and the third notification information notifies that the QoS of the first QoS flow can be ensured. In this way, the information of the QoS flow can be reported during the handover of the cross-access network device.

With reference to the tenth aspect, in certain implementations of the tenth aspect, the method further includes: the second access network device determines whether the information of the first QoS flow is updated.

By way of example, whether the information of the first QoS flow is updated may include, for example: whether the guarantee condition of the QoS in the QoS file of the first QoS flow changes and/or whether the candidate QoS file corresponding to the first QoS flow changes.

With reference to the tenth aspect, in some implementations of the tenth aspect, before the second access network device sends the fourth known information and the information of the second candidate QoS file to the control plane network element, the method further includes: the second access network device determines, according to the information of the first candidate QoS file, that the candidate QoS file implemented for the first QoS flow changes from the first candidate QoS file to the second candidate QoS file in the case that the QoS of the first QoS flow cannot be guaranteed.

With reference to the tenth aspect, in some implementations of the tenth aspect, before the second access network device sends the third notification information to the control plane network element, the method further includes: the second access network device determines that QoS of the first QoS flow is changed from unable to guaranteed.

With reference to the tenth aspect, in some implementations of the tenth aspect, in a case that QoS of the first QoS flow cannot be guaranteed and the candidate QoS file of the first QoS flow that the second access network device can support does not include the first candidate QoS file, the method further includes: the second access network device sends fifth notification information and information of the second candidate QoS file to the user plane network element, wherein the fifth notification information notifies that QoS of the first QoS flow cannot be guaranteed.

With reference to the tenth aspect, in some implementations of the tenth aspect, in a case that QoS of the first QoS flow can be guaranteed, the method further includes: the second access network device sends sixth notification information to the user plane network element, wherein the sixth notification information notifies that the QoS of the first QoS flow cannot be guaranteed.

In an eleventh aspect, a communication method is provided, where the method may be performed by a user plane network element, or may also be performed by a component (such as a chip or a circuit) of the user plane network element, and this is not limited, and for convenience of description, the following is described by taking a case of being performed by the user plane network element.

The method may include: the user plane network element receives information of at least one QoS flow accepted by second access network equipment from the second access network equipment, wherein the at least one QoS flow comprises a first QoS flow; the user plane network element judges whether the QoS information of the first QoS flow is updated or not based on the information of at least one QoS flow accepted by the second access network device and the information of a first candidate QoS file received before from the first access network device, wherein the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the first access network device; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

Based on the above technical solution, if the terminal device is switched from the first access network device to the second access network device, the user plane network element receives information of at least one QoS flow received by the second access network device from the second access network device. In this way, the user plane network element may determine whether the information of the first QoS flow is updated based on the information provided by the first access network device before the handover and the information provided by the second access network device after the handover.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the method further includes: the user plane network element receives first notification information from the first access network device and information of the first candidate QoS file, wherein the first notification information notifies that QoS of the first QoS flow cannot be guaranteed.

With reference to the eleventh aspect, in some implementations of the eleventh aspect, the information of the at least one QoS flow accepted by the second access network device includes: the identification of at least one QoS flow and/or the QoS candidate file corresponding to the at least one QoS flow.

With reference to the eleventh aspect, in some implementations of the eleventh aspect, the determining, by the user plane network element, whether the QoS information of the first QoS flow is updated based on the information of the at least one QoS flow accepted by the second access network device and the information of the first candidate QoS file received previously from the first access network device includes: the information of the at least one QoS flow accepted by the second access network device includes: the identifier of the first QoS flow and the QoS candidate file corresponding to the first QoS flow, and the QoS candidate file corresponding to the first QoS flow is the second QoS candidate file, the user plane network element judges that the QoS information of the first QoS flow is updated. Wherein, the QoS information of the first QoS flow is updated, and the candidate QoS file realized by the first QoS flow is changed from the first candidate QoS file to the second candidate QoS file.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the method further includes: the user plane network element sends the information of the second candidate QoS file to the control plane network element and/or the application network element.

With reference to the eleventh aspect, in some implementations of the eleventh aspect, the determining, by the user plane network element, whether the QoS information of the first QoS flow is updated based on the information of the at least one QoS flow accepted by the second access network device and the information of the first candidate QoS file received previously from the first access network device includes: if the information of at least one QoS flow accepted by the second access network equipment comprises the identification of the first QoS flow, the user plane network element judges that the QoS information of the first QoS flow is updated. Wherein, the QoS information of the first QoS flow is updated, and the QoS in the QoS file of the first QoS flow cannot be guaranteed to be guaranteed, that is, the QoS in the QoS file of the first QoS flow can be guaranteed again.

Illustratively, the information of the at least one QoS flow accepted by the second access network device includes an identification of the first QoS flow, which may implicitly indicate that QoS in the QoS file of the first QoS flow can be guaranteed.

Illustratively, the information of the at least one QoS flow accepted by the second access network device includes an identification of the first QoS flow, and the information of the at least one QoS flow accepted by the second access network device does not include a candidate QoS file corresponding to the first QoS flow. In this case, the user plane network element determines, based on the information of at least one QoS flow accepted by the second access network device, that the QoS information of the first QoS flow is updated, that is, that the QoS in the QoS file of the first QoS flow cannot be guaranteed to be guaranteed.

Illustratively, the information of the at least one QoS flow accepted by the second access network device further includes sixth notification information that notifies that QoS of the first QoS flow can be guaranteed. In this case, the user plane network element may identify the first QoS flow based on the identifier of the first QoS flow, and determine that the QoS information of the first QoS flow is updated according to the sixth notification information, that is, the QoS in the QoS file of the first QoS flow cannot be guaranteed to be changed to be guaranteed.

With reference to the eleventh aspect, in certain implementations of the eleventh aspect, the method further includes: the user plane network element sends second notification information to the control plane network element, the second notification information notifying that the QoS of the first QoS flow can be guaranteed.

A twelfth aspect provides a communication device for performing the method provided in any one of the first to eleventh aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method provided by any of the above-mentioned implementations of any of the first to eleventh aspects.

In one implementation, the apparatus is a communication device (e.g., a control plane network element, as well as an access network device, as well as a user plane network element). When the apparatus is a communication device, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for use in a communication device. When the apparatus is a chip, a system-on-chip or a circuit used in a terminal device, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc. on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a thirteenth aspect, there is provided a communication device comprising: a memory for storing a program; at least one processor configured to execute a computer program or instructions stored in a memory to perform a method provided by any one of the implementations of any one of the first to eleventh aspects.

In one implementation, the apparatus is a communication device (e.g., a control plane network element, as well as an access network device, as well as a user plane network element).

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for use in a communication device.

In a fourteenth aspect, the present application provides a processor configured to perform the method provided in the above aspects.

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

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

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

A seventeenth aspect provides a chip comprising a processor and a communication interface, the processor reading instructions stored on a memory via the communication interface, performing the method provided by any one of the implementations of any one of the first to eleventh aspects.

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

An eighteenth aspect provides a communication system, including one or more of the foregoing control plane network element, user plane network element, first access network device, second access network device, policy control network element, application network element, and terminal device.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application.

Fig. 2 is another schematic diagram of a network architecture suitable for use in embodiments of the present application.

Fig. 3 is a schematic diagram of a communication method 300 according to an embodiment of the present application.

Fig. 4 is a schematic flow chart of a communication method 400 provided in an embodiment of the present application.

FIG. 5 is a schematic diagram of an architecture suitable for use in embodiments of the present application.

Fig. 6 is a schematic diagram of another architecture suitable for use with embodiments of the present application.

Fig. 7 is a schematic flow chart diagram of a communication method 700 provided in an embodiment of the present application.

Fig. 8 is a schematic flow chart diagram of a communication method 800 provided in an embodiment of the present application.

Fig. 9 is a schematic flow chart diagram of a communication method 900 provided in an embodiment of the present application.

Fig. 10 is a schematic block diagram of a communication device 1000 provided in an embodiment of the present application.

Fig. 11 is a schematic block diagram of a communication device 1100 provided by an embodiment of the present application.

Fig. 12 is a schematic block diagram of a chip system 1200 provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

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

To facilitate an understanding of the embodiments of the present application, a communication system suitable for use in the embodiments of the present application will be described in detail with reference to fig. 1 and 2.

Fig. 1 is a schematic diagram of a network architecture suitable for use in embodiments of the present application. As shown in fig. 1, the network architecture may include, for example, but is not limited to, the following: a User Equipment (UE), AN Access Network (AN), AN access and mobility management function (access and mobility management function, AMF) element, a session management function (session management function, SMF) element, a user plane function (user plane function, UPF) element, a policy control function (policy control function, PCF) element, a unified data management (unified data management, UDM) element, AN application function (application function, AF), a Data Network (DN), and the like.

The following briefly describes the network elements shown in fig. 1:

1. UE: a terminal device, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment may be referred to as a terminal device.

The terminal device may be a device that provides voice/data to a user, e.g., a handheld device with wireless connection, an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone, tablet, laptop, palmtop, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, wearable device, terminal device in 5G network or terminal in future evolved land mobile communication network (public land mobile network), and the like, without limiting the present application.

By way of example, and not limitation, in embodiments of the present application, the terminal device may be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the terminal device may also be a terminal device in an IoT system, where IoT is an important component of future information technology development, and the main technical feature is to connect the article with a network through a communication technology, so as to implement man-machine interconnection and an intelligent network for interconnecting the articles.

In addition, the terminal device may further include sensors such as an intelligent printer, a train detector, and a gas station, and the main functions include collecting data (part of the terminal device), receiving control information and downlink data of the network device, and transmitting electromagnetic waves to transmit uplink data to the network device.

It should be understood that the terminal device may be any device that can access the network. The terminal device and the access network device can communicate with each other by adopting a certain air interface technology (such as NR or LTE technology). The terminal equipment and the terminal equipment can also communicate with each other by adopting a certain air interface technology (such as NR or LTE technology).

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

In the embodiment of the present application, the device for implementing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to implement the function, for example, a chip system or a chip, and the device may be installed in the terminal device. In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

2. (radio) access network (R) AN) device: the authorized users of the specific area may be provided with the functionality to access the communication network, which may specifically include wireless network devices in a third generation partnership project (3rd generation partnership project,3GPP) network or may include access points in a non-3GPP (non-3 GPP) network. The following description will be presented using AN apparatus for convenience of description.

AN device may employ different radio access technologies. There are two types of current radio access technologies: 3GPP access technologies (e.g., third generation (3rd generation,3G), fourth generation (4th generation,4G), or wireless access technologies employed in 5G systems) and non-3GPP (non-3 GPP) access technologies. The 3GPP access technology refers to an access technology conforming to the 3GPP standard specification, for example, access network devices in a 5G system are referred to as next generation base station nodes (next generation Node Base station, gNB) or RAN devices. Non-3GPP access technologies can include air interface technologies typified by an Access Point (AP) in Wireless Fidelity (wireless fidelity, wiFi), worldwide interoperability for microwave Access (worldwide interoperability for microwave access, wiMAX), code division multiple Access (code division multiple access, CDMA), and so forth. The AN device may allow interworking between the terminal device and the 3GPP core network using non-3GPP technology.

The AN device can be responsible for radio resource management, quality of service (quality of service, qoS) management, data compression, encryption, and other functions on the air interface side. The AN equipment provides access service for the terminal equipment, and further, the forwarding of control signals and user data between the terminal equipment and the core network is completed.

AN devices may include, for example, but are not limited to: macro base stations, micro base stations (also called small stations), radio network controllers (radio network controller, RNC), node bs (Node bs, NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved NodeB, or home Node bs, HNB), base Band Units (BBU), APs in WiFi systems, wireless relay nodes, wireless backhaul nodes, transmission points (transmission point, TP), or transmission reception points (transmission and reception point, TRP), etc., as well as a gNB or transmission points (TRP or TP) in 5G (e.g., NR) systems, an antenna panel of one or a group (including multiple antenna panels) of base stations in 5G systems, or as well as network nodes constituting a gNB or transmission point, such as a Distributed Unit (DU), or a base station in next generation communication 6G systems, etc. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the AN equipment.

The access network may serve the cell. The terminal device may communicate with the cell via transmission resources (e.g., frequency domain resources, or spectrum resources) allocated by the access network device.

3. AMF network element: the method is mainly used for the functions of access control, mobility management, attachment and detachment and the like.

4. SMF network element: the method is mainly used for user plane network element selection, user plane network element redirection, internet protocol (internet protocol, IP) address allocation of terminal equipment and session management in a mobile network, such as session establishment, modification and release and QoS control.

5. UPF network element: the method is mainly used for receiving and forwarding the user plane data. For example, the UPF may receive user plane data from the DN and send the user plane data to the terminal device through the AN device. The UPF may also receive user plane data from the terminal device through the AN device and forward to the DN. The UPF in the session directly connected to the DN through the N6 interface may be referred to as a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA).

6. PCF network element: the method is mainly used for providing services to the 3GPP network, such as interaction with PCF for policy control and the like.

7. AF network element: interaction with the 3GPP core network is primarily supported to provide services, such as influencing data routing decisions, interacting with Policy Control Functions (PCFs), or providing third parties to the network side, etc.

8. UDM network element: the method is mainly used for subscription data management of the UE, and comprises storage and management of the UE identification, access authorization of the UE and the like. 9. Data Network (DN): the method is mainly used for an operator network for providing data services for the UE. Such as the Internet, a third party's service network, an IP Multimedia Services (IMS) network, etc.

In a communication system, a PDU session is established after a UE accesses a network, and a DN is accessed through the PDU session to interact with an application server deployed in the DN. As shown in fig. 1. According to different DNs accessed by the UE, the network can select UPF accessed to the DNs as PSA according to network policy, and access the application server through the N6 interface of the PSA. The application server of the same application can be deployed at a plurality of positions, so that the network can select PSA which is close to the UE and can support the UE to access DN according to the access position of the UE, thereby reducing routing detour and network delay. Typically, these application servers are typically deployed in a multiple access edge computing (MEC) environment. For applications, qoS information of the traffic data flow transmission path needs to be perceived in order to perform corresponding adjustment at the application layer. In some scenarios, the SMF may not be able to directly manage UPFs for some areas, in which case these UPFs may be managed by deploying an intermediate session management function (I-SMF), as shown in fig. 2.

Fig. 2 is another schematic diagram of a network architecture suitable for use in embodiments of the present application. In some scenarios, the SMF may not be able to directly manage the UPF of some areas, so in one possible way, the management of the UPF may be achieved through the I-SMF. As shown in fig. 2, UPF may be managed by inserting an I-SMF in the network architecture. For the description of each network element, reference is made to the description in fig. 1, and no further description is given here.

In the network architecture shown in fig. 1 or fig. 2, the network elements may communicate with each other through AN interface, for example, the UE connects to the AN device through a radio resource control (radio resource control, RRC) protocol, and the UE and the AN device communicate with each other through a Uu interface. Or may refer to the interfaces shown in fig. 1 or fig. 2, and will not be described in detail herein. In addition, the names of interfaces between the network elements in fig. 1 and fig. 2 are only an example, and the names of interfaces in the specific implementation may be other names, which are not specifically limited in this application.

It should be understood that the network architecture applied to the embodiments of the present application is merely an exemplary illustration, and the network architecture to which the embodiments of the present application are applied is not limited to this, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application. In addition, other network elements may be further included in the network architecture shown above, which is not limited thereto.

It should also be understood that AMF, SMF, UPF, PCF, UDM and the like shown in fig. 1 can be understood as network elements for implementing different functions, e.g. can be combined into network slices as desired. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or be virtualized functions instantiated on a platform (for example, a cloud platform), which is not limited to the specific form of the network elements.

It should also be understood that the functions or network elements shown in fig. 1 or fig. 2, such as AMF, SMF, UPF, PCF, UDM, NSSF, AUSF, may be understood as network elements for implementing different functions, for example, may be combined into network slices as needed. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or be virtualized functions instantiated on a platform (for example, a cloud platform), which is not limited to the specific form of the network elements.

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

To facilitate an understanding of the embodiments of the present application, several basic concepts involved in the embodiments of the present application are briefly described. It should be understood that the basic concepts described below are described in the example of the basic concepts specified in the present protocol, but the embodiments of the present application are not limited to be applied to the existing systems. Therefore, the names appearing in the description of the existing system are all functional descriptions, and specific names are not limited, only indicate functions, and can be correspondingly extended to other systems, such as 6G or future communication systems.

1. Protocol data unit (protocol data unit, PDU) session (PDU session): the 5G core network (5G corenetwork,5GC) supports PDU connectivity services. The PDU connection service may refer to a service of exchanging PDU packets between the terminal device and the DN. The PDU connection service is implemented by the terminal device initiating the establishment of a PDU session. After a PDU session is established, a data transmission channel between the terminal and the DN is established. In other words, the PDU session is UE level. Each terminal device may establish one or more PDU sessions.

As previously mentioned, the SMF primary user is responsible for session management in the mobile network. The PDU session can be established, modified or released between the terminal device and the SMF through NAS session management (session management, SM) signaling.

In the embodiment of the present application, one PDU session may be identified by one PDU session identification (PDU session identifier, PDU session ID). Since the PDU session is UE level, each PDU session identity may also correspond to one terminal device.

2. QoS flow (QoS flow): qoS flow is a fine QoS differentiation granularity in a PDU session. In 5G systems, a QoS Flow identifier (QoS Flow identifier, QFI) may be used to identify a QoS Flow. Multiple QoS flows may be included in a PDU session, but the QFI of each QoS flow is different. In other words, one QFI is unique within one PDU session.

Further, the QoS flow corresponding to the service: may refer to a QoS flow for transmitting data for the service. For example, when data of the service is transmitted through a QoS flow in a PDU session, the QoS flow may be referred to as a QoS flow corresponding to the service. Traffic carried by QoS flows: may refer to traffic that is streamed over the QoS.

Further, both QoS files (QoS profile) and candidate QoS files (alternative QoS profile) may be understood as at least one set of QoS parameters. Taking a QoS file as an example, the QoS file may include at least one set of QoS parameters; or at least one QoS parameter set (qossparameter set).

In the present embodiment, qoS files and candidate QoS files (alternative QoS profile) are mentioned a plurality of times, the meaning of which will be understood by those skilled in the art. Specifically, the control plane network element provides at least one candidate QoS file in addition to the QoS file to the access network device, so that the access network device implements QoS of the QoS flow based on the QoS file first, and when QoS of the QoS file cannot be guaranteed, the access network device determines a supportable candidate QoS file from the at least one candidate QoS file to execute the supportable candidate QoS file.

Whether QoS of a QoS flow can be guaranteed, or whether QoS in a QoS file, which may be referred to as a QoS flow, can be guaranteed, specifically whether QoS parameters can be satisfied. For example, qoS of QoS flows cannot be guaranteed, specifically QoS parameters cannot be met, such as guaranteed traffic bit rate (guaranteed flow bit rate, GFBR) cannot be guaranteed (GFBR can no longer be guaranteed); qoS of QoS flows can be guaranteed, and in particular QoS parameters can be met, such as GFBR can be guaranteed (GFBR can be guaranteed again).

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

The communication method provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings. The embodiments provided in the present application may be applied to the network architecture shown in fig. 1 or fig. 2, and are not limited thereto.

Fig. 3 is a schematic diagram of a communication method 300 according to an embodiment of the present application. The method 300 may include the following steps.

The first device sends information of a first candidate QoS file to the control plane network element, where the first candidate QoS file is a candidate QoS file of a first QoS flow that can be supported by the first access network device.

Accordingly, the control plane network element receives information of the first candidate QoS file from the first device.

The information of the first candidate QoS file indicates information related to the first candidate QoS file, or information that can be used to identify the first candidate QoS file, or information that can be used to learn the first candidate QoS file. As an example, the information of the first candidate QoS file may be an identification (reference) of the first candidate QoS file.

The first candidate QoS file is a candidate QoS file of a first QoS flow that can be supported by the first access network device (currently), which may also be referred to as a candidate QoS file of a first QoS flow that can be met by the first access network device (currently), or a candidate QoS file of a first QoS flow that is executed by the first access network device (currently), or a candidate QoS file that is implemented by the first access network device (currently) for the first QoS flow, or a candidate QoS file that is determined by the first access network device (currently) for the QoS of the first QoS flow, or a candidate QoS file that is matched by the first access network device (currently) for the QoS of the first QoS flow, or the like. The first access network device represents the access network device currently serving the terminal device, or the access network device currently accessed by the terminal device.

The control plane network element may be, for example, a network element of a control plane in the core network, and for example, the control plane network element may communicate with a user plane network element and/or an access network device, or may also communicate with a terminal device. As an example, the control plane network element is an SMF.

Wherein the first device may represent a device providing information of candidate QoS files for the control plane network element. As an example, the first device is an access network device (e.g. a first access network device, as well as a second access network device as mentioned below) or a user plane network element.

And 320, the control plane network element sends the first QoS parameters corresponding to the first candidate QoS file to the terminal equipment.

Wherein the first QoS parameter represents some or all of the QoS parameters contained in the first candidate QoS file.

After receiving the information of the first candidate QoS file, the control plane network element determines a QoS parameter corresponding to the first candidate QoS file according to the information of the first candidate QoS file, and further may send the QoS parameter corresponding to the first candidate QoS file to the terminal device.

Based on the embodiment of the application, the first device sends the information of the candidate QoS file of the first QoS flow that can be supported by the first access network device to the control plane network element, and after the control plane network element receives the information of the candidate QoS file of the first QoS flow, the control plane network element sends the QoS parameter corresponding to the first candidate QoS file to the terminal device, so that the terminal device can obtain the QoS parameter corresponding to the candidate QoS file currently being executed by the first access network device.

Optionally, the method 300 further comprises: the first device sends first notification information to the control plane network element, the first notification information notifying that QoS of the first QoS flow cannot be guaranteed. Accordingly, the control plane network element receives the first notification information from the first device.

The first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and may be replaced by: the first notification information notifies that QoS in a QoS file of the first QoS flow cannot be guaranteed. The QoS in the QoS file of the first QoS flow cannot be guaranteed, which may indicate that the QoS in the QoS file of the first QoS flow cannot be guaranteed. In the embodiment of the present application, in the case that QoS in the QoS file of the first QoS flow cannot be guaranteed, the first access network device determines a candidate QoS file (i.e., a first candidate QoS file) that can be currently supported.

The first notification information and the information of the first candidate QoS file may be carried in the same signaling, or may be carried in different signaling, which is not limited.

It will be appreciated that the first notification information described above is an exemplary illustration, and is not limited thereto. For example, after receiving the information of the first candidate QoS file, the control plane network element may learn that the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed) based on the first candidate QoS file, that is, the first candidate QoS file may implicitly notify that the QoS of the first QoS flow cannot be guaranteed.

Optionally, prior to step 310, the method 300 further comprises step 301.

301, the control plane network element sends first indication information to the first device, where the first indication information indicates to send to the control plane network element: congestion information. Wherein the congestion information may represent information related to the first QoS flow. As an example, the congestion information may be a notification of whether QoS of the first QoS flow can be guaranteed, or the congestion information may be information of a candidate QoS file of the first QoS flow that the access network device can support, or the congestion information may be a notification of whether QoS of the first QoS flow can be guaranteed and information of a candidate QoS file of the first QoS flow that the access network device can support. The first device may send information of the first candidate QoS file to the control plane network element based on the first indication information. In one possible implementation, the first indication information is implemented by at least one bit. For example, assuming that whether congestion information is transmitted to the control plane network element is indicated by 1 bit, if the bit is set to "0", it means that congestion information is not transmitted to the control plane network element; if the bit is set to "1", it indicates that congestion information is sent to the control plane network element. It is to be understood that the above is intended to be illustrative, and not restrictive.

It will be appreciated that the implementation of the first indication information is not limited. For example, a specific implementation of the first indication information may be one or more Information Elements (IEs), such as an indication including a direct notification and an indication of repeated notification (or an indication of notification to a control plane). Wherein the indication of direct notification is used for indicating to notify the user plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. Wherein the indication of repeated notification (or the indication of notification to the control plane) is used for indicating the notification to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support.

Several examples are listed below.

Example 1, the first indication information indicates to send to the control plane network element: and a notification of whether the QoS of the first QoS flow can be guaranteed.

Under this example 1, for example, after the first device receives the first indication information, the first device sends information of the first candidate QoS file to the control plane network element based on the first indication information (or in response to the first indication information). For example, the first device knows, based on the first indication information, a notification of whether the QoS of the first QoS flow can be guaranteed or not to be sent to the control plane network element, and therefore, in a case where the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed), the first device determines, by default or based on internal logic, to send the information of the first candidate QoS file to the control plane network element. Wherein the information of the first candidate QoS file may implicitly inform that QoS of the first QoS flow cannot be guaranteed.

In this example 1, for another example, after receiving the first indication information, the first device sends, to the control plane network element, a notification of whether QoS of the first QoS flow can be guaranteed and information of the first candidate QoS file based on the first indication information (or, in response to the first indication information). For example, the first device knows, based on the first indication information, a notification of whether the QoS of the first QoS flow can be guaranteed or not to be sent to the control plane network element, so the first device knows that the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed), sends, to the control plane network element, notification information (i.e., the first notification information) that the QoS of the first QoS flow cannot be guaranteed, and determines, by default or based on internal logic, information of sending the first candidate QoS file to the control plane network element.

In this example 1, for another example, after the first device receives the first indication information, the first device sends, to the control plane network element, a notification of whether QoS of the first QoS flow can be guaranteed based on the first indication information (or in response to the first indication information). For example, the first device knows, based on the first indication information, a notification of whether the QoS of the first QoS flow can be guaranteed or not to be sent to the control plane network element, and therefore, in a case where the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed), the first device sends, to the control plane network element, notification information (i.e., the first notification information) that the QoS of the first QoS flow cannot be guaranteed.

Example 2, the first indication information indicates to send to the control plane network element: information of candidate QoS files of a first QoS flow that the access network device is capable of supporting.

Under this example 2, for example, after the first device receives the first indication information, the first device sends information of the first candidate QoS file to the control plane network element based on the first indication information (or in response to the first indication information). For example, the first device knows, based on the first indication information, to send to the control plane network element a candidate QoS file for the first QoS flow that the access network device can support, and therefore, the first device sends to the control plane network element information for the first candidate QoS file.

In this example 2, for another example, after the first device receives the first indication information, the first device sends, to the control plane network element, a notification of whether QoS of the first QoS flow can be guaranteed and information of the first candidate QoS file based on the first indication information (or, in response to the first indication information). For example, the first device knows, based on the first indication information, information about candidate QoS files of the first QoS flow that the access network device can support to be sent to the control plane network element, so in a case where QoS of the first QoS flow cannot be guaranteed (i.e., qoS in the QoS files of the first QoS flow cannot be guaranteed), the first device sends the information about the first candidate QoS file to the control plane network element, and determines, by default or based on internal logic, to send notification information (i.e., first notification information) to the control plane network element that QoS of the first QoS flow cannot be guaranteed.

Example 3, the first indication information indicates to send to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and the information of the candidate QoS files of the first QoS flow that the access network device can support. The notification of whether the QoS of the first QoS flow can be guaranteed and the information of the candidate QoS file of the first QoS flow that the access network device can support may be indicated by two pieces of information, or may also be indicated by one piece of information, which is not limited.

In this example 3, for example, after receiving the first indication information, the first device sends, to the control plane network element, a notification of whether QoS of the first QoS flow can be guaranteed and information of the first candidate QoS file based on the first indication information (or in response to the first indication information). For example, the first device knows, based on the first indication information, to send to the control plane network element: notification of whether the QoS of the first QoS flow can be guaranteed and information of candidate QoS files of the first QoS flow that the access network device can support, so in the case that the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed), the first device sends to the control plane network element: a notification that QoS of the first QoS flow cannot be guaranteed (i.e., first notification information), and information of candidate QoS files of the first QoS flow that the access network device can support.

In this example 3, for another example, after the first device receives the first indication information, the first device sends information of the first candidate QoS file to the control plane network element based on the first indication information (or in response to the first indication information). For example, the first device knows, based on the first indication information, to send to the control plane network element: the method includes informing whether the QoS of the first QoS flow can be guaranteed and information of the candidate QoS files of the first QoS flow that the access network device can support, so that in a case where the QoS of the first QoS flow cannot be guaranteed (i.e., the QoS in the QoS file of the first QoS flow cannot be guaranteed), the first device sends the information of the candidate QoS files of the first QoS flow that the access network device can support to the control plane network element. Wherein the information of the first candidate QoS file may implicitly inform that QoS of the first QoS flow cannot be guaranteed.

The above mainly lists the case that the QoS of the QoS flow cannot be guaranteed, and it is understood that the case that the QoS of the QoS flow can be guaranteed is similar, and will not be described herein.

In the above three examples, the first device may be an access network device or a user plane network element, which is not limited. Two schemes are described below.

Scheme 1, the first device is an access network device.

Optionally, under this scheme 1, the control plane network element further sends information of at least one candidate QoS file to the access network device, where the at least one candidate QoS file includes the first candidate QoS file. Optionally, under this scheme 1, the control plane network element also sends information of the QoS file to the access network device. If the QoS in the QoS file of the first QoS flow cannot be guaranteed (i.e. the QoS in the QoS file sent by the control plane network element to the access network device cannot be guaranteed), the access network device may determine the first candidate QoS file from the at least one candidate QoS file, so as to support the QoS of the first QoS flow. The first indication information and the information of the at least one candidate QoS file may be carried in the same signaling, or may be carried in different signaling, without limitation.

Under this scheme 1, step 301 may be: the control plane network element sends first indication information to the access network device. At this time, the first indication information indicates to send to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device may also be replaced by: the first indication information indicates the access network equipment to send through the user plane: and sending to the control plane network element in case of a notification of whether the QoS of the first QoS flow can be guaranteed and/or information of a candidate QoS file of the first QoS flow that can be supported by the access network device: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of a candidate QoS file of the first QoS flow that the access network device can support; or may be replaced with: the first indication information indicates the access network device to send to the control plane network element and the user plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. Accordingly, the access network device can learn that the first indication information is sent through the user plane: and sending to the control plane network element in case of a notification of whether the QoS of the first QoS flow can be guaranteed and/or information of a candidate QoS file of the first QoS flow that can be supported by the access network device: the method comprises the steps that a notice of guaranteeing the QoS of a first QoS flow and/or information of candidate QoS files of the first QoS flow which can be supported by access network equipment are sent to a control plane network element and a user plane network element by the access network equipment: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support.

Based on scheme 1, the access network device may send to the user plane network element and the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device is compared with that the access network device only sends to the user plane network element: the control plane network element may obtain the notification whether the QoS of the first QoS flow can be guaranteed, and/or the information of the candidate QoS file of the first QoS flow that the access network device can support: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device, so that the terminal device can obtain the corresponding QoS parameter of the candidate QoS file of the first QoS flow that can be supported by the access network device. Compared to the access network device sending only to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device may enable the user plane network element to obtain: informing whether the QoS of the first QoS flow can be ensured and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment, so that the user plane network element can send to the application network element: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that the access network device can support, so that the application network element can learn the information more quickly. That is, by the scheme of the application, the control plane network element equipment can obtain the information of the candidate QoS file, so that the latest QoS information (namely, the QoS parameter corresponding to the candidate QoS file) is conveniently transmitted to the terminal equipment, and the consistency of QoS execution of the terminal equipment side and the network side is facilitated; and the user plane network element can also obtain the information of the candidate QoS file, so that the information is rapidly transmitted to the application network element, and the efficiency is improved.

With respect to scheme 1, one possible flow is presented later in connection with method 400.

Scheme 2, the first device is a user plane network element.

Under this scenario, step 301 may be: the control plane network element sends first indication information to the user plane network element. At this time, the first indication information indicates to send to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that can be supported by the access network device, where the first indication information indicates that the user plane network element receives: and sending to the control plane network element in case of a notification of whether the QoS of the first QoS flow can be guaranteed and/or information of a candidate QoS file of the first QoS flow that can be supported by the access network device: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. Accordingly, the user plane network element can learn, based on the first indication information, that the user plane network element has received: and sending to the control plane network element in case of a notification of whether the QoS of the first QoS flow can be guaranteed and/or information of a candidate QoS file of the first QoS flow that can be supported by the access network device: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. Optionally, under this scheme 2, the method 300 further includes: the access network device sends to the user plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support.

Based on scheme 2, the user plane network element may send to the control plane network element: the control plane network element may obtain the notification whether the QoS of the first QoS flow can be guaranteed, and/or the information of the candidate QoS file of the first QoS flow that the access network device can support: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device, so that the terminal device can obtain the corresponding QoS parameter of the candidate QoS file of the first QoS flow that can be supported by the access network device.

With respect to scheme 2, a possible flow is given below in connection with method 700.

Further alternatively, the control plane network element sends the first indication information to the first device based on a message (e.g. denoted as message #a), i.e. the control plane network element sends the first indication information to the first device based on an indication of message #a.

One possible implementation way, the information #a is implemented by at least one bit, i.e. the control plane network element sends the first indication information to the first device based on a field of the at least one bit. For example, assuming that whether to transmit the first instruction information to the first device is instructed by 1 bit, if the bit is set to "0", it means that the first instruction information is not transmitted to the first device; if the bit is set to "1", it indicates that the first indication information is transmitted to the first device. It is to be understood that the above is intended to be illustrative, and not restrictive.

In another possible implementation manner, the information #a is a policy rule, that is, the control plane network element sends the first indication information to the first device based on the policy rule. For example, the control plane network element receives a policy rule from the policy control network element, and the control plane network element determines first indication information based on the policy rule, and then sends the first indication information. The policy rules may be, for example, policy charging control (policy and charging control, PCC) rules. It will be appreciated that the rules refer to policy information elements associated with a PDU session or a service data flow, and reference is made to the existing description and is not limited herein. Several possible scenarios are presented below.

In a first possible scenario, the policy rules include the second indication information. Wherein the second indication information indicates to notify the terminal device of QoS parameters of QoS flows that the access network device can support, or the second indication information indicates to send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

Further optionally, if the first device is an access network device, the second indication information indicates to send to a control plane network element: the notification of whether the QoS of the QoS flow can be guaranteed and/or the information of the candidate QoS file of the QoS flow that the access network device can support may be replaced by: the second indication information indicates the access network device to send to the user plane network element and the control plane network element: notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that can be supported by the access network device, etc., and in particular, reference may also be made to the description of the first indication information.

Further optionally, if the first device is a user plane network element, the second indication information indicates to send to the control plane network element: the notification of whether the QoS of the QoS flow can be guaranteed and/or the information of the candidate QoS file of the QoS flow that the access network device can support may be replaced by: the second indication information indicates the user plane network element to send to the control plane network element: notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that can be supported by the access network device, etc., and in particular, reference may also be made to the description of the first indication information.

Example 1, the second indication information indicates that the terminal device is informed of QoS parameters of QoS flows that the access network device can support.

For example, if the QoS parameters of the QoS flows supported by the access network device are not notified to the terminal device by default, the policy rule includes second indication information, that is, based on the second indication information carried in the policy rule, the QoS parameters of the QoS flows of the terminal device supported by the access network device are notified to the terminal device.

The control plane network element determines, based on the second indication information included in the policy rule, to notify the terminal device of QoS parameters of the QoS flows supported by the access network device. Based on the second indication information (or in response to the second indication information), the control plane network element sends first indication information to the first device, the first indication information indicating to send to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. The first device sends information of a first candidate QoS file to the control plane network element based on the first indication information, and the control plane network element sends QoS parameters of QoS flows supported by the access network device, namely QoS parameters corresponding to the first candidate QoS file, to the terminal device based on the information of the first candidate QoS file sent by the first device.

Example 2, the second indication information indicates to send to the control plane network element: and a notification of whether the QoS of the first QoS flow can be guaranteed.

For example, if the default does not send the notification of whether the QoS of the first QoS flow can be guaranteed to the control plane network element, the policy rule includes the second indication information, that is, based on the second indication information carried in the policy rule, the notification of whether the QoS of the first QoS flow can be guaranteed to the control plane network element can be known.

Based on the second indication information (or in response to the second indication information), the control plane network element sends first indication information to the first device, the first indication information indicating to send to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. For example, the first device sends, to the control plane network element, a notification of whether the QoS of the first QoS flow can be guaranteed based on the first indication information, and the control plane network element may learn, based on the notification of whether the QoS of the first QoS flow can be guaranteed, the notification of whether the QoS of the first QoS flow can be guaranteed. For another example, the first device may send the information of the first candidate QoS file to the control plane network element based on the first indication information, and the control plane network element may learn that the QoS of the first QoS flow cannot be guaranteed based on the information of the first candidate QoS file sent by the first device (i.e., the information of the first candidate QoS file may implicitly notify that the QoS of the first QoS flow cannot be guaranteed).

Example 3, the second indication information indicates to send to the control plane network element: information of candidate QoS files of a first QoS flow that the access network device is capable of supporting.

For example, if the default does not send the information of the candidate QoS file of the first QoS flow that can be supported by the access network device to the control plane network element, the policy rule includes second indication information, that is, based on the second indication information carried in the policy rule, the information of the candidate QoS file of the first QoS flow that can be supported by the access network device to the control plane network element may be known.

Based on the second indication information (or in response to the second indication information), the control plane network element sends first indication information to the first device, the first indication information indicating to send to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. For example, the first device sends information of the first candidate QoS file to the control plane network element based on the first indication information.

Example 4, the second indication information indicates to send to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and the information of the candidate QoS files of the first QoS flow that the access network device can support.

For example, if default does not send to the control plane network element: the policy rule includes second indication information, that is, based on the second indication information carried in the policy rule, it can be known that the second indication information is to be sent to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and the information of the candidate QoS files of the first QoS flow that the access network device can support.

Based on the second indication information (or in response to the second indication information), the control plane network element sends first indication information to the first device, the first indication information indicating to send to the control plane network element: a notification of whether the QoS of the first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that the access network device can support. For example, the first device sends a notification that QoS of the first QoS flow cannot be guaranteed and information of candidate QoS files of the first QoS flow that the access network device can support to the control plane network element based on the first indication information. For another example, the first device sends the information of the first candidate QoS file to the control plane network element based on the first indication information, and the control plane network element may learn the information of the first candidate QoS file and learn that the QoS of the first QoS flow cannot be guaranteed (i.e., the information of the first candidate QoS file may implicitly notify that the QoS of the first QoS flow cannot be guaranteed) based on the information of the first candidate QoS file sent by the first device.

In a second possible scenario, the policy rule does not include third indication information, where the third indication information indicates that the QoS parameters of the QoS flows supported by the access network device are not notified to the terminal device. The third indication information indicates that the terminal device is not notified of QoS parameters of QoS flows that can be supported by the access network device, and may be replaced by: the third indication information indicates not to send to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support.

For example, if the QoS parameters of the QoS flows of the terminal device supported by the access network device are notified to the terminal device by default, the third indication information may not be carried in the policy rule, and the third indication information indicates that the QoS parameters of the QoS flows of the terminal device supported by the access network device are not notified to the terminal device. That is, based on that the policy rule does not carry the third indication information, the QoS parameter of the QoS flow of the terminal device supported by the access network device is informed to the terminal device.

Based on the situation, the control plane network element determines, based on the policy rule, that the third indication information is not included, to notify the terminal device of the QoS parameter of the QoS flow supported by the access network device, and therefore, the control plane network element sends the first indication information to the first device, and the first indication information indicates the first device to send the control plane network element a notification whether the QoS of the first QoS flow can be guaranteed. Reference is specifically made to the foregoing description, and no further description is given here.

In a third possible scenario, the policy rule includes the first indication information. In this case, the control plane network element sends the first indication information to the first device based on the first indication information included in the policy rule.

Based on the situation, the control plane network element determines to send the first indication information to the first device based on the first indication information included in the policy rules.

It will be appreciated that the two implementations described above are exemplary illustrations and are not limiting in this regard. For example, the control plane network element sends the first indication information to the first device as predefined by a standard.

It will also be appreciated that the specific manner in which policy rules are determined with respect to the policy control network element is not limited.

In a possible scenario, the application network element sends fifth indication information to the policy control network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the fifth indication information indicates that the access network device sends to the user plane network element and the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In this case, the policy control network element may send, to the control plane network element, second indication information based on the fifth indication information (or in response to the fifth indication information), the second indication information indicating to notify the terminal device of QoS parameters of QoS flows that the access network device can support, or the second indication information indicating that the access network device sends to the user plane network element and the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In particular, the second indication information may be carried in policy rules. Or in this case, the policy control network element sends policy rules to the control plane network element, where the policy rules do not include third indication information, and the third indication information indicates that QoS parameters of QoS flows that can be supported by the access network device are not notified to the terminal device.

Another possible scenario is that the application network element sends fifth indication information to the policy control network element, where the fifth indication information indicates to notify the terminal device of QoS parameters of QoS flows that the access network device can support, or the fifth indication information indicates to the user plane network element to send: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In this case, the policy control network element may send, to the control plane network element, second indication information based on the fifth indication information (or in response to the fifth indication information), the second indication information indicating to notify the terminal device of QoS parameters of QoS flows that the access network device can support, or the second indication information indicating that the user plane network element sends to the control plane network element: a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. In particular, the second indication information may be carried in policy rules. Or in this case, the policy control network element sends policy rules to the control plane network element, where the policy rules do not include third indication information, and the third indication information indicates that QoS parameters of QoS flows that can be supported by the access network device are not notified to the terminal device.

Optionally, after step 320, the method 300 further includes: the control surface network element receives second notification information from the first device, and the second notification information notifies that the QoS of the first QoS flow can be ensured; the control plane network element sends a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment.

Wherein the second QoS parameter represents some or all of the QoS parameters included in the QoS file of the first QoS flow.

Wherein, the second notification information notifies that the QoS of the first QoS flow can be guaranteed, and may be replaced by: the second notification information notifies the QoS in the QoS file of the first QoS flow that can be guaranteed. That is, the QoS in the QoS file of the first QoS flow can be guaranteed.

Taking the first device as an access network device as an example, the method 300 optionally further includes: the control plane network element sends the QoS file of the first QoS flow to the first access network device. The QoS file of the first QoS flow, the information of the at least one candidate QoS file, and the first indication information may be carried in the same signaling, or may be carried in different signaling, without limitation. When the first access network device determines that the QoS in the QoS file of the first QoS flow can be guaranteed again, the first access network device sends second notification information to the control plane network element, where the second notification information notifies that the QoS of the first QoS flow can be guaranteed, that is, that the QoS in the QoS file of the first QoS flow can be guaranteed. After receiving the second notification information, the control surface network element knows that the QoS in the QoS file of the first QoS flow can be guaranteed, and therefore, the control surface network element sends the second QoS parameters corresponding to the QoS file of the first QoS flow to the terminal equipment. That is, the QoS in the QoS file of the first QoS flow can be guaranteed again, the first access network device may execute the QoS file and notify the control plane network element, and the control plane network element notifies the terminal device of the second QoS parameter corresponding to the QoS file, so that both the first access network device and the terminal device can communicate based on the QoS parameter of the QoS file.

As yet another example, taking the first device as a user plane network element, optionally, the method 300 further includes: the first access network device sends second notification information to the user plane network element. For example, when the first access network device determines that the QoS in the QoS file of the first QoS flow can be guaranteed again, the first access network device sends second notification information to the user plane network element, where the second notification information notifies that the QoS of the first QoS flow can be guaranteed, that is, that the QoS in the QoS file of the first QoS flow can be guaranteed. The user plane network element sends second notification information to the control plane network element, for example, the user plane network element sends the second notification information to the control plane network element based on the first indication information. After receiving the second notification information, the control surface network element knows that the QoS in the QoS file of the first QoS flow can be guaranteed, and therefore, the control surface network element sends the second QoS parameters corresponding to the QoS file of the first QoS flow to the terminal equipment. That is, the QoS in the QoS file of the first QoS flow can be guaranteed again, the first access network device can execute the QoS file and notify the user plane network element, the user plane network element notifies the control plane network element that the first access network device can execute the QoS file, and the control plane network element notifies the terminal device of the second QoS parameter corresponding to the QoS file, so that the first access network device and the terminal device can both communicate based on the QoS parameter of the QoS file.

Optionally, after step 320, the method 300 further includes: the control surface network element receives third notification information from the second access network device, and the third notification information notifies that the QoS of the first QoS flow can be ensured; the control surface network element sends a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

After the terminal device moves, a network handover may occur, for example, an Xn-based Inter NG-RAN handover (Xn-based Inter NG-RAN handover) or an NG-RAN node N2-based handover. In the embodiment of the present application, it is assumed that the terminal device is switched from the first access network device to the second access network device, that is, the first access network device provides a service for the terminal device before the switching, and the second access network device provides a service for the terminal device after the switching.

Wherein, the third notification information informs that the QoS of the first QoS flow can be guaranteed, and may be replaced by: the third notification information notifies that QoS in the QoS file of the first QoS flow can be guaranteed. That is, the QoS in the QoS file of the first QoS flow can be guaranteed.

In one possible implementation, the third notification information directly informs (or explicitly informs) that the QoS of the first QoS flow can be guaranteed. That is, the control plane network element can directly know that the QoS in the QoS file of the first QoS flow can be guaranteed based on the third notification information, so that the control plane network element sends the second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal device.

Optionally, the second access network device further sends at least one QoS flow identifier accepted by the second access network device to the control plane network element, where the at least one QoS flow identifier includes an identifier of the first QoS flow. Based on this, the control plane network element may learn that the QoS flows accepted by the second access network device include the first QoS flow.

Optionally, after step 320, the method 300 further includes: the control surface network element receives fourth known information from the second access network device and information of a second candidate QoS file, wherein the fourth known information informs that the QoS of the first QoS flow cannot be guaranteed, and the second candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the second access network device; and the control surface network element sends a third QoS parameter corresponding to the second candidate QoS file to the terminal equipment.

Wherein the third QoS parameter represents some or all of the QoS parameters included in the second candidate QoS file for the first QoS flow.

Wherein, the fourth notification information informs that the QoS of the first QoS flow cannot be guaranteed, and may be replaced by: the fourth notification information notifies that QoS in the QoS file of the first QoS flow cannot be guaranteed.

In one possible implementation, the fourth notification information directly notifies (or explicitly notifies) that the QoS of the first QoS flow cannot be guaranteed. For example, the control plane network element may directly learn, based on the fourth notification information, that QoS in the QoS file cannot be guaranteed, and therefore, the control plane network element sends, to the terminal device, a third QoS parameter corresponding to the second candidate QoS file of the first QoS flow.

Further optionally, the first access network device sends fourth indication information to the second access network device. The fourth indication information may be determined according to the first indication information, i.e. the function of the fourth indication information is the same as the function of the first indication information, e.g. the fourth indication information indicates that the fourth indication information is sent to the control plane network element: the notification of whether the QoS of the first QoS flow can be guaranteed and/or the information of the candidate QoS file of the first QoS flow that can be supported by the access network device are not described in detail. For example, the second access network device determines to send third notification information to the control plane network element based on the fourth indication information. For another example, the second access network device determines to send fourth notification information and information of the second candidate QoS file to the control plane network element based on the fourth indication information.

It will be appreciated that the fourth indication information and the first indication information are functionally identical, but are here named fourth indication information and first indication information, respectively, in view of the possible forms of information and the fact that the devices transmitting information and receiving information may be different. It is understood that the naming thereof is not limiting to the scope of the present application.

As described above, after the terminal device moves, a network handover may occur, and if the terminal device is handed over from the first access network device to the second access network device, in this scenario, the second access network device or the user plane network element may determine whether the QoS flow information is updated. Wherein, whether the information of the QoS flow is updated or not may include, for example: whether the guarantee condition of QoS in the QoS file of the QoS flow changes and/or whether the candidate QoS file corresponding to the QoS flow changes. Two possible schemes are described below.

In a first possible scenario, the second access network device determines whether the information of the QoS flow changes.

Optionally, the second access network device receives information of a first candidate QoS file from the first access network device, where the first candidate QoS file is a candidate QoS file of a first QoS flow that the first access network device can support; in the case that the QoS of the first QoS flow cannot be guaranteed, and the candidate QoS file of the first QoS flow that can be supported by the second access network device does not include the first candidate QoS file, the second access network device sends fourth notification information and information of the second candidate QoS file to the control plane network element, where the second candidate QoS file is the candidate QoS file of the first QoS flow that can be supported by the second access network device, and the fourth notification information notifies that the QoS of the first QoS flow cannot be guaranteed; and under the condition that the QoS of the first QoS flow can be ensured, the second access network equipment sends third notification information to the control surface network element, and the third notification information notifies that the QoS of the first QoS flow can be ensured.

In one possible scenario, the second access network device determines that the guarantee condition of QoS in the QoS file of the first QoS flow changes. Specifically, the second access network device determines that the QoS in the QoS file of the first QoS flow can be guaranteed again, so the second access network device sends third notification information to the control plane network element, and the third notification information notifies that the QoS in the QoS file of the first QoS flow can be guaranteed. After receiving the third notification information, the control plane network element may send QoS parameters corresponding to the QoS file of the first QoS flow to the terminal device. Further optionally, the second access network device sends a sixth notification message to the user plane network element, where the sixth notification message notifies that QoS of the first QoS flow can be guaranteed.

In another possible scenario, the second access network device determines that the corresponding candidate QoS file for the first QoS flow changes. Specifically, if the candidate QoS file of the first QoS flow that the second access network device is capable of supporting does not include the first candidate QoS file, the second access network device may determine a corresponding candidate QoS file for the first QoS flow. The second access network device sends fourth notification information and information of the second candidate QoS file to the control plane network element, assuming that the candidate QoS file of the first QoS flow that can be supported by the second access network device is the second candidate QoS file. After receiving the fourth known information and the information of the second candidate QoS file, the control plane network element may send QoS parameters corresponding to the second candidate QoS file to the terminal device. Further optionally, the second access network device sends fifth notification information to the user plane network element, where the fifth notification information notifies that QoS of the first QoS flow cannot be guaranteed.

It will be appreciated that the functions of the fifth notification information and the fourth notification information are the same, but are denominated herein as the fifth notification information and the fourth notification information, respectively, in view of the fact that the network elements receiving the fifth notification information and the fourth notification information are different. It is understood that the naming thereof is not limiting to the scope of the present application. The sixth notification information is similar to the third notification information, and will not be described here.

With respect to the first possible scenario, details are described later in connection with method 900.

In a second possible scenario, the user plane network element determines whether the information of the QoS flow changes.

Optionally, the user plane network element receives information of at least one QoS flow accepted by the second access network device from the second access network device, where the at least one QoS flow includes the first QoS flow; the user plane network element judges whether the QoS information of the first QoS flow is updated or not based on the information of at least one QoS flow accepted by the second access network device and the information of the first candidate QoS file received previously from the first access network device. Further optionally, the user plane network element receives first notification information from the first access network device and information of the first candidate QoS file, where the first notification information notifies that QoS of the first QoS flow cannot be guaranteed.

In one possible scenario, the user plane network element determines that the guarantee condition of QoS in the QoS file of the first QoS flow changes. For example, if the information of at least one QoS flow received by the user plane network element from the second access network device by the second access network device includes the identifier of the first QoS flow, the user plane network element determines that QoS in the QoS file of the first QoS flow can be guaranteed again. In this case, the information of the at least one QoS flow accepted by the second access network device includes an identification of the first QoS flow, which may implicitly indicate that QoS in the QoS file of the first QoS flow can be guaranteed. Optionally, the user plane network element sends second notification information to the control plane network element, where the second notification information notifies that QoS in the QoS file of the first QoS flow can be guaranteed. After receiving the second notification information, the control plane network element may send QoS parameters corresponding to the QoS file of the first QoS flow to the terminal device.

The foregoing is illustrative, and is not limiting.

For example, the information of the at least one QoS flow accepted by the second access network device includes an identification of the first QoS flow and does not include a candidate QoS file corresponding to the first QoS flow, which may implicitly indicate that QoS in the QoS file of the first QoS flow can be guaranteed. Based on the information of the at least one QoS flow, the user plane network element determines that the QoS information of the first QoS flow is updated, that is, the QoS in the QoS file of the first QoS flow cannot be guaranteed to be guaranteed.

For another example, the information of the at least one QoS flow accepted by the second access network device includes an identification of the first QoS flow and sixth notification information notifying that QoS of the first QoS flow can be guaranteed. The user plane network element can identify the first QoS flow based on the identifier of the first QoS flow, and determine that the QoS information of the first QoS flow is updated according to the sixth notification information, that is, the QoS in the QoS file of the first QoS flow cannot be guaranteed to be guaranteed. Another possible scenario is that the user plane network element determines that the corresponding candidate QoS file of the first QoS flow changes. For example, if the information of at least one QoS flow received by the user plane network element from the second access network device by the second access network device includes the identifier of the first QoS flow and the QoS candidate file corresponding to the first QoS flow, and the QoS candidate file corresponding to the first QoS flow is the second QoS candidate file, the user plane network element determines that the candidate QoS file corresponding to the first QoS flow changes, that is, changes from the first candidate QoS file to the second candidate QoS file. Optionally, the user plane network element sends the information of the second candidate QoS file to the control plane network element. After receiving the information of the second candidate QoS file, the control plane network element may send QoS parameters corresponding to the second candidate QoS file to the terminal device.

With respect to the second possible scenario, details are described later in connection with method 800.

For ease of understanding, the embodiments of the present application will be described in the following exemplary embodiments with reference to fig. 4 to fig. 9, where the access network device is assumed to be a RAN, the user plane network element is a local PSA (L-PSA), the control plane network element is an SMF, and the first indication information is a duplicate notification indication. In addition, for brevity, description will be given by taking, as an example, a notification in which a duplicate notification instruction indicates whether or not transmission of QoS flows through a user plane and a control plane can be guaranteed. It will be appreciated that the notification indicating whether or not the QoS flow can be guaranteed by the user plane and the control plane may be replaced by a notification indicating that: the duplicate notification indication is used to indicate transmission over the user plane and the control plane: notification of whether QoS flows can be guaranteed and/or information of candidate QoS files of supported QoS flows, specific reference may be made to the relevant description of the first indication information in method 300. In the following embodiments, it is mainly described as an example of whether or not the GFBR of the QoS flow can be guaranteed for the sake of understanding, and it is understood that whether or not the GFBR of the QoS flow can be guaranteed may be replaced with whether or not the QoS of the QoS flow can be guaranteed. The steps involved therein may be referred to in particular as described above.

Fig. 4 is a schematic flow chart of a communication method 400 provided in an embodiment of the present application. The method 400 may be applied to scheme 1 in the method 300 described above, i.e., a scheme in which the RAN sends information of candidate QoS files to the control plane network element. The method 400 may include the following steps.

401, pdu session establishment procedure (PDU session establishment procedure).

For example, the UE initiates establishment of a PDU session, the network selects a PSA for the PDU, and the network assigns an address to the UE. The UE may access an application server in the DN network through the established PDU session. It will be appreciated that after the PDU session is established, that is, the data transmission channels of the terminal device and DN are established.

The foregoing is merely exemplary, and the embodiments of the present application are not limited to step 401. For example, step 401 may refer to the prior art or later occurring means.

The AF may send UE notification (UE notification) information (i.e., an example of fifth indication information) to the PCF, the UE notification information indicating to notify the UE of QoS parameters of QoS flows that the RAN can support, or the UE notification information indicating to instruct the RAN to send to a user plane element (e.g., L-PSA) and a control plane element (e.g., SMF): a notification of whether QoS of the QoS flow can be guaranteed, and/or information of candidate QoS files of the QoS flow that the access network device can support. As an example, the AF may send UE notification information to the PCF via the NEF, as in steps 402 and 403.

402, the af sends a request message #1 to the NEF.

The request message #1 is used for requesting the network to perform QoS guarantee on an application accessed by the UE. As an example, the Request message #1 may be an AF session establishment Request (nnef_afsessionwithqos_create Request) message with QoS for the Nnef interface.

Optionally, the request message #1 includes service information, information for subscribing to network congestion information notification, UE notification information, and a direct notification indication. The following will briefly describe each information.

1. The service information may represent information related to a service.

By way of example, the traffic information may include description information (e.g., quintuple information, as well as filters for matching one or more traffic data flows, one flow identification for each traffic data flow filter) and QoS requirements (QoS requirements) for the traffic data flow (or for the traffic data flow-bound QoS flow, or simply QoS flow).

The five-tuple information generally refers to a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol.

Wherein the QoS requirements comprise QoS parameters corresponding to the traffic data flow, i.e. the requested QoS parameters corresponding to the traffic data flow.

Optionally, the traffic information further comprises at least one candidate QoS requirement (alternative QoS requirement). The candidate QoS requirements may be mapped by the network into candidate QoS files. That is, the candidate QoS file corresponding to the candidate QoS requirement may be learned based on the candidate QoS requirement, or the candidate QoS requirement corresponding to the candidate QoS file may be learned based on the candidate QoS file. It is understood that the number of candidate QoS requirements herein may be greater than or equal to 1, i.e., the number of candidate QoS files may be greater than or equal to 1.

Similarly, a candidate QoS requirement represents a QoS parameter of a candidate corresponding to a traffic data flow, i.e., a requested QoS parameter of a candidate corresponding to the traffic data flow. For example, if the QoS requirements of a traffic data flow cannot be guaranteed, the RAN may select from among the candidate QoS files, one of the candidate QoS files that matches the QoS implemented for that traffic data flow.

2. The information subscribed to the network congestion information notification may represent information related to the network congestion information.

As an example, the information of subscribing to the network congestion information notification (i.e., the notification of subscribing to whether the QoS requirements of the service data flows can be guaranteed) includes: the event identifies and notifies endpoint1a (notification endpoint1 a). The following will briefly describe each information.

1) notification endpoint1a includes a destination address for receiving event notifications, which may be, for example, destination notification address1a (notification target address1 a), or notification target address a and notification-related ID1a (notification correlation Id1 a).

2) The event identification includes: qoS notification control (QoS notification control) indication.

Therein QoS notification control indicates a QoS flow applicable to guaranteed bit rate (guaranteed bit rate, GBR), indicating whether the network (e.g. RAN) reports the QoS parameters of an AF request can be guaranteed. For example, GFBR that reports the QoS flows to which the traffic data flows are bound cannot be guaranteed (GFBR can no longer be guaranteed) (i.e., qoS of the QoS flows cannot be guaranteed) or GFBR can be guaranteed (GFBR can be guaranteed) (i.e., qoS of the QoS flows can be guaranteed). If the request message #1 further includes a candidate QoS requirement, when the RAN cannot guarantee GFBR, the RAN may report the identifier corresponding to the candidate QoS file that can be currently supported when reporting the indication of GFBR can no longer be guaranteed, and then map the identifier corresponding to the candidate QoS requirement to the network and notify the AF. So that the AF can know the QoS currently guaranteed by the RAN.

3. Direct notification indication: indicating to report congestion information through the user plane network element. Wherein the congestion information represents congestion information related to event identification in information subscribed to network congestion information notification. As an example, the congestion information may include: whether QoS of the service data flow can be guaranteed (i.e., qoS of the QoS flow cannot be guaranteed), candidate QoS files matched for QoS implemented by the service data flow (i.e., candidate QoS files of the QoS flow that the RAN can support in the case that QoS of the QoS flow cannot be guaranteed), and so on.

4. UE notification information characterizing whether to notify QoS parameters of QoS flows of the UE (or matched, executed, determined, implemented, selected) that are currently supported by the RAN, such as QoS parameters corresponding to candidate QoS files characterizing QoS flows of the UE that are currently supported by the RAN.

One possible scenario, if the QoS parameters of the QoS flows of the UE currently supported by the RAN are not to be notified by default, may carry in the request message #1 an indication information #a characterizing the QoS parameters of the QoS flows of the UE to be notified to the UE currently supported by the RAN. That is, based on the indication information #a carried in the request message #1, the QoS parameters of the QoS flow of the UE to be notified to the UE supported by the current RAN can be known.

In another possible scenario, if the QoS parameters of the QoS flows of the UE supported by the UE currently RAN are to be notified by default, the request message #1 may not carry the indication information #b (e.g., disable UE notification), which indicates that the QoS parameters of the QoS flows of the UE supported by the UE currently RAN are not to be notified. That is, based on the request message #1 not carrying the indication information #b, the QoS parameters of the QoS flows of the UE supported by the current RAN may be known to notify the UE.

403, NEF sends request message #2 to PCF.

The request message #2 includes information included in the request message #1. For convenience of description, information included in the request message #1 is denoted as information #1. That is, in step 403, the NEF sends information #1 to the PCF. The following is a description of two architectures.

In the architecture shown in fig. 5, the AF may communicate with the NEF, e.g., the L-PSA may send information to the AF over the N4a interface, reporting QoS information.

In the architecture shown in FIG. 6, a local NEF (L-NEF) may be deployed at the local data center, the L-NEF may communicate with the AF over an N33 interface, the L-NEF may communicate with the L-PSA over an N4a interface, and the L-NEF may communicate with the PCF over an N6 interface.

One possible scenario, taking the architecture shown in fig. 5 as an example, the NEF acquires the address of the PCF by interacting with the BSF, and then sends information #1 to the PCF. For example, the NEF sends an Npcf interface policy authorization_creation Request (npcf_policy authorization_create Request) message to the PCF, including information #1.

In another possible scenario, taking the architecture shown in FIG. 6 as an example, L-NEF determines notification endpoint b and saves notification endpoint b and notification endpoint a correspondences. The L-NEF acquires the address of the PCF by interacting with the BSF, and then sends information #1 to the PCF. For example, the NEF sends an Npcf_PolicyAuthorization_Create request message to the PCF, including information #1. It should be noted that, in this case, in the step 403, the information #1 includes notification endpoint b, that is, the notification endpoint1a received in the step 402 is replaced with notification endpoint1b based on the correspondence between notification endpoint b and notification endpoint1 a. notification endpoint1b may include the target notification address1b (notification target address1 b), or notification endpoint1b may include notification target address1b and notification-related ID1b (notification correlation Id1 b).

404, the pcf sends a response message to the NEF requesting message # 2.

After receiving the request message #2, the PCF may save the information #1 included in the request message #2 and return a response message to the request message #2 to the NEF. For example, the Request message #2 in step 403 is an npcf_policy authorization_create Request message, and correspondingly, the Response message of the Request message #2 in step 404 is an Npcf interface policy authorization setup Response (npcf_policy authorization_create Response) message.

The nef sends a response message to the AF requesting message 1 405.

After receiving the PCF's response, the NEF may send a response message to the AF requesting message 1. For example, the Request message #1 in step 402 is an nnef_afsession withqos_create Request message, and correspondingly, the Response message of the Request message #1 in step 405 is an AF session establishment Response (nnef_afsession withqos_create Response) message with QoS on the Nnef interface.

406, the PCF formulates PCC rules.

The PCF makes policy decisions based on the received information #1, making PCC rules for the PDU session established in step 401.

As an example, the PCC rules may include: qoS parameters authorized according to traffic information (i.e., qoS parameters determined based on QoS requirements in the traffic information), information subscribing to network congestion information notification, a set of candidate QoS parameters (alternative QoSparameter set), correspondence. Wherein the correspondence represents the correspondence of the candidate QoS requirement identifier and the alternative QoSparameter set identifier.

The information for subscribing to the network congestion information notification comprises: (1) event identification; (2) notification endpoint1a (as in the architecture of fig. 5) or notification endpoint a (as in the architecture of fig. 6).

Wherein alternative QoSparameter set may be PCF determined. Specifically, if the candidate QoS requirement is carried in step 402, i.e. the candidate QoS requirement is included in the information #1, the PCF determines alternative QoSparameter set corresponding to the candidate QoS requirement for the candidate QoS requirement, and the PCC rule includes alternative QoSparameter set. Optionally, the PCC rule may further include a correspondence between the candidate QoS requirement identifier and the alternative QoSparameter set identifier.

If the PCF receives the UE notification indication in step 403, the PCF may indicate to the SMF the QoS parameters of the QoS flow of the UE supported by the UE currently RAN, i.e., the PCF determines, according to the UE notification indication, the QoS parameters of the QoS flow of the UE to be notified by the UE currently RAN, thereby indicating to the SMF the QoS parameters of the QoS flow of the UE supported by the UE currently RAN. Therefore, the SMF can inform the RAN of the guaranteed QoS flow through the control plane and the user plane, and after receiving the guaranteed QoS flow reported by the RAN, the SMF can inform the UE of the QoS parameters of the QoS flow of the UE supported by the current RAN. The method for indicating the QoS parameters of the QoS flow of the UE supported by the current RAN by the PCF to the SMF comprises the following steps: the PCF sends PCC rules to the SMF, wherein the PCC rules comprise any one of the following: (a) repeating the notification indication; or (b) direct notification indication and second indication information; or (c) a direct notification indication.

In case (a), the PCC rule includes a duplicate notification indication.

The notification indication is repeated, which may indicate that a notification of whether the QoS flow can be guaranteed is to be reported through the control plane and the user plane, that is, a notification of whether the QoS flow can be guaranteed is to be sent to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF). For example, if the UE notification information and the direct notification indication are carried in step 402, that is, the UE notification information and the direct notification indication are included in the information #1, the RAN indicates whether the RAN is to report the guaranteed notification to the AF through the user plane (or whether the L-PSA directly reports the guaranteed notification to the AF), and the UE needs to know the QoS parameters of the QoS flows supported by the current RAN, so the PCF may include the repeated notification indication in the PCC rule to indicate whether the RAN is to send the guaranteed notification to the user plane (e.g., L-PSA) and the control plane (e.g., SMF).

It will be appreciated that the duplicate notification indicator is illustrative and not limiting. For example, the PCC rule includes an indication information, where the indication information indicates whether a notification that can be guaranteed is to be reported through the control plane; or the indication information indicates QoS parameters of QoS flows of UEs to be supported by the current RAN to be reported through the control plane.

In case (b), the PCC rule includes a direct notification indication and second indication information.

If the direct notification indication and the indication information #a are carried in step 402, that is, the information #1 includes the UE notification information and the direct notification indication, the PCF includes the direct notification indication and the second indication information in the PCC rule. The SMF may determine, in combination with the direct notification indication and the second indication information in the PCC rule, that the RAN is to send a notification to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF) whether the QoS flow can be guaranteed. The instruction information #a and the second instruction information have the same function, and the instruction information #a and the second instruction information are named differently because the sender and the receiver of the instruction information #a and the second instruction information are different. For the second indication information, reference may be made to the related description in the foregoing method 300, which is not repeated here.

In case (c), the PCC rule includes a direct notification indication.

If the direct notification indication is carried and the indication information #b is not carried in step 402, that is, the information #1 includes the direct notification indication and the indication information #b is not included, the PCF includes the direct notification indication and the third indication information is not included in the PCC rule. The SMF may determine, according to the direct notification indication and the PCC rule not including the third indication information, that the RAN is to send a notification to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF) that the QoS flow can be guaranteed. The instruction information #b and the third instruction information have the same function, and the instruction information #b and the third instruction information are named differently because the sender and the receiver of the instruction information #b and the third instruction information are different. Regarding the description of the third indication information, reference may be made to the description of the third indication information in the method 300, which is not repeated here.

It may be appreciated that, according to the AF request, the PCF may formulate a PCC rule for each filter and a request parameter of each service data flow, and each PCC rule may include a flow identifier corresponding to the filter, so as to identify a service data flow to which the PCC rule is applicable. It will be appreciated that the rules refer to policy information elements associated with a PDU session or a service data flow, and reference is made to the existing description and is not limited herein.

407, the PCF sends PCC rules to the SMF.

The PCF sends PCC rules to the SMF corresponding to the PDU session established in step 401.

In one possible implementation, the PCF may send a session management policy control update request (npcf_smplicycontrol_ UpdateNotify Request) message to the SMF, where the message contains information of the PCC rule.

At 408, the smf sends an acknowledgement message to the PCF.

After the SMF installs the PCC rules (or binds PCC rules), an acknowledgement message may be returned to the PCF.

In one possible implementation, the SMF may send a session management policy control update response (npcf_smpolicy control_ UpdateNotify Response) message to the PCF.

After receiving the indication from the PCF (i.e., PCC rule), the SMF may send a duplicate notification indication to the RAN to cause the RAN to send a notification to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF) of whether the QoS flow can be guaranteed. Optionally, the SMF may also send information of QoS files and information of candidate QoS files to the RAN. As an example, the SMF may send information to the RAN through the AMF as in steps 409 and 410.

409, the smf sends a request message #3 to the AMF.

The SMF may determine to create or modify a QoS flow according to PCC rules and send request message #3 indicating information related to the QoS flow.

Taking the SMF determination to create a QoS flow as an example, the SMF assigns a QFI (assumed to be QFI 1) to the QoS flow. The SMF sends a request message #3 to the AMF, the request message #3 including: QFI (i.e., QFI 1), qoS notification control indication, qoS file information (i.e., information of QoS file of QoS flow corresponding to QFI 1), candidate QoS file information (i.e., information of candidate QoS file of QoS flow corresponding to QFI 1), and duplicate notification indication. Wherein the SMF may determine that the duplicate notification indication is included in the request message #3 according to any one of the following cases (a), (b), or (c).

In a possible implementation, in step 409, the SMF sends a Namf interface Communication N1N2message transmission request (namf_communication_n1n MessageTransfer Request) message to the AMF.

410, the amf sends the information in request message #3 to the RAN.

That is, in step 410, the AMF interacts with the RAN, and the AMF transmits the information received in step 409 to the RAN.

411, the amf sends a response message to the SMF requesting message #3.

In a possible implementation, in step 409, the SMF sends a namf_communication_n1n2MessageTransfer Request message to the AMF, and in step 411, the AMF sends a Namf interface Communication N1N2message transfer response (namf_communication_n1n2 MessageTransfer Response) message to the SMF.

412, an N4 session modification is made between the smf and the L-PSA.

For example, the SMF sends an N4 session modification request (N4 session modification request) message to the L-PSA, and the L-PSA sends an N4 session modification response (N4 session modification response) message to the SMF. Among these, the N4 session modification request may include, but is not limited to: QFI1, the filter corresponding to QFI1 (e.g., denoted as filter 1), the flow identification corresponding to QFI1 (e.g., denoted as flow identification 1), qoS notification control indication, correspondence (i.e., correspondence of candidate QoS requirement identifications and alternative QoSparameter set identifications), notification endpoint1a (e.g., under the fig. 5 architecture), or notification endpoint1a (e.g., under the fig. 6 architecture).

413, in case the QoS of the QoS file of the QoS flow cannot be guaranteed, the RAN determines that the candidate QoS file of the supported QoS flow is the candidate QoS file #1.

In a possible case, after the RAN receives the QoS file of the QoS flow corresponding to QFI1 in step 410, the RAN executes the QoS file. When the QoS of the QoS file of the QoS flow cannot be guaranteed, the RAN determines a candidate QoS file to which the QoS that the QoS flow can support (or implement) matches. For example, during the execution of the QoS file of the QoS flow corresponding to QFI1, the RAN detects that the GFBR of the QoS flow corresponding to QFI1 changes from being able to be secured, so the RAN determines a candidate QoS file to which the QoS that the QoS flow is able to support (or implement) matches. Specifically, the RAN may determine, from among the candidate QoS files provided by the SMF (i.e., the candidate QoS files in the request message # 3), a candidate QoS file to which the QoS of the QoS flow that can be supported matches. For ease of description, the candidate QoS file determined by the RAN will be denoted as candidate QoS file #1.

In another possible scenario, after the RAN receives the QoS file of the QoS flow corresponding to QFI1 in step 410, it determines (or otherwise detects) whether the QoS file of the QoS flow corresponding to QFI1 can be guaranteed. If the RAN determines that the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed, the RAN may determine that the QoS flow can support (or implement) the QoS that matches the candidate QoS file. Specifically, the RAN may determine, from among the candidate QoS files provided by the SMF (i.e., the candidate QoS files in the request message # 3), a candidate QoS file that can be supported for which the QoS of the QoS flow matches, e.g., denoted as candidate QoS file #1.

After the RAN determines that the QoS file of the QoS flow corresponding to the QFI1 cannot be guaranteed, and determines that the candidate QoS file of the supported QoS flow is the candidate QoS file #1, the RAN determines, according to the repetition indication information, a notification that whether the QoS flow can be guaranteed or not to send to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF). The RAN sends a notification to the user plane network element whether the QoS flow can be guaranteed, step 414.

The ran sends information of candidate QoS file #1 to the L-PSA 414.

For example, the RAN may send information of candidate QoS file #1 (e.g., an identification of candidate QoS file # 1) to the L-PSA according to the duplicate notification indication received in step 410.

The RAN may also send to the L-PSA in step 414: QFI1, cannot guarantee the indication information of GFBR (i.e., qoS in QoS file of QoS flow cannot be guaranteed). For example, the RAN sends a packet to the L-PSA, where the packet includes: QFI1, indication information (an example of first notification information) that cannot guarantee GFBR, and identification of candidate QoS file # 1.

415, the l-PSA sends information of the candidate QoS requirements corresponding to the candidate QoS file #1 to the AF.

In the first possible scenario, the L-PSA determines the corresponding notification endpoint a from the received packet and the candidate QoS requirement corresponding to the candidate QoS file #1 (e.g. denoted as candidate QoS requirement # 1) from the identification of the candidate QoS file #1, and sends the information of the candidate QoS requirement #1 (e.g. the identification of the candidate QoS requirement # 1) to the AF. Optionally, the L-PSA also sends other information received in step 414 to the AF. The L-PSA may also determine from the received data packets the filter 1 or flow identification 1 of the traffic data flow, and the L-PSA includes the filter 1 or flow identification 1 in the message sent to the AF to determine which GFBR of the traffic data flow cannot be guaranteed or can be guaranteed to the AF.

In a second possible scenario, the L-PSA determines the corresponding notification endpoint b from the received packet and the candidate QoS requirement #1 corresponding to the candidate QoS file #1 from the identification of the candidate QoS file #1, and sends the information of the candidate QoS requirement #1 (e.g. the identification of the candidate QoS requirement # 1) to the NEF. Optionally, the L-PSA also sends other information received in step 414 to the NEF. The L-PSA may also determine filter 1 or flow identification 1 of the traffic data flow from the received data packet, and the L-PSA includes filter 1 or flow identification 1 in the message sent to the NEF.

In the second possible scenario described above, the NEF further determines notification endpoint a according to notification endpoint b and sends the information received by the NEF from the L-PSA to the AF. Furthermore, if the NEF receives the filter 1 from the L-PSA, the NEF determines the flow id 1 according to the filter 1, and includes the flow id 1 in the message sent to the AF; if the NEF receives filter 1 from the L-PSA, the message sent by the NEF to the AF also includes flow identification 1.

After the RAN determines that the QoS file of the QoS flow corresponding to the QFI1 cannot be guaranteed, and determines that the candidate QoS file of the supported QoS flow is the candidate QoS file #1, the RAN determines, according to the repetition indication information, a notification that whether the QoS flow can be guaranteed or not to send to the user plane network element (e.g., L-PSA) and the control plane network element (e.g., SMF). The RAN has been described above as sending a notification to the user plane network element that QoS flows can be guaranteed, and the following description is made with reference to steps 416-417 of the RAN sending a notification to the control plane network element that QoS flows can be guaranteed.

The ran sends information of candidate QoS file #1 to the AMF 416.

In step 416, the RAN may send information of the candidate QoS file #1 (e.g., an identification of the candidate QoS file # 1) to the AMF according to the duplicate notification indication received in step 410.

The RAN may also send to the AMF in step 416: QFI1, instruction information (an example of the first notification information) that cannot secure GFBR. For example, the RAN sends an N2 message (N2 message) to the AMF, where the N2 message includes: QFI1, indication information of the GFBR incapable of being secured, and information of the candidate QoS file # 1.

417, the amf sends candidate QoS file #1 information to the SMF.

The AMF may forward the information received in step 416 to the SMF. For example, the AMF receives from the RAN in step 416: QFI1, indication information of GFBR incapable of being secured, information of candidate QoS file #1 (e.g., identification of candidate QoS file # 1), and in step 417, AMF forwards QFI1, indication information of GFBR incapable of being secured, information of candidate QoS file #1 to SMF. In one possible implementation, the AMF sends a Namf interface PDU session update session management context (namf_pduse_updatsmcontext) message to the SMF, where the message includes QFI1, indication information that cannot guarantee GFBR, and information of the candidate QoS file # 1.

418, the smf sends the QoS parameters corresponding to the candidate QoS file #1 to the UE.

In addition, the SMF may also send QFI1 to the UE so that the UE identifies a QoS flow to which the QoS parameter corresponding to the candidate QoS file #1 applies.

As an example, the SMF transmits the QoS parameters corresponding to QFI1 and the candidate QoS file #1 to the UE through the AMF. For example, the SMF sends a namf_communication_n1n2message transfer message to the AMF, where the message includes an N1 message container (N1 message container), and the N1 message container includes QFI1 and QoS parameters corresponding to the candidate QoS file # 1; after the AMF receives the message, the AMF sends NAS message to the UE, wherein the NAS message comprises QFI1 and QoS parameters corresponding to the candidate QoS file # 1.

It will be appreciated that the foregoing is illustrative, and that the AMF may also send the QoS parameters corresponding to QFI1 and candidate QoS file #1 directly to the UE. That is, after the AMF receives the QFI1 and the candidate QoS file #1 sent by the RAN, the QoS parameters corresponding to the QFI1 and the candidate QoS file #1 may be sent to the UE.

One possible procedure is exemplarily described above in connection with steps 401-418 shown in fig. 4. It should be understood that the above steps are merely exemplary illustrations, and are not strictly limited thereto. In addition, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence 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. For example, there is no strict order between the steps 414 and 416, for example, step 414 may be performed first and then step 416 may be performed. Alternatively, step 416 may be performed before step 414 is performed; or may be performed simultaneously, which is not limited.

Based on the above method 400, the pcf includes a duplicate notification indication, or includes a direct notification indication and second indication information, or includes a direct notification indication and no third indication information, in the PCC rule according to the request of the AF, and the SMF sends the duplicate notification indication to the RAN, and the RAN sends, according to the duplicate notification indication, an indication that the GFBR cannot guarantee and an identification of a candidate QoS file (i.e., candidate QoS file # 1) that matches QoS of the QoS flow supported by the RAN, to the control plane network element and the user plane network element, respectively. After the SMF receives the identification of the candidate QoS file, the SMF sends the QoS parameters corresponding to the candidate QoS file to the UE. Thus, the UE may be made aware of QoS parameters corresponding to candidate QoS files currently being executed by the RAN.

Fig. 7 is a schematic flow chart diagram of a communication method 700 provided in an embodiment of the present application. The method 700 may be applied to scheme 2 in the method 300 described above, that is, a scheme in which the user plane network element sends information of the candidate QoS file to the control plane network element. The method 700 may include the following steps.

701, establishment procedure of pdu session.

The af sends a request message #1 to the NEF 702.

703, the nef sends a request message #2 to the PCF.

704, the pcf sends a response message to the NEF requesting message #2.

705, the nef sends a response message to the AF requesting message 1.

Steps 701-705 are similar to steps 401-405 and are not repeated here.

706, the PCF formulates PCC rules.

Step 706 is similar to step 406 except that in step 706, a notification indication is repeated indicating that the L-PSA is to send a notification to the NEF or AF, and the control plane network element (e.g., SMF) whether QoS of the QoS flow can be guaranteed. For example, if the UE notification information and the direct notification indication are carried in step 702, that is, the UE notification information and the direct notification indication are included in the information #1, the RAN indicates whether the AF-oriented notification can be guaranteed (or whether the L-PSA directly reports the AF-oriented notification can be guaranteed) through the user plane, and the UE needs to know the QoS parameters of the QoS flows supported by the current RAN: notification of whether QoS for QoS flows can be guaranteed, the PCF may include a repeat notification indication in the PCC rules to indicate that the L-PSA is to send to the NEF or AF, and a control plane network element (e.g., SMF): notification of whether QoS of QoS flows can be guaranteed. For another example, if the direct notification indication and the indication information #a are carried in step 702, that is, the UE notification information and the direct notification indication are included in the information #1, the PCF includes the direct notification indication and the second indication information in the PCC rule; the SMF may determine, in combination with the direct notification indication and the second indication information in the PCC rule, that the L-PSA is to send a notification to the NEF or AF, and whether the QoS of the QoS flow can be guaranteed by the control plane network element (e.g., the SMF). For another example, if the direct notification indication is carried and the indication information #b is not carried in step 702, that is, the information #1 includes the direct notification indication and the indication information #b is not included, the PCF includes the direct notification indication and the third indication information is not included in the PCC rule; the SMF may determine, according to the PCC rule including the direct notification indication and the PCC rule not including the third indication information, that the L-PSA is to send a notification to the NEF or AF and whether the QoS of the QoS flow can be guaranteed to the control plane network element (e.g., the SMF).

707, the pcf sends PCC rules to the SMF.

At 708, the smf sends an acknowledgement message to the PCF.

After receiving the indication from the PCF (i.e., PCC rule), the SMF may send a direct notification indication to the RAN to cause the RAN to send a notification to the user plane network element (e.g., L-PSA) whether the QoS flow can be guaranteed. As an example, the SMF may send information to the RAN through the AMF, as in steps 709 and 710.

709, the smf sends a request message #3 to the AMF.

Taking the SMF determination to create a QoS flow as an example, the SMF assigns a QFI (assumed to be QFI 1) to the QoS flow. The SMF sends a request message #3 to the AMF, the request message #3 including: QFI (i.e., QFI 1), qoS notification control indication, information of candidate QoS files, direct notification indication. Wherein the SMF may determine that the direct notification indication is included in the request message #3 according to any one of the following cases (a), (b), or (c). The direct notification indicates a notification for indicating whether the RAN transmits QoS of the QoS flow to the L-PSA can be guaranteed.

In a possible implementation, in step 709, the SMF sends a namf_communication_n1n MessageTransfer Request message to the AMF.

The amf sends 710 the information in request message #3 to the RAN.

711, the amf sends a response message to the SMF requesting message # 3.

Steps 707-711 are similar to steps 407-411 and are not described again here.

After the SMF receives the indication from the PCF (i.e., PCC rule), it may send a duplicate notification indication to the L-PSA to cause the L-PSA to send a notification to the control plane network element (e.g., SMF) of whether the QoS flow can be guaranteed. As an example, the SMF may send a duplicate notification indication to the L-PSA through the N4 session modification procedure, as in step 712.

At 712, an N4 session modification is made between the SMF and the L-PSA.

Step 712 is similar to step 412 except that during the N4 session modification between the SMF and the L-PSA, the SMF sends a duplicate notification indication to the L-PSA. It will be appreciated that this is not limiting. For example, the SMF may also send a duplicate notification indication to the L-PSA in other flows.

713, in the case that QoS of the QoS file of the QoS flow cannot be guaranteed, the RAN determines that the candidate QoS file of the supported QoS flow is the candidate QoS file #1.

714, the RAN sends information of candidate QoS file #1 to the L-PSA.

For example, the RAN may send information of candidate QoS file #1 (e.g., an identification of candidate QoS file # 1) to the L-PSA according to the direct notification indication received in step 710.

715, the l-PSA sends information of the candidate QoS requirements corresponding to the candidate QoS file #1 to the AF.

Steps 713-715 are similar to steps 413-415 and are not described in detail herein.

The L-PSA determines whether to send a notification of QoS flow being guaranteed to the control plane network element (e.g., SMF) according to the repetition indication information, in step 716.

716, the l-PSA sends information of candidate QoS file #1 to the SMF.

In step 716, the L-PSA may send information of the candidate QoS file #1 (e.g., an identification of the candidate QoS file # 1) to the AMF according to the duplicate notification indication received in step 712.

In step 716, the L-PSA may also send to the SMF: QFI1, cannot guarantee the indication information of GFBR (i.e., qoS in QoS file of QoS flow cannot be guaranteed). For example, the L-PSA sends an N4 session report (N4 session report) to the SMF, the N4 session report including: QFI1, indication information of the GFBR incapable of being secured, and information of the candidate QoS file # 1.

717, the SMF sends the QoS parameters corresponding to the candidate QoS file #1 to the UE.

Step 717 is similar to step 418 and will not be described again.

One possible flow is illustratively described above in connection with steps 701-717 shown in FIG. 7. It should be understood that the above steps are merely exemplary illustrations, and are not strictly limited thereto. In addition, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence 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. For example, there is no strict sequence between the steps 715 and 716, for example, step 715 may be performed first and then step 716 may be performed; alternatively, step 716 may be performed before step 715 is performed; or may be performed simultaneously, which is not limited.

Based on the method 700 described above, the pcf includes a duplicate notification indication in the PCC rule according to the request of the AF, or includes a direct notification indication and second indication information, or includes a direct notification indication and does not include third indication information, the SMF sends the duplicate notification indication to the L-PSA, and the L-PSA sends an indication that the GFBR cannot guarantee and an identification of a candidate QoS file (i.e., candidate QoS file # 1) that matches the QoS of the RAN-supported QoS flow according to the duplicate notification indication, respectively, to the SMF and the NEF/AF. After the SMF receives the identification of the candidate QoS file matched with the QoS of the QoS flow supported by the RAN, the SMF sends the QoS parameters corresponding to the candidate QoS file to the UE. Thus, the UE may be made aware of QoS parameters corresponding to candidate QoS files currently being executed by the RAN.

The applicable flows for use in method 300 with respect to schemes 1 and 2 are described above in connection with fig. 4 and 7. It is to be understood that the above method 400 and method 700 are mainly described by taking the example that the PCC rule includes the duplicate notification indication, or includes the direct notification indication and the second indication information, or includes the direct notification indication and does not include the third indication information, which is not limited.

The following describes, in connection with fig. 8 and 9, applicable flows involving UE handover in method 400 or method 700. For convenience of description, hereinafter, a RAN before UE handover will be referred to as a first RAN, and a RAN after UE handover will be referred to as a second RAN. That is, it is assumed that the UE is handed over from a first RAN to a second RAN, i.e., the first RAN serves the UE before the handover and the second RAN serves the UE after the handover.

Fig. 8 is a schematic flow chart diagram of a communication method 800 provided in an embodiment of the present application. The method 800 may include the following steps.

801, the ue is handed over from a first RAN to a second RAN.

After the UE moves, a handover of the network may occur, such as an Xn-based handover between NG-RANs or an NG-inter-RAN node N2-based handover. In the present embodiment, it is assumed that the UE is handed over from a first RAN to a second RAN.

During the handover procedure, the second RAN may obtain information of QoS flows of the UE (e.g., information of each QoS flow of the UE) from the first RAN. The information of the QoS flow may include QoS related information, for example.

Among other QoS related information, for example, may include, but is not limited to: qoS notification control, a QoS file of a QoS flow, and at least one candidate QoS file, where the QoS file of the QoS flow is a QoS file executed when the UE accesses the first RAN, and the at least one candidate QoS file is a candidate QoS file corresponding to the QoS flow when the UE accesses the first RAN. For method 400, the qos related information further includes a duplicate notification indication; for method 700, a direct notification indication is also included in the qos related information. The second RAN may determine whether QoS of the QoS flow is supported based on the QoS file of the QoS flow, i.e., the second RAN may determine whether QoS in the QoS file of the QoS flow can be guaranteed. If the second RAN determines that QoS in the QoS file of the QoS flow cannot be guaranteed, the second RAN may determine a candidate QoS file for the supported QoS flow.

For distinction, it is assumed that the QoS flow in step 801 is identified as QFI1, that is, the information of the QoS flow is information corresponding to QFI1.

The second RAN sends 802 a second RAN acceptable QFI list to the AMF.

For example, the second RAN sends an N2 message to the AMF, the N2 message including a QFI list acceptable to the second RAN.

Wherein the second RAN acceptable QFI list includes QFI acceptable to the second RAN or QFI supportable by the second RAN. Optionally, the QFI list further includes information of candidate QoS files (such as an identifier of the candidate QoS file) supporting the QoS flows corresponding to the QFI.

Specifically, if the second RAN does not support the QoS profile of a QoS flow, but supports the candidate QoS profile of the QoS flow, the information of the candidate QoS profile (e.g., the identification of the candidate QoS profile) supporting the QoS flow is included in the QFI list acceptable to the second RAN.

For example, the QoS flow accepted by the second RAN includes a QoS flow corresponding to QFI1, and the candidate QoS file supporting the QoS flow corresponding to QFI1 is candidate QoS file #2, in step 802, the second RAN may include information of QFI1 and candidate QoS file #2 (such as an identifier of candidate QoS file # 2) in the second RAN acceptable QFI list sent to the AMF.

For another example, the QoS flow accepted by the second RAN includes a QoS flow corresponding to QFI1, and a QoS file supporting the QoS flow corresponding to QFI1 (i.e., qoS in the QoS file of the QoS flow can be guaranteed), and the QFI1 may be included in the second RAN acceptable QFI list sent by the second RAN to the AMF.

Assume in step 802 that the second RAN acceptable QFI list includes information for QFI1 and candidate QoS file #2 (e.g., identification of candidate QoS file # 2).

803, the amf sends a QFI list acceptable to the second RAN to the SMF.

After the AMF receives the second RAN acceptable QFI list sent by the second RAN, forwarding the second RAN acceptable QFI list to the SMF, where the second RAN acceptable QFI list includes information of QFI1 and candidate QoS file #2 (e.g., identification of candidate QoS file # 2).

In one possible implementation, the AMF sends a namf_pduse_ UpdateSMContext Request message to the SMF, where the message includes information about QFI1 and candidate QoS file #2 (e.g., an identification of candidate QoS file # 2).

The second RAN may also provide the L-PSA with information of at least one QoS flow acceptable to the second RAN, such as a QFI list acceptable to the second RAN, step 804.

The second RAN sends 804 a list of QFI acceptable to the second RAN to the L-PSA.

In one possible scenario, the second RAN sends the L-PSA with a user plane packet according to a duplicate notification indication (e.g., the duplicate notification indication in method 400): a list of QFI acceptable to the second RAN. Reference may be made to the description in step 802 for a list of QFI acceptable to the second RAN, which is not repeated here.

In another possible scenario, the second RAN sends a list of QFI acceptable to the second RAN to the L-PSA via user plane packets according to a direct notification indication (e.g., the direct notification indication in method 700). Reference may be made to the description in step 802 for a list of QFI acceptable to the second RAN, which is not repeated here.

The L-PSA may determine whether the QoS information of the first QoS flow is updated based on the information of at least one QoS flow acceptable to the second RAN (i.e., the QFI list acceptable to the second RAN) and the information provided by the first RAN, as in step 805.

805, the l-PSA determines whether the information of the QoS flow is updated.

Example 1 the l-PSA receives the following information sent by the first RAN: if the QFI1 and the information of the candidate QoS file #1 corresponding to the QFI1 are included in the second RAN acceptable QFI list received by the L-PSA, the L-PSA may determine that the information of the QoS flow is updated, that is, the QoS in the QoS file of the QoS flow corresponding to the QFI1 cannot be guaranteed, and the candidate QoS file of the QoS flow corresponding to the QFI1 supported by the second RAN becomes the candidate QoS file #2.

Example 2 the l-PSA receives the following information sent by the first RAN: if the QFI list received by the L-PSA includes QFI1, the L-PSA can judge that the information of the QoS flow is updated, namely the QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed.

It is to be understood that the foregoing is illustrative and not restrictive.

806, the l-PSA sends the updated information of the QoS flow to the AF.

When the L-PSA judges that the information of the QoS flow is updated, the L-PSA transmits the updated information of the QoS flow to the AF.

For example, taking example 1 above as an example, the information after the QoS flow update includes that QoS in the QoS files of the QoS flow corresponding to QFI1 cannot be guaranteed, and the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN is candidate QoS file #2, and therefore, the L-PSA sends to the AF: notification that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed, and information of the candidate QoS requirement corresponding to the candidate QoS file # 2.

For another example, taking the example 2 above as an example, qoS in a QoS file including QoS flows corresponding to QFI1 can be guaranteed, and therefore, L-PSA sends to AF: notification that QoS in a QoS file of a QoS flow corresponding to QFI1 can be guaranteed.

In the first possible scenario, the L-PSA determines notification endpoint a from QFI and sends QoS flow updated information to AF.

In a second possible scenario, the L-PSA determines notification endpoint b from QFI and sends QoS flow updated information to the NEF; the NEF determines notification endpoint a according to notification endpoint b and sends the updated QoS flow information to the AF.

Optionally, the method 800 further comprises step 807.

807, the smf determines whether the information of the QoS flow is updated.

For the case of QoS Notification Control, the SMF determines whether the information of the QoS flow is updated based on the notification of whether the QoS of the QoS file of the QoS flow received from the first RAN can be guaranteed, and the QFI list acceptable to the second RAN received in step 803. Specific determination may be referred to the description in step 805, and will not be described herein.

Assuming that the SMF determines that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and that the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN becomes the candidate QoS file #2, the method 800 further includes step 808.

808, the smf sends the QoS parameters corresponding to the candidate QoS file #2 to the UE.

In addition, the SMF may also send QFI1 to the UE so that the UE identifies the QoS flow to which the QoS parameter corresponding to the candidate QoS file #2 applies.

As an example, the SMF transmits the QoS parameters corresponding to the candidate QoS file #2 to the UE through the AMF. For example, the SMF sends a namf_communication_n1n2message transfer message to the AMF, where the message includes n1message container, and where the N1message container includes QoS parameters corresponding to the candidate QoS file # 2; after the AMF receives the message, the AMF sends an NAS message to the UE, wherein the NAS message comprises QoS parameters corresponding to the candidate QoS file # 2.

In one possible scenario, the SMF itself determines candidate QoS file #2. That is, based on step 807, the smf itself determines that the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN becomes the candidate QoS file #2.

In another possible scenario, the L-PSA sends information of candidate QoS file #2 (as a representation of candidate QoS file # 2) to the SMF. After step 805, the method 800 further comprises: the L-PSA sends QFI1 and information of candidate QoS file #2 (as a representation of candidate QoS file # 2) to the SMF. For example, after the L-PSA determines that the QoS flow information is updated, the updated QoS flow information (such as the notification that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and the information of the candidate QoS file # 2) is sent to the SMF according to the repeated notification instruction (such as the method 700), and the SMF sends the QoS parameters corresponding to the candidate QoS file #2 to the UE. In this case, method 800 may not include step 807.

One possible procedure is exemplarily described above in connection with steps 801-808 shown in fig. 8. It should be understood that the above steps are merely exemplary illustrations, and are not strictly limited thereto. In addition, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence 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. For example, there is no strict order between the steps 805 and 807, for example, step 805 may be performed first and then step 807 may be performed. Alternatively, step 807 may be performed first, followed by step 805; or may be performed simultaneously, which is not limited.

Based on the method 800, the RAN (i.e., the second RAN) after the ue switches sends the identifier of the QoS flow that can be received and the identifier of the candidate QoS file that can be supported to the L-PSA, and the L-PSA determines whether the information of the QoS flow is updated. In case of an update of the information of the QoS flow, the AF is notified in time. Therefore, in the process of switching across the RAN, the information of the QoS flow can be reported.

Fig. 9 is a schematic flow chart diagram of a communication method 900 provided in an embodiment of the present application. The method 900 may include the following steps.

901, the ue is handed over from a first RAN to a second RAN.

After the UE moves, a handover of the network may occur. In the present embodiment, it is assumed that the UE is handed over from a first RAN to a second RAN.

In the process of switching from the first RAN to the second RAN, the first RAN may send information of a first candidate QoS file to the second RAN, where the first candidate QoS file is a candidate QoS file of a QoS flow that can be supported by the first RAN, in step 902.

The first RAN sends information of QoS flows to the second RAN 902.

During the handover procedure, the second RAN may obtain information of QoS flows of the UE (e.g., information of each QoS flow of the UE) from the first RAN. The information of the QoS flow may include, for example, but not limited to, qoS related information. Information regarding QoS is described with reference to step 801. In addition, in the embodiment of the present application, the QoS related information may further include: QFI of QoS flows whose QoS cannot be guaranteed by QoS files transmitted before and candidate QoS files (QFI 1 and candidate QoS file #1 are assumed) corresponding to the QFI. For example, assume that QoS of a QoS file of a QoS flow corresponding to QFI1 cannot be guaranteed, and that the first RAN determines a candidate QoS file of a supported QoS flow as candidate QoS file #1.

903, the second RAN determines whether an update of the QoS flow information has occurred.

The second RAN may determine whether the information of the QoS flow is updated according to the information of the QoS flow received in step 902 and the actual situation. By way of example, whether the information of the QoS flow is updated may include, for example: whether the guarantee condition of QoS in the QoS file of the QoS flow changes and/or whether the candidate QoS file corresponding to the QoS flow changes.

For example, the second RAN detects a related situation of the QoS flow corresponding to QFI1, for example, the second RAN determines that QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed; for another example, the second RAN determines that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed, and the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN is the candidate QoS file #2.

The second RAN sends 904 the QoS flow updated information to the SMF.

And in the case that the second RAN judges that the information of the QoS flow is updated, the second RAN sends the updated information of the QoS flow to the SMF.

For example, if the second RAN determines in step 903 that QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed, in step 904, the second RAN sends a notification (i.e., third notification information) to the SMF that QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed.

For another example, if the second RAN determines in step 903 that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN is the candidate QoS file #2, in step 904, the second RAN sends information of the candidate QoS file #2 (e.g., an identifier of the candidate QoS file # 2) to the SMF. Optionally, the second RAN also sends a notification (i.e., fourth notification information) that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and/or QFI1 to the SMF.

One possible implementation manner, the second RAN sends the QoS flow updated information to the SMF through the AMF, that is, the second RAN sends the QoS flow updated information to the AMF, and the AMF forwards the QoS flow updated information to the SMF. For example, the second RAN sends an N2 message to the AMF, the N2 message including information after the QoS flow update; the AMF sends a namf_pduse_ UpdateSMContext Request message to the SMF, the namf_pduse_ UpdateSMContext Request message including information after QoS flow update.

905, the second RAN sends the updated information of the QoS flow to the L-PSA.

And when the second RAN judges that the information of the QoS flow is updated, the second RAN sends the updated information of the QoS flow to the L-PSA.

For example, if the second RAN determines in step 903 that QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed, in step 905, the second RAN sends a notification (i.e., sixth notification information) to the L-PSA that QoS in the QoS file of the QoS flow corresponding to QFI1 can be guaranteed.

For another example, if the second RAN determines in step 903 that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and the candidate QoS file of the QoS flow corresponding to QFI1 supported by the second RAN is the candidate QoS file #2, in step 905, the second RAN sends information of the candidate QoS file #2 (e.g., the identifier of the candidate QoS file # 2) to the L-PSA. Optionally, the second RAN also transmits a notification (i.e., fifth notification information) that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and/or QFI1 to the L-PSA.

906, the L-PSA sends the updated information of the QoS flow to the AF.

The L-PSA sends the information received in step 905 to the AF.

In the first possible scenario, the L-PSA determines notification endpoint a from QFI and sends the information received in step 905 to the AF.

In a second possible scenario, the L-PSA determines notification endpoint b from QFI and sends the information received in step 905 to the NEF; the NEF determines notification endpoint a based on notification endpoint b and forwards the information received from the L-PSA to the AF.

907, the smf sends the QoS parameters corresponding to the candidate QoS file #2 to the UE.

In one possible scenario, the SMF may determine the candidate QoS file #2 according to the updated QoS flow information received in step 904, and further send the QoS parameters corresponding to the candidate QoS file #2 to the UE.

In another possible scenario, after step 905, the method 900 further comprises: the L-PSA sends information of candidate QoS file #2 to the SMF. For example, after receiving the updated information of the sending QoS flow (such as the notification that QoS in the QoS file of the QoS flow corresponding to QFI1 cannot be guaranteed and the information of the candidate QoS file # 2), the L-PSA sends the information of the candidate QoS file #2 to the SMF according to the repeated notification instruction (such as the method 700), and the SMF sends the QoS parameter corresponding to the candidate QoS file #2 to the UE.

One possible flow is described above by way of example in connection with steps 901-907 shown in fig. 9. It should be understood that the above steps are merely exemplary illustrations, and are not strictly limited thereto. In addition, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence 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. For example, there is no strict sequence between the steps 904 and 905, for example, the step 904 may be performed first and then the step 905 may be performed. Alternatively, step 905 may be performed first, and then step X904 may be performed; or may be performed simultaneously, which is not limited.

Based on the method 900, during the cross-RAN handover, the RAN before the UE handover (i.e., the first RAN) sends to the RAN after the UE handover (i.e., the second RAN) a list of QoS flows that QoS of the QoS file sent before cannot guarantee and supported candidate QoS files. The second RAN determines whether an update of the QoS flow information has occurred. If the second RAN judges that the information of the QoS flow is updated, the second RAN can send the updated information to the L-PSA, and the L-PSA sends the received information to the AF. Therefore, in the process of switching across the RAN, the information of the QoS flow can be reported.

It will be appreciated that the examples in fig. 4-9 in the embodiments of the present application are merely for convenience of understanding the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from the examples of fig. 4-9 that various equivalent modifications or variations may be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application.

It will also be appreciated that the various steps of fig. 4-9 described above are merely exemplary and are not strictly limiting. In addition, the sequence number of each process does not mean the sequence of execution sequence, and the execution sequence 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.

It should also be understood that, in the drawings, core network elements such as PSA, SMF, AMF are shown separately for ease of understanding only, and this should not constitute any limitation to the present application. The specific form of the core network element is not limited in the present application.

It should also be understood that in some of the above embodiments, some message names, such as interface request messages or interface response messages, etc., are referred to, and that the naming thereof should not be limited to the scope of the embodiments of the present application.

It is also understood that in some of the above embodiments, whether GFBR of QoS flows can be guaranteed and whether QoS of QoS flows can be guaranteed are sometimes used interchangeably, and those skilled in the art will understand the meaning thereof. It will be further understood that in the embodiments of the present application, reference is made to network element a sending a message, information or data to network element B, and to network element B receiving a description of the message, information or data from network element a, which is intended to illustrate to which network element the message, information or data is intended, without limiting whether it is sent directly between them or indirectly via other network elements.

It will also be appreciated that the above is mainly exemplified by the information informing the UE of the candidate QoS file currently being executed by the RAN, which is not limited thereto. For example, if the RAN detects that the QoS flow corresponding to the QFI can be guaranteed, the UE may be notified of the information of the QoS file matched with the QoS flow.

It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features, or may, in some circumstances, be combined with other features, without limitation.

It is also to be understood that the aspects of the embodiments of the present application may be used in any reasonable combination, and that the explanation or illustration of the terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.

It should also be understood that, in the foregoing embodiments of the method and the operations implemented by the device or the network element, the method and the operations may also be implemented by a component (such as a chip or a circuit) of the device or the network element, which are not limited thereto.

Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for performing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.

Fig. 10 is a schematic block diagram of a communication device 1000 provided in an embodiment of the present application. The apparatus 1000 includes one or more virtual units, such as a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 may be used to implement corresponding communication functions. The transceiver unit 1010 may also be referred to as a communication interface or a communication unit. The processing unit 1020 may be configured to implement a corresponding processing function, such as determining candidate QoS files.

Optionally, the apparatus 1000 further includes a storage unit, where the storage unit may be configured to store instructions and/or data, and the processing unit 1020 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the device or the network element in the foregoing method embodiments.

In a first design, the apparatus 1000 may be a control plane network element in the foregoing embodiment, or may be a component (such as a chip) of the control plane network element. The apparatus 1000 may implement steps or flows performed by network elements corresponding to the control plane in the method embodiments above. The transceiver 1010 may be configured to perform operations related to the transceiving of the control plane network element in the above method embodiment, for example, the operations related to the transceiving of the control plane network element in the embodiment shown in fig. 3, and for example, the operations related to the transceiving of the SMF in the embodiment shown in fig. 4 to 9; the processing unit 1020 may be configured to perform operations related to processing by the control plane network element in the above method embodiment, such as operations related to processing by the control plane network element in the embodiment shown in fig. 3, and operations related to processing by the SMF in the embodiment shown in fig. 4 to 9.

A first possible implementation manner, the transceiver unit 1010 is configured to send first indication information to a first access network device, where the first indication information indicates that the access network device sends to a user plane network element and a control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the transceiver 1010 is further configured to receive first notification information from the first access network device and information of a first candidate QoS file, where the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow that the first access network device can support; the transceiver 1010 is further configured to send, to the terminal device, a first QoS parameter corresponding to the first candidate QoS file.

Optionally, the transceiver 1010 is further configured to receive a policy rule from the policy control network element, where the policy rule includes second indication information, and the second indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the second indication information indicates that the access network device sends to the user plane network element and the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the transceiver 1010 is specifically configured to send the first indication information to the first access network device based on the policy rule.

Optionally, the transceiver 1010 is further configured to receive a policy rule from the policy control network element, where the policy rule does not include third indication information, and the third indication information indicates that QoS parameters of QoS flows that can be supported by the access network device are not notified to the terminal device; the transceiver 1010 is specifically configured to send the first indication information to the first access network device based on the policy rule.

Optionally, the transceiver 1010 is further configured to send a QoS file of the first QoS flow to the first access network device; receiving second notification information from the first access network device, wherein the second notification information notifies that the QoS of the first QoS flow can be guaranteed; and responding to the second notification information, and sending second QoS parameters corresponding to the QoS files of the first QoS flow to the terminal equipment.

Optionally, the transceiver 1010 is further configured to receive third notification information from the second access network device, where the third notification information notifies that QoS of the first QoS flow can be guaranteed; responding to the third notification information, and sending a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment; the first access network device is access network device accessed before terminal device switching, the second access network device is access network device accessed after terminal device switching, and the QoS file of the first QoS flow is sent by the control plane network element to the first access network device.

Illustratively, the third notification information includes at least one QoS flow identification accepted by the second access network device, the at least one QoS flow identification including an identification of the first QoS flow.

Optionally, the transceiver 1010 is further configured to receive fourth notification information from the second access network device and information of a second candidate QoS file, where the fourth notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the second candidate QoS file is a candidate QoS file of the first QoS flow that the second access network device can support; sending a third QoS parameter corresponding to the second candidate QoS file to the terminal equipment; the first access network equipment is access network equipment accessed before terminal equipment is switched, and the second access network equipment is access network equipment accessed after terminal equipment is switched.

A second possible implementation manner, the transceiver unit 1010 is configured to send first indication information to a user plane network element, where the first indication information indicates that the user plane network element sends to a control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the transceiver 1010 is further configured to receive first notification information from a user plane network element and information of a first candidate QoS file, where the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow that can be supported by the first access network device; the transceiver 1010 is further configured to send, to the terminal device, a first QoS parameter corresponding to the first candidate QoS file.

Optionally, the transceiver 1010 is further configured to receive a policy rule from the policy control network element, where the policy rule includes second indication information, and the second indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by the access network device, or the second indication information indicates that the user plane network element sends to the control plane network element: notification of whether QoS of QoS flows can be guaranteed and/or information of candidate QoS files of QoS flows that can be supported by the access network device; the transceiver 1010 is specifically configured to send the first indication information to the user plane network element based on the policy rule.

Optionally, the transceiver 1010 is further configured to receive a policy rule from the policy control network element, where the policy rule does not include third indication information, and the third indication information indicates that QoS parameters of QoS flows that can be supported by the access network device are not notified to the terminal device; the transceiver 1010 is specifically configured to send the first indication information to the user plane network element based on the policy rule.

Optionally, the transceiver 1010 is further configured to receive second notification information from the user plane network element, where the second notification information notifies that QoS of the first QoS flow can be guaranteed; and responding to the second notification information, and sending second QoS parameters corresponding to the QoS files of the first QoS flow to the terminal equipment.

In a second design, the apparatus 1000 may be an access network device in the foregoing embodiment, or may be a component (such as a chip) of the access network device. The apparatus 1000 may implement steps or procedures performed by an access network device corresponding to the above method embodiments. The transceiver 1010 may be configured to perform the operations related to transceiving of the access network device in the above method embodiment, such as the operations related to transceiving of the first access network device in the embodiment shown in fig. 3, such as the operations related to transceiving of the second access network device in the embodiment shown in fig. 3, such as the operations related to transceiving of the RAN in the embodiment shown in fig. 4 or fig. 7, such as the operations related to transceiving of the first RAN in the embodiment shown in fig. 8 or fig. 9, and such as the operations related to transceiving of the second RAN in the embodiment shown in fig. 8 or fig. 9; the processing unit 1020 may be configured to perform the operations related to the processing of the access network device in the method embodiment above, such as the operations related to the processing of the first access network device in the embodiment shown in fig. 3, such as the operations related to the processing of the second access network device in the embodiment shown in fig. 3, such as the operations related to the processing of the RAN in the embodiment shown in fig. 4 or fig. 7, such as the operations related to the processing of the first RAN in the embodiment shown in fig. 8 or fig. 9, and such as the operations related to the processing of the second RAN in the embodiment shown in fig. 8 or fig. 9.

A possible implementation manner, the transceiver unit 1010 is configured to receive first indication information from a control plane network element, where the first indication information indicates that the access network device sends to the user plane network element and the control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the transceiver 1010 is further configured to send, to the control plane network element and the user plane network element, first notification information and information of a first candidate QoS file, where the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow that can be supported by the first access network device.

Optionally, the transceiver unit 1010 is further configured to send second notification information to the control plane network element, where the second notification information informs that QoS of the first QoS flow can be guaranteed.

Optionally, the transceiver 1010 is further configured to send fourth indication information to the second access network device, where the fourth indication information is determined according to the first indication information, the first access network device is an access network device that is accessed before the terminal device is switched, and the second access network device is an access network device that is accessed after the terminal device is switched.

Optionally, the transceiver unit 1010 is further configured to send, to the second access network device, the identification of the first QoS flow and the information of the first candidate QoS file.

In the second possible design, the steps or the flow executed by the first access network device in the above method embodiment are mainly described as examples of implementation of the apparatus 1000, and it is to be understood that the apparatus 1000 may also correspond to the steps or the flow executed by the second access network device in the above method embodiment, and specific reference may be made to the description of the above method embodiment, which is not repeated herein.

In a third design, the apparatus 1000 may be a user plane network element in the foregoing embodiment, or may be a component (e.g. a chip) of the user plane network element. The apparatus 1000 may implement steps or procedures performed corresponding to user plane network elements in the above method embodiments. The transceiver 1010 may be configured to perform operations related to the transceiving of the user plane network element in the above method embodiment, such as the transceiving related operations of the user plane network element in the embodiment shown in fig. 3, and the transceiving related operations of the L-PSA in the embodiments shown in fig. 4 to 9; the processing unit 1020 may be configured to perform the operations related to the processing of the user plane network element in the above method embodiment, such as the operations related to the processing of the user plane network element in the embodiment shown in fig. 3, and such as the operations related to the processing of the L-PSA in the embodiment shown in fig. 4 to 9.

A possible implementation manner, the transceiver unit 1010 is configured to receive first indication information from the control plane network element, where the first indication information indicates that the user plane network element sends to the control plane network element: informing whether the QoS of the first server quality QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment; the transceiver 1010 is further configured to send, to the control plane network element, first notification information and information of a first candidate QoS file, where the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow that can be supported by the first access network device

Optionally, the transceiver unit 1010 is further configured to receive the first notification information and the information of the first candidate QoS file from the first access network device.

Optionally, the transceiver 1010 is further configured to receive second notification information from the first access network device, where the second notification information informs that QoS of the first QoS flow can be guaranteed; and sending second notification information to the control plane network element.

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

It should also be appreciated that the apparatus 1000 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality.

By way of example, the product implementation form of the apparatus 1000 provided in the embodiments of the application is program code that can run on a computer.

The apparatus 1000 provided in the embodiments of the present application may be a communication device, or may be a chip, a system-on-chip (SoC), or a circuit applied to the communication device. When the apparatus 1000 is a communication device, the transceiver unit 1010 may be a transceiver, or an input/output interface; the processing unit 1020 may be a processor. When the apparatus 1000 is a chip, a system-on-chip, or a circuit used in a communication device, the transceiver 1010 may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit on the chip, the system-on-chip, or the circuit; the processing unit 1020 may be a processor, processing circuitry, logic circuitry, or the like.

The transceiver 1010 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

Fig. 11 is a schematic block diagram of a communication device 1100 provided by an embodiment of the present application. The apparatus 1100 includes a processor 1110, the processor 1110 being coupled to a memory 1120. Optionally, a memory 1120 is further included for storing computer programs or instructions and/or data, and the processor 1110 is configured to execute the computer programs or instructions stored in the memory 1120, or to read the data stored in the memory 1120, to perform the methods in the method embodiments above.

Optionally, the processor 1110 is one or more.

Optionally, the memory 1120 is one or more.

Alternatively, the memory 1120 may be integrated with the processor 1110 or provided separately.

Optionally, as shown in fig. 11, the apparatus 1100 further comprises a transceiver 1130, the transceiver 1130 being for receiving and/or transmitting signals. For example, the processor 1110 is configured to control the transceiver 1130 to receive and/or transmit signals.

As an option, the apparatus 1100 is configured to implement the operations performed by the control plane network element in the above method embodiments.

For example, the processor 1110 is configured to execute computer programs or instructions stored in the memory 1120 to implement the relevant operations of the control plane network elements in the above method embodiments. For example, the method performed by the control plane network element in the embodiment shown in fig. 3, or the method performed by the SMF in the embodiments shown in fig. 4 to 9.

Alternatively, the apparatus 1100 is configured to implement the operations performed by the access network device in the method embodiments above.

For example, the processor 1110 is configured to execute computer programs or instructions stored in the memory 1120 to implement the relevant operations of the access network device in the above method embodiments. For example, the method performed by the first access network device in the embodiment shown in fig. 3; as another example, the method performed by the second access network device in the embodiment shown in fig. 3; as another example, the RAN performs the method of the embodiments shown in fig. 4 or fig. 7; as another example, the method performed by the first RAN in the embodiment shown in fig. 8 or fig. 9; as another example, the method performed by the second RAN in the embodiment shown in fig. 8 or fig. 9.

Alternatively, the apparatus 1100 is configured to implement the operations performed by the user plane network element in the above method embodiments.

For example, the processor 1110 is configured to execute computer programs or instructions stored in the memory 1120 to implement the relevant operations of the user plane network element in the above method embodiments. For example, the method performed by the user plane network element in the embodiment shown in fig. 3; as another example, the L-PSA performs the method of the embodiments shown in fig. 4-9.

In implementation, the steps of the methods described above may be performed by integrated logic circuitry in hardware or instructions in software in processor 1110. The method disclosed in connection with the embodiments of the present application may be embodied directly in hardware processor execution or in a combination of hardware and software modules in a processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 1120, and the processor 1110 reads information in the memory 1120 and performs the steps of the above method in combination with its hardware. To avoid repetition, a detailed description is not provided herein.

It should be appreciated that in the embodiments of the present application, the processor may be one or more integrated circuits configured to execute related programs to perform the embodiments of the methods of the present application.

A processor (e.g., processor 1110) may include one or more processors and be implemented as a combination of computing devices. The processor may each include one or more of the following: microprocessors, microcontrollers, digital signal processors (digital signal processor, DSPs), digital signal processing devices (digital signal processing device, DSPD), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate arrays (field programmable gate array, FPGA), programmable logic devices (programmable logic device, PLD), gate logic, transistor logic, discrete hardware circuits, processing circuits, or other suitable hardware, firmware and/or combinations of hardware and software for executing the various functions described in this disclosure. The processor may be a general purpose processor or a special purpose processor. For example, the processor 1110 may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data. The central processor may be used to cause the device to execute a software program and process data in the software program. In addition, a portion of the processor may also include nonvolatile random access memory. The processor may also store information of the device type, for example.

The procedure in this application is used in a broad sense to represent software. Non-limiting examples of software include: program code, program, subroutine, instructions, instruction set, code segments, software modules, applications, or software applications, or the like. The program may run in a processor and/or a computer. Such that the apparatus performs the various functions and/or processes described herein.

Memory (e.g., memory 1120) may store data required by a processor (e.g., processor 1110) when executing software. The memory may be implemented using any suitable memory technology. For example, memory may be any available storage media that can be accessed by a processor and/or computer. Non-limiting examples of storage media include: random access memory (random access memory, RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), compact Disc-ROM (CD-ROM), static RAM, dynamic RAM, DRAM, synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM, DRAM), synchronous DRAM (DRAM), removable media, optical disk storage media, magnetic storage devices, flash memory, registers, state memory, remote mount memory, local or remote memory components, or any other medium capable of carrying or storing software, data, or information and being accessed by a processor/computer. It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory (e.g., memory 1120) and the processor (e.g., processor 1110) may be provided separately or integrated together. The memory may be used in connection with the processor such that the processor can read information from, store information in, and/or write information to the memory. The memory may be integrated in the processor. The memory and processor may be provided in an integrated circuit (e.g., the integrated circuit may be provided in a UE or other network node).

Fig. 12 is a schematic block diagram of a chip system 1200 provided in an embodiment of the present application. The system-on-chip 1200 (or may also be referred to as a processing system) includes logic 1210 and input/output interface 1220.

Logic 1210 may be a processing circuit in system-on-chip 1200, among other things. Logic 1210 may be coupled to a memory unit to invoke instructions in the memory unit so that system-on-chip 1200 may implement the methods and functions of embodiments of the present application. The input/output interface 1220 may be an input/output circuit in the chip system 1200, and outputs information processed by the chip system 1200, or inputs data or signaling information to be processed into the chip system 1200 for processing.

As an aspect, the chip system 1200 is configured to implement the operations performed by the control plane network element in the method embodiments above.

For example, the logic 1210 may be configured to implement the operations related to the processing performed by the control plane network element in the above method embodiment, for example, the operations related to the processing performed by the control plane network element in the embodiment shown in fig. 3, or the operations related to the processing performed by the SMF in the embodiment shown in fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by the control plane network element in the above method embodiment, for example, the operations related to transmission and/or reception performed by the control plane network element in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the SMF in the embodiment shown in fig. 4 to 9.

Alternatively, the chip system 1200 is configured to implement the operations performed by the access network device in the method embodiments above.

For example, the logic 1210 is configured to implement the process-related operations performed by the access network device in the method embodiment, for example, the process-related operations performed by the first access network device in the embodiment shown in fig. 3, the process-related operations performed by the second access network device in the embodiment shown in fig. 3, the process-related operations performed by the RAN in the embodiment shown in fig. 4 or fig. 7, the process-related operations performed by the first RAN in the embodiment shown in fig. 8 or fig. 9, and the process-related operations performed by the second RAN in the embodiment shown in fig. 8 or fig. 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by the access network device in the above method embodiment, for example, the operations related to transmission and/or reception performed by the first access network device in the embodiment shown in fig. 3, for example, the operations related to transmission and/or reception performed by the second access network device in the embodiment shown in fig. 3, for example, the operations related to transmission and/or reception performed by the RAN in the embodiment shown in fig. 4 or fig. 7, for example, the operations related to transmission and/or reception performed by the first RAN in the embodiment shown in fig. 8 or fig. 9, and for example, the operations related to transmission and/or reception performed by the second RAN in the embodiment shown in fig. 8 or fig. 9.

Alternatively, the chip system 1200 is configured to implement the operations performed by the user plane network element in the method embodiments above.

For example, the logic 1210 is configured to implement the operations related to the processing performed by the user plane network element in the above method embodiment, for example, the operations related to the processing performed by the user plane network element in the embodiment shown in fig. 3, or the operations related to the processing performed by the L-PSA in the embodiments shown in fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by the user plane network element in the above method embodiment, for example, the operations related to transmission and/or reception performed by the user plane network element in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the L-PSA in the embodiment shown in fig. 4 to 9.

The embodiments of the present application further provide a computer readable storage medium, on which computer instructions for implementing the method performed by the communication apparatus (e.g., the control plane network element, another e.g., the user plane network element, another e.g., the access network device) in the foregoing method embodiments are stored.

Embodiments of the present application also provide a computer program product containing instructions that, when executed by a computer, implement a method performed by a communication apparatus (e.g., a control plane network element, a user plane network element, and an access network device) in the foregoing method embodiments.

The embodiment of the application also provides a communication system, which comprises one or more of the control plane network element, the user plane network element, the first access network device, the second access network device, the policy control network element, the application network element and the terminal device in each embodiment.

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

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the above-described division of units is merely a logical function division, and there may be another division manner in actual implementation, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to implement the solution provided in the present application.

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

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

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. With respect to computer readable storage media, reference may be made to the description above.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

the control plane network element sends first indication information to first access network equipment, and the first indication information indicates the access network equipment to send to the user plane network element and the control plane network element: a notification of whether QoS of a first quality of service QoS flow can be guaranteed and/or information of candidate QoS files of the first QoS flow that can be supported by the access network device;

the control plane network element receives first notification information from the first access network device and information of a first candidate QoS file, wherein the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the first access network device;

and the control surface network element sends the first QoS parameters corresponding to the first candidate QoS file to the terminal equipment.

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

the control plane network element receives a policy rule from a policy control network element, where the policy rule includes second indication information, where the second indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by an access network device, or where the second indication information indicates that the access network device sends to the user plane network element and the control plane network element: informing whether the QoS of the QoS flow can be ensured, and/or information of candidate QoS files of the QoS flow which can be supported by the access network equipment;

the control plane network element sends first indication information to a first access network device, including:

and based on the policy rules, the control plane network element sends the first indication information to the first access network device.

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

the control surface network element receives a policy rule from a policy control network element, wherein the policy rule does not comprise third indication information, and the third indication information indicates that QoS parameters of QoS flows which can be supported by access network equipment are not notified to the terminal equipment;

4. A method according to any one of claims 1 to 3, further comprising:

the control plane network element sends a QoS file of the first QoS flow to the first access network device;

the control surface network element receives second notification information from the first access network device, wherein the second notification information notifies that the QoS of the first QoS flow can be ensured;

and responding to the second notification information, the control surface network element sends a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment.

5. A method according to any one of claims 1 to 3, further comprising:

the control surface network element receives third notification information from second access network equipment, wherein the third notification information notifies that the QoS of the first QoS flow can be ensured;

responding to the third notification information, the control surface network element sends a second QoS parameter corresponding to the QoS file of the first QoS flow to the terminal equipment;

The first access network device is access network device accessed before switching of the terminal device, the second access network device is access network device accessed after switching of the terminal device, and the QoS file of the first QoS flow is sent by the control plane network element to the first access network device.

6. A method according to any one of claims 1 to 3, further comprising:

the control plane network element receives fourth known information from second access network equipment and information of a second candidate QoS file, wherein the fourth known information informs that QoS of the first QoS flow cannot be guaranteed, and the second candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the second access network equipment;

the control surface network element sends a third QoS parameter corresponding to the second candidate QoS file to the terminal equipment;

the first access network device is access network device accessed before switching of the terminal device, and the second access network device is access network device accessed after switching of the terminal device.

7. A method of communication, comprising:

the control plane network element sends first indication information to the user plane network element, wherein the first indication information indicates the user plane network element to send to the control plane network element: a notification of whether QoS of a first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that can be supported by an access network device;

The control plane network element receives first notification information from the user plane network element and information of a first candidate QoS file, wherein the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by first access network equipment;

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

the control plane network element receives a policy rule from a policy control network element, where the policy rule includes second indication information, where the second indication information indicates to notify the terminal device of QoS parameters of QoS flows that can be supported by an access network device, or where the second indication information indicates that the user plane network element sends to the control plane network element: informing whether the QoS of the QoS flow can be ensured, and/or information of candidate QoS files of the QoS flow which can be supported by the access network equipment;

the control plane network element sending first indication information to the user plane network element, including:

and based on the policy rules, the control plane network element sends the first indication information to the user plane network element.

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

10. The method according to any one of claims 7 to 9, further comprising:

the control plane network element receives second notification information from the user plane network element, wherein the second notification information notifies that the QoS of the first QoS flow can be ensured;

11. The method according to any one of claims 7 to 9, further comprising:

12. The method according to any one of claims 7 to 9, further comprising:

13. A method of communication, comprising:

the method comprises the steps that first indication information from a control plane network element is received by first access network equipment, and the first indication information indicates the access network equipment to send to a user plane network element and the control plane network element: a notification of whether QoS of a first quality of service QoS flow can be guaranteed and/or information of candidate QoS files of the first QoS flow that can be supported by the access network device;

and under the condition that the QoS of the first QoS flow cannot be ensured, the first access network equipment sends first notification information and information of a first candidate QoS file to the control plane network element and the user plane network element, wherein the first notification information notifies that the QoS of the first QoS flow cannot be ensured, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by the first access network equipment.

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

and under the condition that the QoS of the first QoS flow can be ensured, the first access network equipment sends second notification information to the control surface network element, and the second notification information notifies that the QoS of the first QoS flow can be ensured.

15. The method according to claim 13 or 14, characterized in that the method further comprises:

the first access network device sends fourth indication information to the second access network device, and the fourth indication information indicates the access network device to send to the user plane network element and the control plane network element: and notifying whether the QoS of the first QoS flow can be ensured, and/or information of candidate QoS files of the first QoS flow which can be supported by the access network equipment, wherein the first access network equipment is access network equipment accessed before the terminal equipment is switched, and the second access network equipment is access network equipment accessed after the terminal equipment is switched.

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

the first access network device sends the identification of the first QoS flow and the information of the first candidate QoS file to the second access network device.

17. A method of communication, comprising:

the user plane network element receives first indication information from the control plane network element, wherein the first indication information indicates to send to the control plane network element: a notification of whether QoS of a first QoS flow can be guaranteed, and/or information of candidate QoS files of the first QoS flow that can be supported by an access network device;

The user plane network element sends first notification information and information of a first candidate QoS file to the control plane network element, wherein the first notification information notifies that QoS of the first QoS flow cannot be guaranteed, and the first candidate QoS file is a candidate QoS file of the first QoS flow which can be supported by first access network equipment.

18. The method of claim 17, wherein before the user plane network element sends the first notification information and the information of the first candidate QoS file to the control plane network element, the method further comprises:

the user plane network element receives the first notification information and the information of the first candidate QoS file from the first access network device.

19. The method according to claim 17 or 18, characterized in that the method further comprises:

the user plane network element receives second notification information from the first access network device, wherein the second notification information notifies that the QoS of the first QoS flow can be ensured;

and the user plane network element sends the second notification information to the control plane network element.

20. A communication device, the device comprising: means for performing the method of any one of claims 1 to 6, or means for performing the method of any one of claims 7 to 12, or means for performing the method of any one of claims 13 to 16, or means for performing the method of any one of claims 17 to 19.

21. A communication device, comprising:

a processor for executing a computer program stored in a memory to cause the apparatus to perform the method of any one of claims 1 to 6 or to cause the apparatus to perform the method of any one of claims 7 to 12 or to cause the apparatus to perform the method of any one of claims 13 to 16 or to cause the apparatus to perform the method of any one of claims 17 to 19.

22. The apparatus of claim 21, further comprising the memory and/or a communication interface coupled with the processor,

the communication interface is used for inputting and/or outputting information.

23. A computer-readable storage medium, on which a computer program is stored which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 6, or to cause the computer to perform the method of any one of claims 7 to 12, or to cause the computer to perform the method of any one of claims 13 to 16, or to cause the computer to perform the method of any one of claims 17 to 19.

24. A computer program product comprising instructions for performing the method of any one of claims 1 to 6 or for performing the method of any one of claims 7 to 12 or for performing the method of any one of claims 13 to 16 or for performing the method of any one of claims 17 to 19.

25. A communication system comprising a control plane network element and a first access network device;

the control plane network element being configured to perform the method of any one of claims 1 to 6;

the first access network device being configured to perform the method of any of claims 13 to 16.

26. A communication system comprising a control plane network element and a user plane network element;

the control plane network element being configured to perform the method of any one of claims 7 to 12;

the user plane network element being configured to perform the method of any one of claims 17 to 19.