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

Communication method and communication device 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 rates and congestion windows based on congestion information in Quality of Service (QoS) flows to improve system communication efficiency. However, the specific methods for congestion detection and reporting are currently unclear.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.

[0005] 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.

[0006] In 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, the first information being 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 accordance with the first notification manner.

[0007] 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 business flow to a data packet header corresponding to the first business flow; and the third network entity reports the congestion information of the first business flow based on the enabling information.

[0008] In a fourth aspect, a communication method is provided, including: a fourth network entity sends second information to a first network entity, where 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.

[0009] 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.

[0010] In the sixth aspect, a communication device is provided, including: a determination unit for determining a first notification method of congestion information of a first business flow; a sending unit for sending 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 business flow according to the first notification method.

[0011] In the seventh aspect, a communication device is provided, including: a receiving unit for receiving first information from a first network entity or a fifth network entity, wherein the first information is 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, for reporting congestion information of the first service flow in accordance with the first notification manner.

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

[0013] 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.

[0014] 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.

[0015] 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 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 described in any one of the first to fifth aspects.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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 in accordance with the first notification method, thereby helping to determine the congestion control mechanism and the congestion information reporting method. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is an example diagram of a wireless communication system used in an embodiment of the present application.

[0022] FIG2 is an example diagram of a 5GS architecture in an embodiment of the present application.

[0023] FIG3 is a schematic flowchart of a communication method provided in one embodiment of the present application.

[0024] FIG4 is a schematic flowchart of a communication method provided in another embodiment of the present application.

[0025] FIG5 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0026] FIG6 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0027] FIG7 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0028] FIG8 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0029] FIG9 is a schematic structural diagram of a communication device provided in one embodiment of the present application.

[0030] FIG10 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

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

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

[0033] FIG13 is a schematic structural diagram of a communication device provided in yet another embodiment of the present application.

[0034] FIG14 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0035] The technical solution in this application will be described below with reference to the accompanying drawings.

[0036] FIG1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 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 geographic area and may communicate with the UE 120 within the coverage area. The UE 120 may access a network (e.g., a wireless network) through the network device 110.

[0037] Figure 1 exemplarily shows a network device and two UEs. Optionally, the wireless communication system 100 may include multiple network devices, and each network device may include a different number of terminal devices within its coverage area, which is not limited in this 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 this embodiment of the present application.

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

[0039] The UE in the embodiments 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 apparatus. The UE in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or an in-vehicle device with wireless connection capabilities. 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 a 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 sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0040] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may 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, transmitting and receiving point (TRP), transmitting 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, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.

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

[0042] It should be understood that network devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on water; and can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the network devices and the scenarios in which they are used.

[0043] It should also be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0044] The following describes a system architecture in an embodiment of the present application in conjunction with FIG2 .

[0045] Figure 2 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.

[0046] 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). The DN can implement the user plane functions of the application server, and the AF can implement the control plane functions of the application server. Optionally, the access network element can be the network device 110 in Figure 1, and the terminal device can be the terminal device 120 in Figure 1.

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

[0048] 1. User-plane-based congestion information notification

[0049] One approach is for the RAN to detect congestion and add congestion information to the application layer packet header through an explicit congestion notification (ECN) mechanism (such as ECN marking), and then send the congestion information to the AS through the user plane.

[0050] Another approach is for the RAN to detect congestion and send 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 performs ECN mechanisms (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.

[0051] 2. Congestion Information Notification Based on the Control Plane

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

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

[0054] 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.

[0055] 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 how to notify the application server of the congestion information.

[0056] Furthermore, RAN handovers occur when a terminal device moves, and how to implement congestion detection mechanisms in such mobility scenarios also poses technical challenges. For example, when a RAN handover occurs, how to trigger congestion detection in the target RAN, whether the source RAN still needs to cancel congestion detection, and how the target RAN determines how to notify the application server of congestion information remain unclear.

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

[0058] FIG3 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 300 shown in FIG3 may include steps S310 and S320, as follows:

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

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

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

[0062] 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 aforementioned embodiment.

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

[0064] 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: 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 for congestion information of the first service flow includes the control plane and / or the user plane.

[0065] 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.

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

[0067] Method 1:

[0068] The fourth network entity may indicate a congestion information reporting method using 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 method based on the second information.

[0069] Method 2:

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

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

[0072] 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).

