Measurement method, apparatus and device

Abstract

The application provides a measurement method, device and equipment. The measurement method comprises: a first device performs measurement to obtain a measurement result; the measurement result comprises at least one of the following: time delay information based on a PDU set; error transmission rate based on a PDU set; throughput based on a PDU set; data volume based on a PDU set; so that a second device can obtain XR service performance based on the measurement result, thereby helping network optimization and realizing better network performance and XR service performance.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a measurement method, apparatus and device. Background Technology

[0002] XR (eXtended Reality) generally refers to various forms of augmented reality, virtual reality, and mixed reality, where humans or machines, or individuals, communicate via handheld or wearable terminals. These services exhibit quasi-periodic characteristics and are subject to jitter. Downlink typically involves high data rates, such as video; uplink typically involves high-frequency data packets, such as gesture / control updates or uplink video streams. XR services are characterized by low latency, high throughput, and low error rates. To support these characteristics, XR introduces a Protocol Data Unit Set (PDU set). A PDU set is a collection of one or more PDUs generated by the application layer. For some services, the application layer needs to obtain all PDUs in the PDU set to retrieve the desired information unit; however, for other services, even if the application layer cannot obtain all PDUs (e.g., some PDUs are lost), it can still obtain the complete application layer information unit through the application layer data recovery mechanism.

[0003] However, the existing measurement reports do not contain any XR-related information. Especially for services like XR that require low latency and high throughput, the network cannot know the performance of XR services, and therefore cannot determine whether the network's key indicators meet the requirements of XR services, which affects network performance and further impacts XR services and user experience. Summary of the Invention

[0004] The purpose of this application is to provide a measurement method, apparatus, and device to solve the problem that the network cannot accurately process XR services because the measurement reports in the prior art do not contain XR-related information.

[0005] To address the aforementioned problems, this application provides a measurement method, the method comprising:

[0006] The first device performs a measurement and obtains a measurement result; the measurement result includes at least one of the following:

[0007] Delay information based on Protocol Data Unit (PDU) sets;

[0008] Error transmission rate based on PDU set;

[0009] Throughput based on PDU sets;

[0010] The amount of data based on the PDU set.

[0011] The latency information based on the PDU set includes at least one of the following:

[0012] The first delay is the average delay of multiple data packets within a PDU set;

[0013] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0014] The third delay is the delay of a PDU set;

[0015] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0016] The third time delay is:

[0017] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0018] N1 and N2 are positive integers.

[0019] The error transmission rate based on the PDU set includes at least one of the following:

[0020] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0021] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0022] The third loss rate is the average packet loss rate across a QoS flow or a set of M1 PDUs within a DRB.

[0023] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0024] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0025] Where M0, M1, and M2 are positive integers.

[0026] Where the QoS flows corresponding to multiple PDU sets in a DRB are related, the second loss rate can be any of the following:

[0027] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0028] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0029] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0030] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0031] Where the QoS flows corresponding to multiple PDU sets in a DRB are related, the fourth loss rate can be any of the following values:

[0032] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0033] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0034] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0035] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0036] The measurement results also include:

[0037] Identification information of the PDU set of packets dropped due to association.

[0038] The target parameter can take any one of the following values:

[0039] The number of PDU sets included in a QoS flow or a DRB;

[0040] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0041] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0042] The target parameters are N1, N2, M1 and / or M2.

[0043] Where M0 can take any one of the following values:

[0044] The number of packets included in a QoS flow or a DRB;

[0045] The number of packets included in a QoS flow or a DRB during a data burst;

[0046] The number of packets included in a QoS flow or a DRB within a measurement period.

[0047] Where the PDU set contains integrity processing information.

[0048] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0049] or,

[0050] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0051] Where the PDU set has integrity processing information, the measurement result also includes at least one of the following:

[0052] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0053] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0054] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0055] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0056] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0057] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0058] The throughput based on the PDU set is as follows:

[0059] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0060] The amount of data based on the PDU set includes at least one of the following:

[0061] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0062] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0063] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0064] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0065] The method further includes:

[0066] The first device sends the measurement result to the second device; the second device includes at least one of: a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0067] The first device sends the measurement result to the second device, including:

[0068] After the configured statistical collection period ends, the first device sends the measurement results to the second device; wherein the duration of the configured statistical collection period is the duration of a data burst.

[0069] This application embodiment also provides a measurement method, the method comprising:

[0070] The second device receives measurement results sent by the first device, the measurement results including at least one of the following:

[0071] Delay information based on Protocol Data Unit (PDU) sets;

[0072] Error transmission rate based on PDU set;

[0073] Throughput based on PDU sets;

[0074] Data volume based on PDU set;

[0075] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0076] The latency information based on the PDU set includes at least one of the following:

[0077] The first delay is the average delay of multiple data packets within a PDU set;

[0078] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0079] The third delay is the delay of a PDU set;

[0080] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0081] The third time delay is:

[0082] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0083] N1 and N2 are positive integers.

[0084] The error transmission rate based on the PDU set includes at least one of the following:

[0085] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0086] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0087] The third loss rate is the average packet loss rate across a QoS flow or a set of M1 PDUs within a DRB.

[0088] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0089] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0090] Where M0, M1, and M2 are positive integers.

[0091] Where the QoS flows corresponding to multiple PDU sets in a DRB are related, the second loss rate can be any of the following:

[0092] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0093] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0094] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0095] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0096] Where the QoS flows corresponding to multiple PDU sets in a DRB are related, the fourth loss rate can be any of the following values:

[0097] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0098] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0099] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0100] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0101] The measurement results also include:

[0102] Identification information of the PDU set of packets dropped due to association.

[0103] The target parameter can take any one of the following values:

[0104] The number of PDU sets included in a QoS flow or a DRB;

[0105] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0106] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0107] The target parameters are N1, N2, M0, M1 and / or M2.

[0108] Where M0 can take any one of the following values:

[0109] The number of packets included in a QoS flow or a DRB;

[0110] The number of packets included in a QoS flow or a DRB during a data burst;

[0111] The number of packets included in a QoS flow or a DRB within a measurement period.

[0112] Where the PDU set contains integrity processing information.

[0113] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0114] or,

[0115] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0116] Where the PDU set has integrity processing information, the measurement result also includes at least one of the following:

[0117] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0118] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0119] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0120] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0121] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0122] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0123] The throughput based on the PDU set is as follows:

[0124] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0125] The amount of data based on the PDU set includes at least one of the following:

[0126] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0127] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0128] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0129] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0130] This application also provides a first device, including a memory, a transceiver, and a processor:

[0131] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0132] Perform measurements and obtain measurement results; the measurement results include at least one of the following:

[0133] Delay information based on Protocol Data Unit (PDU) sets;

[0134] Error transmission rate based on PDU set;

[0135] Throughput based on PDU sets;

[0136] The amount of data based on the PDU set.

[0137] This application also provides a second device, including a memory, a transceiver, and a processor:

[0138] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0139] Receive measurement results sent by the first device, wherein the measurement results include at least one of the following:

[0140] Delay information based on Protocol Data Unit (PDU) sets;

[0141] Error transmission rate based on PDU set;

[0142] Throughput based on PDU sets;

[0143] Data volume based on PDU set;

[0144] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0145] This application embodiment also provides a measuring device applied to a first device, the device comprising:

[0146] A measurement unit for performing measurements and obtaining measurement results; the measurement results include at least one of the following:

[0147] Delay information based on Protocol Data Unit (PDU) sets;

[0148] Error transmission rate based on PDU set;

[0149] Throughput based on PDU sets;

[0150] The amount of data based on the PDU set.

[0151] This application embodiment also provides a measuring device, applied to a second device, comprising:

[0152] A receiving unit is configured to receive measurement results sent by a first device, the measurement results including at least one of the following:

[0153] Delay information based on Protocol Data Unit (PDU) sets;

[0154] Error transmission rate based on PDU set;

[0155] Throughput based on PDU sets;

[0156] Data volume based on PDU set;

[0157] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0158] This application also provides a processor-readable storage medium storing a program for causing the processor to perform the method described above.

[0159] The above-mentioned technical solution of this application has at least the following beneficial effects: First equipment

