A congestion notification method, apparatus, device, and storage medium

Abstract

The disclosure provides a congestion notification method, device, equipment and storage medium, and belongs to the technical field of communication. The first node sends congestion related information to the second node when congestion occurs. Therefore, the method provided by the disclosure enables the core network device to obtain the congestion related information in the network of the wireless separation architecture, and enables the core network device or the application server to timely adjust the rate according to the congestion related information, thereby avoiding the delay or packet loss of the service, and improving the service quality of the service.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a congestion notification method / apparatus / device and storage medium. Background Technology

[0002] In XR (Extended Reality) services, the L4S (Low Latency Low Loss Scalable throughput) variant is introduced to enable useful information for rate adjustment in applications. This useful information is then transmitted to the application server through the core network equipment, allowing the application server to adjust the data rate in a timely manner based on the useful information, thereby reducing the latency of XR services.

[0003] In related technologies, there are several variations of the L4S tag.

[0004] Method 1: L4S tagging on NG-RAN (Next Generation Radio Access Network) nodes;

[0005] Method 2: L4S marking is performed by PSAUPF (User plane function) network elements based on the information provided by NG-RAN. Summary of the Invention

[0006] The congestion notification method / apparatus / device and storage medium disclosed herein are used to solve the technical problem that core network equipment cannot obtain congestion information in a radio-separated architecture.

[0007] In a first aspect, embodiments of this disclosure provide a congestion notification method, characterized in that it is executed by a first node and includes:

[0008] If congestion occurs, send congestion-related information to the second node.

[0009] In the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling core network devices or application servers to adjust their rates promptly based on this information, thereby preventing service delays or packet loss and improving service quality.

[0010] Secondly, embodiments of this disclosure provide a congestion notification method, executed by a second node, comprising:

[0011] Receive congestion-related information sent by the first node, wherein the congestion-related information is used to instruct the second node to perform congestion-related operations;

[0012] Perform congestion-related operations based on the congestion-related information.

[0013] Thirdly, embodiments of this disclosure provide a congestion notification method, executed by a third node, including:

[0014] Send a congestion report request to the first node, wherein the congestion report request is used to indicate whether the first node needs to perform congestion monitoring and / or whether it needs to send the congestion-related information to the second node.

[0015] Fourthly, embodiments of this disclosure provide a communication device configured in a first node, comprising:

[0016] The sending module is used to send congestion-related information to the second node in the event of congestion.

[0017] Fifthly, embodiments of this disclosure provide a communication device configured in a second node, comprising:

[0018] A receiving module is used to receive congestion-related information sent by a first node, wherein the congestion-related information is used to instruct the second node to perform congestion-related operations;

[0019] The execution module is used to perform congestion-related operations based on the congestion-related information.

[0020] Sixthly, embodiments of this disclosure provide a communication device configured in a third node, comprising:

[0021] The sending module is used to send congestion report request information to the first node, wherein the congestion report request information is used to indicate whether the first node needs to send the congestion-related information to the second node.

[0022] In a seventh aspect, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0023] Eighthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0024] Ninthly, embodiments of this disclosure provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the third aspect above.

[0025] In a tenth aspect, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0026] Eleventhly, embodiments of this disclosure provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0027] In a twelfth aspect, embodiments of this disclosure provide a communication device including a processor and a memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the third aspect above.

[0028] In a thirteenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0029] In a fourteenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0030] In a fifteenth aspect, embodiments of this disclosure provide a communication device including a processor and an interface circuit. The interface circuit is configured to receive code instructions and transmit them to the processor, which is configured to execute the code instructions to cause the device to perform the method described in the third aspect above.

[0031] In a sixteenth aspect, embodiments of this disclosure provide a communication system comprising the communication devices described in the third aspect to the fourth aspect, or the communication devices described in the seventh aspect to the ninth aspect, or the communication devices described in the tenth aspect to the twelfth aspect, or the communication devices described in the thirteenth aspect to the fifteenth aspect.

[0032] In a seventeenth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the network device described above, which, when executed, cause the terminal device to perform the method described in any one of the first to third aspects.

[0033] In an eighteenth aspect, this disclosure also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in any one of the first to third aspects.

[0034] In a nineteenth aspect, this disclosure provides a chip system including at least one processor and an interface for supporting network devices in implementing the functions involved in the methods described in any one of the first to third aspects, such as determining or processing at least one of the data and information involved in the aforementioned methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for source and slave nodes. The chip system may be composed of chips or may include chips and other discrete devices.

[0035] In a twentieth aspect, this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in any one of the first to third aspects. Attached Figure Description

[0036] The above and / or additional aspects and advantages of this disclosure will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, in which:

[0037] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure;

[0038] Figure 2a A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0039] Figure 2b A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure.

[0040] Figure 3 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0041] Figure 4 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0042] Figure 5 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0043] Figure 6A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0044] Figure 7 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0045] Figure 8 A flowchart illustrating a congestion notification method provided in one embodiment of this disclosure;

[0046] Figure 9 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0047] Figure 10 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0048] Figure 11 A flowchart illustrating a congestion notification method provided in one embodiment of this disclosure;

[0049] Figure 12 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0050] Figure 13 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0051] Figure 14 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0052] Figure 15 A flowchart illustrating a congestion notification method provided in yet another embodiment of this disclosure;

[0053] Figure 16 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0054] Figure 17 A flowchart illustrating a congestion notification method provided in one embodiment of this disclosure;

[0055] Figure 18 A flowchart illustrating a congestion notification method provided in another embodiment of this disclosure;

[0056] Figure 19 This is a schematic diagram of the structure of a communication device provided in one embodiment of the present disclosure;

[0057] Figure 20 This is a schematic diagram of the structure of a communication device provided in another embodiment of the present disclosure;

[0058] Figure 21This is a schematic diagram of the structure of a communication device provided in another embodiment of the present disclosure;

[0059] Figure 22 This is a block diagram of a user equipment provided in one embodiment of the present disclosure;

[0060] Figure 23 This is a block diagram of a network-side device provided in one embodiment of the present disclosure. Detailed Implementation

[0061] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this disclosure as detailed in the appended claims.

[0062] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0063] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the words “if” and “suppose” as used herein may be interpreted as “when”, “when”, or “in response to a determination”.

[0064] Embodiments of this disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this disclosure, and should not be construed as limiting this disclosure.

[0065] To better understand the congestion notification method disclosed in this embodiment, the communication system to which this embodiment applies is first described below.

