A reliability measurement method, apparatus and system

Abstract

The application provides a reliability measurement method, device and system, which can realize measurement of end-to-end reliability. An access network device measures reliability between the access network device and a user equipment (UE); the access network device sends the reliability between the access network device and the UE to a core network device; the core network device determines reliability between the access network device and the core network device; and the core network device determines reliability between the UE and the core network device according to the reliability between the access network device and the UE and the reliability between the access network device and the core network device.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to reliability measurement methods, apparatus and systems in wireless communication systems. Background Technology

[0002] In 5G (fifth generation) or new radio (NR) mobile communication systems, for services requiring high reliability, such as those demanding a 99.999% success rate in data packet delivery, the network needs to guarantee the reliability of data packet transmission. The network also needs to collect reliability metrics to understand its performance indicators and perform targeted network optimization. Reliability can be defined as the probability that the sending end successfully transmits X bytes of data packets to the receiving end within a certain latency. Reliability is related to factors such as data packet size, latency, and packet loss rate.

[0003] Existing technologies only provide methods for measuring end-to-end delay of data packets. How to measure or calculate the end-to-end reliability between different network elements in a wireless network has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a reliability measurement method, apparatus, and system that can measure end-to-end reliability.

[0005] Firstly, a method for measuring reliability is provided, including:

[0006] The access network device measures the reliability between the access network device and the user equipment (UE).

[0007] The access network device sends the reliability information between the access network device and the UE to the core network device.

[0008] In conjunction with the first aspect, in a first possible implementation, before measuring the reliability between the access network device and the user equipment (UE), the access network device receives first indication information from the core network device, the first indication information indicating that a reliability measurement should be performed.

[0009] In conjunction with the first aspect or the first possible implementation of the first aspect, in the second possible implementation, the method further includes the access network device receiving second indication information from the core network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0010] In combination with any of the aforementioned possible implementations, in a third possible implementation, the access network device includes a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU).

[0011] The access network device measures the reliability between the access network device and the user equipment (UE) including:

[0012] CU-CP sends the first reliability measurement indication information to CU-UP;

[0013] CU-CP sends a second reliability measurement indication message to DU;

[0014] CU-CP sends a third reliability measurement indication message to the UE;

[0015] CU-UP measures the reliability of CU-UP;

[0016] CU-UP measures the reliability of the interface between CU-UP and DU;

[0017] The reliability of DU measurement;

[0018] The DU sends the measured reliability of the DU to the CU-UP;

[0019] The CU-UP receives the UE's reliability measurements.

[0020] Based on the reliability of the CU-UP, the reliability of the interface between the CU-UP and the DU, the reliability of the DU, and the reliability of the UE, the CU-UP calculates the reliability between the access network device and the UE.

[0021] In a fourth possible implementation, in conjunction with the first aspect or the first or second possible implementation of the first aspect, the access network device includes a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU).

[0022] The access network device measures the reliability between the access network device and the user equipment (UE) including:

[0023] CU-CP sends the first packet loss rate or packet loss count measurement indication information to CU-UP;

[0024] The CU-CP sends a second packet loss rate or packet loss number measurement indication to the DU;

[0025] The CU-CP sends a third packet loss rate or packet loss number measurement indication information to the UE;

[0026] CU-UP measures the number of lost packets or the packet loss rate of the CU-UP itself;

[0027] CU-UP measures the number of lost packets or the packet loss rate at the interface between CU-UP and DU;

[0028] DU measures the number of lost packets or the packet loss rate.

[0029] The DU sends the measured number of lost packets or packet loss rate to the CU-UP;

[0030] The CU-UP receives the number of lost packets or the packet loss rate of the UE as measured by the UE.

[0031] The CU-UP calculates the reliability between the access network device and the UE based on the number or rate of packet loss of the CU-UP itself, the number or rate of packet loss of the interface between the CU-UP and the DU, the number or rate of packet loss of the DU, and the number or rate of packet loss of the UE.

[0032] In conjunction with the first aspect or the first or second possible implementation of the first aspect, in the fifth possible implementation, the access network device measuring the reliability between the access network device and the user equipment (UE) includes: the access network device calculating the transmission delay of data packets between the access network device and the UE, and calculating the reliability between the access network device and the UE based on the transmission delay.

[0033] Secondly, a method for measuring reliability is provided, including:

[0034] User equipment (UE) measures the reliability of the UE;

[0035] The UE sends its reliability information to the access network device.

[0036] In conjunction with the second aspect, in a first possible implementation, the method further includes: before the UE measures the reliability of the UE, the UE receives reliability measurement indication information from the access network device, the reliability measurement indication information indicating that a reliability measurement should be performed.

[0037] In conjunction with the second aspect or the first possible implementation of the second aspect, in the second possible implementation, the method further includes the UE receiving a measurement period from the access network device.

[0038] In conjunction with the second possible implementation of the second aspect, in the third possible implementation, the UE measuring the reliability of the UE includes: the UE measuring the reliability of the UE within the measurement period.

[0039] Thirdly, a method for measuring reliability is provided, including:

[0040] The user equipment (UE) measures the packet loss rate or the number of lost packets.

[0041] The UE sends its packet loss rate or number of lost packets to the access network device.

[0042] In conjunction with the third aspect, in the first possible implementation, the method further includes:

[0043] Before the UE measures the packet loss rate or number of packets lost, the UE receives packet loss rate or number of packets lost measurement indication information from the access network device, which indicates that packet loss rate or number of packets lost measurement should be performed.

[0044] In conjunction with the third aspect or the first possible implementation of the third aspect, in the second possible implementation, the method further includes the UE receiving a measurement period from the access network device.

[0045] In conjunction with the second possible implementation of the third aspect, in the third possible implementation, the UE measuring the packet loss rate or number of lost packets includes: the UE measuring the reliability of the UE during the measurement period.

[0046] Fourthly, a method for measuring reliability is provided, including:

[0047] The core network equipment receives the reliability information between the access network equipment and the user equipment (UE) from the access network equipment.

[0048] The core network equipment determines the reliability between the access network equipment and the core network equipment;

[0049] The core network device determines the reliability between the UE and the core network device based on the reliability between the access network device and the UE, and the reliability between the access network device and the core network device.

[0050] In conjunction with the fourth aspect, in a first possible implementation, the method further includes the core network device sending first indication information to the access network device, wherein the first indication information indicates that a reliability measurement is to be performed.

[0051] In conjunction with the fourth aspect or the first possible implementation of the fourth aspect, in the second possible implementation, the method further includes the core network device sending second indication information to the access network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0052] Fifthly, an access network device is provided, comprising:

[0053] The measurement unit is used to measure the reliability between the access network device and the user equipment (UE).

[0054] The transceiver unit is used to send the reliability information between the access network device and the UE to the core network device.

[0055] In conjunction with the fifth aspect, in a first possible implementation, the transceiver unit is further configured to receive first indication information from the core network device before measuring the reliability between the access network device and the UE, the first indication information indicating that a reliability measurement should be performed.

[0056] In conjunction with the fifth aspect, or the first possible implementation of the fifth aspect, in the second possible implementation, the transceiver unit is further configured to receive second indication information from the core network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0057] In a third possible implementation, in conjunction with the fifth aspect or the first or second implementation of the fifth aspect, the measurement unit for measuring the reliability between the access network device and the user equipment (UE) includes: the measurement unit is used to count the transmission delay of data packets between the access network device and the UE, and to calculate the reliability between the access network device and the UE based on the transmission delay.

[0058] The aforementioned access network equipment can also be implemented using a processor and a transceiver (or transceiver circuit). The processor can implement the function of the measurement unit, and the transceiver (or transceiver circuit) can implement the function of the transceiver unit.

[0059] Sixthly, an access network device is provided, including a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU), wherein,

[0060] The CU-CP is used to send a first reliability measurement indication information to the CU-UP, a second reliability measurement indication information to the DU, and a third reliability measurement indication information to the user equipment (UE).

[0061] The CU-UP is used to measure the reliability of the CU-UP and the reliability of the interface between the CU-UP and the DU;

[0062] The DU is also used to measure the reliability of the DU and send the measured reliability of the DU to the CU-UP;

[0063] The CU-UP is also used to receive the reliability of the UE measured by the UE, calculate the reliability between the access network device and the UE based on the reliability of the CU-UP, the reliability of the interface between the CU-UP and the DU, the reliability of the DU and the reliability of the UE, and report the calculated reliability between the access network device and the UE to the core network device.

[0064] In a seventh aspect, an access network device is provided, comprising a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU), wherein,

[0065] The CU-CP is used to send a first packet loss rate or packet loss number measurement indication information to the CU-UP, a second packet loss rate or packet loss number measurement indication information to the DU, and a third packet loss rate or packet loss number measurement indication information to the user equipment UE.

[0066] The CU-UP is used to measure the number of packet losses or the packet loss rate of the CU-UP, and to measure the number of packet losses or the packet loss rate of the interface between the CU-UP and the DU.

[0067] The DU is used to measure the number of lost packets or the packet loss rate of the DU, and to send the measured number of lost packets or the packet loss rate of the DU to the CU-UP;

[0068] The CU-UP is used to receive the number of packet losses or the packet loss rate of the UE measured by the UE, calculate the reliability between the access network device and the UE based on the number of packet losses or the packet loss rate of the CU-UP, the number of packet losses or the packet loss rate of the interface between the CU-UP and the DU, the number of packet losses or the packet loss rate of the DU and the number of packet losses or the packet loss rate of the UE, and report the calculated reliability between the access network device and the UE to the core network device.