[0073] 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.

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

[0075] In some embodiments, the first notification method may include: the second network entity reporting congestion information via a control plane after performing congestion detection. Optionally, the first information may include at least one of the following: congestion control indication information, first 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 first congestion information reporting path information may be used to indicate that the reporting path for congestion information of the first service flow is the control plane.

[0076] 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, where the third information may include congestion information of the first service flow.

[0077] 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 in accordance with the first notification method, thereby helping to determine the congestion control mechanism and the congestion information reporting method.

[0078] The following example is illustrated with reference to Figure 4. When the application server expects to obtain congestion information from the control plane, it can configure the 5GS through AF to perform RAN congestion detection and control plane-based congestion information reporting. The specific process is as follows:

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

[0080] 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, packet filtering information, AF ID, QoS flow ID, etc., used to determine the description information of the target QoS flow).

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

[0082] S430: The SMF sends first information to the RAN.

[0083] 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 performs congestion detection and reports congestion information through the control plane, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, which then transparently transmits (or forwards) the first information to the RAN.

[0084] 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 for congestion information of the target QoS service flow is the control plane.

[0085] S440: RAN performs congestion detection on the target QoS flow.

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

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

[0088] In some embodiments, the first notification method may include: the second network entity reporting congestion information via 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.

[0089] Optionally, the second network entity may perform congestion detection on the first service flow to obtain congestion information of the first service flow. Furthermore, 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.

[0090] The following example is illustrated with reference to 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:

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

[0092] 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, packet filtering information, AF ID, QoS flow ID, etc., used to determine the descriptive information of the target QoS flow).

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

[0094] S530: The SMF sends first information to the RAN.

[0095] 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 performs congestion detection and reports the congestion information through the user plane, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, which then transparently transmits (or forwards) the first information to the RAN.

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

[0097] S540: RAN performs congestion detection on the target QoS flow.

[0098] 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).

[0099] In some embodiments, the first notification method may include: the second network entity sending congestion information to the third network entity, and the third network entity performing the first operation and then reporting the congestion information via the user plane. 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 a data packet corresponding to the first service flow. For example, the first operation may include ECN marking.

[0100] 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 for congestion information of the first service flow is the user plane.

[0101] 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; and the second network entity may send the first service flow including the first data packet.

[0102] 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.

[0103] Optionally, the third network entity may receive congestion information about the first service flow sent by the second network entity; further, the third network entity may send a third data packet, the header of which may include the congestion information about 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 about the first service flow); and the third network entity may perform the first operation on the third data packet based on the congestion information about the first service flow.

[0104] The following example is illustrated with reference to Figure 6. When 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:

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

[0106] 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, packet filtering information, AF ID, QoS flow ID, etc., used to determine the descriptive information of the target QoS flow).

[0107] S620: The PCF forwards the second information to the SMF.

[0108] S630a: The SMF sends first information to the RAN.

[0109] 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 performs congestion detection and reports the congestion information through the user plane, and send the first information to the RAN. Optionally, the SMF may first send the first information to the AMF, which then transparently transmits (or forwards) the first information to the RAN.

[0110] 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.

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

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

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

[0114] 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.

[0115] S650: The UPF performs a first operation.

[0116] 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).

[0117] When a RAN handover occurs in a mobile scenario of a 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 handover process. Depending on the RAN handover method, there are two methods:

[0118] Method 1: Xn-based switching: the source access network device may send a congestion detection indication and / or congestion notification path configuration information to the target access network device via the Xn interface.

[0119] Optionally, the handover of the terminal device between the source access network device and the target access network device may be handover 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.

[0120] 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 handover between the source access network device and the target access network device based on the Xn 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.

[0121] The following example is illustrated with reference to FIG7. When UE mobility causes an Xn-based RAN handover, the source RAN may 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:

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

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

[0124] 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.

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

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

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

[0128] The target RAN can determine the target QoS flow and the congestion information reporting method based on the received first information. According to the different contents of the congestion information, it can be divided into the following three cases:

[0129] Case 1 (corresponding to the embodiment in Figure 4): 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 the AMF, SMF, PCF, and NEF by control plane signaling.

[0130] In case 2 (corresponding to the embodiment in FIG5 ), when the congestion configuration information received by the target RAN includes enabling information for the first operation, the target RAN may 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.

[0131] Case 3 (corresponding to the embodiment in Figure 6) 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 packet header of the data packet of the target QoS flow.