[0066] Please see Figure 1 , Figure 1This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure. The communication system may include, but is not limited to, gNB-CU-CP (the next Generation Node B-Central Unit-Control Plane), gNB-CU-UP (the next Generation Node B-Central Unit-User Plane), and gNB-DU (the next Generation Node B-Distributed Unit). Specifically, gNB-CU-CP is responsible for the functions of the RRC (Radio Resource Control) and PDCP (Packet Data Convergence Protocol) control planes; gNB-CU-UP is responsible for the functions of the General Packet Radio Service Tunnel Protocol, SDAP (Service Data Adaptation Protocol), and PDCP user planes; and gNB-DU is responsible for the functions of RLC (Radio Link Control), MAC (Media Access Control), and PHY (Physical Layer).

[0067] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0068] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0069] It should be noted that if Method 1 of the aforementioned related technologies is adopted, the base station can detect uplink congestion through the UE's (User Equipment's) BSR (Buffer Status Report). However, in a radio-separated architecture network, the BSR is received by the DU (Distributed Unit), and the existing mechanism does not support direct communication between the DU and the core network equipment. Therefore, in a radio-separated architecture network, the core network equipment cannot obtain congestion information. If Method 2 of the related technologies is adopted, the existing mechanism does not support the core network equipment obtaining the base station's congestion information. Therefore, regardless of whether Method 1 or Method 2 is adopted, the existing mechanism does not support the core network equipment obtaining congestion information in a radio-separated architecture network. This prevents the core network equipment or application server from adjusting the rate in a timely manner based on the congestion information, leading to service delays or packet loss and reducing the quality of service.

[0070] The congestion notification method / apparatus / device and storage medium provided in the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0071] Figure 2a This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure, wherein the method is executed by a first node, as follows: Figure 2a As shown, the congestion notification method may include the following steps:

[0072] Step 201a: If congestion occurs, send congestion-related information to the second node.

[0073] In one embodiment of this invention, the congestion-related information may include at least one of the following:

[0074] Congestion indicators are used to indicate whether congestion has occurred (such as congestion start indicator, congestion end indicator, or a congestion cause value);

[0075] Congestion level, used to indicate the severity and grade of congestion;

[0076] Congestion time is used to indicate the duration of congestion (such as the length of time or a specific time period);

[0077] The recommended bit rate is used to instruct the sender to adjust the rate at the recommended bit rate.

[0078] The available buffer size is used to instruct the sender to adjust the rate based on the available buffer size;

[0079] Remaining transmission time is used to instruct the sender to adjust the rate based on the remaining transmission time of the data packet;

[0080] The direction of data flow corresponding to congestion (e.g., uplink or downlink);

[0081] The bearer information corresponding to the congestion (such as one or more DRB IDs and / or QoS flow IDs and / or PDU session IDs);

[0082] The cause of congestion is used to indicate the reason for the congestion (such as wireless link failure or overload).

[0083] Furthermore, in one embodiment of this disclosure, after the first node sends congestion-related information to the second node, the second node can perform congestion-related operations based on the congestion-related information in order to adjust the rate in a timely manner and thus avoid service delays or packet loss.

[0084] Furthermore, in one embodiment of this disclosure, when the first node and the second node are different, the method by which the corresponding first node sends congestion-related information to the second node also differs. This will be described in detail in subsequent embodiments.

[0085] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0086] Figure 2b This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure, wherein the method is executed by a first node, as follows: Figure 2b As shown, the congestion notification method may include the following steps:

[0087] Step 201b: Determine if the communication link is congested.

[0088] It should be noted that, in one embodiment of this disclosure, the communication link may be a logical channel for transmitting user data or a bearer for transmitting data, such as a PDU session (Protocol Data Unit).

[0089] Specifically, in one embodiment of this disclosure, the communication link may include at least one of the following:

[0090] PDU session;

[0091] QoS flow (Quality of Service Flow);

[0092] DRB (Data Radio Bearer);

[0093] UL (Up Link);

[0094] DL (Down Link).

[0095] Furthermore, in one embodiment of this disclosure, the method by which the first node determines whether a communication link is congested includes at least one of the following:

[0096] Determine whether congestion has occurred in the communication link by monitoring (such as packet detection);

[0097] Receive packet transmission information reported by user equipment and determine whether the communication link is congested based on the packet transmission information.

[0098] In one of the disclosed embodiments, the method for the first node to receive packet transmission information reported by the user equipment and determine whether the communication link is congested based on the packet transmission information may specifically include: receiving a BSR reported by the user equipment and determining whether the communication link is congested based on the remaining time of packet transmission in the BSR.

[0099] Specifically, in one embodiment of this disclosure, a BSR reported by a user equipment is received. The BSR may include the remaining time for packet transmission and the data to be transmitted uplink in the user equipment buffer. The first node can determine the time required for current data transmission based on the data to be transmitted uplink in the user equipment buffer and the channel resources currently supporting the uplink process. If the time required for current data transmission is greater than the remaining time for packet transmission, it means that the remaining time for packet transmission cannot complete the transmission of the data to be transmitted uplink, and the communication link is determined to be congested. Otherwise, if the time required for current data transmission is not greater than the remaining time for packet transmission, it means that the remaining time for packet transmission can complete the transmission of the data to be transmitted uplink, and the communication link is determined not to be congested.

[0100] Furthermore, in one embodiment of this disclosure, the first node can periodically determine whether the communication link is congested. In another embodiment of this disclosure, the first node can determine whether the communication link is congested after receiving an indication that congestion detection is required. This will be described in detail in subsequent embodiments.

[0101] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0102] It should be noted that, in one embodiment of this disclosure, the congestion notification method provided in the above embodiment is also related to the types of the first node and the second node. Specifically, when the first node and the second node are different, the specific execution steps of the congestion notification method will also differ. The following provides a detailed description of the congestion notification methods corresponding to different first nodes and second nodes.

[0103] Figure 3 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 3 In a corresponding embodiment, the first node can be gNB-DU (the next Generation NodeB-Distributed Unit), and the second node can be gNB-CU-UP (the next Generation Node B-Central Unit-User Plane). And, as... Figure 3 As shown, the congestion notification method may include the following steps:

[0104] Step 301: If congestion occurs, send congestion-related information to the second node via the NR (New Radio) user plane protocol.

[0105] In one embodiment of this disclosure, the method by which the first node sends congestion-related information to the second node via the NR user plane protocol may include: the first node generating a frame including congestion information and sending the frame including congestion information to the second node via the NR user plane protocol, wherein the frame including congestion information includes congestion-related information.

[0106] Furthermore, in one disclosed embodiment, the aforementioned first node can generate frames in various formats that include congestion information.

[0107] Specifically, in one embodiment of this disclosure, the first node can generate a DL DATA DELIVERYSTATUS frame and send the DL DATA DELIVERY STATUS frame to the second node via the NR user plane protocol, wherein the PDU Type corresponding to the DL DATA DELIVERY STATUS frame is 1.

[0108] In one embodiment of this disclosure, when the first node generates a DL DATA DELIVERY STATUS frame and the PDU Type is 1, the number of bits that can be used to indicate the cause of congestion in the DL DATA DELIVERY STATUS frame is 8 bits. Based on this, congestion-related information can use a new cause value to indicate the cause of congestion.