[0069] Eighthly, a user equipment (UE) is provided, comprising: a measurement unit and a transceiver unit, wherein,

[0070] The measurement unit is used to measure the reliability of the UE;

[0071] The transceiver unit is used to send the reliability of the UE to the access network equipment.

[0072] In conjunction with the eighth aspect, in a first possible implementation, the transceiver unit is further configured to receive reliability measurement indication information from the access network device before the measurement unit measures the reliability of the UE, the reliability measurement indication information indicating that a reliability measurement should be performed.

[0073] In conjunction with the eighth aspect, or the first possible implementation of the eighth aspect, in the second possible implementation, the transceiver unit is further configured to receive a measurement cycle from the access network device.

[0074] In conjunction with the second possible implementation of the eighth aspect, in the third possible implementation, the measurement unit for measuring the reliability of the UE includes: the measurement unit is used to measure the reliability of the UE within the measurement period.

[0075] The aforementioned UE can also be implemented using a processor and a transceiver (or transceiver circuit). The processor can implement the function of the measurement unit, and the transceiver (or transceiver circuit) can implement the function of the transceiver unit.

[0076] Ninthly, a user equipment (UE) is provided, comprising: a measurement unit and a transceiver unit, wherein,

[0077] The measurement unit is used to measure the packet loss rate or the number of lost packets of the UE;

[0078] The transceiver unit is used to send the packet loss rate or number of lost packets of the UE to the access network device.

[0079] In conjunction with the ninth aspect, in a first possible implementation, the transceiver unit is further configured to receive packet loss rate or packet loss number measurement indication information from the access network device before the measurement unit measures the packet loss rate or packet loss number of the UE, the packet loss rate or packet loss number measurement indication information indicating that packet loss rate or packet loss number measurement is performed.

[0080] In conjunction with the ninth aspect, or the first possible implementation of the ninth aspect, in the second possible implementation, the transceiver unit is further configured to receive a measurement cycle from the access network device.

[0081] In conjunction with the second possible implementation of the ninth aspect, in the third possible implementation, the measurement unit for measuring the packet loss rate or number of packet losses of the UE includes: the measurement unit is used to measure the reliability of the UE during the measurement period.

[0082] The aforementioned UE can also be implemented using a processor and a transceiver (or transceiver circuit). The processor can implement the function of the measurement unit, and the transceiver (or transceiver circuit) can implement the function of the transceiver unit.

[0083] In a tenth aspect, a core network device is provided, including a transceiver unit and a determination unit, wherein,

[0084] The transceiver unit is used to receive the reliability information between the access network device and the user equipment (UE) from the access network device.

[0085] The determining unit is used to determine the reliability between the access network device and the core network device, and to determine the reliability between the UE and the core network device based on the reliability between the access network device and the UE and the reliability between the access network device and the core network device.

[0086] In conjunction with the tenth aspect, in a first possible implementation, the transceiver unit is further configured to send first indication information to the access network device, wherein the first indication information indicates that a reliability measurement is to be performed.

[0087] In conjunction with the tenth aspect, or the first possible implementation of the tenth aspect, in the second possible implementation, the transceiver unit is further configured to send second indication information to the access network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0088] The aforementioned core network equipment can also be implemented using a processor and a transceiver (or transceiver circuit). The processor can perform the function of a deterministic unit, and the transceiver (or transceiver circuit) can perform the function of a transceiver unit.

[0089] Eleventhly, a communication system is provided, including at least two of the aforementioned access network equipment, core network equipment, and user equipment (UE).

[0090] In a twelfth aspect, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform any of the methods described in the preceding aspects.

[0091] In a thirteenth aspect, a computer program product containing instructions is provided that, when run on a computer, causes the computer to perform any of the methods described in the preceding aspects. Attached Figure Description

[0092] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0093] Figure 1 A schematic diagram of a communication system structure provided in an embodiment of the present invention;

[0094] Figure 2 A schematic diagram of a protocol stack provided for an embodiment of the present invention;

[0095] Figure 3 A schematic diagram of a base station structure provided in an embodiment of the present invention;

[0096] Figure 4 A flowchart of a reliability measurement method provided in an embodiment of the present invention;

[0097] Figure 5 A flowchart of another reliability measurement method provided in an embodiment of the present invention;

[0098] Figure 6 A flowchart of another reliability measurement method provided in an embodiment of the present invention;

[0099] Figure 7 A schematic diagram of time delay measurement provided in an embodiment of the present invention;

[0100] Figure 8 This is another schematic diagram of time delay measurement provided in an embodiment of the present invention;

[0101] Figure 9 This is a schematic diagram of an access network device structure provided in an embodiment of the present invention;

[0102] Figure 10 A schematic diagram of a UE structure provided in an embodiment of the present invention;

[0103] Figure 11 This is a schematic diagram of a core network device structure provided in an embodiment of the present invention. Detailed Implementation

[0104] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings. The network architecture and service scenarios described in the embodiments of the present invention are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present invention, and do not constitute a limitation on the technical solutions provided in the embodiments of the present invention. As those skilled in the art will know, with the evolution of network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present invention are also applicable to similar technical problems.

[0105] Figure 1 A possible system network diagram of this application is shown. For example... Figure 1 As shown, at least one terminal 10 communicates with a radio access network (RAN). The RAN includes at least two base stations: base station 20 and base station 30. Only two base stations and one user equipment (UE) are shown in the figure. The RAN is connected to a core network (CN). The core network includes one or more core network devices. Optionally, the CN may be coupled to one or more external networks, such as the Internet, the public switched telephone network (PSTN), etc. During UE movement, the connection with the radio access network can be switched from base station 20 to base station 30. In this case, base station 20 can be called the source base station, and base station 30 can be called the target base station. The UE can communicate with the base stations through an air interface (e.g., the Uu interface).

[0106] In Long Term Evolution (LTE) and New Radio (NR), the UE and the base station / access and mobility management function (AMF) entity communicate over the air interface. To better process data, network protocols define several protocol stacks, each with a different function, for example... Figure 2 As shown in the diagram. The non-access stratum (NAS) layer is the signaling channel between the UE and the AMF. Specifically, the UE sends a NAS message to the base station, which then forwards the NAS message to the AMF. The base station does not parse the NAS message during this forwarding process. The NAS layer is primarily responsible for management functions such as public land mobile network (PLMN) selection, manual selection, access control, registration, and subscription information. These processes can coordinate with other protocol layers, such as the access stratum (AS) layer.

[0107] The AS layer refers to the protocol layer other than the NAS layer. It can include radio resource control (RRC), packet data convergence protocol (PDCP), radio link control (RLC), medium access control (MAC), and physical layer (PHY). The AS layer is mainly responsible for functions such as handover, encryption, data retransmission, sequencing, and transmission.

[0108] To facilitate understanding, some terms used in this application will be explained below.

[0109] In this application, the terms "network" and "system" are often used interchangeably. However, those skilled in the art will understand their meanings. The communication apparatus described in this application refers to network elements in a communication system, such as terminals, base stations, and core network equipment.

[0110] A terminal, sometimes called User Equipment (UE), is a communication-enabled device. It can include handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem. Examples include handheld devices and in-vehicle devices with wireless connectivity. Currently, some examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, self-driving, remote medical surgery, smart grids, transportation safety, smart cities, and smart homes.

[0111] Access network equipment refers to radio access network (RAN) nodes (or devices) that connect terminals to a wireless network, typically including base stations. Examples of RAN nodes include: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), basestation controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc. Additionally, in a network architecture, access network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment comprising both CU and DU nodes. This includes RAN equipment for CU nodes and DU nodes, which separates the base station's protocol layer. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. The access network equipment or base station in this embodiment may include a central unit (CU) and DUs, for example... Figure 3As shown. The CU and DU can be physically separated or deployed together; this embodiment does not specifically limit this. One CU can connect to one DU, or multiple DUs can share one CU, which can save costs and facilitate network expansion. The CU and DU can be partitioned according to the protocol stack. One possible approach is to deploy the radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers on the CU, and the remaining radio link control (RLC), media access control (MAC), and physical layers on the DU. This invention does not completely limit the above protocol stack partitioning method; other partitioning methods are also possible. The CU and DU are connected via the F1 interface. The CU represents the gNB and connects to the core network via the Ng interface. The CU may further include a centralized unit control plane (CU-CP) node or a centralized unit user plane (CU-UP) node. The CU-CP is responsible for control plane functions, mainly including RRC and PDCP-C. PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. The CU-UP is responsible for user plane functions, mainly including SDAP and PDCP-U. SDAP is mainly responsible for processing core network data and mapping flows to bearers. PDCP-U is mainly responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB and connects to the core network via the Ng interface. It connects to the DU via the F1-C (control plane) interface. The CU-UP connects to the DU via the F1-U (user plane) interface. Alternatively, PDCP-C may also be located within the CU-UP. The access network equipment mentioned in this application can be a device including a CU, or a DU, or a device including both CU and DU, or a control plane CU node (CU-CP node), a user plane CU node (CU-UP node), and a DU node. Furthermore, in other possible cases, the access network device can be other devices that provide wireless communication functions for terminal devices. The embodiments of this application do not limit the specific technology or device form used in the access network device. In the embodiments of this application, nodes such as CU nodes, CU-CP nodes, CU-UP nodes, CU nodes, and DU nodes can also be entities, devices, or functional units, and can be simply referred to as CU-CP, CU-UP, CU, DU, etc., all referring to the same meaning.CU, DU, CU-CP, and CU-UP are merely examples of names. Devices or entities that perform the same or similar functions may have other names, and this application does not limit them.