[0132] Method 2: Based on N2 switching, 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.

[0133] Optionally, the switching of the terminal device between the source access network device and the target access network device may be switching based on the N2 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 target AMF.

[0134] It should be understood that the fifth network entity can be equivalent to the second network entity in the aforementioned embodiment, and can receive the first information sent by the first network entity, etc. When the terminal device performs a handover based on the N2 interface between the source access network device and the target access network device, the fifth network entity can 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.

[0135] The following example illustrates this with reference to Figure 8. When no Xn interface exists between the source RAN and target RAN or an 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 via the source AMF and target AMF. The specific process is as follows:

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

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

[0138] 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.

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

[0140] S820. The source AMF sends first information to the target AMF.

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

[0142] S830. The target AMF sends first information to the target RAN.

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

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

[0145] The target RAN can determine the target QoS flow and the congestion information reporting method based on the received first information. According to the different contents of the congestion information, it can be divided into the following three cases:

[0146] Case 1 (corresponding to the embodiment in Figure 4): 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 the AMF, SMF, PCF, and NEF by control plane signaling.

[0147] In case 2 (corresponding to the embodiment in FIG5 ), when the congestion configuration information received by the target RAN includes enabling information for the first operation, the target RAN may 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.

[0148] Case 3 (corresponding to the embodiment in Figure 6) 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 packet header of the data packet of the target QoS flow.

[0149] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 14 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

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

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

[0152] 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.

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

[0154] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

[0155] 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 to the data packet header corresponding to the first service flow.

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

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

[0158] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the user plane.

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

[0160] 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 the data packet header corresponding to the first service flow.

[0161] 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.

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

[0163] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the third congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow includes the control plane and / or the user plane.

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

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

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

[0167] Optionally, the flow description information includes at least one of the following information: 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.

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

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

[0170] Optionally, the first service flow is a service data flow or a Quality of Service (QoS) flow.

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

[0172] 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 apparatus to report congestion information of the first service flow in a first notification manner;

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

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

[0175] Optionally, the notification unit 1020 is specifically configured 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.

[0176] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

[0177] 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 to the data packet header corresponding to the first service flow.

[0178] 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.

[0179] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the second congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the user plane.

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

[0181] Optionally, the first notification method includes: the device reporting congestion information through a user interface after performing congestion detection.

[0182] 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 send the first business flow containing the second data packet when network congestion occurs in the first business flow.

[0183] 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 the data packet header corresponding to the first service flow.

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

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

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

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

[0188] 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.

[0189] 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.

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

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

[0192] Optionally, the first service flow is a service data flow or a Quality of Service (QoS) flow.

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

[0194] 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;

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

[0196] Optionally, the notification unit 1120 is specifically configured to: receive congestion information of the first service flow sent by a 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.

[0197] Optionally, the notification unit 1120 is specifically used to: read the 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.

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

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

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

[0201] Optionally, the first service flow is a service data flow or a Quality of Service (QoS) flow.

[0202] FIG12 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 1200 in FIG12 includes a sending unit 1210, which is specifically as follows:

[0203] The sending unit 1210 is configured 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.

[0204] 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the third congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow includes the control plane and / or the user plane.

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

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

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

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

[0209] Optionally, the first service flow is a service data flow or a Quality of Service (QoS) flow.

[0210] FIG13 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device 1300 in FIG13 includes a sending unit 1310, which is specifically as follows:

[0211] The sending unit 1310 is configured 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 a first service flow in a first notification manner.

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

[0213] 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 to the data packet header corresponding to the first service flow.

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

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

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

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

[0218] 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.

[0219] 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.

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

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

[0222] Optionally, the first service flow is a service data flow or a Quality of Service (QoS) flow.

[0223] FIG14 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dashed lines in FIG14 indicate that the unit or module is optional. Apparatus 1400 may be used to implement the method described in the above method embodiment. Apparatus 1400 may be a chip or a communication device.

[0224] 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 method embodiment above. 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 be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0225] The apparatus 1400 may further include one or more memories 1420. The memories 1420 store programs that can be executed by the processor 1410, causing the processor 1410 to perform the methods described in the above method embodiments. The memories 1420 may be independent of the processor 1410 or integrated into the processor 1410.

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

[0227] The present invention 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 invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0228] 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 present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

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

