WO2024065550A1 - 一种丢包处理方法及装置 - Google Patents

一种丢包处理方法及装置 Download PDF

Info

Publication number
WO2024065550A1
WO2024065550A1 PCT/CN2022/122943 CN2022122943W WO2024065550A1 WO 2024065550 A1 WO2024065550 A1 WO 2024065550A1 CN 2022122943 W CN2022122943 W CN 2022122943W WO 2024065550 A1 WO2024065550 A1 WO 2024065550A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
packet loss
information
gnb
sent
Prior art date
Application number
PCT/CN2022/122943
Other languages
English (en)
French (fr)
Inventor
李艳华
吴锦花
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2022/122943 priority Critical patent/WO2024065550A1/zh
Publication of WO2024065550A1 publication Critical patent/WO2024065550A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a packet loss processing method and device.
  • multi-stream transmission is introduced in the Extended Reality (XR) service, and the concept of multi-stream modeling is introduced. That is, the data is distinguished according to its importance, such as I frame and P frame modeling, where I frame can be understood as a more important frame, and the terminal device needs to use I frame decoding, while P frame cannot be decoded alone. Therefore, on the core network side, a possible processing mechanism is that when an I frame is not transmitted and received correctly, the data packet corresponding to the associated P frame can be discarded to avoid unnecessary transmission and waste of air interface resources.
  • XR Extended Reality
  • an embodiment of the present disclosure provides a packet loss processing method, the method being applied to a first node, the method comprising:
  • the packet loss or information related to the packet loss is used to assist the core network in performing cost statistics.
  • sending the first information to the second node includes:
  • the first information is sent to the second node through a control plane.
  • an embodiment of the present disclosure provides a packet loss processing method, which is applied to a second node and includes:
  • a first message sent by a first node is received, where the first message includes packet loss or information related to packet loss.
  • an embodiment of the present disclosure provides a packet loss processing device, characterized in that the device is applied to a first node, and the device includes:
  • the sending module is used to send first information to the second node, where the first information includes packet loss or information related to packet loss.
  • an embodiment of the present disclosure provides a packet loss processing device, characterized in that the device is applied to a second node, and the device includes:
  • the receiving module is used to receive first information sent by a first node, where the first message includes packet loss or information related to packet loss.
  • an embodiment of the present disclosure provides a computer-readable storage medium for storing instructions for the above-mentioned communication device, and when the instructions are executed, the communication device executes the method described in the first aspect or the second aspect.
  • an embodiment of the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect above.
  • an embodiment of the present disclosure provides a chip system, which includes at least one processor and an interface, for supporting a communication device to implement the functions involved in the first aspect or the second aspect, for example, determining or processing at least one of the data and information involved in the above method.
  • the chip system also includes a memory, which is used to store computer programs and data necessary for the communication device.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • an embodiment of the present disclosure further provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first or second aspect above.
  • FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure.
  • FIG2 is a schematic diagram of a flow chart of a packet loss processing method provided by an embodiment of the present disclosure
  • FIG3 is a schematic diagram of a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG4 is a schematic diagram of a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG5 is a schematic diagram of a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG6 is a schematic diagram of a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG7 is a schematic diagram of a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG8 is a schematic flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG9 is a schematic flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • FIG10 is a schematic flow chart of another packet loss processing method provided in an embodiment of the present disclosure.
  • FIG11 is a flow chart of another packet loss processing method provided in an embodiment of the present disclosure.
  • FIG12 is a schematic diagram of a flow chart of another packet loss processing method provided in an embodiment of the present disclosure.
  • FIG13 is a flow chart of another packet loss processing method provided in an embodiment of the present disclosure.
  • FIG14 is a schematic diagram of a flow chart of another packet loss processing method provided in an embodiment of the present disclosure.
  • FIG15 is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.
  • FIG. 16 is a schematic diagram of the structure of a chip provided in an embodiment of the present disclosure.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure.
  • the communication system may include, but is not limited to, a network device and a terminal device.
  • the number and form of devices shown in FIG. 1 are only used as examples and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included.
  • the communication system shown in FIG. 1 includes, for example, a network device 11 and a terminal device 12.
  • LTE long term evolution
  • 5G fifth generation
  • NR 5G new radio
  • the network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals.
  • the network device 101 may be an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system.
  • eNB evolved NodeB
  • TRP transmission point
  • gNB next generation NodeB
  • WiFi wireless fidelity
  • the embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network device.
  • the network device provided in the embodiment of the present disclosure may be composed of a central unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit.
  • CU central unit
  • DU distributed unit
  • the CU-DU structure may be used to split the protocol layer of the network device, such as a base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.
  • the terminal device 12 in the disclosed embodiment is an entity on the user side for receiving or transmitting signals, such as a mobile phone.
  • the terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc.
  • the terminal device may be a car with communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in a smart city (smart city), a wireless terminal device in a smart home (smart home), etc.
  • the embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the terminal device.
  • 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 provided by the embodiment of the present disclosure.
  • a person skilled in the art can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.
  • multi-stream transmission is introduced in the Extended Reality (XR) service, and the concept of multi-stream modeling is introduced. That is, the data is distinguished according to its importance, such as I frame and P frame modeling, where I frame can be understood as a more important frame, and the terminal device needs to use I frame decoding, while P frame cannot be decoded alone. Therefore, on the wireless side, a possible processing mechanism is that when an I frame is not transmitted and received correctly, the data packet corresponding to the associated P frame can be discarded to avoid unnecessary transmission and waste of air interface resources.
  • XR Extended Reality
  • Figure 2 is a flow chart of a packet loss processing method provided by an embodiment of the present disclosure, and the method is executed by the first node. As shown in Figure 2, the method may include but is not limited to the following steps:
  • Step S201 Send first information to a second node, where the first information includes packet loss or information related to packet loss.
  • the first node sends packet loss or information related to packet loss to the second node to assist the second node in counting traffic and avoid inconsistency with the statistics on the terminal device side.
  • the packet loss refers to a data packet to be discarded, and the information related to the packet loss is generated based on statistics of the packet loss, wherein the statistics of the packet loss can be based on statistics of entity packet loss in the first node.
  • packet loss statistics are performed based on the Packet Data Convergence Protocol (PDCP) in the first node, wherein when the PDCP layer performs packet loss statistics, the packet loss statistics results of the Radio Link Control (RLC) entity in the node may also be referred to for statistics.
  • the packet loss amount of the PDCP layer statistics is X (possibly based on the timeout of the discard timer), and the packet loss amount of the RLC layer is Y, then the packet loss amount in the final PDCP statistics needs to consider the sum of the packet loss amount of the PDCP layer itself and the packet loss amount of the RLC layer.
  • statistics are performed based on packet loss signaling sent by the first node to other nodes.
  • PDCP can collect information related to packet loss based on packet loss signaling sent to RLC.
  • the PDCP of the centralized unit (CU) may count information related to packet loss based on packet loss signaling from the RLC of the distributed unit (DU).
  • the embodiment of the present disclosure does not limit the implementation method of packet loss statistics.
  • FIG. 3 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure, which can be applied to the second node.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S301 receiving first information sent by a first node, wherein the first message includes packet loss or information related to packet loss.
  • the first node sends packet loss or information related to packet loss to the second node, and the second node receives the first information sent by the first node to perform traffic statistics to avoid inconsistency with the statistics on the terminal device side.
  • the second node if the second node is a node responsible for statistics (for example, a session management function (SMF) or a user plane function (UPF)), the second node performs statistics based on the packet loss or information related to the packet loss.
  • a session management function for example, a session management function (SMF) or a user plane function (UPF)
  • the second node performs statistics based on the packet loss or information related to the packet loss.
  • SMF session management function
  • UPF user plane function
  • the packet loss or the data packet in the packet loss statistics is caused by the important data packet associated therewith failing to be correctly sent.
  • the packet loss may also refer to a data packet to be returned.
  • the second node if the second node is not the node responsible for statistics (for example, a node on a base station), the second node forwards the packet loss or information related to the packet loss to the node responsible for statistics or a node having a signaling connection therewith, so that the node responsible for statistics or a node having a signaling connection therewith performs statistics based on the packet loss or information related to the packet loss.
  • the node responsible for statistics or a node having a signaling connection therewith performs statistics based on the packet loss or information related to the packet loss.
  • the first node sends packet loss or information related to packet loss to the second node, and the packet loss or information related to packet loss received by the second node is used to assist the core network in performing cost statistics, so as to assist the core network in performing traffic statistics and cost statistics, and avoid inconsistencies with cost statistics on the terminal device side.
  • FIG. 4 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure, which can be applied to the second node.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S401 The first node sends the first information to the second node through the control plane.
  • the first information includes packet loss or information related to packet loss.
  • the information related to packet loss includes at least one of the following: a bearer identifier corresponding to the packet loss, a time of packet loss, a data volume of the packet loss, a packet loss rate, a reason for the packet loss, and a reason for reporting.
  • the bearer identifier corresponding to the packet loss includes but is not limited to a data radio bearer identifier (DRB) ID, a quality of service QoS Flow Identifier (QFI) ID, a protocol data unit session identifier (PDU) session ID, and a protocol data unit group identifier PDU set ID;
  • the time of packet loss includes but is not limited to a start timestamp and an end timestamp;
  • the data volume of the packet loss includes but is not limited to a data volume, and the data volume of the packet loss can be divided into an uplink data volume and/or a downlink data volume;
  • the packet loss rate is the proportion of the packet loss;
  • the reason for the packet loss includes but is not limited to an important frame loss;
  • the reason for reporting includes but is not limited to periodic reporting, switching reporting, and connection release.
  • the disclosed embodiment does not limit the information related to packet loss.
  • the base station-central unit-control plane gNB-CU-CP is responsible for the functions of the RRC and PDCP control planes.
  • Sending the first information to the second node through the control plane may specifically be, but is not limited to, sending the first information to the second node through signaling of the control plane.
  • the first node is a gNB-DU base station-distributed unit
  • the second node is a base station-central unit gNB-CU or gNB-CU-CP
  • the first message is an F1 application protocol (F1 Application Proposal, F1AP) message
  • F1AP Application Proposal
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the first message is an E1 Application Proposal (E1AP) message
  • the first node is a secondary node in a dual connectivity (DC) scenario
  • the second node is a primary node in a DC scenario
  • the first message is an Xn Application Proposal (XnAP) message
  • the XnAP message may be a packet loss statistics reporting message and/or other XnAP messages;
  • the first node is a gNB, a gNB-CU, a gNB-CU-CP or a base station-central unit-user plane gNB-CU-UP
  • the second node is a core network node (for example, a session management function (SMF))
  • the first message is an NG application protocol (NG Application Proposal, NGAP) message
  • the NGAP message may be a packet loss statistics reporting message and/or other NGAP messages.
  • NGAP NG Application Proposal
  • first node, the second node and the first message are not limited thereto.
  • Step S402 The second node receives the first information sent by the first node through the control plane.
  • the second node when the second node receives the first information, it also receives it based on the control plane.
  • the control plane please refer to the detailed description of step S301, so it will not be repeated here.
  • the first node sends packet loss or first information related to packet loss to the second node through the control plane, and the second node receives packet loss or information related to packet loss to assist the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistencies with the traffic and/or cost statistics on the terminal device side.
  • FIG. 5 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure, which can be applied to the second node.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment, or in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S501 The first node sends the first information to the second node through the user plane.
  • the first information includes packet loss or information related to packet loss.
  • information related to packet loss please refer to the above embodiment, so it will not be repeated here.
  • gNB-CU-UP In the separated architecture of the wireless network, gNB-CU-UP is responsible for the functions of GTP-U (GPRS Tunneling Protocol)-User plane, Service Data Adaptation Protocol (SDAP) and PDCP user plane.
  • GTP-U GPRS Tunneling Protocol
  • SDAP Service Data Adaptation Protocol
  • the first information is sent to the second node through a user plane, and specifically may be, but is not limited to, sending the first information to the second node through user data of the user plane.
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP
  • the second node is a UPF
  • the first node is a gNB, a gNB-CU, or a gNB-CU-UP
  • the second node is a UPF
  • the first node is a secondary node in a DC scenario
  • the second node is a primary node in a DC scenario
  • first node and the second node are at least one of the above.
  • the embodiments of the present disclosure are not limited to the first node and the second node.
  • Step S502 The second node receives the first information sent by the first node through the user plane.
  • the second node when the second node receives the first information, it also receives it based on the user plane.
  • the user plane please refer to the detailed description of step S401, so it will not be repeated here.
  • the first node sends packet loss or first information related to packet loss to the second node through the user plane, and the second node receives packet loss or information related to packet loss to assist the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistencies with the traffic and/or cost statistics on the terminal device side.
  • FIG6 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or any possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S601 The first node sends the packet loss to the second node via GTP-U, and the packet header of the GTP-U includes packet loss indication information, and the packet loss indication information is used to instruct the second node to identify whether the GTP-U protocol data unit (PDU) is a packet loss.
  • PDU protocol data unit
  • the first node sends a packet loss to the second node, and the packet loss refers to a packet received by the first node from the second node, but the first node does not send the data packet to the terminal device (for example, other packets related to the packet parsing are not sent correctly), but instead loses the packet.
  • the second node can calculate the amount of data corresponding to the packet loss based on the packet loss for traffic and/or cost statistics.
  • the first node sends a lost packet to the second node via GTP-U
  • the GTP-U packet header corresponding to the packet loss includes packet loss indication information
  • the packet loss indication information is used by the second node to identify whether the GTP-U PDU is a lost packet.
  • the packet loss or the data packet in the packet loss statistics is caused by the important data packet associated therewith failing to be correctly sent.
  • the packet loss may also refer to a data packet to be returned.
  • Step S602 The second node receives the GTP-U PDU sent by the first node, and obtains the packet loss indication information included in the GTP-U header according to the GTP-U PDU, wherein the packet loss indication information is used to instruct the second node to identify whether the GTP-UPDU is a packet loss.
  • the information indicating packet loss may also refer to information indicating packet return, and “packet loss” and “packet return” have the same meaning.
  • the second node receives the GTP-U PDU sent by the first node, parses the GTP-U PDU, obtains the packet loss indication information included in the GTP-U packet header, and determines whether the data packet received this time is packet loss according to the packet loss indication information. If it is determined to be packet loss, the data packet is discarded. If it is determined that the data packet is not packet loss, traffic and/or cost statistics are performed based on the received data packet.
  • the first node sends the packet loss information to the second node through GTP-U
  • the GTP-U packet header includes packet loss indication information
  • the second node receives the GTP-U PDU sent by the first node, obtains the packet loss indication information included in the GTP-U packet header according to the GTP-U PDU, and assists the core network in performing traffic and/or cost statistics according to the packet loss indication information to avoid the occurrence of inconsistency with the traffic and/or cost statistics on the terminal device side.
  • FIG7 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or any possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S701 the first node sends the information related to packet loss to the second node through GTP-U, and the packet header of the GTP-U includes the information related to packet loss.
  • a first node sends information related to packet loss to a second node
  • the statistical packet loss in the information related to packet loss refers to a data packet received by the first node from the second node, but the first node does not send the data packet to the terminal device (for example, other data packets related to the parsing of the data packet are not sent correctly), but instead loses or returns the data packet.
  • the second node can calculate the amount of data corresponding to the packet loss or packet return based on the information related to packet loss, for accurate traffic and/or cost statistics.
  • the first node sends information related to packet loss to the second node, where the information related to packet loss is included in a header of a GTP-U.
  • the information related to packet loss includes at least one of the following: a bearer identifier corresponding to the packet loss, a time of packet loss, a data volume of packet loss, a packet loss rate, a reason for packet loss, and a reason for reporting.
  • a bearer identifier corresponding to packet loss a time of packet loss, a data volume of packet loss, a packet loss rate, a reason for packet loss, and a reason for reporting.
  • the information related to packet loss is generated based on packet loss statistics, wherein the packet loss statistics may be based on entity packet loss in the first node.
  • packet loss statistics may be based on entity packet loss in the first node.
  • Step S702 The second node receives the GTP-U PDU sent by the first node, and obtains the information related to packet loss included in the GTP-U PDU header based on the GTP-U PDU.
  • the second node receives the GTP-U PDU sent by the first node, parses the GTP-U PDU, obtains the information related to packet loss included in the GTP-U packet header, and determines whether the data packet received this time is a lost or returned data packet based on the information related to packet loss, and performs traffic and/or cost statistics based on the received data packet.
  • the second node if the second node determines that the data packet received this time is a lost or returned data packet, the second node will subtract the lost or returned data packet from the traffic and/or billing statistics.
  • the first node sends the information related to packet loss to the second node through the GTP-U PDU
  • the second node receives the GTP-U PDU sent by the first node, obtains the information related to packet loss included in the GTP-U header according to the GTP-U PDU, and assists the core network in performing traffic and/or cost statistics according to the information related to packet loss, so as to avoid the occurrence of inconsistency with the traffic and/or cost statistics on the terminal device side.
  • FIG8 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S801 the second node sends second information to the first node, where the second information includes request information for packet loss statistics.
  • the second information is used to instruct the first node to send packet loss statistics, that is, the second node, as a requester of packet loss statistics, requests the first node whether to send packet loss statistics or when to send packet loss statistics, etc., and the first node performs packet loss statistics, processing and/or reporting according to the request of the second node.
  • the present disclosure does not limit the specific content contained in the second information.
  • Step S802 the first node receives the second information sent by the second node, and in response to receiving the second information sent by the second node, sends the first information to the second node, where the second information includes request information for packet loss statistics.
  • the first node sends packet loss or information related to packet loss to the second node.
  • the first node may send packet loss or information related to packet loss to the second node according to a preset protocol agreement; as another implementable method of this embodiment, the first node may send packet loss or information related to packet loss to the second node according to Operation Administration and Maintenance (OAM) configuration.
  • OAM Operation Administration and Maintenance
  • Step S803 Receive the first information sent by the first node in response to receiving the second information sent by the second device.
  • the first information includes packet loss or information related to packet loss.
  • packet loss or information related to packet loss.
  • the second node receives the first information sent by the first node, parses the first information, obtains the packet loss or information related to the packet loss included in the first information, and performs traffic and/or cost statistics based on the packet loss or information related to the packet loss.
  • the first node in response to receiving the second information sent by the second node, wherein the second information includes request information for packet loss statistics, the first node sends first information related to packet loss statistics to the second node, and the second node obtains the packet loss or information related to packet loss included in the first information, and assists the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistencies with the traffic and/or cost statistics on the terminal device side.
  • FIG. 9 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S901 The second node sends the second information to the first node through the user plane.
  • the second information is used to instruct the first node to send packet loss statistics, that is, the second node, as the controller of packet loss statistics, instructs the first node whether to send packet loss statistics or when to send packet loss statistics.
  • the present disclosure does not limit the specific content contained in the second information.
  • the second information is sent to the first node through a user plane, which may specifically be, but is not limited to, sending the second information to the first node through user data of the user plane.
  • the gNB-CU-UP is responsible for the functions of GTP-U, SDAP and PDCP user plane.
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-UP
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP, and the second node is a UPF;
  • the first node is a secondary node and the second node is a primary node.
  • first node and the second node are at least one of the above.
  • the embodiments of the present disclosure are not limited to the first node and the second node.
  • Step S902 The first node receives second information sent by the second node through the user plane.
  • the first node when the first node receives the second information, it is also received based on the user plane.
  • the user plane please refer to the detailed description of step S801, so it will not be repeated here.
  • the first node receives through the user plane the second information sent by the second node through the user plane, wherein the second information includes request information for packet loss statistics, and sends first information related to packet loss statistics to the second node.
  • the second node obtains the packet loss or information related to packet loss included in the first information, and assists the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistencies with the traffic and/or cost statistics on the terminal device side.
  • FIG. 10 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S1001 The second node sends the second information to the second node through the control plane.
  • the second information is used to instruct the first node to send packet loss statistics, that is, the second node, as a requester of packet loss statistics, requests the first node whether to send packet loss statistics or when to send packet loss statistics, etc., and the first node performs packet loss statistics, processing and/or reporting according to the request of the second node.
  • the present disclosure does not limit the specific content contained in the second information.
  • the second information is sent to the first node through the control plane, which may specifically be but is not limited to sending the second information to the first node through signaling of the control plane.
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-CP
  • the second message is a F1AP message, which may be a UE CONTEXT REQUEST message, a UE CONTEXT MODIFY REQUEST message, or another F1AP message;
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the second message is an E1AP message
  • the E1AP message may be a bearer context request message, a bearer context modification request message, or other E1AP message
  • the first node is a primary node
  • the second node is a secondary node
  • the second message is an XnAP message
  • the XnAP message is an SN add request message, an SN modify request message, or other XnAP message
  • the first node is a target gNB
  • the second node is a source gNB
  • the second message is an XnAP message
  • the XnAP message is a handover request message, a retrieve UE context feedback message, or other XnAP message
  • the first node is a gNB, a gNB-CU, a gNB-CU-CP, or a gNB-CU-UP
  • the second node is a core network node
  • the second message is an NGAP message
  • the NGAP message may be a UE context establishment request message, a UE context modification request message, a PDU session resource establishment request message, a PDU session resource modification request message, or other NGAP messages.
  • Step S1002 The first node receives second information sent by the second node through the control plane.
  • the first node when the first node receives the second information sent by the second node through the control plane, it is also received based on the control plane.
  • the control plane please refer to the detailed description of step S901, so it will not be repeated here.
  • the first node receives through the control plane the second information sent by the second node through the control plane, wherein the second information includes request information for packet loss statistics, and sends first information related to packet loss statistics to the second node.
  • the second node obtains the packet loss or information related to packet loss included in the first information, and assists the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistencies with the traffic and/or cost statistics on the terminal device side.
  • FIG. 11 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S1101 The second node sends the second information to the first node through GTP-U, and the packet header of the GTP-U PDU includes request information related to packet loss.
  • This embodiment is used in a process of sending the second information to the first node through a user plane.
  • the second node sends request information related to packet loss to the first node via GTP-U.
  • the information for the packet loss statistics request includes at least one of the following:
  • Packet loss statistics indication for example, can carry the packet loss report query Discard Report polling in the GTP-U packet header to indicate that operations related to packet loss need to be performed.
  • the bearer identifier of the packet loss report such as DRB, QFI, PDU session ID, PDU set ID, is used to indicate the granularity of the operations related to packet loss of the first node.
  • a threshold for packet loss reporting where the threshold may be a packet size or a packet loss rate.
  • the first node performs reporting;
  • the time of packet loss reporting where the time may be a specific time period and/or a reporting period, and is used to indicate when the first node performs packet loss related reporting;
  • the packet loss reporting method includes user plane (User Plane, UP) reporting, control plane (Control Plane, CP) reporting, packet loss return and/or packet loss size indication, etc.
  • the reporting method is used to indicate the first node how to report related to packet loss.
  • Step S1102 The first node receives the GTP-U PDU sent by the second node, and obtains the request information related to packet loss included in the GTP-U packet header according to the GTP-U PDU.
  • the GTP-U PDU is parsed to obtain the request information related to the packet loss included in the GTP-U packet header, and the first information is reported based on the request information related to the packet loss.
  • the first node obtains request information related to packet loss included in the GTP-U packet header based on the GTP-U PDU sent by the second node, and sends first information related to packet loss statistics to the second node based on the request information related to packet loss.
  • the second node obtains packet loss or information related to packet loss included in the first information, and assists the core network in performing traffic and/or cost statistics to avoid the occurrence of inconsistency with the traffic and/or cost statistics on the terminal device side.
  • FIG. 12 is a flow chart of another packet loss processing method provided by an embodiment of the present disclosure.
  • the packet loss processing method can be executed alone or in combination with any embodiment of the present disclosure or a possible implementation method in an embodiment. It can also be executed in combination with any technical solution in the related technology.
  • the packet loss processing method may include the following steps:
  • Step S1201 In response to determining to perform an operation related to packet loss, sending the first information to the second node.
  • the operation related to packet loss is performed.
  • the first node sends first information related to packet loss to the second node.
  • the operation related to packet loss is any one of the following: monitoring packet loss, reporting information related to packet loss, and returning packet loss (ie, sending returned data packets). There is no limitation on the operation related to packet loss.
  • the present disclosure also provides a packet loss processing device. Since the packet loss processing device provided in the embodiments of the present disclosure corresponds to the packet loss processing method provided in the embodiments of Figures 2 to 12 above, the implementation method of the packet loss processing method is also applicable to the packet loss processing device provided in the embodiments of the present disclosure, and will not be described in detail in the embodiments of the present disclosure.
  • FIG13 is a schematic diagram of the structure of a packet loss processing device provided by an embodiment of the present disclosure.
  • the device is arranged at a first node, and the device comprises:
  • the sending module 1301 is used to send first information to the second node, where the first information includes packet loss or information related to packet loss.
  • the packet loss or information related to the packet loss is used to assist the core network in performing cost statistics.
  • the sending module 1301 is further configured to:
  • the first information is sent to the second node through a control plane.
  • the first node, the second node, and the first information are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-CP
  • the first information is an F1AP message
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the first information is an E1AP message
  • the first node is a secondary node, the second node is a primary node, and the first information is an XnAP message;
  • the first node is gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, the second node is a core network node, and the first information is an NGAP message.
  • the sending module 1301 is further configured to:
  • the first information is sent to the second node through a user plane.
  • the first node and the second node are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-UP;
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP, and the second node is a UPF;
  • the first node is a secondary node, and the second node is a primary node.
  • the sending module 1301 is further configured to:
  • the packet loss is sent to the second node via GTP-U, wherein the packet header of the GTP-U includes packet loss indication information, and the packet loss indication information is used to instruct the second node to identify whether the GTP-U PDU is a packet loss.
  • the sending module 1301 is further configured to include:
  • the information related to packet loss is sent to the second node via GTP-U, and the packet header of the GTP-U includes the information related to packet loss.
  • the information related to packet loss includes at least one of the following:
  • the bearer identifier corresponding to the packet loss, the time of packet loss, the amount of packet loss data, the packet loss rate, the reason for packet loss, and the reason for reporting.
  • the sending module 1301 is further configured to:
  • the first information is sent to the second node, where the second information includes request information for packet loss statistics.
  • the receiving module 1302 is configured to receive second information sent by the second node through a user plane.
  • the receiving module 1302 is further configured to:
  • the GTP-U PDU obtain request information related to packet loss included in the GTP-U packet header.
  • the first node and the second node are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-UP;
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP, and the second node is a UPF;
  • the first node is a secondary node, and the second node is a primary node.
  • the receiving module 1302 is further configured to:
  • Second information sent by the second node through the control plane is received.
  • the first node, the second node, and the first information are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-CP
  • the first information is an F1AP message
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the first information is an E1AP message
  • the first node is a primary node
  • the second node is a secondary node
  • the first information is an XnAP message
  • the first node is a gNB, a gNB-CU, a gNB-CU-CP or a gNB-CU-UP, the second node is a core network node, and the first information is an NGAP message;
  • the first node is a target gNB
  • the second node is a source gNB
  • the second information is an XnAP message.
  • the information used for the packet loss statistics request includes at least one of the following:
  • Packet loss statistics indication Packet loss statistics indication, bearer identifier for packet loss reporting, threshold for packet loss reporting, time for packet loss reporting, and method for packet loss reporting.
  • the sending module 1301 is further configured to:
  • the first information is sent to the second node.
  • the operation related to packet loss is any one of the following:
  • Monitor packet loss report information related to packet loss, and return lost packets.
  • FIG14 is a packet loss processing device provided by an embodiment of the present disclosure, wherein the device is applied to a second node, and the device includes:
  • the receiving module 1401 is configured to receive first information sent by a first node, where the first message includes packet loss or information related to packet loss.
  • the packet loss or information related to the packet loss is used to assist the core network in performing cost statistics.
  • the receiving module 1401 is further configured to:
  • the first node, the second node, and the first information are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-CP
  • the first information is an F1AP message
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the first information is an E1AP message
  • the first node is a secondary node, the second node is a primary node, and the first information is an XnAP message;
  • the first node is gNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, the second node is a core network node, and the first information is an NGAP message.
  • the receiving module 1401 is further configured to:
  • the first node and the second node are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-UP;
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP, and the second node is a UPF;
  • the first node is a secondary node, and the second node is a primary node.
  • the receiving module 1401 is further configured to:
  • packet loss indication information included in the GTP-U packet header is obtained, and the packet loss indication information is used to instruct the second node to identify whether the GTP-U PDU is a packet loss.
  • the receiving module 1401 is further configured to:
  • the GTP-U PDU obtain the packet loss related information included in the GTP-U packet header.
  • the information related to packet loss includes at least one of the following:
  • the bearer identifier corresponding to the packet loss, the time of packet loss, the amount of packet loss data, the packet loss rate, the reason for packet loss, and the reason for reporting.
  • the receiving module 1401 is further configured to:
  • the first information is received, which is sent by the first node to the second node in response to receiving the second information sent by the second device, wherein the second information includes request information for packet loss statistics.
  • the device further includes:
  • the sending module 1402 is configured to send the second information to the first node.
  • the sending module 1402 is further configured to:
  • the second information is sent to the first node through a user plane.
  • the sending module 1402 is further configured to:
  • the second information is sent to the first node via GTP-U, wherein the packet header of the GTP-U includes request information related to packet loss.
  • the first node and the second node are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-UP;
  • the first node is a gNB, a gNB-CU or a gNB-CU-UP, and the second node is a UPF;
  • the first node is a secondary node, and the second node is a primary node.
  • the sending module 1402 is further configured to:
  • the second information is sent to the first node through a control plane.
  • the first node, the second node, and the second information are at least one of the following:
  • the first node is a gNB-DU
  • the second node is a gNB-CU or a gNB-CU-CP
  • the second information is an F1AP message
  • the first node is a gNB-CU-UP
  • the second node is a gNB-CU-CP
  • the second information is an E1AP message
  • the first node is a primary node
  • the second node is a secondary node
  • the second information is an XnAP message
  • the first node is a gNB, a gNB-CU, a gNB-CU-CP or a gNB-CU-UP
  • the second node is a core network node
  • the second information is an NGAP message
  • the first node is a target gNB
  • the second node is a source gNB
  • the second information is an XnAP message.
  • the information used for the packet loss statistics request includes at least one of the following:
  • Packet loss statistics indication Packet loss statistics indication, bearer identifier for packet loss reporting, threshold for packet loss reporting, time for packet loss reporting, and method for packet loss reporting.
  • the receiving module 1401 is further configured to:
  • the first information sent by the first node to the second node in response to determining to perform an operation related to packet loss is received.
  • the operation related to packet loss is any one of the following:
  • Monitor packet loss report information related to packet loss, and return lost packets.
  • the communication device 1500 can be a network device, or a terminal device, or a chip, a chip system, or a processor that supports the network device to implement the above method, or a chip, a chip system, or a processor that supports the terminal device to implement the above method.
  • the device can be used to implement the method described in the above method embodiment, and the details can be referred to the description in the above method embodiment.
  • the communication device 1500 may include one or more processors 1501.
  • the processor 1501 may be a general-purpose processor or a dedicated processor, etc.
  • it may be a baseband processor or a central processing unit.
  • the baseband processor may be used to process the communication protocol and communication data
  • the central processing unit may 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 a computer program, and process the data of the computer program.
  • the communication device 1500 may further include one or more memories 1502, on which a computer program 1504 may be stored, and the processor 1501 executes the computer program 1504 so that the communication device 1500 performs the method described in the above method embodiment.
  • data may also be stored in the memory 1502.
  • the communication device 1500 and the memory 1502 may be provided separately or integrated together.
  • the communication device 1500 may further include a transceiver 1505 and an antenna 1506.
  • the transceiver 1505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 1505 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., and is used to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is used to implement a transmitting function.
  • the communication device 1500 may further include one or more interface circuits 1507.
  • the interface circuit 1507 is used to receive code instructions and transmit them to the processor 1501.
  • the processor 1501 runs the code instructions to enable the communication device 1500 to perform the method described in the above method embodiment.
  • the communication device 1500 is a first node: the transceiver 1505 is used to execute steps such as step 201 in FIG. 2 .
  • the communication device 1500 is a network device: the transceiver 1505 is used to execute steps such as step 402 in FIG. 4 .
  • the processor 1501 may include a transceiver for implementing the receiving and sending functions.
  • the transceiver may be a transceiver circuit, an interface, or an interface circuit.
  • the transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
  • the processor 1501 may store a computer program 1503, which runs on the processor 1501 and enables the communication device 1500 to perform the method described in the above method embodiment.
  • the computer program 1503 may be fixed in the processor 1501, in which case the processor 1501 may be implemented by hardware.
  • the communication device 1500 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiments.
  • the processor and transceiver described in the present disclosure may be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
  • the processor and transceiver may also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS N-type metal oxide semiconductor
  • PMOS P-type metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in the present disclosure is not limited thereto, and the structure of the communication device may not be limited by FIG. 15.
  • the communication device may be an independent device or may be part of a larger device.
  • the communication device may be:
  • the IC set may also include a storage component for storing data and computer programs;
  • ASIC such as modem
  • the communication device can be a chip or a chip system
  • the communication device can be a chip or a chip system
  • the schematic diagram of the chip structure shown in Figure 16 includes a processor 1601 and an interface 1603.
  • the number of processors 1601 can be one or more, and the number of interfaces 1603 can be multiple.
  • Interface 1603 is used to execute step 201 in FIG. 2 ; step 301 in FIG. 3 ; step 401 in FIG. 4 ; step 501 in FIG. 5 , etc.
  • Interface 1603 is used to execute step 402 in FIG. 4 , step 502 in FIG. 5 , etc.
  • the chip 1600 further includes a memory 1602, and the memory 1602 is used to store necessary computer programs and data.
  • the present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.
  • the present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
  • the computer program product includes one or more computer programs.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer program can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
  • a magnetic medium e.g., a floppy disk, a hard disk, a magnetic tape
  • an optical medium e.g., a high-density digital video disc (DVD)
  • DVD high-density digital video disc
  • SSD solid state disk
  • At least one in the present disclosure may also be described as one or more, and a plurality may be two, three, four or more, which is not limited in the present disclosure.
  • the technical features in the technical feature are distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc., and there is no order of precedence or size between the technical features described by the "first”, “second”, “third”, “A”, “B”, “C” and “D”.
  • plural refers to two or more than two, and other quantifiers are similar thereto.
  • “And/or” describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects before and after are in an “or” relationship.
  • the singular forms “a”, “the”, and “the” are also intended to include plural forms, unless the context clearly indicates other meanings.
  • the corresponding relationships shown in the tables in the present disclosure can be configured or predefined.
  • the values of the information in each table are only examples and can be configured as other values, which are not limited by the present disclosure.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc.
  • the names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of the parameters can also be other values or representations that can be understood by the communication device.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种丢包处理方法及装置，应用于通信技术领域，方法包括：第一节点向第二节点发送第一信息，第二节点接收第一信息，第一信息中包括丢包或者与丢包相关的信息，由此第二节点接收丢包或者与丢包相关的信息，以辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。