[0109] For example, in one embodiment of this disclosure, the value range is: {0 = UNKNOWN, 1 = RADIO LINK OUTAGE, 2 = RADIO LINK RESUME, 3 = UL RADIO LINK OUTAGE, 4 = DL RADIO LINK OUTAGE, 5 = UL RADIO LINK RESUME, 6 = DL RADIO LINK RESUME, 7 = UL CONGESTION, 8 = DL CONGESTION, 9-228 = reserved for future value extensions, 229-255 = reserved for test purposes}

[0110] Furthermore, in another embodiment of this disclosure, the first node can generate a new frame format and send the new frame format to the second node via the NR user plane protocol. For example, in one embodiment of this disclosure, the new frame format may be a Congestion Stutas or a Congestion Feedback.

[0111] It should be noted that, in one embodiment of this disclosure, the method of the first node sending congestion-related information to the second node in step 301 can be applied to variations of the L4S tag in method one and method two of the above scheme. That is, regardless of whether method one or method two is used, step 301 can be used to enable the core network device to obtain congestion-related information in the wireless separation architecture network and adjust the rate in a timely manner according to the congestion-related information, thereby avoiding service delays.

[0112] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0113] Figure 4 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 4 In a corresponding embodiment, the first node can be a base station, and the second node can be a user plane node of the core network. And, as... Figure 4 As shown, the congestion notification method may include the following steps:

[0114] Step 401: If congestion occurs, send congestion-related information to the second node via PDU Session User Plane Protocol frames.

[0115] In one embodiment of this disclosure, the method by which the first node sends congestion-related information to the second node via a PDU Session User PlaneProtocol frame may include: the first node sending congestion-related information to the second node via a UL PDU Session Information frame sent by the NG-RAN to the UPF, wherein the PDU type corresponding to the UL PDU Session Information is 1.

[0116] Furthermore, in another embodiment of this disclosure, the first node sends congestion-related information to the second node via a new user plane frame sent to the UPF through the NG-RAN. For example, in one embodiment of this disclosure, the new user plane frame may be Congestion Information.

[0117] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0118] Figure 5 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 5 In a corresponding embodiment, the first node can be gNB-DU, and the second node can be gNB-CU-CP (the next Generation Node B-Central Unit-Control Plane) or gNB-CU (the next Generation Node B-Central Unit). And, as... Figure 5 As shown, the congestion notification method may include the following steps:

[0119] Step 501: If congestion occurs, send congestion-related information to the second node via F1AP (F1 Application Protocol) messages.

[0120] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0121] Figure 6This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 6 In a corresponding embodiment, the first node can be a base station, and the second node can be a control plane node of the core network (such as AMF (Access and Mobility Management Function) / SMF (Session Management Function)). And, as... Figure 6 As shown, the congestion notification method may include the following steps:

[0122] Step 601: If congestion occurs, send congestion-related information to the second node via NGAP (Next Generation Application Protocol) messages.

[0123] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0124] Figure 7 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 7 In a corresponding embodiment, the first node can be a base station, and the second node can be a UE. And, as... Figure 7 As shown, the congestion notification method may include the following steps:

[0125] Step 701: If congestion occurs, send congestion-related information to the second node via the air interface protocol.

[0126] In one embodiment of this disclosure, the method of sending congestion-related information to the second node via an air interface protocol may include sending congestion-related information to the second node via RRC (Radio Resource Control) messages, MAC (Media Access Control) signaling, or PHY (Physical Layer) signaling.

[0127] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0128] Figure 8 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, such as... Figure 8 As shown, the congestion notification method may include the following steps:

[0129] Step 801: Receive the congestion report request information sent by the third node.

[0130] In one embodiment of this disclosure, the congestion report request information is used to indicate whether the first node needs to perform congestion detection and / or whether it needs to send the congestion-related information to the second node.

[0131] Furthermore, in one embodiment of this disclosure, the congestion report request information may include at least one of the following:

[0132] Congestion Request Indication (CRI) information;

[0133] Threshold for congestion request reporting;

[0134] Bearer information corresponding to congestion requests;

[0135] The direction of data flow corresponding to the congestion request;

[0136] Congestion indication frame or bit.

[0137] Specifically, in one embodiment of this disclosure, the congestion request indication information may include N bits, where N is a positive integer. For example, in one embodiment of this disclosure, assuming the congestion request indication information includes 2 bits, where when the bit is 01, the congestion request indication information indicates that the first node needs to perform congestion detection; when the bit is 10, the congestion request indication information indicates that the first node needs to send congestion-related information to the second node; when the bit is 11, the congestion request indication information indicates that the first node needs to perform congestion detection and send congestion-related information to the second node; and when the bit is 00, the congestion request indication information indicates that the first node does not need to perform congestion detection and does not need to send congestion-related information to the second node.

[0138] Furthermore, in one embodiment of this disclosure, the congestion request reporting threshold may include, but is not limited to, a buffer size threshold, a data packet waiting time threshold, and a data packet remaining transmission time threshold. In one embodiment of this disclosure, after receiving the congestion report request information, the first node may send congestion-related information to the second node if the congestion request reporting threshold is exceeded or falls below it.

[0139] For example, in one embodiment of this disclosure, assuming that the threshold for congestion request reporting is a threshold for the remaining time of a data packet, the remaining transmission time of the current data packet is compared with the threshold for the remaining transmission time of the data packet. If the remaining transmission time of the current data packet exceeds the threshold for the remaining transmission time of the data packet, it is determined that the congestion-related information needs to be sent to the second node.

[0140] Furthermore, in one embodiment of this disclosure, the bearer information corresponding to the congestion request may include at least one of PDU session, QoS flow, and DRB.

[0141] Furthermore, in one embodiment of this disclosure, the bearer information corresponding to the congestion request may include one or more PDU session IDs, QoS flow IDs, and / or DRB IDs, used to indicate the specific bearer or communication link for which congestion measurement is required.

[0142] For example, in one embodiment of this disclosure, assuming that the bearer information corresponding to the congestion request is at least one PDU session ID, it is determined that congestion detection needs to be performed on the bearer or communication link corresponding to the PDU session ID, and when it is determined that the bearer or communication link corresponding to the PDU session ID is congested, congestion-related information is sent to the second node.

[0143] For example, in one embodiment of this disclosure, assuming that the bearer information corresponding to the congestion request is at least one QoS flow ID, it is determined that congestion detection needs to be performed on the bearer or communication link corresponding to the QoS flow ID, and when it is determined that the bearer or communication link corresponding to the QoS flow ID is congested, congestion-related information is sent to the second node.