[0230] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0231] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0232] 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.

[0233] In the several embodiments provided in this 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 merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, 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.

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

[0235] 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.

[0236] 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 can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can 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 can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can 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 therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0237] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The first network entity determines a first notification method for congestion information of the 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 reports congestion information through a control plane after performing congestion detection.

3. The method according to claim 2, characterized in that 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

4. The method according to claim 1, wherein 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 to the data packet header corresponding to the first service flow.

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

6. The method according to claim 4 or 5, characterized in that The third network entity is a user plane function UPF.

7. The method according to any one of claims 4 to 6, 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.

8. 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.

9. The method according to claim 8, characterized in that 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. The first operation includes adding congestion information of the first service flow to the data packet header 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 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.

11. The method according to any one of claims 1 to 10, 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, and the second information is used to trigger the first network entity to determine the first notification method.

12. The method according to claim 11, characterized in that 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.

13. The method according to claim 11 or 12, characterized in that The method further comprises: The first network entity receives the second information sent by the fourth network entity.

14. The method according to claim 13, characterized in that The fourth network entity is an application function AF network element.

15. The method according to claim 14, characterized in that The second information is preconfigured in the first network entity.

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

17. The method according to any one of claims 1 to 16, characterized in that The first network entity is a session management function SMF, and the second network entity is an access network device.

18. The method according to claim 17, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

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

20. 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 the congestion information of the first service flow according to the first notification method.

21. The method according to claim 20, characterized in that The first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

22. The method according to claim 21, characterized in that The second network entity reporting, according to the first notification manner, the congestion information of the first service flow, includes: Performing congestion detection, by the second network entity, on the first service flow; The second network entity sends third information to the fourth network entity, where the third information includes congestion information of the first service flow.

23. The method according to claim 21 or 22, characterized in that 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

24. The method according to claim 20, 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, and the first operation includes adding the congestion information of the first service flow to the data packet header corresponding to the first service flow.

25. The method according to claim 24, characterized in that The second network entity reporting, according to the first notification manner, the congestion information of the first service flow, includes: The second network entity performs congestion detection on the first service flow to obtain congestion information of the first service flow; The second network entity adds the congestion information of the first service flow to a header of a first data packet in the first service flow; The second network entity sends the first service flow including the first data packet.

26. The method according to claim 24 or 25, 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.

27. The method according to any one of claims 24 to 26, characterized in that The third network entity is a user plane function UPF.

28. The method according to claim 20, wherein The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

29. The method according to claim 28, characterized in that The second network entity reporting, according to the first notification manner, the congestion information of the first service flow, includes: The second network entity performs congestion detection on the first service flow to obtain congestion information of the first service flow; The second network entity adds the congestion information of the first service flow to a header of a second data packet in the first service flow; When network congestion occurs in the first service flow, the second network entity sends the first service flow including the second data packet.

30. The method according to claim 28 or 29, characterized in that 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. The first operation includes adding congestion information of the first service flow to the data packet header corresponding to the first service flow.

31. The method according to any one of claims 20 to 30, characterized in that The first network entity is a session management function SMF, and the second network entity is an access network device.

32. The method according to claim 31, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

33. The method according to any one of claims 20 to 32, characterized in that The second network entity is a target access network device, and the fifth network entity is a source access network device.

34. The method according to claim 33, wherein The switching of the terminal device between the source access network device and the target access network device is based on the Xn interface.

35. The method according to any one of claims 20 to 32, characterized in that The second network entity is the target access network device, and the fifth network entity is the target access and mobility management function AMF network element.

36. The method according to claim 35, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

37. The method according to any one of claims 33 to 36, characterized in that The source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

38. The method according to any one of claims 33 to 36, characterized in that The target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

39. The method according to any one of claims 20 to 38, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

40. A communication method, characterized in that: include: The third network entity receives enabling information of a first operation sent by the 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; The third network entity reports congestion information of the first service flow based on the enabling information.

41. The method according to claim 40, characterized in that The third network entity reporting, based on the enabling information, congestion information of the first service flow, includes: The third network entity receives congestion information of the first service flow sent by the second network entity; The third network entity sends a third data packet, where a header of the third data packet includes congestion information of the first service flow.

