Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: a first network entity determines a first notification mode of congestion information of a first service flow; and the first network entity sends first information to a second network entity, wherein the first information is used for triggering the second network entity to report the congestion information of the first service flow according to the first notification mode. The method provided by the embodiment of the invention is helpful for determining a congestion control mechanism and a congestion information reporting mode.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] In some communication systems, application servers can adjust service data transmission rate and congestion window based on congestion information of quality of service (QoS) flows to improve communication efficiency of the system. However, it is not clear how to perform congestion detection and report congestion information. Summary of the invention

[0003] The embodiments of the present application provide a communication method and a communication device. The following introduces various aspects involved in the embodiments of the present application.

[0004] In a first aspect, a communication method is provided, including: a first network entity determines a first notification method for congestion information of a first service flow; the first network entity sends first information to a second network entity, wherein the first information is used to trigger the second network entity to report the congestion information of the first service flow according to the first notification method.

[0005] According to a second aspect, a communication method is provided, including: a second network entity receives first information from a first network entity or a fifth network entity, wherein the first information is used to trigger the second network entity to report congestion information of a first service flow in a first notification manner; in response to the first information, the second network entity reports the congestion information of the first service flow in the first notification manner.

[0006] According to a third aspect, a communication method is provided, including: a third network entity receives enabling information of a first operation sent by a first network entity, wherein the first operation includes adding congestion information of the first service flow in a data packet header corresponding to the first service flow; and the third network entity reports the congestion information of the first service flow based on the enabling information.

[0007] In a fourth aspect, a communication method is provided, comprising: a fourth network entity sends second information to a first network entity, wherein the second information is used to trigger a first notification method in which the first network entity determines congestion information of a first service flow.

[0008] In a fifth aspect, a communication method is provided, including: a fifth network entity sends first information to a second network entity, wherein the first information is used to trigger the second network entity to report congestion information of a first service flow in a first notification manner.

[0009] In the sixth aspect, a communication device is provided, including: a determination unit, used to determine a first notification method of congestion information of a first service flow; a sending unit, used to send first information to a second network entity, wherein the first information is used to trigger the second network entity to report the congestion information of the first service flow according to the first notification method.

[0010] In the seventh aspect, a communication device is provided, including: a receiving unit, used to receive first information from a first network entity or a fifth network entity, the first information being used to trigger the device to report congestion information of a first service flow in a first notification manner; a notification unit, in response to the first information, used to report the congestion information of the first service flow in the first notification manner.

[0011] In the eighth aspect, a communication device is provided, including: a receiving unit, used to receive enabling information of a first operation sent by a first network entity, wherein the first operation includes adding congestion information of the first service flow in a data packet header corresponding to the first service flow; and a notification unit, used to report the congestion information of the first service flow based on the enabling information.

[0012] In a ninth aspect, a communication device is provided, comprising: a sending unit, configured to send second information to a first network entity, wherein the second information is used to trigger a first notification method for the first network entity to determine congestion information of a first service flow.

[0013] In a tenth aspect, a communication device is provided, comprising: a sending unit, configured to send first information to a second network entity, wherein the first information is used to trigger the second network entity to report congestion information of a first service flow in a first notification manner.

[0014] In the eleventh aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor receives and sends data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in any one of the first to fifth aspects.

[0015] In a twelfth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in any one of the first to fifth aspects.

[0016] In a thirteenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of the first to fifth aspects.

[0017] In a fourteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in any one of the first to fifth aspects.

[0018] In a fifteenth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to fifth aspects.

[0019] In an embodiment of the present application, the first network entity sends the first information to the second network entity, which can trigger the second network entity to report the congestion information of the first service flow according to the first notification method, thereby helping to determine the congestion control mechanism and the congestion information reporting method. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 This is an example diagram of a wireless communication system used in an embodiment of the present application.

[0021] Figure 2 This is an example diagram of the 5GS architecture in one embodiment of the present application.

[0022] Figure 3 It is a schematic flow chart of a communication method provided by an embodiment of the present application.

[0023] Figure 4 It is a schematic flow chart of a communication method provided by another embodiment of the present application.

[0024] Figure 5 It is a schematic flow chart of a communication method provided by yet another embodiment of the present application.

[0025] Figure 6 It is a schematic flow chart of a communication method provided by yet another embodiment of the present application.

[0026] Figure 7 It is a schematic flow chart of a communication method provided by yet another embodiment of the present application.

[0027] Figure 8 It is a schematic flow chart of a communication method provided by yet another embodiment of the present application.

[0028] Fig. 9 It is a schematic structural diagram of a communication device provided in one embodiment of the present application.

[0029] Fig.10 It is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0030] Fig.11 It is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0031] Fig.12 It is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0032] Fig.13It is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0033] Fig.14 It is a schematic structural diagram of a device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0034] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0035] Figure 1 The wireless communication system 100 used in the embodiment of the present application may include a network device 110 and a user equipment (UE) 120. The network device 110 may communicate with the UE 120. The network device 110 may provide communication coverage for a specific geographical area and may communicate with the UE 120 located in the coverage area. The UE 120 may access a network (such as a wireless network) through the network device 110.

