Packet loss processing method and apparatus, and storage medium
The method coordinates packet loss handling among nodes in extended reality systems to optimize resource usage and enhance QoS by aligning packet loss processing, addressing inefficiencies in CU-DU separated architectures.
Patent Information
- Application Number
- PCT/CN2023/142491
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-12-27
- Publication Date
- 2025-07-03
AI Technical Summary
Existing communication systems face challenges in efficiently handling packet loss for extended reality (XR) services, leading to suboptimal resource utilization and reduced quality of service (QoS) due to inefficient packet loss handling across nodes in CU-DU separated architectures.
A method and apparatus for coordinated packet loss handling among nodes, including gNB-CU-UP, gNB-DU, and gNB-CU-CP, where nodes exchange packet loss information to optimize resource usage and improve QoS by aligning packet loss processing based on PDU set quality of service parameters.
Enhances resource utilization and transmission capacity by coordinating packet loss handling across nodes, thereby improving the reliability and quality of service for PDU sets in extended reality applications.
Smart Images

Figure CN2023142491_03072025_PF_FP_ABST
Abstract
Description
Packet loss processing method and device, and storage medium Technical Field
[0001] The present disclosure relates to the field of communications, and in particular to a packet loss processing method and device, and a storage medium. Background Art
[0002] Currently, for extended reality (XR) services, a group of data packets may be used to write the payload of a packet data unit (PDU) set.
[0003] Summary of the Invention
[0004] In order to improve the service quality and reliability of PDU set processing, embodiments of the present disclosure provide a packet loss processing method and apparatus, and a storage medium.
[0005] According to a first aspect of an embodiment of the present disclosure, a packet loss processing method is provided. The method is performed by a first node and includes:
[0006] receiving packet loss information sent by the second node, where the packet loss information is determined by the second node based on packet data unit (PDU) loss status of the second node;
[0007] Based on the packet loss information, PDU packet loss processing is performed.
[0008] According to a second aspect of an embodiment of the present disclosure, a packet loss processing method is provided. The method is performed by a second node and includes:
[0009] Determining packet loss information based on packet data unit (PDU) loss conditions;
[0010] The packet loss information is sent to the first node.
[0011] According to a third aspect of an embodiment of the present disclosure, a packet loss processing method is provided. The method is performed by a third node and includes:
[0012] A first message is sent to a second node, where the first message includes a request message, where the request message is used to request the second node to send packet loss information to the first node, where the packet loss information is determined by the second node based on a packet data unit (PDU) loss situation of the second node.
[0013] According to a fourth aspect of an embodiment of the present disclosure, there is provided a first node, including:
[0014] a transceiver module configured to receive packet loss information sent by the second node, where the packet loss information is determined by the second node based on a packet data unit (PDU) loss condition of the second node;
[0015] The processing module is configured to perform PDU packet loss processing based on the packet loss information.
[0016] According to a fifth aspect of an embodiment of the present disclosure, a second node is provided, including:
[0017] The processing module is configured to determine packet loss information based on packet data unit (PDU) loss conditions;
[0018] The transceiver module is configured to send the packet loss information to the first node.
[0019] According to a sixth aspect of an embodiment of the present disclosure, a third node is provided, including:
[0020] The transceiver module is configured to send a first message to the second node, where the first message includes a request message, where the request message is used to request the second node to send packet loss information to the first node, where the packet loss information is determined by the second node based on the packet data unit (PDU) loss situation of the second node.
[0021] According to a seventh aspect of an embodiment of the present disclosure, there is provided a first node, including:
[0022] one or more processors;
[0023] The processor is configured to execute the packet loss processing method according to any one of the first aspects.
[0024] According to an eighth aspect of an embodiment of the present disclosure, a second node is provided, including:
[0025] one or more processors;
[0026] The processor is used to execute the packet loss processing method described in any one of the second aspects.
[0027] According to a ninth aspect of an embodiment of the present disclosure, a third node is provided, including:
[0028] one or more processors;
[0029] Wherein, the processor is used to execute the packet loss processing method described in the third aspect.
[0030] According to a tenth aspect of an embodiment of the present disclosure, a communication system is provided, comprising a first node, a second node, and a third node, wherein the first node is configured to implement the packet loss processing method described in any one of the first aspect, the second node is configured to implement the packet loss processing method described in any one of the second aspect, and the third node is configured to implement the packet loss processing method described in any one of the third aspect.
[0031] According to an eleventh aspect of an embodiment of the present disclosure, a storage medium is provided, which stores instructions, and when the instructions are executed on a communication device, the communication device executes a packet loss processing method as described in any one of the first aspect, the second aspect or the third aspect.
[0032] In an embodiment of the present disclosure, a first node can perform PDU packet loss processing based on packet loss information sent by a second node, where the packet loss information is determined by the second node based on the PDU packet loss status of the second node. This achieves the purpose of collaborative processing of PDU packet loss among multiple nodes, saves air interface resources and transmission resources, effectively improves resource utilization and transmission capacity, improves the availability of PDU set quality of service (QoS) parameters, and improves the reliability of PDU set processing.
[0033] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0034] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0035] FIG1A is an exemplary schematic diagram of the architecture of an access network device provided according to an embodiment of the present disclosure.
[0036] FIG1B is another exemplary schematic diagram of the architecture of an access network device provided according to an embodiment of the present disclosure.
[0037] FIG2A is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0038] FIG2B is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0039] FIG3A is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0040] FIG3B is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0041] FIG3C is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0042] FIG4A is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0043] FIG4B is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0044] FIG4C is an exemplary interactive diagram of a packet loss processing method provided according to an embodiment of the present disclosure.
[0045] FIG5A is a schematic diagram of an exemplary interaction of a first node provided according to an embodiment of the present disclosure.
[0046] FIG5B is a schematic diagram of an exemplary interaction of a second node provided according to an embodiment of the present disclosure.
[0047] FIG5C is a schematic diagram of an exemplary interaction of a second node provided according to an embodiment of the present disclosure.
[0048] FIG6A is a schematic diagram of an exemplary interaction of a communication device according to an embodiment of the present disclosure.
[0049] FIG6B is an exemplary interaction diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0050] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent like or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present invention, as detailed in the appended claims.
[0051] The embodiments of the present disclosure provide a packet loss processing method, device, and storage medium.
[0052] In a first aspect, an embodiment of the present disclosure provides a packet loss processing method, which is executed by a first node and includes:
[0053] receiving packet loss information sent by the second node, where the packet loss information is determined by the second node based on packet data unit (PDU) loss status of the second node;
[0054] Based on the packet loss information, PDU packet loss processing is performed.
[0055] In the above embodiment, the first node can perform PDU packet loss processing based on the packet loss information sent by the second node. This achieves the purpose of collaborative processing of PDU packet loss among multiple nodes, saves air interface resources and transmission resources, effectively improves resource utilization and transmission capacity, improves the availability of PDU set QoS parameters, and improves the reliability of PDU set processing.
[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the packet loss information includes at least one of the following:
[0057] a packet loss PDU set sequence number PSSN, where the packet loss PSSN is a sequence number of the PDU set discarded by the second node;
[0058] A packet loss PDU sequence number (PSN), where the packet loss PSN is a sequence number of a PDU discarded by the second node;
[0059] a packet loss percentage, where the packet loss percentage is the percentage of the number of PDUs discarded by the second node to the total number of PDUs;
[0060] Cause of packet loss.
[0061] In the above embodiment, the packet loss information may include but is not limited to at least one of the above items. The packet loss situation of the second node can be notified to the first node through the above packet loss information, thereby achieving the purpose of collaborative processing of PDU packet loss among multiple nodes.
[0062] In conjunction with some embodiments of the first aspect, in some embodiments, receiving packet loss information sent by the second node includes:
[0063] A first user plane frame sent by the second node is received, where the first user plane frame includes the packet loss information.
[0064] In the above embodiment, the first node can receive the first user plane frame sent by the second node, thereby obtaining the packet loss information. This is simple to implement and has high availability.
[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the type of the first user plane frame is at least one of the following:
[0066] Downlink user data frame;
[0067] Auxiliary information data frame;
[0068] Downlink PDU set information frame.
[0069] In the above embodiment, the type of the first user plane frame may be at least one of the above items. Existing user plane frames are reused to transmit packet loss information, which has little change to the protocol and high availability.
[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0071] A second user plane frame is sent to the second node, where the second user plane frame includes a request message, where the request message is used to request the second node to send the packet loss information to the first node.
[0072] In the above embodiment, the first node may send a second user plane frame to the second node, including a request message, thereby requesting the second node to send the packet loss information to the first node. The second node may send the packet loss information to the first node based on the request message, thereby saving air interface resources and transmission resources, and effectively improving resource utilization and transmission capacity.
[0073] In combination with some embodiments of the first aspect, in some embodiments, the type of the second user plane frame is at least one of the following:
[0074] Downlink user data frame;
[0075] Auxiliary information data frame;
[0076] Downlink PDU set information frame.
[0077] In the above embodiment, the existing user plane frame can be reused to send the request message, which is simple to implement and has high availability.
[0078] In combination with some embodiments of the first aspect, in some embodiments, the second user plane frame includes a polling bit, and when the bit value of the polling bit is a first value, it is used to request the second node to send the packet loss information to the first node.
[0079] In the above embodiment, a polling bit can be used to request the second node to send the packet loss information to the first node, which saves signaling resources and avoids the problem of the second node frequently sending packet loss information to the first node, resulting in a large amount of air interface resources and transmission resources being occupied.
[0080] In a second aspect, an embodiment of the present disclosure provides a packet loss processing method, which is executed by a second node and includes:
[0081] Determining packet loss information based on packet data unit (PDU) loss conditions;
[0082] The packet loss information is sent to the first node.
[0083] In the above embodiment, the second node can determine packet loss information based on the PDU packet loss situation and send it to the first node, so that the first node can perform PDU packet loss processing based on the packet loss information sent by the second node. This achieves the purpose of collaborative processing of PDU packet loss among multiple nodes, saves air interface resources and transmission resources, effectively improves resource utilization and transmission capacity, improves the availability of PDU set QoS parameters, and improves the reliability of PDU set processing.
[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the packet loss information includes at least one of the following:
[0085] a packet loss PDU set sequence number PSSN, where the packet loss PSSN is a sequence number of the PDU set discarded by the second node;
[0086] A packet loss PDU sequence number (PSN), where the packet loss PSN is a sequence number of a PDU discarded by the second node;
[0087] a packet loss percentage, where the packet loss percentage is the percentage of the number of PDUs discarded by the second node to the total number of PDUs;
[0088] Cause of packet loss.
[0089] In conjunction with some embodiments of the second aspect, in some embodiments, sending the packet loss information to the first node includes:
[0090] Sending a first user plane frame to the first node, where the first user plane frame includes the packet loss information.
[0091] In conjunction with some embodiments of the second aspect, in some embodiments, the type of the first user plane frame is at least one of the following:
[0092] Downlink user data frame;
[0093] Auxiliary information data frame;
[0094] Downlink PDU set information frame.
[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0096] A second user plane frame sent by the first node is received, where the second user plane frame includes a request message, where the request message is used to request the second node to send the packet loss information to the first node.
[0097] In conjunction with some embodiments of the second aspect, in some embodiments, the type of the second user plane frame is at least one of the following:
[0098] Downlink user data frame;
[0099] Auxiliary information data frame;
[0100] Downlink PDU set information frame.
[0101] In combination with some embodiments of the second aspect, in some embodiments, the second user plane frame includes a polling bit, and when the bit value of the polling bit is a first value, it is used to request the second node to send the packet loss information to the first node.
[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0103] A first message sent by a third node is received, where the first message includes a request message, and the request message is used to request the second node to send the packet loss information to the first node.
[0104] In combination with some embodiments of the second aspect, in some embodiments, the first node is a user plane gNB-CU-UP of a centralized unit of a network device, the second node is a distributed unit gNB-DU of the network device, the third node is a control plane gNB-CU-CP of a centralized unit of the network device, and the type of the first message is an F1AP message; or
[0105] The first node is a gNB-DU, the second node is a gNB-CU-UP, the third node is a control plane gNB-CU-CP of a centralized unit of the network device, and the type of the first message is an E1AP message.
[0106] In a third aspect, an embodiment of the present disclosure provides a packet loss processing method, which is executed by a third node and includes:
[0107] A first message is sent to a second node, where the first message includes a request message, where the request message is used to request the second node to send packet loss information to the first node, where the packet loss information is determined by the second node based on a packet data unit (PDU) loss situation of the second node.
[0108] In combination with some embodiments of the third aspect, in some embodiments, the first node is a user plane gNB-CU-UP of a centralized unit of a network device, the second node is a distributed unit gNB-DU of the network device, the third node is a control plane gNB-CU-CP of a centralized unit of the network device, and the type of the first message is an F1AP message; or
[0109] The first node is a gNB-DU, the second node is a gNB-CU-UP, the third node is a control plane gNB-CU-CP of a centralized unit of the network device, and the type of the first message is an E1AP message.
[0110] In a fourth aspect, an embodiment of the present disclosure provides a first node, including:
[0111] a transceiver module configured to receive packet loss information sent by the second node, where the packet loss information is determined by the second node based on a packet data unit (PDU) loss condition of the second node;
[0112] The processing module is configured to perform PDU packet loss processing based on the packet loss information.
[0113] In a fifth aspect, an embodiment of the present disclosure provides a second node, including:
[0114] The processing module is configured to determine packet loss information based on packet data unit (PDU) loss conditions;
[0115] The transceiver module is configured to send the packet loss information to the first node.
[0116] In a sixth aspect, an embodiment of the present disclosure provides a third node, including:
[0117] The transceiver module is configured to send a first message to the second node, where the first message includes a request message, where the request message is used to request the second node to send packet loss information to the first node, where the packet loss information is determined by the second node based on the packet data unit (PDU) loss situation of the second node.
[0118] In a seventh aspect, an embodiment of the present disclosure provides a first node, including:
[0119] one or more processors;
[0120] The processor is configured to execute the packet loss processing method described in any one of the first aspects.
[0121] In an eighth aspect, an embodiment of the present disclosure provides a second node, including:
[0122] one or more processors;
[0123] The processor is used to execute the packet loss processing method described in any one of the second aspects.
[0124] In a ninth aspect, an embodiment of the present disclosure provides a third node, including:
[0125] one or more processors;
[0126] Wherein, the processor is used to execute the packet loss processing method described in the third aspect.
[0127] In the tenth aspect, an embodiment of the present disclosure proposes a communication system, comprising a first node, a second node, and a third node, wherein the first node is configured to implement the packet loss processing method described in any one of the first aspect, the second node is configured to implement the packet loss processing method described in any one of the second aspect, and the third node is configured to implement the packet loss processing method described in any one of the third aspect.
[0128] In the eleventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes a packet loss processing method as described in any one of the first aspect, the second aspect or the third aspect.
[0129] It is understandable that the above nodes, communication systems, storage media, and computer programs are all used to execute the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods and will not be repeated here.
[0130] The present disclosure provides a packet loss handling method, apparatus, and storage medium. In some embodiments, the terms "packet loss handling method" and "information processing method" and "communication method" are interchangeable; the terms "packet loss handling apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.
[0131] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0132] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.
[0133] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.
[0134] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.
[0135] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.
[0136] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.
[0137] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.
[0138] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.
[0139] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0140] In some embodiments, a node can be interpreted as a physical or virtual node, and its name is not limited to the name described in the embodiment. In some cases, it can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "entity", "subject", etc.
[0141] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.
[0142] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.
[0143] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.
[0144] In some embodiments, data, information, etc. may be obtained with the user's consent.
[0145] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.
[0146] FIG1A is a schematic diagram showing an architecture of an access network device according to an embodiment of the present disclosure.
[0147] As shown in FIG1A , the access network device 100 may be composed of a central unit (CU) and a distributed unit (DU), that is, a CU-DU separation architecture is adopted.
[0148] In some embodiments, the access network device 100 may separate the user plane (UP) and the control plane (CP) of the CU.
[0149] In some embodiments, the access network device 100 may include but is not limited to a first node 101 , a second node 102 , and a third node 103 .
[0150] In some embodiments, the first node 101 may be the user plane of a centralized unit (gNB-CU-UP) of a network device.
[0151] The second node 102 may be the control plane of a centralized unit (gNB-CU-CP) of the network device.
[0152] The third node 103 may be a distribution unit gNB-DU of the network device.
[0153] FIG1B is another schematic diagram of the architecture of an access network device according to an embodiment of the present disclosure.
[0154] As shown in FIG1B , the access network device 100 ′ may be composed of a CU and a DU, that is, a CU-DU separation architecture is adopted.
[0155] In some embodiments, the access network device 100 ′ may separate the UP and CP of the CU.
[0156] In some embodiments, the access network device 100 ′ may include but is not limited to a first node 101 ′, a second node 102 ′, and a third node 103 ′.
[0157] In some embodiments, the first node 101' may be a gNB-DU.
[0158] The second node 102′ may be a gNB-CU-CP.
[0159] The third node 103′ may be a gNB-CU-UP.
[0160] In the above embodiment, the gNB-CU-UP and the gNB-CU-CP can communicate through the E1 interface.
[0161] In the above embodiment, the gNB-CU-UP and gNB-DU can communicate through the F1-U interface.
[0162] In the above embodiment, the gNB-CU-CP and gNB-DU can communicate via the F1-C interface.
[0163] In the above embodiment, the gNB-CU-CP may be responsible for the control plane functions of the Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), the gNB-CU-UP is responsible for the user plane functions of the GPRS Tunneling Protocol-User Plane (GTP-U), Service Data Adaptation Protocol (SDAP), and PDCP used in the GPRS network, and the gNB-DU is responsible for the Radio Link Control (RLC), Media Access Control (MAC), and Physical Layer (PHY) functions.
[0164] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.
[0165] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.
[0166] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A or FIG1B , or a portion of the subject, but are not limited thereto. The subjects shown in FIG1A or FIG1B are examples. The communication system may include all or part of the subjects in FIG1A or FIG1B , or may include other subjects other than those in FIG1A or FIG1B . The number and form of the subjects are arbitrary. The subjects may be physical or virtual. The connection relationship between the subjects is an example. The subjects may be connected or disconnected. The connection may be in any manner, directly or indirectly, and wired or wireless.
[0167] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 6th generation mobile communication system (6G), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, systems utilizing other communication methods, and next-generation systems based on these. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be used.
[0168] Currently, at the media layer, the messages in a PDU set are decoded / processed as a whole. For example, a frame can only be decoded if all packets carrying the frame or a certain number of packets are successfully sent.
[0169] For example, a frame in a Group of Pictures (GOP) can only be decoded by the client if all frames associated with it are successfully received. Therefore, the packets in a PDU set are inherently correlated at the media layer. If the correlation between messages in a PDU set is not considered, the 5G system may perform inefficient scheduling. For example, the 5G system may randomly discard messages but try to send other messages in the same PDU set, which are useless to the client, thereby wasting radio resources.
[0170] In some embodiments, PDU Set integrated packet processing defines the following PDU Set QoS parameters to support PDU Set processing:
[0171] 1. PDU Set Error Rate (PSER)
[0172] PSER defines an upper limit on the ratio of the number of PDU sets that were not successfully received within a measurement window to the total number of PDU sets sent to the receiver. It can be understood as defining an upper limit on the proportion of PDU sets processed by the sender of RLC that have not been successfully passed to the upper layer (such as PDCP) by the corresponding receiver. Therefore, PSER defines an upper limit for non-congestion related packet loss rate. The purpose of PSER is to allow appropriate link layer protocol configuration (such as RLC and HARQ). For each 5G QoS identifier (5QI), the value of PSER is the same in the uplink and downlink. If any PDU in the PDU Set is not successfully transmitted, the PDU Set is considered to be erroneous.
[0173] 2. PDU Set Delay Budget (PSDB).
[0174] The PSDB defines the upper bound on the transmission delay of a PDU set between the terminal and the N6 termination point on the User Port Function (UPF). This is the time from receipt of the first PDU to the successful delivery of the last arriving PDU. The PSDB applies to downlink PDU sets received by the UPF over the N6 interface and to uplink PDU sets sent by the terminal. For a given 5QI, the PSDB value is the same for both the uplink and downlink.
[0175] 3. PDU Set Integrated Handling Information (PSIHI)
[0176] The PSIHI indicates to the application layer whether all PDUs in the PDU set are required to use the PDU set.
[0177] To support PDU set-based QoS processing, the PDU Session Anchor-User Port Function (PSA-UPF) identifies the PDUs that belong to a PDU set and determines the following PDU set information that it sends in the GTP-U header to the Next Generation Radio Access Network (NG-RAN). As described above, the PDU set information is used by the NG-RAN for PDU set-based QoS processing.
[0178] The PDU set information may include but is not limited to at least one of the following:
[0179] -PDU Set Sequence Number (PSSN).
[0180] -Indication of End PDU of the PDU Set.
[0181] -PDU Sequence Number within a PDU Set (PSN).
[0182] -PDU Set Size in bytes.
[0183] -PDU Set Importance (PSI), which identifies the relative importance of a PDU set compared to other PDU sets in the QoS flow.
[0184] In some embodiments, at least one of the following packet loss handling methods may be considered:
[0185] The first is the packet loss processing method based on PSIHI.
[0186] When PSIHI is set for a QoS flow, as long as it is known that one PDU in a PDU set is lost, the remaining PDUs in the PDU set can be considered no longer needed by the application and can be discarded at the sending end to release radio resources.
[0187] The second method is to handle packet loss based on PSI.
[0188] In case of network congestion, the gNB can use the PSI to discard PDU sets. For the uplink, dedicated downlink signaling is used to request the terminal to use a shorter discard timer for PDUs of lower importance in PDCP.
[0189] In some embodiments, in a CU-DU split architecture, the gNB-CU-CP sends PDU set QoS parameters to the gNB-CU-UP and gNB-DU. The gNB-CU-UP and gNB-DU process uplink and downlink data for XR services based on the PDU set QoS parameters. However, coordinated packet loss handling between nodes is not possible. In embodiments of the present disclosure, a packet loss handling method, apparatus, and storage medium are provided that can implement coordinated packet loss handling between nodes based on the PSIHI packet loss handling method, or based on both the PSIHI and PSI packet loss handling methods.
[0190] Figure 2A is a schematic diagram illustrating an interaction of a packet loss handling method according to an embodiment of the present disclosure. As shown in Figure 2A , the present embodiment relates to a packet loss handling method, wherein the first node is a gNB-CU-UP, the second node is a gNB-DU, and the third node is a gNB-CU-CP. The method includes:
[0191] In step S2101, the first node gNB-CU-UP sends a request message to the second node gNB-DU.
[0192] In some embodiments, the request message is used to request the second node gNB-DU to send packet loss information to the first node gNB-CU-UP.
[0193] In some embodiments, the second node gNB-DU receives the request message.
[0194] In some embodiments, the packet loss information is determined by the second node gNB-DU based on the PDU loss situation of the second node gNB-DU.
[0195] In some embodiments, the packet loss information includes but is not limited to at least one of the following:
[0196] Packet loss PDU set sequence number PSSN;
[0197] Packet loss PDU sequence number PSN;
[0198] Packet loss percentage;
[0199] Cause of packet loss.
[0200] Exemplarily, the packet loss PSSN is the sequence number of the PDU set discarded by the gNB-DU.
[0201] Exemplarily, the packet loss PSN is the PDU sequence number discarded by the gNB-DU.
[0202] Exemplarily, the packet loss percentage is the percentage of PDUs discarded by the gNB-DU to the total number of PDUs.
[0203] Exemplarily, the reasons for packet loss include but are not limited to at least one of the following: congestion; wireless link failure, etc.
[0204] In some embodiments, the first node gNB-CU-UP sends a second plane frame to the second node gNB-DU, including the request message.
[0205] In an example, the type of the second plane frame may be limited to at least one of the following:
[0206] Downlink user data (DL USER DATA) frame;
[0207] ASSISTANCE INFORMATION DATA frame;
[0208] Downlink PDU set information (DL PDU SET INFORMATION) frame.
[0209] In one example, the second user plane frame may include a polling bit. When the polling bit has a first value, the polling bit is used to request the second node gNB-DU to send the packet loss information to the first node gNB-CU-UP. The first value may be 1 or 0, which is not limited in this disclosure.
[0210] Exemplarily, when the polling bit has a second value, it indicates to the first node gNB-CU-UP that it no longer requests the packet loss information. The second value is different from the first value. For example, if the first value is 1, the second value is 0, or vice versa.
[0211] Alternatively, when the first node no longer requests to obtain the packet loss information, the second node may stop sending the packet loss information to the first node by no longer sending the request message.
[0212] It is understandable that the request message may be sent in the second user plane frame in other ways, for example, the request message may be sent to the second node in a display indication manner.
[0213] The above description is for illustrative purposes only. Any scheme in which the gNB-DU sends other messages or plane frames to send the request message to the gNB-CU-UP shall fall within the scope of protection of this disclosure.
[0214] In step S2102, the third node gNB-CU-CP sends a request message to the second node gNB-DU.
[0215] In some embodiments, the request message is used to request the second node gNB-DU to send packet loss information to the first node gNB-CU-UP.
[0216] In some embodiments, the second node gNB-DU receives the request message.
[0217] In some embodiments, the packet loss information is determined by the second node gNB-DU based on the PDU loss situation of the second node gNB-DU.
[0218] In some embodiments, the packet loss information includes but is not limited to at least one of the following: packet loss PDU set sequence number PSSN; packet loss PDU sequence number PSN; packet loss percentage; packet loss reason. The specific information content has been introduced in step S2101 and will not be repeated here.
[0219] In some embodiments, the third node gNB-CU-CP sends a first message to the second node gNB-DU, including the request message.
[0220] Exemplarily, the type of the first message may be an F1 Application Protocol (F1AP) message.
[0221] In step S2103, the second node gNB-DU determines packet loss information.
[0222] In some embodiments, the second node gNB-DU determines packet loss information based on its own PDU packet loss situation.
[0223] Exemplarily, the second node gNB-DU determines the packet loss PSSN based on the discarded PSSN.
[0224] Exemplarily, the second node gNB-DU determines the packet loss PSN based on the discarded PSN.
[0225] Exemplarily, the second node gNB-DU determines the packet loss percentage based on the percentage of the number of discarded PDUs to the total number of PDUs.
[0226] Exemplarily, the second node gNB-DU performs radio link detection to determine the cause of packet loss.
[0227] In step S2104, the second node gNB-DU sends packet loss information to the first node gNB-CU-UP.
[0228] In some embodiments, the second node gNB-DU determines the packet loss information based on its own PDU packet loss situation and sends it to the first node gNB-CU-UP.
[0229] In some embodiments, the first node gNB-CU-UP receives the packet loss information.
[0230] In some embodiments, the second node gNB-DU sends a first user plane frame to the first node gNB-CU-UP, including the packet loss information.
[0231] Exemplarily, the type of the first user plane frame may not be limited to at least one of the following:
[0232] Downlink user data frame;
[0233] Auxiliary information data frame;
[0234] Downlink PDU set information frame.
[0235] In step S2105, the first node gNB-CU-UP performs PDU packet loss processing based on the packet loss information.
[0236] In some embodiments, the first node gNB-CU-UP performs PDU packet loss processing based on the packet loss information and in accordance with the PSIHI combined with its own decision.
[0237] Alternatively, the first node gNB-CU-UP performs PDU packet loss processing based on the packet loss information, according to the PSIHI and PSI, and in combination with its own decision.
[0238] In one example, the packet loss information includes the packet loss PSSN. The first node gNB-CU-UP can determine the PSSN discarded by the second node gNB-DU based on the packet loss PSSN. Further, the first node gNB-CU-UP can discard other PDU sets associated with the PDU set indicated by the packet loss PSSN.
[0239] For example, assuming the packet loss PSSN is 1, where PSSN#1, PSSN#2, and PSSN#3 are used to transmit all frames in a GOP, PSSN#1 is associated with PSSN#2 and PSSN#3. The first node gNB-CU-UP determines based on the packet loss PSSN that the second node gNB-DU discarded the PDU set of PSSN#1. In this case, the first node gNB-CU-UP may discard the PDU set of PSSN#2 and PSSN#3.
[0240] In one example, the packet loss information includes a packet loss PSN, and the first node gNB-CU-UP may discard other PDUs that belong to the same PDU set as the PDU corresponding to the packet loss PSN.
[0241] For example, assuming that the lost packet PSNs are 2 and 3, where PSN#1, PSN#2, and PSN#3 belong to PDU set #1, the first node gNB-CU-UP can discard the PDU of PSN#1 in lost PDU set #1 based on PSIHI.
[0242] In one example, the packet loss information includes a packet loss percentage, and the first node gNB-CU-UP may determine whether to discard a PDU or a PDU set based on the PSIHI.
[0243] Assuming that the packet loss percentage exceeds a preset threshold, the first node gNB-CU-UP may discard multiple PDU sets based on the PSIHI.
[0244] Alternatively, assuming that the packet loss percentage exceeds a preset threshold, the first node gNB-CU-UP may discard at least some PDUs in a PDU set with a lower PSI level based on the PSIHI.
[0245] In one example, the packet loss information includes a packet loss cause, and the first node gNB-CU-UP may determine whether to discard a PDU or a PDU set based on the PSIHI.
[0246] Exemplarily, the cause of packet loss includes congestion. The first node gNB-CU-UP may consider that the network is in a congested state at this time and may discard multiple PDU sets, or discard at least some PDUs in a PDU set with a lower PSI level.
[0247] Exemplarily, the packet loss cause includes radio link failure, and the first node gNB-CU-UP may not discard the PDU set, or may not discard the PDUs in the PDU set, or may discard at least some PDUs in the PDU set with a lower PSI level.
[0248] The above description is merely an example. Any scheme in which the first node gNB-CU-UP performs packet loss processing based on packet loss information should fall within the scope of protection of this disclosure.
[0249] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0250] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.
[0251] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.
[0252] In some embodiments, terms such as "certain", "preseted", "preset", "setting", "indicated", "a certain", "any", "first", and "designated" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.
[0253] In some embodiments, the packet loss processing method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2105. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, step S2101+step S2103+step S2104 can be implemented as an independent embodiment, step S2102+step S2103+step S2104 can be implemented as an independent embodiment, step S2105 can be implemented as an independent embodiment, and steps S2101 to S2105 can be implemented as independent embodiments, but are not limited thereto.
[0254] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives a request message from another execution entity, such as a third node, or if the second node directly sends packet loss information to the first node, step S2101 may not be performed.
[0255] In some embodiments, step S2102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives another execution subject, such as a request message sent by the first node, or if the second node directly sends packet loss information to the first node, step S2102 may not be executed.
[0256] In some embodiments, either step S2101 or step S2102 may be performed alternatively. In some embodiments, step S2103 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if other nodes determine packet loss information, step S2103 may not be performed.
[0257] In some embodiments, step S2104 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node gNB-DU performs packet loss handling, step S2104 may not be performed.
[0258] In some embodiments, step S2105 is optional. One or more of these steps may be omitted or replaced in different embodiments. For example, if the first node gNB-CU-UP performs PDU packet loss handling only based on the PSI or the second node performs PDU packet loss handling, step S2105 may not be performed.
[0259] In some embodiments, steps S2101 to S2105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0260] In the above embodiment, the gNB-CU-UP can perform PDU loss handling based on packet loss information sent by the gNB-DU. The packet loss information is determined by the gNB-DU based on the PDU loss status of the gNB-DU. This enables coordinated PDU loss handling among multiple nodes, conserving air interface and transmission resources, effectively improving resource utilization and transmission capacity, enhancing the availability of PDU set QoS parameters, and improving the reliability of PDU set processing.
[0261] Figure 2B is a schematic diagram illustrating an interaction of a packet loss handling method according to an embodiment of the present disclosure. As shown in Figure 2B , the present embodiment relates to a packet loss handling method, wherein the first node is a gNB-DU, the second node is a gNB-CU-UP, and the third node is a gNB-CU-CP. The method includes:
[0262] In step S2201, the first node gNB-DU sends a request message to the second node gNB-CU-UP.
[0263] In some embodiments, the request message is used to request the second node gNB-CU-UP to send packet loss information to the first node gNB-DU.
[0264] In some embodiments, the second node gNB-CU-UP receives the request message.
[0265] In some embodiments, the packet loss information is determined by the second node gNB-CU-UP based on the PDU packet loss situation of the second node gNB-CU-UP.
[0266] In some embodiments, the packet loss information includes but is not limited to at least one of the following: packet loss PSSN; packet loss PSN; packet loss percentage; and packet loss reason.
[0267] In some embodiments, the first node gNB-DU sends a second plane frame to the second node gNB-CU-UP, including the request message.
[0268] In an example, the type of the second plane frame may be, but is not limited to, at least one of the following:
[0269] Downlink user data (DL USER DATA) frame;
[0270] ASSISTANCE INFORMATION DATA frame;
[0271] Downlink PDU set information (DL PDU SET INFORMATION) frame.
[0272] In one example, the second user plane frame may include a polling bit. When the polling bit has a first value, the polling bit is used to request the second node gNB-CU-UP to send the packet loss information to the first node gNB-DU. The first value may be 1 or 0, which is not limited in this disclosure.
[0273] Exemplarily, when the polling bit has a second value, it indicates to the first node gNB-DU that it no longer requests the packet loss information. The second value is different from the first value, for example, if the first value is 1, the second value is 0, or the first value is 0 and the second value is 1.
[0274] Alternatively, when the first node no longer requests to obtain the packet loss information, the second node may stop sending the packet loss information to the first node by no longer sending the request message.
[0275] The above description is for illustrative purposes only. Any scheme in which the gNB-CU-UP sends other messages or plane frames to send the request message to the gNB-DU shall fall within the scope of protection of this disclosure.
[0276] In step S2202, the third node gNB-CU-CP sends a request message to the second node gNB-CU-UP.
[0277] In some embodiments, the request message is used to request the second node gNB-CU-UP to send packet loss information to the first node gNB-DU.
[0278] In some embodiments, the second node gNB-CU-UP receives the request message.
[0279] In some embodiments, the packet loss information is determined by the second node gNB-CU-UP based on the PDU packet loss situation of the second node gNB-DU.
[0280] In some embodiments, the packet loss information includes but is not limited to at least one of the following: packet loss PSSN; packet loss PSN; packet loss percentage; and packet loss reason. The specific information content has been introduced in the previous embodiment and will not be repeated here.
[0281] In some embodiments, the third node gNB-CU-CP sends a first message to the second node gNB-CU-UP, including the request message.
[0282] Exemplarily, the type of the first message may be an E1 Application Protocol (E1AP) message.
[0283] In step S2203, the second node gNB-CU-UP determines packet loss information.
[0284] In some embodiments, the second node gNB-CU-UP determines the packet loss information in a manner similar to step S2103 above and is not repeated here.
[0285] In step S2204, the second node gNB-CU-UP sends packet loss information to the first node gNB-DU.
[0286] In some embodiments, the second node gNB-CU-UP determines the packet loss information based on its own PDU packet loss situation and sends it to the first node gNB-DU.
[0287] In some embodiments, the first node gNB-DU receives the packet loss information.
[0288] In some embodiments, the second node gNB-CU-UP sends a first user plane frame to the first node gNB-DU, including the packet loss information.
[0289] Exemplarily, the type of the first user plane frame may not be limited to at least one of the following:
[0290] Downlink user data frame;
[0291] Auxiliary information data frame;
[0292] Downlink PDU set information frame.
[0293] In step S2205, the first node gNB-DU performs PDU packet loss processing based on the packet loss information.
[0294] In some embodiments, the first node gNB-DU performs PDU packet loss processing based on the packet loss information, according to the PSIHI or the PSIHI and PSI, and in combination with its own decision.
[0295] In one example, the packet loss information includes the packet loss PSSN. The first node gNB-DU can determine the PSSN discarded by the second node gNB-CU-UP based on the packet loss PSSN. Further, the first node gNB-DU can discard other PDU sets associated with the PDU set indicated by the packet loss PSSN.
[0296] For example, assuming the packet loss PSSN is 1, where PSSN#1, PSSN#2, and PSSN#3 are used to transmit all frames in a GOP, PSSN#1 is associated with PSSN#2 and PSSN#3. The first node gNB-DU determines based on the packet loss PSSN that the second node gNB-CU-UP discarded the PDU set of PSSN#1. In this case, the first node gNB-DU can discard the PDU sets of PSSN#2 and PSSN#3.
[0297] In one example, the packet loss information includes a packet loss PSN, and the first node gNB-DU may discard other PDUs that belong to the same PDU set as the PDU corresponding to the packet loss PSN.
[0298] In one example, the packet loss information includes a packet loss percentage, and the first node gNB-DU can determine whether to discard the PDU or PDU set based on the PSIHI.
[0299] Assuming that the packet loss percentage exceeds a preset threshold, the first node gNB-DU may discard multiple PDU sets based on the PSIHI.
[0300] Alternatively, assuming that the packet loss percentage exceeds a preset threshold, the first node gNB-CU-UP may discard at least some PDUs in a PDU set with a lower PSI level based on the PSIHI.
[0301] In one example, the packet loss information includes a packet loss reason, and the first node gNB-DU may determine whether to discard a PDU or a PDU set based on the PSIHI.
[0302] Exemplarily, the cause of packet loss includes congestion. The first node gNB-DU may consider that the network is in a congested state at this time and may discard multiple PDU sets, or discard at least some PDUs in a PDU set with a lower PSI level.
[0303] Exemplarily, the packet loss cause includes radio link failure, and the first node gNB-DU may not discard the PDU set, or may not discard the PDUs in the PDU set, or may discard at least some of the PDUs in the PDU set with a lower PSI level.
[0304] The above description is merely an example. Any scheme in which the first node gNB-DU performs packet loss processing based on packet loss information should fall within the scope of protection of this disclosure.
[0305] In some embodiments, the packet loss processing method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2205. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, step S2203 can be implemented as an independent embodiment, step S2204 can be implemented as an independent embodiment, step S2201+step S2203+step S2204 can be implemented as an independent embodiment, step S2202+step S2203+step S2204 can be implemented as an independent embodiment, step S2205 can be implemented as an independent embodiment, and steps S2201 to S2205 can be implemented as independent embodiments, but are not limited thereto.
[0306] In some embodiments, step S2201 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives another execution entity, such as a request message sent by the first node, or if the second node directly sends packet loss information to the first node, step S2201 may not be executed.
[0307] In some embodiments, step S2202 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives a request message from another execution entity, such as a third node, or if the second node directly sends packet loss information to the first node, step S2202 may not be performed.
[0308] In some embodiments, step S2201 and step S2202 can be performed alternatively.
[0309] In some embodiments, step S2203 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when other nodes determine packet loss information, step S2203 may not be performed.
[0310] In some embodiments, step S2204 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first node gNB-DU provides the second node gNB-CU-UP with packet loss information of the first node, step S2204 may not be performed.
[0311] In some embodiments, step S2205 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the first node gNB-DU performs PDU packet loss processing based only on the PSI, step S2205 may not be performed.
[0312] In some embodiments, steps S2201 to S2205 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0313] In the above embodiment, the gNB-DU can perform PDU loss handling based on packet loss information sent by the gNB-CU-UP. The packet loss information is determined by the gNB-CU-UP based on the PDU loss status of the gNB-CU-UP. This achieves the goal of coordinated PDU loss handling among multiple nodes, conserving air interface and transmission resources, effectively improving resource utilization and transmission capacity, enhancing the availability of PDU set QoS parameters, and improving the reliability of PDU set processing.
[0314] Figure 3A is a schematic diagram illustrating an interaction of a packet loss handling method according to an embodiment of the present disclosure. As shown in Figure 3A , the present embodiment relates to a packet loss handling method, which may be performed by a first node, which may be a gNB-CU-UP or a gNB-DU. The method includes:
[0315] Step S3101, send a request message.
[0316] In some embodiments, the first node may send a request message to the second node.
[0317] In some embodiments, the request message may be used to request the second node to send packet loss information to the first node.
[0318] In some embodiments, the second node receives the request message.
[0319] In some embodiments, when the first node is a gNB-CU-UP and the second node is a gNB-DU, the optional implementation method of step S3101 can refer to the optional implementation method of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, and will not be repeated here.
[0320] In some embodiments, when the first node is a gNB-DU and the second node is a gNB-CU-UP, the optional implementation of step S3101 can refer to the optional implementation of step S2201 in Figure 2B and other related parts of the embodiment involved in Figure 2B, and will not be repeated here.
[0321] Step S3102: Obtain packet loss information.
[0322] In some embodiments, the packet loss information is determined by the second node based on a PDU loss condition of the second node.
[0323] In some embodiments, the first node may obtain the packet loss information from the second node, but is not limited thereto. The first node may also receive packet loss information sent by other entities.
[0324] In some embodiments, the first node obtains packet loss information determined according to a predefined rule.
[0325] In some embodiments, the first node performs processing to obtain the packet loss information.
[0326] In some embodiments, step S3102 is omitted, the first node autonomously implements the function indicated by the packet loss information, or the first node obtains the packet loss information based on predefined rules or protocol agreements, or the above functions are default or default.
[0327] In some embodiments, when the first node is a gNB-CU-UP and the second node is a gNB-DU, the optional implementation method of step S3102 can refer to the optional implementation method of step S2104 in Figure 2A and other related parts of the embodiments involved in Figure 2A, and will not be repeated here.
[0328] In some embodiments, when the first node is a gNB-DU and the second node is a gNB-CU-UP, the optional implementation of step S3102 can refer to the optional implementation of step S2204 in Figure 2B and other related parts of the embodiment involved in Figure 2B, and will not be repeated here.
[0329] Step S3103: perform PDU packet loss processing.
[0330] In some embodiments, when the first node is a gNB-CU-UP, the optional implementation of step S3103 can refer to the optional implementation of step S2105 in Figure 2A and other related parts of the embodiment involved in Figure 2A, and will not be repeated here.
[0331] In some embodiments, when the first node is a gNB-DU, the optional implementation method of step S3103 can refer to the optional implementation method of step S2205 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.
[0332] In some embodiments, the packet loss processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3103. For example, step S3101 can be implemented as an independent embodiment, step S3102 can be implemented as an independent embodiment, step S3103 can be implemented as an independent embodiment, step S3101 + step S3103 can be implemented as an independent embodiment, and step S3102 + step S3103 can be implemented as independent embodiments, but the present invention is not limited thereto.
[0333] In some embodiments, step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives a request message from another execution entity, such as a third node, or if the second node directly sends packet loss information to the first node, step S3101 may not be performed.
[0334] In some embodiments, step S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node does not need to perform collaborative packet loss processing with the second node, step S3102 may not be performed.
[0335] In some embodiments, step S3103 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node performs PDU packet loss processing only based on the PSI or the second node performs PDU packet loss processing, step S3103 may not be performed.
[0336] In some embodiments, steps S3101 to S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0337] In the above embodiment, the first node can perform PDU packet loss processing based on packet loss information sent by the second node, where the packet loss information is determined by the second node based on the PDU packet loss situation of the second node. This achieves the purpose of collaborative processing of PDU packet loss among multiple nodes, saves air interface resources and transmission resources, effectively improves resource utilization and transmission capacity, improves the availability of PDU set QoS parameters, and improves the reliability of PDU set processing.
[0338] Figure 3B is an interactive diagram illustrating a packet loss handling method according to an embodiment of the present disclosure. As shown in Figure 3B , this embodiment of the present disclosure relates to a packet loss handling method, which can be performed by a second node. The first node can be a gNB-DU or gNB-CU-UP. The method includes:
[0339] Step S3201, obtain the request message.
[0340] In some embodiments, the request message may be used to request the second node to send packet loss information to the first node.
[0341] In some embodiments, the second node may obtain the request message from the first node or the third node, but is not limited thereto. The second node may also receive a request message sent by other entities.
[0342] In some embodiments, the second node obtains a request message determined according to a predefined rule.
[0343] In some embodiments, the second node performs processing to obtain the request message.
[0344] In some embodiments, step S3201 is omitted, the second node autonomously implements the function indicated by the request message, or the second node obtains the request message based on predefined rules or protocol agreements, or the above functions are default or default.
[0345] In some embodiments, when the second node is a gNB-DU and the first node is a gNB-CU-UP, the optional implementation of step S3201 can refer to the optional implementation of step S2101 in Figure 2A and other related parts of the embodiment involved in Figure 2A, and will not be repeated here.
[0346] In some embodiments, when the second node is a gNB-DU and the third node is a gNB-CU-CP,
[0347] The optional implementation of step S3201 can refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.
[0348] In some embodiments, when the second node is a gNB-CU-UP and the first node is a gNB-DU, the optional implementation of step S3101 can refer to the optional implementation of step S2201 in Figure 2B and other related parts in the embodiments involved in Figure 2B, and will not be repeated here.
[0349] In some embodiments, when the second node is a gNB-CU-UP and the third node is a gNB-CU-CP, the optional implementation of step S3101 can refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, and will not be repeated here.
[0350] Step S3202: Determine packet loss information.
[0351] In some embodiments, the optional implementation method of step S3202 can refer to the optional implementation method of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, or the optional implementation method of step S3202 can refer to the optional implementation method of step S2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.
[0352] Step S3203: Send packet loss information.
[0353] In some embodiments, the packet loss information is determined by the second node based on a PDU loss condition of the second node.
[0354] In some embodiments, the second node may send the packet loss information to the first node.
[0355] In some embodiments, the first node receives the packet loss information.
[0356] In some embodiments, when the second node is a gNB-DU and the first node is a gNB-CU-UP, the optional implementation of step S3203 can refer to the optional implementation of step S2104 in Figure 2A and other related parts in the embodiment involved in Figure 2A, and will not be repeated here.
[0357] In some embodiments, when the second node is a gNB-CU-UP and the first node is a gNB-DU, the optional implementation method of step S3203 can refer to the optional implementation method of step S2204 in Figure 2B and other related parts in the embodiments involved in Figure 2B, and will not be repeated here.
[0358] In some embodiments, the packet loss processing method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, step S3203 can be implemented as an independent embodiment, step S3202 + step S3203 can be implemented as an independent embodiment, and steps S3201 to S3203 can be implemented as independent embodiments, but are not limited thereto.
[0359] In some embodiments, step S3201 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the second node directly sends packet loss information to the first node, step S3201 may not be performed.
[0360] In some embodiments, step S3202 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when other nodes determine packet loss information, step S3202 may not be performed.
[0361] In some embodiments, step S3203 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, when the first node and the second node do not need to perform coordinated packet loss processing, step S3203 may not be performed.
[0362] In some embodiments, steps S3201 to S3203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.
[0363] In the above embodiment, the second node can determine the packet loss information and send it to the first node, thereby achieving the purpose of collaborative processing of PDU packet loss among multiple nodes, saving air interface resources and transmission resources, effectively improving resource utilization and transmission capacity, improving the availability of PDU set QoS parameters, and improving the reliability of PDU set processing.
[0364] FIG3C is an interactive diagram illustrating a packet loss handling method according to an embodiment of the present disclosure. As shown in FIG3C , the present embodiment relates to a packet loss handling method, which may be executed by a third node, which may be a gNB-CU-CP. The method includes:
[0365] Step S3301, send a request message.
[0366] In some embodiments, the request message may be used to request the second node to send packet loss information to the first node.
[0367] In some embodiments, the third node may send the request message to the second node.
[0368] In some embodiments, the second node may receive the request message.
[0369] In some embodiments, when the second node may be a gNB-DU and the first node may be a gNB-CU-UP, the optional implementation of step S3301 may refer to the optional implementation of step S2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, and will not be repeated here.
[0370] In some embodiments, when the second node may be a gNB-CU-UP and the first node may be a gNB-DU, the optional implementation of step S3301 may refer to the optional implementation of step S2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, and will not be repeated here.
[0371] In some embodiments, step S3301 is optional, and one or more of these steps may be omitted or replaced in different embodiments. For example, if the second node receives a request message from the first node, or if the second node directly sends packet loss information, step S3301 may not be performed.
[0372] In the above embodiment, the third node can send a request message to the second node, which can be used to request the second node to send packet loss information to the first node. This achieves the purpose of collaborative processing of PDU packet loss among multiple nodes, saves air interface resources and transmission resources, effectively improves resource utilization and transmission capacity, improves the availability of PDU set QoS parameters, and improves the reliability of PDU set processing.
[0373] The above process is further illustrated by the following examples:
[0374] In the disclosed embodiments, the first node is a gNB-CU-UP, the second node is a gNB-DU, and the third node is a gNB-CU-CP. Alternatively, the first node is a gNB-DU, the second node is a gNB-CU-UP, and the third node is a gNB-CU-CP.
[0375] First, the first node executes:
[0376] Packet loss information is received from the second node, wherein the packet loss information is determined by the second node according to a packet loss situation of the second node.
[0377] Based on the above, the packet loss information includes at least one of the following information:
[0378] -Discard PSSN, used to indicate the PSSN where the discarded PDU is located;
[0379] -Discard PSN, used to indicate the PSN corresponding to the discarded PDU;
[0380] -Packet loss percentage (discard percentage), used to indicate the percentage of discarded PDUs in the PSSN to the total number of PDUs;
[0381] -Discard cause, used to indicate the cause of packet loss, such as congestion or wireless link failure.
[0382] Based on the above, the packet loss information is included in the user plane frame sent by the second node to the first node.
[0383] In some embodiments, packet loss information is included in a DL USER DATA frame, an ASSISTANCE INFORMATION DATA frame, and / or a DL PDU SET INFORMATION frame.
[0384] Based on the above, the first node receives the packet loss information from the second node, including: the second node receives a packet loss request message from the first node or the third node, and the second node sends the packet loss information to the first node according to the packet loss request message.
[0385] Based on the above, the second node receives a packet loss request message from the third node through signaling.
[0386] In some embodiments, the second node is a gNB-DU, the third node is a gNB-CU-CP, and the packet loss request message is included in an F1AP message.
[0387] In some embodiments, the second node is a gNB-CU-UP, the third node is a gNB-CU-CP, and the packet loss request message is included in an E1AP message.
[0388] Based on the above, the second node receives the packet loss request message from the first node via a user plane frame.
[0389] In some embodiments, the packet loss request message is a polling bit, a value of 1 represents requesting packet loss information, and a value of 0 represents not requesting packet loss information.
[0390] In some embodiments, the packet loss request message is included in a DL USER DATA frame, an ASSISTANCE INFORMATION DATA frame, and / or a DL PDU SET INFORMATION frame.
[0391] Embodiment 1: The downlink (DL) PDU set information frame includes packet loss information.
[0392] The transmission of PDU set information includes:
[0393] Downlink PDU Set Information Frame, which may include all PDUs belonging to the DL discarded PDU set sequence number that can be discarded by the gNB-DU.
[0394] As shown in FIG4A , the first node is a gNB-CU node. Specifically, the first node may be a gNB-CU-UP, and the second node may be a gNB-DU. The method includes:
[0395] In step S4101, the first node gNB-CU-UP sends a downlink PDU set information frame to the second node gNB-DU, including packet loss information.
[0396] In an example, the structure of the downlink PDU set information frame including packet loss information is shown in Table 1.
[0397] Table 1
[0398] The following two parameters can be added to Table 1:
[0399] 1. Downlink PSSN clear (DL PSSN Flush).
[0400] Description: This parameter indicates the presence of DL Discard PSSN.
[0401] Value range: {0=DL Discard PSSN does not exist, 1=DL Discard-PSN exists}.
[0402] Field length: 1 bit.
[0403] 2. Downlink packet loss PSSN (DL Discard PSSN).
[0404] Description: This parameter indicates the downlink DL Discard PSSN that can be discarded.
[0405] Value range: {0..2 16 -1}.
[0406] Field length: 2 octets.
[0407] Embodiment 2: The auxiliary information data frame includes packet loss information.
[0408] As shown in Figure 4B, the second node can be a gNB-DU and the first node can be a gNB-CU-UP, or the second node can be a gNB-CU-UP and the first node can be a gNB-DU.
[0409] In FIG4B , in step S4201, a second node serving as a corresponding node may send an auxiliary information data frame including packet loss information to a first node serving as a node hosting NR PDCP.
[0410] In some embodiments, the Assistance Information Data frame may include uplink packet loss information and / or downlink packet loss information implemented by the corresponding node. If supported, the node carrying NR PDCP should consider this information to perform PDU set-based packet loss operations in the NG-RAN node. For example, the node carrying NR PDCP may also discard the remaining PDUs in the PDU set indicated in the DL discard information.
[0411] The structure of the auxiliary information data frame including packet loss information may be as shown in Table 2, for example.
[0412] Table 2
[0413] The following parameters are added to Table 2:
[0414] 1. Uplink packet loss information indicator.
[0415] Description: This parameter indicates the presence of uplink (UL) packet loss information.
[0416] Value range: {0=UL packet loss information does not exist, 1=UL packet loss information exists}.
[0417] Field length: 1 bit.
[0418] 2. DL packet loss information indicator.
[0419] Description: This parameter indicates the presence of DL packet loss information.
[0420] Value range: {0=no DL packet loss information, 1=presence of DL packet loss information}.
[0421] Field length: 1 bit.
[0422] 3. UL packet loss information.
[0423] Description: This field indicates the UL PDU Set Sequence Number (PSSN), where at least one PDU is discarded by the corresponding node (second node).
[0424] Value range: {0..2 16 -1}.
[0425] Field length: 2 octets.
[0426] 4. DL packet loss information.
[0427] Description: This field indicates the DL PDU Set Sequence Number (PSSN), where at least one PDU is discarded by the corresponding node (second node).
[0428] Value range: {0..2 16 -1}.
[0429] Field length: 2 octets.
[0430] Embodiment 3: The downlink PDU set information frame includes a request message.
[0431] The transmission of PDU set information includes:
[0432] The downlink PDU aggregate information frame may include a packet loss information polling bit to request the second node to report the packet loss information of the PDU aggregate.
[0433] As shown in FIG4C , the first node is a gNB-CU node, and the second node is a gNB-DU. The method includes:
[0434] Step S4301: The first node sends a request message to the second node, requesting the second node to report packet loss information.
[0435] In an example, the structure of the downlink PDU set information frame including the polling bit is shown in Table 3.
[0436] Table 3
[0437] The following parameters are added to Table 3:
[0438] 1. Discard report polling.
[0439] Description: This parameter indicates that the node hosting the NR PDCP entity requests a drop status report (packet loss information) for a set of PDUs.
[0440] Value range: {0 = no abandonment information report requested, 1 = abandonment information report requested}.
[0441] Field length: 1 bit.
[0442] The embodiments of the present disclosure also provide apparatuses for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by the first node in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by the second node in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by the third node in any of the above methods.
[0443] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.
[0444] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.
[0445] FIG5A is a schematic diagram of the structure of a first node proposed in an embodiment of the present disclosure. As shown in FIG5A , the first node 5100 may include: a transceiver module 5101 and a processing module 5102 .
[0446] In some embodiments, the transceiver module 5101 is configured to receive packet loss information sent by the second node, where the packet loss information is determined by the second node based on a packet data unit (PDU) loss condition of the second node.
[0447] In some embodiments, the processing module 5102 is configured to perform PDU packet loss processing based on the packet loss information.
[0448] Optionally, the above-mentioned transceiver module 5101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first node 5100 in any of the above methods (for example, step S2101, step S2104, step S2201, step S2204, but not limited to these), which will not be repeated here.
[0449] Optionally, the processing module 5102 is used to execute at least one of the other steps (such as step S2105 and step S2205, but not limited thereto) executed by the first node 5100 in any of the above methods, which will not be repeated here.
[0450] FIG5B is a schematic diagram of the structure of a second node proposed in an embodiment of the present disclosure. As shown in FIG5B , the second node 5200 may include: a processing module 5201 and a transceiver module 5202 .
[0451] In some embodiments, the processing module 5201 is configured to determine packet loss information based on packet data unit (PDU) loss conditions.
[0452] In some embodiments, the transceiver module 5202 is configured to send the packet loss information to the first node.
[0453] Optionally, the above-mentioned processing module 5201 is used to execute at least one of the other steps (for example, step S2101, step S2102, step S2104, step S2201, step S2202, step S2204, but not limited to these) performed by the second node 5200 in any of the above methods, which are not repeated here.
[0454] Optionally, the above-mentioned transceiver module 5202 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2103, step S2203, but not limited to this) performed by the second node 5200 in any of the above methods, which will not be repeated here.
[0455] FIG5C is a schematic diagram of the structure of a third node proposed in an embodiment of the present disclosure. As shown in FIG5C , the third node 5300 may include: a transceiver module 5301 .
[0456] In some embodiments, the above-mentioned transceiver module 5301 is configured to send a first message to the second node, and the first message includes a request message, and the request message is used to request the second node to send packet loss information to the first node, and the packet loss information is determined by the second node based on the packet data unit PDU packet loss situation of the second node.
[0457] Optionally, the above-mentioned transceiver module 5301 is used to execute at least one of the communication steps such as sending and / or receiving (for example, step S2102, step S2202, but not limited to this) performed by the third node 5300 in any of the above methods, which will not be repeated here.
[0458] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.
[0459] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.
[0460] Figure 6A is a schematic diagram of the structure of a communication device 6100 proposed in an embodiment of the present disclosure. Communication device 6100 can be a network device (e.g., a first node, a second node, a third node, etc.), or a chip, a chip system, or a processor that supports the network device in implementing any of the above methods. Communication device 6100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.
[0461] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to perform any of the above methods. Optionally, one or more processors 6101 are used to call instructions to cause the communication device 6100 to perform any of the above methods.
[0462] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps (e.g., steps S2101, S2102, S2104, S2201, S2202, S2204, but not limited thereto) of sending and / or receiving in the above method, and the processor 6101 performs at least one of the other steps (e.g., steps S2103, S2105, S2203, S2205, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.
[0463] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memories 6103 may be located outside the communication device 6100. In alternative embodiments, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuits 6104 are connected to the memory 6102 and may be configured to receive data from the memory 6102 or other devices, or to send data to the memory 6102 or other devices. For example, the interface circuits 6104 may read data stored in the memory 6102 and send the data to the processor 6101.
[0464] The communication device 6100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited to FIG6A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.
[0465] 6B is a schematic diagram of the structure of a chip 6200 according to an embodiment of the present disclosure. If the communication device 6100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 6200 shown in FIG6B , but the present disclosure is not limited thereto.
[0466] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to execute any of the above methods.
[0467] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Alternatively, all or part of memory 6203 may be located external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203 and may be used to receive data from memory 6203 or other devices, or may be used to send data to memory 6203 or other devices. For example, interface circuit 6202 may read data stored in memory 6203 and send the data to processor 6201.
[0468] In some embodiments, the interface circuit 6202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method (e.g., steps S2101, S2102, S2104, S2201, S2202, and S2204, but not limited thereto). The interface circuit 6202 performing the communication steps, such as sending and / or receiving, in the above-described method, for example, means that the interface circuit 6202 performs data exchange between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of the other steps (e.g., steps S2103, S2105, S2203, and S2205, but not limited thereto).
[0469] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0470] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 6100, the communication device 6100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.
[0471] The present disclosure also provides a program product, which, when executed by the communication device 6100, enables the communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.
[0472] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.
[0473] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A packet loss handling method, characterized in that, The method is executed by a first node and includes: Receiving packet loss information sent by a second node, where the packet loss information is determined by the second node based on the packet loss situation of the second node's packet data unit (PDU); Performing PDU packet loss processing based on the packet loss information.
2. The method according to claim 1, wherein The packet loss information includes at least one of the following: Packet loss PDU set sequence number (PSSN), where the packet loss PSSN is the sequence number of the PDU set discarded by the second node; Packet loss PDU sequence number (PSN), where the packet loss PSN is the sequence number of the PDU discarded by the second node; Packet loss percentage, where the packet loss percentage is the percentage of the number of PDUs discarded by the second node in the total number of PDUs; Packet loss reason.
3. The method according to claim 1 or 2, characterized in that, The receiving the packet loss information sent by the second node includes: Receiving a first user plane frame sent by the second node, where the first user plane frame includes the packet loss information.
4. The method according to claim 3, wherein The type of the first user plane frame is at least one of the following: Downlink user data frame; Auxiliary information data frame; Downlink PDU set information frame.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: Sending a second user plane frame to the second node, where the second user plane frame includes a request message for requesting the second node to send the packet loss information to the first node.
6. The method according to claim 5, wherein The type of the second user plane frame is at least one of the following: Downlink user data frame; Auxiliary information data frame; Downlink PDU set information frame.
7. The method according to claim 5 or 6, characterized in that The second user plane frame includes a polling bit, and when the bit value of the polling bit is a first value, it is used to request the second node to send the packet loss information to the first node.
8. A method for handling packet loss, characterized in that, The method is executed by a second node and includes: Determining packet loss information based on the packet loss situation of the packet data unit (PDU); Sending the packet loss information to a first node.
9. The method according to claim 8, wherein The packet loss information includes at least one of the following: Packet loss PDU set sequence number (PSSN), where the packet loss PSSN is the sequence number of the PDU set discarded by the second node; Packet loss PDU sequence number (PSN), where the packet loss PSN is the sequence number of the PDU discarded by the second node; Packet loss percentage, where the packet loss percentage is the percentage of the number of PDUs discarded by the second node in the total number of PDUs; Packet loss reason.
10. The method according to claim 8 or 9, characterized in that, The sending the packet loss information to the first node includes: Sending a first user plane frame to the first node, where the first user plane frame includes the packet loss information.
11. The method according to claim 10, wherein The type of the first user plane frame is at least one of the following: Downlink user data frame; Auxiliary information data frame; Downlink PDU set information frame.
12. The method according to any one of claims 8-11, characterized in that, The method further includes: Receiving a second user plane frame sent by the first node, where the second user plane frame includes a request message for requesting the second node to send the packet loss information to the first node.
13. The method according to claim 12, wherein The type of the second user plane frame is at least one of the following: Downlink user data frame; Auxiliary information data frame; Downlink PDU set information frame.
14. The method according to claim 12 or 13, characterized in that The second user plane frame includes a polling bit, and when the bit value of the polling bit is a first value, it is used to request the second node to send the packet loss information to the first node.
15. The method according to any one of claims 8-11, characterized in that, The method further includes: Receive a first message sent by a third node, where the first message includes a request message for requesting the second node to send the packet loss information to the first node.
16. The method according to claim 15, wherein the first node is the user plane gNB-CU-UP of the central unit of the network device, the second node is the distributed unit gNB-DU of the network device, the third node is the control plane gNB-CU-CP of the central unit of the network device, and the type of the first message is an F1AP message; or the first node is a gNB-DU, the second node is a gNB-CU-UP, the third node is the control plane gNB-CU-CP of the central unit of the network device, and the type of the first message is an E1AP message.
17. A method for handling packet loss, characterized in that, The method is executed by a third node and includes: Sending a first message to a second node, where the first message includes a request message for requesting the second node to send packet loss information to a first node, and the packet loss information is determined by the second node based on the packet loss situation of the second node's packet data unit PDU.
18. The method according to claim 17, wherein the first node is the user plane gNB-CU-UP of the central unit of the network device, the second node is the distributed unit gNB-DU of the network device, the third node is the control plane gNB-CU-CP of the central unit of the network device, and the type of the first message is an F1AP message; or the first node is a gNB-DU, the second node is a gNB-CU-UP, the third node is the control plane gNB-CU-CP of the central unit of the network device, and the type of the first message is an E1AP message.
19. A first node, characterized in that, Including: A transceiver module configured to receive the packet loss information sent by the second node, where the packet loss information is determined by the second node based on the packet loss situation of the second node's packet data unit PDU; A processing module configured to perform PDU packet loss processing based on the packet loss information.
20. A second node, characterized in that, Including: A processing module configured to determine packet loss information based on the packet loss situation of the packet data unit PDU; A transceiver module configured to send the packet loss information to the first node.
21. A third node, characterized in that, Including: A transceiver module configured to send a first message to the second node, where the first message includes a request message for requesting the second node to send packet loss information to the first node, and the packet loss information is determined by the second node based on the packet loss situation of the second node's packet data unit PDU.
22. A first node, characterized in that, Including: One or more processors; wherein the processor is used to execute the packet loss processing method according to any one of claims 1-7.
23. A second node, characterized in that, Including: One or more processors; wherein the processor is used to execute the packet loss processing method according to any one of claims 8-16.
24. A third node, characterized in that, Including: One or more processors; wherein the processor is used to execute the packet loss processing method according to claim 17 or 18.
25. A communication system, characterized in that, It includes a first node, a second node, and a third node. Among them, the first node is configured to implement the packet loss handling method described in any one of claims 1-7, the second node is configured to implement the packet loss handling method described in any one of claims 8-16, and the third node is configured to implement the packet loss handling method described in any one of claims 17 or 18.
26. A storage medium, the storage medium stores instructions, characterized in that, When the instruction runs on the communication device, it causes the communication device to execute the packet loss handling method described in any one of claims 1-7, 8-16, or 17-18.
Citation Information
Patent Citations
Communication method and device
CN113939044A
Information processing method and device, communication equipment and storage medium
CN116171561A
Enhancements for PDCP layer
US20160308776A1
Reliability measurement method, apparatus and system
WO2022052129A1