CN113518391A

CN113518391A - Communication method and communication device

Info

Publication number: CN113518391A
Application number: CN202010275897.4A
Authority: CN
Inventors: 李永翠; 李濛
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-04-09
Filing date: 2020-04-09
Publication date: 2021-10-19
Anticipated expiration: 2040-04-09
Also published as: WO2021204200A1; CN113518391B

Abstract

The present application provides a communication method and a communication apparatus, which can contribute to accurate QoS control when an access network device supporting AQP information processing and an access network device not supporting AQP information coexist in a communication system. In this embodiment of the present application, the session management network element can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow when it is determined that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, so that the session management network element can perform QoS processing on the first QoS flow according to the AQP information corresponding to the first QoS flow when the access network device does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, which is beneficial to performing QoS control accurately.

Description

Communication method and communication device

Technical Field

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

Background

In a 5G communication system, a quality of service (QoS) controlled management procedure, such as a QoS flow (flow) establishment, modification, or deletion procedure, may be performed through a signaling plane. In the management flow of QoS control, a notification control mechanism is also introduced. As an example, for some important QoS flows, such as Guaranteed Bit Rate (GBR) QoS flows, when the notification mechanism is enabled, the access network device may send a notification message to the core network device when detecting that current resources cannot meet QoS profile information of the QoS flow, so as to indicate that the current resources of the access network device cannot meet the requirement of the QoS flow.

In addition, in the management flow of QoS control, Alternative QoS Profile (AQP) information is also introduced, and the core network device sends the AQP information to the access network device. For example, when the access network device detects that the current resources cannot meet the QoS profile information requirement of the QoS flow, it may also attempt to perform degradation processing on the QoS flow according to the priority of the AQP information, i.e., determine whether the current resources can meet the AQP information. And under the condition that the current resources can not meet the AQP information, the access network equipment sends a notification message to the core network equipment to indicate that the current resources of the access network equipment can not meet the requirements of the QoS flow.

Existing notification control mechanisms are implemented based on that the access network equipment supports processing of AQP information, and a case that the communication system also includes the access network equipment that does not support processing of AQP information is not considered. Therefore, when an access network device supporting AQP information processing and an access network device not supporting AQP information processing coexist in a communication system, how to perform QoS control is an urgent problem to be solved.

Disclosure of Invention

The present application provides a communication method and a communication apparatus, which can contribute to accurate QoS control when an access network device supporting AQP information processing and an access network device not supporting AQP information coexist in a communication system.

In a first aspect, a communication method is provided, in which a session management network element sends QoS profile information of a first quality of service, QoS, flow and alternative QoS profile, AQP, information; determining that the access network device is not performing QoS processing for the first QoS flow according to the AQP information. Then, the session management network element performs QoS processing on the first QoS flow according to the AQP information.

Therefore, in this embodiment of the present application, the session management network element can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow when it is determined that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, so that the session management network element can perform QoS processing on the first QoS flow according to the AQP information corresponding to the first QoS flow when the access network device does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, which is beneficial to performing QoS control accurately.

In the embodiment of the present application, the QoS treatment may be decreasing QoS parameters of a QoS flow (i.e., downgrading QoS treatment or downgrading treatment), increasing QoS parameters of a QoS flow (i.e., upgrading QoS treatment or upgrading treatment), rejecting a QoS flow, and the like.

In some embodiments, the session management network element may send the QoS profile information and the AQP information for the first QoS flow to the access network device (via an access management network element, e.g., an AMF). In a non-mobile scenario, the access network device may be the access network device that does not perform QoS processing on the first QoS flow according to the AQP information. In a mobile scenario, the access network device may be a source access network device, and the above-mentioned access network device that does not perform QoS processing on the first QoS flow according to the AQP information is a target access network device.

With reference to the first aspect, in some implementations of the first aspect, before the determining, by the session management network element, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, the method further includes:

the session management network element determines that resources of the access network device do not satisfy the QoS document information of the first QoS flow.

That is, the session management network element may further determine that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, in a case that it is determined that the resources of the access network device do not satisfy the QoS profile information of the first QoS flow. At this time, the session management network element may perform QoS processing on the first QoS flow according to the AQP information, e.g., perform QoS reduction processing on the first QoS flow according to the AQP information.

In some optional embodiments, when the QoS information of the AQP information corresponding to the first QoS flow, such as the QoS information in the QoS profile information with a PDB higher than the first QoS, the QoS processing of the first QoS flow by the session management network element according to the AQP information may be QoS-up processing of the first QoS flow according to the AQP information.

In some optional embodiments, when the access network device's own conditions (e.g., resources) cannot satisfy the AQP information of the first QoS flow, the QoS treatment of the first QoS flow according to the AQP information may be to reject the first QoS flow according to the AQP information.

With reference to the first aspect, in certain implementations of the first aspect, the determining, by the session management network element, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information includes:

the session management network element acquires indication information;

and the session management network element determines that the access network equipment does not perform QoS processing on the first QoS flow according to the AQP information according to the indication information.

Therefore, in this embodiment of the present application, the session management network element may determine, according to the indication information, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, and perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that when the access network device does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, the session management network element performs QoS processing on the first QoS flow according to the AQP information corresponding to the first QoS flow, which is favorable for performing QoS control accurately.

With reference to the first aspect, in some implementations of the first aspect, the indication information is used to indicate that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, or indicate that the access network device does not have a capability of supporting AQP information processing.

Illustratively, the access network device has a capability of supporting processing of the AQP information, and may refer to the access network device having an ability of recognizing the AQP information and being capable of performing QoS processing on the QoS flow according to the AQP information. On the contrary, the access network device does not have the capability of supporting the processing of the AQP information, which may mean that the access network device does not have the capability of identifying the AQP information, or the access network device has the capability of identifying the AQP information, but cannot perform QoS processing on the QoS flow according to the AQP information.

With reference to the first aspect, in certain implementations of the first aspect, the session management network element may receive the indication information from the access network device. For example, in a mobile scenario, the indication information may indicate that the target access network device does not perform QoS processing on the first QoS flow according to the AQP information, or indicate that the target access network device does not have the capability of supporting AQP information processing. At this time, the session management network element may receive the indication information from the target access network device or the source access network device.

As an implementation manner, when the access network device determines that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, the indication information #1 is generated for indicating that the access network device does not perform QoS flow processing on the first QoS flow according to the AQP information of the first QoS flow. In some specific embodiments, the indication information #1 may also be a first cause value. When the access network device sends the indication information #1 to the session management network element, that is, the session management network element receives the indication information #1 from the access network device, the session management network element may determine, according to the indication information #1, that the access network device does not process the first QoS flow according to the AQP information of the first QoS flow.

As another implementation manner, when the access network device determines that the access network device does not have the capability of supporting the processing of the AQP information, the indication information #2 is generated for indicating that the access network device does not have the capability of supporting the processing of the AQP information. When the access network device sends the indication information #2 to the session management network element, that is, the session management network element receives the indication information #2 from the access network device, the session management network element may determine, according to the indication information #2, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow.

In other embodiments, when the access network device determines that the access network device performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow, the access network device may generate other indication information, for example, indication information #3, for instructing the access network device to perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow. In some specific embodiments, the indication information #3 may also be a second cause value. When the access network device sends the indication information #3 to the session management network element, that is, the session management network element receives the indication information #3 from the access network device, the session management network element may determine, according to the indication information #3, that the access network device performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow.

Alternatively, in other embodiments, when it is determined that the access network device has the capability of supporting the processing of AQP information, the access network device may generate other indication information, for example, indication information #4, for indicating that the access network device has the capability of supporting the processing of AQP information. When the access network device sends the indication information #4 to the session management network element, that is, the session management network element receives the indication information #4 from the access network device, the session management network element may determine, according to the indication information #4, that the access network device performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow.

In some embodiments, when the access network device does not QoS process the first QoS flow according to the AQP information of the first QoS flow, or does not have the capability of supporting the processing of the AQP information, without generating the indication information, the session management element may determine that the access network device does not QoS process the first QoS flow according to the AQP information if the session management element does not receive the indication information from the access network device.

In other embodiments, the session management network element may receive the indication information from other network elements in the core network device, such as the AMF, the PCF, or the UDM, which is not limited in this embodiment of the application.

With reference to the first aspect, in some implementations of the first aspect, the obtaining, by the session management network element, the indication information includes:

acquiring the identifier of the access network equipment;

sending a first request according to the identifier of the access network equipment, wherein the first request is used for inquiring whether the access network equipment has the capability of supporting the processing of AQP information;

receiving capability information of the access network equipment, wherein the capability information is used for indicating that the access network equipment does not have the capability of supporting the processing of AQP information;

and taking the capability information as the indication information.

Illustratively, the session management network element may send the first request to the access network device, or to another network element in the core network, such as the AMF, PCF, or UDM, to query whether the access network device has the capability to support processing AQP information.

Therefore, in this embodiment of the present application, the session management network element may obtain the capability information of the access network device by sending, to other network devices or network elements, a first request for querying whether the access network device has a capability of supporting processing of AQP information. Further, when the capability information of the access network device is used to indicate that the access network device does not have the capability of supporting the processing of the AQP information, it may be determined that the access network device does not perform QoS processing on the first QoS flow according to the AQP information.

Optionally, when acquiring whether the access network device supports the capability of processing the AQP information, the session management network element may locally store the capability information.

obtaining an identification (RAN ID) of the access network device;

and determining whether the access network equipment has the capability of supporting the processing of the AQP information according to the corresponding relation between the pre-acquired identifier of the access network equipment and the capability of supporting the processing of the AQP information.

Therefore, the session management network element may determine whether the access network device has the capability of supporting the processing of the AQP information according to the correspondence between the pre-acquired RAN ID and whether the RAN has the capability of supporting the processing of the AQP information, and further determine whether the access network device performs QoS processing on the first QoS stream according to the AQP information. Under the condition that the access network equipment does not perform the QoS processing on the first QoS flow according to the AQP information, the session management network element can perform the QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the session management network element can process the first QoS flow according to the AQP information when the access network equipment does not perform the QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the accurate QoS control is facilitated.

It should be noted that the first aspect and the methods of various possible implementations of the first aspect are also executed by a component (e.g., a chip or a circuit, etc.) configurable in a session management network element, and this is not limited in this embodiment of the present application.

In a second aspect, a method of communication is provided in which a first access network device determines indication information for determining that a second access network device does not QoS treat a first quality of service, QoS, flow according to alternative QoS profile, AQP, information for the first QoS flow. Then, the first access network device sends the indication information.

Therefore, in this embodiment of the present application, the access network device sends the indication information to the session management network element, and the session management network element can determine that the access network device does not perform QoS processing on the first QoS flow according to the AQP information according to the indication information, and perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the session management network element can process the first QoS flow according to the AQP information when the access network device does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, which is beneficial to accurately performing QoS control.

With reference to the second aspect, in some implementations of the second aspect, the indication information is used to indicate that the second access network device does not perform QoS processing on the first QoS flow according to the AQP information, or indicate that the second access network device does not have a capability of supporting AQP information processing.

In other embodiments, the access network device may further send the indication information to the AMF, which is not limited in this embodiment.

With reference to the second aspect, in some implementations of the second aspect, the determining, by the first access network device, the indication information includes:

receiving a first request for inquiring whether the second access network equipment has the capability of supporting the processing of AQP information;

determining capability information of the second access network device, wherein the capability information is used for indicating that the second access network device does not have the capability of supporting the processing of AQP information;

determining the capability information as the indication information.

For example, the access network device may receive the first request from a session management network element, or an AMF, which is not limited in this embodiment.

Therefore, in this embodiment of the present application, the access network device receives a first request for querying whether the access network device has the capability of supporting the AQP information, and may send a response to the first request, where the response includes the capability information of the access network device. Further, when the capability information indicates that the access network device does not have the capability to support processing the AQP information, the session management network element may determine that the access network device does not QoS process the first QoS flow according to the AQP information.

With reference to the second aspect, in some implementations of the second aspect, the first access network device and the second access network device are the same access network device.

For example, in a non-mobile scenario, the first access network device and the second access network device are the same access network device. For another example, in a mobile scenario, the first access network device and the second access network device may also be the same access network device, for example, both are target access network devices (T-RANs).

With reference to the second aspect, in some implementations of the second aspect, the determining, by the first access network device, the first indication information includes:

receiving a handover confirmation message from the second access network device, where the handover confirmation message includes capability information of the second access network device, and the capability information is used to indicate that the second access network device does not have a capability of supporting AQP information processing;

determining the capability information as the indication information.

For example, in a mobile scenario, the first access network device is a source access network device (S-RAN), and the second access network device is a target access network device. At this time, the target access network device may indicate the capability information of the target access network device to the source access network device through the handover confirmation message.

It should be noted that the second aspect and the methods of various possible implementations of the second aspect are also executed by a component (e.g., a chip or a circuit, etc.) that may be configured in the access network device, and this is not limited in this embodiment of the present application.

In a third aspect, a communications method is provided in which an access management device may determine indication information indicating that an access network device does not have a capability to support processing AQP information. The access management device may then send the indication information to a session management network element.

Therefore, in this embodiment of the present application, the access management network element sends the indication information to the session management network element, and the session management network element can determine that the access network device does not perform QoS processing on the first QoS flow according to the AQP information according to the indication information, and perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the session management network element can process the first QoS flow according to the AQP information when the access network device does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, which is beneficial to accurately performing QoS control.

With reference to the third aspect, in some implementations of the third aspect, the sending the indication information to the session management network element includes:

sending a request for updating the session management context to a session management network element, wherein the request for updating the session management context comprises the indication information; or

And sending a request for creating the session management context to a session management network element, wherein the request for creating the session management context comprises the indication information.

With reference to the third aspect, in some implementations of the third aspect, the access management network element may obtain the identifier of the access network device, and then determine whether the access network device has the capability of supporting AQP information processing according to a correspondence between the identifier of the access network device and whether the access network device has the capability of supporting AQP information processing, which is obtained in advance.

With reference to the third aspect, in some implementations of the third aspect, the access management network element may receive the indication information from the access network device, where the indication information is reported to the AMF after the access network device powers on, or the indication information is carried in an N2 message sent by the access network device to the AMF.