[0112] Core network equipment refers to the equipment in the core network (CN) that provides service support to terminals. Examples of core network equipment include: Access and Mobility Management Function (AMF) entities, Session Management Function (SMF) entities, User Plane Function (UPF) entities, etc., which will not be listed here. Specifically, the AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; and the UPF entity can be a user plane function entity, primarily responsible for connecting to external networks.

[0113] In this application, entities can also be referred to as network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and an SMF entity can also be called an SMF network element or an SMF functional entity, etc. When describing specific network elements or entities, sometimes the terms "entity," "network element," and "functional entity" are omitted. For example, an AMF entity is abbreviated as AMF, and a UPF entity is abbreviated as UPF. In future communication systems, such as 6G, the above-mentioned network elements may have other names, which are not limited in this application.

[0114] The following description uses a 5G network as an example to illustrate the solution provided in the embodiments of the present invention. However, the solution of the present invention is not limited to 5G networks. For example, the solution of the present invention can also be applied to LTE, or subsequent evolved networks, or multiple converged networks, etc. The embodiments of the present invention do not limit this.

[0115] This invention provides a reliability measurement scheme. This scheme can be applied to... Figure 1 The system shown. (As shown in the image) Figure 4 As shown:

[0116] Step 401: The core network device sends a first indication message to the access network device, the indication message instructing the access network device to perform a reliability measurement.

[0117] The first instruction information can specifically instruct to perform uplink reliability measurement, downlink reliability measurement, or both uplink reliability measurement and downlink reliability measurement.

[0118] The first instruction information can also instruct the performance of reliability measurements between the access network device and the UE, between the access network device and the core network device, and between the core network device and the UE.

[0119] In this embodiment, reliability can be defined as the probability that a data packet sent by the sending end will be successfully received by the receiving end within a certain time delay. Optionally, for the reliability between the access network device and the UE, this time delay refers to the distance a data packet travels from the ingress point of the service data unit (SDU) at the layer 2 / layer 3 (L2 / L3) of the sending end to the egress point at the layer 2 / L3 of the receiving end. Optionally, the data packet may have a set size, such as X bytes. Reliability is related to factors such as the size of the data packet, the time delay, and the packet loss rate.

[0120] Optionally, the core network equipment may send a second indication message to the access network equipment, indicating the reliability measurement cycle or the reliability reporting cycle.

[0121] Optionally, the core network device can send a delay threshold to the access network device, which is used by the access network device to calculate reliability.

[0122] Optionally, the aforementioned first or second instruction information is sent by the control plane entity of the core network element.

[0123] Optionally, the specific method of carrying the aforementioned first or second indication information can be achieved by adding the aforementioned indication information to existing Quality of Service (QoS) monitoring information elements, or by adding the aforementioned indication information to existing configuration information for Immediate Minimization of Drive-Tests (immediateMDT).

[0124] Step 402: The access network device receives the first indication information and measures the reliability between the access network device and the UE.

[0125] Optionally, step 401 is an optional step. The access network device can actively perform reliability measurements without the core network indication, that is, the access network device does not need to receive the first indication information or the core network device does not need to send the first indication information.

[0126] The uplink reliability between the access network device and the UE can be identified as: Reliability_Uu_UL

[0127] The downlink reliability between the access network equipment and the UE can be identified as: Reliability_Uu_DL

[0128] Optionally, the access network device measures the uplink / downlink reliability between the access network device and the UE according to the aforementioned reliability measurement cycle.

[0129] Step 403: The access network device sends the reliability information between the access network device and the UE to the core network device.

[0130] Access network equipment can send the above-mentioned reliability information to the control plane entity of the core network element, or it can send the above-mentioned reliability information to the user plane entity of the core network element.

[0131] Optional, for Figure 3 The architecture shown, with CU and DU separated, allows the access network device to transmit the aforementioned reliability data to the control plane entity of the core network element via CU-CP, and also to the user plane entity of the core network element via CU-UP. It should be noted that this refers to the access network device transmitting the reliability measurement results (i.e., the corresponding reliability values) between the access network device and the UE to the core network device.

[0132] Optionally, the access network device reports reliability according to the aforementioned reliability reporting cycle. Step 404: The core network device determines the reliability between the access network device and the core network device, and determines the reliability between the UE and the core network device.

[0133] Optionally, the core network equipment in this step can be a core network user plane device, such as a UPF.

[0134] Regarding the reliability between access network equipment and core network equipment:

[0135] Downlink reliability: Reliability_NG_DL = 1 - {sum(number of lost packets (measurement results not received from RAN), number of packets successfully transmitted but downlink latency timeout) / total number of packets sent by CN carrying reliability detection indication or QoS detection indication}.

[0136] Uplink reliability: Reliability_NG_UL = 1 - {sum(number of lost packets (measurement results not received from RAN), number of successfully transmitted packets but uplink latency timeout) / total number of packets sent by CN carrying reliability detection indications or QoS detection indications}. The meaning of the number of lost packets (measurement results not received from RAN) is the same as that of downlink reliability.

[0137] The number of lost packets (measurement results for which no RAN feedback was received) is determined by the core network device based on whether it received a response from the access network device to the data packet carrying a reliability detection indicator or QoS monitoring packet indicator (QMP indicator) sent by the core network device to the access network device. If no response is received, the packet is considered lost, and the value of "number of lost packets (measurement results for which no RAN feedback was received)" is incremented by 1. If a response is received, the core network device calculates the downlink and uplink delays between the access network device and the core network device. If the downlink delay exceeds a preset threshold, the core network device considers the packet to be a successfully transmitted packet with downlink delay timeout, and the value of "number of successfully transmitted packets with downlink delay timeout" is incremented by 1. Similarly, if the uplink delay exceeds a preset threshold, the core network device considers the packet to be a successfully transmitted packet with uplink delay timeout, and the value of "number of successfully transmitted packets with uplink delay timeout" is incremented by 1. Optionally, the data packet carrying a reliability indication or QoS detection indication sent by the core network device to the access network device also carries the time when the core network device sent the data packet (which can be called timestamp T1). Receiving the response from the access network device to the data packet carrying the reliability indication or QoS detection indication sent by the core network device to the access network device means that the core network device has received the data packet carrying timestamp T1 from the access network device. Optionally, the data packet carrying timestamp T1 received by the core network device from the access network device also carries the time when the access network device received the data packet carrying timestamp T1 from the core network device (called timestamp T2), and the time when the access network device sent the data packet carrying timestamp T1 to the core network device (called timestamp T3). The time when the core network device received the data packet carrying timestamp T1 from the access network device is called timestamp T4. The core network device calculates the downlink delay and uplink delay between the access network device and the core network device based on T1, T2, T3, and T4. If the core network equipment and the access network equipment are time-synchronized, the downlink latency between the access network equipment and the core network equipment is T2-T1, and the uplink latency between the access network equipment and the core network equipment is T4-T3. If the core network equipment and the access network equipment are not time-synchronized, the downlink latency and uplink latency between the access network equipment and the core network equipment are both {(T4-T1)-(T3-T2)} / 2.

[0138] Optionally, regarding downlink reliability, the number of lost packets (measurement results not received from the RAN) may also refer to the number of data packets sent by the core network device to the access network device but not received by the access network device. The access network device can obtain the number of unreceived data packets based on the GPRS Tunneling Protocol User Plane (GTP-U) sequence numbers received from the core network device (i.e., if the access network device finds that packets with certain GTP-U sequence numbers have not been received, it considers the corresponding packets lost). Similarly, regarding uplink reliability, the number of lost packets (measurement results not received from the RAN) may also refer to the number of data packets sent by the access network device to the core network device but not received by the core network device. The core network device can obtain the number of unreceived data packets based on the GTP-U sequence numbers received from the access network (i.e., if the core network device finds that packets with certain GTP-U sequence numbers have not been received, it considers the corresponding packets lost).

[0139] It should be noted that core network equipment can periodically determine the reliability between access network equipment and core network equipment. The above "number of lost packets (measurement results not received from RAN)," "number of successfully transmitted packets but downlink latency timeouts," "number of successfully transmitted packets but uplink latency timeouts," and "total number of packets sent by CN carrying reliability detection indications or QoS detection indications" refer to the corresponding statistical results within the corresponding period. Each time periodic statistics are performed, the above values ​​are initialized to 0.

[0140] Regarding the reliability between the UE and core network equipment:

[0141] Uplink reliability: Reliability_UL = Reliability_Uu_UL * Reliability_NG_UL

[0142] Downlink reliability: Reliability_DL = Reliability_Uu_DL * Reliability_NG_DL

[0143] Through the above scheme, the access network device first measures the reliability between the UE and the access network device and feeds it back to the core network device, which can then calculate the reliability between the UE and the core network device.

[0144] Once the core network equipment or access network equipment obtains reliability, the network performance can be known (the reliability can be displayed or sent to a third party). Reliability can also be used as a reference when deploying new services on the network, or network parameter settings or service parameter settings can be adjusted based on reliability during network management.

[0145] It should be noted that steps 401, 403, and 404 are optional steps. That is, the access network device measures the reliability between the UE and the access network device according to its own needs, or the access network device obtains indication information from other devices (such as network management) indicating that the reliability between the UE and the access network device needs to be measured.