42. The method according to claim 41, wherein The receiving, by the third network entity, the congestion information of the first service flow sent by the second network entity includes: The third network entity reads a first data packet in the first service flow sent by the second network entity, where a header of the first data packet includes congestion information of the first service flow; The third network entity performs the first operation on the third data packet based on the congestion information of the first service flow.

43. The method according to claim 41 or 42, characterized in that The second network entity is an access network device.

44. The method according to claim 43, wherein The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

45. The method according to any one of claims 40 to 44, characterized in that The first network entity is a session management function SMF, and the third network entity is a user plane function UPF.

46. ​​The method according to any one of claims 40 to 45, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

47. A communication method, characterized in that: include: The fourth network entity sends 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 the first service flow.

48. The method according to claim 47, wherein 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.

49. The method according to claim 47 or 48, characterized in that The method further comprises: The fourth network entity receives third information sent by the second network entity, where the third information includes congestion information of the first service flow.

50. The method according to claim 49, wherein The second network entity is an access network device.

51. The method according to claim 50, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

52. The method according to any one of claims 47 to 51, characterized in that The first network entity is a session management function SMF, and the fourth network entity is an application function AF network element.

53. The method according to any one of claims 47 to 52, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

54. A communication method, characterized in that: include: The fifth 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 a first notification manner.

55. The method according to claim 54, characterized in that The first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

56. The method according to claim 54, wherein 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 to the data packet header corresponding to the first service flow.

57. The method according to claim 56, characterized in that The third network entity is a user plane function UPF.

58. The method according to claim 54, characterized in that The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

59. The method according to any one of claims 54 to 58, characterized in that The second network entity is a target access network device, and the fifth network entity is a source access network device.

60. The method according to claim 59, wherein The switching of the terminal device between the source access network device and the target access network device is based on the Xn interface.

61. The method according to any one of claims 54 to 60, characterized in that The second network entity is the target access network device, and the fifth network entity is the target access and mobility management function AMF network element.

62. The method according to claim 61, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

63. The method according to any one of claims 59 to 62, characterized in that The source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

64. The method according to any one of claims 59 to 62, characterized in that The target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

65. The method according to any one of claims 54 to 64, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

66. A communication device, characterized in that include: a determining unit, configured to determine a first notification method for 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.

67. The device according to claim 66, characterized in that The first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

68. The device according to claim 67, characterized in that 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

69. The device according to claim 66, 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, and the first operation includes adding the congestion information of the first service flow to the data packet header corresponding to the first service flow.

70. The device according to claim 69, characterized in that The sending unit is further configured to send enabling information of the first operation to the third network entity.

71. The device according to claim 69 or 70, characterized in that The third network entity is a user plane function UPF.

72. The device according to any one of claims 69 to 71, 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.

73. The device according to claim 66, characterized in that The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

74. The device according to claim 73, characterized in that 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. The first operation includes adding congestion information of the first service flow to the data packet header corresponding to the first service flow.

75. The device according to any one of claims 66 to 74, characterized in that The determining unit is specifically used to: determine 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 the control plane, and whether the second network entity supports reporting congestion information through the user plane.

76. The device according to any one of claims 66 to 75, characterized in that The determining unit is specifically configured to determine the first notification method based on second information, where the second information is used to trigger the device to determine the first notification method.

77. The device according to claim 76, characterized in that 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.

78. The device according to claim 76 or 77, characterized in that The apparatus further includes a receiving unit configured to receive the second information sent by a fourth network entity.

79. The device according to claim 78, characterized in that The fourth network entity is an application function AF network element.

80. The device according to claim 79, characterized in that The second information is preconfigured in the device.

81. The device of claim 68, 72, 74 or 77, wherein: The flow description information includes at least one of the following information: The data packet filtering information corresponding to the first business flow, the identifier of the target UE corresponding to the first business flow, the address of the target UE, the application identifier corresponding to the first business flow, and the quality of service QoS identifier corresponding to the first business flow.

82. The device according to any one of claims 66 to 81, characterized in that The device is a session management function SMF, and the second network entity is an access network device.

83. The device according to claim 82, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

84. The device according to any one of claims 66 to 83, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

85. 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 apparatus 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 in accordance with the first notification method.

86. The device according to claim 85, characterized in that The first notification method includes: the device reports congestion information through a control plane after performing congestion detection.

87. The device according to claim 86, characterized in that The notification unit is specifically configured 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.