With reference to the third aspect, in some implementations of the third aspect, an access management network element may send a first request to the access network device/PCF/UDM, where the first request is used to query whether the access network device has a capability of supporting AQP information processing;

and receiving the capability information of the access network equipment from the access network equipment/PCF/UDM, wherein the capability information is used for indicating that the access network equipment does not have the capability of supporting the processing of AQP information.

It should be noted that the third aspect and the methods of various possible implementation manners of the third aspect are also executed by a component (e.g., a chip or a circuit, etc.) configurable in the access management network element, and this is not limited in this embodiment of the present application.

In a fourth aspect, a communication device is provided, which comprises means or a unit for performing the communication method in the first aspect or any one of the possible implementations of the first aspect, or any one of the possible implementations of the second aspect or the second aspect, or any one of the possible implementations of the third aspect or the third aspect.

In a fifth aspect, a communication device is provided, which includes a processor and a transceiver, where the processor is configured to execute a program, and when the processor executes the program, the processor and the transceiver implement the first aspect or any one of the possible implementations of the first aspect, or the second aspect or any one of the possible implementations of the second aspect, or the third aspect or any one of the possible implementations of the third aspect.

Optionally, the communication device may further comprise a memory for storing the program executed by the processor.

An example of the communication device may be a session management network element, an access network device, or an access management network element.

A sixth aspect provides a computer readable storage medium storing program code for execution by a synchronous apparatus, the program code comprising instructions for implementing the first aspect or any one of the possible implementations of the first aspect, or any one of the possible implementations of the second aspect or the second aspect, or the method in any one of the possible implementations of the third aspect or the third aspect.

A seventh aspect provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the first aspect or any one of the possible implementations of the first aspect, or any one of the possible implementations of the second aspect or the second aspect, or the method of any one of the possible implementations of the third aspect or the third aspect.

In an eighth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is configured to communicate with an external device, and the processor is configured to implement the first aspect or any one of the possible implementations of the first aspect, or any one of the possible implementations of the second aspect or the second aspect, or the method in any one of the possible implementations of the third aspect or the third aspect.

Optionally, the chip may further include a memory, where instructions are stored in the memory, and the processor is configured to execute the instructions stored in the memory, and when the instructions are executed, the processor is configured to implement the first aspect or any one of the possible implementations of the first aspect, or any one of the possible implementations of the second aspect or the second aspect, or the method in any one of the possible implementations of the third aspect or the third aspect.

Alternatively, the chip may be integrated on a session management network element, an access network device, or an access management network element.

Drawings

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

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

Fig. 3 shows an example of the management flow of QoS control in a 5G network.

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

Fig. 5 shows a schematic flow chart of another communication method provided in the embodiment of the present application.

Fig. 6 shows a schematic flow chart of another communication method provided in the embodiment of the present application.

Fig. 7 shows a schematic flow chart of another communication method provided by the embodiment of the present application.

Fig. 8 shows a schematic flow chart of another communication method provided in the embodiment of the present application.

Fig. 9 shows a schematic flow chart of another communication method provided in the embodiment of the present application.

Fig. 10 shows a schematic flow chart of another communication method provided by the embodiment of the present application.

Fig. 11 shows a schematic flow chart of another communication method provided in the embodiment of the present application.

Fig. 12 shows a schematic diagram of an apparatus for wireless communication according to an embodiment of the present application.

Fig. 13 is a schematic diagram illustrating another apparatus for wireless communication according to an embodiment of the present disclosure.

Fig. 14 is a schematic diagram illustrating another apparatus for wireless communication according to an embodiment of the present disclosure.

Fig. 15 shows a schematic structural diagram of a network device according to an embodiment of the present application.

Detailed Description

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

The technical scheme of the embodiment of the application can be applied to various communication systems, for example: for example: global system for mobile communications (GSM) systems, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, system architecture evolution (system architecture evolution, SAE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD), universal mobile telecommunications system (universal mobile telecommunications system, UMTS), universal internet access (WiMAX), wireless telecommunication system (WiMAX), and so on, and new generation communication systems (NR 5 ) and so on.

Fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present application. Fig. 1 includes an access network device, a core network device, and a terminal device. The terminal equipment is connected with the access network equipment, and the access network equipment is connected with the core network equipment, so that the terminal equipment can communicate with the core network equipment through the access network equipment.

The terminal device in the embodiment of the present application may also be referred to as: user Equipment (UE), Mobile Station (MS), Mobile Terminal (MT), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device, etc.

The terminal device may be a device providing voice/data connectivity to a user, e.g. a handheld device, a vehicle mounted device, etc. with wireless connection capability. Currently, some examples of terminals are: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (autonomous driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety, a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol) phone, a PDA (personal digital assistant), a wireless local loop (wireless local) phone, a SIP (personal digital assistant), a personal digital assistant (personal digital assistant) device with wireless communication function, and a wireless terminal with wireless communication function, A computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in an evolved Public Land Mobile Network (PLMN), and the like, which is not limited in this embodiment of the present application.

By way of example and not limitation, in the embodiments of the present application, a wearable device may also be referred to as a wearable smart device, which is a generic term for intelligently designing daily wearing and developing wearable devices, such as glasses, gloves, watches, clothing, shoes, and the like, by applying wearable technology. A 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 realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.

In addition, in the embodiment of the present application, the terminal device may also be a terminal device in an internet of things (IoT) system, where IoT is an important component of future information technology development, and a main technical feature of the present application is to connect an article with a network through a communication technology, so as to implement an intelligent network with interconnected human-computer and interconnected objects.

The various terminal devices described above, if located on a vehicle (e.g., placed in or installed in the vehicle), may be considered to be vehicle-mounted terminal devices, which are also referred to as on-board units (OBUs), for example.

In this embodiment, the terminal device may further include a relay (relay). Or, it is understood that any device capable of data communication with a base station may be considered a terminal device.

In this embodiment, the access network device is a device in a radio access network (R) AN, or is a RAN node that accesses a terminal device to a radio network, or a device in a next generation radio access network (NG-RAN). For example, by way of example and not limitation, as access network devices, mention may be made of: a gbb, a Transmission Reception Point (TRP), an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), or a wireless fidelity (Wifi) Access Point (AP), etc.

In one network configuration, the access network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node), and a RAN device of a DU node.