[0146] In this embodiment of the application, the reliability measurement between the access network device and the UE in step 402 can be implemented in various ways. The following will use... Figure 3 The following example illustrates step 402 using a CU and DU separation architecture, but the present invention is not limited to the following implementation.

[0147] Implementation method 1:

[0148] The reliability measurement between the access network device and the UE is divided into multiple segments. The corresponding entity first calculates the reliability of each segment, and then the overall reliability between the access network device and the UE is calculated.

[0149] Optionally, the reliability between the access network element and the UE can be segmented as follows: the reliability of the CU-UP (measured by the CU-UP), the reliability of the F1-U interface between the CU-UP and the DU (measured by the CU-UP), the reliability of the DU (measured by the DU), and the reliability of the UE (measured by the UE).

[0150] For example, such as Figure 5 As shown, the process for calculating reliability in segments is as follows:

[0151] Step 501: CU-CP sends the first reliability measurement indication information to CU-UP, CU-CP sends the second reliability measurement indication information to DU, and CU-CP sends the third reliability measurement indication information to UE.

[0152] The first, second, and third reliability measurement indication information can specifically indicate whether to perform uplink reliability measurement, downlink reliability measurement, or both. Optionally, the measurement directions indicated by the first, second, and third reliability measurement indication information may differ. For example, the CU-CP may notify the CU-UP to measure uplink, while the CU-CP may notify the DU to measure downlink, or the CU-CP may notify the UE to measure both uplink and downlink.

[0153] Optionally, the CU-CP may send reliability measurement indication information to only one or two of the CU-UP, DU, and UE.

[0154] Optionally, CU-UP, DU, and UE can perform reliability measurements at the Data Radio Bearer (DRB) granularity level.

[0155] Optionally, the CU-CP can send reliability measurement cycles or reporting cycles to the CU-UP, DU, and UE. Optionally, the measurement cycle or reporting cycle can utilize existing latency measurement cycles or reporting cycles.

[0156] Optionally, the CU-CP can send latency thresholds to the CU-UP, DU, and UE respectively. Each entity (CU-UP, DU, and UE) performs reliability measurements based on these latency thresholds (i.e., the latency thresholds used by each entity to calculate reliability, as described below). Optionally, the CU-CP decomposes the latency threshold between the access network element and the UE sent by the core network control plane entity into corresponding latency thresholds for each entity. For example, if the latency threshold between the access network element and the UE is Threlod1, the corresponding latency thresholds for each entity are Threlod2, Threlod3, and Threlod4, where Threlod1 = Threlod2 + Threlod3 + Threlod4.

[0157] Optionally, if the core network control plane does not send a latency threshold to the access network device, the access network device can obtain the latency threshold based on the end-to-end packet delay budget (PDB) corresponding to the QoS flow carried in the DRB. The end-to-end PDB of the QoS flow is the upper limit of latency between the UE and the core network user plane entity (terminating at the N6 interface, i.e., the interface between the core network user plane and the data network). The core network device (such as the core network control plane device) can notify the access network device of this value, or use the PDB value corresponding to 5QI for the QoS flow as specified in existing protocols. The access network device can obtain the corresponding PDB required on the access network side based on this end-to-end PDB value and the PDB on the core network side; for example, by subtracting the core network device's PDB from the end-to-end PDB.

[0158] The PDB corresponding to the core network equipment is the PDB between the access network equipment and the core network user plane. It can be set according to the values ​​specified in the 3GPPTS 23.501 protocol (which specifies the values ​​of the PDB corresponding to the core network equipment for certain QoS flows corresponding to 5QI), or the access network equipment can pre-configure the values ​​of the PDB corresponding to the core network equipment.

[0159] Optionally, step 501 is optional. In this implementation, step 502 can be executed directly, meaning that each entity does not need to receive reliability measurement indication information from CU-CP.

[0160] Step 502: Measure the reliability of each entity CU-UP, DU and UE respectively.

[0161] In the embodiments of this application, the number of lost packets, the number of packets successfully transmitted but with timeout, and the total number of packets mentioned below can refer to the values ​​counted by each entity or device in each measurement cycle or reporting cycle.

[0162] CU-UP reliability: Reliability_CU-UP = 1 - {sum(number of lost packets, number of successfully transmitted packets but timed out) / total number of packets}. Specifically, it can be divided into uplink and downlink reliability. This reliability is measured by the CU-UP side.

[0163] For downlink reliability, the number of lost packets refers to the number of downlink packet losses on the CU-UP side, meaning that the CU-UP received a data packet from the core network user plane entity, but the data packet was not sent to the DU through the F1 interface. The number of packets that were successfully transmitted but timed out refers to the number of packets for which the CU-UP sent the data packet received from the core network user plane entity to the DU, but the downlink latency on the CU-UP side exceeded a certain threshold. The total number of packets refers to the total number of packets received by the CU-UP from the core network user plane entity.

[0164] For uplink reliability, the number of lost packets refers to the number of uplink lost packets on the CU-UP side. This includes the number of packets that the CU-UP receives from the DU but does not forward to the core network user plane entities, and / or the number of packets for which the CU-UP does not receive PDCP sequence numbers (SNs) from the DU (i.e., the number of packets for which the CU-UP does not receive packets corresponding to certain PDCP sequence numbers from the DU). The number of packets that are successfully transmitted but timed out refers to the number of packets for which the CU-UP forwards data packets to core network elements, but the uplink latency on the CU-UP side exceeds a certain threshold. The total number of packets refers to the total number of uplink PDCP sequence numbers between the sequence number of the first data packet sent from the DU to the CU-UP and the sequence number of the last data packet (including the number of PDCP sequence numbers that the CU-UP did not receive from the DU). Here, the first and last data packets refer to data packets within one measurement period.

[0165] The downlink latency on the CU-UP side is defined as the difference between the time when the CU-UP receives a data packet from the core network user plane entity and the time when the CU-UP sends the data packet to the DU. The uplink latency on the CU-UP side is calculated as the difference between the time when the CU-UP receives a PDCP Service Data Unit (PDCP SDU) from the DU and the time when the CU-UP sends the data packet to the core network user plane entity.

[0166] Optionally, the data packets here refer to PDCP layer data packets (such as PDCP SDU) or SDAP layer data packets (such as SDAP SDU).

[0167] The reliability of the F1-U interface is defined as: Reliability_F1 = 1 - {sum(number of lost packets, number of successfully transmitted packets that timed out) / total number of packets)}. Specifically, it can be divided into uplink and downlink reliability. Downlink reliability is measured by the DU side. Uplink reliability is measured by the CU-UP side.

[0168] For downlink reliability, the number of lost packets refers to the number of data packets sent by the CU-UP to the DU but not received by the DU. The DU can determine the number of unreceived packets based on the GTP-U sequence numbers received from the CU-UP (i.e., if the DU finds that packets with certain GTP-U sequence numbers have not been received, the DU considers the corresponding packets lost). The number of packets that were successfully transmitted but timed out refers to the number of packets for which the DU received the corresponding data packets, but the downlink delay of the corresponding data packets (i.e., the downlink delay of the F1-U interface) exceeded a certain threshold. The total number of packets refers to the number of packets between the sequence number of the first data packet received by the DU from the CU-UP and the sequence number of the last data packet (including the number of lost packets). Optionally, the data packets here refer to PDCP layer data packets (such as PDCP protocol data units (PDCP PDUs)).

[0169] For uplink reliability, a similar method to downlink reliability can be used. The number of lost packets refers to the number of data packets sent by the DU to the CU-UP but not received by the CU-UP. The CU-UP can determine the number of unreceived packets based on the GTP-U sequence numbers received from the DU (i.e., if the CU-UP finds that packets with certain GTP-U sequence numbers have not been received, the CU-UP considers the packet lost). The number of successfully transmitted but timed-out packets refers to the number of data packets for which the CU-UP received the corresponding data packet, but the uplink delay (i.e., the F1-U interface uplink delay) exceeded a certain threshold. The total number of packets refers to the number of packets between the sequence number of the first data packet sent by the DU to the CU-UP and the sequence number of the last data packet (including the number of lost packets). Optionally, the data packets here refer to PDCP layer data packets (such as PDCP SDUs).

[0170] The downlink latency (i.e., the F1-U interface downlink latency) is defined as: the difference between the time when CU-UP sends a data packet to DU and the time when CU-UP receives a GTP-U packet transmission status message from DU confirming successful transmission, minus the processing latency on the DU side, and then divided by 2. The uplink latency has the same value as the downlink latency. That is, (the time when CU-UP receives a GTP-U packet transmission status message from DU confirming successful transmission - the time when CU-UP sends a data packet to DU - the processing latency on the DU side) / 2.

[0171] Optionally, CU-UP can also assume that uplink and downlink reliability have the same value. For example, CU-UP can use the above definition of uplink reliability to obtain uplink reliability, and the downlink reliability value is the same as the uplink reliability value.

[0172] Optionally, the reliability of CU-UP and F1 port can be calculated as a whole. The specific definition is as follows:

[0173] For downlink reliability, packet loss refers to a packet received by the CU-UP from the core network user plane entity, but the packet was not successfully received by the DU. A packet that was successfully transmitted but timed out refers to a packet received by the CU-UP from the core network user plane entity and correctly received by the DU, but the corresponding downlink delay exceeded a certain threshold. The total number of packets refers to the number of packets received by the CU-UP from the core network user plane entity. Optionally, the packets here refer to PDCP layer packets (e.g., PDCP SDU) or SDAP layer packets (e.g., SDAP SDU).