[0036] Figure 1 An exemplary embodiment shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other number of terminal devices within its coverage area, which is not limited in the embodiment of the present application. Optionally, the wireless communication system 100 may also include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0037] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) system or new radio (new radio, NR), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, and so on.

[0038] The UE in the embodiment of the present application may also be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The UE in the embodiment of the present application may refer to a device that provides voice and / or data connectivity to a user, and may be used to connect people, objects and machines, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. The UE in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using a sidelink signal. Cellular phones and smart home devices communicate without relaying communication signals through a base station.

[0039] The network device in the embodiment of the present application may be a device for communicating with a UE, and the network device may also be referred to as an access network device or a radio access network device, such as a base station. The network device in the embodiment of the present application may refer to a radio access network (RAN) node (or device) that accesses a UE to a wireless network. The base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, base band unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.

[0040] In some embodiments, the network device may be fixed or mobile. For example, a helicopter or a drone may be configured to act as a mobile network device, and one or more cells may move according to the location of the mobile network device. In other examples, a helicopter or a drone may be configured to act as a device for communicating with another network device. In some embodiments, the network device may refer to a CU or a DU, or the network device may include a CU and a DU, or the network device may also include an AAU.

[0041] It should be understood that the network device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface; it can also be deployed on aircraft, balloons and satellites in the air. The network device and the scenarios in which the embodiments of the present application are located are not limited in the embodiments of the present application.

[0042] It should also be understood that all or part of the functions of the network device and UE in the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (eg, a cloud platform).

[0043] Combine the following Figure 2 A system architecture in an embodiment of the present application is described.

[0044] Figure 2 This is an architecture diagram of the 5G system (5GS), which includes: network slice specific authentication and authorization function (NSSAAF), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), network slice admission control function (NSACF), access and mobility management function (AMF), session management function (SMF), policy control function (PCF), application function (AF), UE, radio access network (RAN), user plane function (UPF), data network (DN) and other network elements.

[0045] The embodiments of the present application involve access network elements (RAN), control plane elements (e.g., PCF, SMF, etc.), user plane elements (e.g., UPF), and application servers (AS). DN can implement the functions of the user plane part of the application server, and AF can implement the functions of the control plane part of the application server. Optionally, the access network element can be Figure 1 The network device 110 and the terminal device in the embodiment can be Figure 1 The terminal device 120 in.

[0046] by Figure 2 For example, 5GS can notify the application server (such as AF) of the congestion information so that it can adjust the service data sending rate and congestion window. The methods of notifying the application server of the congestion information can be divided into the following two categories:

[0047] 1. Congestion Information Notification Based on User Plane

[0048] One way is that the RAN detects the congestion status and adds the congestion information to the application layer packet header through the explicit congestion notification (ECN) mechanism (such as ECN marking), and sends the congestion information to the AS through the user plane;

[0049] Another way is that the RAN detects the congestion status and sends the congestion information to the protocol data unit (PDU) session anchor (PSA) UPF through the user plane part of the general packet radio service (GPRS) tunnel protocol (GTP-U). The PSA UPF then executes the ECN mechanism (such as ECN marking), adds the congestion information to the application layer header, and sends the congestion information to the AS through the user plane.

[0050] 2. Congestion Information Notification Based on Control Plane

[0051] One way is that RAN detects the congestion status and sends the congestion information to AF through control plane network elements such as SMF, PCF, and NEF.

[0052] Another way is that RAN detects the congestion status and sends the congestion information to PSA UPF through GTP-U, and then UPF sends the congestion information to AF through control plane network elements such as SMF, PCF, and NEF.

[0053] In addition, the SMF can send explicit indication information to the RAN or UPF to enable the congestion detection mechanism for a specific QoS flow, or use a dedicated 5G QoS identifier (5G QoS identifier, 5QI) to enable the congestion detection mechanism at the QoS flow level.

[0054] The above embodiments mention two congestion control mechanisms: RAN executing ECN marking and UPF executing ECN marking, as well as two notification methods: user plane-based congestion information notification and control plane-based congestion information notification. However, it is not clear how 5GS specifically determines which congestion control mechanism to use and which method to use to notify the application server of the congestion information.

[0055] In addition, RAN switching occurs when the terminal device moves. How to implement the congestion detection mechanism in this mobile scenario is also a technical problem that needs to be solved. For example, when RAN switching occurs, how to trigger the switching target RAN to perform congestion detection, whether the source RAN still needs to cancel the congestion detection, and how the target RAN determines the way to notify the application server of the congestion information are still unclear.

[0056] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device. Figures 3 to 8 The embodiments of the present application are described in detail with examples.

[0057] Figure 3 It is a schematic flowchart of the communication method of an embodiment of the present application. Figure 3 The method 300 shown may include steps S310 and S320, which are specifically as follows:

[0058] S310: A first network entity determines a first notification method for congestion information of a first service flow.