[0144] For example, in one embodiment of this disclosure, assuming that the bearer information corresponding to the congestion request is at least one DRB ID, it is determined that congestion detection needs to be performed on the bearer or communication link corresponding to the DRB ID, and when it is determined that the bearer or communication link corresponding to the DRB ID is congested, congestion-related information is sent to the second node.

[0145] Furthermore, in one embodiment of this disclosure, the data flow direction corresponding to the congestion request may include at least one of uplink and downlink.

[0146] For example, in one embodiment of this disclosure, assuming that the data flow direction corresponding to the congestion request is uplink, it is determined that congestion detection of the uplink is required, and when it is determined that congestion has occurred in the uplink, congestion-related information is sent to the second node.

[0147] Furthermore, in one embodiment of this disclosure, the aforementioned congestion indication frame or bit may include a polling frame or polling bit.

[0148] For example, in one embodiment of this disclosure, assuming that the congestion report request information includes polling frames or polling bits, it is determined that congestion detection is required and / or the congestion-related information needs to be sent to a second node.

[0149] It should be noted that in one embodiment of this disclosure, the third node and the second node may be the same or different. Furthermore, when the second node and the third node are the same or different, the method for receiving the congestion report request information sent by the third node will also differ. This will be described in detail in subsequent embodiments.

[0150] Step 802: When the congestion report request information indicates that the first node needs to perform congestion detection or needs to send congestion-related information to the second node, send the congestion-related information to the second node.

[0151] In one embodiment of this disclosure, when a congestion report request indicates that a first node needs to perform congestion detection or needs to send congestion-related information to a second node, the first node can send congestion-related information to the second node based on the information included in the congestion report request.

[0152] Specifically, in one embodiment of this disclosure, when a congestion report request information indicates that a first node needs to perform congestion detection or needs to send congestion-related information to a second node, congestion detection is performed based on the congestion request report information, and congestion-related information is sent to the second node when congestion is detected. The congestion report request information includes conditions for performing congestion detection. In one embodiment of this disclosure, the conditions for performing congestion detection may include at least one of the following: a congestion request report threshold, bearer information corresponding to the congestion request, and the data flow direction corresponding to the congestion request.

[0153] For example, in one embodiment of this disclosure, assuming that the congestion report request information includes congestion request indication information and a congestion request report threshold, wherein the congestion request indication information is 01, the first node performs congestion detection according to the congestion request report threshold, and sends congestion-related information to the second node when the congestion is exceeded or below the congestion request report threshold.

[0154] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0155] Figure 9 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 9 In the corresponding embodiment, the second node and the third node are the same. And, as... Figure 9 As shown, the congestion notification method may include the following steps:

[0156] Step 901: Receive the congestion report request information sent by the third node through the user plane protocol.

[0157] In one embodiment of this disclosure, when the first node and the third node correspond to different nodes, the method for receiving congestion report request information sent by the third node via the user plane protocol is also different.

[0158] Specifically, in one embodiment of this disclosure, when the first node is a base station (NG-RAN) and the third node is a core network node (AMF / SMF), the method for receiving congestion report request information sent by the third node via the user plane protocol may include: receiving congestion report request information sent by the third node via NGAP message.

[0159] Furthermore, in another embodiment of this disclosure, when the first node is gNB-DU and the third node is gNB-CU or gNB-CU-CP, the method for receiving congestion report request information sent by the third node via the user plane protocol may include: receiving congestion report request information sent by the third node via F1AP message.

[0160] Furthermore, in another embodiment of this disclosure, when the second and third nodes are gNB-CU-UP, the method for receiving congestion report request information sent by the third node via the user plane protocol may include: receiving the congestion report request information sent by the third node via an NR user plane protocol frame. For example, in one embodiment of this disclosure, the congestion report request information sent by the third node is received via a polling frame or polling bit.

[0161] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0162] Figure 10 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a first node, wherein... Figure 10 In the corresponding embodiments, the second node and the third node are different. And, as... Figure 10 As shown, the congestion notification method may include the following steps:

[0163] Step 1001: Receive congestion report request information sent by the third node through the information established by QoS flow or the information modified by QoS flow, wherein the information established by QoS flow or the information modified by QoS flow includes the congestion report request information.

[0164] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0165] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0166] Figure 11This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, as follows: Figure 11 As shown, the congestion notification method may include the following steps:

[0167] Step 1101: Receive congestion-related information sent by the first node.

[0168] Furthermore, in one embodiment of this invention, the aforementioned congestion-related information may include at least one of the following:

[0169] Congestion indicators are used to indicate whether congestion has occurred (such as congestion start indicator, congestion end indicator, or a congestion cause value);

[0170] Congestion level, used to indicate the severity and grade of congestion;

[0171] Congestion time is used to indicate the duration of congestion (such as the length of time or a specific time period);

[0172] The recommended bit rate is used to instruct the sender to adjust the rate at the recommended bit rate.

[0173] The available buffer size is used to instruct the sender to adjust the rate based on the available buffer size;

[0174] Remaining transmission time is used to instruct the sender to adjust the rate based on the remaining transmission time of the data packet;

[0175] The direction of data flow corresponding to congestion (e.g., uplink or downlink):

[0176] The bearer information corresponding to the congestion (such as one or more DRB IDs and / or QoS flow IDs and / or PDU session IDs);

[0177] The cause of congestion is used to indicate the reason for the congestion (such as wireless link failure or overload).

[0178] Furthermore, in one embodiment of this disclosure, when the first node and the second node are different, the method by which the corresponding second node receives congestion-related information sent by the first node also differs. This will be described in detail in subsequent embodiments.

[0179] Step 1102: Perform congestion-related operations based on congestion-related information.

[0180] In one embodiment of this disclosure, performing congestion-related operations may include at least one of the following:

[0181] Perform congestion-related marking;

[0182] Send congestion-related information to the fourth node.

[0183] Furthermore, in one embodiment of this disclosure, the method for performing congestion-related marking may include performing ECN (Explicit Congestion Notification) marking in L4S.

[0184] Specifically, in one embodiment of this disclosure, the second node performs ECN tagging at the IP (Internet Protocol) layer.

[0185] Furthermore, in another embodiment of this disclosure, the second node performs ECN marking at the GTP-U (General Packet Radio Service Tunnel Protocol) layer.

[0186] Furthermore, in one embodiment of this disclosure, when sending congestion-related information to the fourth node, the first node may be gNB-DU, the second node may be gNB-CU-UP, and the fourth node may be a core network node (such as UPF).

[0187] Furthermore, in another embodiment of this disclosure, when sending congestion-related information to the fourth node, the first node may be gNB-DU, the second node may be gNB-CU-CP, and the fourth node may be a core network node (such as AMF or SMF).

[0188] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0189] Figure 12 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, wherein... Figure 12 In a corresponding embodiment, the first node can be gNB-DU, and the second node can be gNB-CU-UP. And, as... Figure 12 As shown, the congestion notification method may include the following steps:

[0190] Step 1201: Receive congestion-related information sent by the first node via the NR user plane protocol.

[0191] In one embodiment of this disclosure, the method of receiving congestion-related information sent by a first node via the NR user plane protocol may include receiving a frame containing congestion information sent by the first node via the NR user plane protocol, wherein the frame containing congestion information includes congestion-related information.

[0192] Furthermore, in one disclosed embodiment, the frame containing congestion information may have a variety of different formats.

[0193] Specifically, in one embodiment of this disclosure, a DL DATA DELIVERY STATUS frame sent by a first node is received via the NR user plane protocol, wherein the PDU Type corresponding to the DL DATA DELIVERY STATUS frame is 1.

[0194] In another embodiment of this disclosure, a new frame format sent by the first node is received via the NR user plane protocol. For example, in one embodiment of this disclosure, the new frame format may be Congestion Stutas or Congestion Feedback.

[0195] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0196] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0197] Figure 13 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, wherein... Figure 13 In a corresponding embodiment, the first node can be a base station, and the second node can be a user plane node of the core network. And, as... Figure 13 As shown, the congestion notification method may include the following steps:

[0198] Step 1301: Receive congestion-related information sent by the first node via the PDU Session User Plane Protocol frame.

[0199] In one embodiment of this disclosure, the method of receiving congestion-related information sent by the first node via a PDU Session User Plane Protocol frame may include: receiving congestion-related information sent by the first node via a UL PDU SessionInformation frame sent by NG-RAN to UPF.

[0200] Furthermore, in another embodiment of this disclosure, the method of receiving congestion-related information sent by the first node via a PDU Session User Plane Protocol frame may include: receiving congestion-related information sent by the first node via a new user plane frame sent from the NG-RAN to the UPF. For example, in one embodiment of this disclosure, the new user plane frame may be Congestion Information.

[0201] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0202] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0203] Figure 14 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, wherein... Figure 14 In a corresponding embodiment, the first node can be gNB-DU, and the second node can be gNB-CU-CP or gNB-CU. And, as... Figure 14 As shown, the congestion notification method may include the following steps:

[0204] Step 1401: Receive congestion-related information sent by the first node via F1AP message.

[0205] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0206] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0207] Figure 15 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, wherein... Figure 15 In a corresponding embodiment, the first node can be a base station, and the second node can be a control plane node (such as AMF / SMF) of the core network equipment. And, as... Figure 15 As shown, the congestion notification method may include the following steps:

[0208] Step 1501: Receive congestion-related information sent by the first node via NGAP message.

[0209] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0210] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0211] Figure 16 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, wherein... Figure 16 In a corresponding embodiment, the first node can be a base station, and the second node can be a UE. And, as... Figure 16 As shown, the congestion notification method may include the following steps:

[0212] Step 1601: Receive congestion-related information sent by the first node via the air interface protocol.

[0213] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0214] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0215] Figure 17 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a second node, as follows: Figure 17 As shown, the congestion notification method may include the following steps:

[0216] Step 1701: Send a congestion report request to the first node.

[0217] In one embodiment of this disclosure, the aforementioned congestion report request information can be used to indicate whether the first node needs to perform congestion monitoring and / or whether it needs to send congestion-related information to the second node.

[0218] Furthermore, in one embodiment of this disclosure, the congestion report request information may include at least one of the following:

[0219] Congestion Request Indication (CRI) information;

[0220] Threshold for congestion request reporting;

[0221] Bearer information corresponding to congestion requests;

[0222] The direction of data flow corresponding to the congestion request;

[0223] Congestion indication frame or bit.

[0224] Furthermore, in one embodiment of this disclosure, the method of sending congestion report request information to the first node may include: sending congestion report request information to the first node via a user plane protocol.

[0225] In one embodiment of this disclosure, when the first node and the second node are different, the method of sending congestion report request information to the first node through the user plane protocol is also different.

[0226] Specifically, in one embodiment of this disclosure, when the first node is a base station (NG-RAN) and the second node is a core network node (AMF / SMF), the method of sending congestion report request information to the first node via the user plane protocol may include: sending congestion report request information to the first node via NGAP message.

[0227] Furthermore, in another embodiment of this disclosure, when the first node is gNB-DU and the second node is gNB-CU or gNB-CU-CP, the method of sending congestion report request information to the first node via the user plane protocol may include: sending congestion report request information to the first node via F1AP message.

[0228] Furthermore, in another embodiment of this disclosure, when the second node is gNB-CU-UP, the method for sending congestion report request information to the first node via the user plane protocol may include: sending congestion report request information to the first node via an NR user plane protocol frame. For example, in one embodiment of this disclosure, congestion report request information is sent to the first node via a polling frame or polling bit.

[0229] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0230] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0231] Figure 18 This is a flowchart illustrating a congestion notification method provided in an embodiment of this disclosure. The method is executed by a third node, such as... Figure 18 As shown, the congestion notification method may include the following steps:

[0232] Step 1801: Send a congestion report request to the first node.

[0233] In one embodiment of this disclosure, the aforementioned congestion report request information can be used to indicate whether the first node needs to perform congestion monitoring and / or whether it needs to send congestion-related information to the second node.

[0234] Furthermore, in one embodiment of this disclosure, the congestion report request information may include at least one of the following:

[0235] Congestion Request Indication (CRI) information;

[0236] Threshold for congestion request reporting;

[0237] Bearer information corresponding to congestion requests;

[0238] The direction of data flow corresponding to the congestion request;

[0239] Congestion indication frame or bit.

[0240] Furthermore, in one embodiment of this disclosure, the method of sending congestion report request information to the first node may include: sending congestion report request information to the first node through information established by QoS flow or information modified by QoS flow, wherein the information established by QoS flow includes the congestion report request information.

[0241] In addition, other details regarding this embodiment can be found in the description of the above embodiments.

[0242] In summary, in the congestion notification method provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used, the first node can send congestion-related information to the second node when congestion occurs. This allows core network devices in a radio-separated architecture network to obtain congestion-related information, enabling the core network devices or application servers to adjust their rates promptly based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0243] Figure 19 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure, as shown below. Figure 19 As shown, the device may include:

[0244] The sending module 1901 is used to send congestion-related information to the second node when congestion occurs, wherein the congestion-related information is used to instruct the second node to perform congestion-related operations.

[0245] In summary, in the communication device provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used in the method provided in this disclosure, the first node can send congestion-related information to the second node when congestion occurs. This allows the core network device to obtain congestion-related information in a wireless-separated architecture network, enabling the core network device or application server to adjust its rate in a timely manner based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0246] Optionally, in one embodiment of this disclosure, the above-described apparatus is further used for:

[0247] Determine if the communication link is congested.