[0174] For uplink reliability, packet loss refers to a packet received by the CU-UP from the DU, but which the CU-UP fails to forward to the core network. A successfully transmitted but timed-out packet refers to a packet received by the CU-UP from the DU and forwarded to the core network element, but whose corresponding uplink latency exceeds a certain threshold. The total number of packets refers to the number of data packets received by the CU-UP from the core network user plane entity. The total number of packets refers to the total number of uplink PDCP sequence numbers between the sequence number of the first data packet sent by the DU to the CU-UP and the sequence number of the last data packet (including the number of PDCP sequence numbers that the CU-UP did not receive from the DU). Here, the first and last data packets refer to data packets within one measurement period. Optionally, the data packets here refer to PDCP layer data packets (e.g., PDCP SDU) or SDAP layer data packets (e.g., SDAP SDU).

[0175] The downlink latency is defined as: downlink latency on the CU-UP side + downlink latency on the F1-U interface. The uplink latency is defined as: uplink latency on the CU-UP side + uplink latency on the F1-U interface.

[0176] DU reliability: Reliability_DU = 1 - {sum(number of lost packets, number of successfully transmitted packets but timed out) / total number of packets)}. Specifically, it can be divided into uplink and downlink reliability. Both downlink and uplink reliability are measured by the DU side.

[0177] For downlink reliability, the number of lost packets refers to the number of packets that the DU receives from the CU-UP but fails to successfully transmit to the UE. The number of packets that are successfully transmitted but time out refers to packets that the DU successfully transmits to the UE, but the corresponding downlink latency exceeds a threshold. The total number of packets refers to the total number of packets received by the DU from the CU-UP. Optionally, the data packets here refer to PDCP layer data packets (such as PDCP PDUs).

[0178] For uplink reliability, the number of lost packets refers to the number of packets that the DU receives from the UE but does not forward to the CU-UP. The number of packets that are successfully transmitted but time out refers to packets that the DU forwards to the CU-UP, but the corresponding uplink latency on the DU side exceeds a threshold. The total number of packets refers to the total number of packets received by the DU from the UE. Optionally, the packets here refer to PDCP layer packets (such as PDCP PDUs).

[0179] The downlink latency is defined as: the downlink latency of the DU's RLC layer processing plus the downlink latency from the DU's MAC layer to determining that the UE has correctly received the RLC SDU. The downlink latency of the DU's RLC layer processing is defined as: the difference between the time the RLC layer receives the RLC SDU from the F1-U interface and the time the MAC layer schedules the last part of the RLC SDU. The downlink latency from the DU's MAC layer to determining that the UE has correctly received the RLC SDU is defined as: the difference between the time the MAC layer receives the corresponding RLC SDU and the time the DU determines that the last part of the RLC SDU has been correctly received by the UE (for RLC UM mode, the DU uses HARQ feedback to determine whether the UE has correctly received the SDU. For RLC AM mode, the DU uses RLC feedback to determine whether the UE has correctly received the SDU).

[0180] The uplink latency is defined as: the uplink latency of the DU's RLC layer processing plus the uplink latency of the DU processing data packets over the air interface. The uplink latency of the DU's RLC layer processing is defined as: the difference between the time the RLC receives the first part of an RLC SDU and the time the RLC layer sends the RLC SDU to the PDCP or CU. The uplink latency of the DU processing data packets over the air interface is defined as: the difference between the uplink transmission time of an uplink MAC SDU corresponding to an uplink grant indication and the time the MAC layer correctly receives the uplink MAC SDU.

[0181] UE reliability: Reliability_UE = 1 - {sum(number of lost packets, number of packets successfully transmitted but timed out) / total number of packets)}.

[0182] Specifically, reliability can be divided into uplink and downlink reliability. Both downlink and uplink reliability are measured by the UE.

[0183] For uplink reliability, the number of lost packets refers to the number of data packets received by the UE's PDCP layer from the upper layer, but which the UE failed to successfully transmit to the access network equipment (e.g., base station). The number of packets successfully transmitted but timed out refers to the number of packets successfully transmitted by the UE to the access network equipment, but the corresponding uplink latency exceeded a threshold. The total number of packets refers to the total number of packets received by the UE's PDCP from the upper layer.

[0184] For downlink reliability, the number of lost packets refers to the number of data packets that the UE did not correctly receive from the access network equipment (for example, the UE obtains the number of unreceived data packets based on the PDCP sequence numbers received from the access network equipment; that is, if the UE finds that packets with certain PDCP sequence numbers have not been received, the UE considers the packet lost). The number of successfully transmitted but timed-out packets refers to the number of data packets that the UE received from the access network equipment, but the downlink latency on the UE side exceeded a certain threshold. The total number of packets refers to the number of data packets correctly received by the UE from the access network equipment, as well as the number of lost packets.

[0185] Downlink latency is defined as the difference between the moment the UE correctly receives a downlink data packet and the moment the UE's PDCP sends the packet to the upper layer. Correct reception of a downlink data packet by the UE is defined as follows: for RLC UM mode, it is when the UE's MAC layer correctly receives a data packet; for RLC AM mode, it is when the UE's RLC layer correctly receives a data packet.

[0186] The uplink latency is defined as the difference between the time when the UE's PDCP layer receives a data packet from the upper layer and the time when the UE obtains the uplink authorization to send the uplink data packet, including the latency of the UE obtaining the uplink authorization and sending a scheduling request or random access procedure.

[0187] Step 503: DU sends the measured reliability data to CU-UP.

[0188] Step 504: The UE reports the measured reliability to the CU-UP.

[0189] Optionally, the UE can send the measured reliability data to the CU-CP, which in turn forwards it to the CU-UP.

[0190] Step 504 is optional.

[0191] Step 505: CU-UP then calculates the reliability between the access network equipment and the UE based on the reliability reported by the DU and UE.

[0192] Reliability_Uu = Reliability_CU - UP * Reliability_F1 * Reliability_DU * Reliability_UE (uplink and downlink are calculated separately) or Reliability_Uu = Reliability_CU - UP * Reliability_F1 * Reliability_DU. It should be noted that the uplink and downlink reliability between the access network device and the UE are calculated using CU - UP, F1, DU, and the UE's uplink and downlink reliability according to the above formulas.

[0193] CU-UP can notify the core network user plane entity of the calculated reliability between the access network device and the UE. This step corresponds to step 403 in the previous text.

[0194] Optionally, in this embodiment, the access network device can perform reliability measurements between the access network device and the UE at the DRB granularity. If the core network device indicates that a reliability measurement is to be performed on a certain QoS flow, the access network device can perform certain conversions, such as the access network device assuming that each QoS flow carried in a certain DRB has the same reliability.

[0195] Optionally, the reliability between the access network device and the UE, and the reliability between the access network device and the core network device (e.g., UPF) can be statistically analyzed or measured separately. That is, only the reliability between the access network device and the UE is measured, or only the reliability between the access network device and the UPF is statistically analyzed.

[0196] Implementation Method Two:

[0197] This implementation method is similar to the first implementation method mentioned above, and the reliability is measured in segments. The difference is that in the second implementation method, the reliability of each entity is not directly measured. Instead, the packet loss rate or number of packets lost in each segment or entity is measured or counted. Finally, the CU-UP calculates the reliability between the access network element and the UE based on the packet loss rate or number of packets lost reported by each entity.

[0198] Optionally, the packet loss rate or number of lost packets between the access network device and the UE can be segmented as follows: packet loss rate or number of lost packets for the CU-UP (measured by the CU-UP), packet loss rate or number of lost packets for the F1-U interface between the CU-UP and the DU (measured by the CU-UP), packet loss rate or number of lost packets for the DU (measured by the DU), and packet loss rate or number of lost packets for the UE (measured by the UE). The packet loss measurement for each segment or entity can refer to Implementation Method 1. The packet loss rate is the number of lost packets / total number of packets. The definition of the total number of packets can refer to the description in Implementation Method 1, and will not be repeated here.

[0199] like Figure 6 As shown, the measurement process is as follows:

[0200] Step 601: CU-CP sends a first packet loss rate or packet loss number measurement indication information to CU-UP, CU-CP sends a second packet loss rate or packet loss number measurement indication information to DU, and CU-CP sends a third packet loss rate or packet loss number measurement indication information to UE.

[0201] The first, second, and third packet loss rate or packet loss number measurement indication information can specifically indicate uplink packet loss rate or packet loss number measurement, downlink packet loss rate or packet loss number measurement, or both. Optionally, the measurement directions indicated by the first, second, and third packet loss rate or packet loss number measurement indication information may differ. For example, CU-CP notifies CU-UP to measure uplink, while CU-CP notifies DU to measure downlink, or CU-CP notifies UE to measure both uplink and downlink.

[0202] Optionally, the CU-CP can send packet loss rate or packet loss number measurement indication information to only one or two of the CU-UP, DU, and UE.

[0203] Step 602: Measure the corresponding packet loss rate or number of packets lost for each entity, CU-UP, DU, and UE.

[0204] CU-UP measures or counts the number of lost packets or the packet loss rate of CU-UP itself.

[0205] CU-UP measures or counts the number of lost packets or the packet loss rate of the F1 interface.

[0206] DU measures or counts the number of lost packets or the packet loss rate.

[0207] The UE measures or counts the number of lost packets or the packet loss rate.

[0208] Step 603: DU sends the measured number of lost packets or packet loss rate to CU-UP.

[0209] Step 604: The UE reports the measured number of lost packets or packet loss rate to the CU-UP.

[0210] Optionally, the UE can send the measured number of lost packets or packet loss rate to the CU-CP, which then forwards it to the CU-UP.