[0059] The first network entity may be a control plane network element, for example, a session management function (SMF).

[0060] The first service flow may be a service data flow or a quality of service (QoS) flow.

[0061] Optionally, the first notification method may include a method for reporting congestion information (such as a reporting path for congestion information). For example, the first notification method may include the user plane-based congestion information notification method and / or the control plane-based congestion information notification method mentioned in the above embodiments.

[0062] The first network entity may determine the first notification method based on the second information.

[0063] Optionally, the second information may be used to trigger the first network entity to determine the first notification method. For example, the second information may include at least one of the following information: congestion control indication information, third congestion information reporting path information, and flow description information of the first service flow. The congestion control indication information may be used to indicate that congestion control is enabled for the first service flow, and the third congestion information reporting path information may be used to indicate that the reporting path of the congestion information of the first service flow includes a control plane and / or a user plane.

[0064] Optionally, the flow description information may include at least one of the following information: data packet filtering information corresponding to the service flow, an identifier of a target UE corresponding to the service flow, an address of the target UE, an application identifier corresponding to the service flow, and a QoS identifier corresponding to the service flow.

[0065] In the embodiment of the present application, the first network entity may determine the first notification method in the following two ways:

[0066] Method 1:

[0067] The fourth network entity may indicate the manner of reporting the congestion information through indication information (such as the second information). The fourth network entity may be an AF. For example, the fourth network entity may send the second information to the first network entity. Further, the first network entity may determine the first notification manner based on the second information.

[0068] Method 2:

[0069] The second information may be pre-configured in a core network element (eg, SMF, PCF, UDM, etc.). When congestion control is enabled for the first service flow, the first network entity may determine whether to report congestion information through the control plane or the user plane based on the second information.

[0070] S320: The first network entity sends first information to the second network entity.

[0071] The second network entity may be an access network device, for example, a Radio Access Network (RAN) or a Next Generation Radio Access Network (NG-RAN).

[0072] Optionally, the first information may be used to trigger the second network entity to report congestion information of the first service flow in accordance with the first notification manner.

[0073] In response to the first information, the second network entity may report congestion information of the first service flow in a first notification manner.

[0074] In some embodiments, the first notification method may include: the second network entity reports congestion information through a control plane after performing congestion detection. Optionally, the first information may include at least one of the following information: congestion control indication information, first congestion information reporting path information, and flow description information of the first service flow. Among them, the congestion control indication information can be used to indicate that congestion control is enabled for the first service flow, and the first congestion information reporting path information can be used to indicate that the reporting path of the congestion information of the first service flow is the control plane.

[0075] Optionally, after receiving the first information, the second network entity may perform congestion detection on the first service flow. Further, the second network entity may send third information to the fourth network entity, and the third information may include congestion information of the first service flow.

[0076] In an embodiment of the present application, the first network entity sends the first information to the second network entity, which can trigger the second network entity to report the congestion information of the first service flow according to the first notification method, thereby helping to determine the congestion control mechanism and the congestion information reporting method.

[0077] Combine the following Figure 4 When the application server expects to obtain congestion information from the control plane, the AF can be used to configure the 5GS to perform RAN congestion detection and control plane-based congestion information reporting. The specific process is as follows:

[0078] S410, the AF sends second information to the PCF through a network exposure function (NEF). The second information may include at least one of the following information:

[0079] Congestion control indication information (which can be used to instruct 5GS to enable congestion control for the target flow), third congestion information reporting path information (which can be used to instruct the target network entity to report congestion information through the control plane) and flow description information (which can be UE ID, UE address, data packet filtering information, AF ID, QoS flow ID, etc., which are used to determine the description information of the target QoS flow).

[0080] S420, PCF forwards the second information to SMF.

[0081] S430, SMF sends first information to RAN.

[0082] The SMF may determine, based on the pre-configured information of the network operator and the second information for the target QoS flow provided by the AF, that the RAN reports the congestion information through the control plane after performing congestion detection, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, and then the AMF transparently transmits (or forwards) the first information to the RAN.

[0083] Optionally, the first information may include congestion control indication information, first congestion information reporting path information and flow description information of the target QoS flow. The first congestion information reporting path information may be used to indicate that the reporting path of the congestion information of the target QoS service flow is the control plane.

[0084] S440, RAN performs congestion detection on the target QoS flow.

[0085] S450: RAN sends third information to AF. The third information may include congestion information of the target QoS service flow.

[0086] RAN can report the congestion information of the target QoS service flow to AF through AMF, SMF, PCF, and NEF by control plane signaling. The congestion information may include flow description information, congestion direction (uplink, downlink), congestion degree, and other information.

[0087] In some embodiments, the first notification method may include: the second network entity reports congestion information through a user plane after performing congestion detection. Optionally, the first information may include at least one of the following information: enabling information of the first operation, and flow description information of the first service flow.

[0088] Optionally, the second network entity may perform congestion detection on the first service flow to obtain congestion information of the first service flow. Further, the second network entity may add the congestion information of the first service flow to the header of the second data packet in the first service flow; when network congestion occurs in the first service flow, the second network entity may send the first service flow including the second data packet.