[0160] In the measurement method, apparatus, and device of this application embodiment, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, thereby contributing to network optimization and achieving better network performance and XR service performance. Attached Figure Description

[0161] Figure 1 This diagram illustrates one of the steps of the measurement method provided in this application embodiment;

[0162] Figure 2 This is the second schematic diagram illustrating the steps of the measurement method provided in the embodiments of this application;

[0163] Figure 3 This is a schematic diagram of the structure of the first device provided in an embodiment of this application;

[0164] Figure 4 This is a schematic diagram showing the structure of the second device provided in an embodiment of this application;

[0165] Figure 5 This is a schematic diagram of the structure of the measuring device provided in an embodiment of this application;

[0166] Figure 6 This is a second schematic diagram showing the structure of the measuring device provided in the embodiments of this application. Detailed Implementation

[0167] To make the technical problems, technical solutions and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments.

[0168] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0169] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0170] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0171] The technical solutions provided in this application can be applied to a variety of systems. For example, applicable systems may include Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Long Term Evolution Advanced (LTE-A) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5G New Radio (NR) systems and their evolved communication systems, and 6G (sixth generation mobile communication technology) systems. These systems may include terminal equipment and network equipment. The systems may also include a core network component, such as the Evolved Packet Core (EPC) and the 5G Core Network (5GC).

[0172] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0173] The network device involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, a base station may also be called an access point, or a device in an access network that communicates with a wireless terminal device through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The network device can also coordinate the attribute management of the air interface. For example, the network equipment involved in the embodiments of this application can be a base transceiver station (BTS) in a Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a NodeB in a Wide-band Code Division Multiple Access (WCDMA) system, an evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, a 5G base station (gNB) in a next generation system, a Home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of this application. In some network structures, the network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may be geographically separated.

[0174] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0175] like Figure 1 As shown in the figure, this application provides a measurement method, the method comprising:

[0176] Step 101: The first device performs a measurement and obtains a measurement result; the measurement result includes at least one of the following:

[0177] Delay information based on Protocol Data Unit (PDU) sets;

[0178] Error transmission rate based on PDU set;

[0179] Throughput based on PDU sets;

[0180] The amount of data based on the PDU set.

[0181] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0182] Optionally, the measurement performed by the first device is specifically a layer 2 measurement, or a layer 2 measurement related to a PDU set.

[0183] Optionally, the first device is a terminal or a base station.

[0184] In at least one embodiment of this application, the method further includes:

[0185] The first device sends the measurement result to the second device; the second device includes at least one of: a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0186] In one implementation, if the first device is a terminal, the second device is a base station.

[0187] In another implementation, if the first device is a base station, the second device is an OAM device or a TCE.

[0188] In this embodiment of the application, the second device can obtain XR service performance based on the measurement result, thereby determining whether the key network indicators meet the requirements of XR services, and then scheduling XR services, which helps network optimization and can achieve better network performance and XR service performance.

[0189] As an optional embodiment, the first device sends the measurement result to the second device, including:

[0190] After the configured statistical collection period ends, the first device sends the measurement results to the second device; wherein the duration of the configured statistical collection period is the duration of a data burst.

[0191] A data burst is a set of data generated by the application layer over a period of time. A data burst can contain one or more PDU sets. Data bursts are periodic.

[0192] This application embodiment also provides a reporting trigger condition for measurement results, that is, the length of each data burst is the length of a statistical collection period, and the reporting of the measurement result is triggered after the data burst ends; or the period of the data burst is used as the reporting trigger condition for measurement results, that is, the reporting of the measurement result is triggered after one period of the data burst ends.

[0193] Optionally, the reporting trigger conditions for the measurement results are configured by the network to the first device.

[0194] It should be noted that the measurements mentioned in the embodiments of this application are for a specific terminal, that is, the above measurement results are obtained based on per UE.

[0195] In existing schemes, PDU set QoS flows are defined for PDU sets. For a QoS flow, all PDUs in that PDU set follow the PDU set QoS parameters flow. Different QoS flows map to a DRB, but these QoS flows are correlated. For example, if PDU set 1 and PDU set 2 are correlated, and PDU set 1 is dropped in one QoS flow, then PDU set 2 associated with PDU set 1 in other QoS flows also needs to be dropped. PDU set integrity handling information (PSIHI) can be understood as follows: a PDU set can only be used by the application layer if all packets are present. Alternatively, if this PSIHI indication exists, then if one or more packets in a PDU set are dropped, the entire PDU set is discarded.

[0196] In at least one embodiment of this application, the latency information based on the PDU set includes at least one of the following:

[0197] The first delay is the average delay of multiple data packets within a PDU set;

[0198] The second delay is the average of the first delays of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB); N1 is a positive integer.

[0199] The third delay is the delay of a PDU set;

[0200] The fourth delay is the average of the third delays of a QoS flow or a set of N2 PDUs within a DRB; N2 is a positive integer.

[0201] The third delay is the difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set.

[0202] In one implementation, the first delay is equal to the sum of the delays of all data packets in a PDU set divided by the number of data packets in that PDU set.

[0203] In another implementation, the second delay is equal to the sum of the delays of all packets in a PDU set divided by the number of packets in the PDU set to obtain the first delay of the PDU set. Then, the first delay of all PDU sets in a QoS flow or a DRB is taken as the (arithmetic) average.

[0204] In another implementation, the moment of receiving the last data packet in the PDU set can also be understood as the moment when all data packets in the PDU set have been transmitted, or the moment when all data packets in the PDU set have been received.

[0205] In another implementation, the fourth delay is equal to the sum of the third delays of a QoS flow or all PDU sets within a DRB, divided by the number of PDU sets within that QoS flow or DRB, and then taken as the (arithmetic) average.

[0206] As an optional embodiment, N1 and / or N2 may take any of the following values:

[0207] The number of PDU sets included in a QoS flow or a DRB;

[0208] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0209] The number of PDU sets included in a QoS flow or a DRB within a measurement period.

[0210] For example, if N1 is the number of PDU sets included in a QoS flow or a DRB during a data burst, then the second delay is: the average of the first delay of the PDU sets included in a QoS flow or a DRB during a data burst.

[0211] For example, if N1 is the number of PDU sets included in a QoS flow or a DRB within the measurement time, then the second delay is: the average of the first delay of a QoS flow or a DRB included in the measurement time.

[0212] For example, if N2 is the number of PDU sets included in a QoS flow or a DRB during a data burst, then the fourth delay is: the average of the third delay of the PDU sets included in a QoS flow or a DRB during a data burst.

[0213] For example, if N2 is the number of PDU sets included in a QoS flow or a DRB within the measurement time, then the fourth delay is: the average of the third delay of a QoS flow or a DRB included in the measurement time.

[0214] In at least one embodiment of this application, the error transmission rate based on the PDU set includes at least one of the following:

[0215] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0216] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB; M0 is a positive integer.

[0217] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB; M1 is a positive integer.

[0218] The fourth loss rate is the PDU set loss rate of a QoS flow or a DRB containing M2 PDU sets; where M2 is a positive integer.

[0219] A fifth loss rate, which indicates whether a set of PDUs has been lost. For example, a fifth loss rate of 1 (or 100%) indicates that a set of PDUs has been lost; as another example, a fifth loss rate of 0 (or 0%) indicates that a set of PDUs has not been lost.

[0220] In one implementation, the first loss rate is: the number of packets lost in a PDU set under non-congested and / or congested conditions, divided by the total number of packets in that PDU set.

[0221] In another implementation, the third loss rate is: the ratio of PDUs lost in a PDU set under non-congested and / or congested conditions, to obtain the packet loss rate of each PDU set, and then the (arithmetic) average of the packet loss rates of all PDU sets in a QoS flow or a DRB is taken.

[0222] In another implementation, the fourth loss rate is: the number of PDU sets lost in a QoS flow or a DRB under non-congested and / or congested conditions, divided by the total number of all PDU sets in that QoS flow or DRB.

[0223] Optionally, M1 and / or M2 can take any of the following values:

[0224] The number of PDU sets included in a QoS flow or a DRB;

[0225] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0226] The number of PDU sets included in a QoS flow or a DRB within a measurement period.