[0211] Step 605: CU-UP then calculates the reliability between the access network equipment and the UE based on the number of lost packets or the packet loss rate reported by the DU and UE.

[0212] CU-UP measures reliability: CU-UP calculates the reliability between access network elements and UE by statistically analyzing uplink and downlink latency and packet loss rate between access network equipment and UE.

[0213] CU-UP can notify the core network user plane entity of the calculated reliability, which corresponds to step 403 in the previous text.

[0214] Uplink reliability between access network equipment and UE: Reliability_Uu_UL = 1 - {sum(uplink packet loss, number of packets successfully received but with latency exceeding the threshold) / total number of data packets in the CU-UP within the statistical period}.

[0215] The uplink packet loss count is calculated as the sum of CU-UP packet loss, F1 interface packet loss, DU packet loss, and UE packet loss, or it may only include CU-UP packet loss. The CU-UP packet loss count, F1 interface packet loss count, DU packet loss count, and UE packet loss count are described in Implementation Method 1.

[0216] If in step 601, the CU-CP notifies each entity to measure the packet loss rate, then the number of lost packets is the uplink packet loss rate * the total number of data packets of CU-UP within the statistical period. The uplink packet loss rate is 1 - (1 - the packet loss rate of CU-UP as calculated by CU-UP) * (1 - the packet loss rate of the F1 interface) * (1 - the packet loss rate of DU) * (1 - the packet loss rate of the F1 interface) * (1 - the packet loss rate of UE), or only includes the packet loss rate calculated by CU-UP. The number of packets successfully received but with latency exceeding a threshold is as follows: if the uplink latency between the access network device and the UE calculated by CU-UP within a statistical period exceeds a certain threshold, then all packets counted within that statistical period are considered successfully received but with uplink latency exceeding the threshold. If the uplink latency between the access network device and the UE calculated by CU-UP within a statistical period does not exceed a certain threshold, then all packets counted within that statistical period do not meet the condition of being successfully received but with latency exceeding the threshold. The total number of data packets for CU-UP within the statistical period is the sum of the number of uplink packet losses and the number of data packets successfully received by CU-UP. The uplink latency between the access network device and the UE refers to the sum of the uplink latency of each segment in implementation mode one.

[0217] Downlink reliability between access network equipment and UE: Reliability_Uu_DL = 1 - {sum(downlink packet loss, number of packets successfully sent to UE but with latency exceeding the threshold) / total number of data packets received by CU-UP from core network elements within the statistical period}.

[0218] The uplink packet loss count is calculated as the sum of the packet loss counts for CU-UP (statistics of CU-UP), F1 interface, DU, and UE, or only the UE side packet loss count. The packet loss counts for CU-UP, F1 interface, DU, and UE are described in Implementation Method 1.

[0219] If in step 601, the CU-CP notifies each entity to measure the packet loss rate, then the number of lost packets is the downlink packet loss rate multiplied by the total number of data packets received by the CU-UP from the core network elements within the statistical period. The downlink packet loss rate is 1 - (1 - the packet loss rate of the CU-UP as calculated by the CU-UP) * (1 - the packet loss rate of the F1 interface) * (1 - the packet loss rate of the DU) * (1 - the packet loss rate of the F1 interface) * (1 - the packet loss rate of the UE), or only includes the packet loss rate calculated by the CU-UP. The number of packets successfully sent to the UE but with a latency exceeding a threshold is defined as follows: if the downlink latency between the access network device and the UE calculated by the CU-UP within a statistical period exceeds a certain threshold, then all packets counted within that statistical period are considered successfully sent but with a latency exceeding the threshold. If the downlink latency between the access network device and the UE calculated by the CU-UP within a statistical period does not exceed a certain threshold, then none of the packets counted within that statistical period meet the criteria of being successfully sent to the UE but with a latency exceeding the threshold. The downlink latency refers to the sum of the downlink latency of each segment in implementation method one.

[0220] Implementation method three:

[0221] In this implementation, unlike the segmented measurement or statistics in the first implementation, the access network device counts the overall transmission delay of data packets between the access network device and the UE, and then calculates the reliability between the access network device and the UE based on the delay.

[0222] Uplink reliability between access network equipment and UE: Reliability_Uu_UL = 1 - {sum(uplink packet loss, number of packets successfully received but with latency exceeding the threshold) / total number of data packets in the statistical period}.

[0223] The uplink packet loss count refers to the number of data packets between the access network device and the UE that underwent uplink latency measurement, but whose uplink latency was not calculated (e.g., the access network device notified the UE to perform uplink latency measurement on a certain uplink data packet, but the uplink data packet was not successfully received by the access network device; for example, the uplink data packet was not sent by the UE, or the UE sent it but the access network device did not successfully receive it). The number of successfully received packets whose latency exceeded the threshold refers to the number of data packets between the access network device and the UE whose uplink latency was measured, but whose calculated uplink latency exceeded a certain threshold. The total number of data packets within the statistical period refers to the number of data packets for which uplink latency measurement was performed.

[0224] Downlink reliability between access network equipment and UE: Reliability_Uu_DL = 1 - {sum(downlink packet loss, number of packets successfully received but with latency exceeding the threshold) / total number of data packets in the statistical period}.

[0225] Downlink packet loss refers to the number of data packets between the access network device and the UE that underwent downlink delay measurement, but whose downlink delay result was not calculated (e.g., the access network device notifies the UE to perform downlink delay measurement on a certain downlink data packet, but the downlink data packet is not successfully received by the UE; for example, the downlink data packet was not sent by the access network device, or it was sent but not successfully received by the UE, or the access network device notifies the UE to perform downlink delay measurement on a certain downlink data packet, but the data packet containing the downlink delay information returned by the UE is not successfully received by the access network device). The number of successfully received packets whose delay exceeds a threshold refers to the number of data packets between the RAN and the UE whose downlink delay was measured, but whose calculated downlink delay exceeded a certain threshold. The total number of data packets within the statistical period refers to the number of data packets for which downlink delay measurement was performed.

[0226] The following example illustrates how the access network device calculates the overall transmission delay of data packets between the access network device and the UE.

[0227] Example 1: The sender adds a timestamp to the data packet, and the receiver obtains the transmission delay of the data packet based on the time of receiving the data packet and the timestamp carried in the data packet.

[0228] For example, regarding downlink latency, for data packets requiring downlink latency measurement, the access network device carries a timestamp when transmitting the data packet (e.g., the PDCP layer of the access network device adds a timestamp to the header of the PDCP PDU, indicating the time when the PDCP layer receives the corresponding PDCP SDU from the upper layer, i.e., T_send). Optionally, the access network device carries latency measurement indication information when transmitting the downlink data packet, indicating whether the data packet needs downlink latency measurement (e.g., the PDCP layer of the access network device adds this indication information to the header of the PDCP PDU). When the UE receives the data packet, the UE records the time when its PDCP layer submits the data packet (e.g., the PDCP SDU) to the upper layer, denoted as T_receive. Optionally, the UE determines whether downlink latency measurement of the data packet needs to be performed based on the latency measurement indication information sent by the access network device. If downlink latency measurement is required, the UE can calculate the downlink transmission latency of the data packet as: T_receive - T_send; Optionally, the UE can send the uplink transmission latency measurement result to the access network device, or the UE can send T_receive to the access network device, and the access network device can calculate the corresponding downlink latency of the data packet based on T_receive and T_send stored by the access network device itself.