[0089] Combine the following Figure 5 When the application server expects to obtain congestion information from the user plane and the RAN supports ECN marking, the AF can be used to configure the 5GS to perform RAN congestion detection and UP-based congestion information reporting. The specific process is as follows:

[0090] S510: The AF sends second information to the PCF via the NEF. The second information may include at least one of the following information:

[0091] Congestion control indication information (which can be used to instruct 5GS to enable congestion control for the target flow), third congestion information reporting path configuration (which can be used to instruct the target network entity to report congestion information through the user plane) and flow description information (which can be UE ID, UE address, data packet filtering information, AF ID, QoS flow ID, etc., which are used to determine the description information of the target QoS flow).

[0092] S520, PCF forwards the second information to SMF.

[0093] S530, SMF sends first information to RAN.

[0094] The SMF may determine, based on the pre-configured information of the network operator and the second information for the target QoS flow provided by the AF, that the RAN reports the congestion information through the user plane after performing congestion detection, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, and then the AMF transparently transmits (or forwards) the first information to the RAN.

[0095] Optionally, the first information may include at least one of the following information: enabling information of the first operation, flow description information of the target QoS flow. Optionally, the first operation includes adding congestion information of the target QoS flow in a packet header corresponding to the target QoS flow. For example, the first operation may be ECN marking.

[0096] S540, RAN performs congestion detection on the target QoS flow.

[0097] The RAN may perform congestion detection on the target QoS flow, and perform the first operation on the second data packet in the target QoS flow when the network is congested. Further, the RAN may send the second data packet (obtained after performing the first operation).

[0098] In some embodiments, the first notification method may include: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing the first operation. Optionally, the third network entity is a user plane network element, such as a UPF. Optionally, the first operation may include adding the congestion information of the first service flow to the header of the data packet corresponding to the first service flow, such as the first operation may be ECN marking.

[0099] Optionally, the first information may include at least one of the following information: congestion control indication information, second congestion information reporting path information, and flow description information of the first service flow. The congestion control indication information may be used to indicate that congestion control is enabled for the first service flow, and the second congestion information reporting path information may be used to indicate that the reporting path of the congestion information of the first service flow is the user plane.

[0100] Optionally, after receiving the first information, the second network entity may perform congestion detection on the first service flow to obtain congestion information of the first service flow. Further, the second network entity may add the congestion information of the first service flow to the header of the first data packet in the first service flow; the second network entity may send the first service flow including the first data packet.

[0101] Optionally, the first network entity may send enabling information of the first operation to the third network entity. The third network entity may report congestion information of the first service flow based on the enabling information.

[0102] Optionally, the third network entity may receive the congestion information of the first service flow sent by the second network entity; further, the third network entity may send a third data packet, and the header of the third data packet may include the congestion information of the first service flow. For example, the third network entity may read the first data packet (corresponding to the first service flow) sent by the second network entity (the header of the first data packet may include the congestion information of the first service flow); the third network entity may perform the first operation on the third data packet based on the congestion information of the first service flow.

[0103] Combine the following Figure 6When the application server expects to obtain congestion information from the user plane and the UPF supports ECN marking (the RAN does not support ECN marking), the AF can be used to configure the 5GS to perform RAN congestion detection and UP-based congestion information reporting. The specific process is as follows:

[0104] S610: The AF sends second information to the PCF through the NEF. The second information may include at least one of the following information:

[0105] Congestion control indication information (which can be used to instruct 5GS to enable congestion control for the target flow), third congestion information reporting path configuration (which can be used to instruct the target network entity to report congestion information through the user plane) and flow description information (which can be UE ID, UE address, data packet filtering information, AF ID, QoS flow ID, etc., which are used to determine the description information of the target QoS flow).

[0106] S620, PCF forwards the second information to SMF.

[0107] S630a, SMF sends first information to RAN.

[0108] The SMF may determine, based on the pre-configured information of the network operator and the second information for the target QoS flow provided by the AF, that the RAN reports the congestion information through the user plane after performing congestion detection, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, and then the AMF transparently transmits (or forwards) the first information to the RAN.

[0109] Optionally, the first information may include at least one of the following information: congestion control indication information, second congestion information reporting path information and flow description information of the target QoS flow. Optionally, the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the target QoS flow is the user plane.

[0110] S630b, SMF sends the fourth information to UPF.

[0111] Optionally, the fourth information may include at least one of the following information: enabling information of the first operation, flow description information of the target QoS flow. Optionally, the first operation includes adding congestion information of the target QoS flow in a packet header corresponding to the target QoS flow. For example, the first operation may be ECN marking.

[0112] S640: RAN performs congestion detection on the target QoS flow.

[0113] The RAN may perform congestion detection on the target QoS flow to obtain congestion information of the target QoS flow; the RAN may add the congestion information of the target QoS flow to the GTP-U header of the first data packet corresponding to the target QoS flow; further, the RAN may send the first data packet.