Description

一种丢包处理方法及装置 技术领域
本公开涉及通信技术领域，尤其涉及一种丢包处理方法及装置。
背景技术
相关技术中，扩展现实(ExtendedReality，XR)业务中，引入了多流传输，并引入了多流建模的概念。即按照数据的重要性进行区分，比如I帧和P帧建模，其中I帧可以理解为比较重要的帧，终端设备需要利用I帧解码，而P帧无法单独解码。因此，在核心网侧，可能的处理机制是，当I帧没有正确传输和接收，可以丢掉与之关联的P帧对应的数据包，以避免不必要的传输和空口资源的浪费。
若由于无线侧无法正确发送重要帧，而丢掉一定数量的与重要帧关联的其他帧对应的数据包，会导致核心网侧的流量统计和终端设备侧的流量统计不一致的问题。
发明内容
第一方面，本公开实施例提供一种丢包处理方法，所述方法应用于第一节点，所述方法包括：
向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
在一种实现方式中，所述丢包或者与丢包相关的信息用于辅助核心网进行费用统计。
在一种实现方式中，所述向第二节点发送第一信息包括：
通过控制平面向所述第二节点发送所述第一信息。
第二方面，本公开实施例提供一种丢包处理方法，所述方法应于第二节点，所述方法包括：
接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
第三方面，本公开实施例提供一种丢包处理装置，其特征在于，所述装置应用于第一节点，所述装置包括：
发送模块，用于向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
第四方面，本公开实施例提供一种丢包处理装置，其特征在于，所述装置应于第二节点，所述装置包括：
接收模块，用于接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
第五方面，本公开实施例提供了一种计算机可读存储介质，用于储存为上述通信装置所用的指令，当所述指令被执行时，使所述通信装置执行上述第一方面或第二方面所述的方法。
第六方面，本公开实施例还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面所述的方法。
第七方面，本公开实施例提供了一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持通信装置实现第一方面或第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存通信装置必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括 芯片和其他分立器件。
第八方面，本公开实施例还提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面所述的方法。
附图说明
为了更清楚地说明本公开实施例或背景技术中的技术方案，下面将对本公开实施例或背景技术中所需要使用的附图进行说明。
图1为本公开实施例提供的一种通信系统的架构示意图；
图2为本公开实施例提供的一种丢包处理方法的流程示意图；
图3为本公开实施例提供的另一种丢包处理方法的流程示意图；
图4为本公开实施例提供的另一种丢包处理方法的流程示意图；
图5为本公开实施例提供的另一种丢包处理方法的流程示意图；
图6为本公开实施例提供的另一种丢包处理方法的流程示意图；
图7为本公开实施例提供的另一种丢包处理方法的流程示意图；
图8为本公开实施例提供的另一种丢包处理方法的流程示意图；
图9为本公开实施例提供的另一种丢包处理方法的流程示意图；
图10为本公开实施例提供的另一种丢包处理方法的流程示意图；
图11为本公开实施例提供的另一种丢包处理方法的流程示意图；
图12为本公开实施例提供的另一种丢包处理方法的流程示意图；
图13为本公开实施例提供的另一种丢包处理方法的流程示意图；
图14为本公开实施例提供的另一种丢包处理方法的流程示意图；
图15为本公开实施例提供的一种通信装置的结构示意图；
图16是本公开实施例提供的芯片的结构示意图。
具体实施方式
为了更好的理解本公开实施例公开的一种丢包处理方法及装置，下面首先对本公开实施例适用的通信系统进行描述。
请参见图1，图1为本公开实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个网络设备、和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本公开实施例的限定，实际应用中可以包括两个或两个以上的网络设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个网络设备11、和一个终端设备12为例。
需要说明的是，本公开实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本公开实施例中的网络设备11是网络侧的一种用于发射或接收信号的实体。例如，网络设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中 的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本公开的实施例对网络设备所采用的具体技术和具体设备形态不做限定。本公开实施例提供的网络设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将网络设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本公开实施例中的终端设备12是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本公开的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
可以理解的是，本公开实施例描述的通信系统是为了更加清楚的说明本公开实施例的技术方案，并不构成对于本公开实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本公开实施例提供的技术方案对于类似的技术问题，同样适用。
相关技术中，扩展现实(ExtendedReality，XR)业务中，引入了多流传输，并引入了多流建模的概念。即按照数据的重要性进行区分，比如I帧和P帧建模，其中I帧可以理解为比较重要的帧，终端设备需要利用I帧解码，而P帧无法单独解码。因此，在无线侧，可能的处理机制是，当I帧没有正确传输和接收，可以丢掉与之关联的P帧对应的数据包，以避免不必要的传输和空口资源的浪费。
若由于无线侧无法正确发送重要帧，而丢掉一定数量的与重要帧关联的其他帧对应的数据包，会导致核心网侧的流量统计和终端设备侧的流量统计不一致的问题。
请参见图2，图2为本公开实施例提供的一种丢包处理方法的流程示意图，该方法由第一节点执行。如图2所示，该方法可以包括但不限于如下步骤：
步骤S201，向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
第一节点向第二节点发送丢包或者与丢包相关的信息，以辅助第二节点进行统计流量，避免与终端设备侧的统计不一致。
作为一种实施例，丢包为要丢掉的数据包，所述丢包相关的信息是根据丢包的统计生成的，其中，所述丢包的统计可以是基于第一节点中的实体丢包进行统计的。
作为一种实施例，基于第一节点中的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)进行丢包统计，其中PDCP层进行丢包统计时，还可以参考该节点中无线链路层控制协 议(Radio Link Control，RLC)实体的丢包统计结果进行统计。例如，PDCP层统计丢包量为X(可能基于丢弃定时器超时)，而RLC层丢包量为Y，则PDCP最终统计中的丢包量时需要同时考虑PDCP层自身的丢包量和RLC层丢包量之和。
作为一种实施例，基于第一节点向其他节点发送的丢包信令而进行统计的，例如，PDCP可以基于发送给RLC的丢包信令统计丢包相关的信息。
作为一种实施例，也可以是第一节点从其他节点收到的与丢包相关的信息；例如，集中单元(Centralized Unit，CU)的PDCP可以基于从分布单元(Distributed Unit，DU)的RLC的丢包信令统计丢包相关的信息。本公开实施例对丢包统计的实现方式不进行限定。
本公开实施例提供了另一种丢包处理方法，图3为本公开实施例提供的另一种丢包处理方法的流程示意图，可应用于第二节点，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图3所示，该丢包处理方法可包括如下步骤：
步骤S301：接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
第一节点向第二节点发送丢包或者与丢包相关的信息，第二节点接收第一节点发送的第一信息，以进行流量统计，避免与终端设备侧的统计不一致。
在一些实施例中，如果所述第二节点是负责统计的节点(例如，会话管理功能(Session Management Function,SMF)或用户面功能(User Plane Function,UPF))，所述第二节点根据所述丢包或者与丢包相关的信息进行统计。
在一些实施例中，所述丢包或丢包统计中的数据包是由于与之关联的重要数据包无法正确发送而导致的。
在本公开实施例中，所述丢包也可以是指要退回的数据包。
在一些实施例中，如果所述第二节点不是负责统计的节点(例如基站上的节点)，所述第二节点将所述丢包或者与丢包相关的信息转发给负责统计的节点或与之有信令连接的节点，以使负责统计的节点或与之有信令连接的节点根据所述丢包或者与丢包相关的信息进行统计。
在一些实施例中，第一节点向第二节点发送丢包或者与丢包相关的信息，以及第二节点接收到的丢包或者与丢包相关的信息，用于辅助核心网进行费用统计，以辅助核心网进行流量统计、费用统计，避免与终端设备侧的费用统计不一致。
本公开实施例提供了另一种丢包处理方法，图4为本公开实施例提供的另一种丢包处理方法的流程示意图，可应用于第二节点，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图4所示，该丢包处理方法可包括如下步骤：
步骤S401：第一节点通过控制平面向所述第二节点发送所述第一信息。
所述第一信息中包括丢包或者与丢包相关的信息。所述与丢包相关的信息包括以下至少一 个：丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。其中，丢包对应的承载标识包含但不限于数据无线承载标识(Data Radio Bearer，DRB)ID、业务质量流标识(Qualityof Service QoS Flow Identifier，QFI)ID、协议数据单元会话标识(Protocal Data Unit，PDU)session ID、协议数据单元组标识PDU set ID；丢包的时间包含但不限于开始时间戳start timestamp、结束时间戳end timestamp；丢包的数据量包含但不限于数据量data volume，丢包的数据量可以分为上行数据量和/或下行数据量；丢包率为丢包的比例；丢包的原因包含但不限于重要帧丢失；上报的原因包含但不限于周期上报、切换上报、连接释放，本公开实施例对与丢包相关的信息不做限定。
在无线网络的分离架构中，基站-中央单元-控制平面gNB-CU-CP负责RRC和PDCP控制平面的功能。
通过控制平面向所述第二节点发送所述第一信息，具体可以但不局限于为通过控制平面的信令向所述第二节点发送第一信息。
所述第一节点是gNB-DU基站-分布单元，所述第二节点是基站-中央单元gNB-CU或gNB-CU-CP，所述第一消息是F1应用协议(F1 Application Proposal，F1AP)消息，所述F1AP消息丢包统计上报消息和/或其他F1AP消息；
在一些实施例中，所述第一节点是gNB-CU-UP，所述第二节点是gNB-CU-CP，所述第一消息是E1应用协议(E1 Application Proposal，E1AP)消息，所述F1AP消息丢包统计上报消息和/或其他E1AP消息；
在一些实施例中，所述第一节点是双连接(Dual Connectivity，DC)场景下的辅节点，所述第二节点是DC场景下的主节点，所述第一消息是Xn应用协议(Xn Application Proposal，XnAP)消息，所述XnAP消息可以是丢包统计上报消息和/或其他XnAP消息；
在一些实施例中，所述第一节点是gNB、gNB-CU、gNB-CU-CP或基站-中央单元-用户平面gNB-CU-UP，所述第二节点是核心网节点(例如，会话管理功能(Session Management Function，SMF))，所述第一消息是NG应用协议(NG Application Proposal，NGAP)消息，所述NGAP消息可以是丢包统计上报消息和/或其他NGAP消息。
应当理解，以上仅为示例，第一节点、第二节点和第一消息不限于此。
有关第一节点进行丢包统计的具体实现，可参见上述实施例，故在此不再赘述。
步骤S402：第二节点接收所述第一节点通过控制平面发送所述的第一信息。
对第一节点相对应的，在第二节点接收第一信息时，同样基于控制平面进行接收，有关控制平面的解释，可参见步骤S301的详细说明，故在此不再赘述。
综上所述，第一节点通过控制平面向第二节点发送丢包或者与丢包相关的第一信息，第二节点接收丢包或者与丢包相关的信息，以辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图5为本公开实施例提供的另一种丢包处理方法的流程示意图，可应用于第二节点，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种 技术方案一起被执行。
如图5所示，该丢包处理方法可包括如下步骤：
步骤S501：第一节点通过用户平面向所述第二节点发送所述第一信息。
所述第一信息中包括丢包或者与丢包相关的信息，有关与丢包相关的信息的说明，可参见上述实施例，故在此不再赘述。
在无线网络的分离架构中，gNB-CU-UP负责GTP-U(GPRS隧道协议,GPRSTunnelingProtocol)-User用户平面,、业务数据适配协议(Service Data Adaptation Protocol，SDAP)和PDCP用户平面的功能。
通过用户平面向所述第二节点发送所述第一信息，具体可以但不局限于为通过用户平面的用户数据向所述第二节点发送第一信息。
在一些实施例中，所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF。
在一些实施例中，所述第一节点是gNB、gNB-CU、gNB-CU-UP，所述第二节点是UPF。
在一些实施例中，所述第一节点为DC场景下的辅节点，所述第二节点为DC场景下的主节点。
应当理解，以上仅为示例，关于第一节点、所述第二节点为以上至少一种，本公开实施例对第一节点、第二节点不限于此。
步骤S502：第二节点接收所述第一节点通过用户平面发送所述的第一信息。
对第一节点相对应的，在第二节点接收第一信息时，同样基于用户平面进行接收，有关用户平面的解释，可参见步骤S401的详细说明，故在此不再赘述。
综上所述，第一节点通过用户平面向第二节点发送丢包或者与丢包相关的第一信息，第二节点接收丢包或者与丢包相关的信息，以辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图6为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图6所示，该丢包处理方法可包括如下步骤：
步骤S601：第一节点通过GTP-U将丢包发送给所述第二节点，所述GTP-U的包头中包括丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-U协议数据单元(Protocal Data Unit，PDU)是否为丢包。
在一些实施例中，第一节点向第二节点发送丢包，所述丢包是指第一节点从第二节点接收的包，但第一节点不要把所述数据包发送给终端设备(例如与所述包解析相关的其他包没有被正确发送)，而是丢包，第二节点可以根据所述丢包，计算丢包对应的数据量，用于流量和/或费用统计。
在一些实例中，第一节点将丢包通过GTP-U发送至第二节点，在丢包对应的GTP-U包头中包括丢包指示信息，所述丢包指示信息用于第二节点识别所述GTP-U PDU是否为丢包。
在一些实施例中，所述丢包或丢包统计中的数据包是由于与之关联的重要数据包无法正确 发送而导致的。
在本发明中，所述丢包也可以是指要退回的数据包。
有关第一节点进行丢包统计的具体实现，可参见上述实施例，故在此不再赘述。
步骤S602：第二节点接收所述第一节点发送的GTP-U PDU，根据所述GTP-U PDU，获取所述GTP-U包头中包括的丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-UPDU是否为丢包。
在本公开实施例中，所述丢包指示的信息也可以是指退包指示的信息，“丢包”与“退包”具有相同的含义。
对第一节点相对应的，第二节点接收所述第一节点发送的GTP-U PDU，对GTP-U PDU进行解析，得到GTP-U包头中包括的丢包指示信息，并根据丢包指示信息确定本次接收的数据包是否为丢包，若确定为丢包，则将该数据包进行丢弃，若确定该数据包不为丢包，则基于接收到的数据包进行流量和/或费用统计。
综上所述，第一节点通过GTP-U将丢包发送给所述第二节点，所述GTP-U的包头中包括丢包指示信息，第二节点接收所述第一节点发送的GTP-U PDU，根据所述GTP-U PDU，获取所述GTP-U包头中包括的丢包指示信息，根据该丢包指示信息辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图7为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图7所示，该丢包处理方法可包括如下步骤：
步骤S701：第一节点通过GTP-U将所述丢包相关的信息发送给所述第二节点，所述GTP-U的包头中包括所述与丢包相关的信息。
在一些实施例中，第一节点向第二节点发送丢包相关的信息，所述丢包相关的信息中的统计的丢包是指第一节点从第二节点接收的数据包，但第一节点不要把所述数据包发送给终端设备(例如与所述数据包解析相关的其他数据包没有被正确发送)，而是丢掉或退回所述数据包，第二节点可以根据所述丢包相关的信息，计算丢包或退包对应的数据量，用于准确地流量和/或费用统计。
在一些实例中，第一节点向第二节点发送与丢包相关的信息，所述与丢包相关的信息被包括在GTP-U的包头中。
在一些实例中，与丢包相关的信息包括以下至少一个：丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。有关丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因的举例说明，可参见上述实施例，故在此不再赘述。
在一些实施例中，所述与丢包相关的信息是根据丢包的统计生成的，其中，所述丢包的统计可以是基于第一节点中的实体丢包进行统计的，有关第一节点进行丢包统计的具体实现，可参见上述实施例，故在此不再赘述。
步骤S702：第二节点接收所述第一节点发送的GTP-U PDU，根据所述GTP-U PDU，获取所述GTP-U PDU包头中包括的所述与丢包相关的信息。
对第一节点相对应的，第二节点接收所述第一节点发送的GTP-U PDU，对GTP-U PDU进行解析，得到GTP-U包头中包括的与丢包相关的信息，并根据与丢包相关的信息确定本次接收的数据包是否为丢包或退回的数据包，并基于接收到的数据包进行流量和/或费用统计。
在一些实施例中，若第二节点确定本次接收的数据包为丢包或退回的数据包，则第二节点将在流量和/或计费统计中减去所述丢包或退回的数据包。
综上所述，第一节点通过GTP-U PDU将与丢包相关的信息发送给所述第二节点，第二节点接收所述第一节点发送的GTP-U PDU，根据所述GTP-U PDU，获取所述GTP-U包头中包括的与丢包相关的信息，根据与丢包相关的信息辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图8为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图8所示，该丢包处理方法可包括如下步骤：
步骤S801：第二节点向所述第一节点发送第二信息，所述第二信息中包括用于丢包统计的请求信息。
该第二信息用于指示第一节点发送丢包统计，也就是说，第二节点作为丢包统计的请求方，请求第一节点是否发送丢包统计或何时发送丢包统计等控制，第一节点根据第二节点的请求进行丢包统计、处理和/或报告。具体的，本公开对第二信息中包含的具体内容不做限定。
步骤S802：第一节点接收到所述第二节点发送的第二信息，响应于接收到所述第二节点发送的第二信息，向所述第二节点发送所述第一信息，所述第二信息中包括用于丢包统计的请求信息。
在一些实施方式中，第一节点向第二节点发送丢包或者与丢包相关的信息，除了依据本步骤中接收到的第二信息的情况外，作为本实施例的一种可实现方式，还可以根据预设协议约定，第一节点向第二节点发送丢包或者与丢包相关的信息；作为本实施例的另一种可实现方式，还可以根据操作维护管理(Operation Administration and Maintenance，OAM)配置，第一节点向第二节点发送丢包或者与丢包相关的信息，具体的，本申请实施例不做具体限定。
在本公开实施例中，“响应于”与“根据”或“考虑”具有相同的含义。
步骤S803：接收所述第一节点响应于接收到所述第二设备发送的所述第二信息，发送的所述第一信息。
所述第一信息中包括丢包或者与丢包相关的信息。有关第一信息的说明，可参见上述实施例，故在此不再赘述。
对第一节点相对应的，第二节点接收所述第一节点发送的第一信息，对第一信息进行解析，得到第一信息中包括的丢包或者与丢包相关的信息，并根据丢包或者与丢包相关的信息进行流量和/或费用统计。
综上所述，第一节点响应于接收到所述第二节点发送的第二信息，所述第二信息中包括用于丢包统计的请求信息，向所述第二节点发送丢包统计相关的第一信息，第二节点获取第一信息中包括的丢包或者与丢包相关的信息，辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图9为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图9所示，该丢包处理方法可包括如下步骤：
步骤S901：第二节点通过用户平面向所述第一节点发送所述第二信息。
该第二信息用于指示第一节点发送丢包统计，也就是说，第二节点作为丢包统计的控制方，指示第一节点是否发送丢包统计或何时发送丢包统计等控制。具体的，本公开对第二信息中包含的具体内容不做限定。
通过用户平面向所述第一节点发送所述第二信息，具体可以但不局限于为通过用户平面的用户数据向所述第一节点发送第二信息。
在无线网络的分离架构中，gNB-CU-UP负责GTP-U、SDAP和PDCP用户平面的功能。
在一些实施例中，所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
在一些实施例中，所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
在一些实施例中，所述第一节点为辅节点，所述第二节点为主节点。
应当理解，以上仅为示例，关于第一节点、所述第二节点为以上至少一种，本公开实施例对第一节点、第二节点不限于此。
步骤S902：第一节点接收到所述第二节点通过用户平面发送的第二信息。
对第二节点相对应的，在第一节点接收第二信息时，同样基于用户平面进行接收，有关用户平面的解释，可参见步骤S801的详细说明，故在此不再赘述。
综上所述，第一节点响应于通过用户平面接收到所述第二节点通过用户平面发送的第二信息，所述第二信息中包括用于丢包统计的请求信息，向所述第二节点发送丢包统计相关的第一信息，第二节点获取第一信息中包括的丢包或者与丢包相关的信息，辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图10为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图10所示，该丢包处理方法可包括如下步骤：
步骤S1001：第二节点通过控制平面向所述第二节点发送所述第二信息。
该第二信息用于指示第一节点发送丢包统计，也就是说，第二节点作为丢包统计的请求方，请求第一节点是否发送丢包统计或何时发送丢包统计等控制，第一节点根据第二节点的请求进行丢包统计、处理和/或报告。具体的，本公开对第二信息中包含的具体内容不做限定。
通过控制平面向所述第一节点发送所述第二信息，具体可以但不局限于为通过控制平面的信令向所述第一节点发送第二信息。
在一些实例中，所述第一节点是gNB-DU，所述第二节点是gNB-CU或gNB-CU-CP，所述第二消息是F1AP消息，所述F1AP消息可以是UE上下文请求消息、UE上下文修改请求消息或其他F1AP消息；
在一些实例中，所述第一节点是gNB-CU-UP，第二节点是gNB-CU-CP，所述第二消息是E1AP消息，所述E1AP消息可以是承载上下文请求消息、承载上下文修改请求消息或其他E1AP消息；
在一些实例中，所述第一节点是主节点，所述第二节点的辅节点，所述第二消息是XnAP消息，所述XnAP消息是SN添加请求消息、SN修改请求消息或其他XnAP消息；
在一些实例中，所述第一节点是目标gNB，所述第二节点是源gNB，所述第二消息是XnAP消息，所述XnAP消息是切换请求消息、检索UE上下文反馈消息或其他XnAP消息；
在一些实例中，所述第一节点是gNB、gNB-CU、gNB-CU-CP或gNB-CU-UP，所述第二节点是核心网节点，所述第二消息是NGAP消息，所述NGAP消息可以是UE上下文建立请求消息、UE上下文修改请求消息、PDU会话资源建立请求消息、PDU会话资源修改请求消息或其他NGAP消息。
以上示例是举例性说明，本申请实施例对第一节点、第二节点及第二信息的具体内容不做限定。
步骤S1002：第一节点接收到所述第二节点通过控制平面发送的第二信息。
对第二节点相对应的，在第一节点接收第二节点通过控制平面发送的第二信息时，同样基于控制平面进行接收，有关控制平面的解释，可参见步骤S901的详细说明，故在此不再赘述。
综上所述，第一节点响应于通过控制平面接收到所述第二节点通过控制平面发送的第二信息，所述第二信息中包括用于丢包统计的请求信息，向所述第二节点发送丢包统计相关的第一信息，第二节点获取第一信息中包括的丢包或者与丢包相关的信息，辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图11为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图11所示，该丢包处理方法可包括如下步骤：
步骤S1101：第二节点通过GTP-U向所述第一节点发送所述第二信息，所述GTP-U PDU的包头中包括的与丢包相关的请求信息。
本实施例用于通过用户平面向所述第一节点发送所述第二信息的过程中。
在一些实例中，第二节点将与丢包相关的请求信息通过GTP-U发送至第一节点，在一些实施例中，所述用于丢包统计请求的信息包括以下至少一个：
丢包统计指示，例如，可以在GTP-U包头中携带丢包报告查询Discard Report polling，以 指示需要进行与丢包相关的操作。
丢包上报的承载标识，例如是DRB、QFI、PDU session ID、PDU set ID，用于指示第一节点与丢包相关的操作的粒度。
丢包上报的门限，所述门限可以是包大小或丢包率，满足所述门限后，第一节点执行上报；
丢包上报的时间，所述时间可以是具体的时间段和/或上报周期，用于指示第一节点何时进行丢包相关的上报；
丢包上报的方式，包括用户平面(User Plane，UP)上报、控制平面(Control Plane，CP)上报、退回丢包和/或丢包大小指示等，所述上报方式用于指示第一节点通过何种方式进行与丢包相关的上报。
以上为关于丢包统计请求的信息的举例说明，本公开实施例对丢包统计请求的信息不做限定。
步骤S1102：第一节点接收所述第二节点发送的GTP-U PDU，根据所述GTP-U PDU，获取所述GTP-U包头中包括的与丢包相关的请求信息。
对第二节点相对应的，在第一节点接收GTP-U PDU时，对GTP-U PDU进行解析，获取GTP-U包头中包括的与丢包相关的请求信息，并基于与丢包相关的请求信息执行第一信息的上报。
综上所述，第一节点根据第二节点发送的GTP-U PDU，获取GTP-U包头中包括的与丢包相关的请求信息，根据该与丢包相关的请求信息向所述第二节点发送丢包统计相关的第一信息，第二节点获取第一信息中包括的丢包或者与丢包相关的信息，辅助核心网进行流量和/或费用统计，避免与终端设备侧的流量和/或费用统计不一致问题的发生。
本公开实施例提供了另一种丢包处理方法，图12为本公开实施例提供的另一种丢包处理方法的流程示意图，该丢包处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。
如图12所示，该丢包处理方法可包括如下步骤：
步骤S1201：响应于确定进行与丢包相关的操作，向所述第二节点发送所述第一信息。
如果第一节点确定需要进行与丢包相关的操作，执行与丢包相关的操作。为了与第二节点的统计结果的统一，第一节点向第二节点发送与丢包相关的第一信息。
在一些实施例中，所述与丢包相关的操作为以下任一个：监控丢包、上报与丢包相关的信息、退回丢包(即发送退回的数据包)。对与丢包相关的操作不做限定。
与上述图2至图12实施例提供的丢包处理方法相对应，本公开还提供一种丢包处理装置，由于本公开实施例提供丢包处理装置与上述图2至图12实施例提供的丢包处理方法相对应，因此在丢包处理方法的实施方式也适用于本公开实施例提供的丢包处理装置，在本公开实施例中不再详细描述。
图13为本公开实施例所提供的一种丢包处理装置的结构示意图。所述装置设置于第一节点，所述装置包括：
发送模块1301，用于向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
作为本公开实施例的一种可能实现方式，所述丢包或者与丢包相关的信息用于辅助核心网进行费用统计。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于：
通过控制平面向所述第二节点发送所述第一信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第一信息为F1AP消息；
所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1AP消息；
所述第一节点为辅节点，所述第二节点为主节点，所述第一信息为XnAP消息；
所述第一节点是gNB、gNB-CU、gNB-CU-CP、gNB-CU-UP，所述第二节为核心网节点，所述第一信息为NGAP消息。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于：
通过用户平面向所述第二节点发送所述第一信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
根所述第一节点为辅节点，所述第二节点为主节点。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于：
通过GTP-U将丢包发送给所述第二节点，所述GTP-U的包头中包括丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-U PDU是否为丢包。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于包括：
通过GTP-U将所述丢包相关的信息发送给所述第二节点，所述GTP-U的包头中包括所述与丢包相关的信息。
作为本公开实施例的一种可能实现方式，所述与丢包相关的信息包括以下至少一个：
丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于：
响应于接收到所述第二节点发送的第二信息，向所述第二节点发送所述第一信息，所述第二信息中包括用于丢包统计的请求信息。
作为本公开实施例的一种可能实现方式，还包括：
接收模块1302，用于接收到所述第二节点通过用户平面发送的第二信息。
作为本公开实施例的一种可能实现方式，所述接收模块1302还用于：
接收所述第二节点发送的GTP-U PDU；
根据所述GTP-U PDU，获取所述GTP-U包头中包括的与丢包相关的请求信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
根所述第一节点为辅节点，所述第二节点为主节点。
作为本公开实施例的一种可能实现方式，所述接收模块1302还用于：
接收到所述第二节点通过控制平面发送的第二信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第一信息为F1AP消息；
所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1AP消息；
所述第一节点为主节点，所述第二节点为辅节点，所述第一信息为XnAP消息；
所述第一节点是gNB、gNB-CU、gNB-CU-CP或gNB-CU-UP，所述第二节为核心网节点，所述第一信息为NGAP消息；
所述第一节点为目标gNB，所述第二节点为源gNB，所述第二信息为XnAP消息。
作为本公开实施例的一种可能实现方式，所述用于丢包统计请求的信息包括以下至少一个：
丢包统计指示、丢包上报的承载标识、丢包上报的门限、丢包上报的时间、丢包上报的方式。
作为本公开实施例的一种可能实现方式，所述发送模块1301还用于：
响应于确定进行与丢包相关的操作，向所述第二节点发送所述第一信息。
作为本公开实施例的一种可能实现方式，所述与丢包相关的操作为以下任一个：
监控丢包、上报与丢包相关的信息、退回丢包。
图14为本公开实施例所提供的一种丢包处理装置，其特征在于，所述装置应于第二节点，所述装置包括：
接收模块1401，用于接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
作为本公开实施例的一种可能实现方式，所述丢包或者与丢包相关的信息用于辅助核心网进行费用统计。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点通过控制平面发送所述的第一信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第一信息为F1AP消息；
所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1AP消息；
所述第一节点为辅节点，所述第二节点为主节点，所述第一信息为XnAP消息；
所述第一节点是gNB、gNB-CU、gNB-CU-CP、gNB-CU-UP，所述第二节为核心网节点，所述第一信息为NGAP消息。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点通过用户平面发送所述的第一信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
根所述第一节点为辅节点，所述第二节点为主节点。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点发送的GTP-U PDU，
根据所述GTP-U PDU，获取所述GTP-U包头中包括的丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-U PDU是否为丢包。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点发送的GTP-U PDU，
根据所述GTP-U PDU，获取所述GTP-U包头中包括的所述与丢包相关的信息。
作为本公开实施例的一种可能实现方式，所述与丢包相关的信息包括以下至少一个：
丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点响应于接收到所述第二设备发送的所述第二信息，向所述第二节点发送的所述第一信息，所述第二信息中包括用于丢包统计的请求信息。
作为本公开实施例的一种可能实现方式，所述装置还包括：
发送模块1402，用于向所述第一节点发送所述第二信息。
作为本公开实施例的一种可能实现方式，所述发送模块1402还用于：
通过用户平面向所述第一节点发送所述第二信息。
作为本公开实施例的一种可能实现方式，所述发送模块1402还用于：
通过GTP-U向所述第一节点发送所述第二信息，所述GTP-U的包头中包括的与丢包相关的请求信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
根所述第一节点为辅节点，所述第二节点为主节点。
作为本公开实施例的一种可能实现方式，所述发送模块1402还用于：
通过控制平面向所述第一节点发送所述第二信息。
作为本公开实施例的一种可能实现方式，所述第一节点、所述第二节点、所述第二信息为以下至少一种：
所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第二信息为F1AP 消息；
所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第二信息为E1AP消息；
所述第一节点为主节点，所述第二节点为辅节点，所述第二信息为XnAP消息；
所述第一节点是gNB、gNB-CU、gNB-CU-CP或gNB-CU-UP，所述第二节为核心网节点，所述第二信息为NGAP消息；
所述第一节点为目标gNB，所述第二节点为源gNB，所述第二信息为XnAP消息。
作为本公开实施例的一种可能实现方式，所述用于丢包统计请求的信息包括以下至少一个：
丢包统计指示、丢包上报的承载标识、丢包上报的门限、丢包上报的时间、丢包上报的方式。
作为本公开实施例的一种可能实现方式，所述接收模块1401还用于：
接收所述第一节点响应于确定进行与丢包相关的操作，向所述第二节点发送的所述第一信息。
作为本公开实施例的一种可能实现方式，所述与丢包相关的操作为以下任一个：
监控丢包、上报与丢包相关的信息、退回丢包。
请参见图15，图15为本公开实施例提供的另一种通信装置的结构示意图。图15中，该通信装置1500可以是网络设备，也可以是终端设备，也可以是支持网络设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
通信装置1500可以包括一个或多个处理器1501。处理器1501可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对通信装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，通信装置1500中还可以包括一个或多个存储器1502，其上可以存有计算机程序1504，处理器1501执行所述计算机程序1504，以使得通信装置1500执行上述方法实施例中描述的方法。可选的，所述存储器1502中还可以存储有数据。通信装置1500和存储器1502可以单独设置，也可以集成在一起。
可选的，通信装置1500还可以包括收发器1505、天线1506。收发器1505可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器1505可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，通信装置1500中还可以包括一个或多个接口电路1507。接口电路1507用于接收代码指令并传输至处理器1501。处理器1501运行所述代码指令以使通信装置1500执行上述方法实施例中描述的方法。
通信装置1500为第一节点：收发器1505用于执行图2中的步骤201等步骤。
通信装置1500为网络设备：收发器1505用于执行图4中的步骤402等步骤。
在一种实现方式中，处理器1501中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，处理器1501可以存有计算机程序1503，计算机程序1503在处理器1501上运行，可使得通信装置1500执行上述方法实施例中描述的方法。计算机程序1503可能固化在处理器1501中，该种情况下，处理器1501可能由硬件实现。
在一种实现方式中，通信装置1500可以包括电路，所述电路可以实现前述方法实施例中发送或接收或者通信的功能。本公开中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的通信装置可以是网络设备，或者终端设备，但本公开中描述的通信装置的范围并不限于此，而且通信装置的结构可以不受图15的限制。通信装置可以是独立的设备或者可以是较大设备的一部分。例如所述通信装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、网络设备、云设备、人工智能设备等等；
(6)其他等等。
对于通信装置可以是芯片或芯片系统的情况，可参见图16所示的芯片的结构示意图。图16所示的芯片1600包括处理器1601和接口1603。其中，处理器1601的数量可以是一个或多个，接口1603的数量可以是多个。
对于芯片用于实现本公开实施例中第一节点的功能的情况：
接口1603，用于执行图2中的步骤201；图3中的步骤301；图4中的步骤401；图5中的步骤501等。
对于芯片用于实现本公开实施例中第二节点的功能的情况：
接口1603，用于执行图4中的步骤402，图5中的步骤502等。
可选的，芯片1600还包括存储器1602，存储器1602用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本公开实施例列出的各种说明性逻辑块(illustrative logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现所述的功能，但这种实现不应被理解为超出本公开实施例保护的范围。
本公开还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本公开还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行所述计算机程序时，全部或部分地产生按照本公开实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本公开中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本公开实施例的范围，也表示先后顺序。
本公开中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本公开不做限制。在本公开实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
进一步可以理解的是，本公开中“多个”是指两个或两个以上，其它量词与之类似。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。
进一步可以理解的是，本公开中涉及到的“响应于”、“如果”、“如若”等词语的含义 取决于语境以及实际使用的场景，如在此所使用的词语“如若”可以被解释成为“在……时”或“当……时”。
本公开中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本公开并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本公开中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。

Claims (41)

  1. 一种丢包处理方法，其特征在于，所述方法应用于第一节点，所述方法包括：
    向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述丢包或者与丢包相关的信息用于辅助核心网进行费用统计。
  3. 根据权利要求1所述的方法，其特征在于，所述向第二节点发送第一信息包括：
    通过控制平面向所述第二节点发送所述第一信息。
  4. 根据权利要求3所述的方法，其特征在于，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
    所述第一节点为基站-分布单元gNB-DU，所述第二节点为基站-中央单元gNB-CU或基站-基站-中央单元-控制平面gNB-CU-CP，所述第一信息为F1应用协议F1AP消息；
    所述第一节点为基站-中央单元-用户平面gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1应用协议E1AP消息；
    所述第一节点为辅节点，所述第二节点为主节点，所述第一信息为Xn应用协议XnAP消息；
    所述第一节点是NR系统中的下一代基站gNB、gNB-CU、gNB-CU-CP、或gNB-CU-UP，所述第二节点为核心网节点，所述第一信息为NG应用协议NGAP消息。
  5. 根据权利要求1所述的方法，其特征在于，向第二节点发送第一信息包括：
    通过用户平面向所述第二节点发送所述第一信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第一节点、所述第二节点为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
    所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
    所述第一节点为辅节点，所述第二节点为主节点。
  7. 根据权利要求6所述的方法，其特征在于，通过用户平面向所述第二节点发送所述第一信息包括：
    通过GPRS隧道协议GTP-U将丢包发送给所述第二节点，所述GTP-U的包头中包括丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-U协议数据单元PDU是否为丢包。
  8. 根据权利要求6所述的方法，其特征在于，通过用户平面向所述第二节点发送所述第一信息包括：
    通过GTP-U将所述丢包相关的信息发送给所述第二节点，所述GTP-U的包头中包括所述与丢包相关的信息。
  9. 根据权利要求1-8中任一项所述的方法，其特征在于，所述与丢包相关的信息包括以下至少一个：
    丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。
  10. 根据权利要求1所述的方法，其特征在于，所述向第二节点发送第一信息包括：
    响应于接收到所述第二节点发送的第二信息，向所述第二节点发送所述第一信息，所述第二信息中包括用于丢包统计的请求信息。
  11. 根据权利要求10所述的方法，其特征在于，所述接收到所述第二节点向所述第一节点发送的第二信息包括：
    接收到所述第二节点通过用户平面发送的第二信息。
  12. 根据权利要求11所述的方法，其特征在于，接收到所述第二节点通过用户平面发送的第二信息包括：
    接收所述第二节点发送的GTP-U PDU；
    根据所述GTP-U PDU，获取所述GTP-U包头中包括的与丢包统计请求信息。
  13. 根据权利要求12所述的方法，其特征在于，所述第一节点、所述第二节点为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
    所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
    根所述第一节点为辅节点，所述第二节点为主节点。
  14. 根据权利要求10所述的方法，其特征在于，所述接收到所述第二节点发送的第二信息包括：
    接收到所述第二节点通过控制平面发送的第二信息。
  15. 根据权利要求14所述的方法，其特征在于，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第一信息为F1AP消息；
    所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1AP消息；
    所述第一节点为主节点，所述第二节点为辅节点，所述第一信息为XnAP消息；
    所述第一节点是gNB、gNB-CU、gNB-CU-CP或gNB-CU-UP，所述第二节为核心网节点，所述第一信息为NGAP消息；
    所述第一节点为目标gNB，所述第二节点为源gNB，所述第二信息为XnAP消息。
  16. 根据权利要求12-15中任一项所述的方法，其特征在于，所述用于丢包统计请求的信息包括以下至少一个：
    丢包统计指示、丢包上报的承载标识、丢包上报的门限、丢包上报的时间、丢包上报的方式。
  17. 根据权利要求9所述的方法，其特征在于，所述向第二节点发送第一消息包括：
    响应于确定进行与丢包相关的操作，向所述第二节点发送所述第一信息。
  18. 根据权利要求17所述的方法，其特征在于，所述与丢包相关的操作为以下任一个：
    监控丢包、上报与丢包相关的信息、退回丢包。
  19. 一种丢包处理方法，其特征在于，所述方法应于第二节点，所述方法包括：
    接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
  20. 根据权利要求19所述的方法，其特征在于，所述丢包或者与丢包相关的信息用于辅助核心网进行费用统计。
  21. 根据权利要求19所述的方法，其特征在于，所述接收第一节点发送的第一信息包括：
    接收所述第一节点通过控制平面发送所述的第一信息。
  22. 根据权利要求21所述的方法，其特征在于，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
    所述第一节点为基站-分布单元gNB-DU，所述第二节点为基站-中央单元gNB-CU或基站-基站-中央单元-控制平面gNB-CU-CP，所述第一信息为F1应用协议F1AP消息；
    所述第一节点为基站-中央单元-用户平面gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第一信息为E1应用协议E1AP消息；
    所述第一节点为辅节点，所述第二节点为主节点，所述第一信息为Xn应用协议XnAP消息；
    所述第一节点是NR系统中的下一代基站gNB、gNB-CU、gNB-CU-CP、gNB-CU-UP，所述第二节为核心网节点，所述第一信息为NG应用协议NGAP消息。
  23. 根据权利要求19所述的方法，其特征在于，所述接收第一节点发送的第一信息包括：
    接收所述第一节点通过用户平面发送所述的第一信息。
  24. 根据权利要求23所述的方法，其特征在于，所述第一节点、所述第二节点为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
    所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
    根所述第一节点为辅节点，所述第二节点为主节点。
  25. 根据权利要求24所述的方法，其特征在于，所述接收所述第一节点通过用户平面发送所述的第一信息包括：
    接收所述第一节点发送的GPRS隧道协议GTP-U协议数据单元PDU，
    根据所述GTP-U PDU，获取所述GTP-U包头中包括的丢包指示信息，所述丢包指示信息用于指示所述第二节点识别所述GTP-U PDU是否为丢包。
  26. 根据权利要求24所述的方法，其特征在于，所述接收所述第一节点通过用户平面发送所述的第一信息包括：
    接收所述第一节点发送的GTP-U PDU，
    根据所述GTP-U PDU，获取所述GTP-U包头中包括的所述与丢包相关的信息。
  27. 根据权利要求19-26中任一项所述的方法，其特征在于，所述与丢包相关的信息包括以下至少一个：
    丢包对应的承载标识、丢包的时间、丢包的数据量、丢包率、丢包的原因、上报的原因。
  28. 根据权利要求19所述的方法，其特征在于，所述接收第一节点发送的第一信息包括：
    接收所述第一节点响应于接收到所述第二设备发送的所述第二信息，向所述第二节点发送的所述第一信息，所述第二信息中包括用于丢包统计的请求信息。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    向所述第一节点发送所述第二信息。
  30. 根据权利要求29所述的方法，其特征在于，所述向所述第一节点发送所述第二信息包括：
    通过用户平面向所述第一节点发送所述第二信息。
  31. 根据权利要求30所述的方法，其特征在于，所述通过用户平面向所述第一节点发送所述第二信息包括：
    通过GTP-U向所述第一节点发送所述第二信息，所述GTP-U的包头中包括的与丢包相关的请求信息。
  32. 根据权利要求31所述的方法，其特征在于，所述第一节点、所述第二节点为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-UP；
    所述第一节点为gNB、gNB-CU或gNB-CU-UP，所述第二节点为UPF；
    根所述第一节点为辅节点，所述第二节点为主节点。
  33. 根据权利要求29所述的方法，其特征在于，所述向所述第一节点发送所述第二信息包括：
    通过控制平面向所述第一节点发送所述第二信息。
  34. 根据权利要求33所述的方法，其特征在于，所述第一节点、所述第二节点、所述第一信息为以下至少一种：
    所述第一节点为gNB-DU，所述第二节点为gNB-CU或gNB-CU-CP，所述第二信息为F1AP消息；
    所述第一节点为gNB-CU-UP，所述第二节点为gNB-CU-CP，所述第二信息为E1AP消息；
    所述第一节点为主节点，所述第二节点为辅节点，所述第二信息为XnAP消息；
    所述第一节点是gNB、gNB-CU、gNB-CU-CP或gNB-CU-UP，所述第二节为核心网节点，所述第二信息为NGAP消息；
    所述第一节点为目标gNB，所述第二节点为源gNB，所述第二信息为XnAP消息。
  35. 根据权利要求28-34中任一项所述的方法，其特征在于，所述用于丢包统计请求的信息包括以下至少一个：
    丢包统计指示、丢包上报的承载标识、丢包上报的门限、丢包上报的时间、丢包上报的方式。
  36. 根据权利要求19所述的方法，其特征在于，所述接收第一节点发送的第一信息包括：
    接收所述第一节点响应于确定进行与丢包相关的操作，向所述第二节点发送的所述第一信息。
  37. 根据权利要求36所述的方法，其特征在于，所述与丢包相关的操作为以下任一个：
    监控丢包、上报与丢包相关的信息、退回丢包。
  38. 一种丢包处理装置，其特征在于，所述装置应用于第一节点，所述装置包括：
    发送模块，用于向第二节点发送第一信息，所述第一信息中包括丢包或者与丢包相关的信息。
  39. 一种丢包处理装置，其特征在于，所述装置应于第二节点，所述装置包括：
    接收模块，用于接收第一节点发送的第一信息，所述第一消息中包括丢包或者与丢包相关的信息。
  40. 一种通信装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至18中任一项所述的方法，或者执行如权利要求19至37中任一项所述的方法。
  41. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，使如权利要求1至18中任一项所述的方法，或者执行如权利要求19至37中任一项所述的方法。
PCT/CN2022/122943 2022-09-29 2022-09-29 一种丢包处理方法及装置 WO2024065550A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/122943 WO2024065550A1 (zh) 2022-09-29 2022-09-29 一种丢包处理方法及装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/122943 WO2024065550A1 (zh) 2022-09-29 2022-09-29 一种丢包处理方法及装置

Publications (1)

Publication Number Publication Date
WO2024065550A1 true WO2024065550A1 (zh) 2024-04-04

Family

ID=90475511

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/122943 WO2024065550A1 (zh) 2022-09-29 2022-09-29 一种丢包处理方法及装置

Country Status (1)

Country Link
WO (1) WO2024065550A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102204164A (zh) * 2011-05-24 2011-09-28 华为技术有限公司 网络丢包信息报告方法及装置
CN103684923A (zh) * 2013-12-24 2014-03-26 华为技术有限公司 一种丢包测量的方法及网络设备
CN111757553A (zh) * 2019-03-28 2020-10-09 北京三星通信技术研究有限公司 一种提高冗余分组数据会话性能的方法和设备
US20210185755A1 (en) * 2018-04-02 2021-06-17 Lg Electronics Inc. Method and apparatus for discarding buffered data while keeping connection in cp-up separation
WO2022052129A1 (zh) * 2020-09-14 2022-03-17 华为技术有限公司 一种可靠性测量方法、装置及系统
WO2022140959A1 (zh) * 2020-12-28 2022-07-07 华为技术有限公司 一种通信方法、装置及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102204164A (zh) * 2011-05-24 2011-09-28 华为技术有限公司 网络丢包信息报告方法及装置
CN103684923A (zh) * 2013-12-24 2014-03-26 华为技术有限公司 一种丢包测量的方法及网络设备
US20210185755A1 (en) * 2018-04-02 2021-06-17 Lg Electronics Inc. Method and apparatus for discarding buffered data while keeping connection in cp-up separation
CN111757553A (zh) * 2019-03-28 2020-10-09 北京三星通信技术研究有限公司 一种提高冗余分组数据会话性能的方法和设备
WO2022052129A1 (zh) * 2020-09-14 2022-03-17 华为技术有限公司 一种可靠性测量方法、装置及系统
WO2022140959A1 (zh) * 2020-12-28 2022-07-07 华为技术有限公司 一种通信方法、装置及系统

Similar Documents

Publication Publication Date Title
US20210367683A1 (en) Delay measurement method, network device, and terminal device
EP4336953A1 (en) Access failure processing method and apparatus, terminal device and storage medium
US11259362B2 (en) Method for repeatedly transmitting data and device
WO2024065842A1 (zh) 路径添加方法和装置
WO2024092523A1 (zh) 侧行链路定位消息的发送方法、接收方法及其装置
WO2024065127A1 (zh) 控制中继设备信息发送的方法及其装置
WO2024065550A1 (zh) 一种丢包处理方法及装置
WO2024092661A1 (zh) 模型的标识方法及装置
WO2024092828A1 (zh) 一种连接建立的方法及装置
WO2022266861A1 (zh) 寻呼处理方法、通信装置和存储介质
WO2024027560A1 (zh) 无线承载的处理方法及装置
WO2023010429A1 (zh) 一种带宽部分的同步方法及其装置
WO2024031373A1 (zh) 一种确定触发连续lbt失败的方法及装置
WO2023220941A1 (zh) 一种数据前转信息的传输方法及其装置
WO2024031272A1 (zh) 一种上报方法、装置、设备及存储介质
WO2024087074A1 (zh) 传输配置方法、装置、设备及存储介质
WO2024065844A1 (zh) 一种路径切换能力的交互方法及其装置
WO2024065128A1 (zh) 一种控制终端设备连接的方法及其装置
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
WO2024065441A1 (zh) 一种中继通信配置方法及装置
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2023193273A1 (zh) 一种控制源辅节点释放的方法及装置
WO2024092558A1 (zh) 一种测量方法、装置、设备及存储介质
WO2024092622A1 (zh) 一种lbt失败次数的计数方法及装置
WO2024040411A1 (zh) 一种实现多接入的方法及其装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22960185

Country of ref document: EP

Kind code of ref document: A1