The access network device provides service for a cell, and a terminal device communicates with the access network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the access network device (e.g., a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell (small cell), where the small cell may include: urban cell (metro cell), micro cell (microcell), pico cell (pico cell), femto cell (femto cell), etc., and these small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission service.

Fig. 2 shows a schematic diagram of a network architecture suitable for use in embodiments of the present application. The network architecture is a 5G network architecture diagram defined by the third generation partnership project (3 GPP) TS 23.501.

The access and mobility management function (AMF) is responsible for access and mobility management functions, and the main functions include management of user registration, reachability detection, selection of SMF node, mobility state transition management, and the like. Wherein the AMF may communicate with the UE through AN N1 interface and communicate with the (R) AN through AN N2 interface.

The Session Management Function (SMF) is responsible for session management functions, and mainly functions to control establishment, modification, and deletion of sessions, selection of user plane nodes, and the like. Wherein the SMF may communicate with the UPF via an N4 interface.

The User Plane Function (UPF) mainly provides user plane support, and the main functions are packet routing and forwarding, serving as a session anchor point, serving as an uplink classifier to support routing traffic to a local data network, serving as a branch point to support multi-homed PDU session (multi-homed PDU session), and the like. The (R) AN and the UPF can communicate through AN N3 interface, and the UPF can communicate through AN N9 interface.

The Policy Control Function (PCF) is responsible for user policy management, and the main function is a policy decision point, which provides rules such as detection based on service data flow or application, quality of service (QoS), and flow-based charging control. And provides policies to the AMF and SMF, such as slice selection policies to the AMF and session management policies to the SMF.

The main function of Unified Data Management (UDM) is to store user data, such as subscription information, authentication/authorization information, and the like.

An authentication service function (AUSF) is an authentication and authorization service module, and is responsible for performing authentication and authorization on access of the UE.

Application Function (AF), the main function is to interact with the 3GPP core network to provide services to affect the traffic flow routing, policy control, etc.

A Network Exposure Function (NEF), which securely opens services and capabilities provided by the 3GPP network function, such as services and capabilities to third parties, edge computing, AF, and the like. Internal and external information may also be converted, such as converting information outside the 3GPP to information inside the 3 GPP.

A Data Network (DN), such as a carrier service, internet access or a third party service. The DN and UPF may communicate via an N6 interface.

A network data analysis function (NWDAF), which provides a network data acquisition and analysis function based on technologies such as big data and artificial intelligence.

A network storage function (NRF) provides network element registration and discovery, and enables Network Functions (NFs) to discover each other, thereby performing communication.

The management flow of QoS control in a 5G network is described below in conjunction with fig. 3. Referring to fig. 3, an example of a management flow for QoS control in a 5G network is shown. Hereinafter, the management flow of the QoS control will be described by taking the network architecture in fig. 2 as an example.

The SMF determines to establish the QoS flow 300.

Illustratively, the SMF may determine to establish the QoS flow based on local policy or based on Policy and Charging Control (PCC) rules obtained from the PCF.

301, the SMF sends a Packet Detection Rule (PDR) and a QoS Enforcement Rule (QER) to the UPF.

The SMF sends QoS profile information for the QoS flow to the RAN through the AMF 302. Illustratively, the QoS profile information may include a Guaranteed Flow Bit Rate (GFBR), a 5G QoS identifier (5G QoS identifier, 5QI), or a Maximum Bit Rate (MBR) of the QoS flow, and the like. For example, the QoS profile information of a GBR QoS flow may contain a Guaranteed Flow Bit Rate (GFBR), a 5G QoS identifier (5G QoS identifier, 5QI) of the GBR QoS flow. As another example, the QoS profile information of a non-GBR (non-GBR) QoS flow may include the 5QI and MBR of the non-GBR QoS flow.

Optionally, the QoS document information may further include QoS features corresponding to 5QI, such as Packet Delay Budget (PDB) and Packet Error Rate (PER). In some embodiments, the 5QI corresponding QoS features may also be preconfigured on the RAN.

The SMF sends a QoS rule (rule) to the UE via the AMF, RAN, 303, which contains QoS control information.

Specifically, the PCC rule, PDR, QER, QoS rule, and the like may refer to descriptions in the prior art, and are not described herein again. Through the above steps 300 to 303, the establishment of QoS flows can be completed among the UE, the RAN, and the UPF.

304, the RAN establishes a Data Radio Bearer (DRB) with the UE over the air interface according to the QoS document information. The RAN and the UE may also store the mapping relationship of QoS flows and DRBs, respectively.

And 305, executing the modification and deletion process of the QoS flow.

In some embodiments, when the demand corresponding to the QoS flow changes, the SMF may initiate a QoS flow modification procedure to update relevant QoS information on the UE, RAN, and UPF. Illustratively, the QoS information is, for example, QER, QoS document information, QoS rule, and the like.

In some embodiments, when the traffic corresponding to the QoS flow is terminated, the SMF may initiate a deletion procedure for the QoS flow, deleting the relevant QoS information on the UE, RAN, and UPF.

The SMF sends the QoS notification control parameters to the RAN 306.

Illustratively, for some important QoS flows, such as Guaranteed Bit Rate (GBR) QoS flows, the SMF may enable a notification control mechanism, sending QoS notification control parameters (QoS notification control parameter) to the RAN. When the resources cannot meet the requirement of the GBR QoS flow, the RAN may send a notification message to the SMF according to the QoS notification control parameter to indicate that the current resources cannot meet the requirement of the GBR QoS flow.

As a specific example, in a non-mobile scenario, when the RAN detects that the current resources cannot meet the requirement of the QoS profile information of the GBR QoS flow, for example, the RAN cannot meet the Guaranteed Flow Bit Rate (GFBR), Packet Delay Budget (PDB), or Packet Error Rate (PER) of the GBR QoS flow, the RAN may perform step 310, that is, send a notification message to the SMF to indicate that the RAN cannot meet the requirement of the GBR QoS flow, that is, cannot meet the QoS profile information of the GBR QoS flow. The RAN may then reserve the GBR QoS flow (i.e., the RAN does not release the GBR QoS flow).

In addition, in the 5G communication system, an Alternative QoS Profile (AQP) mechanism is introduced. Under the AQP mechanism, the management flow of QoS control in fig. 3 further includes steps 307 to 309.

It should be noted that there may be a RAN supporting AQP information processing and a RAN not supporting AQP information processing in the communication system. Steps 307 through 309 are not performed for RANs that do not support AQP information processing. Here, processing the AQP information refers to QoS processing of QoS flows according to the AQP information. Wherein the QoS treatment may be a decreasing QoS parameter of a QoS flow (i.e., downgrading QoS treatment or downgrading treatment), an increasing QoS parameter of a QoS flow (i.e., upgrading QoS treatment or upgrading treatment), or rejecting a QoS flow, etc. Otherwise, when the RAN does not have the AQP information identification capability, or the RAN has the AQP information identification capability but the RAN does not perform QoS processing on the QoS flow according to the AQP information, the RAN may be classified as not supporting AQP information processing.

307, the SMF sends AQP information to the RAN.

Specifically, under the AQP mechanism, the SMF may send, to the RAN, AQP information corresponding to the QoS flow, where the AQP information includes at least one AQP information corresponding to the QoS flow, that is, the number of the AQP information may be one or more. For example, when the AQP information includes a plurality of AQP information, the plurality of AQP information may form a list, which may be referred to as an AQP list.

Correspondingly, the RAN receives AQP information for the QoS flow. When the RAN determines that the current resources cannot satisfy the QoS profile information of the QoS flow, the RAN may determine whether the current resources can satisfy the AQP information corresponding to the QoS flow.

As a specific example, in a non-mobile scenario, if the RAN supports processing AQP information, when the RAN determines that current resources cannot satisfy some important QoS flows, such as QoS profile information of GBR QoS flows, the RAN may determine whether the current resources of the RAN can satisfy one of the AQP information in an AQP list according to a priority of the AQP information in the AQP list corresponding to the GBR QoS flows from top to bottom.

As another specific example, in a mobile scenario where the UE moves and is handed over from the source RAN to the target RAN, the QoS flow of the UE is handed over from the source RAN to the target RAN, and the source RAN sends the QoS profile information of the GBR QoS flow and the AQP list to the target RAN. If the target RAN supports processing the AQP information, when the target RAN determines that the current resources cannot satisfy the QoS profile information of the GBR QoS flow, the target RAN may determine, from high to low, whether the current resources of the target RAN may satisfy one of the AQP information in the AQP list according to the priority of the AQP information in the AQP list corresponding to the GBR QoS flow.

The RAN downgrades 308 the QoS flow.

Illustratively, when the RAN determines that the current resources cannot satisfy the QoS profile information of a QoS flow and the current resources satisfy AQP information (e.g., satisfy one of the AQP information in the AQP list), the RAN may downgrade the QoS flow according to the AQP information.

Continuing with the example in step 307, for a non-mobile scenario, one possible scenario is that if the resources of the RAN satisfy one of the AQP information in the AQP list, the RAN may downgrade the GBR QoS flow according to the AQP information. Optionally, the RAN may also perform step 309, i.e. the RAN informs the SMF of the AQP information that the current resources are met.

Another possible scenario is that if the resources of the RAN do not satisfy any of the AQP information in the AQP list, step 310 may be performed, where the RAN sends a notification message to the SMF to indicate that the current resources of the RAN do not satisfy the requirements of the GBR QoS flow, i.e., do not satisfy the QoS profile information and AQP information of the GBR QoS flow. The RAN may then reserve the GBR QoS flow, i.e. the RAN does not release the GBR QoS flow.

In a mobile scenario, it is a possible scenario that if the resources of the RAN satisfy one of the AQP information in the AQP list, the target RAN accepts the GBR QoS flow and performs degradation processing on the GBR QoS flow according to the AQP information. Optionally, step 309 may also be performed.

Another possible scenario is that the target RAN rejects the GBR QoS flow if the resources of the RAN do not satisfy any of the AQP information in the AQP list. Optionally, step 310 may be further performed, in which the RAN sends a notification message to the SMF to indicate that the current resources of the RAN do not satisfy the requirements of the GBR QoS flow, i.e., do not satisfy the QoS profile information and AQP information of the GBR QoS flow.

Optionally, 311, after receiving the notification that the current resources sent by the RAN do not satisfy the requirement of the QoS flow, the SMF notifies the PCF that the current resources of the RAN do not satisfy the requirement of the QoS flow.

In some optional embodiments, the SMF may further notify the AF that the current resources of the RAN do not meet the requirement of the QoS flow, which is not limited in this embodiment of the present application.

In some other embodiments, in a mobile scenario where the UE moves and is handed over from the source RAN to the target RAN, the QoS flow of the UE is also handed over from the source RAN to the target RAN, and the target RAN also receives the QoS profile information of the QoS flow and the AQP information. However, if the target RAN does not support the handling of AQP information, when the target RAN determines that the current resources cannot satisfy the QoS profile information of the GBR QoS flow, the target RAN cannot handle the QoS flow according to the AQP information corresponding to the QoS flow, but directly rejects the QoS flow.

As can be seen from the above description, when there may be a RAN supporting AQP information processing and a RAN not supporting AQP information processing in a communication system, in a non-mobile scenario, the SMF receives a notification message sent by the RAN in the following cases 1 and 2, so as to indicate that the current resources of the RAN cannot meet the QoS flow requirement.

Case 1: the RAN does not support handling AQP information. In this case, the RAN determines that the current resources cannot satisfy the QoS profile information of the QoS flow, and does not attempt to process, e.g., downgrade, the QoS flow according to the AQP information corresponding to the QoS flow. At this time, the SMF cannot perceive that the RAN is not attempting degradation processing on the QoS flow, but directly considers that the resources of the RAN cannot satisfy the QoS profile information corresponding to the QoS flow and the AQP information corresponding to the QoS flow, thereby causing the inaccuracy of the notification message.

Case 2: the RAN supports handling AQP information. In this case, the RAN attempts to process, e.g., downgrade, the QoS flow based on the AQP information corresponding to the QoS flow. However, the current resources of the RAN still cannot satisfy the AQP information corresponding to the QoS flow, for example, cannot satisfy the AQP information of the lowest priority in the AQP list corresponding to the QoS flow. At this time, the notification message is accurate, that is, the resources of the RAN cannot satisfy the QoS profile information corresponding to the QoS flow and the AQP information of the QoS flow.

In addition, when there may be a RAN supporting AQP information processing and a RAN not supporting AQP information processing in the communication system, in a mobile scenario, the target RAN rejects the QoS flow of the terminal device for handover in the following cases 3 and 4, or sends a notification message to the SMF to indicate that the current resources of the RAN cannot meet the requirements of the QoS flow.

Case 3: the target RAN does not support handling AQP information. In this case, when the target RAN determines that the current resources cannot satisfy the QoS profile information of the QoS flow, the target RAN does not further attempt to process, e.g., downgrade, the QoS flow according to the QoS information corresponding to the QoS flow, but directly rejects the QoS flow. At this point, the target RAN may not need to reject the QoS flow or the notification message sent by the target RAN to the SMF is inaccurate.

In case 4, the target RAN supports handling AQP information. In this case, when the target RAN determines that the current resources cannot satisfy the QoS profile information of the QoS flow, the target RAN further attempts to process, for example, downgrade, the QoS flow according to the QoS information corresponding to the QoS flow. However, the current resources of the target RAN still cannot satisfy the AQP information corresponding to the QoS flow, for example, cannot satisfy the AQP information of the lowest priority in the AQP list corresponding to the QoS flow. The target RAN rejects the QoS flow at this point. At this point, the target RAN may not need to reject the QoS flow or the notification message sent by the target RAN to the SMF is accurate.

That is, when there may be a RAN supporting AQP information processing and a RAN not supporting AQP information processing in a communication system, for the RAN not supporting AQP information processing, when its resources do not satisfy QoS profile information of a QoS flow, the RAN cannot perform QoS processing according to AQP information corresponding to the QoS flow. However, the existing notification control mechanisms are implemented based on that the RAN can perform QoS processing according to the AQP information, and therefore cannot accurately perform QoS control.

In view of this, the present application provides a communication method and apparatus. The core network device in the communication system can determine whether the access network device performs the QoS treatment on the QoS flow according to the AQP information of the QoS flow, and can perform the QoS treatment on the QoS flow according to the AQP information under the condition that the access network device does not perform the QoS treatment on the QoS flow according to the AQP information of the QoS flow, thereby facilitating accurate QoS control.

The communication method and the communication apparatus provided in the present application will be described in detail below with reference to the accompanying drawings.

The technical solution of the present application may be applied to a wireless communication system, for example, the communication system shown in fig. 1 or the communication system shown in fig. 2. Communication devices in a wireless communication system may have wireless communication connections between them. One of the communication devices may be, for example, a core network device or a chip configured in the core network device, and the other device may be, for example, an access network device or a chip configured in the access network device. The embodiment of the present application does not limit this.

In this embodiment, the communication system may include two access network devices, that is, a first access network device and a second access network device. Wherein, in some embodiments, the first access network device and the second access network device are the same access network device. For example, in a non-mobile scenario, the first access network device and the second access network device are the same access network device. For another example, in a mobile scenario, the first access network device and the second access network device may also be the same access network device, for example, both are target access network devices (T-RANs). In yet other embodiments, the first access network device and the second access network device are different access network devices. For example, in a mobile scenario, the first access network device is a source access network device (S-RAN), and the second access network device is a target access network device.

Fig. 4 illustrates a schematic flow chart of a communication method 400 provided by an embodiment of the present application from the perspective of device interaction. The method 400 is performed by an access network device and a session management network element. Illustratively, the access network device may be a RAN in a non-mobile scenario, or a T-RAN or an S-RAN in a mobile scenario, and the session management network element may be an SMF in fig. 2. As shown in fig. 4, method 400 includes steps 410 through 450. Wherein step 420 and step 430 are optional steps.

And 410, the session management network element sends the QoS document information and the AQP information of the first QoS flow.

Illustratively, in the QoS control management procedure, the session management network element may send the QoS profile information and the AQP information of the first QoS flow to the access network device through the access management network element (e.g., AMF). The access network device may be a RAN in a non-mobile scenario or an S-RAN in a mobile scenario. That is, in a non-mobile scenario, the RAN receives the QoS profile information and the AQP information of the first QoS flow from the session management network element, and in a mobile scenario, the S-RAN receives the QoS profile information and the AQP information of the first QoS flow from the session management network element.

Specifically, the QoS profile information and the AQP information can be referred to the description in fig. 3, and are not described herein again for brevity.

The access network device determines the indication information 420. Wherein the indication information is used to determine that the access network device does not perform QoS processing for the first QoS flow according to the AQP information of the first QoS flow. Here, the QoS process is, for example, to lower QoS parameters of a QoS flow (i.e., downgrade QoS process or downgrade process), to raise QoS parameters of a QoS flow (i.e., upgrade QoS process or upgrade process), or to reject a QoS flow.

In some embodiments, the access network device may determine whether to generate the indication information according to whether the access network device performs QoS processing for the first QoS according to the AQP information of the first QoS flow, or according to whether the access network device has a capability of supporting the processing of the AQP information.

Illustratively, the access network device has a capability of supporting processing of the AQP information, and may refer to the access network device having an ability of recognizing the AQP information and being capable of performing QoS processing on the QoS flow according to the AQP information. On the contrary, the access network device does not have the capability of supporting the processing of the AQP information, which may mean that the access network device does not have the capability of identifying the AQP information, or the access network device has the capability of identifying the AQP information, but does not perform QoS processing on the QoS flow according to the AQP information.

In addition, in the embodiments of the present application, "to support AQP information" may be equivalent to "to support AQP processing", and both represent the same meaning.

As one implementation manner, when it is determined that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, indication information #1 is generated for indicating that the access network device does not perform QoS flow processing on the first QoS flow according to the AQP information of the first QoS flow. In some specific embodiments, the indication information #1 may also be a first cause value. At this time, the indication information #1 may be used (by the session management network element) to determine that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow.

It should be noted that, when the access network device is generating the indication information #1, the access network device may have a capability of supporting processing of the AQP information but does not perform QoS processing on the first QoS flow according to the AQP information, or does not have the capability of supporting processing of the AQP information, which is not limited in this embodiment of the present application.

As another implementation, when it is determined that the access network device does not have the capability of supporting the processing of the AQP information, indication information #2 is generated for indicating that the access network device does not have the capability of supporting the processing of the AQP information. At this time, the indication information #2 may be used (by the session management network element) to determine that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow.

It will be appreciated that when an access network device does not have the capability to support the processing of AQP information, the access network device is necessarily unable to process a first QoS flow according to its AQP information.

In other embodiments, when it is determined that the access network device performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow, the access network device may generate other indication information, for example, indication information #3, for instructing the access network device to perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow. In some specific embodiments, the indication information #3 may also be a second cause value.

It can be appreciated that when an access network device processes a first QoS flow according to its AQP information, the access network device necessarily has the capability to support the processing of the AQP information.

Alternatively, in other embodiments, when it is determined that the access network device has the capability of supporting the processing of AQP information, the access network device may generate other indication information, for example, indication information #4, for indicating that the access network device has the capability of supporting the processing of AQP information.

It will be appreciated that when an access network device has the capability to support the processing of AQP information, the access network device may generally process the first QoS information in accordance with the AQP information for the first QoS flow.

In some possible embodiments, the RAN does not generate the indication information without the access network device performing QoS processing for the first QoS flow in accordance with the AQP information, or without the access network device having the capability to support processing of the AQP information. And when the access network equipment performs the QoS processing on the first QoS flow according to the AQP information or the access network equipment has the capability of supporting the processing of the AQP information, generating indication information, wherein the indication information is used for indicating that the QoS processing is performed on the first QoS flow according to the AQP information or the access network equipment has the capability of supporting the processing of the AQP information.

In some possible embodiments, the RAN does not generate the indication information if the access network device performs QoS processing for the first QoS flow according to the AQP information, or if the access network device is capable of supporting the capability of processing the AQP information. And under the condition that the access network equipment does not perform QoS processing on the first QoS flow according to the AQP information or the access network equipment does not have the capability of supporting the processing of the AQP information, generating indication information, wherein the indication information is used for indicating that the access network equipment does not perform QoS processing on the first QoS flow according to the AQP information or that the access network equipment does not have the capability of supporting the processing of the AQP information.

For example, a first access network device may determine indication information for determining that a second access network device is not QoS treating a first QoS flow based on AQP information for the first QoS flow. At this time, step 420 includes the following three possible cases.

In the first case, in the embodiment of the non-mobile scenario, the first access network device and the second access network device are the same access network device, and the access network device that receives the QoS profile information and the AQP information of the first QoS flow from the session management network element in step 410 is the same access network device.

At this time, the access network device may determine whether to generate the indication information according to whether to perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, or according to whether to support the capability of processing the AQP information.

In a second case, in an embodiment of a mobile scenario, both the first access network device and the second access network device are T-RANs. And the access network device receiving the QoS profile information and AQP information of the first QoS flow in step 410 is the S-RAN.

As an example, during the process of switching the terminal device from the S-RAN to the T-RAN, the QoS flow (e.g., including the first QoS flow) of the terminal device is also switched from the S-RAN to the T-RAN, and accordingly, the S-RAN sends the QoS profile information and the AQP information of the first QoS flow to the T-RAN.

At this time, the T-RAN may determine whether to generate the indication information according to whether it performs QoS processing on the first QoS flow according to AQP information of the first QoS flow, or according to whether it has a capability of supporting the processing of the AQP information.

In a third case, in the embodiment of the mobile scenario, the first access network device is an S-RAN, the second access network device is a T-RAN, and the access network device receiving the QoS document information and the AQP information of the first QoS flow in step 410 is the S-RAN.

At this time, the S-RAN may determine whether to generate the indication information according to whether the T-RAN performs QoS processing on the first QoS flow according to AQP information of the first QoS flow, or according to whether the T-RAN has a capability of supporting the processing of the AQP information.

430, the access network equipment sends the indication information. Wherein, the indication information is the indication information in step 420, and the access network device that determines the indication information in step 420 are the same access network device.

Illustratively, the access network device may send the indication information to a session management network element, or other network elements in the core network device (e.g., AMF, or PCF, or UDM).

For example, when the indication information indicates that the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, the indication information may be sent to the session management network element. For another example, when the indication information is used to indicate that the access network device does not have the capability of processing the AQP information, the indication information may be sent to a session management network element, or an AMF, or a PCF, or a UDM, which is not limited in this embodiment of the present application.

In some embodiments, after generating the indication information #1, the access network device may send the indication information #1 to the session management network element, i.e., explicitly indicate to the session management network element that the access network device does not perform QoS flow processing for the first QoS flow according to the AQP information of the first QoS flow.

In some embodiments, after generating the indication information #2, the access network device may send the indication information #2 to the session management network element, i.e., the session management network element explicitly indicates that the access network device does not have the capability to support processing AQP information.

In some embodiments, after generating the indication information #3, the access network device may send the indication information #3 to the session management network element, that is, explicitly indicate to the session management network element that the access network device has performed QoS flow processing on the first QoS flow according to the AQP information of the first QoS flow.

In some embodiments, after generating the indication information #4, the access network device may send the indication information #4 to the session management element, i.e., the session management element explicitly indicates that the access network device has the capability to support processing AQP information.

Alternatively, in other embodiments, the access network device does not generate the indication information when the first QoS flow is not QoS-processed according to the AQP information of the first QoS flow or does not have a capability of supporting processing of the AQP information, and generates the indication information #3 when the first QoS flow is QoS-processed according to the AQP information of the first QoS flow or generates the indication information #4 when the first QoS flow has a capability of supporting processing of the AQP information. Illustratively, the access network equipment is predefined to perform the above-described operations, for example.

In this way, when the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, or does not have the capability of supporting the processing of the AQP information, no indication information is sent to the session management network element. And the access network equipment may send the indication information #3 to the session management network element when performing QoS processing on the first QoS according to the first QoS flow AQP information, or send the indication information #4 to the session management network element when having the capability of supporting the processing of the AQP information. Accordingly, the access network device may implicitly indicate that the access network device does not QoS process the first QoS flow according to its AQP information, or does not have the capability to support processing of the AQP information, by not sending the indication information to the session management network element.

Alternatively, in other embodiments, the access network device may be predefined to generate the indication information #1 when the first QoS flow is not QoS processed according to its AQP information, or to generate the indication information #2 when it does not have the capability to support processing of AQP information. And when the first QoS flow is QoS-processed according to the AQP information of the first QoS flow, or when the capability of supporting the processing of the AQP information is provided, the indication information is not generated.

In this way, when the access network device does not perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, the indication information #1 is transmitted to the session management network element, or when it does not have the capability of supporting the processing of the AQP information, the indication information #2 is transmitted to the session management network element. And when the first QoS flow is subjected to QoS processing according to the AQP information of the first QoS flow or has the capability of supporting the processing of the AQP information, no indication information is sent to the session management network element. Therefore, the access network device may implicitly indicate that the access network device is capable of performing QoS processing on the first QoS flow according to the AQP information of the first QoS flow or has a capability of supporting the processing of the AQP information by not sending the indication information to the session management network element.

The session management element determines 440 that the access network device is not QoS processing the first QoS flow according to the AQP information.

As an example, in a non-mobile scenario, the access network device is the same access network device as the access network device that receives the QoS profile information and the AQP information of the first QoS flow in step 410, and in a mobile scenario, the access network device is a T-RAN.

In some embodiments, when step 430 is performed, and in step 430, the access network device sends the indication information (for example, the indication information #1 or the indication information #2 described above) to the session management network element, or other network elements in the core network forward the received indication information to the session management network element, the session management network element may determine, according to the indication information, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information.

In some embodiments, when the access network device does not QoS-process the first QoS flow according to the AQP information of the first QoS flow, or does not have the capability of supporting the processing of the AQP information, without generating the indication information, if the session management network element does not receive the indication information (e.g., the above-mentioned indication information #3 or indication information #4) from the access network device within a preset time, the session management network element may determine that the access network device does not QoS-process the first QoS flow according to the AQP information.

In some other embodiments, when the access network device sends the indication information #3 or the indication information #4 to the session management network element, or when another network element in the core network forwards the received indication information #3 or the received indication information #4 to the session management network element, the session management network element may determine, according to the indication information #3 or the indication information #4, that the access network device performs QoS processing on the first QoS according to the AQP information.

In some further embodiments, when the access network device does not generate the indication information when performing the QoS treatment on the first QoS flow according to the AQP information of the first QoS flow or when having the capability of supporting the treatment of the AQP information, if the session management network element does not receive the indication information (e.g., the above-mentioned indication information #1 or indication information #2) from the access network device within the preset time, the session management network element may determine that the access network device performs the QoS treatment on the first QoS flow according to the AQP information.

In some embodiments, the session management network element itself may pre-acquire and store the capability information of the access network device without relying on steps 420 and 430. The capability information may include, among other things, whether capabilities for processing AQP information are supported. As an example, the session management network element may store an access network device Identification (ID) and capability information of whether the access network device corresponding to the access network device identification supports processing of AQP information.

Thus, in an implementation manner in which the session management network element determines that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, the session management network element may obtain the identifier of the access network device, and further determine whether the access network device has the capability of supporting the processing of the AQP information according to a correspondence between the identifier of the access network device obtained in advance and whether the access network device has the capability of supporting the processing of the AQP information. When the identity of the access network device corresponds to not having the capability to support processing of AQP information, it may be determined that the access network device did not QoS process the first QoS flow in accordance with the AQP information. When the access network device's identity corresponds to having the capability to support processing AQP information, it may be determined that the access network device has QoS-processed the first QoS flow in accordance with the AQP information.

In some optional embodiments, the session management network element may determine whether the access network device performs QoS processing on the first QoS flow according to the AQP information, in case that it is determined that the resources of the access network device do not satisfy the QoS profile information of the first QoS flow. As an example, the QoS information of the AQP information, e.g., the PDB, corresponding to the first QoS flow at this time may be lower than the QoS information of the QoS profile information of the first QoS flow. Correspondingly, the QoS treatment is performed on the first QoS flow according to the AQP information, that is, the QoS reduction treatment is performed on the first QoS flow according to the AQP information.

In some optional embodiments, when the QoS information of the AQP information corresponding to the first QoS flow, for example, the QoS information in the QoS profile information with a PDB higher than the first QoS, performing QoS processing on the first QoS flow according to the AQP information is to perform QoS raising processing on the first QoS flow according to the AQP information.

In some optional embodiments, when the access network device cannot satisfy the AQP information of the first QoS flow according to the self condition (e.g., resource), performing QoS processing on the first QoS flow according to the AQP information is to reject the first QoS flow according to the AQP information.

And 450, the session management network element performs QoS processing on the first QoS flow according to the AQP information.

When the session management network element determines that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, the session management network element may perform QoS processing on the first QoS flow according to the AQP information. Here, the QoS treatment is performed on the first QoS flow, including upgrading the QoS treatment to the first QoS flow, or downgrading the QoS treatment to the first QoS flow, or rejecting the first QoS flow. Specifically, the QoS process may be referred to the description in step 440 for brevity. And will not be described in detail herein.

For example, when the session management network element determines that the resources of the access network device do not satisfy the QoS profile information of the first QoS flow and the access network device does not perform QoS processing on the first QoS flow according to the AQP information, the session management network element may attempt to perform QoS degradation processing on the first QoS flow according to the AQP information corresponding to the first QoS flow, for example, send the AQP information to the access network device, thereby implementing QoS degradation processing on the first QoS flow.

As a possible implementation manner, in a mobile scenario, after the handover procedure is ended, the SMF may initiate a session modification procedure, establish a first QoS flow according to AQP information of the first QoS flow, or reject the first QoS flow in case the T-RAN does not satisfy the AQP information, for example, any AQP information in an AQP list. In a non-mobile scenario, the SMF may initiate a session modification procedure to modify the first QoS flow based on the AQP information for the first QoS flow. When the AQP information is in the form of a list, i.e., an AQP list, the SMF attempts to establish or modify the first QoS flow according to the priority of the AQP list.

As a specific example, when the AQP information is an AQP list, AQP information of a high priority in the AQP list may be transmitted to the RAN. For example, the bandwidth information in the QoS document information is 100Mbps, and the bandwidth information in the AQP list is {50Mbs, 20Mbps }. When the RAN does not meet the QoS requirements for bandwidth information of 100Mbps, the session management network element may send 50Mbps (i.e., attempt to downgrade from the highest priority in the AQP list) to the RAN in the initiated session modification procedure. And if the RAN cannot meet the QoS requirement of 50Mbps, the session management network element further initiates a session modification flow and sends the 20Mbps to the RAN. If the RAN can meet the 20Mbps requirement, the RAN transmits the traffic flow of the first QoS flow with the QoS requirement of 20 Mbps. If the RAN cannot meet the 20Mbps requirement, the session management network element may decide to release the first QoS flow, or alternatively, reserve the first QoS flow with QoS parameters that the RAN's current resources can meet.

That is, when the RAN fails to satisfy the AQP information of the lowest priority in the AQP list, the session management network element may determine that the RAN fails to satisfy the first QoS flow, i.e., fails to satisfy the AQP information of the first QoS flow. The first QoS flow may be released when the session management network element determines that the RAN is unable to satisfy the AQP information for the first QoS flow.

In the following, several specific examples provided by the embodiments of the present application will be described with reference to fig. 5 to 11, taking a moving scene as an example. The access network equipment in the mobile scene comprises source access network equipment and target access network equipment. Specifically, the following description will take the example that the session management network element is an SMF, the source access network device is an S-RAN, the target access network device is a T-RAN, and the terminal device is a UE. For the implementation methods of the chip in the SMF, the chip in the S-RAN, the chip in the T-RAN, and the chip in the UE, reference may be made to the specific descriptions of the SMF, the T-RAN, the S-RAN, and the UE, and no repeated description is made.

In the following example, the SMF can distinguish whether the T-RAN performs QoS processing on the QoS according to the AQP information of the QoS flow in the handover procedure, for example, distinguish between case 3 and case 4 above. In the following embodiments, the T-RAN may reject the QoS flow, or reserve the QoS flow, or accept the QoS flow when resources are not full of the QoS flow, which is not limited in the embodiments of the present application. In the following, the example that the T-RAN rejects the QoS flow is taken as an example for explanation, but the embodiment of the present application is not limited to this, and for example, the T-RAN may also reserve the QoS flow or accept the QoS flow.

Fig. 5 shows a schematic flow chart of a communication method provided in an embodiment of the present application. Wherein the T-RAN may send a cause value to the SMF, so that the SMF determines whether the T-RAN performs QoS treatment on the QoS flow according to the AQP information corresponding to the QoS flow according to the cause value. As shown in fig. 5, the method includes steps 501 to 511.

Before the UE is handed over from the S-RAN to the T-RAN, the UE may communicate with the core network device through the S-RAN, for example, for Uplink (UL)/downlink (UL) data transmission. Illustratively, the core network device is a UPF.

501, the S-RAN makes handover decisions.

Illustratively, the S-RAN makes a handover decision (HO decision), e.g., decides to handover to the T-RAN, based on the UE' S measurement report.

Optionally, 502, the S-RAN determines whether the T-RAN supports handling AQP information.

For example, in a case where the S-RAN supports AQP handling (AQP handling), the S-RAN may further determine whether the T-RAN supports AQP handling. When the T-RAN supports processing the AQP information, then the AQP information corresponding to the QoS flow is sent (e.g., may be included in the handover request) to the T-RAN. When the T-RAN does not support the handling of AQP information, then AQP information corresponding to the QoS flow may not be sent (e.g., may not be included in the handover request) to the T-RAN.

In some optional embodiments, before step 502, for example, when the access network device is powered on, the S-RAN may exchange information with a plurality of RANs (including the T-RAN) in the periphery, so as to obtain capability information of the plurality of RANs, where the capability information includes whether or not the capability of processing the AQP information is supported.

503, the S-RAN sends a handover request to the T-RAN.

Illustratively, the handover request may include a list of sessions to be handed over, an identification of the QoS flow, and QoS profile information (QoS profile) corresponding to the QoS flow. Optionally, the handover request may further include AQP information corresponding to the QoS flow, for example, an AQP list, which is not limited in this embodiment.

The T-RAN performs admission control 504.

Illustratively, the T-RAN may perform admission control on QoS flows. When the T-RAN is for the first QoS flow, a cause value (cause) may be generated that indicates a cause for handling the first QoS flow.

As an example, when the T-RAN does not support the handling of AQP information and the current resources cannot satisfy the QoS profile information of a first QoS flow, the T-RAN generates a first cause value for the first QoS flow, e.g., cause value 1. Optionally, the T-RAN may reject the first QoS flow. Wherein the first cause value is used to indicate that the reason for rejecting the first QoS flow is that the T-RAN does not support the AQP information, i.e., the current resources of the T-RAN cannot satisfy the QoS profile information of the first QoS flow, and the T-RAN does not perform QoS treatment on the first QoS flow according to the AQP information. At this time, the first cause value may be one example of the indication information #1 in fig. 4.

For example, it is assumed that bandwidth information in the QoS document information of the first QoS flow is 100Mbps, and bandwidth information included in the AQP list corresponding to the first QoS flow is {50Mbps, 20Mbps }. When the current resources of the T-RAN cannot meet the 100Mbps bandwidth information in the QoS document information, a first cause value is generated because the T-RAN cannot process the AQP information. Further, the T-RAN may also reject the first QoS flow.

As another example, when the T-RAN supports processing of AQP information and the current resources cannot satisfy the QoS profile information of the first QoS flow and the T-RAN current resources cannot satisfy any one of the AQP information in the AQP list, the T-RAN does not generate a cause value or generates a second cause value different from the first cause value, for example, a cause value of 2. Further, the T-RAN may reject the first QoS flow. Wherein the second cause value is used to indicate that the reason for rejecting the first QoS flow is that the T-RAN supports processing the AQP information, i.e., the T-RAN can perform QoS processing on the first QoS flow according to the AQP information, but the current resource still cannot satisfy the AQP information of the first QoS flow, for example, any AQP information in the AQP list. At this time, the second cause value may be one example of the indication information #3 in fig. 4.

For example, it is assumed that bandwidth information in the QoS document information of the first QoS flow is 100Mbps, and bandwidth information included in the AQP list corresponding to the first QoS flow is {50Mbps, 20Mbps }. And when the current resources of the T-RAN cannot meet the bandwidth information of 100Mbps in the QoS document information and cannot meet the bandwidth information of 50Mbps and 20Mbps in the AQP list, the T-RAN does not generate a cause value or generates a second cause value. Further, the T-RAN rejects the first QoS flow.

Alternatively, in other embodiments, when the T-RAN does not support processing AQP information and the current resources cannot meet the QoS profile information for a first QoS flow, the T-RAN does not generate a cause value for the first QoS flow. And when the T-RAN supports the processing of the AQP information and the current resources cannot meet any one of the QoS list corresponding to the first QoS flow and the AQP information in the AQP list, the T-RAN generates a second cause value for the first QoS flow. Further, the T-RAN rejects the first QoS flow.

It should be noted that, when the T-RAN generates only one cause value, the cause value may be directly referred to as a cause value without distinguishing the cause value as the first cause value or the second cause value.

The T-RAN sends a handover request acknowledgement (HO request ACK) to the S-RAN 505.

The S-RAN sends 506 a handover command to the UE.

The S-RAN and the T-RAN send a sequence number status transfer (SN status transfer) 507.

The T-RAN sends a path switch request (N2 path switch request) to the AMF 508.

Illustratively, the path switch request may include a switched session list, a QoS flow identifier accepted by the T-RAN, and tunnel information (AN tunnel info) of the T-RAN. Optionally, the path switching request may further include a cause value. Specifically, the cause value is generated by the T-RAN in step 504. Wherein the AN tunnel info is used to update the user plane connection between the T-RAN and the UPF.

As a possible implementation manner, the path switch request may include a switched PDU session list (list of PDU sessions to be switched), and N2SM info. The AN tunnel info and the cause value may be included in N2SM info, but the embodiment of the present application is not limited thereto.

509, the AMF sends an update session management context message (Nsmf PDU session update SM context request) to the SMF. Illustratively, a cause value or the like may be included in the message.

As a possible implementation, N2SM info may be included in the update session management context message. The AN tunnel info and the cause value may be included in the N2SM info, but the embodiment of the present application is not limited thereto.

The SMF determines 510 whether the T-RAN is QoS treating the first QoS flow based on the AQP information.

For example, the SMF may determine whether the T-RAN performs QoS processing for the first QoS flow according to the AQP information based on whether a cause value is received or based on the received cause value.

As an example, when the T-RAN generates a cause value for a first QoS flow without supporting the processing of the AQP information and the T-RAN does not generate a cause value for the first QoS flow without supporting the processing of the AQP information, when the SMF determines that the first QoS is not included in the accepted QoS flow (e.g., the first QoS flow is rejected) and receives the cause value, it may be determined that the T-RAN rejects the first QoS flow because the processing of the AQP information is not supported (i.e., the T-RAN does not QoS process the first QoS flow according to the AQP information) and the resources cannot satisfy the QoS profile information of the first QoS flow.

When the SMF determines that the first QoS flow is not included in the accepted QoS flows and the cause value is not received, it may be determined that the T-RAN supports processing the AQP information (i.e., the T-RAN performs QoS processing on the first QoS flow according to the AQP information), and the resources still cannot satisfy the AQP information of the first QoS.

As another example, when the T-RAN generates a first cause value (e.g., cause value 1) for a first QoS flow without supporting the processing of AQP information and the T-RAN generates a second cause value (e.g., cause value 2) for the first QoS flow with supporting the processing of AQP information, when the SMF determines that the first QoS is not included in an accepted QoS flow (e.g., the first QoS flow is rejected) and receives cause value 1, it may be determined that the T-RAN is not supported because the processing of AQP information is not supported (i.e., the T-RAN does not QoS process the first QoS flow according to the AQP information) and the resources cannot satisfy the QoS profile information of the first QoS flow.

When the SMF determines that the first QoS is not included in the accepted QoS flows and receives the cause value of 2, it may be determined that the T-RAN supports processing the AQP information (i.e., the T-RAN performs QoS processing on the first QoS flows according to the AQP information), and the resources still cannot satisfy the AQP information of the first QoS.

As another example, when the T-RAN does not generate a cause value for the first QoS flow without supporting the processing of the AQP information and the T-RAN generates a cause value for the first QoS flow without supporting the processing of the AQP information, when the SMF determines that the first QoS is not included in the accepted QoS flow (i.e., the first QoS flow is rejected) and does not receive the cause value, it may be determined that the T-RAN is not because the processing of the AQP information is not supported (i.e., the T-RAN does not QoS process the first QoS flow according to the AQP information) and the resources cannot satisfy the QoS profile information of the first QoS flow.

When the SMF determines that the first QoS is not included in the accepted QoS flows and the cause value is received, it may be determined that the T-RAN supports processing the AQP information (i.e., the T-RAN performs QoS processing on the first QoS flows according to the AQP information), and the resources still cannot satisfy the AQP information of the first QoS.

511, the SMF performs QoS processing on the first QoS flow according to the AQP information

As an example, when the SMF determines that the T-RAN is not supporting the processing of the AQP information (i.e., the T-RAN is not QoS processing the first QoS flow according to the AQP information) and the resources cannot meet the QoS profile information for the first QoS flow, the SMF may determine that the T-RAN is not downgrading the first QoS flow according to the AQP information for the first QoS. At this time, the SMF may downgrade the first QoS flow based on the AQP information.

Specifically, the process of performing QoS processing on the first QoS flow by the SMF according to the AQP information may refer to the description in fig. 4, and for brevity, details are not described here again.

When the SMF determines that the T-RAN supports processing the AQP information (i.e., the T-RAN performs QoS processing on the first QoS flow according to the AQP information), and the resources still cannot satisfy the AQP information of the first QoS, the SMF does not need to perform special processing on the first QoS flow (i.e., the rejected QoS flow).

Fig. 5 is described only by taking a moving scene as an example. The above-mentioned manner of sending the cause value to the SMF to inform the SMF whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow is also applicable to the non-mobile scenario. Different from the mobile scenario, in the non-mobile scenario, when the RAN determines that the resources do not satisfy the QoS profile information of the QoS flow, the RAN notifies the RAN whether to perform QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow by initiating a session modification procedure and carrying a cause value in the session modification procedure (in the mobile scenario, the T-RAN initiates a handover procedure and carries a cause value in the handover procedure). In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment, the RAN may send a cause value to the SMF, so that the SMF determines whether the RAN performs QoS processing on the first QoS flow according to the AQP information according to the cause value. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform QoS processing on the first QoS flow according to the AQP information corresponding to the first QoS flow when the RAN does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the SMF is favorable for performing accurate QoS control.

Fig. 6 shows a schematic flow chart of a communication method provided in an embodiment of the present application. The SMF may determine, according to the capability information of the locally configured RAN, whether the T-RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow. Wherein the capability information includes whether the RAN is capable of supporting the capability of processing AQP information. As shown in fig. 6, the method includes steps 600 to 611.

600, capability information of SMF configured RAN.

Illustratively, the SMF may be configured with a correspondence between an Identification (ID) of the RAN in its coverage area and whether the RAN supports handling AQP information. For example, the SMF stores a RAN ID and capability information whether the RAN to which the RAN ID corresponds supports processing AQP information.

601, the S-RAN makes handover decisions.

And 602, judging whether the T-RAN supports the processing of the AQP information.

603, the S-RAN sends a handover request to the T-RAN.

The T-RAN performs admission control 604.

Here, when the T-RAN rejects the first QoS flow, a cause value may not be generated.

The T-RAN sends a handover request acknowledgement to the S-RAN 605.

606, the S-RAN sends a handover command to the UE.

The S-RAN and the T-RAN send sequence number status transfer (SN status transfer) 607.

For example, steps 601 to 607 can be referred to the descriptions of steps 501 to 507 in fig. 5, and are not described herein again for brevity.

The T-RAN sends 608 a path switch request to the AMF.

Illustratively, the path switch request may include a list of sessions for switching, a QoS flow identifier accepted by the T-RAN, AN tunnel info, and a RAN ID of the T-RAN. As a possible implementation manner, the AN tunnel info and the RAN ID may be contained in the N2SM info, but the embodiment of the present application is not limited thereto.

In some optional embodiments, the path switching request may include location information of the UE, and the location information of the UE further includes a RAN ID of the T-RAN.

609, the AMF sends an update session management context message to the SMF. Illustratively, the message may include a RAN ID or location information of the UE.

As a possible implementation, N2SM info may be included in the session management context message. The AN tunnel info and the RAN ID may be contained in the N2SM info, or the AN tunnel info and the location information of the UE may be contained in the N2SM info, but the embodiment of the present application is not limited thereto.

The SMF determines 610 whether the T-RAN is QoS treating the first QoS flow based on the AQP information.

When the SMF determines that the first QoS flow is not included in the accepted QoS flow (e.g., the first QoS flow is rejected), the SMF may determine whether the T-RAN has the capability to support the processing of the AQP information according to capability information of the RAN configured on the SMF, and further determine whether the T-RAN performs QoS processing on the first QoS flow according to the AQP information.

For example, the SMF may determine whether the RAN (i.e., T-RAN) corresponding to the RAN ID has the capability of supporting the processing of the AQP information according to the RAN ID obtained in step 609 and the correspondence between the RAN ID obtained in advance and the capability of supporting the processing of the AQP information.

When the RAN corresponding to the RAN ID, namely the T-RAN, does not have the capability of supporting the processing of the AQP information, the SMF determines that the T-RAN does not perform QoS flow processing on the first QoS flow according to the AQP information and resources cannot meet QoS document information of the first QoS flow, and rejects the first QoS flow. When the RAN corresponding to the RAN ID, namely the T-RAN has the capability of supporting the processing of the AQP information, the SMF determines that the T-RAN performs QoS processing on the first QoS flow according to the AQP information, and the resources still cannot meet the AQP information of the first QoS.

611, the SMF performs QoS processing for the first QoS flow based on the AQP information. This step is an optional step.

Illustratively, when the SMF determines that the T-RAN does not have the capability to support processing the AQP information, i.e., the T-RAN rejects the first QoS flow without QoS flow processing for the first QoS flow according to the AQP information and without the resources satisfying the QoS profile information for the first QoS flow, the SMF may determine that the T-RAN does not downgrade the first QoS flow according to the AQP information for the first QoS. At this time, the SMF may downgrade the first QoS flow based on the AQP information.

When the SMF determines that the T-RAN has the capability of supporting the processing of the AQP information, that is, the T-RAN performs QoS processing on the first QoS flow according to the AQP information, and the resources still cannot satisfy the AQP information of the first QoS and rejects the first QoS flow, the SMF does not need to perform special processing on the first QoS flow (i.e., rejected QoS flow), that is, does not need to perform degradation processing on the first QoS flow according to the AQP information.

Fig. 6 is described only by taking a moving scene as an example. The above-mentioned manner of determining whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow according to the correspondence between the pre-acquired RAN ID and whether the RAN has the capability of supporting the processing of the AQP information is also applicable to the non-mobile scenario. Unlike the mobility scenario, in the non-mobility scenario, when the RAN determines that the resources do not satisfy the QoS profile information of the QoS flow, the RAN notifies the SMF of the RAN ID by initiating a session modification procedure and carrying the RAN ID in the session modification procedure (whereas in the mobility scenario, the T-RAN notifies the RAN ID by initiating a handover procedure and carrying the RAN ID in the handover procedure). In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment of the present application, the SMF may determine whether the RAN has the capability of supporting the AQP information according to a correspondence between the pre-acquired RAN ID and whether the RAN has the capability of supporting the AQP information, and further determine whether the RAN performs QoS processing on the first QoS flow according to the AQP information. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform QoS processing on the first QoS flow according to the AQP information when the RAN does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the QoS control is accurately performed.

Fig. 7 shows a schematic flow chart of a communication method provided in an embodiment of the present application. Wherein the SMF may query the T-RAN or the AMF for capability information of the T-RAN to determine whether the T-RAN performs QoS treatment on the QoS flow according to the AQP information corresponding to the QoS flow. Wherein the capability information includes whether the RAN is capable of supporting the capability of processing AQP information. As shown in fig. 7, the method includes steps 701 to 713.

701, the S-RAN makes handover decisions.

And 702, judging whether the T-RAN supports the processing of the AQP information.

703, the S-RAN sends a handover request to the T-RAN.

The T-RAN performs admission control 704.

The T-RAN sends a handover request acknowledgement to the S-RAN 705.

706, the S-RAN sends a handover command to the UE.

707, the S-RAN and the T-RAN send sequence number status transfer (SN status transfer).

The T-RAN sends a path switch request to the AMF 708.

709, the AMF sends an update session management context message to the SMF. Illustratively, the message may include a RAN ID.

For example, steps 701 to 709 can refer to the description in steps 601 to 609 in fig. 6 for the sake of brevity. And will not be described in detail herein.

The SMF sends a request to the T-RAN for RAN capabilities and receives a response from the T-RAN for RAN capabilities. This step is an optional step.

Illustratively, when the SMF determines that the first QoS flow is not included in the accepted QoS flow (e.g., the first QoS flow is rejected), the SMF may send a query request to the RAN through the AMF, the query request requesting capability information of the RAN. Wherein the capability information includes whether capabilities for processing AQP information are supported. As an example, capability information of the RAN may be included in a response corresponding to the query request. And the SMF further determines whether the T-RAN performs QoS processing on the first QoS flow according to the acquired RAN capability information.

In some embodiments, the SMF sends the query request to the RAN corresponding to the RAN ID, i.e., the T-RAN, through the AMF, so as to obtain capability information of the RAN. The T-RAN then sends a response corresponding to the query request to the SMF through the AMF.

In some embodiments, the SMF may send the query request to the AMF to obtain capability information of the RAN. The AMF then sends a response to the SMF corresponding to the query request. Wherein, capability information of RAN can be configured on AMF. For example, the AMF may configure a corresponding relationship between the ID of the RAN and whether the RAN supports AQP information processing. For example, the AMF stores a RAN ID and capability information whether a RAN corresponding to the RAN ID supports processing of AQP information.

The AMF may further obtain whether the RAN supports the capability of processing AQP information as follows.

In the mode 1, in the process of powering on the access network device, the RAN reports its capability information to the AMF, where the capability information includes whether the capability of processing the AQP information is supported. Correspondingly, the AMF receives and stores the capability information.

Mode 2, in the UE-initiated registration procedure, the RAN sends its capability information to the AMF through an N2 message, including whether the capability of handling AQP information is supported.

Mode 3, during the handover of the UE from the S-RAN to the T-RAN, the T-RAN sends the capability information of the T-RAN to the AMF through an N2 message, which includes whether the T-RAN supports the capability of processing the AQP information.

Optionally, when the AMF finds that the capability of the RAN to handle AQP information is not maintained, a query request may be sent to the RAN to obtain the capability information of the RAN. Illustratively, the RAN may send to the AMF, in a response corresponding to the query request, whether the RAN supports the capability of handling AQP information.

It should be noted that before step 710, the SMF may query whether the RAN ID and its corresponding RAN's capability to handle AQP information are locally stored. Step 710 may not need to be performed when the RAN ID and its corresponding RAN's capability to handle AQP information is locally maintained. Step 710 of actively learning the capabilities of the RAN may be performed when the RAN ID and its corresponding RAN's capabilities to handle AQP information are not locally stored.

711, the SMF stores the RAN capability information, i.e., the RAN capability information acquired in step 710.

The SMF determines 712 whether the T-RAN is QoS treating the first QoS flow based on the AQP information.

Illustratively, the SMF determines whether the T-RAN has a capability of supporting the processing of the AQP information according to the capability information of the RAN acquired in step 710, and further determines whether the T-RAN performs QoS processing on the first QoS according to the AQP information.

When the T-RAN does not have the capability to support processing the AQP information, the SMF determines that the T-RAN does not perform QoS flow processing for a first QoS flow according to the AQP information and that resources cannot satisfy QoS profile information of the first QoS flow and rejects the first QoS flow. When the T-RAN has the capability of supporting the processing of the AQP information, the SMF determines that the T-RAN performs QoS processing on the first QoS flow according to the AQP information, and the resources still cannot meet the AQP information of the first QoS.

713, the SMF performs QoS processing for the first QoS flow based on the AQP information.

For example, step 713 may be referred to the description of step 611 in fig. 6, and for brevity, will not be described again.

Fig. 7 is described only by taking a moving scene as an example. The above-mentioned manner of inquiring whether the RAN has the capability of supporting the processing of the AQP information to the RAN or the AMF, and determining whether the RAN performs the QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow is also applicable to the non-mobile scenario. Unlike the mobility scenario, in the non-mobility scenario, when the RAN determines that the resources do not satisfy the QoS profile information of the QoS flow, the RAN notifies the SMF of the RAN ID by initiating a session modification procedure and carrying the RAN ID in the session modification procedure (whereas in the mobility scenario, the T-RAN notifies the RAN ID by initiating a handover procedure and carrying the RAN ID in the handover procedure). In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment, the SMF may determine whether the RAN has the capability of supporting the processing of the AQP information by querying the RAN or the AMF whether the RAN has the capability of supporting the processing of the AQP information, and further determine whether the RAN performs QoS processing on the first QoS flow according to the AQP information. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF performs QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform the QoS processing on the first QoS flow according to the AQP information when the RAN does not perform the QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the QoS control is accurately performed.

Fig. 8 shows a schematic flow chart of a communication method provided in an embodiment of the present application. The AMF may send, to the SMF, capability information indicating whether the T-RAN supports processing of the AQP information or indication information indicating the capability information in the handover procedure, so that the SMF may determine, when determining that the T-RAN rejects the QoS flow, whether the T-RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow. As shown in fig. 8, the method includes steps 800 to 812.

The AMF configures capability information of the RAN including whether the RAN supports the capability of handling AQP information 800.

Specifically, the capability information of the RAN configured on the AMF and the manner of configuring the capability information of the RAN may refer to the description in step 710 in fig. 7, and for brevity, are not described herein again.

801, the S-RAN makes handover decisions.

And 802, judging whether the T-RAN supports the processing of the AQP information.

803, the S-RAN sends a handover request to the T-RAN.

The T-RAN performs admission control 804.

The T-RAN sends a handover request acknowledgement to the S-RAN 805.

806, the S-RAN sends a handover command to the UE.

807, the S-RAN and the T-RAN send sequence number status transfer (SN status transfer).

The T-RAN sends a path switch request to the AMF 808.

For example, steps 801 to 808 may be referred to as described in steps 601 to 608 in fig. 6 for brevity. And will not be described in detail herein.

Optionally, 809, the AMF determines the indication information.

Illustratively, the AMF determines a RAN ID corresponding to the T-RAN according to the received path switch request. It is then determined whether the T-RAN has the capability to support the handling of AQP information based on the RAN ID and the capability information of the RAN configured in step 800.

In some optional embodiments, the AMF may generate an indication information indicating whether the T-RAN has the capability of supporting the processing of the AQP information according to whether the T-RAN has the capability of supporting the processing of the AQP information. For example, the indication information may specifically be whether the capability information supports processing of AQP information, or may be a flag (for example, when the flag is 1, the T-RAN may be indicated to have the capability of supporting processing of AQP information, and when the flag is 0, the T-RAN may be indicated to have the capability of not supporting processing of AQP information, or vice versa).

In some optional embodiments, the AMF may generate the indication information for indicating that the T-RAN does not have the capability of supporting the processing of the AQP information only when the T-RAN does not have the capability of supporting the processing of the AQP information. For example, the indication information may also be capability information that does not support processing of AQP information, or a flag bit (e.g., 0).

In some optional embodiments, the AMF may generate the indication information for indicating that the T-RAN has the capability of supporting the processing of the AQP information only when the T-RAN has the capability of supporting the processing of the AQP information. Illustratively, the indication information may also be capability information supporting the processing of AQP information, or a flag bit (e.g., 1).

The AMF sends an update session management context message to the SMF 810.

Optionally, when the AMF generates the indication information in step 809, the indication information generated in step 809 may be included in the message. This indication information may be contained in N2SM info as an example, but the present embodiment is not limited thereto.

811, the SMF determines whether the T-RAN is QoS processing the first QoS flow according to the AQP information.

Illustratively, the SMF determines whether the T-RAN has the capability of supporting the processing of the AQP information according to the indication information obtained in step 810, and further determines whether the T-RAN performs QoS processing on the first QoS according to the AQP information.

In some embodiments, when the AMF generates the indication information only if the T-RAN does not have the capability of supporting the processing of the AQP information, if the indication information is included in the update session management context message received in step 810, the SMF determines that the T-RAN does not have the capability of supporting the processing of the AQP information, and may further determine that the T-RAN does not perform QoS processing for the first QoS according to the AQP information. If the indication information is not included in the update session management context message received in step 810, the SMF determines that the T-RAN has the capability of supporting the processing of the AQP information, and may further determine that the T-RAN performs QoS processing on the first QoS according to the AQP information.

In some embodiments, when the AMF generates the indication information only if the T-RAN has the capability of supporting the processing of the AQP information, if the indication information is included in the update session management context message received in step 810, the SMF determines that the T-RAN has the capability of supporting the processing of the AQP information, and may determine that the T-RAN performs QoS processing for the first QoS according to the AQP information. If the indication information is not included in the update session management context message received in step 810, the SMF determines that the T-RAN does not have the capability of supporting the processing of the AQP information, and may further determine that the T-RAN does not perform QoS processing for the first QoS according to the AQP information.

The SMF performs QoS processing for the first QoS flow in accordance with the AQP information 812.

For example, step 812 may refer to the description of step 611 in fig. 6, and is not repeated here for brevity.

Fig. 8 is described only by taking a moving scene as an example. The above-mentioned manner in which the AMF indicates to the SMF whether the RAN has the capability of processing the AQP information, so that the SMF determines whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow, is also applicable to the non-mobile scenario. Unlike the mobile scenario, in the non-mobile scenario, the AMF may indicate to the SMF whether the RAN has the capability to process AQP information in the session modification procedure. In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment, the AMF may indicate to the SMF whether the RAN has the capability of supporting the processing of the AQP information, so that the SMF determines whether the RAN has the capability of supporting the processing of the AQP information, and further determines whether the RAN performs QoS processing on the first QoS flow according to the AQP information. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform QoS processing on the first QoS flow according to the AQP information when the RAN does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the QoS control is accurately performed.

Fig. 9 shows a schematic flow chart of a communication method provided in an embodiment of the present application. Wherein, the SMF can query the PCF/UDM for capability information of the T-RAN to determine whether the T-RAN performs QoS treatment on the QoS flow according to the AQP information corresponding to the QoS flow. Wherein the capability information includes whether the RAN is capable of supporting the capability of processing AQP information. As shown in fig. 9, the method includes steps 900 through 912.

PCF/UDM configures capability information of the RAN 900.

For example, the capability information of the RAN configured on the PCF/UDM may refer to the capability information of the RAN configured on the SMF, which is not described herein again.

901, the S-RAN makes a handover decision.

And 902, determining whether the T-RAN supports AQP information processing.

903, the S-RAN sends a handover request to the T-RAN.

The T-RAN performs admission control 904.

905, the T-RAN sends a handover request acknowledgement to the S-RAN.

906, the S-RAN sends a handover command to the UE.

907, the S-RAN and the T-RAN send sequence number status transfer (SN status transfer).

The T-RAN sends a path switch request to the AMF 908.

The AMF sends 909 an update session management context message to the SMF. Illustratively, the message may include a RAN ID.

For example, steps 901 to 909 may refer to descriptions in steps 601 to 609 in fig. 6 for brevity. And will not be described in detail herein.

The SMF sends a request to the PCF or UDM inquiring about RAN capabilities 910 and receives a response inquiring about RAN capabilities.

Illustratively, when the SMF determines that the first QoS flow is not included in the accepted QoS flow (e.g., the first QoS flow is rejected), the SMF may send an inquiry request to the PCF/UDM requesting capability information of the RAN. Wherein the capability information includes whether capabilities for processing AQP information are supported. As an example, the PCF/UDM may include capability information of the RAN in a response corresponding to the query request. And the SMF further determines whether the T-RAN performs QoS processing on the first QoS flow according to the acquired RAN capability information.

In some embodiments, the SMF may send the query request to the PCF/UDM according to the RAN ID obtained in step 909, and the query request may include the RAN ID. The PCF/UDM may then send a response to the SMF corresponding to the query request including whether the RAN to which the RAN ID corresponds supports the capability to process AQP information.

It should be noted that before step 910, the SMF may query whether the RAN ID and its corresponding RAN's capability to handle AQP information are locally stored. Step 910 may not need to be performed when the RAN ID and its corresponding RAN's capability to handle AQP information is locally maintained. Step 910, i.e., actively learning the capabilities of the RAN, may be performed when the RAN ID and its corresponding RAN's capabilities to handle AQP information are not locally stored. Optionally, after obtaining whether the RAN supports AQP information handling capability information, the SMF may save the capability information.

911, the SMF determines whether the T-RAN is to QoS process the first QoS flow based on the AQP information.

The SMF performs QoS processing for the first QoS flow based on the AQP information 912.

For example, step 911 and step 912 can be referred to the descriptions of steps 712 and 713 in fig. 7, and are not described here for brevity.

Fig. 9 is described only by taking a moving scene as an example. The above-mentioned manner of inquiring the PCF/UDM whether the RAN has the capability of supporting the processing of the AQP information, so as to determine whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow, is also applicable to non-mobile scenarios. Unlike the mobility scenario, in the non-mobility scenario, when the RAN determines that the resources do not satisfy the QoS profile information of the QoS flow, the RAN notifies the SMF of the RAN ID by initiating a session modification procedure and carrying the RAN ID in the session modification procedure (whereas in the mobility scenario, the T-RAN notifies the RAN ID by initiating a handover procedure and carrying the RAN ID in the handover procedure). In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment of the present application, the SMF may determine whether the RAN has the capability of supporting the processing of the AQP information by querying, to the PCF/UDM, whether the RAN has the capability of supporting the processing of the AQP information, and further determine whether the RAN performs QoS processing on the first QoS flow according to the AQP information. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform QoS processing on the first QoS flow according to the AQP information when the RAN does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the QoS control is accurately performed.

Fig. 10 shows a schematic flow chart of a communication method provided in an embodiment of the present application. When AMF can inquire the capability information of T-RAN to PCF/UDM, and send the capability information of whether T-RAN supports processing AQP information to SMF in the switching process, the SMF can determine whether T-RAN processes QoS for the QoS flow according to the AQP information corresponding to the QoS flow. As shown in fig. 10, the method includes steps 1000 to 1012.

PCF/UDM configures capability information for the RAN 1000.

1001, the S-RAN makes handover decisions.

And 1002, judging whether the T-RAN supports the processing of the AQP information.

1003, the S-RAN sends a handover request to the T-RAN.

The T-RAN performs admission control 1004.

The T-RAN sends a handover request acknowledgement to the S-RAN 1005.

1006, the S-RAN sends a handover command to the UE.

1007, the S-RAN and the T-RAN send sequence number status transfer (SN status transfer).

The T-RAN sends a path switch request to the AMF 1008.

For example, steps 1000 to 1008 can be referred to the description of steps 900 to 908 in fig. 9 for brevity. And will not be described in detail herein.

1009, the AMF sends a request to the PCF or UDM inquiring about RAN capabilities and receives a response inquiring about RAN capabilities.

Illustratively, the AMF determines a RAN ID corresponding to the T-RAN according to the received path switch request. Then, based on the RAN ID, an inquiry request is sent to the PCF/UDM, the inquiry request requesting capability information of the RAN. Wherein the capability information includes whether capabilities are supported for processing AQP information. The RAN ID may be included in the query request. The PCF/UDM may then send a response to the SMF corresponding to the query request including whether the RAN to which the RAN ID corresponds supports the capability to process AQP information.

It should be noted that before step 1009, the AMF may query whether the RAN ID and its corresponding RAN's capability to handle AQP information are locally stored. Step 1009 may not need to be performed when the RAN ID and its corresponding RAN's capability to handle AQP information is locally maintained. Step 1009, the ability to actively learn the RAN, may be performed when the RAN ID and its corresponding RAN's ability to handle AQP information is not locally stored. Optionally, after acquiring whether the RAN supports AQP information handling capability information, the AMF may save the capability information.

At 1010, the AMF sends an update session management context message to the SMF. Illustratively, whether the T-rana acquired by the AMF in step 1009 supports the capability of handling AQP information may be included in the message.

As a possible implementation manner, the capability information whether to support processing of AQP information may be included in N2SM info, which is not limited in this embodiment of the application.

1011, the SMF determines whether the T-RAN is QoS treating the first QoS flow according to the AQP information.

For example, the SMF may determine whether the T-RAN has the capability of supporting the processing of the AQP information according to the capability information of whether the RAN supports the processing of the AQP information, which is carried in the message in step 1010, and further determine whether the T-RAN performs QoS processing on the first QoS according to the AQP information.

1012, the SMF performs QoS processing for the first QoS flow based on the AQP information.

For example, step 1011 and step 1012 can be referred to the descriptions of steps 712 and 713 in fig. 7, and are not described here for brevity.

Fig. 10 is described only by taking a moving scene as an example. The AMF inquires whether the RAN has the capability of supporting the processing of the AQP information from the PCF/UDM, and sends the capability information of whether the RAN supports the processing of the AQP information to the SMF, so that the SMF determines whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow, and the method is also suitable for non-mobile scenes. Unlike the mobile scenario, in the non-mobile scenario, the AMF may send the capability information to the SMF in a session modification procedure after querying the capability information of the RAN (whereas in the mobile scenario, the AMF informs the SMF whether the RAN has the capability to support the handling of AQP information by sending the capability information to the SMF in a handover procedure). In addition, in a non-mobile scenario, when the RAN determines that resources cannot satisfy a QoS flow, the QoS flow is not rejected, but is reserved.

Therefore, in this embodiment of the present application, the AMF may query, from the PCF/UDM, whether the RAN has the capability of supporting the processing of the AQP information, and send, to the SMF, the capability information of whether the RAN has the capability of supporting the processing of the AQP information, so that the SMF determines, according to the capability information, whether the RAN performs QoS processing on the first QoS flow according to the AQP information. When the SMF determines that the RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform QoS processing on the first QoS flow according to the AQP information when the RAN does not perform QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the QoS control is accurately performed.

Fig. 11 shows a schematic flow chart of a communication method provided in an embodiment of the present application. After determining whether the T-RAN supports the capability of processing the AQP information, the S-RAN may notify the SMF whether the T-RAN supports the capability of processing the AQP information, so that the SMF may determine whether the T-RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow. As shown in fig. 11, the method includes steps 1101 to 1112.

1101, the S-RAN makes a handover decision.

1102, the S-RAN sends a handover request to the T-RAN.

1103, the T-RAN performs admission control.

For example, steps 1101 to 1103 may be referred to the description above for brevity. And will not be described in detail herein.

The T-RAN sends a handover request acknowledgement to the S-RAN 1104.

In some optional embodiments, capability information of the T-RAN, e.g., whether the T-RAN supports the capability of handling AQP information, may be included in the handover request acknowledgement. In this way, the T-RAN may explicitly indicate whether the T-RAN has the capability to process AQP information.

In some optional embodiments, the handover request acknowledgement may include an indication of whether the T-RAN has processed the QoS flow in accordance with AQP information. For example, the T-RAN may indicate by way of the indication information whether it has processed the QoS flow in accordance with the AQP information. For example, the T-RAN may implement the above description by carrying whether or not indication information is carried, or by carrying different indication information.

In some optional embodiments, indication information of whether the T-RAN can process the AQP information may be included in the handover request acknowledgement. When the T-RAN is capable of processing the AQP information, it indicates that the T-RAN has a capability of supporting the processing of the AQP information. When the T-RAN is not capable of processing the AQP information, it indicates that the T-RAN does not have a capability of supporting the processing of the AQP information. In this way, the T-RAN may implicitly indicate whether the T-RAN has the capability to process AQP information.

1105, determine if the T-RAN supports AQP processing.

Illustratively, the S-RAN may determine whether the T-RAN has the capability to process AQP information based on the handover request acknowledgement received in step 1104.

Optionally, before step 1102, the S-RAN may also determine whether the T-RAN supports handling AQP information. The process of the S-RAN determining whether the T-RAN supports the AQP information processing herein can be referred to the description of step 502 in fig. 5, and for brevity, the detailed description is omitted here. In addition, if the S-RAN determines whether the T-RAN supports the handling of AQP information before step 1102, the S-RAN may not need to perform step 1105 below. Accordingly, the handover request acknowledgement in step 1104 at this time may not include capability information whether the T-RAN supports handling AQP information, i.e., the same as the handover request acknowledgement in the related art.

1106, the S-RAN sends a notification message to the SMF. The step is a selection step.

Illustratively, the notification message may be used to inform the SMF whether the T-RAN has the capability to support processing AQP information.

In some embodiments, an announcement message may be sent to the SMF to inform the SMF that the T-RAN does not have the capability to support processing of AQP information only if the T-RAN does not have the capability to support processing of AQP information or the T-RAN does not process QoS flows according to AQP information.

In some embodiments, the notification message may be sent to the SMF only if the T-RAN has the capability to support processing of AQP information or the T-RAN processes the QoS flow according to the AQP information to notify the SMF that the T-RAN has the capability to support processing of AQP information.

In some embodiments, the notification message may be sent to the SMF and distinguished by the content of the notification message being different, both when the T-RAN does not have the capability to support processing of AQP information or when the T-RAN does not have the capability to support processing of QoS flows according to AQP information, and when the T-RAN has the capability to support processing of AQP information or when the T-RAN processes QoS flows according to AQP information.

1107, the S-RAN sends a handover command to the UE.

The S-RAN and the T-RAN send sequence number status transfer (SN status transfer) 1108.

1109, the T-RAN sends a path switch request to the AMF. Here, the cause value may not need to be included in the path switch request.

1110, the AMF sends an update session management context message to the SMF. Here, the message may not include a cause value, or RAN ID of T-RAN

1111, the SMF determines whether the T-RAN is QoS processing the first QoS flow according to the AQP information.

For example, the SMF may determine whether the T-RAN has the capability of supporting the processing of the AQP information according to the notification message in step 1106 or whether the notification message sent by the S-RAN is received, and then determine whether the T-RAN performs QoS processing on the first QoS according to the AQP information.

In some embodiments, when the S-RAN sends the notification message to the SMF only if the T-RAN does not have the capability to support processing of AQP information, it may be determined that the T-RAN does not have the capability to support processing of AQP information if the SMF receives the notification message. If the SMF does not receive the notification message, it may be determined that the T-RAN has the capability to support processing AQP information.

In some embodiments, when the S-RAN sends the notification message to the SMF only if the T-RAN has the capability to support processing of AQP information, it may be determined that the T-RAN has the capability to support processing of AQP information if the SMF receives the notification message. If the SMF does not receive the notification message, it may be determined that the T-RAN does not have the capability to support processing AQP information.

The SMF performs QoS processing for the first QoS flow based on the AQP information 1112.

For example, step 1111 and step 1112 may be referred to the descriptions in steps 712 and 713 in fig. 7, and are not described here for brevity.

Therefore, in this embodiment, the S-RAN may send a notification message to the SMF, so that the SMF determines whether the T-RAN performs QoS processing on the first QoS flow according to the AQP information according to the notification message. Under the condition that the SMF determines that the T-RAN does not perform QoS processing on the first QoS flow according to the AQP information, the SMF can perform QoS processing on the first QoS flow according to the AQP information of the first QoS flow, so that the SMF can perform the QoS processing on the first QoS flow according to the AQP information corresponding to the first QoS when the T-RAN does not perform the QoS processing on the first QoS flow according to the AQP information or cannot process the AQP information, and the SMF is favorable for performing accurate QoS control.

In the above embodiment, only the example that the indication information (for example, the cause value or the capability information) is carried in the handover procedure is described, but the embodiment of the present application is not limited to this. For example, in a mobile scenario, the T-RAN may also initiate a session modification procedure after the handover procedure is ended, and notify the SMF whether the RAN performs QoS processing on the QoS flow according to the AQP information corresponding to the QoS flow in a manner of carrying a cause value or capability information in the session modification procedure.

Fig. 12 is a schematic diagram of an apparatus 1200 for wireless communication according to the foregoing method.

The apparatus 1200 may be a session management network element, or may also be a chip or a circuit, for example, a chip or a circuit that may be disposed in the session management network element. The apparatus 1200 may include a processing unit 1210 (i.e., an example of a processor) and a transceiving unit 1230.

Alternatively, the transceiving unit 1230 may be implemented by a transceiver or transceiver-related circuit or interface circuit.

Optionally, the apparatus may further include a storage unit 1220. In one possible approach, the storage unit 1220 is used to store instructions. Optionally, the storage unit may also be used to store data or information. The storage unit 1220 may be implemented by a memory.

In one possible design, the processing unit 1210 may be configured to execute the instructions stored by the storage unit 1220, so as to enable the apparatus 1200 to implement the steps performed by the session management network element in the method described above.

Further, the processing unit 1210, the storage unit 1220 and the transceiving unit 1230 may communicate with each other via the internal connection path to transmit control and/or data signals. For example, the storage unit 1220 is used to store a computer program, and the processing unit 1210 may be used to call and run the computing program from the storage unit 1220 to control the transceiving unit 1230 to receive and/or transmit signals, so as to complete the steps of the session management network element in the above method. The storage unit 1220 may be integrated with the processing unit 1210, or may be provided separately from the processing unit 1210.

Alternatively, if the apparatus 1200 is a communication device, the transceiving unit 1230 may include a receiver and a transmitter. Wherein the receiver and the transmitter may be the same or different physical entities. When the same physical entity, may be collectively referred to as a transceiver.

Alternatively, if the apparatus 1200 is a chip or a circuit, the transceiving unit 1230 may include an input interface and an output interface.

As an implementation manner, the function of the transceiving unit 1230 may be considered to be implemented by a transceiving circuit or a dedicated chip for transceiving. The processing unit 1210 may be considered to be implemented by a dedicated processing chip, a processing circuit, a processing unit or a general-purpose chip.

As another implementation manner, it may be considered that the communication device (e.g., a session management network element) provided in the embodiment of the present application is implemented by using a general-purpose computer. Program codes for implementing the functions of the processing unit 1210 and the transceiving unit 1230 are stored in the storage unit 1220, and the general-purpose processing unit implements the functions of the processing unit 1210 and the transceiving unit 1230 by executing the codes in the storage unit 1220.

In one implementation, the transceiving unit 1230 is configured to send QoS profile information of the first quality of service QoS flow and the alternative QoS profile AQP information.

Processing unit 1210 is configured to determine that an access network device is not performing QoS processing for the first QoS flow according to the AQP information.

Processing unit 1210 is further configured to perform QoS processing for the first QoS flow according to the AQP information.

Optionally, before the session management network element determines that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, the processing unit 1210 may further determine that resources of the access network device do not satisfy the QoS profile information of the first QoS flow.

Optionally, the transceiving unit 1230 may be configured to acquire indication information, and the processing unit 1210 is specifically configured to determine, according to the indication information, that the access network device does not perform QoS processing on the first QoS flow according to the AQP information.

Optionally, the transceiving unit 1230 may receive the indication information from the access network device.

Optionally, the indication information is used to indicate that the access network device does not perform QoS processing on the first QoS flow according to the AQP information, or is used to indicate that the access network device does not have a capability of supporting AQP information processing.

Optionally, the indication information is a cause value.

Optionally, the transceiving unit 1230 may obtain an identifier of the access network device, and send a first request according to the identifier of the access network device, where the first request is used to query whether the access network device has a capability of supporting AQP information processing. Then, the transceiving unit 1230 receives capability information of the access network device, where the capability information is used to indicate that the access network device does not have a capability of supporting AQP information processing, and uses the capability information as the indication information.

Optionally, the transceiving unit 1230 may acquire an identifier of the access network device. The processing unit 1210 may determine whether the access network device has the capability of supporting AQP information processing according to a correspondence relationship between a pre-obtained identifier of the access network device and whether the access network device has the capability of supporting AQP information processing.

The respective units in the above embodiments may also be referred to as modules or circuits or components.

The functions and actions of the modules or units in the apparatus 1200 listed above are only exemplary, and when the apparatus 1200 is configured or is itself a session management network element, the modules or units in the apparatus 1200 may be configured to execute the actions or processes executed by the session management network element in the above method.

For the concepts, explanations, details and other steps related to the technical solutions provided in the embodiments of the present application related to the apparatus 1200, please refer to the descriptions of the foregoing methods or other embodiments, which are not repeated herein.

Fig. 13 is a schematic diagram of an apparatus 1300 for wireless communication according to the foregoing method.

The apparatus 1300 may be an access network device, or may be a chip or a circuit, for example, a chip or a circuit that may be disposed in an access network device. The apparatus 1300 may include a processing unit 1310 (i.e., one example of a processor) and a transceiver 1330.

Alternatively, the transceiving unit 1330 may be implemented by a transceiver or transceiver-related circuit or interface circuit.

Optionally, the apparatus may further include a storage unit 1320. In one possible approach, the memory unit 1320 is used to store instructions. Optionally, the storage unit may also be used to store data or information. The storage unit 1320 may be implemented by a memory.

In one possible design, the processing unit 1310 may be configured to execute the instructions stored in the storage unit 1320 to enable the apparatus 1300 to implement the steps performed by the access network device in the method described above.

Further, the processing unit 1310, the memory unit 1320, and the transceiver unit 1330 may communicate with each other via internal connection paths to transmit control and/or data signals. For example, the storage unit 1320 is used to store a computer program, and the processing unit 1310 may be used to call and run the computer program from the storage unit 1320 to control the transceiving unit 1330 to receive and/or transmit signals, thereby performing the steps of the access network device in the above-described method. The memory unit 1320 may be integrated with the processing unit 1310 or may be provided separately from the processing unit 1310.

Alternatively, if the apparatus 1300 is a communication device, the transceiving unit 1330 may comprise a receiver and a transmitter. Wherein the receiver and the transmitter may be the same or different physical entities. When the same physical entity, may be collectively referred to as a transceiver.

Alternatively, if the apparatus 1300 is a chip or a circuit, the transceiver 1330 may include an input interface and an output interface.

As an implementation manner, the function of the transceiving unit 1330 may be considered to be implemented by a transceiving circuit or a dedicated chip for transceiving. The processing unit 1310 may be considered to be implemented by a dedicated processing chip, a processing circuit, a processing unit, or a general-purpose chip.

As another implementation manner, the communication device (e.g., access network device) provided by the embodiment of the present application may be implemented by using a general-purpose computer. Program codes for implementing the functions of the processing unit 1310 and the transceiving unit 1330 are stored in the storage unit 1320, and the general processing unit implements the functions of the processing unit 1310 and the transceiving unit 1330 by executing the codes in the storage unit 1320.

In one implementation, the processing unit 1310 is configured to determine indication information for determining that the second access network device does not perform QoS processing on the first quality of service QoS flow according to the replaced QoS profile AQP information of the first QoS flow.

The transceiving unit 1330 is configured to transmit the indication information.

Optionally, the indication information is used to indicate that the second access network device does not perform QoS processing on the first QoS flow according to the AQP information, or is used to indicate that the second access network device does not have a capability of supporting AQP information processing.

Optionally, the indication information is a cause value.

Optionally, the transceiving unit 1330 is further configured to receive a first request, where the first request is used to query whether the second access network device has a capability of supporting AQP information processing.

The processing unit 1310 is further configured to determine capability information of the second access network device, where the capability information is used to indicate that the second access network device does not have a capability of supporting AQP information processing, and determine the capability information as the indication information.

Optionally, the second access network device is apparatus 1300.

Optionally, the transceiving unit 1330 is configured to receive a handover confirmation message from the second access network device, where the handover confirmation message includes capability information of the second access network device, and the capability information is used to indicate that the second access network device does not have a capability of supporting AQP information processing.

The processing unit 1310 is configured to determine the capability information as the indication information.

The functions and actions of the modules or units in the apparatus 1300 listed above are only exemplary, and when the apparatus 1300 is configured as or is itself an access network device, the modules or units in the apparatus 1300 may be configured to execute the actions or processes executed by the access network device in the above method.

For the concepts, explanations, details, and other steps related to the technical solutions provided in the embodiments of the present application related to the apparatus 1300 refer to the descriptions of the foregoing methods or other embodiments, which are not repeated herein.

Fig. 14 is a schematic diagram of an apparatus 1400 for wireless communication according to the foregoing method.

The apparatus 1400 may be an access management network element, or may also be a chip or a circuit, for example, a chip or a circuit that can be set in an access management network element. The apparatus 1400 may include a processing unit 1410 (i.e., one example of a processor) and a transceiving unit 1430.

Alternatively, the transceiving unit 1430 may be implemented by a transceiver or transceiver-related circuits or interface circuits.

Optionally, the apparatus may further include a storage unit 1420. In one possible approach, the storage unit 1420 is used to store instructions. Optionally, the storage unit may also be used to store data or information. The storage unit 1420 may be implemented by a memory.

In one possible design, the processing unit 1410 may be configured to execute the instructions stored by the storage unit 1420, so as to enable the apparatus 1400 to implement the steps performed by the access management network element in the method described above.

Further, the processing unit 1410, the storage unit 1420, and the transceiving unit 1430 may communicate with each other via internal connection paths to transmit control and/or data signals. For example, the storage unit 1420 is configured to store a computer program, and the processing unit 1410 may be configured to call and run the computer program from the storage unit 1420, so as to control the transceiving unit 1430 to receive and/or transmit a signal, thereby performing the steps of the method for accessing the management network element. The storage unit 1420 may be integrated into the processing unit 1410 or may be provided separately from the processing unit 1410.

Alternatively, if the apparatus 1400 is a communication device, the transceiving unit 1430 may include a receiver and a transmitter. Wherein the receiver and the transmitter may be the same or different physical entities. When the same physical entity, may be collectively referred to as a transceiver.

Alternatively, if the apparatus 1400 is a chip or a circuit, the transceiver 1430 may include an input interface and an output interface.

As an implementation manner, the function of the transceiving unit 1430 may be considered to be implemented by a transceiving circuit or a dedicated chip for transceiving. The processing unit 1410 may be considered to be implemented by a dedicated processing chip, a processing circuit, a processing unit or a general-purpose chip.

As another implementation manner, it may be considered that the communication device (e.g., access management network element) provided in the embodiment of the present application is implemented by using a general-purpose computer. Program codes that will realize the functions of the processing unit 1410 and the transmitting/receiving unit 1430 are stored in the storage unit 1420, and the general-purpose processing unit realizes the functions of the processing unit 1410 and the transmitting/receiving unit 1430 by executing the codes in the storage unit 1420.

In one implementation, processing unit 1410 is configured to determine indication information indicating that an access network device does not have a capability to support processing AQP information.

The transceiver 1430 is configured to send the indication information to a session management network element.

Optionally, the transceiver 1430 may be configured to send a request for updating a session management context to the session management network element, where the request for updating the session management context includes the indication information, or send a request for creating a session management context to the session management network element, where the request for creating the session management context includes the indication information.

Optionally, the transceiver 1430 may be configured to acquire an identifier of the access network device. Processing unit 1410 is configured to determine whether the access network device has the capability of supporting AQP information processing according to a correspondence between a pre-obtained identifier of the access network device and whether the access network device has the capability of supporting AQP information processing.

Optionally, the transceiver 1430 is configured to receive the indication information from the access network device, where the indication information is reported to the AMF after the access network device powers on, or the indication information is carried in an N2 message sent by the access network device to the AMF.

Optionally, the transceiving unit 1430 is configured to send a first request to the access network device/PCF/UDM, where the first request is used to query whether the access network device has a capability of supporting AQP information processing.

The transceiving unit 1430 is further configured to receive capability information of the access network device from the access network device/PCF/UDM, where the capability information is used to indicate that the access network device does not have a capability of supporting AQP information processing.

The functions and actions of the modules or units in the apparatus 1400 listed above are only exemplary, and when the apparatus 1400 is configured as or is itself an access network device, the modules or units in the apparatus 1400 may be configured to perform the actions or processes performed by the access management network element in the foregoing method.

For the concepts, explanations, details and other steps related to the technical solutions provided in the embodiments of the present application related to the apparatus 1400, please refer to the descriptions of the foregoing methods or other embodiments, which are not repeated herein.

Fig. 15 is a schematic structural diagram of a network device 1500 according to an embodiment of the present application, which may be used to implement the function of an access network device (e.g., a first access network device or a second access network device) in the foregoing method. The network device 1500 includes one or more radio frequency units, such as a Remote Radio Unit (RRU) 1510 and one or more baseband units (BBUs) (also referred to as digital units, DUs) 1520. The RRU1510 may be referred to as a transceiver unit, transceiver, transceiving circuitry, or transceiver, etc., which may include at least one antenna 1511 and a radio frequency unit 1512. The RRU1510 is mainly used for transceiving radio frequency signals and converting radio frequency signals and baseband signals, for example, for sending signaling messages described in the above embodiments to a terminal device. The BBU1520 is mainly used for performing baseband processing, controlling a base station, and the like. The RRU1510 and the BBU1520 may be physically disposed together or may be physically disposed separately, i.e., distributed base stations.

The BBU1520 is a control center of the base station, and may also be referred to as a processing unit, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, spreading, and the like. For example, the BBU (processing unit) 1520 may be used to control the access network device to perform the operation procedures described above with respect to the access network device in the method embodiments.

In an example, the BBU1520 may be formed by one or more boards, and the boards may support a radio access network of a single access system (e.g., an LTE system or a 5G system) together, or may support radio access networks of different access systems respectively. The BBU1520 also includes a memory 1521 and a processor 1522. The memory 1521 is used to store necessary instructions and data. The processor 1522 is configured to control the access network device to perform necessary actions, for example, to control the access network device to execute the operation flows related to the access network device in the foregoing method embodiments. The memory 1521 and the processor 1522 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Multiple boards may share the same memory and processor. In addition, each single board can be provided with necessary circuits.

In one possible implementation, with the development of system-on-chip (SoC) technology, all or part of the functions of section 1520 and section 1510 may be implemented by SoC technology, for example, by a base station function chip integrating a processor, a memory, an antenna interface and other devices, and a program of the related functions of the base station is stored in the memory and executed by the processor to implement the related functions of the base station. Optionally, the base station function chip can also read a memory outside the chip to implement the relevant functions of the base station.

It should be understood that the structure of the network device illustrated in fig. 15 is only one possible form, and should not limit the embodiments of the present application in any way. This application does not exclude the possibility of other forms of base station structure that may appear in the future.

It should be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), and the processor may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

An embodiment of the present application further provides a computer-readable medium, on which a computer program is stored, where the computer program, when executed by a computer, implements the steps executed by the session management network element, or the steps executed by the access network device, or the steps executed by the access management network element in any of the above embodiments.

An embodiment of the present application further provides a computer program product, where the computer program product, when executed by a computer, implements the steps executed by the session management network element, or the steps executed by the access network device, or the steps executed by the access management network element in any of the above embodiments.

An embodiment of the present application further provides a system chip, where the system chip includes: a communication unit and a processing unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin or a circuit, etc. The processing unit may execute computer instructions, so that a chip in the communication device executes the steps executed by the session management network element, the steps executed by the access network device, or the steps executed by the access management network element, which are provided in the embodiment of the present application.

Optionally, the computer instructions are stored in a storage unit.

The embodiments in the present application may be used independently or jointly, and are not limited herein.

In addition, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

It should be understood that in the above illustrated embodiments, the first and second are only for convenience of distinguishing different objects, and should not constitute any limitation to the present application. E.g. to distinguish between different access network devices, etc.

It should also be understood that "and/or," which describes an association relationship for an associated object, indicates that there may be three relationships, e.g., a and/or B, may indicate: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one" means one or more than one; "at least one of a and B", similar to "a and/or B", describes an association relationship of associated objects, meaning that three relationships may exist, for example, at least one of a and B may mean: a exists alone, A and B exist simultaneously, and B exists alone.

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 implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the 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 conceive of the changes or substitutions within the technical scope of the present application, and shall 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:

a session management network element sends QoS document information of a first quality of service (QoS) flow and replaced QoS document AQP information;

the session management network element determines that the access network equipment does not perform QoS processing on the first QoS flow according to the AQP information;

and the session management network element carries out QoS processing on the first QoS flow according to the AQP information.

2. The method of claim 1, wherein before the session management network element determines that the access network device does not perform QoS processing for the first QoS flow according to the AQP information, further comprising:

3. The method of claim 1 or 2, wherein the determining, by the session management network element, that the access network device is not performing QoS processing for the first QoS flow according to the AQP information comprises:

the session management network element acquires indication information;

4. The method of claim 3, wherein the obtaining of the indication information by the session management network element comprises:

and the session management network element receives the indication information from the access network equipment.

5. The method of claim 3 or 4, wherein the indication information is used to indicate that the access network device does not perform QoS processing for the first QoS flow according to the AQP information or indicate that the access network device does not have a capability of supporting AQP information processing.

6. The method according to any of claims 3-5, wherein the indication information is a cause value.

7. The method according to any of claims 3-5, wherein the obtaining of the indication information by the session management network element comprises:

acquiring the identifier of the access network equipment;

and taking the capability information as the indication information.

8. The method of claim 1 or 2, wherein the determining, by the session management network element, that the access network device is not performing QoS processing for the first QoS flow according to the AQP information comprises:

acquiring the identifier of the access network equipment;

9. A method of communication, comprising:

the method comprises the steps that a first access network device determines indication information, wherein the indication information is used for determining that a second access network device does not carry out QoS processing on a first QoS flow according to replaced QoS document AQP information of the first QoS flow;

and the first access network equipment sends the indication information.

10. The method of claim 9, wherein the indication information indicates that the second access network device does not perform QoS processing for the first QoS flow according to the AQP information or indicates that the second access network device does not have a capability to support processing of AQP information.

11. The method according to claim 9 or 10, wherein the indication information is a cause value.

12. The method of claim 9 or 10, wherein the determining, by the first access network device, the indication information comprises:

determining the capability information as the indication information.

13. The method of any of claims 10-12, wherein the first access network device and the second access network device are the same access network device.

14. The method of claim 9, wherein the first access network device determining the first indication information comprises:

determining the capability information as the indication information.

15. A communication device comprising means or modules for performing the method performed by the session management network element as claimed in any of claims 1-8.

16. A communications apparatus comprising means or modules for performing the method performed by the first access network device in any of claims 9-14.

17. A communication apparatus, comprising a processor and a memory, the memory having stored therein instructions that, when executed by the processor, cause the apparatus to perform the method of any of claims 1-8 as performed by the session management network element.

18. A communications apparatus comprising a processor and a memory, the memory having instructions stored therein, which when executed by the processor, causes the apparatus to perform the method of any of claims 9-14 performed by the first access network device.

19. A computer-readable storage medium, characterized in that the storage medium has stored therein a computer program or instructions which, when executed by a communication device, carry out the method performed by the session management network element as in any one of claims 1-8.

20. A computer-readable storage medium, in which a computer program or instructions are stored, which, when executed by a communication device, carry out the method performed by the first access network apparatus as in any one of claims 9-14.

21. A chip comprising a processor and a communication interface, the processor being configured to invoke and execute instructions from the communication interface, the instructions, when executed by the processor, implementing the method performed by the session management network element as claimed in any one of claims 1 to 8.

22. A chip comprising a processor and a communication interface, the processor being configured to invoke and execute instructions from the communication interface, the instructions when executed by the processor implementing the method performed by the first access network device as in any of claims 9-14.