[0229] For example, regarding uplink latency, for data packets requiring uplink latency measurement, the UE carries a timestamp when transmitting the data packet (e.g., the UE's PDCP layer adds a timestamp to the header of the PDCP PDU, indicating the time when the UE's PDCP layer receives the corresponding PDCP SDU from the upper layer, i.e., T_send). Optionally, the UE carries latency measurement indication information when transmitting uplink data packets, indicating whether the data packet needs uplink latency measurement (e.g., the UE's PDCP layer adds this indication information to the header of the PDCP PDU). Optionally, for uplink transmission latency, the UE can send T_send to the access network device in other ways, such as through an RRC message. Optionally, the RRC message also carries the PDCP sequence number of the PDCP layer corresponding to the data packet for T_send. When the access network device receives the data packet, it records the time when its PDCP layer submits the data packet (e.g., PDCP SDU) to the upper layer, denoted as T_receive. The access network device can calculate the uplink transmission delay of the data packet as: T_receive - T_send.

[0230] In this application embodiment, the method for measuring the transmission delay of data packets between the core network device and the access network device and between the access network device and the UE can be implemented in various ways. An example is given below, but this application is not limited to the implementation method described below.

[0231] For the latency between the core network user plane (e.g., UPF) and RAN equipment (e.g., base stations), the method is as follows:

[0232] The core network control plane sends a latency statistics indication to the RAN device, indicating that the latency between the RAN device and the UPF needs to be measured. This indication can be uplink, downlink, or a combination of both.

[0233] When the core network user plane sends a packet to the RAN device, it includes an indication (such as a QoS monitoring packet indicator, QMP) in the GTP-U header, indicating that the packet is used for uplink / downlink latency measurement. It also includes a downlink transmission timestamp T1, which represents the time the core network user plane sent the packet. This timestamp can be the local time of the core network user plane.

[0234] When the RAN device receives the data packet, it records the received time T1 and its own local time T2. This time can be the RAN device's local time.

[0235] The RAN device sends an uplink packet to the core network user plane. This uplink packet may or may not carry uplink data transmitted by the UE. The GTP-U header of this packet carries T1, T2, the time T3 when the RAN device sent the packet, and an indication (such as a QoS monitoring packet indicator) indicating that the packet is used for uplink / downlink delay measurement. The time when the RAN device sends the packet can be the RAN device's local time. When the core network user plane receives this uplink packet, it records the time T4 when it receives the packet. The RAN device may also carry the uplink delay and downlink delay between the RAN device and the UE in this uplink packet. The uplink delay and downlink delay between the RAN device and the UE are measured by the RAN device. Optionally, the RAN device may also carry the uplink delay and downlink delay between the RAN device and the UE in other uplink packets (i.e., the corresponding uplink packets do not carry T1, T2, T3).

[0236] refer to Figure 7 The uplink delay between the RAN device and the UE includes PDCP queuing delay (D1), air interface uplink delay measured by DU (D2.1), RLC delay measured by DU (D2.2), F1 interface uplink delay (D2.3), and PDCP reordering delay (D2.4).

[0237] D1 is defined as the time delay from when the UE's PDCP layer receives a data packet from the upper layer to when the UE obtains uplink authorization to send that uplink data packet, including the time delay when the UE sends a scheduling request or random access procedure to obtain uplink authorization.

[0238] D2.1 is defined as: the time delay between the uplink transmission time of an uplink data packet (e.g., MAC SDU) corresponding to an uplink grant indication and the base station correctly receiving the data packet.

[0239] D2.2 is defined as: from the time the base station receives the first part of an RLC SDU to the time it sends the RLC SDU to the PDCP or CU.

[0240] D2.3 is defined as follows: When CU-UP sends a data packet to DU, and CU-UP receives a GTP-U packet transmission status message from DU confirming successful transmission of the packet, the processing delay on the DU side is subtracted. Then, the result is divided by 2.

[0241] The definition of D2.4 is: When CU-UP receives a PDCP SDU from DU, CU-UP sends the packet to the core network user plane.

[0242] refer to Figure 8The downlink latency between the RAN device and the UE includes downlink air interface latency (D1), downlink latency of the DU's RLC layer processing (D2), downlink latency of the F1 interface (D3), and downlink latency on the CU-UP side (D4).

[0243] Downlink air interface delay (D1) is defined as the difference between the time the MAC layer receives the corresponding RLC SDU and the time the DU determines that the last part of the RLC SDU has been correctly received by the UE (for RLC UM mode, the DU determines whether the UE has received it correctly according to HARQ feedback. For RLC AM mode, the DU determines whether the UE has received it correctly according to RLC feedback).

[0244] The downlink latency (D2) of the RLC layer for a DU is defined as the difference between the time when the RLC layer receives the RLC SDU from the F1-U interface and the time when the MAC layer schedules the last part of the RLC SDU.

[0245] The downlink latency of F1 port is the same as the uplink latency of F1 port.

[0246] CU-UP downlink delay (D4) definition: The difference between the time when CU-UP receives a data packet from the core network user plane and the time when CU-UP sends the data packet to DU.

[0247] The delays mentioned above are average delays over a period of time or cycle.

[0248] Corresponding to the reliability measurement method given in the above method embodiments, this application also provides a corresponding communication device (sometimes also called a communication equipment) and a communication system. The communication device includes modules or units for executing each part of the above embodiments. The modules or units can be software, hardware, or a combination of software and hardware. The following is only a brief description of the communication device and system. For details of the implementation, please refer to the description of the foregoing method embodiments, which will not be repeated here.

[0249] This application provides an access network device for implementing... Figure 4 The corresponding method embodiment, such as Figure 9 As shown, the access network device includes:

[0250] The measurement unit is used to measure the reliability between the access network device and the user equipment (UE).

[0251] The transceiver unit is used to send the reliability information between the access network device and the UE to the core network device.

[0252] Optionally, before measuring the reliability between the access network device and the user equipment (UE), the transceiver unit is further configured to receive first indication information from the core network device, the first indication information indicating that a reliability measurement should be performed.

[0253] Optionally, the transceiver unit is further configured to receive second indication information from the core network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0254] In implementation method three of the preceding method embodiments, the measurement unit measures the reliability between the access network device and the user equipment (UE) including:

[0255] The measurement unit is used to count the transmission delay of data packets between the access network device and the UE, and to calculate the reliability between the access network device and the UE based on the transmission delay.

[0256] The aforementioned access network equipment can also be implemented using a processor and transceiver (or transceiver circuit) or other hardware and software methods.

[0257] Regarding the first implementation of the method described above, this application provides an access network device, referring to... Figure 3 The structures shown include: CU-CP, CU-UP, and DU.

[0258] CU-CP is used to send the first reliability measurement indication information to CU-UP;

[0259] CU-CP is used to send a second reliability measurement indication message to DU;

[0260] CU-CP is used to send third reliability measurement indication information to the UE;

[0261] CU-UP is used to measure the reliability of CU-UP.

[0262] CU-UP is used to measure the reliability of the interface between CU-UP and DU;

[0263] DU is used to measure the reliability of the DU.

[0264] DU is used to send the reliability of the measured DU to CU-UP;

[0265] CU-UP is used to receive the UE's reliability measured by the UE.

[0266] CU-UP is used to calculate the reliability between the access network device and the UE based on the reliability of CU-UP, the reliability of the interface between CU-UP and DU, the reliability of DU and the reliability of UE.

[0267] CU-UP is used to report the calculated reliability between the access network device and the UE to the core network device.

[0268] Regarding the second implementation of the method embodiments described above, this application provides an access network device, referring to... Figure 3 The structures shown include: CU-CP, CU-UP, and DU.

[0269] CU-CP is used to send the first packet loss rate or packet loss number measurement indication information to CU-UP;

[0270] CU-CP is used to send a second packet loss rate or packet loss number measurement indication information to DU;

[0271] CU-CP is used to send a third packet loss rate or packet loss number measurement indication information to the UE;

[0272] CU-UP is used to measure the number of lost packets or the packet loss rate of the CU-UP itself.

[0273] CU-UP is used to measure the number of lost packets or the packet loss rate at the interface between CU-UP and DU.

[0274] DU is used to measure the number of lost packets or the packet loss rate.

[0275] DU is used to send the measured number of lost packets or packet loss rate of DU to CU-UP;

[0276] CU-UP is used to receive the number of packet losses or packet loss rate of the UE measured by the UE.

[0277] CU-UP is used to calculate the reliability between the access network device and the UE based on the number or rate of packet loss of CU-UP itself, the number or rate of packet loss of the interface between CU-UP and DU, the number or rate of packet loss of DU and the number or rate of packet loss of UE.

[0278] CU-UP is used to report the calculated reliability between the access network device and the UE to the core network device.

[0279] This application provides a UE for implementing the method embodiments described above, such as... Figure 10 As shown, the UE includes: a measurement unit and a transceiver unit.

[0280] A measurement unit is used to measure the reliability of the UE;

[0281] The transceiver unit is used to send the reliability of the UE to the access network equipment.

[0282] Optionally, before the measurement unit measures the reliability of the UE, the transceiver unit is further configured to receive reliability measurement indication information from the access network device, the reliability measurement indication information indicating that a reliability measurement should be performed.

[0283] Optionally, the transceiver unit is also configured to receive a measurement cycle from the access network device.

[0284] Optionally, the measurement unit measures the reliability of the UE by including:

[0285] A measurement unit is used to measure the reliability of the UE during the measurement period.

[0286] This application provides a UE for implementing the method embodiments described above, such as... Figure 10 As shown, the UE includes: a measurement unit and a transceiver unit.

[0287] A measurement unit is used to measure the packet loss rate or the number of lost packets of the UE;

[0288] The transceiver unit is used to send the packet loss rate or number of lost packets of the UE to the access network equipment.

[0289] Optionally, before the measurement unit measures the packet loss rate or number of packets lost by the UE, the transceiver unit is configured to receive packet loss rate or number of packets lost measurement indication information from the access network device, the packet loss rate or number of packets lost measurement indication information indicating that packet loss rate or number of packets lost measurement should be performed.

[0290] Optionally, the transceiver unit is also configured to receive a measurement cycle from the access network device.

[0291] Optionally, the measurement unit measures the packet loss rate or number of packet losses of the UE, including:

[0292] The measurement unit is used to measure the reliability of the UE during the measurement period.

[0293] The aforementioned UE can also be implemented using a processor and transceiver (or transceiver circuit) or other hardware and software methods.

[0294] This application provides a core network device, including a transceiver unit and a determination unit.

[0295] A transceiver unit is used to receive reliable information between the access network device and the user equipment (UE) from the access network device.

[0296] A determining unit is used to determine the reliability between the access network device and the core network device;

[0297] The determining unit is further configured to determine the reliability between the UE and the core network device based on the reliability between the access network device and the UE and the reliability between the access network device and the core network device.

[0298] Optionally, the transceiver unit is further configured to send a first indication information to the access network device, wherein the first indication information indicates that a reliability measurement is to be performed.

[0299] Optionally, the transceiver unit is further configured to send a second indication information to the access network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

[0300] The aforementioned core network equipment can also be implemented using processors and transceivers (or transceiver circuits) or other hardware and software methods.

[0301] It should be noted that the designations "first," "second," "third," etc., in the embodiments of this application are merely for distinguishing multiple nouns with the same name in one embodiment, and do not indicate the order or processing sequence of the device. Nouns with different designations in different embodiments may have the same meaning; nouns with the same designation in different embodiments may also have different meanings. The specific meaning needs to be determined according to the specific scheme.