[0227] In one implementation, M1 is the number of PDU sets included in a QoS flow or a DRB during a data burst. The third loss rate is the average packet loss rate of the PDU set within a QoS flow or a DRB in a data burst; for example, the number of packets lost in a data burst divided by the total number of packets in the data burst.

[0228] In another implementation, M2 represents the number of PDU sets included in a QoS flow or a DRB during a data burst. The fourth loss rate is then the PDU set loss rate of a QoS flow or a DRB within a data burst. For example, the PDU set loss rate of each PDU set is obtained by dividing the number of lost packets in each PDU set by the total number of packets in each PDU set. The average PDU set loss rate of all PDU sets in the data burst is then averaged (arithmetic mean) to obtain the average PDU set loss rate in the data burst.

[0229] Optionally, M0 can take any of the following values:

[0230] The number of packets included in a QoS flow or a DRB;

[0231] The number of packets included in a QoS flow or a DRB during a data burst;

[0232] The number of packets included in a QoS flow or a DRB within a measurement period.

[0233] In an optional embodiment of this application, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0234] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0235] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0236] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0237] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0238] In another optional embodiment of this application, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following:

[0239] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0240] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0241] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0242] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0243] Optionally, the measurement results may also include:

[0244] Identification information of the PDU set of packets dropped due to association.

[0245] For example, the identification information is a PDU set SN (serial number) identifier pair. For example, PDU set1 and PDU set2 are a pair and have an associated relationship.

[0246] In at least one embodiment of this application, when the PDU set has integrity processing information (PDU Set Integrated Handling Information, PSIHI), the M1 PDU sets do not include PDU sets lost due to integrity processing information; for example, when reporting the third loss rate per QoS flow or per DRB, PDU sets lost due to PSIHI indication are not included.

[0247] Alternatively, if the PDU set has integrity processing information (PDU Set Integrated Handling Information, PSIHI), the M1 PDU sets include PDU sets lost due to integrity processing information; for example, when reporting the third loss rate per QoS flow or per DRB, PDU sets lost due to PSIHI indication are included.

[0248] In at least one optional embodiment of this application, where the PDU set has PDU SetIntegrated Handling Information (PSIHI), the measurement result further includes at least one of the following:

[0249] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information; for example, the PDU set is identified by the PDU set SN;

[0250] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0251] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0252] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0253] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0254] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0255] As an optional embodiment, the throughput based on the PDU set is the ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst. If the buffer is empty, it does not include data transmitted within a slot.

[0256] As another optional embodiment, the data volume based on the PDU set includes at least one of the following:

[0257] The number of bits that a QoS flow or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0258] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0259] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0260] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0261] In summary, in this embodiment, the first device reports measurement results based on PDU sets according to network configuration, and specifies how to determine the measurement results when associated with PSIHI and PDU sets. This method helps the network understand XR service performance, determine whether some key indicators meet the conditions, and facilitates network optimization to achieve better network performance and XR service performance. For example, if a PDU set has very low latency, low throughput, and almost no packet loss, more resources can be allocated to other PDU sets. Similarly, if a QoS flow or DRB appears to have very low latency, low throughput, and almost no packet loss at the PDU set granularity, resources can be allocated to other QoS flows or DRBs.

[0262] like Figure 2 As shown in the embodiments of this application, a measurement method is also provided, the method comprising:

[0263] Step 201: The second device receives the measurement results sent by the first device, the measurement results including at least one of the following:

[0264] Delay information based on Protocol Data Unit (PDU) sets;

[0265] Error transmission rate based on PDU set;

[0266] Throughput based on PDU sets;

[0267] Data volume based on PDU set;

[0268] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0269] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0270] Optionally, the first device is a terminal or a base station.

[0271] In one implementation, if the first device is a terminal, the second device is a base station.

[0272] In another implementation, if the first device is a base station, the second device is an OAM device or a TCE.

[0273] In this embodiment of the application, the second device can obtain XR service performance based on the measurement result, thereby determining whether the key network indicators meet the requirements of XR services, and then scheduling XR services, which helps network optimization and can achieve better network performance and XR service performance.

[0274] In at least one embodiment of this application, the latency information based on the PDU set includes at least one of the following:

[0275] The first delay is the average delay of multiple data packets within a PDU set;

[0276] The second delay is the average of the first delays of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB); N1 is a positive integer.

[0277] The third delay is the delay of a PDU set;

[0278] The fourth delay is the average of the third delays of a QoS flow or a set of N2 PDUs within a DRB; N2 is a positive integer.

[0279] The third delay is the difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set.

[0280] In one implementation, the first delay is equal to the sum of the delays of all data packets in a PDU set divided by the number of data packets in that PDU set.

[0281] In another implementation, the second delay is equal to the sum of the delays of all packets in a PDU set divided by the number of packets in the PDU set to obtain the first delay of the PDU set. Then, the first delay of all PDU sets in a QoS flow or a DRB is taken as the (arithmetic) average.

[0282] In another implementation, the moment of receiving the last data packet in the PDU set can also be understood as the moment when all data packets in the PDU set have been transmitted, or the moment when all data packets in the PDU set have been received.

[0283] In another implementation, the fourth delay is equal to the sum of the third delays of a QoS flow or all PDU sets within a DRB, divided by the number of PDU sets within that QoS flow or DRB, and then taken as the (arithmetic) average.

[0284] As an optional embodiment, N1 and / or N2 may take any of the following values:

[0285] The number of PDU sets included in a QoS flow or a DRB;

[0286] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0287] The number of PDU sets included in a QoS flow or a DRB within a measurement period.

[0288] For example, if N1 is the number of PDU sets included in a QoS flow or a DRB during a data burst, then the second delay is: the average of the first delay of the PDU sets included in a QoS flow or a DRB during a data burst.

[0289] For example, if N1 is the number of PDU sets included in a QoS flow or a DRB within the measurement time, then the second delay is: the average of the first delay of a QoS flow or a DRB included in the measurement time.

[0290] For example, if N2 is the number of PDU sets included in a QoS flow or a DRB during a data burst, then the fourth delay is: the average of the third delay of the PDU sets included in a QoS flow or a DRB during a data burst.

[0291] For example, if N2 is the number of PDU sets included in a QoS flow or a DRB within the measurement time, then the fourth delay is: the average of the third delay of a QoS flow or a DRB included in the measurement time.

[0292] In at least one embodiment of this application, the error transmission rate based on the PDU set includes at least one of the following:

[0293] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0294] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB; M0 is a positive integer.

[0295] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB; M1 is a positive integer.

[0296] The fourth loss rate is the PDU set loss rate of a QoS flow or a DRB containing M2 PDU sets; where M2 is a positive integer.

[0297] A fifth loss rate, which indicates whether a set of PDUs has been lost. For example, a fifth loss rate of 1 (or 100%) indicates that a set of PDUs has been lost; as another example, a fifth loss rate of 0 (or 0%) indicates that a set of PDUs has not been lost.

[0298] In one implementation, the first loss rate is: the number of packets lost in a PDU set under non-congested and / or congested conditions, divided by the total number of packets in that PDU set.

[0299] In another implementation, the third loss rate is: the ratio of PDUs lost in a PDU set under non-congested and / or congested conditions, to obtain the packet loss rate of each PDU set, and then the (arithmetic) average of the packet loss rates of all PDU sets in a QoS flow or a DRB is taken.

[0300] In another implementation, the fourth loss rate is: the number of PDU sets lost in a QoS flow or a DRB under non-congested and / or congested conditions, divided by the total number of all PDU sets in that QoS flow or DRB.

[0301] Optionally, M1 and / or M2 can take any of the following values:

[0302] The number of PDU sets included in a QoS flow or a DRB;

[0303] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0304] The number of PDU sets included in a QoS flow or a DRB within a measurement period.

[0305] In one implementation, M1 is the number of PDU sets included in a QoS flow or a DRB during a data burst. The third loss rate is the average packet loss rate of the PDU set within a QoS flow or a DRB in a data burst; for example, the number of packets lost in a data burst divided by the total number of packets in the data burst.