[0248] Optionally, in one embodiment of this disclosure, the above-described apparatus is further used for at least one of the following:

[0249] Determine whether communication links are congested by monitoring;

[0250] Receive packet transmission information reported by user equipment and determine whether the communication link is congested based on the packet transmission information.

[0251] Optionally, in one embodiment of this disclosure, the communication link includes at least one of the following:

[0252] PDU session;

[0253] QoS flow;

[0254] DRB;

[0255] UL;

[0256] DL.

[0257] Optionally, in one embodiment of this disclosure, congestion-related information includes at least one of the following:

[0258] Congestion indication;

[0259] Congestion level;

[0260] Congestion time;

[0261] Recommended bit rate;

[0262] Available cache size;

[0263] Remaining transmission time;

[0264] The direction of data flow corresponding to congestion;

[0265] The bearer information corresponding to congestion;

[0266] The cause of the congestion.

[0267] Optionally, in one embodiment of this disclosure, the first node is gNB-DU, the second node is gNB-CU-UP, and the aforementioned transmitting module 1901 is further configured to:

[0268] Congestion-related information is sent to the second node via the NR user plane protocol.

[0269] Optionally, in one embodiment of this disclosure, the sending module 1902 is further configured to:

[0270] The first node generates a frame that includes congestion information, and the frame that includes congestion information contains congestion-related information.

[0271] Frames containing congestion information are sent to the second node via the NR user plane protocol.

[0272] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a user plane node of the core network, and the aforementioned sending module 1901 is further used for:

[0273] Congestion-related information is sent to the second node via PDU Sequence User Plane Protocol frames.

[0274] Optionally, in one embodiment of this disclosure, the first node is gNB-DU, the second node is gNB-CU-CP or gNB-CU, and the aforementioned transmitting module 1901 is further configured to:

[0275] Congestion-related information is sent to the second node via FLAP messages.

[0276] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a control plane node of the core network, and the aforementioned transmitting module 1901 is further used for:

[0277] Congestion-related information is sent to the second node via NGAP messages.

[0278] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a user equipment (UE), and the aforementioned transmitting module 1901 is further configured to:

[0279] Congestion-related information is sent to the second node via the air interface protocol.

[0280] Optionally, in one embodiment of this disclosure, the above-described apparatus is further used for:

[0281] Receive congestion report request information sent by the third node, wherein the congestion report request information is used to indicate whether the first node needs to perform congestion detection and / or whether it needs to send congestion-related information to the second node;

[0282] Based on the congestion report request information, send congestion-related information to the second node.

[0283] Optionally, in one embodiment of this disclosure, the congestion report request information includes at least one of the following:

[0284] Congestion Request Indication (CRI) information;

[0285] Threshold for congestion request reporting;

[0286] Bearer information corresponding to congestion requests;

[0287] The direction of data flow corresponding to the congestion request;

[0288] Congestion indication frame or bit.

[0289] Optionally, in one embodiment of this disclosure, the third node may be the same as or different from the second node.

[0290] Optionally, in one embodiment of this disclosure, when the third node is the same as the second node, the above-described apparatus is further used to:

[0291] Receive congestion report request information sent by the third node through the user plane protocol.

[0292] Optionally, in one embodiment of this disclosure, when the third node is different from the second node, the above-described apparatus is further used to:

[0293] The information established through QoS flow includes congestion report request information sent by the third node.

[0294] The congestion report request information sent by the third node is received through QoS flow modified information, which includes the congestion report request information.

[0295] Figure 20 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure, as shown below. Figure 20 As shown, the device may include:

[0296] Receiver module 2001 receives congestion-related information sent by the first node;

[0297] Execution module 2002 performs congestion-related operations based on congestion-related information.

[0298] In summary, in the communication device provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used in the method provided in this disclosure, the first node can send congestion-related information to the second node when congestion occurs. This allows the core network device to obtain congestion-related information in a wireless-separated architecture network, enabling the core network device or application server to adjust its rate in a timely manner based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0299] Optionally, in one embodiment of this disclosure, congestion-related information includes at least one of the following:

[0300] Congestion indication;

[0301] Congestion level;

[0302] Congestion time;

[0303] Recommended bit rate;

[0304] Available cache size;

[0305] Remaining transmission time;

[0306] The direction of data flow corresponding to congestion;

[0307] The information carried by the congestion;

[0308] The cause of congestion.

[0309] Optionally, in one embodiment of this disclosure, the first node is gNB-DU, the second node is gNB-CU-UP, and the receiving module 2001 is further configured to:

[0310] The congestion-related information is received from the first node via the NR user plane protocol.

[0311] Optionally, in one embodiment of this disclosure, the receiving module 2001 is further configured to;

[0312] The first node sends a frame containing congestion information via the NR user plane protocol. The frame containing congestion information includes congestion-related information.

[0313] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a core network node, and the receiving module 2001 is further configured to:

[0314] The congestion-related information is received from the first node via the PDU Session User Plane Protocol frame.

[0315] Optionally, in one embodiment of this disclosure, the first node is gNB-DU, the second node is gNB-CU-CP or gNB-CU, and the receiving module 2001 is further configured to:

[0316] The congestion-related information is received from the first node via F1AP messages.

[0317] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a core network node, and the receiving module 2001 is further configured to:

[0318] The congestion-related information is received from the first node via NGAP messages.

[0319] Optionally, in one embodiment of this disclosure, the first node is a base station, the second node is a UE, and the receiving module 2001 is further configured to:

[0320] Receive congestion-related information sent by the first node via the air interface protocol.

[0321] Optionally, in one embodiment of this disclosure, the above-described apparatus is further used for:

[0322] Send a congestion report request to the first node, wherein the congestion report request is used to indicate whether the first node needs to perform congestion monitoring and / or whether it needs to send the congestion-related information to the second node.

[0323] Optionally, in one embodiment of this disclosure, the above-described apparatus is further used for:

[0324] The user plane protocol sends a congestion report request to the first node.

[0325] Optionally, in one embodiment of this disclosure, the congestion report request information includes at least one of the following:

[0326] Congestion Request Indication (CRI) information;

[0327] Threshold for congestion request reporting;

[0328] Bearer information corresponding to congestion requests;

[0329] The direction of data flow corresponding to the congestion request;

[0330] Congestion indication frame or bit.

[0331] Optionally, in one embodiment of this disclosure, congestion-related operations include at least one of the following:

[0332] Perform congestion-related marking;

[0333] Send congestion-related information to the fourth node.

[0334] Figure 21 This is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure, as shown below. Figure 21 As shown, the device may include:

[0335] The sending module 2101 is used to send congestion report request information to the first node, wherein the congestion report request information is used to indicate whether the first node needs to perform congestion monitoring and / or whether it needs to send congestion-related information to the second node.