[0114] S650: UPF performs a first operation.

[0115] The UPF reads the GTP-U header of the target QoS flow, and performs the first operation on the third data packet in the target QoS flow according to the congestion information carried in the GTP-U header. Further, the UPF may send the third data packet (obtained after performing the first operation).

[0116] When RAN switching occurs in the mobile scenario of the terminal device, the source RAN can forward the received congestion detection indication and congestion notification path indication to the target access network device through the switching process. According to different RAN switching methods, it can be divided into the following two methods:

[0117] Method 1: Based on Xn switching, the source access network device may send the congestion detection indication and / or congestion notification path configuration information to the target access network device through the Xn interface.

[0118] Optionally, the switching of the terminal device between the source access network device and the target access network device may be switching based on an Xn interface, and the second network entity may receive the first information from the fifth network entity. Optionally, the second network entity may be the target access network device, and the fifth network entity may be the source access network device.

[0119] It should be understood that the fifth network entity may be equivalent to the second network entity in the aforementioned embodiment, and may receive the first information sent by the first network entity, etc. When the terminal device performs a handover based on the Xn interface between the source access network device and the target access network device, the fifth network entity may send a congestion detection indication and / or congestion notification path configuration information (such as the first information) to the target access network device.

[0120] Combine the following Figure 7 Take an example to illustrate. When UE mobility causes Xn-based RAN switching, the source RAN can send congestion detection indication information and / or congestion notification path configuration information to the target RAN via the Xn interface. The specific process is as follows:

[0121] S710: The source RAN sends first information to the target RAN.

[0122] The first information may include at least one of the following information:

[0123] Congestion control indication information (which can be used to instruct 5GS to enable congestion control for the target flow), enabling information of the first operation, congestion information reporting path configuration (which can be used to instruct the target network entity to report congestion information through the control plane and / or user plane) and flow description information of the target QoS flow.

[0124] The first information may be carried by a handover request message in a RAN handover procedure based on an Xn interface.

[0125] For example, the flow description information of the target QoS flow may include a QoS flow ID (QoS flow ID, QFI), packet filter set information (packet filter set), and the like.

[0126] S720: The target RAN reports congestion information.

[0127] The target RAN can determine the target QoS flow and the congestion information reporting method according to the received first information. The congestion information can be divided into the following three cases according to the different contents:

[0128] Case 1 (corresponding to Figure 4 Embodiment in): When the congestion configuration information received by the target RAN device includes congestion control indication information, and the congestion information reporting path is the control plane, the target RAN can perform congestion detection on the target QoS flow, and report the congestion information to the AF through AMF, SMF, PCF, and NEF by control plane signaling.