[0306] In another implementation, M2 represents the number of PDU sets included in a QoS flow or a DRB during a data burst. The fourth loss rate is then the PDU set loss rate of a QoS flow or a DRB within a data burst. For example, the PDU set loss rate of each PDU set is obtained by dividing the number of lost packets in each PDU set by the total number of packets in each PDU set. The average PDU set loss rate of all PDU sets in the data burst is then averaged (arithmetic mean) to obtain the average PDU set loss rate in the data burst.

[0307] Optionally, M0 can take any of the following values:

[0308] The number of packets included in a QoS flow or a DRB;

[0309] The number of packets included in a QoS flow or a DRB during a data burst;

[0310] The number of packets included in a QoS flow or a DRB within a measurement period.

[0311] In an optional embodiment of this application, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0312] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0313] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0314] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0315] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0316] In another optional embodiment of this application, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following:

[0317] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0318] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0319] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0320] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0321] Optionally, the measurement results may also include:

[0322] Identification information of the PDU set of packets dropped due to association.

[0323] For example, the identification information is a PDU set SN (serial number) identifier pair. For example, PDU set1 and PDU set2 are a pair and have an associated relationship.

[0324] In at least one embodiment of this application, when the PDU set has integrity processing information (PDU Set Integrated Handling Information, PSIHI), the M1 PDU sets do not include PDU sets lost due to integrity processing information; for example, when reporting the third loss rate per QoS flow or per DRB, PDU sets lost due to PSIHI indication are not included.

[0325] Alternatively, if the PDU set has integrity processing information (PDU Set Integrated Handling Information, PSIHI), the M1 PDU sets include PDU sets lost due to integrity processing information; for example, when reporting the third loss rate per QoS flow or per DRB, PDU sets lost due to PSIHI indication are included.

[0326] In at least one optional embodiment of this application, where the PDU set has PDU SetIntegrated Handling Information (PSIHI), the measurement result further includes at least one of the following:

[0327] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information; for example, the PDU set is identified by the PDU set SN;

[0328] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0329] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0330] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0331] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0332] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0333] As an optional embodiment, the throughput based on the PDU set is the ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst. If the buffer is empty, it does not include data transmitted within a slot.

[0334] As another optional embodiment, the data volume based on the PDU set includes at least one of the following:

[0335] The number of bits that a QoS flow or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0336] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0337] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0338] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0339] In summary, in this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, thereby contributing to network optimization and achieving better network performance and XR service performance.

[0340] To better describe the measurement method provided in the embodiments of this application, several examples are given below.

[0341] Example 1

[0342] The data packet delay reported by the terminal or base station for the PDU set, including the first delay and / or the second delay;

[0343] The average DL PDU set delay per QoS flow or per DRB includes the average air interface DL delay, the average DL RLC layer (DU) delay, the average F1-U delay, and the average CU-UP delay, which are added together.

[0344] Average air interface DL delay refers to the delay of each PDU set within a QoS flow or DRB, calculated as the sum of the time taken for the last RLC SDU packet to be sent to the UE and receive the ACK from the UE, minus the time it takes for the RLC SDU to reach the MAC layer. This sum is divided by the number of RLC SDU packets successfully transmitted to the UE within that PDU set. This yields the first delay for each PDU set. The second delay is then calculated by averaging the delays of each PDU set, which is the sum of the delays of all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB. A PDU set can be identified using a PDU Set SN.

[0345] The average DL RLC layer (DU) delay is calculated as follows: the sum of all data packets in each PDU set within a QoS flow or DRB (the time it takes for the last RLC SDU packet to be scheduled to be sent to the MAC layer via the air interface, minus the time it takes for that packet to arrive at the RLC ingress F1-U terminal), divided by the number of RLC SDUs in that PDU set that successfully arrive at the RLC ingress F1-U terminal, yields the delay for each PDU set (the first delay). The second delay is then calculated by averaging the delays of each PDU set, i.e., the sum of the delays of all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB. A PDU set can be identified using a PDU Set SN.

[0346] The average F1-U delay is calculated as follows: the time it takes to receive a GTP packet from the gNB-DU at the upper-layer GTP inlet minus the time it takes to send that GTP packet back to the gNB-DU from the upper-layer GTP outlet, minus the DU's feedback delay, and then divided by 2. This gives the average delay for each data packet. The delay (first delay) for each PDU set is calculated by multiplying the number of data packets by the average delay for each data packet. Alternatively, the second delay can be calculated by summing the delays of all PDU sets in a QoS flow or DRB and dividing by the total number of PDU sets contained in that QoS flow or DRB. The delay of each PDU set can be identified by its PDU Set SN.

[0347] The average CU-UP delay is calculated as follows: the sum of all packets in each PDU set within a QoS flow or DRB (calculated by subtracting the time it takes for the packet to arrive at the NG-U ingress IP address from the time it takes to send the PDCP SDU to the DU at the PDCP layer egress of F1-U / Xn-U), divided by the number of PDCP SDUs that successfully arrive at the NG-U ingress IP address within that PDU set, yields the delay for each PDU set (the first delay). The second delay is then calculated by averaging the delays of each PDU set, which is the sum of the delays of all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB. A PDU set can be identified using a PDU Set SN.

[0348] The average UL PDU set delay includes the average UL PDCP packet delay, the average air interface delay, the average RLC packet delay, the average UL F1-U delay, and the average PDCP reordering delay.

[0349] The average UL PDCP packet delay is calculated as follows: the sum of all data packets in each PDU set within a QoS flow or DRB (calculated from the UL authorization available for transmitting the data packets, minus the data packets arriving at the PDCP upper layer SAP), divided by the number of data packets successfully received by PDCP in that PDU set, yielding the first delay for each PDU set. The second delay is obtained by averaging the delays of each PDU set, i.e., the sum of delays for all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB. A PDU set can be identified using a PDU Set SN.

[0350] The average air interface delay is calculated as follows: the sum of all data packets in each PDU set within a QoS flow or DRB (the time when the UL MAC SDU is successfully sent to the RLC minus the time when the UL MAC SDU is scheduled at the MAC layer based on the provided scheduling authority), divided by all UL MAC SDU data packets in that PDU set, yields the delay for each PDU set (the first delay). The average delay for each PDU set is then calculated as the sum of the delays for all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB, yielding the second delay. A PDU set can be identified using a PDU Set SN.

[0351] The average RLC packet delay is calculated as follows: the sum of all packets in each PDU set within a QoS flow or DRB (based on the time the UL RLC SDU is sent to the PDCP or CU-UP), divided by the total number of UL RLC SDU packets in that PDU set, yields the delay for each PDU set (the first delay). The second delay is then calculated by averaging the delays of each PDU set, which is the sum of the delays of all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB. A PDU set can be identified using a PDU Set SN.

[0352] The average UL F1-U delay is the same as the average DL F1-U delay, so it will not be repeated here.

[0353] The average PDCP reordering delay is calculated as follows: the sum of all data packets in each PDU set within a QoS flow or DRB (the time when the UL PDCP PDU is sent to the upper-layer SAP, minus the time when the UL PDCP SDU is received by the PDCP), divided by the total number of UL PDCP SDUs received in that PDU set, yields the delay for each PDU set (the first delay). The average delay for each PDU set is then calculated as the sum of the delays of all PDU sets within a QoS flow or DRB, divided by the total number of PDU sets contained in that QoS flow or DRB, yielding the second delay. PDU sets can be identified using PDUset SN.

[0354] Optionally, the collection period for the above measurement results can be the length of the data burst, that is, from the start of the data burst to the end of the data burst, and then reported to the base station, OAM, or TCE. For example, to calculate the average PDU set delay per QoS flow or per DRB, the (arithmetic) average of the delay of each PDU set transmitted by the QoS flow or the DRB within the data burst can be taken, that is, the sum of the delays of each PDU set transmitted by the QoS flow or the DRB within the data burst, divided by the number of PDU sets transmitted by the QoS flow or the DRB within the data burst.

[0355] The aforementioned UL or DL ​​measurements can also use a data burst as a Layer 2 measurement reporting condition; that is, when the data burst ends, the UE or base station reports the collected measurement results. Alternatively, the data burst period can be used as the L2 measurement reporting period. The data burst period length is from the first data packet of the data burst to the receipt of the end of data burst indication. Of course, the aforementioned UL / DL measurement results can also be triggered for reporting or statistical analysis using existing methods, without specific limitations here.