[0336] In summary, in the communication device provided in this disclosure, the first node sends congestion-related information to the second node when congestion occurs. Therefore, regardless of whether Method 1 or Method 2 is used in the method provided in this disclosure, the first node can send congestion-related information to the second node when congestion occurs. This allows the core network device to obtain congestion-related information in a wireless-separated architecture network, enabling the core network device or application server to adjust its rate in a timely manner based on the congestion-related information, thereby avoiding service delays or packet loss and improving service quality.

[0337] Optionally, in one embodiment of this disclosure, the congestion report request information includes at least one of the following:

[0338] Congestion Request Indication (CRI) information;

[0339] Threshold for congestion request reporting;

[0340] Bearer information corresponding to congestion requests;

[0341] The direction of data flow corresponding to the congestion request;

[0342] Congestion indication frame or bit.

[0343] Optionally, in one embodiment of this disclosure, the sending module 2101 is further configured to:

[0344] The congestion report request information is sent to the first node based on the information established by the QoS flow, wherein the information established by the QoS flow includes the congestion report request information;

[0345] The congestion report request information is sent to the first node based on the information modified by the QoS flow, which includes the congestion report request information.

[0346] Please see Figure 22 , Figure 22This is a schematic diagram of the structure of a communication device 2200 provided in an embodiment of this application. The communication device 2200 can be a network device, a terminal device, a chip, chip system, or processor that supports the implementation of the above methods in a network device, or a chip, chip system, or processor that supports the implementation of the above methods in a terminal device. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0347] The communication device 2200 may include one or more processors 2201. The processor 2201 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0348] Optionally, the communication device 2200 may further include one or more memories 2202, which may store a computer program 2204. The processor 2201 executes the computer program 2204 to cause the communication device 2200 to perform the method described in the above method embodiments. Optionally, the memory 2202 may also store data. The communication device 2200 and the memory 2202 may be provided separately or integrated together.

[0349] Optionally, the communication device 2200 may also include a transceiver 2205 and an antenna 2206. The transceiver 2205 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 2205 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0350] Optionally, the communication device 2200 may further include one or more interface circuits 2207. The interface circuits 2207 are used to receive code instructions and transmit them to the processor 2201. The processor 2201 executes the code instructions to cause the communication device 2200 to perform the methods described in the above method embodiments.

[0351] Communication device 2200 is a terminal device: transceiver 2205 is used to perform... Figure 3 Steps 301-302 in the text; Figure 4 Steps 401 to 402 in the process; Figure 5 Steps 501 to 503 in the process; Figure 6 Steps 601a to 603a in a; Figure 6Steps 601b to 602b in b. Processor 2201 is used to execute step 201 in Figure 2; Figure 3 Steps 303-304 in the text; Figure 4 Step 403 in the middle; Figure 5 Steps 504 and 505 in the text; Figure 6 Step 604a in a; Figure 6 Step 603b in b; Figure 7 Steps 701-702 in the text.

[0352] Communication device 2200 is a network device: transceiver 2205 is used to perform... Figure 11 Step 1102a in a. Processor 2201 is used to execute Figure 8 Step 801 in the middle; Figure 9 Steps 901 to 904 in the process; Figure 10 Steps 1001 to 1005 in the process; Figure 11 Step 1101a in a; Figure 11 Steps 1101b and 1102b in b.

[0353] In one implementation, the processor 2201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0354] In one implementation, processor 2201 may store computer program 2203, which runs on processor 2201 and enables communication device 2200 to execute the methods described in the above method embodiments. Computer program 2203 may be embedded in processor 2201; in this case, processor 2201 may be implemented in hardware.

[0355] In one implementation, the communication device 2200 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0356] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 22 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0357] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0358] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0359] (3) ASIC, such as modem;

[0360] (4) Modules that can be embedded in other devices;

[0361] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0362] (6) Other equipment.

[0363] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 23 The diagram shows the structure of the chip. Figure 23 The chip shown includes a processor 2301 and an interface 2302. There can be one or more processors 2301, and multiple interfaces 2302.

[0364] Optionally, the chip also includes a memory 2303, which is used to store necessary computer programs and data.

[0365] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0366] This application also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0367] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0368] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0369] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0370] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0371] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0372] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0373] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0374] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0375] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A congestion notification method, characterized in that, The method is executed by the first node and includes: If congestion occurs, send congestion-related information to the second node; Sending congestion-related information to the second node includes: The congestion-related information is sent to the second node via the New Radio (NR) user plane protocol. The first node is the base station distributed unit (gNB-DU), and the second node is the base station central unit user plane (gNB-CU-UP). The congestion-related information is also sent by the second node to the core network node. or, The first node is a base station, and the second node is a user plane node of the core network. The congestion-related information is sent to the second node through the Protocol Data Unit Session User Plane Protocol (PDU) frame. The method further includes: The first node receives a congestion report request message sent by a third node, wherein the congestion report request message is used to instruct the first node whether to perform congestion detection and / or whether to send the congestion-related information to the second node. When the congestion report request information instructs the first node to perform congestion detection or to send the congestion-related information to the second node, the congestion-related information is sent to the second node; The third node is different from the second node.

2. The method as described in claim 1, characterized in that, The method further includes: Determine if the communication link is congested.

3. The method as described in claim 2, characterized in that, Determining whether a communication link is congested includes at least one of the following: Determine whether communication links are congested by monitoring; Receive packet transmission information reported by the user equipment, and determine whether the communication link is congested based on the packet transmission information.

4. The method as described in claim 3, characterized in that, The communication link includes at least one of the following: Protocol Data Unit (PDU) session; Quality of Service (QoS) flow; Wireless Data Bearer (DRB); Uplink UL; Downlink (DL).

5. The method as described in claim 1, characterized in that, The congestion-related information includes at least one of the following: Congestion indication; Congestion level; Congestion time; Recommended bit rate; Available cache size; Remaining transmission time; The direction of data flow corresponding to congestion; The information carried by the congestion; The cause of congestion.

6. The method as described in claim 1, characterized in that, Congestion-related information is sent to the second node via the NR user plane protocol, including: The first node generates a frame including congestion information, wherein the frame including congestion information includes congestion-related information; Frames containing congestion information are sent to the second node via the NR user plane protocol.

7. The method as described in claim 1, characterized in that, The congestion report request information includes at least one of the following: Congestion Request Indication (CRI) information; Threshold for congestion request reporting; Bearer information corresponding to congestion requests; The direction of data flow corresponding to the congestion request; Congestion indication frame or bit.

8. The method as described in claim 1, characterized in that, When the third node is the same as the second node, receiving the congestion report request information sent by the third node includes: The user plane protocol receives the congestion report request information sent by the third node.

9. The method as described in claim 1, characterized in that, When the third node is different from the second node, receiving the congestion report request information sent by the third node includes any one of the following: The information established through QoS flow includes the congestion report request information sent by the third node. The congestion report request information sent by the third node is received through QoS flow modification information, wherein the QoS flow modification information includes the congestion report request information.