[0129] Case 2 (corresponding to Figure 5 In the embodiment of the present invention, when the congestion configuration information received by the target RAN includes enabling information of the first operation, the target RAN can perform congestion detection on the target QoS flow and perform the first operation (such as ECN marking) on ​​the data packets in the target QoS flow when the network is congested.

[0130] Case 3 (corresponding to Figure 6 In the embodiment of the present invention, when the congestion configuration information received by the target RAN includes congestion control indication information and the congestion information reporting path is the user plane, the target RAN can perform congestion detection on the target QoS flow and add the congestion information of the target QoS flow to the GTP-U header of the data packet of the target QoS flow.

[0131] Method 2: Based on the switching of N2, the source access network device sends the congestion detection indication and / or congestion notification path configuration information to the target access network device through the source AMF and the target AMF.

[0132] Optionally, the switching of the terminal device between the source access network device and the target access network device can be a switching based on the N2 interface, and the second network entity can receive the first information from the fifth network entity. Optionally, the second network entity can be the target access network device, and the fifth network entity can be the target AMF.

[0133] It should be understood that the fifth network entity may be equivalent to the second network entity in the aforementioned embodiment, and may receive the first information sent by the first network entity, etc. When the terminal device performs a handover between the source access network device and the target access network device based on the N2 interface, the fifth network entity may send a congestion detection indication and / or congestion notification path configuration information (such as the first information) to the target access network device through the source AMF and the target AMF.

[0134] Combine the following Figure 8 Take an example. When there is no Xn interface between the source RAN and the target RAN or the Xn-based RAN handover fails, the source RAN may initiate an N2-based RAN handover. The source RAN may send congestion detection indication information and / or congestion notification path configuration information to the target RAN through the source AMF and the target AMF. The specific process is as follows:

[0135] S810. The source RAN sends first information to the source AMF.

[0136] The first information may include at least one of the following information:

[0137] Congestion control indication information (which can be used to instruct 5GS to enable congestion control for the target flow), enabling information of the first operation, congestion information reporting path configuration (which can be used to instruct the target network entity to report congestion information through the control plane and / or user plane) and flow description information of the target QoS flow.

[0138] The first information may be carried by a handover request (handover required) message in a RAN handover procedure based on the N2 interface.

[0139] S820, the source AMF sends the first information to the target AMF.

[0140] The first information may be carried by a Namf_Communication_CreateUEContext Request message in the RAN handover process based on the N2 interface.

[0141] S830, the target AMF sends first information to the target RAN.

[0142] The first information may be carried by a handover request message in a RAN handover procedure based on the N2 interface.

[0143] S840: The target RAN reports congestion information.

[0144] The target RAN can determine the target QoS flow and the congestion information reporting method according to the received first information. The congestion information can be divided into the following three cases according to the different contents:

[0145] Case 1 (corresponding to Figure 4 Embodiment in): When the congestion configuration information received by the target RAN device includes congestion control indication information, and the congestion information reporting path is the control plane, the target RAN can perform congestion detection on the target QoS flow, and report the congestion information to the AF through AMF, SMF, PCF, and NEF by control plane signaling.

[0146] Case 2 (corresponding to Figure 5 In the embodiment of the present invention, when the congestion configuration information received by the target RAN includes enabling information of the first operation, the target RAN can perform congestion detection on the target QoS flow and perform the first operation (such as ECN marking) on ​​the data packets in the target QoS flow when the network is congested.

[0147] Case 3 (corresponding to Figure 6 In the embodiment of the present invention, when the congestion configuration information received by the target RAN includes congestion control indication information and the congestion information reporting path is the user plane, the target RAN can perform congestion detection on the target QoS flow and add the congestion information of the target QoS flow to the GTP-U header of the data packet of the target QoS flow.

[0148] Combination of the above Figures 1 to 8 , describes the method embodiment of the present application in detail, and the following is combined with Figures 9 to 14 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0149] Fig. 9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. Fig. 9 As shown, the device 900 includes a determining unit 910 and a sending unit 920, which are specifically as follows:

[0150] A determining unit 910, configured to determine a first notification method for congestion information of a first service flow;

[0151] The sending unit 920 is used to send first information to the second network entity, where the first information is used to trigger the second network entity to report congestion information of the first service flow according to the first notification method.

[0152] Optionally, the first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

[0153] Optionally, the first information includes at least one of the following information: congestion control indication information, first congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the control plane.

[0154] Optionally, the first notification method includes: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing a first operation, and the first operation includes adding the congestion information of the first service flow in the data packet header corresponding to the first service flow.

[0155] Optionally, the sending unit 920 is further used to: send enabling information of the first operation to the third network entity.

[0156] Optionally, the third network entity is a user plane function UPF.

[0157] Optionally, the first information includes at least one of the following information: congestion control indication information, second congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the user plane.

[0158] Optionally, the first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

[0159] Optionally, the first information includes at least one of the following information: enabling information of the first operation, flow description information of the first service flow, and the first operation includes adding congestion information of the first service flow to a data packet header corresponding to the first service flow.

[0160] Optionally, the determination unit 910 is specifically used to: determine the first notification method based on pre-configuration information, and the pre-configuration information is used to indicate at least one of the following information: whether the second network entity supports reporting congestion information through the control plane, and whether the second network entity supports reporting congestion information through the user plane.

[0161] Optionally, the determining unit 910 is specifically used to: determine the first notification method based on second information, and the second information is used to trigger the device to determine the first notification method.

[0162] Optionally, the second information includes at least one of the following information: congestion control indication information, third congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the third congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow includes the control plane and / or the user plane.

[0163] Optionally, the device 900 further includes a receiving unit 930, configured to: receive the second information sent by a fourth network entity.

[0164] Optionally, the fourth network entity is an application function AF network element.

[0165] Optionally, the second information is preconfigured in the device.

[0166] Optionally, the flow description information includes at least one of the following information: data packet filtering information corresponding to the first service flow, an identifier of a target UE corresponding to the first service flow, an address of the target UE, an application identifier corresponding to the first service flow, and a quality of service QoS identifier corresponding to the first service flow.

[0167] Optionally, the device is a session management function SMF, and the second network entity is an access network device.

[0168] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0169] Optionally, the first service flow is a service data flow or a quality of service QoS flow.

[0170] Fig.10 It is a schematic structural diagram of a communication device provided in one embodiment of the present application. Fig.10 The communication device 1000 includes a receiving unit 1010 and a notification unit 1020, which are specifically as follows:

[0171] The receiving unit 1010 is configured to receive first information from the first network entity or the fifth network entity, where the first information is used to trigger the device to report congestion information of the first service flow in a first notification manner;

[0172] The notification unit 1020 is configured to report congestion information of the first service flow in accordance with the first notification method in response to the first information.

[0173] Optionally, the first notification method includes: the device reports congestion information through a control plane after performing congestion detection.

[0174] Optionally, the notification unit 1020 is specifically used to: perform congestion detection on the first service flow; and send third information to a fourth network entity, where the third information includes congestion information of the first service flow.

[0175] Optionally, the first information includes at least one of the following information: congestion control indication information, first congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the control plane.

[0176] Optionally, the first notification method includes: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing a first operation, and the first operation includes adding the congestion information of the first service flow in the data packet header corresponding to the first service flow.

[0177] Optionally, the notification unit 1020 is specifically used to: perform congestion detection on the first business flow to obtain congestion information of the first business flow; add the congestion information of the first business flow to the header of the first data packet in the first business flow; and send the first business flow containing the first data packet.

[0178] Optionally, the first information includes at least one of the following information: congestion control indication information, second congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the user plane.

[0179] Optionally, the third network entity is a user plane function UPF.

[0180] Optionally, the first notification method includes: the device reports congestion information through a user plane after performing congestion detection.

[0181] Optionally, the notification unit 1020 is specifically used to: perform congestion detection on the first business flow to obtain congestion information of the first business flow; add the congestion information of the first business flow to the header of the second data packet in the first business flow; and when network congestion occurs in the first business flow, send the first business flow including the second data packet.

[0182] Optionally, the first information includes at least one of the following information: enabling information of the first operation, flow description information of the first service flow, and the first operation includes adding congestion information of the first service flow to a data packet header corresponding to the first service flow.

[0183] Optionally, the first network entity is a session management function SMF, and the device is an access network device.

[0184] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0185] Optionally, the apparatus is a target access network device, and the fifth network entity is a source access network device.

[0186] Optionally, the switching of the terminal device between the source access network device and the target access network device is based on the switching of the Xn interface.

[0187] Optionally, the device is a target access network device, and the fifth network entity is a target access and mobility management function AMF network element.

[0188] Optionally, the switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

[0189] Optionally, the source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0190] Optionally, the target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0191] Optionally, the first service flow is a service data flow or a quality of service QoS flow.