[0356] The first part of the above average PDU set delay (first delay) is the delay of each PDU set, which is the per PDU set delay (second delay). The second delay is also the sum of the above four average air interface delay, average RLC layer (DU) delay, average F1-U delay and average CU-UP delay.

[0357] Example 2

[0358] The UE / base station reports the delay of the PDU set, such as the third delay and / or the fourth delay;

[0359] The time when all data packets of a PDU set are transmitted (the time when all data packets of a PDU set are received) is subtracted from the time when the first data packet of the PDU set is received to obtain the PDU set delay (third delay) of each PDU set. Then, the PDU set delay of each PDU set in a QoS flow or a DRB is summed and divided by the number of all PDU sets in the QoS flow or a DRB to obtain the (arithmetic) average, which gives the fourth delay.

[0360] Example 3

[0361] The UE / base station reports the transmission error rate, including at least one of the following:

[0362] The first packet loss rate, the packet loss rate per PDU set (also known as the DL air interface packet loss rate): the number of packets lost in a PDU set under non-congested and / or congested conditions, divided by the total number of packets in the PDU set. All packets in a PDU set can be interpreted as packets successfully transmitted over the air interface and actively acknowledged, plus packets transmitted over the air interface but not actively acknowledged and not retransmitted. If any, add packets transmitted over the air interface and actively acknowledged, but whose RLC SDU DL delay exceeds the delay threshold.

[0363] For separation scenarios, the following also needs to be considered:

[0364] UL PDCP SDU packet loss rate: The number of PDCP SDUs in a PDU set that were not successfully received by the upper layer (which can be represented by the number of missing UL PDCP sequence numbers), divided by the total number of UL PDCP sequence numbers in that PDU set.

[0365] UL F1-U packet loss rate: The number of PDCP SDUs in a PDU set that were not successfully received by the upper layer (which can be represented by the number of missing UL GTP sequence numbers) divided by the total number of UL GTP sequence numbers in the PDU set.

[0366] UL F1-U packet loss rate: The number of PDCP SDUs in a PDU set that were not successfully received by the lower layer (which can be represented by the number of missing DL GTP sequence numbers), divided by the total number of DL GTP sequence numbers in the PDU set.

[0367] For PDU sets with PSIHI indication, if one packet is lost, all other packets in the PDU set will also be dropped, resulting in a 100% packet loss rate for that PDU set. Optionally, the presence of PSIHI indication in the PDU set can be reported.

[0368] The third packet loss rate, the average packet loss rate per QoS flow or per DRB: Based on the packet loss rate per PDU set mentioned above, that is, the packet loss rate of each PDU set, the average packet loss rate of all PDU sets in a QoS flow or a DRB is taken (arithmetic mean). That is, the sum of the packet loss rates of each PDU set is divided by the total number of all PDU sets contained in a QoS flow or a DRB to obtain the average packet loss rate of a QoS flow or a DRB.

[0369] For PDU sets with PSIHI indications, these PDU sets are not included in the average packet loss rate per QoS flow or per DRB. That is, neither the numerator (the sum of packet loss rates for each PDU set) nor the denominator (the total number of PDU sets contained in a QoS flow or DRB) counts towards the average packet loss rate for that type of PDU set. For example, if a DRB or QoS flow has 100 PDU sets, 20 of which have PSIHI indications, and 18 of these PDU sets experience packet loss, then the third packet loss rate under this scheme is calculated as the sum of the packet loss rates of (100-18) PDU sets divided by (100-18). Optionally, it is necessary to report the identifiers of PDU sets that are excluded from the average packet loss rate per QoS flow or per DRB due to PSIHI. Alternatively, these PDU sets can be included in the average packet loss rate per QoS flow or per DRB. For example, a DRB or a QoS flow has 100 PDU sets, of which 20 PDU sets have PSIHI indications, and 18 of these PDU sets with PSIHI indications experienced packet loss. Under this scheme, the third packet loss rate = the sum of the packet loss rates of the 100 PDU sets divided by 100, where at least 18 sets have an average packet loss rate of 100%. Optionally, it is also necessary to report the PDU set whose packet loss rate is 100% due to PSIHI, and the proportion of this 100% packet loss rate relative to the total number of PDU sets in a QoS flow or DRB, for example, 18 / 100.

[0370] The fourth loss rate, per QoS flow or per DRB, is the PDU set loss rate: the number of PDU sets dropped in a QoS flow or DRB under non-congested and / or congested conditions, divided by the total number of PDU sets in that QoS flow or DRB. For example, if a DRB or QoS flow has 100 PDU sets, and 20 of them are lost, with 18 of the lost packets having PSIHI indications and 30 of the unlost packets having PSIHI indications, then the fourth loss rate in this scenario is 20 / 100.

[0371] For PDU sets with PSIHI indications, optionally, the proportion of PSIHI packets needs to be reported, including the proportion of lost PDU sets containing PSIHI (e.g., 18 / 20), the proportion of all PDU sets containing PSIHI (e.g., 38 / 100), and the proportion of packets without PSIHI (e.g., 30 / 80). This type of PDU set can also be included in the PDU set loss rate per QoS flow or per DRB (e.g., 36 / 100). Optionally, the PDU set identifier of the lost PDU set due to PSIHI should also be reported, as well as the proportion of packet loss of that PDU set due to PSIHI out of the total number of PDU sets included in a QoS flow or DRB (e.g., 18 / 100).

[0372] The fifth is the loss rate. The measurement result can only be lost or not lost, which can be represented by 0 and 1, or 0% and 100%. This method indicates whether the PDU set has been lost.

[0373] Optionally, the measurement collection period can be the length of the data burst, that is, the statistics start from the beginning of the data burst and continue until the end of the data burst, and then be reported to the base station / OAM / TCE.

[0374] For example, to calculate the packet loss rate of a QoS flow or per DRB, you can divide the number of packets lost in the databurst by the total number of packets in the databurst.

[0375] For example, to calculate the average packet loss rate per QoS flow or per DRB, you can divide the number of lost packets in each PDU set within the data burst time of the QoS flow or DRB by the total number of packets in each PDU set to get the packet loss rate of each PDU set. Then, take the average (arithmetic mean) of the packet loss rates of all PDU sets in the data burst to get the average packet loss rate in the data burst.

[0376] For example, to calculate the PDU set loss rate per QoS flow or per DRB, you can divide the number of PDU sets lost in the data burst of that QoS flow or DRB by the total number of PDU sets in the data burst of that QoS flow or DRB.

[0377] Optionally, a data burst can be used as an L2 measurement reporting condition, meaning the UE / base station reports the collected measurements when the data burst ends. Alternatively, the data burst period can be used as the L2 measurement reporting period. The data burst period length is from the first data packet of the data burst to the receipt of the end of data burst indication. Of course, the above UL / DL measurement results can also be triggered for reporting or statistical analysis in traditional ways, including using OOC as a trigger event, measurement as a trigger event, or a period set by the network implementation, etc., without specific limitations here.

[0378] Example 4

[0379] For scenarios where multiple QoS flows within a DRB are correlated, the UE / base station reported loss rate

[0380] When reporting the packet loss rate per DRB, packets dropped due to PDU set association are ignored; only packets lost by the packet set itself are considered.

[0381] The number of lost data packets is calculated by dividing the total number of data packets in the DRB. For example, if the DRB has 100 data packets, 10 packets in PDU set 1 are all lost, 15 packets in PDU set 2 are related to each other, and 3 out of 20 packets in PDU set 3 are lost, the second loss rate under this scheme is (10+3) / 100. Optionally, the PDU set identifiers that caused the data packet loss due to related relationships are reported.

[0382] The number of packets lost is calculated by dividing the total number of packets in the DRB by the number of packets lost due to PDU set associations. Optionally, the PDU set identifiers that caused packet loss due to associations are reported. For example, if the DRB has 100 packets, 10 packets in PDU set 1 are all lost, 15 packets in PDU set 2 are associated with PDU set 2, and 3 out of 20 packets in PDU set 3 are lost, then the second loss rate under this scheme is (10+3) / 85.