10. A congestion notification method, characterized in that, The method is executed by the second node, including: The first node receives congestion-related information sent by the first node, wherein the congestion-related information is sent by the first node upon receiving a congestion report request information sent by the third node, and the congestion report request information indicates whether the first node performs congestion detection and / or whether to send the congestion-related information to the second node, wherein the third node is different from the second node. Perform congestion-related operations based on the congestion-related information; The congestion-related information received from the first node includes: The congestion-related information sent by the first node is received through the NR user plane protocol. The first node is gNB-DU and the second node is gNB-CU-UP. The congestion-related information is also used by the second node to send to the core network node. or, The congestion-related information sent by the first node is received through the PDU Session User Plane Protocol frame. The first node is a base station, and the second node is a core network node.

11. The method as described in claim 10, characterized in that, The congestion-related information includes at least one of the following: Congestion indication; Congestion level; Congestion time; Recommended bit rate; Available cache size; Remaining transmission time; The direction of data flow corresponding to congestion; The information carried by the congestion; The cause of congestion.

12. The method as described in claim 10, characterized in that, The step of receiving congestion-related information sent by the first node via the NR user plane protocol includes: The first node sends a frame containing congestion information via the NR user plane protocol. The frame containing congestion information includes congestion-related information.

13. The method as described in claim 10, characterized in that, The method includes: Send a congestion report request to the first node, wherein the congestion report request is used to indicate whether the first node performs congestion monitoring and / or whether to send the congestion-related information to the second node.

14. The method as described in claim 13, characterized in that, Sending the congestion report request information to the first node includes: The user plane protocol is used to send a congestion report request to the first node.

15. The method according to any one of claims 13 to 14, characterized in that, The congestion report request information includes at least one of the following: Congestion Request Indication (CRI) information; Threshold for congestion request reporting; Bearer information corresponding to congestion requests; The direction of data flow corresponding to the congestion request; Congestion indication frame or bit.

16. The method as described in claim 10, characterized in that, The congestion-related operations include at least one of the following: Perform congestion-related marking; Send the congestion-related information to the fourth node.

17. A congestion notification method, characterized in that, The method is executed by the third node and includes: A congestion report request message is sent to a first node, wherein the congestion report request message is used to instruct the first node whether to perform congestion monitoring and / or whether to send congestion-related information to a second node, wherein when the congestion report request message instructs the first node to perform congestion monitoring or to send the congestion-related information to the second node, the first node sends the congestion-related information to the second node, and the third node is different from the second node; In the case where the first node is a base station distributed unit (gNB-DU) and the second node is a base station central unit user plane (gNB-CU-UP), the first node sends congestion-related information to the second node through the New Radio (NR) user plane protocol. The congestion-related information is also used by the second node to send it to the core network node. When the first node is a base station and the second node is a user plane node of the core network, the first node sends congestion-related information to the second node through Protocol Data Unit Session User Plane Protocol (PDU) frames.

18. The method as described in claim 17, characterized in that, The congestion report request information includes at least one of the following: Congestion Request Indication (CRI) information; Threshold for congestion request reporting; Bearer information corresponding to congestion requests; The direction of data flow corresponding to the congestion request; Congestion indication frame or bit.

19. The method as described in claim 17, characterized in that, The step of sending a congestion report request to the first node includes: The congestion report request information is sent to the first node using information established through QoS flow, wherein the information established through QoS flow includes the congestion report request information; The congestion report request information is sent to the first node using information modified by the QoS flow, wherein the information modified by the QoS flow includes the congestion report request information.

20. A communication device, configured in a first node, comprising: The sending module is used to send congestion-related information to the second node when congestion occurs. The sending module is specifically used for: The congestion-related information is sent to the second node via the New Radio (NR) user plane protocol. The first node is the base station distributed unit (gNB-DU), and the second node is the base station central unit user plane (gNB-CU-UP). The congestion-related information is also sent by the second node to the core network node. or, The first node is a base station, and the second node is a user plane node of the core network. The congestion-related information is sent to the second node through the Protocol Data Unit Session User Plane Protocol (PDU) frame. The first node is also used for: The first node receives a congestion report request message sent by a third node, wherein the congestion report request message is used to instruct the first node whether to perform congestion detection and / or whether to send the congestion-related information to the second node. When the congestion report request information instructs the first node to perform congestion detection or to send the congestion-related information to the second node, the third node sends the congestion-related information to the second node; the third node is different from the second node.

21. A communication device configured in a second node, comprising: A receiving module is used to receive congestion-related information sent by a first node, wherein the congestion-related information is sent by the first node upon receiving a congestion report request information sent by a third node, and the congestion report request information indicates whether the first node performs congestion detection and / or whether to send the congestion-related information to the second node, wherein the third node is different from the second node; The execution module is used to perform congestion-related operations based on the congestion-related information. The receiving module is specifically used for: The congestion-related information sent by the first node is received through the NR user plane protocol. The first node is gNB-DU and the second node is gNB-CU-UP. The congestion-related information is also used by the second node to send to the core network node. or, The congestion-related information sent by the first node is received through the PDU Session User Plane Protocol frame. The first node is a base station, and the second node is a core network node.

22. A communication device configured in a third node, comprising: A sending module is used to send congestion report request information to a first node, wherein the congestion report request information is used to instruct the first node whether to perform congestion monitoring and / or whether to send congestion-related information to a second node, wherein when the congestion report request information instructs the first node to perform congestion monitoring or to send the congestion-related information to the second node, the first node sends the congestion-related information to the second node, and the third node is different from the second node; In the case where the first node is a base station distributed unit (gNB-DU) and the second node is a base station central unit user plane (gNB-CU-UP), the first node sends congestion-related information to the second node through the New Radio (NR) user plane protocol. The congestion-related information is also used by the second node to send it to the core network node. When the first node is a base station and the second node is a user plane node of the core network, the first node sends congestion-related information to the second node through Protocol Data Unit Session User Plane Protocol (PDU) frames.

23. A communication device, characterized in that, The device includes a processor and a memory, wherein the memory stores a computer program, the processor executes the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 1 to 9, or the processor executes the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 10 to 16, or the processor executes the computer program stored in the memory to cause the device to perform the method as claimed in any one of claims 17 to 19.

24. A communication device, characterized in that, include: Processor and interface circuitry, wherein: The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform the method as claimed in any one of claims 1 to 9, or to execute the code instructions to perform the method as claimed in any one of claims 10 to 16, or to execute the code instructions to perform the method as claimed in any one of claims 17 to 19.

25. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 9 to be implemented, or when executed, cause the method of any one of claims 10 to 16 to be implemented, or when executed, cause the method of any one of claims 17 to 19 to be implemented.

Images