[0192] Fig.11 It is a schematic structural diagram of a communication device provided in one embodiment of the present application. Fig.11 The communication device 1100 in the embodiment includes a receiving unit 1110 and a notification unit 1120, which are specifically as follows:

[0193] The receiving unit 1110 is configured to receive enabling information of a first operation sent by a first network entity, where the first operation includes adding congestion information of the first service flow to a header of a data packet corresponding to the first service flow;

[0194] The notification unit 1120 is configured to report congestion information of the first service flow based on the enabling information.

[0195] Optionally, the notification unit 1120 is specifically used to: receive congestion information of the first service flow sent by the second network entity; and send a third data packet, wherein a header of the third data packet includes the congestion information of the first service flow.

[0196] Optionally, the notification unit 1120 is specifically used to: read a first data packet in the first service flow sent by the second network entity, the first data packet header including congestion information of the first service flow; and perform the first operation on the third data packet based on the congestion information of the first service flow.

[0197] Optionally, the second network entity is an access network device.

[0198] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0199] Optionally, the first network entity is a session management function SMF, and the device is a user plane function UPF.

[0200] Optionally, the first service flow is a service data flow or a quality of service QoS flow.

[0201] Fig.12 It is a schematic structural diagram of a communication device provided in one embodiment of the present application. Fig.12 The communication device 1200 in the embodiment includes a sending unit 1210, which is specifically as follows:

[0202] The sending unit 1210 is used to send second information to the first network entity, where the second information is used to trigger the first network entity to determine a first notification method for congestion information of a first service flow.

[0203] Optionally, the second information includes at least one of the following information: congestion control indication information, third congestion information reporting path information, and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the third congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow includes the control plane and / or the user plane.

[0204] Optionally, the device 1200 further includes a receiving unit 1220, configured to: receive third information sent by the second network entity, wherein the third information includes congestion information of the first service flow.

[0205] Optionally, the second network entity is an access network device.

[0206] Optionally, the access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0207] Optionally, the first network entity is a session management function SMF, and the device is an application function AF network element.

[0208] Optionally, the first service flow is a service data flow or a quality of service QoS flow.

[0209] Fig.13 It is a schematic structural diagram of a communication device provided in one embodiment of the present application. Fig.13 The communication device 1300 in the embodiment includes a sending unit 1310, which is specifically as follows:

[0210] The sending unit 1310 is used to send first information to the second network entity, where the first information is used to trigger the second network entity to report congestion information of the first service flow in a first notification manner.

[0211] Optionally, the first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

[0212] Optionally, the first notification method includes: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing a first operation, and the first operation includes adding the congestion information of the first service flow in the data packet header corresponding to the first service flow.

[0213] Optionally, the third network entity is a user plane function UPF.

[0214] Optionally, the first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

[0215] Optionally, the second network entity is a target access network device, and the device is a source access network device.

[0216] Optionally, the switching of the terminal device between the source access network device and the target access network device is based on the switching of the Xn interface.

[0217] Optionally, the second network entity is a target access network device, and the device is a target access and mobility management function AMF network element.

[0218] Optionally, the switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

[0219] Optionally, the source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0220] Optionally, the target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

[0221] Optionally, the first service flow is a service data flow or a quality of service QoS flow.

[0222] Fig.14 It is a schematic structural diagram of a device provided in one embodiment of the present application. Fig.14 The dotted line in the figure indicates that the unit or module is optional. The device 1400 can be used to implement the method described in the above method embodiment. The device 1400 can be a chip or a communication device.