[0383] Alternatively, packet loss due to association can be included in the per-DRB packet loss rate. For example, if a DRB has 100 packets, 10 packets in PDU set 1 are all lost, 15 packets in PDU set 2 are associated with PDU set 1, and 3 out of 20 packets in PDU set 3 are lost, the second loss rate in this scheme is 28 / 100. Optionally, it is also necessary to report the lost PDU set identifier pairs in other PDU sets due to PDU set association, as well as the proportion of packet loss due to PDU set association to the total number of packets in a DRB (e.g., 15 / 100).

[0384] When reporting PDU set loss rates per QoS flow or per DRB, PDU sets dropped due to PDU set associations are ignored; only PDU sets dropped by the flow itself are considered. The expression can be at least one of the following:

[0385] The number of PDU sets dropped (excluding those dropped due to association) is calculated by dividing the total number of PDU sets in the QoS flow or DRB by the total number of PDU sets in that flow. Optionally, pairs of PDU set identifiers that caused packet loss due to association are reported. For example, if 6 PDU sets 1-6 are lost, and PDU sets 7-12 are associated with PDU sets 1-6, then 12 PDU sets are lost. Additionally, 4 unrelated PDU sets 13-16 are also lost, for a total of 100 PDU sets in this QoS or DRB. Under this scheme, the fourth loss rate is 4 / 100.

[0386] The number of PDU sets dropped (excluding those dropped due to association) is divided by the total number of PDU sets in the QoS flow or DRB, minus the number of PDU sets dropped due to PDU set association. For example, if 6 PDU sets 1-6 are lost, and PDU sets 7-12 are associated with PDU sets 1-6, then 12 PDU sets are lost. Additionally, 4 unrelated PDU sets 13-16 are also lost, for a total of 100 PDU sets in this QoS or DRB. Under this scheme, the fourth loss rate is 4 / 96. Optionally, report the PDU set identifiers that caused packet loss due to association.

[0387] Alternatively, the PDU set loss rate per QoS flow or per DRB can be calculated based on the PDU sets dropped due to association relationships. For example, if 6 PDU sets 1-6 are lost, and PDU sets 7-12 are associated with PDU sets 1-6, then 12 PDU sets are lost. Additionally, 4 unassociated PDU sets 13-16 are also lost, for a total of 100 PDU sets in this QoS or DRB. Under this scheme, the fourth loss rate equals 16 / 100. Optionally, it is also necessary to report the PDU set identifier pairs that caused other PDU sets to be lost due to PDU set association relationships, as well as the number of PDU set association relationships that caused the PDU sets to be dropped, divided by the proportion of the total number of PDU sets contained in a QoS flow or DRB (e.g., 6 / 100).

[0388] In summary, in this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, thereby contributing to network optimization and achieving better network performance and XR service performance.

[0389] like Figure 3 As shown, this application embodiment also provides a first device, including a memory 320, a transceiver 310, and a processor 300:

[0390] The memory 320 is used to store computer programs; the transceiver 310 is used to send and receive data under the control of the processor 300; the processor 300 is used to read the computer program in the memory 320 and perform the following operations:

[0391] Perform measurements and obtain measurement results; the measurement results include at least one of the following:

[0392] Delay information based on Protocol Data Unit (PDU) sets;

[0393] Error transmission rate based on PDU set;

[0394] Throughput based on PDU sets;

[0395] The amount of data based on the PDU set.

[0396] As an optional embodiment, the latency information based on the PDU set includes at least one of the following:

[0397] The first delay is the average delay of multiple data packets within a PDU set;

[0398] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0399] The third delay is the delay of a PDU set;

[0400] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0401] The third time delay is:

[0402] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0403] N1 and N2 are positive integers.

[0404] As an optional embodiment, the error transmission rate based on the PDU set includes at least one of the following:

[0405] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0406] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0407] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB.

[0408] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0409] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0410] Where M0, M1, and M2 are positive integers.

[0411] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0412] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0413] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0414] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0415] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0416] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following values:

[0417] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0418] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0419] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0420] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0421] As an optional embodiment, the measurement results further include:

[0422] Identification information of the PDU set of packets dropped due to association.

[0423] As an optional embodiment, the target parameter can take any of the following values:

[0424] The number of PDU sets included in a QoS flow or a DRB;

[0425] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0426] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0427] The target parameters are N1, N2, M1 and / or M2.

[0428] As an optional embodiment, M0 can take any of the following values:

[0429] The number of packets included in a QoS flow or a DRB;

[0430] The number of packets included in a QoS flow or a DRB during a data burst;

[0431] The number of packets included in a QoS flow or a DRB within a measurement period.

[0432] As an optional embodiment, if the PDU set has integrity processing information,

[0433] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0434] or,

[0435] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0436] As an optional embodiment, if the PDU set has integrity processing information, the measurement result further includes at least one of the following:

[0437] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0438] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0439] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0440] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0441] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0442] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0443] As an optional embodiment, the throughput based on the PDU set is:

[0444] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0445] As an optional embodiment, the amount of data based on the PDU set includes at least one of the following:

[0446] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0447] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0448] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0449] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0450] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0451] The measurement results are sent to a second device; the second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0452] As an optional embodiment, the processor is also configured to read a computer program from the memory and perform the following operations:

[0453] After the configured statistical collection period ends, the measurement results are sent to the second device; wherein the duration of the configured statistical collection period is the duration of a data burst.

[0454] Among them, Figure 3In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 300) and memory (memory 320). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 310 can be multiple elements, including transmitters and receivers, providing units for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 300 is responsible for managing the bus architecture and general processing, and the memory 3320 can store data used by the processor 300 during operation.

[0455] The processor 300 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0456] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0457] It should be noted that the first device provided in the embodiments of this application is a device capable of performing the above measurement method. Therefore, all embodiments of the above measurement method are applicable to this device and can achieve the same or similar beneficial effects, which will not be repeated here.

[0458] like Figure 4 As shown in the embodiments of this application, a second device is also provided, including a memory 420, a transceiver 410, and a processor 400:

[0459] The memory 420 is used to store computer programs; the transceiver 410 is used to send and receive data under the control of the processor 400; the processor 400 is used to read the computer programs in the memory 420 and perform the following operations:

[0460] Receive measurement results sent by the first device, wherein the measurement results include at least one of the following:

[0461] Delay information based on Protocol Data Unit (PDU) sets;

[0462] Error transmission rate based on PDU set;

[0463] Throughput based on PDU sets;

[0464] Data volume based on PDU set;

[0465] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0466] As an optional embodiment, the latency information based on the PDU set includes at least one of the following:

[0467] The first delay is the average delay of multiple data packets within a PDU set;

[0468] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0469] The third delay is the delay of a PDU set;

[0470] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0471] The third time delay is:

[0472] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0473] N1 and N2 are positive integers.

[0474] As an optional embodiment, the error transmission rate based on the PDU set includes at least one of the following:

[0475] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0476] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0477] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB.

[0478] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0479] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0480] Where M0, M1, and M2 are positive integers.

[0481] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0482] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0483] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0484] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0485] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0486] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following values:

[0487] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0488] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0489] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0490] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0491] As an optional embodiment, the measurement results further include:

[0492] Identification information of the PDU set of packets dropped due to association.

[0493] As an optional embodiment, the target parameter can take any of the following values:

[0494] The number of PDU sets included in a QoS flow or a DRB;

[0495] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0496] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0497] The target parameters are N1, N2, M1 and / or M2.

[0498] As an optional embodiment, M0 can take any of the following values:

[0499] The number of packets included in a QoS flow or a DRB;

[0500] The number of packets included in a QoS flow or a DRB during a data burst;

[0501] The number of packets included in a QoS flow or a DRB within a measurement period.

[0502] As an optional embodiment, if the PDU set has integrity processing information,

[0503] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0504] or,

[0505] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0506] As an optional embodiment, if the PDU set has integrity processing information, the measurement result further includes at least one of the following:

[0507] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0508] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0509] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0510] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0511] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0512] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0513] As an optional embodiment, the throughput based on the PDU set is:

[0514] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0515] As an optional embodiment, the amount of data based on the PDU set includes at least one of the following:

[0516] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0517] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0518] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0519] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0520] Among them, Figure 4 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 400) and memory (memory 420). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 410 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over transmission media, including wireless channels, wired channels, optical fibers, etc. The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 can store data used by the processor 400 during operation.

[0521] The processor 400 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0522] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0523] It should be noted that the second device provided in this application embodiment is a device capable of performing the above measurement method. Therefore, all embodiments of the above measurement method are applicable to this device and can achieve the same or similar beneficial effects, which will not be repeated here.

[0524] like Figure 5 As shown in the illustration, this application also provides a measuring device applied to a first device, the device comprising:

[0525] Measurement unit 501 is used to perform measurements and obtain measurement results; the measurement results include at least one of the following:

[0526] Delay information based on Protocol Data Unit (PDU) sets;

[0527] Error transmission rate based on PDU set;

[0528] Throughput based on PDU sets;

[0529] The amount of data based on the PDU set.

[0530] As an optional embodiment, the latency information based on the PDU set includes at least one of the following:

[0531] The first delay is the average delay of multiple data packets within a PDU set;

[0532] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0533] The third delay is the delay of a PDU set;

[0534] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0535] The third time delay is:

[0536] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0537] N1 and N2 are positive integers.

[0538] As an optional embodiment, the error transmission rate based on the PDU set includes at least one of the following:

[0539] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0540] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0541] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB.

[0542] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0543] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0544] Where M0, M1, and M2 are positive integers.

[0545] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0546] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0547] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0548] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0549] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0550] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following values:

[0551] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0552] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0553] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0554] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0555] As an optional embodiment, the measurement results further include:

[0556] Identification information of the PDU set of packets dropped due to association.

[0557] As an optional embodiment, the target parameter can take any of the following values:

[0558] The number of PDU sets included in a QoS flow or a DRB;

[0559] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0560] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0561] The target parameters are N1, N2, M1 and / or M2.

[0562] As an optional embodiment, M0 can take any of the following values:

[0563] The number of packets included in a QoS flow or a DRB;

[0564] The number of packets included in a QoS flow or a DRB during a data burst;

[0565] The number of packets included in a QoS flow or a DRB within a measurement period.

[0566] As an optional embodiment, if the PDU set has integrity processing information,

[0567] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0568] or,

[0569] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0570] As an optional embodiment, if the PDU set has integrity processing information, the measurement result further includes at least one of the following:

[0571] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0572] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0573] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0574] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0575] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0576] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0577] As an optional embodiment, the throughput based on the PDU set is:

[0578] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0579] As an optional embodiment, the amount of data based on the PDU set includes at least one of the following:

[0580] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0581] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0582] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0583] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0584] As an optional embodiment, the apparatus further includes:

[0585] The transmitting unit is used to transmit the measurement results to the second device; the second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0586] As an optional embodiment, the transmitting unit includes:

[0587] A sending subunit is used to send the measurement results to the second device after the configured statistical collection period ends; wherein the duration of the configured statistical collection period is the duration of a data burst.

[0588] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0589] It should be noted that the device provided in this application embodiment is a device capable of performing the above measurement method. Therefore, all embodiments of the above measurement method are applicable to this device and can achieve the same or similar beneficial effects, which will not be repeated here.

[0590] like Figure 6 As shown, this application embodiment also provides a measuring device, applied to a second device, comprising:

[0591] The receiving unit 601 is configured to receive measurement results sent by the first device, the measurement results including at least one of the following:

[0592] Delay information based on Protocol Data Unit (PDU) sets;

[0593] Error transmission rate based on PDU set;

[0594] Throughput based on PDU sets;

[0595] Data volume based on PDU set;

[0596] The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

[0597] As an optional embodiment, the latency information based on the PDU set includes at least one of the following:

[0598] The first delay is the average delay of multiple data packets within a PDU set;

[0599] The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB).

[0600] The third delay is the delay of a PDU set;

[0601] The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB;

[0602] The third time delay is:

[0603] The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set;

[0604] N1 and N2 are positive integers.

[0605] As an optional embodiment, the error transmission rate based on the PDU set includes at least one of the following:

[0606] First loss rate, the first loss rate is the packet loss rate within the PDU set;

[0607] The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB.

[0608] The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB.

[0609] The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB.

[0610] The fifth loss rate is used to indicate whether a set of PDUs has been lost;

[0611] Where M0, M1, and M2 are positive integers.

[0612] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the second loss rate can be any of the following values:

[0613] The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB.

[0614] The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association.

[0615] The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association.

[0616] The ratio of the number of packets dropped due to association within a DRB to the first number.

[0617] As an optional embodiment, when the QoS flows corresponding to multiple PDU sets in a DRB are associated, the fourth loss rate can be any of the following values:

[0618] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow.

[0619] The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association.

[0620] The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association.

[0621] The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

[0622] As an optional embodiment, the measurement results further include:

[0623] Identification information of the PDU set of packets dropped due to association.

[0624] As an optional embodiment, the target parameter can take any of the following values:

[0625] The number of PDU sets included in a QoS flow or a DRB;

[0626] The number of PDU sets included in a QoS flow or a DRB during a data burst;

[0627] The number of PDU sets included in a QoS flow or a DRB within the measurement time period;

[0628] The target parameters are N1, N2, M1 and / or M2.

[0629] As an optional embodiment, M0 can take any of the following values:

[0630] The number of packets included in a QoS flow or a DRB;

[0631] The number of packets included in a QoS flow or a DRB during a data burst;

[0632] The number of packets included in a QoS flow or a DRB within a measurement period.

[0633] As an optional embodiment, if the PDU set has integrity processing information,

[0634] The M1 PDU sets do not include PDU sets lost due to integrity processing information;

[0635] or,

[0636] The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

[0637] As an optional embodiment, if the PDU set has integrity processing information, the measurement result further includes at least one of the following:

[0638] The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information;

[0639] The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB.

[0640] The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information;

[0641] The proportion of PDU sets containing integrity processing information among the lost PDU sets;

[0642] The proportion of PDUs containing integrity processing information within a QoS flow or a DRB;

[0643] The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

[0644] As an optional embodiment, the throughput based on the PDU set is:

[0645] The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

[0646] As an optional embodiment, the amount of data based on the PDU set includes at least one of the following:

[0647] The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst;

[0648] The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB;

[0649] The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst;

[0650] The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

[0651] In this embodiment of the application, the first device performs measurements related to the PDU set and obtains measurement results. The measurement results include at least one of the following: latency information based on the PDU set, error transmission rate based on the PDU set, throughput based on the PDU set, and data volume based on the PDU set. This enables the second device to obtain XR service performance based on the measurement results, which helps to optimize the network and achieve better network performance and XR service performance.

[0652] It should be noted that the device provided in this application embodiment is a device capable of performing the above measurement method. Therefore, all embodiments of the above measurement method are applicable to this device and can achieve the same or similar beneficial effects, which will not be repeated here.

[0653] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0654] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0655] This application also provides a processor-readable storage medium storing a computer program. The computer program is used to cause the processor to execute the various processes described in the measurement method embodiments above, achieving the same technical effect. To avoid repetition, further details are omitted here. The processor-readable storage medium can be any available medium or data storage device accessible to the processor, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs), etc.).

[0656] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes in the measurement method embodiments described above and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0657] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0658] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0659] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0660] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0661] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A measurement method, characterized in that, The method includes: The first device performs a measurement and obtains a measurement result; the measurement result includes at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; The amount of data based on the PDU set.

2. The method according to claim 1, characterized in that, The latency information based on the PDU set includes at least one of the following: The first delay is the average delay of multiple data packets within a PDU set; The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB). The third delay is the delay of a PDU set; The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB; The third time delay is: The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set; N1 and N2 are positive integers.

3. The method according to claim 1, characterized in that, The error transmission rate based on the PDU set includes at least one of the following: First loss rate, the first loss rate is the packet loss rate within the PDU set; The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB. The third loss rate is the average packet loss rate within a QoS flow or a set of M1 PDUs in a DRB. The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB. The fifth loss rate is used to indicate whether a set of PDUs has been lost; Where M0, M1, and M2 are positive integers.