[0302] In this application, the use of singular designations for elements is intended to indicate "one or more," not "one and only one," unless otherwise specified. "Some" refers to one or more. "At least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

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

Claims

1. A method for measuring reliability, characterized in that, include: The access network device measures the reliability between the access network device and the user equipment (UE). The reliability is the probability that the transmitting end sends a data packet to the receiving end and successfully receives the data packet within a delay threshold. The reliability is calculated based on the following parameters: the number of lost packets, the number of packets that are successfully transmitted but exceed the delay threshold, and the total number of packets. The access network device includes a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU). The access network device sends the reliability information between the access network device and the UE to the core network device; The access network device measures the reliability between the access network device and the user equipment (UE), including: The reliability between the access network device and the UE is measured in multiple segments, and the CU-UP calculates the reliability between the access network device and the UE based on the reliability of each segment. or, The access network device and the UE are divided into multiple segments, and the packet loss rate or number of packets lost in each segment is measured. The CU-UP calculates the reliability between the access network device and the UE based on the packet loss rate or number of packets lost in each segment.

2. The method according to claim 1, characterized in that, It also includes, Before measuring the reliability between the access network device and the user equipment (UE), the access network device receives first indication information from the core network device, the first indication information indicating that a reliability measurement should be performed.

3. The method according to claim 1 or 2, characterized in that, It also includes, The access network device receives a second indication information from the core network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

4. The method according to claim 1 or 2, characterized in that... The reliability between the access network device and the UE is measured in multiple segments, and the CU-UP calculates the reliability between the access network device and the UE based on the reliability of each segment, including: CU-CP sends the first reliability measurement indication information to CU-UP; CU-CP sends a second reliability measurement indication message to DU; CU-CP sends a third reliability measurement indication message to the UE; CU-UP measures the reliability of CU-UP; CU-UP measures the reliability of the interface between CU-UP and DU; The reliability of DU measurement; The DU sends the measured reliability of the DU to the CU-UP; The CU-UP receives the UE's reliability measurements. Based on the reliability of the CU-UP, the reliability of the interface between the CU-UP and the DU, the reliability of the DU, and the reliability of the UE, the CU-UP calculates the reliability between the access network device and the UE.

5. The method according to claim 1 or 2, characterized in that... The access network device and the UE are divided into multiple segments, and the packet loss rate or number of packets lost in each segment is measured. The CU-UP calculates the reliability between the access network device and the UE based on the packet loss rate or number of packets lost in each segment, including: CU-CP sends the first packet loss rate or packet loss count measurement indication information to CU-UP; The CU-CP sends a second packet loss rate or packet loss number measurement indication to the DU; The CU-CP sends a third packet loss rate or packet loss number measurement indication information to the UE; CU-UP measures the number of lost packets or the packet loss rate of the CU-UP itself; CU-UP measures the number of lost packets or the packet loss rate at the interface between CU-UP and DU; DU measures the number of lost packets or the packet loss rate. The DU sends the measured number of lost packets or packet loss rate to the CU-UP; The CU-UP receives the number of lost packets or the packet loss rate of the UE as measured by the UE. The CU-UP calculates the reliability between the access network device and the UE based on the number or rate of packet loss of the CU-UP itself, the number or rate of packet loss of the interface between the CU-UP and the DU, the number or rate of packet loss of the DU, and the number or rate of packet loss of the UE.

6. A method for measuring reliability, characterized in that, include: The core network equipment receives the reliability between the access network equipment and the user equipment (UE) from the access network equipment. The reliability is the probability that the sending end sends a data packet to the receiving end and successfully receives the data packet within the delay threshold. The reliability is calculated based on the following parameters: the number of lost packets, the number of packets that are successfully transmitted but exceed the delay threshold, and the total number of packets. The reliability between the access network equipment and the user equipment (UE) is obtained by comprehensively calculating the reliability after measuring the data in multiple segments between the access network equipment and the UE. The core network equipment determines the reliability between the access network equipment and the core network equipment; The core network device determines the reliability between the UE and the core network device based on the reliability between the access network device and the UE, and the reliability between the access network device and the core network device.

7. The method according to claim 6, characterized in that, It also includes, The core network device sends a first indication message to the access network device, indicating that a reliability measurement should be performed.

8. The method according to claim 6 or 7, characterized in that, It also includes, The core network device sends a second indication information to the access network device, the second indication information indicating the reliability measurement cycle or the reliability reporting cycle.

9. An access network device, characterized in that, include: The measurement unit is used to measure the reliability between the access network device and the user equipment (UE). The reliability is the probability that the transmitting end sends a data packet to the receiving end and successfully receives the data packet within the delay threshold. The reliability is calculated based on the following parameters: the number of lost packets, the number of packets that are successfully transmitted but exceed the delay threshold, and the total number of packets. The access network device includes a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), and a distributed unit (DU). The transceiver unit is used to send the reliability information between the access network device and the UE to the core network device; The measurement of reliability between the access network device and the user equipment (UE) includes: The reliability between the access network device and the UE is measured in multiple segments, and the CU-UP calculates the reliability between the access network device and the UE based on the reliability of each segment. or, The access network device and the UE are divided into multiple segments, and the packet loss rate or number of packets lost in each segment is measured. The CU-UP calculates the reliability between the access network device and the UE based on the packet loss rate or number of packets lost in each segment.

10. The access network device according to claim 9, characterized in that, The transceiver unit is further configured to receive first indication information from the core network device before measuring the reliability between the access network device and the UE, the first indication information indicating that a reliability measurement should be performed.

11. The access network device according to claim 9 or 10, characterized in that, The transceiver unit is also configured to receive second indication information from the core network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

12. The access network equipment according to claim 9 or 10, characterized in that, The measurement unit is used to measure the reliability between the access network device and the user equipment (UE), including: The measurement unit is used to count the transmission delay of data packets between the access network device and the UE, and to calculate the reliability between the access network device and the UE based on the transmission delay.

13. An access network device, characterized in that, It includes the centralized unit control plane CU-CP, the centralized unit user plane CU-UP, and the distributed unit DU, among which, The CU-CP is used to send a first reliability measurement indication information to the CU-UP, a second reliability measurement indication information to the DU, and a third reliability measurement indication information to the user equipment (UE). The CU-UP is used to measure the reliability of the CU-UP and the reliability of the interface between the CU-UP and the DU. The reliability is the probability that the sending end sends a data packet to the receiving end and successfully receives the data packet within the delay threshold. The reliability is calculated based on the following parameters: the number of packet loss, the number of packets that are successfully transmitted but exceed the delay threshold, and the total number of packets. The DU is also used to measure the reliability of the DU and send the measured reliability of the DU to the CU-UP; The CU-UP is also used to receive the reliability of the UE measured by the UE, calculate the reliability between the access network device and the UE based on the reliability of the CU-UP, the reliability of the interface between the CU-UP and the DU, the reliability of the DU and the reliability of the UE, and report the calculated reliability between the access network device and the UE to the core network device.

14. An access network device, characterized in that, It includes the centralized unit control plane CU-CP, the centralized unit user plane CU-UP, and the distributed unit DU, among which, The CU-CP is used to send a first packet loss rate or packet loss number measurement indication information to the CU-UP, a second packet loss rate or packet loss number measurement indication information to the DU, and a third packet loss rate or packet loss number measurement indication information to the user equipment UE. The CU-UP is used to measure the number of packet losses or the packet loss rate of the CU-UP, and to measure the number of packet losses or the packet loss rate of the interface between the CU-UP and the DU. The DU is used to measure the number of lost packets or the packet loss rate of the DU, and to send the measured number of lost packets or the packet loss rate of the DU to the CU-UP; The CU-UP is used to receive the number of packet losses or the packet loss rate of the UE measured by the UE. Based on the number of packet losses or the packet loss rate of the CU-UP, the number of packet losses or the packet loss rate of the interface between the CU-UP and the DU, the number of packet losses or the packet loss rate of the DU, and the number of packet losses or the packet loss rate of the UE, the CU-UP calculates the reliability between the access network device and the UE, and reports the calculated reliability between the access network device and the UE to the core network device. The reliability is the probability that the sending end sends a data packet to the receiving end and successfully receives the data packet within the delay threshold. The reliability is calculated based on the following parameters: the number of packet losses, the number of packets that were successfully transmitted but exceeded the delay threshold, and the total number of packets.

15. A core network device, characterized in that, It includes a transceiver unit and a determination unit, wherein, The transceiver unit is used to receive the reliability between the access network device and the user equipment (UE) from the access network device. The reliability is the probability that the sending end sends a data packet to the receiving end and successfully receives the data packet within the delay threshold. The reliability is calculated based on the following parameters: the number of lost packets, the number of packets that are successfully transmitted but exceed the delay threshold, and the total number of packets. The reliability between the access network device and the user equipment (UE) is obtained by comprehensively calculating the reliability after measuring the data in multiple segments between the access network device and the UE. The determining unit is used to determine the reliability between the access network device and the core network device, and to determine the reliability between the UE and the core network device based on the reliability between the access network device and the UE and the reliability between the access network device and the core network device.

16. The core network equipment according to claim 15, characterized in that, The transceiver unit is further configured to send a first indication message to the access network device, wherein the first indication message indicates that a reliability measurement should be performed.

17. The core network equipment according to claim 15 or 16, characterized in that, The transceiver unit is also used to send a second indication information to the access network device, the second indication information indicating a reliability measurement cycle or a reliability reporting cycle.

Images