[0223] The device 1400 may include one or more processors 1410. The processor 1410 may support the device 1400 to implement the method described in the foregoing method embodiment. The processor 1410 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0224] The apparatus 1400 may further include one or more memories 1420. The memory 1420 stores a program, which can be executed by the processor 1410, so that the processor 1410 executes the method described in the above method embodiment. The memory 1420 may be independent of the processor 1410 or integrated in the processor 1410.

[0225] The apparatus 1400 may further include a transceiver 1430. The processor 1410 may communicate with other devices or chips through the transceiver 1430. For example, the processor 1410 may transmit and receive data with other devices or chips through the transceiver 1430.

[0226] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present application, and the program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

[0227] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the embodiment of the present application, and the program enables the computer to execute the method performed by the communication device in each embodiment of the present application.

[0228] The embodiment of the present application also provides a computer program. The computer program can be applied to the communication device provided in the embodiment of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

[0229] It should be understood that in the embodiment of the present application, "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0230] It should be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0231] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0232] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0233] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0234] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0235] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0236] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: The first network entity determines a first notification method of congestion information of a first service flow; The first network entity sends first information to the second network entity, where the first information is used to trigger the second network entity to report congestion information of the first service flow in the first notification manner.

2. The method according to claim 1, characterized in that: The first notification method includes: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing a first operation, the first operation includes adding the congestion information of the first service flow in the data packet header corresponding to the first service flow, and the third network entity is a user plane function UPF.

3. The method according to claim 1, characterized in that The method further comprises: The first network entity sends enabling information of the first operation to a third network entity.

4. The method according to claim 2 or 3, characterized in that: The first information includes at least one of the following information: congestion control indication information, second congestion information reporting path information and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the user plane.

5. The method according to claim 1, characterized in that The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection; The first information includes at least one of the following information: enabling information of the first operation and flow description information of the first service flow, and the first operation includes adding congestion information of the first service flow in the data packet header corresponding to the first service flow.

6. The method according to any one of claims 1 to 5, characterized in that The first network entity determines a first notification method of congestion information of a first service flow, including: The first network entity determines the first notification method based on pre-configuration information, where the pre-configuration information is used to indicate at least one of the following information: whether the second network entity supports reporting congestion information through a control plane, and whether the second network entity supports reporting congestion information through a user plane.

7. The method according to any one of claims 1 to 6, characterized in that The first network entity determines a first notification method of congestion information of a first service flow, including: The first network entity determines the first notification method based on second information, where the second information is used to trigger the first network entity to determine the first notification method; The second information includes at least one of the following information: congestion control indication information, third congestion information reporting path information and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the third congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow includes the control plane and / or the user plane.

8. The method according to any one of claims 1 to 7, characterized in that The first network entity determines a first notification method based on congestion control indication information or flow description information of a first service flow, wherein the congestion control indication information indicates enabling congestion control for the first service flow.

9. The method according to claim 4, 5, 7 or 8, characterized in that The flow description information includes at least one of the following information: The data packet filtering information corresponding to the first service flow, the identifier of the target UE corresponding to the first service flow, the address of the target UE, the application identifier corresponding to the first service flow, and the quality of service QoS identifier corresponding to the first service flow.

10. The method according to any one of claims 1 to 9, characterized in that The first network entity is a session management function SMF, and the second network entity is an access network device; The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

11. The method according to any one of claims 1 to 10, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

12. A communication method, characterized in that: include: The second network entity receives first information from the first network entity or the fifth network entity, where the first information is used to trigger the second network entity to report congestion information of the first service flow in a first notification manner; In response to the first information, the second network entity reports congestion information of the first service flow according to the first notification method.

13. The method according to claim 12, characterized in that The first notification method includes: the second network entity sends congestion information to the third network entity, and the third network entity reports the congestion information through the user plane after performing a first operation, the first operation includes adding the congestion information of the first service flow in the data packet header corresponding to the first service flow, and the third network entity is a user plane function UPF.

14. The method according to claim 13, characterized in that The first information includes at least one of the following information: congestion control indication information, second congestion information reporting path information and flow description information of the first service flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first service flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first service flow is the user plane.

15. The method according to claim 12, characterized in that The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection; The first information includes at least one of the following information: enabling information of the first operation and flow description information of the first service flow, and the first operation includes adding congestion information of the first service flow in the data packet header corresponding to the first service flow.

16. The method according to any one of claims 12 to 15, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

17. A communication device, characterized in that: include: A determining unit, configured to determine a first notification method of congestion information of a first service flow; A sending unit is used to send first information to a second network entity, where the first information is used to trigger the second network entity to report congestion information of the first service flow according to the first notification method.

18. A communication device, characterized in that: include: A receiving unit, configured to receive first information from the first network entity or the fifth network entity, wherein the first information is used to trigger the device to report congestion information of the first service flow in a first notification manner; A notification unit, in response to the first information, is used to report the congestion information of the first service flow according to the first notification method.

19. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 11.

20. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 12 to 16.

Images