4. The method according to claim 3, characterized in that, When the QoS flows corresponding to multiple PDU sets in a DRB are related, the second loss rate can be any of the following: The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB. The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association. The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association. The ratio of the number of packets dropped due to association within a DRB to the first number.

5. The method according to claim 3, characterized in that, When the QoS flows corresponding to multiple PDU sets in a DRB are related, the fourth loss rate can be any of the following values: The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow. The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association. The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association. The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

6. The method according to claim 4 or 5, characterized in that, The measurement results also include: Identification information of the PDU set of packets dropped due to association.

7. The method according to claim 2 or 3, characterized in that, The target parameter can take any of the following values: The number of PDU sets included in a QoS flow or a DRB; The number of PDU sets included in a QoS flow or a DRB during a data burst; The number of PDU sets included in a QoS flow or a DRB within the measurement time period; The target parameters are N1, N2, M1 and / or M2.

8. The method according to claim 3, characterized in that, M0 can take any of the following values: The number of packets included in a QoS flow or a DRB; The number of packets included in a QoS flow or a DRB during a data burst; The number of packets included in a QoS flow or a DRB within a measurement period.

9. The method according to claim 3, characterized in that, If the PDU set contains integrity processing information, The M1 PDU sets do not include PDU sets lost due to integrity processing information; or, The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

10. The method according to claim 3, characterized in that, If the PDU set has integrity processing information, the measurement result also includes at least one of the following: The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information; The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB. The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information; The proportion of PDU sets containing integrity processing information among the lost PDU sets; The proportion of PDUs containing integrity processing information within a QoS flow or a DRB; The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

11. The method according to claim 1, characterized in that, The throughput based on the PDU set is: The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

12. The method according to claim 1, characterized in that, The amount of data based on the PDU set includes at least one of the following: The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst; The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB; The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst; The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: The first device sends the measurement result to the second device; the second device includes at least one of: a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

14. The method according to claim 13, characterized in that, The first device sends the measurement results to the second device, including: After the configured statistical collection period ends, the first device sends the measurement results to the second device; wherein the duration of the configured statistical collection period is the duration of a data burst.

15. A measurement method, characterized in that, The method includes: The second device receives measurement results sent by the first device, the measurement results including at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; Data volume based on PDU set; The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

16. The method according to claim 15, characterized in that, The latency information based on the PDU set includes at least one of the following: The first delay is the average delay of multiple data packets within a PDU set; The second delay is the average of the first delay of a Quality of Service (QoS) stream or a set of N1 PDUs within a Data Radio Bearer (DRB). The third delay is the delay of a PDU set; The fourth delay is the average of the third delay of a QoS flow or a set of N2 PDUs within a DRB; The third time delay is: The difference between the reception time of the last data packet in the PDU set and the reception time of the first data packet in the PDU set; N1 and N2 are positive integers.

17. The method according to claim 15, characterized in that, The error transmission rate based on the PDU set includes at least one of the following: First loss rate, the first loss rate is the packet loss rate within the PDU set; The second loss rate is the loss rate of M0 packets within a QoS flow or a DRB. The third loss rate is the average packet loss rate across a QoS flow or a set of M1 PDUs within a DRB. The fourth loss rate is the PDU set loss rate of an M2 PDU set within a QoS flow or a DRB. The fifth loss rate is used to indicate whether a set of PDUs has been lost; Where M0, M1, and M2 are positive integers.

18. The method according to claim 17, characterized in that, When the QoS flows corresponding to multiple PDU sets in a DRB are related, the second loss rate can be any of the following: The ratio of the number of packets lost within a DRB to a first number; where the first number is the total number of packets within the DRB. The ratio of the number of packets lost within a DRB to a second number; the second number is the difference between the total number of packets within the DRB and the number of packets dropped due to association. The ratio of the third quantity to the first quantity; the third quantity is the sum of the number of packets lost within a DRB and the number of packets dropped due to association. The ratio of the number of packets dropped due to association within a DRB to the first number.

19. The method according to claim 17, characterized in that, When the QoS flows corresponding to multiple PDU sets in a DRB are related, the fourth loss rate can be any of the following values: The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fourth quantity; where the fourth quantity is the total number of PDU sets within the DRB or QoS flow. The ratio of the number of PDU sets lost within a DRB or a QoS flow to a fifth quantity; the fifth quantity is the difference between the total number of PDU sets within the DRB and the number of PDU sets dropped due to association. The ratio of the sixth quantity to the fourth quantity; the sixth quantity is the sum of the number of PDU sets lost within a DRB or a QoS flow and the number of PDU sets dropped due to association. The ratio of the number of PDU sets dropped due to association within a DRB or a QoS flow to the fourth number.

20. The method according to claim 18 or 19, characterized in that, The measurement results also include: Identification information of the PDU set of packets dropped due to association.

21. The method according to claim 16 or 17, characterized in that, The target parameter can take any of the following values: The number of PDU sets included in a QoS flow or a DRB; The number of PDU sets included in a QoS flow or a DRB during a data burst; The number of PDU sets included in a QoS flow or a DRB within the measurement time period; The target parameters are N1, N2, M1 and / or M2.

22. The method according to claim 17, characterized in that, M0 can take any of the following values: The number of packets included in a QoS flow or a DRB; The number of packets included in a QoS flow or a DRB during a data burst; The number of packets included in a QoS flow or a DRB within a measurement period.

23. The method according to claim 17, characterized in that, If the PDU set contains integrity processing information, The M1 PDU sets do not include PDU sets lost due to integrity processing information; or, The M1 PDU sets include the PDU sets that were lost due to integrity processing information.

24. The method according to claim 17, characterized in that, If the PDU set has integrity processing information, the measurement result also includes at least one of the following: The first indication information of the PDU set is used to indicate that the PDU set was lost due to the presence of integrity processing information; The ratio of the number of PDU sets lost due to integrity processing information in a PDU set to the total number of PDU sets in a QoS flow or a DRB. The second indication information corresponding to the PDU set is used to indicate that the PDU set has integrity processing information; The proportion of PDU sets containing integrity processing information among the lost PDU sets; The proportion of PDUs containing integrity processing information within a QoS flow or a DRB; The proportion of PDUs with integrity processing information in the set of PDUs that have not been lost.

25. The method according to claim 15, characterized in that, The throughput based on the PDU set is: The ratio of the number of bits in a data burst of a QoS stream or DRB to the transmission time of a data burst.

26. The method according to claim 15, characterized in that, The amount of data based on the PDU set includes at least one of the following: The number of bits that a QoS stream or a DRB sends from the centralized unit (CU) to the distributed unit (DU) during a data burst; The number of bits that an uplink PDCP PDU sends from the DU to the CU during a data burst in a QoS stream or a DRB; The number of bits that a QoS stream or a DRB enters the PDCP layer of the radio access node during a data burst; The number of bits that a QoS stream or a DRB leaves the PDCP layer of the radio access node during a data burst.

27. A first device, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Perform measurements and obtain measurement results; the measurement results include at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; The amount of data based on the PDU set.

28. A second device, characterized in that, Includes memory, transceiver, and processor: A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Receive measurement results sent by the first device, wherein the measurement results include at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; Data volume based on PDU set; The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

29. A measuring device, characterized in that, Applied to a first device, the device includes: A measurement unit for performing measurements and obtaining measurement results; the measurement results include at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; The amount of data based on the PDU set.

30. A measuring device, characterized in that, Applied to a second device, including: A receiving unit is configured to receive measurement results sent by a first device, the measurement results including at least one of the following: Delay information based on Protocol Data Unit (PDU) sets; Error transmission rate based on PDU set; Throughput based on PDU sets; Data volume based on PDU set; The second device includes at least one of a base station, an operation and maintenance management (OAM) device, and a terminal control unit (TCE).

31. A processor-readable storage medium, characterized in that, The processor-readable storage medium stores There is a program that causes the processor to perform the method according to any one of claims 1 to 14. Alternatively, the program may be used to cause the processor to perform the method according to any one of claims 15 to 26.

Images