88. The device according to claim 86 or 87, characterized in that 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 business flow, wherein the congestion control indication information is used to indicate that congestion control is enabled for the first business flow, and the first congestion information reporting path information is used to indicate that the reporting path of the congestion information of the first business flow is the control plane.

89. The device according to claim 85, 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, and the first operation includes adding the congestion information of the first service flow to the data packet header corresponding to the first service flow.

90. The device according to claim 89, characterized in that The notification unit 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.

91. The device according to claim 89 or 90, 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.

92. The device according to any one of claims 89 to 91, characterized in that The third network entity is a user plane function UPF.

93. The device according to claim 85, characterized in that The first notification method includes: the device reports congestion information through a user interface after performing congestion detection.

94. The device according to claim 93, characterized in that The notification unit 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 send the first business flow containing the second data packet when network congestion occurs in the first business flow.

95. The device according to claim 93 or 94, characterized in that 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. The first operation includes adding congestion information of the first service flow to the data packet header corresponding to the first service flow.

96. The device according to any one of claims 85 to 95, characterized in that The first network entity is a session management function SMF, and the device is an access network device.

97. The device according to claim 96, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

98. The device according to any one of claims 85 to 97, characterized in that The device is a target access network device, and the fifth network entity is a source access network device.

99. The device according to claim 98, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the Xn interface.

100. The device according to any one of claims 85 to 97, characterized in that The device is a target access network device, and the fifth network entity is a target access and mobility management function AMF network element.

101. The device according to claim 100, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

102. The device according to any one of claims 98 to 101, characterized in that The source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

103. The device according to any one of claims 98 to 101, characterized in that The target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

104. The device according to any one of claims 85 to 103, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

105. A communication device, characterized in that include: a receiving unit, 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; A notification unit is configured to report congestion information of the first service flow based on the enabling information.

106. The device according to claim 105, characterized in that The notification unit is specifically configured to: receive the 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.

107. The device according to claim 106, characterized in that The notification unit is specifically used to: read the first data packet in the first service flow sent by the second network entity, the first data packet header including the 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.

108. The device according to claim 106 or 107, characterized in that The second network entity is an access network device.

109. The device according to claim 108, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

110. The device according to any one of claims 105 to 109, characterized in that The first network entity is a session management function SMF, and the device is a user plane function UPF.

111. The device according to any one of claims 105 to 110, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

112. A communication device, characterized in that include: A sending unit 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.

113. The device according to claim 112, characterized in that 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.

114. The device according to claim 112 or 113, characterized in that The device further includes a receiving unit configured to receive third information sent by the second network entity, where the third information includes congestion information of the first service flow.

115. The device according to claim 114, characterized in that The second network entity is an access network device.

116. The device according to claim 115, characterized in that The access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

117. The device according to any one of claims 112 to 116, characterized in that The first network entity is a session management function SMF, and the device is an application function AF network element.

118. The device according to any one of claims 112 to 117, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

119. A communication device, characterized in that include: 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 in a first notification manner.

120. The device according to claim 119, characterized in that The first notification method includes: the second network entity reports congestion information through a control plane after performing congestion detection.

121. The device according to claim 119, 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, and the first operation includes adding the congestion information of the first service flow to the data packet header corresponding to the first service flow.

122. The device according to claim 121, characterized in that The third network entity is a user plane function UPF.

123. The device according to claim 119, characterized in that The first notification method includes: the second network entity reports congestion information through a user plane after performing congestion detection.

124. The device according to any one of claims 119 to 123, characterized in that The second network entity is a target access network device, and the device is a source access network device.

125. The device according to claim 124, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the Xn interface.

126. The device according to any one of claims 119 to 125, characterized in that The second network entity is a target access network device, and the device is a target access and mobility management function AMF network element.

127. The device according to claim 126, characterized in that The switching of the terminal device between the source access network device and the target access network device is based on the N2 interface.

128. The device according to any one of claims 124 to 127, characterized in that The source access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

129. The device according to any one of claims 124 to 127, characterized in that The target access network device is a radio access network RAN ​​or a next generation radio access network NG-RAN.

130. The device according to any one of claims 119 to 129, characterized in that The first service flow is a service data flow or a quality of service QoS flow.

131. 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 65.

132. A chip, characterized in that: The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 65.

133. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 65.

134. A computer program product, characterized in that A program is included, which causes a computer to execute the method according to any one of claims 1 to 65.

135. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 65.

Images