Time delay measurement method and equipment

Abstract

The invention discloses a time delay measurement method and equipment. The time delay measurement method comprises: measuring data packets in a data radio bearer to generate a first measurement result, the data packets comprising a first type of data packets and a second type of data packets, the generation of the second type of data packets depending on the first type of data packets; the first measurement result at least comprises the time delay of the first type of data packets; wherein the time delay comprises any one or more of the following items: average time delay; minimum time delay; a maximum time delay; and carrying out excessive packet delay. The method is favorable for ensuring the QoS of the service.

Description

Technical Field

[0001] This application relates to a wireless communication system, and particularly to a method for delay measurement and measurement report reception, a terminal, and a base station. Background Art

[0002] The application scenarios of future wireless communication systems are becoming more and more diversified, and different application scenarios pose different performance requirements on the system. In order to meet the different performance requirements of various application scenarios, it was decided at the 72nd plenary session of 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) to conduct research on the new air interface technology (NR, New Radio) (or Fifth Generation, 5G). At the 75th plenary session of 3GPP RAN, the WI (Work Item) of NR was approved, and the standardization work of NR was started.

[0003] In communication, whether it is LTE (Long Term Evolution) or 5G NR, it involves the accurate reception of reliable information, optimized energy efficiency ratio, determination of information validity, flexible resource allocation, scalable system architecture, efficient non-access stratum information processing, low service interruption and disconnection rates, support for low power consumption, which is of great significance for the normal communication between base stations and user equipment (UE), for the reasonable scheduling of resources, and for the balancing of system loads. It can be said to be the cornerstone of high throughput, meeting the communication needs of various services, improving spectrum utilization, and improving service quality. It is indispensable for eMBB (enhanced Mobile BroadBand), URLLC (UltraReliable Low Latency Communication), or eMTC (enhanced Machine Type Communication). At the same time, in the IIoT (Industrial Internet of Things) in the industrial field, in V2X (Vehicular to X), in device-to-device communication, in communication on unlicensed spectrum, in user communication quality monitoring, in network planning and optimization, in NTN (Non Terrestrial Network) communication, in TN (Terrestrial Network) communication, in dual connectivity systems, in radio resource management and multi-antenna codebook selection, in signaling design, neighbor cell management, service management, and in beamforming, there are extensive requirements. The information transmission methods are divided into broadcast and unicast, and both methods are essential for the 5G system because they are very helpful in meeting the above requirements. The way for UE to connect to the network can be direct connection or through relay connection.

[0004] With the continuous increase in the scenarios and complexities of the system, higher requirements are put forward for reducing the interruption rate, reducing latency, enhancing reliability, enhancing system stability, for service flexibility, and for power saving. At the same time, compatibility between different system versions also needs to be considered during system design. Meanwhile, the types of services supported by the 5G system are becoming increasingly rich, and these new services also bring corresponding challenges to the system. To better meet the user experience, monitoring the quality of service (QoS) of services is one of them to better support the transmission of interactive services. Summary of the Invention

[0005] In a wireless communication system, QoS (Quality of Service) monitoring is an important issue because it is necessary for a communication network to guarantee the required QoS, so QoS needs to be monitored during the communication process. In QoS monitoring, monitoring delay is a very important aspect. In scenarios where delay needs to be measured and reported, how to measure packet delay is a problem that needs to be solved. Researchers have found that both uplink (UL) and downlink (DL) transmissions need to meet QoS requirements, including requirements for delay. For the downlink, the network can generally measure it by itself, while for the uplink, the UE needs to measure and report it.

[0006] The uplink transmission delay refers to the transmission delay of the uplink data packet of a terminal (such as a UE). The measurement locations of the uplink transmission delay are mainly distributed at the Packet Data Convergence Protocol (PDCP) layer of the terminal, the Media Access Control (MAC) layer on the network side, the Radio Link Control (RLC) layer on the network side, and the PDCP layer on the network side.

[0007] Researchers have also found that in order to guarantee service QoS, repair data packets (also known as repair packets or repair data packets) (for example, repair Protocol Data Units (repair PDUs)) are introduced in wireless communication to form a source block from a series of unmodified source packets. However, the introduction of repair data packets will have a certain impact on the measurement and calculation of packet delay, so further research is needed to more accurately reflect the QoS status during the communication process.

[0008] In view of the above problems, the present application provides a solution.

[0009] It should be noted that, without conflict, the embodiments and features in any node of the present application can be applied to any other node. Without conflict, the embodiments and features in the embodiments of the present application can be combined with each other arbitrarily. In addition, the method proposed in the present application can also be used to solve other problems in the communication system.

[0010] The present application discloses a method for measuring delay in a terminal, including:

[0011] Measure data packets in a data radio bearer (DRB) to generate a first measurement result. The data packets include first-type data packets and second-type data packets, and the generation of the second-type data packets depends on the first-type data packets.

[0012] The first measurement result at least includes the delay of the first-type data packets.

[0013] Wherein, the delay includes any one or more of the following: Average Delay; minimum delay, maximum delay, Excess Packet Delay.

[0014] As an embodiment, the problems to be solved by this application include: how to measure and determine the data packet delay in a DRB to monitor QoS and better support low-latency interactive services.

[0015] As an embodiment, in the prior art solution, a DRB usually only allows one type of data packet to exist. Therefore, when different types of data packets are allowed to appear in a DRB, the existing delay measurement solutions can no longer meet the current delay measurement requirements.

[0016] How to measure and determine the data packet delay in a DRB to monitor QoS and better support low-latency interactive services.

[0017] As an embodiment, the problems to be solved by this application include: when a DRB includes different types of data packets, how to monitor the data packet delay to more accurately evaluate QoS.

[0018] As an embodiment, the advantages of the above method include: when the data packets include different types (such as the first-type data packets and the second-type data packets), at least measure the delay of the first-type data packets, which can more accurately reflect the delay situation, more accurately monitor QoS, and better support interactive services.

[0019] As an embodiment, the advantages of the above method include: adapting to the development needs of technology and still being able to accurately monitor QoS when a DRB allows different types of data packets.

[0020] As an embodiment, the advantages of the above method include: it can better support XR services.

[0021] As an embodiment, the advantages of the above method include: it can be compatible with measuring different delays, which is beneficial to reducing system complexity.

[0022] As an embodiment, the first type of data packet and the second type of data packet belong to the same PDU set.

[0023] As a sub - embodiment of this embodiment, the advantage of the above - mentioned method is that it is beneficial to provide more detailed delay information according to different data packets in the same PDU set.

[0024] As a sub - embodiment of this embodiment, the advantage of the above - mentioned method is that it is beneficial to reduce complexity. The first type of data packet and the second type of data packet only need one PDCP entity for processing, such as for repair, without the need for coordination and communication between PDCP entities.

[0025] As a variant embodiment, the first type of data packet and the second type of data packet belong to different PDU sets.

[0026] As a sub - embodiment of this embodiment, the advantage of the above - mentioned method is that it is beneficial to statistically calculate delay information according to different PDU sets, so that the statistically calculated delay information can completely reflect the delay of some PDU sets.

[0027] As a sub - embodiment of this embodiment, the advantage of the above - mentioned method is that it can better distinguish the first type of data packet and the second type of data packet, especially when they need to be configured with different QoS.

[0028] As an embodiment, the data packet is a PDU packet. The first type of data packet included in the PDU packet is a first - type PDU packet, and the second type of data packet included in the PDU packet is a second - type PDU packet.

[0029] In one implementation manner, the PDU packet is a PDCP PDU.

[0030] In another implementation manner, the PDU packet is an RLC PDU.

[0031] In another implementation manner, the PDU packet is a MAC PDU.

[0032] As an embodiment, the data packet is an SDU packet. The first type of data packet included in the SDU packet is a first - type SDU packet, and the second type of data packet included in the SDU packet is a second - type SDU packet.

[0033] In one implementation manner, the SDU packet is a PDCP SDU.

[0034] In another implementation manner, the SDU packet is an RLC SDU.

[0035] In another embodiment, the SDU packet is a MAC SDU.

[0036] As an example, for each DRB, the terminal performs data packet delay measurement for uplink.

[0037] Specifically, according to one aspect of the present application, the first measurement result includes the delay of the second type of data packet.

[0038] As an example, the benefits provided by this method include: measuring the delays of the first type of data packet and the second type of data packet simultaneously, and obtaining the delay information of different types of data packets more comprehensively.

[0039] Specifically, according to one aspect of the present application, the delay reporting method further includes:

[0040] Sending a first measurement report, where the first measurement report includes the first measurement result.

[0041] As an example, the benefits provided by this method include: reporting the measurement result in the form of the first measurement report, so that the receiving party (such as the base station) can obtain the QoS status in the communication process more accurately.

[0042] As an example, the first measurement report only includes one of the average delay, minimum delay, maximum delay, and excessive packet delay.

[0043] As an example, the first measurement report only includes the average delay of the first type of data packet.

[0044] As an example, the first measurement report includes the average delays of the first type of data packet and the second type of data packet.

[0045] As an example, the first measurement report only includes the minimum delay of the first type of data packet.

[0046] As an example, the first measurement report includes the minimum delays of the first type of data packet and the second type of data packet.

[0047] As an example, the first measurement report only includes the maximum delay of the first type of data packet.

[0048] As an example, the first measurement report includes the maximum delays of the first type of data packet and the second type of data packet.

[0049] As an example, the first measurement report only includes the excessive packet delay of the first type of data packet.

[0050] As an embodiment, the first measurement result included in the first measurement report is the latency of the first type of data packet.

[0051] As an embodiment, the first measurement result included in the first measurement report is the latency of the first type of data packet and the latency of the second type of data packet.

[0052] Specifically, according to one aspect of the present application, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0053] As an embodiment, the second type of data packet is a repair data packet of the first type of data packet.

[0054] As an embodiment, the second type of data packet is generated from one or more of the first type of data packet.

[0055] As an embodiment, the first type of data packet and the second type of data packet are PDUs respectively, and each repair PDU in the second data packet is generated based on one or more PDUs in the first type of data packet.

[0056] In one embodiment, each PDU in the first type of data packet is a source PDU and is used to generate each repair PDU in the second data packet.

[0057] As an embodiment, the first type of data packet and the second type of data packet are SDUs respectively, and each repair SDU in the second data packet is generated based on one or more SDUs in the first type of data packet.

[0058] In one embodiment, the first type of SDU in the first type of data packet generates the second type of SDU in the second type of data packet.

[0059] As an embodiment, the first type of SDU generates the second type of SDU, which means that the second type of SDU used to repair the first type of SDU is generated based on the first type of SDU.

[0060] Specifically, according to one aspect of the present application, measuring the data packets in a data radio bearer includes:

[0061] Measuring the first type of data packet in the data radio bearer and measuring the second type of data packet; or,

[0062] Measuring the first type of data packet in the data radio bearer and ignoring the second type of data packet.

[0063] As an embodiment, the advantage of the above method is that when measuring the first type of data packet, it is possible to determine whether to measure the second type of data packet according to requirements, with high flexibility.

[0064] Specifically, according to one aspect of the present application, the first type of data packet is a PDCP source packet, and the delay measurement method includes:

[0065] Before measuring the data packets in a data radio bearer, receive a first measurement configuration, where the first measurement configuration includes a first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet;

[0066] After measuring the data packets in a data radio bearer, send a first measurement report, where the first measurement report includes at least the delay of the PDCP source packet.

[0067] As an embodiment, the advantages of the above method include: defining the first type of data packet as a PDCP source packet is easy to be compatible with the existing 3GPP standard protocol, and reporting the first measurement report is beneficial for the receiving party to accurately obtain the delay of the PDCP source packet.

[0068] As an embodiment, the PDCP source packet is a PDCP packet, or is also referred to as a PDCP data packet, PDCPPDU.

[0069] As an embodiment, the PDCP source packet is relative to the PDCP repair packet. When the first type of data packet is the PDCP source packet, the second type of data packet is the PDCP repair packet, and the PDCP repair packet is a repair data packet generated based on the PDCP source packet.

[0070] In one implementation manner, when the PDCP source packet is a PDCP PDU, the PDCP repair packet is also a PDCPPDU.

[0071] For example, when the PDCP source packet is a PDCP SDU, the PDCP repair packet is a PDCP SDU.

[0072] As a variant embodiment, the first type of data packet is the first type of SDU, the second type of data packet is the second type of SDU, and the delay of the first type of SDU may include one or more of the following:

[0073] The average delay of the first type of SDU;

[0074] The minimum delay of the SDU in the first type of SDU;

[0075] The maximum latency of the SDUs in the first type of SDU.

[0076] As an embodiment, the latency of the first type of SDU includes the average latency.

[0077] As an embodiment, the latency of the first type of SDU includes the minimum value among the latencies of the SDUs in the first type of SDU.

[0078] As an embodiment, the latency of the first type of SDU includes the maximum value among the latencies of the SDUs in the first type of SDU.

[0079] As an embodiment, the latency of the first type of SDU includes the excessive packet latency of the first type of SDU.

[0080] Specifically, according to one aspect of the present application, the latency reporting method includes:

[0081] Sending a second measurement report, which is generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0082] As an embodiment, the advantage of the above method is that by sending the second measurement report, the receiving party can know the latency information of the first type of data packet and also know that the first type of data packet is discarded by the terminal, which is beneficial to obtaining a more comprehensive QoS monitoring result.

[0083] As an embodiment, the second measurement report is a special form of the first measurement report. The terminal either sends the first measurement report or sends the second measurement report.

[0084] As an embodiment, the second measurement report is generated when the first type of data packet is discarded.

[0085] As an embodiment, the second measurement report is generated after the first type of data packet is discarded.

[0086] As an embodiment, the discarding of the first type of data packet is the motivation for generating the second measurement report.

[0087] As a variant embodiment, when the first type of data packet is discarded, the first measurement report is not sent.

[0088] As a variant embodiment, when the first type of data packet is discarded, the terminal does not measure the first type of data packet, and its corresponding first measurement result is recorded as empty or marked as not measured.

[0089] Optionally, the first type of data packet is discarded, and the terminal does not measure the first type of data packet nor generate the first measurement result.

[0090] As an embodiment, if the second type of data packet is discarded, it does not affect the generation of the first measurement result, nor the generation and transmission of the first measurement report.

[0091] In other words, the importance of the first type of data packet is higher than that of the second type of data packet.

[0092] In one implementation, the importance of the first type of data packet depends on the importance of the PDU set it belongs to, and the importance of the PDU set is indicated by the parameter PDU Set Importance (PSI).

[0093] Specifically, according to one aspect of the present application, the time delay is the excess packet delay, and the excess packet delay includes a first excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the first data packets received by the terminal;

[0094] Wherein, the total number of the first data packets received by the terminal includes the number of the second type of data packets.

[0095] As an embodiment, the advantage of the above method is that it provides a calculation method for the excess packet delay for data packets of different categories, unifies the statistical method of the excess packet delay for data packets of different categories, and is beneficial to minimizing the impact caused by the excess packet delay.

[0096] As an embodiment, the first measurement report includes the first excess packet delay.

[0097] Specifically, according to one aspect of the present application, the time delay is the excess packet delay, and the time delay measurement method includes:

[0098] The excess packet delay includes a second excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the second data packets received by the terminal;

[0099] Wherein, the total number of the second data packets received by the terminal excludes the number of the second type of data packets.

[0100] As an embodiment, the advantage of the above method is that it provides a method for calculating the excessive packet delay for data packets of different categories, unifies the statistical method of the excessive packet delay for data packets of different categories, and is conducive to minimizing the impact caused by the excessive packet delay.

[0101] As an embodiment, the first measurement report includes the second excessive packet delay.

[0102] As an embodiment, the second total data packets received by the terminal are received by the PDCP sublayer of the terminal from the SDAP sublayer.

[0103] As an embodiment, the quantity of the second total data packets received by the terminal excluding the second type of data packets refers to the quantity of the total data packets received by the terminal that do not include the second type of data packets.

[0104] As an embodiment, if the second type of data packets is discarded, it does not affect the reporting of the delay of the first type of data packets.

[0105] As an embodiment, the delay of the first type of data packets is called the first delay. If the second type of data packets is discarded, it does not affect the reporting of the first delay.

[0106] As an embodiment, the first type of data packets is a PDCP packet, the second type of data packets is a repair packet of the PDCP packet, the delay of the PDCP packet is called the first delay. If the repair packet of the PDCP packet is discarded, it does not affect the reporting of the first delay.

[0107] As an embodiment, the first type of data packets is an uplink PDCP source packet, the second type of data packets is an uplink PDCP repair packet of the uplink PDCP source packet, the delay of the uplink PDCP source packet is called the first delay. If the uplink PDCP repair packet is discarded, it does not affect the reporting of the first delay.

[0108] As an embodiment, the first type of data packets is a PDCP PDU, the second type of data packets is a repair PDU of the PDCP PDU, the delay of the PDCP PDU is called the first delay. If the repair packet of the PDCP PDU is discarded, it does not affect the reporting of the first delay.

[0109] As an embodiment, the first type of data packets is a PDCP SDU, the second type of data packets is a repair PDU of the PDCP SDU, the delay of the PDCP SDU is called the first delay. If the repair packet of the PDCP SDU is discarded, it does not affect the reporting of the first delay.

[0110] As an embodiment, if the second type of data packet is discarded, the first measurement report includes the latency of the first type of data packet and does not include the latency of the second type of data packet.

[0111] As an embodiment, the latency of the first type of data packet is referred to as the first latency, and the latency of the second type of data packet is referred to as the second latency. If the second type of data packet is discarded, the first measurement report includes the first latency and does not include the second latency.

[0112] As an embodiment, if the first type of data packet is discarded, the first measurement report is not reported; or, in this case, a special value is reported.

[0113] Specifically, according to one aspect of the present application, the first measurement report is part of the minimized drive test (MDT) report of the terminal.

[0114] As an embodiment, MDT is used to reduce drive tests and lower the costs of operators.

[0115] As an embodiment, the first measurement report is used for MDT.

[0116] As an embodiment, the second measurement report is used for MDT.

[0117] As an embodiment, both the first measurement report and the second measurement report are used for MDT.

[0118] As an embodiment, the technical field of the present application is MDT.

[0119] As an embodiment, the technical field of the present application is the uplink.

[0120] Specifically, according to one aspect of the present application, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0121] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet;

[0122] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0123] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0124] As an embodiment, the first type of data packet is a source UL PDCP PDU, and the second type of data packet is a UL PDCP repair PDU generated from the source UL PDCP PDU.

[0125] As an embodiment, the first type of data packet is a source UL PDCP SDU, and the second type of data packet is a UL PDCP repair SDU generated from the source UL PDCP SDU.

[0126] Specifically, the present application discloses a terminal, which includes:

[0127] One or more processors and a memory;

[0128] The memory is coupled to the one or more processors, and the memory is used to store computer program code. The computer program code includes computer instructions, and the one or more processors call the computer instructions to cause the terminal to execute the delay measurement method as described above.

[0129] Specifically, according to one aspect of the present application, the terminal is an Internet of Things terminal.

[0130] Specifically, according to one aspect of the present application, the terminal is a user equipment.

[0131] Specifically, according to one aspect of the present application, the terminal is a relay.

[0132] Specifically, according to one aspect of the present application, the terminal is an access network device.

[0133] Specifically, according to one aspect of the present application, the terminal is a vehicle-mounted terminal.

[0134] Specifically, according to one aspect of the present application, the terminal is an aircraft.

[0135] Specifically, according to one aspect of the present application, the terminal is a mobile phone.

[0136] Specifically, the present application discloses a terminal suitable for delay measurement, including:

[0137] A processor that measures data packets in a data radio bearer to generate a first measurement result. The data packets include a first type of data packet and a second type of data packet, and the generation of the second type of data packet depends on the first type of data packet;

[0138] The first measurement result at least includes the delay of the first type of data packet;

[0139] Wherein, the time delay includes any one or more of the following: average time delay; minimum time delay; maximum time delay; excess packet time delay.

[0140] Specifically, according to one aspect of the present application, the first measurement result includes the time delay of the second type of data packet.

[0141] Specifically, according to one aspect of the present application, the terminal includes:

[0142] A transmitter that sends a first measurement report, and the first measurement report includes the first measurement result.

[0143] Specifically, according to one aspect of the present application, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0144] Specifically, according to one aspect of the present application, the processor includes a processing sub-module that measures the first type of data packet in the data radio bearer and measures the second type of data packet; or, the processing sub-module measures the first type of data packet in the data radio bearer and ignores the second type of data packet.

[0145] Specifically, according to one aspect of the present application, the first type of data packet is a PDCP source packet, and the terminal includes:

[0146] A receiver that receives a first measurement configuration before measuring the data packets in a data radio bearer, and the first measurement configuration includes a first uplink time delay configuration for configuring the time delay measurement of the uplink PDCP source packet;

[0147] The transmitter sends a first measurement report after measuring the data packets in a data radio bearer, and the first measurement report includes at least the time delay of the PDCP source packet.

[0148] Specifically, according to one aspect of the present application, the terminal includes:

[0149] The transmitter sends a second measurement report, which is generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0150] Specifically, according to one aspect of the present application, the time delay is an excess packet time delay, and the excess packet time delay includes a first excess packet time delay, which is the ratio of the number of the first type of data packets exceeding the configured time delay threshold during the measurement period to the total number of the first data packets received by the terminal;

[0151] Among them, the first total data packet received by the terminal includes the quantity of the second type of data packet.

[0152] Specifically, according to one aspect of the present application, the time delay is an excessive packet time delay, and the excessive packet time delay includes a second excessive packet time delay, where the second excessive packet time delay is the ratio of the quantity of the first type of data packet exceeding the configured time delay threshold during the measurement period to the second total data packet received by the terminal;

[0153] Among them, the second total data packet received by the terminal excludes the quantity of the second type of data packet.

[0154] Specifically, according to one aspect of the present application, the first measurement report is a part of the minimized drive test (MDT) report of the terminal.

[0155] Specifically, according to one aspect of the present application, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0156] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet;

[0157] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0158] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0159] Specifically, the present application discloses a method for receiving a measurement report in a base station, including:

[0160] Receiving a first measurement report, where the first measurement report includes a first measurement result, and the first measurement result is generated by a terminal measuring data packets in a data radio bearer, and the data packets include a first type of data packet and a second type of data packet, and the generation of the second type of data packet depends on the first type of data packet;

[0161] Among them, the first measurement result at least includes the time delay of the first type of data packet;

[0162] The time delay includes any one or more of the following: average time delay; minimum time delay; maximum time delay; excessive packet time delay.

[0163] Specifically, according to one aspect of the present application, the first measurement result includes the time delay of the second type of data packet.

[0164] Specifically, according to one aspect of the present application, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0165] Specifically, according to one aspect of the present application, the first type of data packet is a PDCP source packet, and the method for receiving a measurement report includes:

[0166] Before receiving the first measurement report, send a first measurement configuration, where the first measurement configuration includes a first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet;

[0167] Wherein, the first measurement report includes at least the delay of the PDCP source packet.

[0168] Specifically, according to one aspect of the present application, the method for receiving a measurement report includes:

[0169] Receive a second measurement report, which is generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0170] Specifically, according to one aspect of the present application, the delay is an excessive packet delay.

[0171] The excessive packet delay includes a first excessive packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the first data packets received by the terminal;

[0172] Wherein, the total number of the first data packets received by the terminal includes the number of the second type of data packets.

[0173] Specifically, according to one aspect of the present application, the delay is an excessive packet delay.

[0174] The excessive packet delay includes a second excessive packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the second data packets received by the terminal;

[0175] Wherein, the total number of the second data packets received by the terminal excludes the number of the second type of data packets.

[0176] Specifically, according to one aspect of the present application, the first measurement report is a part of the minimized drive test (MDT) report of the terminal.

[0177] Specifically, according to one aspect of the present application, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0178] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet;

[0179] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0180] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0181] Specifically, the present application discloses a base station, and the base station includes:

[0182] One or more processors and a memory;

[0183] The memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the base station to execute the measurement report receiving method as described above.

[0184] Specifically, the present application discloses a base station suitable for a measurement report receiving method, and the base station includes:

[0185] A receiver that receives a first measurement report, the first measurement report includes a first measurement result, the first measurement result is generated by a terminal measuring data packets in a data radio bearer, the data packets include a first type of data packet and a second type of data packet, and the generation of the second type of data packet depends on the first type of data packet;

[0186] Wherein, the first measurement result at least includes the delay of the first type of data packet;

[0187] The delay includes any one or more of the following: average delay; minimum delay; maximum delay; excess packet delay.

[0188] Specifically, according to one aspect of the present application, the first measurement result includes the delay of the second type of data packet.

[0189] Specifically, according to one aspect of the present application, the fact that the generation of the second type of data packet depends on the first type of data packet means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0190] Specifically, according to one aspect of the present application, the first type of data packet is a PDCP source packet, and the base station includes:

[0191] A transmitter that, before receiving the first measurement report, sends a first measurement configuration, the first measurement configuration including a first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet;

[0192] Wherein, the first measurement report at least includes the delay of the PDCP source packet.

[0193] Specifically, according to one aspect of the present application, the base station includes:

[0194] A receiver that receives a second measurement report generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0195] Specifically, according to one aspect of the present application, the delay is an excess packet delay.

[0196] The excess packet delay includes a first excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the first data packets received by the terminal.

[0197] Wherein, the total number of the first data packets received by the terminal includes the number of the second type of data packets.

[0198] Specifically, according to one aspect of the present application, the delay is an excess packet delay.

[0199] The excess packet delay includes a second excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the second data packets received by the terminal.

[0200] Wherein, the total number of the second data packets received by the terminal excludes the number of the second type of data packets.

[0201] Specifically, according to one aspect of the present application, the first measurement report is a part of the minimized drive test (MDT) report of the terminal.

[0202] Specifically, according to one aspect of the present application, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0203] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet.

[0204] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0205] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0206] As an embodiment, compared with the traditional solution, the present application has the following advantages:

[0207] More accurately grasp the delay of the monitoring service and verify whether the QoS requirements are met.

[0208] Meet the requirements of technological development. When different types of data packets are allowed in the DRB, it is still possible to accurately monitor QoS.

[0209] It can be compatible with measuring different delays, which is beneficial to reducing the system complexity.

[0210] It can support richer service types, such as XR services. BRIEF DESCRIPTION OF THE DRAWINGS

[0211] By reading the following detailed description of non-limiting embodiments with reference to the accompanying drawings, other features, objects, and advantages of the present application will become more apparent:

[0212] Figure 1 Shows a flowchart of a delay measurement method according to an embodiment of the present application;

[0213] Figure 2 Shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0214] Figure 3 Shows a schematic diagram of an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0215] Figure 4 Shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0216] Figure 5 Shows a flowchart of a radio signal transmission according to an embodiment of the present application;

[0217] Figure 6 Shows a partial flowchart of a radio signal transmission according to an embodiment of the present application;

[0218] Figure 7 Shows a flowchart of a radio signal transmission according to an embodiment of the present application;

[0219] Figure 8Shows a partial wireless signal processing flowchart according to an embodiment of the present application;

[0220] Figure 9 Shows a schematic diagram of determining the delay of N PDCP source packets according to an embodiment of the present application;

[0221] Figure 10 Illustrates a schematic diagram of calculating delay according to an embodiment of the present application;

[0222] Figures 11 to 12 Respectively shows a schematic diagram of the UL PDCP source packet delay formula according to an embodiment of the present application;

[0223] Figure 13 Illustrates a schematic diagram of a measurement report receiving method in a base station according to an embodiment of the present application;

[0224] Figure 14 Illustrates a schematic diagram of a processing device in a terminal according to an embodiment of the present application;

[0225] Figure 15 Illustrates a schematic diagram of a processing device in a base station according to an embodiment of the present application. Detailed implementation manners

[0226] To facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the technical solutions related to the embodiments of the present application.

[0227] The following will further elaborate on the technical solutions of the present invention in conjunction with the accompanying drawings. It should be noted that, without conflict, the embodiments and features in the embodiments of the present invention can be combined arbitrarily with each other.

[0228] Example 1

[0229] Embodiment 1 illustrates a flowchart of a delay measurement method according to an embodiment of the present application, as shown in the accompanying Figure 1 figure. In the accompanying Figure 1 figure, each box represents a step.

[0230] In Embodiment 1, the delay measurement method can be executed in the terminal 100. The terminal 100 includes but is not limited to various terminal devices. Typically, the terminal 100 can be a UE. The terminal 100 is within the service range of a network (such as a serving cell).

[0231] In Embodiment 1, in step 101, the terminal 100 measures data packets in a data radio bearer to generate a first measurement result. The data packets include first-class data packets and second-class data packets, and the generation of the second-class data packets depends on the first-class data packets.

[0232] Among them, the first measurement result at least includes the delay of the first type of data packet; the delay includes any one or more of the following: average delay; minimum delay; maximum delay; excess packet delay.

[0233] As an example, the terminal 100 is in the RRC connected state.

[0234] As an example, the interpretation of the terms in this application refers to the definitions in the 3GPP specification protocol TS38 series.

[0235] As an example, any parameter not explicitly stated in this application can be network-indicated or network-configured or pre-configured.

[0236] As an example, any parameter not explicitly stated in this application can be determined by the internal algorithm of the terminal 100 when not network-indicated.

[0237] As an example, any parameter in this application can be initialized to 0 when not network-indicated.

[0238] As an example, any parameter in this application can be set to a random number when not network-indicated.

[0239] As an example, any parameter in this application can be preferentially selected according to the simulation results when not network-indicated.

[0240] As an example, the terminal 100 is a UE. The serving cell refers to the cell where the UE camps. Performing cell search includes the UE searching for a suitable cell of the selected PLMN (Public Land Mobile Network) or SNPN (Stand-alone Non-Public Network), selecting the suitable cell to provide available services, and monitoring the control channel of the suitable cell. This process is defined as camping on the cell; that is, a camped cell is the serving cell of this UE relative to this UE. Camping on a cell in the RRC idle state or RRC inactive state has the following advantages: enabling the UE to receive system information from the PLMN or SNPN; after the UE is registered, if the UE wishes to establish an RRC connection or resume a suspended RRC connection, the UE can achieve this by performing initial access on the control channel of the camped cell; the network can page the UE; enabling the UE to receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

[0241] As an example, for a UE in the RRC connected state without CA / DC (carrier aggregation / dual connectivity) configured, there is only one serving cell, such as the Primary Cell. For a UE in the RRC connected state with CA / DC configured, the serving cell is used to indicate a set of cells including the SpCell (Special Cell) and all Secondary Cells. The Primary Cell is the MCG (Master Cell Group) cell, operating on the primary frequency, and the UE performs the initial connection establishment process or initiates connection reestablishment on the Primary Cell. For dual connectivity operation, the Special Cell refers to the PCell of the MCG or the PSCell (Primary SCG Cell) of the SCG (Secondary Cell Group); if it is not dual connectivity operation, the Special Cell refers to the PCell.

[0242] As an example, the frequency on which the SCell operates is the secondary frequency.

[0243] As an example, the individual content of an information element is called a field.

[0244] As an example, MR-DC (Multi-Radio Dual Connectivity) refers to the dual connectivity between an E-UTRA and an NR node, or the dual connectivity between two NR nodes.

[0245] As an example, in MR-DC, the radio access node that provides the control plane connection to the core network is the master node, and the master node can be the master eNB, the master ng-eNB, or the master gNB.

[0246] As an example, MCG refers to a set of serving cells associated with the master node in MR-DC, including the SpCell; it may also include one or more SCell.

[0247] As an example, the PCell is the SpCell of the MCG.

[0248] As an example, the PSCell is the SpCell of the SCG.

[0249] As an example, in MR-DC, the radio access node that does not provide the control plane connection to the core network and provides additional resources to the UE is the secondary node. The secondary node can be an en-gNB, a secondary ng-eNB, or a secondary gNB.

[0250] As an example, in MR-DC, a set of serving cells associated with the secondary node is the SCG, including the SpCell; it may also include one or more SCell.

[0251] As an example, the terminal 100 is configured with an MCG, and the MCG configured for the terminal 100 includes at least one SCell.

[0252] As an example, the terminal 100 is configured with an MCG and an SCG.

[0253] As a sub-example of this example, the MCG configured for the terminal 100 includes at least one SCell.

[0254] As a sub-example of this example, the SCG configured for the terminal 100 includes at least one SCell.

[0255] As an example, measuring the data packets in a DRB is for measuring the latency, and the first measurement result includes at least the result of the latency measurement.

[0256] As an example, the first measurement result only includes the latency of the first type of data packets.

[0257] As a sub - embodiment of this embodiment, the meaning that the first measurement result only includes the delay of the first type of data packets is that the first measurement result does not include the delay of the second type of data packets.

[0258] As a sub - embodiment of this embodiment, the meaning that the first measurement result only includes the delay of the first type of data packets is that the terminal does not count the delay of the second type of data packets.

[0259] As an embodiment, the first measurement result includes the delay of the second type of data packets.

[0260] As an embodiment, the first measurement result includes the delay of the first type of data packets and the delay of the second type of data packets.

[0261] As an embodiment, the first type of data packets and the second type of data packets belong to the same PDU set.

[0262] As an embodiment, the data packet is a PDU packet. The first type of data packets included in the PDU packet are the first type of PDU packets, and the second type of data packets included in the PDU packet are the second type of PDU packets.

[0263] In one implementation, the PDU packet is a PDCP PDU.

[0264] In another implementation, the PDU packet is an RLC PDU.

[0265] In another implementation, the PDU packet is a MAC PDU.

[0266] As an embodiment, the data packet is an SDU packet. The first type of data packets included in the SDU packet are the first type of SDU packets, and the second type of data packets included in the SDU packet are the second type of SDU packets.

[0267] In one implementation, the SDU packet is a PDCP SDU.

[0268] In another implementation, the SDU packet is an RLC SDU.

[0269] In another implementation, the SDU packet is a MAC SDU.

[0270] As an embodiment, for each DRB, the terminal performs data packet delay measurement for the uplink.

[0271] As an example, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet for repairing the first type of data packet is generated based on the first type of data packet.

[0272] As an example, the second type of data packet is a repair data packet of the first type of data packet.

[0273] As an example, the second type of data packet is generated from one or more of the first type of data packet.

[0274] As an example, the first type of data packet and the second type of data packet are PDUs respectively, and each repair PDU in the second data packet is generated based on one or more PDUs in the first type of data packet.

[0275] In one embodiment, each PDU in the first type of data packet is a source PDU for generating each repair PDU in the second data packet.

[0276] As an example, the first type of data packet and the second type of data packet are SDUs respectively, and each repair SDU in the second data packet is generated based on one or more SDUs in the first type of data packet.

[0277] In one embodiment, the first type of SDU in the first type of data packet generates the second type of SDU in the second type of data packet.

[0278] As an example, the generation of the second type of SDU by the first type of SDU means that the second type of SDU for repairing the first type of SDU is generated based on the first type of SDU.

[0279] As an example, the generation of the second type of data packet depends on the first type of data packet, which means that when the first type of data packet is discarded, the second type of data packet is discarded together.

[0280] As an example, the generation of the second type of data packet depends on the first type of data packet, which means that without the first type of data packet, there is no second type of data packet.

[0281] As an example, the generation of the second type of data packet depends on the first type of data packet, which means that the first type of data packet and the second type of data packet belong to the same layer of data packets. For example, both are PDCP PDUs, or both are PDCP SDUs; or both are RLC PDUs, or both are RLC SDUs; or both are MAC PDUs, or both are MAC SDUs.

[0282] As an example, the first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet.

[0283] As an example, the first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet.

[0284] As an example, the first type of data packet is a source UL MAC packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0285] As an example, measuring the data packets in a DRB includes: measuring the first type of data packets in the DRB and measuring the second type of data packets.

[0286] In one implementation, after differentiating the first type of data packets and the second type of data packets in the DRB, the first type of data packets and the second type of data packets in the DRB can be measured separately.

[0287] In another implementation, each data packet in the DRB is measured in sequence, and then the measurement results are processed separately according to whether the data packet belongs to the first type of data packet or the second type of data packet.

[0288] As an example, measuring the data packets in a DRB includes: measuring the first type of data packets in the DRB and ignoring the second type of data packets.

[0289] As a sub - example of this example, the advantage of ignoring the second type of data packets is that the measurement results can better reflect the latency of the first type of data packets, excluding the interference of the second type of data packets. The first type of data packets has a direct impact on the user experience, so it can more truly reflect the latency performance and QoS.

[0290] In one embodiment, after differentiating between the first type of data packets and the second type of data packets in the DRB, only the first type of data packets are measured, and the measurement result is used as the first measurement result.

[0291] In another embodiment, the second type of data packets in the DRB are discarded, and the first type of data packets are measured to obtain a first measurement result that only includes the first type of data packets.

[0292] In one example, the delay includes any one or more of the following: average delay; minimum delay; maximum delay; excess packet delay.

[0293] In one embodiment, the average delay may refer to the average delay of uplink PDCP data packets.

[0294] In one embodiment, the average delay may refer to the average delay of uplink radio interface data packets.

[0295] In one embodiment, the average delay may refer to the average delay of uplink RLC data packets.

[0296] In one embodiment, the average delay may refer to the average reordering delay of uplink PDCP.

[0297] As one example, the first type of data packets and the second type of data packets belong to the same PDU set.

[0298] As a sub - example of this example, the advantage of the above method is that it is beneficial to provide more detailed delay information according to different data packets in the same PDU set.

[0299] As one example, the first type of data packets and the second type of data packets belong to different PDU sets.

[0300] As a sub - example of this example, the advantage of the above method is that it is beneficial to count the delay information according to different PDU sets, so that the counted delay information can completely reflect the delay of some PDU sets.

[0301] As one example, a PDU set includes, for example, a frame of video, a video slice.

[0302] As one example, in some applications, the data of a PDU set needs to be decoded together to be meaningful.

[0303] As one example, the PDU in a PDU set is an application - layer PDU or a PDU of other protocol layers carrying application - layer information.

[0304] As an example, a PDU set consists of one or more PDUs carrying a unit of information generated by the application layer.

[0305] As an example, any PDU in a PDU set includes an ID or index for identifying this PDU set.

[0306] As an example, the data packet is a PDU packet. The first type of data packet included in the PDU packet is the first type of PDU packet, and the second type of data packet included in the PDU packet is the second type of PDU packet.

[0307] In one embodiment, the PDU packet is a PDCP PDU.

[0308] In another embodiment, the PDU packet is an RLC PDU.

[0309] In another embodiment, the PDU packet is a MAC PDU.

[0310] As an example, the data packet is an SDU packet. The first type of data packet included in the SDU packet is the first type of SDU packet, and the second type of data packet included in the SDU packet is the second type of SDU packet.

[0311] In one embodiment, the PDU packet is a PDCP SDU.

[0312] In another embodiment, the PDU packet is an RLC SDU.

[0313] In another embodiment, the PDU packet is a MAC SDU.

[0314] Typically, the data packet is a PDCP packet. The first type of data packet includes M PDCP source packets, and the second type of data packet is a PDCP repair packet generated for the M PDCP source packets.

[0315] As an example, any PDCP source packet among the M PDCP source packets carries an identifier or identity or index indicating any PDCP source packet among the M PDCP source packets.

[0316] As an example, the protocol header of any PDCP source packet among the M PDCP source packets carries an identifier or identity or index indicating any PDCP source packet among the M PDCP source packets.

[0317] As an embodiment, the protocol header of the SDAP PDU included in any one of the M PDCP source packets carries an indication of the identity or identification or index of any one of the M PDCP source packets.

[0318] As an embodiment, the protocol header of the higher layer PDU included in any one of the M PDCP source packets carries an indication of the identity or identification or index of any one of the N PDCP source packets.

[0319] As an embodiment, the first uplink delay configuration is used to configure the uplink PDCP source packet delay measurement to include an indication of a plurality of DRBs, and the M PDCP source packets occupy the plurality of DRBs.

[0320] As an embodiment, the first uplink delay configuration is used to configure the uplink PDCP source packet delay measurement to include an indication of a single DRB, and the M PDCP source packets occupy the single DRB.

[0321] As a sub - embodiment of this embodiment, indicating a single DRB can be regarded as a special case of indicating a plurality of DRBs.

[0322] As an embodiment, the first uplink delay configuration is used to configure the uplink PDCP source packet delay measurement to include an indication of a plurality of DRBs, and the uplink PDCP source packet delay measurement is to measure the delay of the M PDCP source packets on the plurality of DRBs.

[0323] As an embodiment, the advantage of performing the uplink PDCP source packet delay measurement for a plurality of DRBs is that for some services that occupy a plurality of DRBs, including the N PDCP source packets occupying a plurality of DRBs, performing the uplink PDCP source packet measurement for a plurality of DRBs is beneficial to understanding the delay situation of the services that occupy a plurality of DRBs, so as to better perform QoS monitoring.

[0324] As an embodiment, the first uplink delay configuration is used to configure the uplink PDCP source packet delay measurement to include an indication of the identity (such as ID) of the first DRB and the uplink PDCP packet category, the M PDCP source packets occupy the first DRB and belong to the uplink PDCP packet category; the first DRB is used to carry at least one other PDCP packet that does not belong to the uplink PDCP packet category.

[0325] As a sub - embodiment, the uplink PDCP packet category is an uplink PDCP source packet, the other PDCP packets are PDCP repair packets, and the PDCP repair packets are generated based on the uplink PDCP source packets. The first uplink delay configuration is used to configure uplink PDCP source packet delay measurement, including indicating the identifier (such as ID) of the first DRB and the uplink source PDCP packets. The M PDCP source packets occupy the first DRB and belong to the uplink PDCP source packets; the first DRB is used to carry at least one PDCP repair packet.

[0326] Example 2

[0327] Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in the appendix Figure 2 shown.

[0328] Appendix Figure 2 illustrates the network architecture diagrams of 5G NR, LTE (Long - Term Evolution) and LTE - A (Long - Term Evolution Advanced) systems. The 5G NR or LTE network architecture 200 can be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable term. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG - RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As Figure 2As shown, the 5GS / EPS 200 provides packet switching services. However, those skilled in the art will readily understand that the various concepts presented throughout the present invention can be extended to networks that provide circuit switching services or other cellular networks. The NG-RAN includes an NR Node B (gNB) 203 and other gNBs 204. The gNB 203 provides user and control plane protocol termination towards the UE 201. The gNB 203 can be connected to other gNBs 204 via the Xn interface (e.g., backhaul). The gNB 203 can also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmission and reception point), or some other suitable term. The gNB 203 provides an access point to the 5GC / EPC 210 for the UE 201. Examples of the UE 201 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia, video, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, automobiles, wearable devices, or any other similar functions. Those skilled in the art may also refer to the UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile, wireless, wireless communication, remote, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. The gNB 203 is connected to the 5GC / EPC 210 via the S1 / NG interface. The 5GC / EPC 210 includes an MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, an S-GW (Service Gateway) / UPF (User Plane Function) 212, and a P-GW (Packet Date Network Gateway) / UPF 213. The MME / AMF / SMF 211 is a control node that processes the signaling between the UE 201 and the 5GC / EPC 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management.All user IP (Internet Protocol) packets are transmitted through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet service 230. The Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0329] As an example, the terminal in this application is the UE 201.

[0330] As an example, the base station in this application is the gNB 203, or an NR Node B.

[0331] As an example, the radio link from the UE 201 to the NR Node B is an uplink.

[0332] As an example, the radio link from the NR Node B to the UE 201 is a downlink.

[0333] As an example, the UE 201 supports relay transmission.

[0334] As an example, the UE 201 includes a mobile phone.

[0335] As an example, the UE 201 is a vehicle including an automobile.

[0336] As an example, the UE 201 is an Internet of Things device.

[0337] As an example, the UE 201 is an aircraft.

[0338] As an example, the UE 201 is a dedicated device or special equipment with communication functions.

[0339] As an example, the gNB 203 is a macrocellular base station.

[0340] As an example, the gNB 203 is a micro cell base station.

[0341] As an example, the gNB 203 is a picocell base station.

[0342] As an example, the gNB 203 is a flying platform device.

[0343] As an example, the gNB 203 is a satellite device.

[0344] Example 3

[0345] Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in the appendix Figure 3 as shown. Figure 3 It is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. Figure 3The radio protocol architecture of the control plane 300 for the first node (UE, gNB, or satellite or aircraft in NTN) and the second node (gNB, UE, or satellite or aircraft in NTN), or between two UEs, is shown with three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (Physical Layer) signal processing functions. Layer 1 will be referred to as PHY301 in this document. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and between two UEs via PHY301. Layer 2 305 includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304, and these sublayers terminate at the second node. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets and provides handover support for the first node between the second nodes. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for disordered reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between the first nodes. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the second node and the first node. The PC5-S (PC5 Signaling Protocol) sublayer 307 is responsible for handling the signaling protocol of the PC5 interface. The radio protocol architecture of the user plane 350 includes Layer 1 (L1 layer) and Layer 2 (L2 layer). The radio protocol architecture for the first node and the second node in the user plane 350 is generally the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead.The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sub-layer 356. The SDAP sub-layer 356 is responsible for the mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. The SRB can be regarded as a service or interface provided by the PDCP layer to higher layers, such as the RRC layer. In the NR system, the SRB includes SRB1, SRB2, SRB3, and when it comes to sidelink communication, there is also SRB4, which are respectively used to transmit different types of control signaling. The SRB is a bearer between the UE and the access network, and is used to transmit control signaling including RRC signaling between the UE and the access network. SRB1 has special significance for the UE. After each UE establishes an RRC connection, there will be an SRB1, which is used to transmit RRC signaling. Most of the signaling is transmitted through SRB1. If SRB1 is interrupted or unavailable, the UE must perform RRC reconstruction. SRB2 is generally only used to transmit NAS signaling or signaling related to security. The UE may not be configured with SRB3. Except for emergency services, the UE must establish an RRC connection with the network to perform subsequent communication. Although not shown, the first node may have several upper layers above the L2 layer 355. In addition, it also includes a network layer (e.g., IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.). A protocol sub-layer can also be referred to as a protocol layer. Attached. Figure 3 The shown is a general protocol layer structure, and the nodes used in the present invention may lack some protocol layers.

[0346] As an example, attached Figure 3 The wireless protocol architecture in is applicable to the terminal described in the present application.

[0347] As an example, attached Figure 3 The wireless protocol architecture in is applicable to the base station described in the present application.

[0348] As an example, the first measurement configuration is generated in RRC306.

[0349] As an example, the first measurement report is generated in RRC306.

[0350] Example 4

[0351] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application, as attached Figure 4 shown. Figure 4 It is a block diagram of a first communication device 450 and a second communication device 410 that communicate with each other in an access network.

[0352] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, and optionally a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454, and an antenna 452.

[0353] The second communication device 410 includes a controller / processor 475, a memory 476, a receive processor 470, a transmit processor 416, and optionally a multi-antenna receive processor 472, a multi-antenna transmit processor 471, a transmitter / receiver 418, and an antenna 420.

[0354] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 (Layer-2) layer. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, and mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding on the coded and modulated symbols, including codebook-based precoding and non-codebook-based precoding, and beamforming processing, to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time domain and / or frequency domain, and then uses the inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. Subsequently, the multi-antenna transmit processor 471 performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to different antennas 420.

[0355] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives signals via its respective antenna 452. Each receiver 454 recovers the information modulated onto the radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream for providing to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 perform various signal processing functions of the L1 layer. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receivers 454. The receive processor 456 uses the fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receive analog precoding / beamforming operations from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receive processor 456, where the reference signal will be used for channel estimation, and the data signal recovers any spatial streams destined for the first communication device 450 after multi-antenna detection in the multi-antenna receive processor 458. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. Subsequently, the receive processor 456 decodes and de-interleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. Subsequently, the upper layer data and control signals are provided to the controller / processor 459. The controller / processor 459 performs the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover upper layer data packets from the core network. Subsequently, the upper layer data packets are provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 for L3 processing.

[0356] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, the data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function described at the second communication device 410 in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements the L2 layer functions for the user plane and the control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing. The multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Subsequently, the transmit processor 468 modulates the generated spatial streams into multi-carrier / single-carrier symbol streams, and after passing through the analog precoding / beamforming operation in the multi-antenna transmit processor 457, provides them to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and then provides it to the antenna 452.

[0357] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the receiving functions described at the first communication device 450 in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives radio frequency signals through its corresponding antenna 420, converts the received radio frequency signals into baseband signals, and provides the baseband signals to the multi-antenna receive processor 472 and the receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 jointly implement the L1 layer functions. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 may be associated with a memory 476 that stores program code and data. The memory 476 may be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the UE 450. The upper layer data packets from the controller / processor 475 may be provided to the core network.

[0358] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor, and the first communication device 450 is at least configured to: measure data packets in a data radio bearer to generate a first measurement result, the data packets including first type data packets and second type data packets, and the generation of the second type data packets depends on the first type data packets; the first measurement result at least includes the latency of the first type data packets; wherein, the latency includes any one or more of the following: average latency, minimum latency, maximum latency, excess packet latency.

[0359] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: measuring data packets in a data radio bearer to generate a first measurement result, the data packets including first type data packets and second type data packets, and the generation of the second type data packets depends on the first type data packets; the first measurement result at least includes the latency of the first type data packets; wherein, the latency includes any one or more of the following: average latency, minimum latency, maximum latency, excess packet latency.

[0360] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor, and the second communication device 410 is at least configured to: receive a first measurement report, the first measurement report including a first measurement result, the first measurement result being generated by a terminal measuring data packets in a data radio bearer, the data packets including first type data packets and second type data packets, and the generation of the second type data packets depends on the first type data packets; wherein, the first measurement result at least includes the latency of the first type data packets; the latency includes any one or more of the following: average latency, minimum latency, maximum latency, excess packet latency.

[0361] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, which generates actions when executed by at least one processor, and the actions include: receiving a first measurement report, where the first measurement report includes a first measurement result, and the first measurement result is generated by a terminal measuring data packets in a data radio bearer, and the data packets include first-type data packets and second-type data packets, and the generation of the second-type data packets depends on the first-type data packets; wherein, the first measurement result at least includes the latency of the first-type data packets; the latency includes any one or more of the following: average latency, minimum latency, maximum latency, excessive packet latency.

[0362] As an embodiment, the first communication device 450 corresponds to the terminal in the present application.

[0363] As an embodiment, the second communication device 410 corresponds to the base station in the present application.

[0364] As an embodiment, the first communication device 450 is a UE.

[0365] As an embodiment, the first communication device 450 is a vehicle-mounted terminal.

[0366] As an embodiment, the second communication device 450 is a relay.

[0367] As an embodiment, the second communication device 410 is a satellite.

[0368] As an embodiment, the second communication device 410 is an aircraft.

[0369] As an embodiment, the second communication device 410 is a base station.

[0370] As an embodiment, some or all of {the antenna 420, the transmitter 418, the transmit processor 416, the multi-antenna transmit processor 471, the controller / processor 475} are used to send the first measurement configuration.

[0371] As an embodiment, some or all of {the antenna 420, the receiver 418, the receive processor 470, the multi-antenna receive processor 472, the controller / processor 475, the memory 476} are used to receive the first measurement report and the second measurement report.

[0372] As an example, some or all of {the antenna 452, the receiver 454, the receiving processor 456, the multi-antenna receiving processor 458, the controller / processor 459, the memory 460} are used to receive the first measurement configuration.

[0373] As an example, some or all of {the antenna 420, the transmitter 418, the transmitting processor 416, the multi-antenna transmitting processor 471, the controller / processor 475} are used to transmit the first measurement report and the second measurement report.

[0374] Example 5

[0375] Example 5 illustrates a wireless signal transmission flowchart according to an embodiment of the present application, as shown in the attached Figure 5 figure. The attached Figure 5 figure shows the wireless signal transmission and processing process between the terminal U01 and the network device U02.

[0376] For the terminal U01, in step S5101, it receives the first measurement configuration; in step S5102, it measures the data packets in a data radio bearer to generate a first measurement result; in step S5103, it sends the first measurement report.

[0377] For the network device U02, in step S5201, it sends the first measurement configuration; in step S5202, it sends the first measurement configuration; in step S5203, it receives the first measurement report.

[0378] In Example 5, the data packets include first-class data packets and second-class data packets, and the generation of the second-class data packets depends on the first-class data packets; the first measurement result at least includes the delay of the first-class data packets; the delay includes any one or more of the following: average delay; minimum delay; maximum delay; excess packet delay.

[0379] In Example 5, the first measurement configuration includes a first uplink delay configuration; after measuring the data packets in a data radio bearer, the first measurement report is sent.

[0380] As an example, the terminal U01 is a UE, and the network device U02 is the serving cell or cell group of the terminal U01.

[0381] As an example, the terminal U01 is a UE, and the network device U02 is the base station serving the terminal U01.

[0382] As an example, the terminal U01 is a UE, and the network device U02 is the SpCell of the terminal U01 or the base station corresponding to the SpCell.

[0383] As an example, the terminal U01 is a UE, and the network device U02 is the PCell of the terminal U01 or the base station corresponding to the PCell.

[0384] As an example, the network device U02 is the serving base station of the terminal U01.

[0385] As an example, the terminal U01 is in the RRC connected state.

[0386] As an example, the interface between the terminal U01 and the network device U02 is the Uu interface.

[0387] As an example, step S5101 is before step S5102.

[0388] As an example, step S5102 is before step S5103.

[0389] As an example, the first measurement configuration includes RRC signaling.

[0390] As an example, the first measurement configuration is or includes at least one cell in the RRCReconfiguration message.

[0391] As an example, the first measurement configuration only includes the fields or cells in the RRCReconfiguration message whose names include Meas.

[0392] As an example, the first measurement configuration includes at least one cell in the RRCConnectionReconfiguration.

[0393] As an example, the first measurement configuration is or includes MeasConfig.

[0394] As an example, the first measurement configuration is or includes L2-MeasConfig.

[0395] As an example, the first measurement configuration is or includes appLayerMeasConfig.

[0396] As an example, the first measurement configuration is used to configure a cell group.

[0397] As an example, the first measurement configuration is unicast.

[0398] As an example, the first measurement configuration is sent to the terminal U01 through a dedicated control channel.

[0399] As an example, the first measurement configuration is sent to the terminal U01 using a dedicated channel.

[0400] As an example, the first measurement configuration is sent through SRB1.

[0401] As an example, the first measurement result includes the delay of the first type of data packet.

[0402] As an example, the first measurement result includes the delay of the first type of data packet and the delay of the second type of data packet.

[0403] As an example, the first measurement report is sent through SRB1.

[0404] As an example, the first measurement report includes the first measurement result.

[0405] As an example, the first measurement report includes the identifier of the first uplink delay configuration (such as the terminal U01 ID).

[0406] As an example, the first measurement configuration includes a (measurement) report configuration list, and the report configuration list includes a report configuration for the delay measurement value.

[0407] As a sub - example of this example, the report configuration list is ReportConfigToAddModList.

[0408] As an example, the report configuration includes the identifier of the report configuration (such as ID).

[0409] As an example, the report configuration includes a report configuration for NR.

[0410] As an example, the report configuration includes a report configuration for NR, or one of the report configurations for other access technologies.

[0411] As an example, the report configuration includes ReportConfigNR.

[0412] As an example, the report configuration consists of the identifier of the report configuration and ReportConfigNR.

[0413] As an example, the report configuration includes a report type.

[0414] As an example, the ReportConfigNR included in the report configuration includes a report type.

[0415] As an example, the report type is periodic.

[0416] As an example, the report type is time-triggered.

[0417] As an example, the report type is condition-triggered.

[0418] As an example, the report type is periodic, and the report configuration includes a reporting time interval (reportInterval).

[0419] As an example, the report type is periodic, and the report configuration includes the number of reports.

[0420] As an example, the report configuration in the first measurement configuration includes the first uplink delay configuration.

[0421] As an example, the first uplink delay configuration is used to configure the uplink delay.

[0422] As an example, the first uplink delay configuration is a configuration other than ul-DelayValueConfig.

[0423] As an example, the first uplink delay configuration is ul-DelayPDUSetValueConfig.

[0424] As an example, the first uplink delay configuration is ul-DelayValueConfigPDUSet.

[0425] As an example, the first uplink delay configuration is used to configure the delay measurement of the uplink PDCP source packet.

[0426] As an example, the meaning of the first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet includes: the first uplink delay configuration indicates that the delay measurement is for the uplink PDCP source packet.

[0427] As an example, the meaning of the first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is for the uplink PDCP source packet in the data packet.

[0428] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is for PDCP source packets on multiple DRBs.

[0429] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is based on the maximum delay of the uplink PDCP source packet.

[0430] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is based on the minimum delay of the uplink PDCP source packet.

[0431] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is based on the excessive packet delay of the uplink PDCP source packet.

[0432] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the delay measurement is performed based on the importance of the PDCP source packet.

[0433] As an embodiment, the meaning of the first uplink delay configuration for configuring the uplink PDCP source packet delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP source packet delay measurement is based on the average delay of the uplink PDCP source packet.

[0434] As an embodiment, performing the uplink PDCP source packet delay measurement according to the first uplink delay configuration includes counting the delay of the uplink PDCP source packet.

[0435] As an embodiment, performing the uplink PDCP source packet delay measurement according to the first uplink delay configuration includes generating a first delay. The first delay refers to the uplink PDCP source packet delay.

[0436] As an embodiment, performing the uplink PDCP source packet delay measurement according to the first uplink delay configuration includes counting the delay of the PDCP source packet measured within a time length T.

[0437] As an embodiment, the unit of the first delay is milliseconds.

[0438] As an embodiment, the first time delay is equal to the ratio of the sum of the time delays of each PDCP source packet in the M PDCP source groups sent to M, which means that: the first time delay is equal to the ratio of the sum of the time delays of each PDCP source packet in the M PDCP source groups sent to M.

[0439] As an embodiment, the first time delay is equal to the ratio of the sum of the time delays of each PDCP packet in the M PDCP packets sent to M, which means that: each PDCP source packet in the M PDCP source packets has its own time delay, and there are M time delays in total for the M PDCP source packets. The first time delay is equal to the ratio of the sum of the M time delays to M.

[0440] As an embodiment, the number of PDCP source packets counted in the uplink PDCP source packet time delay measurement performed in different time periods may be different.

[0441] As an embodiment, M is equal to the number of PDCP source packets sent.

[0442] As an embodiment, M is equal to the number of PDCP source packets sent within the measurement time.

[0443] As an embodiment, M is equal to the number of PDCP source packets sent within the first time length.

[0444] As an embodiment, the uplink PDCP source packet is a PDCP source packet generated by the uplink PDCP entity.

[0445] As an embodiment, the uplink PDCP source packet is a PDCP source packet processed by the uplink PDCP entity.

[0446] As an embodiment, the uplink PDCP source packet is a PDCP source packet received by the uplink PDCP entity from a higher layer.

[0447] As an embodiment, the uplink PDCP source packet includes at least one PDCP packet generated by the uplink PDCP entity.

[0448] As an embodiment, the uplink PDCP source packet includes at least one PDCP packet processed by the uplink PDCP entity.

[0449] As an embodiment, the uplink PDCP source packet includes at least one PDCP packet received by the uplink PDCP entity from a higher layer.

[0450] As an embodiment, the first measurement report includes a MeasurementReport message.

[0451] As an embodiment, the first measurement report includes measurement results.

[0452] As an embodiment, the first measurement report includes at least one field in the MeasurementReport message.

[0453] As an embodiment, the first measurement report includes at least one field in the UEAssistanceInformation message.

[0454] As an embodiment, the first measurement report is transmitted in a dedicated manner.

[0455] As an embodiment, the logical channel used by the first measurement report is the DCCH (dedicated Control channel).

[0456] As an embodiment, the first measurement report is transmitted using SRB1 (signaling radio bearer 1).

[0457] As an embodiment, the first measurement report is transmitted using SRB4 or SRB5 or SRB6.

[0458] As an embodiment, the first measurement report is unicast.

[0459] As an embodiment, the first measurement report is uplink.

[0460] In a specific implementation, step S5102 can be executed using the following sub-steps: measuring the first type of data packets in the data radio bearer and measuring the second type of data packets. For details, reference can be made to Embodiment 1 and the previous description.

[0461] In a specific implementation, step S5102 can also be executed using the following sub-steps: measuring the first type of data packets in the data radio bearer and ignoring the second type of data packets. For details, reference can be made to Embodiment 1 and the previous description.

[0462] Example 6

[0463] Embodiment 6 exemplifies a partial wireless signal transmission flowchart according to an embodiment of the present application. As shown in the appendix Figure 6 As shown, a partial process of wireless signal transmission and processing between the terminal U01 and the network device U02 is shown.

[0464] Figure 6Steps S6201 and S6101 are optional. When steps S6201 and S6101 do not exist, the terminal U01 can determine the QoS information of the data packet using the default configuration, and then refer to Figure 5 the process shown to complete the measurement and reporting of the delay, which will not be elaborated here. Otherwise, the network device U02 can send the QoS information in step S6201. Correspondingly, the terminal U01 can receive the QoS information in step S6101.

[0465] Combined with Figure 5 and Figure 6 , step S5201 is after step S6201.

[0466] Combined with Figure 5 and Figure 6 , step S5101 is after step S6101.

[0467] As an embodiment, the data packet in a DRB is associated with the QoS information.

[0468] As an embodiment, the QoS of the data packet is determined by the QoS information.

[0469] As an embodiment, the QoS information is the QoS information of the data packet.

[0470] As an embodiment, the QoS information is used to configure the category of the data packet.

[0471] Specifically in implementation, the QoS information is used to configure the first type of data packet and the second type of data packet.

[0472] As an embodiment, the QoS information is used to configure the importance parameter of the data packet.

[0473] Specifically in implementation, the QoS information is used to configure the respective importance parameters of the first type of data packet and the second type of data packet.

[0474] As an embodiment, the QoS information is used to configure the arrival characteristics of the data packet.

[0475] As a sub - embodiment of this embodiment, the arrival characteristics of the data packet are used to calculate the delay of the data packet.

[0476] As an embodiment, the QoS information is used to configure the delay requirement of the data packet.

[0477] As a sub - embodiment of this embodiment, the delay requirement of the data packet is used to calculate the delay of the uplink data packet.

[0478] As a sub - embodiment of this embodiment, the delay requirement of the data packet is used to calculate the excessive packet delay of the uplink data packet.

[0479] Example 7

[0480] Embodiment 7 exemplifies a wireless signal transmission flowchart according to an embodiment of the present application, as shown in the appendix Figure 7 as follows. Figure 7 It shows the wireless signal transmission process between the terminal U01 and the network device U02 when a data packet is a PDCP packet, where the first type of data packet is a PDCP source packet and the second type of data packet is a PDCP repair packet.

[0481] For Terminal U01 , in step S7101, QoS information is received; in step S7102, a first measurement configuration is received, and the first measurement configuration includes a first uplink delay configuration, and the first uplink delay configuration is used to configure the delay measurement of the uplink PDCP source packet; in step S7103, the data packets in a data radio bearer are measured to generate a first measurement result; in step S7104, a first measurement report is sent.

[0482] For Network device U02 , in step S7201, QoS information is sent, in step S7202, the first measurement configuration is sent; in step S7203, the first measurement report is received; the first measurement report at least includes the delay of the PDCP source packet.

[0483] In Embodiment 7, the data packet includes a first type of data packet and a second type of data packet, and the generation of the second type of data packet depends on the first type of data packet; the first measurement result at least includes the delay of the first type of data packet; the delay includes any one or more of the following: average delay; minimum delay; maximum delay; excessive packet delay.

[0484] Among them, the first measurement configuration and the first uplink delay configuration can refer to the relevant descriptions in Embodiment 5.

[0485] In a specific implementation, the terminal U01 that receives the QoS information and the first measurement configuration can execute step S7103, that is, measure the data packets in a data radio bearer to generate a first measurement result.

[0486] In one embodiment, the terminal U01 may measure only the first type of data packets in the data radio bearer and ignore the second type of data packets. At this time, the first type of data packets are the PDCP source packets, and the first measurement result includes only the delay of the first type of data packets, that is, only the delay of the PDCP source packets, which is referred to as the first delay here.

[0487] In a specific implementation, the first delay is the average delay of the PDCP source packets.

[0488] In a specific implementation, the first delay includes but is not limited to the average delay of the PDCP source packets; the minimum delay in the PDCP source packets; the maximum delay in the PDCP source packets; the excess packet delay.

[0489] As an example, the delay of the first type of data packets refers to the delay of the PDCP source packets.

[0490] In one embodiment, the terminal U01 may measure the first type of data packets and the second type of data packets in the data radio bearer separately. At this time, the first type of data packets are the PDCP source packets, and the second type of data packets are PDCP repair packets, and the PDCP repair packets are generated from the PDCP source packets. The first measurement result includes the delay of the PDCP source packets (referred to as the first delay) and the delay of the PDCP repair packets (referred to as the second delay).

[0491] In a specific implementation, the second delay is the average delay of the PDCP repair packets.

[0492] In a specific implementation, the second delay includes but is not limited to the average delay of the PDCP repair packets; the minimum delay in the PDCP repair packets; the maximum delay in the PDCP repair packets; the excess packet delay.

[0493] As an example, the first measurement report includes the first measurement result. In a specific implementation, the first measurement report includes only the first delay. Alternatively, the first measurement report includes the first delay and the second delay.

[0494] As an example, the first type of data packets are PDCP source packets, the second type of data packets are PDCP repair packets, and the second type of data packets are generated from the first type of data packets.

[0495] As an example, the first type of data packet is a PDCP PDU source packet, the second type of data packet is a PDCP PDU repair packet, and the PDCP PDU repair packet is generated based on the PDCP PDU source packet.

[0496] As an example, the first type of data packet is a PDCP source data packet group formed by multiple PDCP PDU source packets (e.g., PDCP PDU set), the second type of data packet is a PDCP repair data packet group formed by multiple PDCP PDU repair packets, and each PDCP PDU repair packet in the PDCP repair data packet group is generated based on one or more PDCP PDU source packets in the PDCP source data packet group.

[0497] As an example, the first type of data packet is a PDCP SDU source packet, the second type of data packet is a PDCP SDU repair packet, and the PDCP SDU repair packet is generated based on the PDCP SDU source packet.

[0498] As an example, the first type of data packet is a PDCP source data packet group formed by multiple PDCP SDU source packets, the second type of data packet is a PDCP repair data packet group formed by multiple PDCP SDU repair packets, and each PDCP SDU repair packet in the PDCP repair data packet group is generated based on one or more PDCP SDU source packets in the PDCP source data packet group.

[0499] As an example, the first measurement configuration includes the first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet.

[0500] In one implementation, the delay measurement of the uplink PDCP source packet refers to measuring the delay of the uplink PDCP source packet on the target DRB. Among them, the first measurement configuration includes the identifier (such as ID) of the target DRB.

[0501] As an example, the delay of the PDCP source packet refers to the delay of the uplink PDCP source packet.

[0502] As an embodiment, the first uplink delay is configured to configure the delay measurement of uplink PDCP source packets; the first measurement result includes the first delay, and the first delay is equal to the ratio of the sum of the delays of each of the M PDCP source packets arriving within the time length T to M; M is a positive integer; the delay of any one of the M PDCP source packets is equal to the time interval between the arrival time of any one of the M PDCP source packets and the time when the uplink MAC PDU carrying any one of the M PDCP source packets is scheduled for transmission.

[0503] As an embodiment, the first uplink delay configuration is one of the report configuration lists included in the first measurement configuration.

[0504] As an embodiment, the first uplink delay configuration is ul-DelayValueConfig.

[0505] As an embodiment, the time when the uplink MAC PDU carrying any one of the M PDCP source packets is scheduled for transmission may refer to: the earliest time when all the uplink MAC PDUs carrying any one of the M PDCP source packets are scheduled for transmission.

[0506] As an embodiment, the time when the uplink MAC PDU carrying any one of the M PDCP source packets is scheduled for transmission refers to: the time when the MAC layer requests the PDCP layer to transmit any one of the M PDCP source packets.

[0507] As an embodiment, when the MAC receives the scheduling signaling, it requests data from the PDCP layer.

[0508] As an embodiment, the first delay is equal to the average of the time that each of the M PDCP source packets is cached in the PDCP entity.

[0509] As an embodiment, the set of the M PDCP source packets is a data burst.

[0510] Those skilled in the art understand that step S7101 can refer to Figure 6 step S6101 therein, and step S7201 can refer to Figure 6 step S6201 therein. Steps S7102 to S7104, step S7202, and step S7203 can respectively refer to the relevant descriptions of the embodiments shown in Figures 1 to 5 and will not be elaborated here.

[0511] Example 8

[0512] Embodiment 8 exemplifies a partial wireless signal processing flowchart according to an embodiment of the present application, as shown in the appendix Figure 8 as follows. Figure 8 It shows that the terminal sends different measurement reports under different conditions. Typically, the terminal is a UE.

[0513] As an embodiment, the terminal may be the terminal in Embodiments 1 to 7.

[0514] Combined with any of the scenarios in Embodiments 5, 6, and 7, after receiving the QoS information and the first measurement configuration, the terminal may measure the data packets in a DRB. Among them, the data packets include the first type of data packets and the second type of data packets, and the second type of data packets is generated based on the first type of data packets. Under this condition, the situation shown in Figure 8 may occur.

[0515] Specifically, referring to Figure 8 , in step S801, the terminal determines whether the first type of data packets is discarded. If not, that is, the first type of data packets is not discarded, the terminal may send a first measurement report in step S8021. The generation and sending of the first measurement report may refer to the descriptions in Embodiments 1, 5 to 7.

[0516] In specific implementation, if the first type of data packets is discarded, step S8022 may be executed to send a second measurement report. The second measurement report is generated when the first type of data packets is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0517] Optionally, if the first type of data packets is discarded, the sending of the first measurement report and the second measurement report may be abandoned.

[0518] As an embodiment, the first measurement configuration includes: when discarding the first type of data packets, abandoning the sending of the measurement report. At this time, the terminal may abandon sending the first measurement report and the second measurement report.

[0519] As an embodiment, the first measurement configuration includes: when discarding the first type of data packets, configuring to send a second measurement report. At this time, the terminal may send the second measurement report, and the second measurement report is sent based on the first measurement configuration.

[0520] Example 9

[0521] Example 9 exemplifies a schematic diagram for determining the delay of N PDCP source packets according to an embodiment of the present application. As Figure 9 shown, the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed are used to determine the delay of the N PDCP source packets.

[0522] For ease of description, in this embodiment, the first type of data packet is regarded as a PDCP source packet. However, this embodiment does not limit the type of the first type of data packet.

[0523] As an embodiment, the meaning that the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed are used to determine the delay of the N PDCP source packets is that: the arrival time of a PDCP source packet included in the N PDCP source packets and the time when this PDCP source packet is processed are jointly used to determine the delay of the N PDCP source packets.

[0524] As an embodiment, the meaning that the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed are used to determine the delay of the N PDCP source packets is that: the time interval between the arrival time of a PDCP source packet included in the N PDCP source packets and the time when this PDCP source packet is processed is the delay of the N PDCP source packets.

[0525] As an embodiment, the meaning that the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed are used to determine the delay of the N PDCP source packets is that: the arrival time of the first PDCP source packet included in the N PDCP source packets and the processing time of the last PDCP source packet processed are jointly used to determine the delay of the N PDCP source packets.

[0526] As an embodiment, the meaning that the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed are used to determine the delay of the N PDCP source packets is that: the delays of each PDCP source packet included in the N PDCP source packets are jointly used to determine the delay of the N PDCP source packets.

[0527] As an example, the meaning of using the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed to determine the delay of the N PDCP source packets is that: the arrival time of the first PDCP source packet included in the N PDCP source packets and the time when the last transmitted PDCP source packet is transmitted together determine the delay of the N PDCP source packets.

[0528] As an example, the meaning of using the arrival time of the first PDCP source packet among the N PDCP source packets and the time when the last PDCP source packet among the N PDCP source packets is processed to determine the delay of the N PDCP source packets is that: the arrival time of the first PDCP source packet included in the N PDCP source packets and the time when the default PDCP source packet is processed together determine the delay of the N PDCP source packets.

[0529] As a sub - example of this example, the default PDCP source packet among the N PDCP source packets is the PDCP source packet that is processed last among the N PDCP source packets.

[0530] As a sub - example of this example, the default PDCP source packet among the N PDCP source packets is the PDCP source packet that is transmitted last among the N PDCP source packets.

[0531] As a sub - example of this example, the default PDCP source packet among the N PDCP source packets is the PDCP source packet that is scheduled last among the N PDCP source packets.

[0532] As a sub - example of this example, the default PDCP source packet among the N PDCP source packets is the PDCP source packet with the largest sequence number among the N PDCP source packets.

[0533] As a sub - example of this example, the default PDCP source packet among the N PDCP source packets is the second - last PDCP source packet that is transmitted or scheduled among the N PDCP source packets.

[0534] As an example, the first uplink delay configuration indicates that one PDCP source packet among the N PDCP source packets is the default PDCP source packet.

[0535] As a sub - example, the default PDCP source packet is the middle PDCP source packet.

[0536] As a sub - example, the default PDCP source packet is the last PDCP source packet.

[0537] As a sub - embodiment, the default PDCP source packet is the source packet with the largest sequence number.

[0538] As an embodiment, the first PDCP source packet is the earliest - arrived PDCP packet among the N PDCP source packets.

[0539] As an embodiment, the first PDCP source packet is the PDCP packet with the earliest sequence number among the N PDCP source packets.

[0540] As an embodiment, the last PDCP source packet is the PDCP source packet that is transmitted last among the N PDCP source packets.

[0541] As an embodiment, the last PDCP source packet is the PDCP source packet that is the last to be completely transmitted among the N PDCP source packets.

[0542] As an embodiment, the last PDCP source packet is the PDCP source packet that is the latest - scheduled among the N PDCP source packets.

[0543] As a sub - embodiment of this embodiment, the latest - scheduled means scheduled for transmission.

[0544] As a sub - embodiment of this embodiment, the latest - scheduled PDCP source packet is the PDCP source packet carried by the latest - scheduled MAC PDU among the MAC PDUs carrying at least the first part of the N PDCP source packets.

[0545] As a sub - embodiment of this embodiment, the latest - scheduled PDCP source packet is the PDCP source packet carried by the latest - scheduled MAC PDU among the MAC PDUs respectively carrying the first part of each of the N PDCP source packets.

[0546] As a sub - embodiment of this embodiment, the latest - scheduled PDCP source packet is the PDCP source packet carried by the latest - scheduled MAC PDU among the MAC PDUs carrying the PDCP packets of the N PDCP source packets.

[0547] As a sub - embodiment of this embodiment, the earliest - scheduled MAC PDU among the MAC PDUs carrying at least a part of the \(i\) - th PDCP packet in the \(N\) PDCP source packets is MAC PDU \(i\); where \(i\) is any integer between 1 and \(N\), including 1 and \(N\). Then, if the latest - scheduled MAC PDU among MAC PDU 1, MAC PDU 2, …, MAC PDU \(N\) is MAC PDU \(j\), the latest - scheduled PDCP packet in the \(N\) PDCP source packets is the \(j\) - th PDCP packet.

[0548] As an embodiment, a PDCP source packet being scheduled means that the MAC PDU carrying the PDCP source packet is scheduled.

[0549] As an embodiment, a PDCP source packet being scheduled means that the resources indicated by the scheduling for transmission are used to transmit the PDCP source packet.

[0550] As an embodiment, a PDCP source packet being scheduled means that the MAC PDU carrying at least the first part of the PDCP source packet is scheduled.

[0551] As an embodiment, a PDCP source packet being scheduled means that the resources indicated by the scheduling for transmission are received for transmitting at least the first part of the PDCP source packet.

[0552] Example 10

[0553] Embodiment 10 exemplifies a schematic diagram for calculating the delay according to an embodiment of the present application. As shown in the appendix Figure 10 As shown, Embodiment 10 gives a specific implementation manner for determining the delay of the \(N\) PDCP source packets when the first - type data packets are \(N\) PDCP source packets. Among them, the \(N\) PDCP source packets are uplink PDCP source packets. The uplink PDCP source packets can be PDCP source PDUs.

[0554] In this embodiment, \(M(T, drbid)\) represents the average delay of the uplink PDCP source packets of a certain DRB within the time period \(T\), \(T\) represents the time period for performing the measurement, and \(drbid\) represents the DRB identifier being measured. Preferably, the unit of \(T\) is \(0.1\) ms. For the convenience of description, \(M(T, drbid)\) is referred to as the first delay.

[0555] In this embodiment, For indexing one of the N PDCP source packets. The index i indexes the i-th PDCP source packet among the N PDCP source packets; tArrival(i) represents the time when the uplink PDCP source packet i arrives at the PDCP upper layer service access point (SAP), and tDeliv(i) represents the transmission time when the uplink MAC PDU k containing the first part of the uplink PDCP source packet i is scheduled for transmission. I(T) represents the total number of uplink PDCP source packets received by the PDCP (layer) within the time period T.

[0556] In this embodiment, M(T, drbib) is equal to the integer part of the ratio of the sum of the delays of each PDCP source packet among the N PDCP source packets to I(T).

[0557] As a sub - embodiment of this embodiment, the integer part is the floor function.

[0558] In one implementation, M(T, drbid) represents the average delay measured for the N PDCP source PDUs within the time period T, M() characterizes the formula for calculating the delay of the uplink PDCP source PDU, and is the result of the uplink PDCP source PDU delay measurement performed within the time period T. T represents the time period for performing the measurement, tArrival(i) represents the time when the uplink PDCP source SDU i arrives at the PDCP upper layer service access point (SAP), tDeliv(i) represents the transmission time when the uplink MAC PDU k containing the first part of the uplink PDCP source SDU i is scheduled for transmission; i represents a UL PDCP SDU received by the PDCP (layer) within the time period T. I(T) represents the total number of uplink PDCP source SDUs received by the PDCP (layer) within the time period T, and drbid represents the DRB identifier being measured.

[0559] As an embodiment, the delay of the first - type data packet is equal to the first delay.

[0560] As an embodiment, the unit of the first delay is 0.1 millisecond.

[0561] As an embodiment, the unit of the first delay is 1 millisecond.

[0562] As an embodiment, the unit of the first delay is 10 milliseconds.

[0563] As an embodiment, the unit of the first delay is 100 milliseconds.

[0564] As an embodiment, the unit of the first delay is 1 second.

[0565] As an embodiment, the terminal measures the N PDCP source packets within the time period T.

[0566] In one embodiment, i represents the identifier of a UL PDCP SDU received by the PDCP (layer) within the time period T. I(T) represents the total number of PDCP SDUs received by the PDCP (layer) within the time period T. tArrival(i) represents the time when the uplink PDCP source packet i arrives at the PDCP upper layer service access point (SAP), and tDeliv(i) represents the transmission time when the first part of the uplink MAC PDU k containing the uplink PDCP source packet i is scheduled for transmission.

[0567] As an example, the arrival time includes the time of arrival at the PDCP higher service access point.

[0568] As an example, the N PDCP source packets are determined as the nth PDCP source packet in the order of arrival.

[0569] As a sub - embodiment of this example, for instance, the earliest - arrived PDCP source packet among the N PDCP source packets is the first PDCP source packet.

[0570] As an example, the N PDCP source packets are determined as the nth PDCP source packet in the order of the arrival times of the earliest - arrived PDCP packets they contain.

[0571] As an example, the second - type data packets are ignored when calculating the first delay.

[0572] As an example, the second - type data packets are excluded when calculating the first delay.

[0573] As an example, the second - type data packets are not considered when calculating the first delay.

[0574] As an example, when the first - type data packets are N PDCP source packets and the second - type data packets are PDCP repair packets of the N PDCP source packets, the influence of the PDCP repair packets is not considered when calculating the first delay of the N PDCP source packets.

[0575] As an example, the first delay determined by the above method is more accurate for measuring the maximum delay of PDCP source packets, which is beneficial to grasping the bottom line of network transmission.

[0576] Example 11

[0577] Example 11 illustrates a schematic diagram for calculating the delay of the first - type data packets according to an embodiment of the present application.

[0578] As shown in the appendixFigure 11 As shown in Figure 11 , Embodiment 11 provides a specific implementation for determining the delay of N PDCP source packets when the first type of data packet is N PDCP source packets and the second type of data packet is its PDCP repair packet. Among them, the N PDCP source packets are uplink PDCP source packets. The uplink PDCP source packets may be PDCP source PDUs.

[0579] In this embodiment, M(T_sandr, drbid) represents the average delay of the uplink PDCP source packets of a certain DRB within the time period T_sandr. T_sandr represents the time period for performing the measurement, and drbid represents the DRB identifier to be measured. It should be noted that T_sandr means that within the time period for performing the measurement, the terminal receives the N PDCP source packets and at least some of their repair packets together.

[0580] For ease of explanation, M(T_sandr, drbid) is referred to as the first delay.

[0581] Preferably, the unit of T_sandr is 0.1 ms.

[0582] In this embodiment, is used to index one of the N PDCP source packets. The i indexes the i-th PDCP source packet among the N PDCP source packets; tArrival(i) represents the moment when the uplink PDCP source packet i reaches the PDCP upper layer service access point (SAP), and tDeliv(i) represents the transmission moment when the first part of the uplink MAC PDU k containing the uplink PDCP source packet i is scheduled for transmission. I(T_sandr) represents the total number of uplink PDCP source packets received by the PDCP (layer) within the time period T_sandr.

[0583] In this embodiment, M(T_sandr, drbib) is equal to the integer part of the ratio of the sum of the delays of each PDCP source packet among the N PDCP source packets to I(T_sandr).

[0584] As a sub - embodiment of this embodiment, the integer part is rounded down.

[0585] In one embodiment, M(T_sandr, drbid) represents the average delay measured for the N PDCP source PDUs within the time period T_sandr. M() characterizes the formula for calculating the delay of the uplink PDCP source PDUs and is the result of the uplink PDCP source PDU delay measurement performed within the time period T_sandr. T_sandr represents the time period during which the measurement is performed. tArrival(i) represents the time when the uplink PDCP source SDU i arrives at the PDCP upper layer service access point (SAP). tDeliv(i) represents the transmission time when the first part of the uplink MAC PDU k containing the uplink PDCP source SDU i is scheduled for transmission. i represents a UL PDCP SDU received by the PDCP (layer) within the time period T_sandr. I(T_sandr) represents the total number of uplink PDCP source SDUs received by the PDCP (layer) within the time period T_sandr. drbid represents the DRB identifier being measured.

[0586] As an example, the delay of the first type of data packet is equal to the first delay.

[0587] As an example, the unit of the first delay is one of 0.1 millisecond, 1 millisecond, 10 milliseconds, 100 milliseconds, 1 second.

[0588] As an example, the terminal measures the N PDCP source packets within the time period T_sandr.

[0589] In one embodiment, i represents the identifier of a UL PDCP SDU received by the PDCP (layer) within the time period T_sandr. I(T_sandr) represents the total number of PDCP SDUs received by the PDCP (layer) within the time period T_sandr. tArrival(i) represents the time when the uplink PDCP source packet i arrives at the PDCP upper layer service access point (SAP). tDeliv(i) represents the transmission time when the first part of the uplink MAC PDU k containing the uplink PDCP source packet i is scheduled for transmission.

[0590] As an example, the arrival time includes the time of arrival at the PDCP higher service access point.

[0591] As an example, the N PDCP source packets are determined as the nth PDCP source packet in the order of arrival.

[0592] As a sub - example of this example, for instance, the earliest - arriving PDCP source packet among the N PDCP source packets is the first PDCP source packet.

[0593] As an example, the N PDCP source packets are determined as the nth PDCP source packet in the order of the arrival times of the earliest arrived PDCP packets they contain.

[0594] As an example, the terminal may measure the UL PDCP queue delay at the DRB level. Under the assumption that all QoS flows mapped to the same DRB receive the same QoS treatment, it is determined by the network device (such as gNB, NR base station) to convert the DRB-level delay to the QoS-level delay; if multiple DRBs are mapped to the same QoS, the network device calculates the QoS-level delay.

[0595] Example 12

[0596] Embodiment 12 exemplifies a schematic diagram for calculating the UL PDCP excessive packet delay according to an embodiment of the present application, as shown in the appendix Figure 12 shown. The measurement and calculation of the UL PDCP excessive packet delay are performed on the terminal side. Preferably, it is performed at the PDCP layer.

[0597] As an example, the purpose of the terminal to measure the UL PDCP excessive packet delay is to measure the excessive data packet delay in the PDCP layer to verify the QoS of MDT.

[0598] In a sub-embodiment of this embodiment, the excessive data packet refers to the PDCP excessive source packet.

[0599] As an example, the excessive packet delay includes the second excessive packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the total number of the second data packets received by the terminal; wherein, the total number of the second data packets received by the terminal excludes the number of the second type of data packets. Optionally, the excessive packet delay is the second excessive packet delay.

[0600] In a sub-embodiment of this embodiment, the second excessive packet delay refers to the UL PDCP excessive packet delay. Wherein, the first type of data packets refers to the PDCP source packets, such as UL PDCP source packets. The total number of the second data packets refers to the total number of the PDCP source packets received for a certain DRB during the measurement period.

[0601] Embodiment 12 gives some embodiments and implementation manners for determining the excessive packet delay of the PDCP source packet when the first type of data packet is a PDCP source packet and the second type of data packet is a PDCP repair packet of the PDCP source packet. Among them, the PDCP source packet is a UL PDCP source packet. The UL PDCP source packet may be a PDCP source PDU or a PDCP source SDU.

[0602] In one implementation manner, the UL PDCP excessive packet delay refers to the excessive packet delay of the PDCP source data packet in each DRB in the uplink. It represents the ratio of the data packets in the received UL PDCP source data packets that exceed the threshold of the configured delay to the received UL PDCP source data packets in each DRB in the UL. The delay of each source data packet is calculated from the time when the source data packet arrives at the PDCP upper layer SAP until the uplink grant available for transmitting the source data packet, which already includes the delay required for the terminal to obtain the resource grant (from sending SR / RACH to obtaining the first grant). This measurement is performed separately for each DRB.

[0603] In one implementation manner, the PDCP excessive packet delay refers to the excessive packet delay of the PDCP source data in each DRB in the uplink. It represents the ratio of the data packets in the received UL PDCP source SDUs that exceed the threshold of the configured delay to the received UL PDCP source SDUs in each DRB in the UL. The delay of each source data packet is calculated from the time when the source data packet arrives at the PDCP upper layer SAP until the uplink grant available for transmitting the source data packet, which already includes the delay required for the terminal to obtain the resource grant (from sending SR / RACH to obtaining the first grant). This measurement is performed separately for each DRB.

[0604] Specifically, Embodiment 12 gives an implementation manner for measuring the UL PDCP excessive packet delay when the first type of data packet is a UL PDCP source packet and the second type of data packet is a PDCP repair packet generated therefrom.

[0605] In one embodiment, the first type of data packet is a UL PDCP packet, and the terminal performs UL PDCP excessive packet delay measurement on the UL PDCP packet in a DRB at the PDCP layer, and the generated first measurement result includes the UL PDCP excessive packet delay.

[0606] In one embodiment, the purpose of performing the UL PDCP excessive packet delay measurement is to measure the excessive packet delay in the PDCP layer to verify the QoS of MDT.

[0607] As an embodiment, the first measurement configuration includes an over-packet delay configuration.

[0608] In some embodiments, the over-packet delay configuration includes a DRB for which the terminal is to perform PDCP over-packet delay measurement, and a list of DRB identifiers.

[0609] As a sub-embodiment of this embodiment, the UL PDCP over-packet delay measurement includes a configured delay threshold.

[0610] As an embodiment, a candidate value of the delay threshold is 1 ms.

[0611] As an embodiment, a candidate value of the delay threshold is 5 ms.

[0612] As an embodiment, a candidate value of the delay threshold is 10 ms.

[0613] As an embodiment, the terminal may calculate the over-packet delay based on the configuration information of the delay threshold.

[0614] In a specific implementation, the delay threshold may be sent through the UL-DelayConfig IE.

[0615] As an embodiment, the network device determines the threshold according to the QoS requirements of the UL PDCP over-packet.

[0616] As an embodiment, the unit of the UL PDCP over-packet delay is one of 0.1 millisecond, 1 millisecond, 10 milliseconds, 100 milliseconds, and 1 second.

[0617] In still some other embodiments, the over-packet delay configuration includes a mapping relationship between the DRB identifier and the list of delay thresholds. Optionally, the mapping relationship may be a one-to-one mapping, that is, each DRB is assigned a separate delay threshold; it may also be a one-to-many mapping. For example, one delay threshold may apply to multiple DRBs. For example, a DRB may be configured with multiple delay thresholds.

[0618] As an embodiment, based on the over-packet delay configuration, the terminal may send a first measurement report including the over-packet delay measurement result to the network device, and the first measurement report may include a list of PDCP over-packet delay measurements.

[0619] As an embodiment, the first measurement report is part of the minimized drive test (MDT) report of the terminal.

[0620] As an example, the first measurement report includes the second excessive packet delay, in other words, the first measurement report includes the UL PDCP excessive packet delay.

[0621] In this embodiment, M(T, drbid) represents the proportion of UL PDCP source packets that exceed the configured delay threshold within a time period T for a certain DRB, where the first part of the UL PDCP source packet is scheduled for transmission in the ULMAC PDU. Here, T represents the time period for performing the measurement, and drbid represents the DRB identifier being measured. Preferably, the unit of T is 0.1 ms.

[0622] In this embodiment, nExcess(T, drbid) represents the number of PDCP source packets in the UL PDCP source packets whose delay exceeds the delay threshold for the data radio bearer with DRB identifier drbid within the time period T.

[0623] As an example, the delay of the i-th PDCP source packet in the UL PDCP source packets is tULdelay(i).

[0624] As a sub - embodiment of this embodiment, the i-th PDCP source packet is any one of the UL PDCP source packets.

[0625] Exemplarily, M(T, drbid) represents the proportion of UL PDCP SDUs that exceed the configured delay threshold within a time period T for the data radio bearer with DRB identifier drbid, where the first part of the UL PDCP SDU is scheduled for transmission in the ULMAC PDU. Here, T represents the time period for performing the measurement, and drbid represents the DRB identifier being measured. Preferably, the unit of T is 0.1 ms.

[0626] Exemplarily, nExcess(T, drbid) represents the number of PDCP SDUs when the UL delay tULdelay(i, drbid) exceeds the delay threshold for the data radio bearer with DRB identifier drbid within the time period T.

[0627] In this embodiment, nTotal(T, drbid) represents the number of UL PDCP source packets transmitted for the data radio bearer with DRB identifier drbid within the time period T.

[0628] Exemplarily, nTotal(T, drbid) represents the number of PDCP source SDUs transmitted for the data radio bearer with DRB identifier drbid within the time period T, where the scheduled ULMAC PDU includes the first part of the UL PDCP source SDU.

[0629] In this embodiment, tULdelay(i, drbid) represents the queuing delay of the PDCP layer of the terminal observed during the time period T in the data radio bearer with the DRB identifier drbid, from the UL PDCP source packet i arriving at the PDCP upper layer SAP to the lower layer UL source packet k including the first part of the UL PDCP source packet i being scheduled for transmission. tArrival(i) represents the time when the uplink PDCP source packet i arrives at the PDCP upper layer service access point (SAP), and tDeliv(i) represents the transmission time when the uplink MAC PDU k including the first part of the uplink PDCP source packet i is scheduled for transmission.

[0630] As an embodiment, the lower layer includes at least one of the physical layer, MAC sublayer, RLC sublayer, and PDCP sublayer.

[0631] Exemplarily, tULdelay(i, drbid) represents the queuing delay of the PDCP layer of the terminal observed during the time period T in the data radio bearer with the DRB identifier drbid, from the UL PDCP SDU i arriving at the PDCP upper layer SAP to the UL MAC PDU k including the first part of the UL PDCP SDU i being scheduled for transmission. tArrival(i) represents the time when the uplink PDCP source SDU i arrives at the PDCP upper layer service access point (SAP), and tDeliv(i) represents the time when the uplink MAC PDU k including the first part of the uplink PDCP source SDU i is scheduled for transmission.

[0632] As an embodiment, when the terminal delays upon obtaining the UL PDCP excess packet, the first measurement result can be obtained. Thereafter, the terminal can at least send the first measurement result as the first measurement report to the network device.

[0633] Example 13

[0634] Embodiment 13 gives another implementation manner for determining the measurement of the UL PDCP excess packet delay. The measurement and calculation of the UL PDCP excess packet delay are performed on the terminal side. Preferably, it is performed at the PDCP layer.

[0635] As an embodiment, the purpose of the terminal to perform the UL PDCP excess packet delay measurement is to measure the excess data packet delay in the PDCP layer to verify the QoS of MDT.

[0636] As an example, the excessive packet delay includes a first excessive packet delay, which is the ratio of the number of the first type of data packets exceeding a configured delay threshold during a measurement period to the total number of the first data packets received by the terminal; wherein, the total number of the first data packets received by the terminal includes the number of the second type of data packets. Optionally, the excessive packet delay is the first excessive packet delay.

[0637] In a sub - example of this example, the first excessive packet delay refers to the UL PDCP excessive packet delay. Wherein, the first type of data packets refers to PDCP source packets, such as UL PDCP source packets, and the total number of the first data packets refers to the total number of the PDCP source packets and the generated PDCP repair packets received for a certain DRB during the measurement period.

[0638] As an example, the first excessive packet delay is the ratio of the number of UL PDCP source packets exceeding a configured delay threshold to the total number of the first UL PDCP packets received by the terminal, and the total number of the first UL PDCP packets is the sum of the number of UL PDCP source packets and their PDCP repair packets.

[0639] Example 13 gives some examples and implementations for determining the excessive packet delay of PDCP source packets when the first type of data packets are PDCP source packets and the second type of data packets are PDCP repair packets of the PDCP source packets. Wherein, the PDCP source packets are UL PDCP source packets. The UL PDCP source packets can be PDCP source PDUs or PDCP source SDUs.

[0640] In an implementation, the UL PDCP excessive packet delay refers to the excessive packet delay of PDCP source data packets in each DRB in the uplink. It represents the ratio of the data packets exceeding the configured delay threshold among the received UL PDCP source data packets to the sum of the received UL PDCP source data packets and their generated PDCP repair packets in each DRB in the UL. The delay of each source data packet is calculated from the time when the source data packet arrives at the PDCP upper - layer SAP until the uplink grant available for transmitting the source data packet, which already includes the delay required for the terminal to obtain the resource grant (from sending SR / RACH to obtaining the first grant). This measurement is performed separately for each DRB.

[0641] In one embodiment, the PDCP excessive packet delay refers to the PDCP source data excessive packet delay in each DRB on the uplink. It represents the ratio of the data packets in the received UL PDCP source SDUs that exceed the configured delay threshold to the sum of the received UL PDCP source SDUs and the PDCP retransmission SDUs generated thereby in each DRB on the UL. The delay of each source data packet is calculated starting from the arrival of the source data packet at the PDCP upper-layer SAP until the uplink grant available for transmitting the source data packet, which already includes the delay required for the terminal to obtain the resource grant (from sending the SR / RACH to obtaining the first grant). This measurement is performed separately for each DRB.

[0642] As an example, the first measurement configuration includes a first uplink delay configuration, and the first uplink delay configuration includes an excessive packet delay configuration.

[0643] In some embodiments, the excessive packet delay configuration includes the DRBs for which the terminal is to perform PDCP excessive packet delay measurement, and a list of DRB identifiers.

[0644] In a specific implementation, the excessive packet delay configuration includes a configured delay threshold.

[0645] As an example, a candidate value for the delay threshold is 1 ms.

[0646] As an example, a candidate value for the delay threshold is 5 ms.

[0647] As an example, a candidate value for the delay threshold is 10 ms.

[0648] As an example, the terminal can calculate the excessive packet delay based on the configuration information of the delay threshold.

[0649] In a specific implementation, the delay threshold may be sent through the UL-DelayConfig IE.

[0650] As a sub-example of this example, the UL PDCP excessive packet delay measurement includes a configured delay threshold.

[0651] As an example, a candidate value for the delay threshold is 1 ms.

[0652] As an example, a candidate value for the delay threshold is 5 ms.

[0653] As an example, a candidate value for the delay threshold is 10 ms.

[0654] As an embodiment, the network device determines the threshold according to the QoS requirements of the ULPDCP excess packet.

[0655] As an embodiment, the unit of the ULPDCP excess packet delay is one of 0.1 millisecond, 1 millisecond, 10 milliseconds, 100 milliseconds, and 1 second.

[0656] In still other embodiments, the excess packet delay configuration includes a mapping relationship between the DRB identifier and the delay threshold list. Optionally, the mapping relationship can be a one-to-one mapping, that is, each DRB is assigned a separate delay threshold; it can also be a one-to-many mapping. Exemplarily, one delay threshold can be applicable to multiple DRBs. Exemplarily, a DRB can be configured with multiple delay thresholds.

[0657] As an embodiment, based on the excess packet delay configuration, the terminal can send a first measurement report including the excess packet delay measurement result to the network device, and the first measurement report can include a list of PDCP excess packet delay measurements.

[0658] As an embodiment, the first measurement report is a part of the minimized drive test (MDT) report of the terminal.

[0659] As an embodiment, the first measurement report includes the first excess packet delay. In other words, the first measurement report includes the ULPDCP excess packet delay in this embodiment.

[0660] As an embodiment, the calculation formula of the first excess packet delay can refer to Figure 12 , and the meanings of the parameters are as follows.

[0661] Refer to Figure 12 , M(T, drbid) represents the proportion of the first part of the UL MAC PDU including the UL PDCP source packet in the UL PDCP source packets that exceed the configured delay threshold within a time period T for a certain DRB. Wherein, T represents the time period for performing the measurement, and drbid represents the DRB identifier being measured. Preferably, the unit of T is 0.1 ms.

[0662] In one embodiment, M(T, drbid) refers to the first excess packet delay.

[0663] In this embodiment, tExcess(T, drbid) represents the number of PDCP source packets whose delay exceeds the delay threshold in the UL PDCP source packets for the data radio bearer with the DRB identifier drbid within the time period T.

[0664] As an example, the delay of the i-th PDCP source packet in the UL PDCP source packets is tULdelay(i).

[0665] As a sub-example of this example, the i-th PDCP source packet is any one of the UL PDCP source packets.

[0666] Exemplarily, M(T, drbid) represents the ratio of the UL MAC PDUs including the first part of the UL PDCP SDUs that are scheduled for transmission among the UL PDCP SDUs exceeding the configured delay threshold within the time period T for the data radio bearer with the DRB identifier drbid. Here, T represents the time period for performing the measurement, and drbid represents the DRB identifier being measured. Preferably, the unit of T is 0.1 ms.

[0667] Exemplarily, nExcess(T, drbid) represents the number of PDCP SDUs when the UL delay tULdelay(i, drbid) of the data radio bearer with the DRB identifier drbid exceeds the delay threshold within the time period T.

[0668] In this example, xTotal(T, drbid) represents the number of UL PDCP source packets transmitted for the data radio bearer with the DRB identifier drbid within the time period T.

[0669] Exemplarily, nTotal(T, drbid) represents the sum of the number of PDCP source SDUs transmitted and the number of PDCP repair SDUs generated for the data radio bearer with the DRB identifier drbid within the time period T, where the scheduled UL MAC PDU includes the first part of the UL PDCP source SDU.

[0670] In this example, tULdelay(i, drbid) represents the queuing delay of the PDCP layer of the terminal observed from the arrival of the UL PDCP source packet i at the PDCP upper layer SAP to the transmission time of the lower layer UL source packet k including the first part of the UL PDCP source packet i being scheduled for transmission within the time period T for the data radio bearer belonging to the DRB identifier drbid. tArrival(i) represents the time when the uplink PDCP source packet i arrives at the PDCP upper layer service access point (SAP), and tDeliv(i) represents the transmission time when the uplink MAC PDU k includes the first part of the uplink PDCP source packet i being scheduled for transmission.

[0671] As an example, the lower layer includes at least one of the physical layer, MAC sub-layer, RLC sub-layer, and PDCP sub-layer.

[0672] Exemplarily, tULdelay(i, drbid) represents the queuing delay of the PDCP layer of the terminal observed within a time period T in the data radio bearer with DRB identifier drbid, from the arrival of the UL PDCP SDU i at the ULPDCP upper-layer SAP to the ULMAC PDU k including the first part of the ULPDCP SDU i being scheduled for transmission. tArrival(i) represents the time when the uplink PDCP source SDU i arrives at the PDCP upper-layer service access point (SAP), and tDeliv(i) represents the transmission time when the uplink MAC PDU k includes the first part of the uplink PDCP source SDU i being scheduled for transmission.

[0673] As an embodiment, when the terminal delays upon obtaining the UL PDCP excess packet, a first measurement result including the first excess packet delay can be obtained. Subsequently, the terminal can at least send the first measurement result to the network device as the first measurement report.

[0674] As an embodiment, the uplink PDCP excess packet group delay determined by the above method is more accurate for obtaining the measurement result based on the average delay of the PDCP packet group, which is beneficial for grasping the comprehensive performance of network transmission.

[0675] Example 14

[0676] Embodiment 14 exemplifies a flowchart of a measurement report receiving method according to an embodiment of the present application, as shown in the appendix Figure 13 as shown. In the appendix Figure 13 Each block represents a step.

[0677] In Embodiment 14, the delay measurement method can be executed at the base station 200. The base station 200 can be Figure 1 the network device of the terminal 100 shown, providing services for the terminal 100 and being the serving base station of the terminal 100.

[0678] In Embodiment 14, at step S1301, the base station 200 receives a first measurement report, which includes a first measurement result. The first measurement result is generated by the terminal measuring data packets in a data radio bearer. The data packets include first-type data packets and second-type data packets, and the generation of the second-type data packets depends on the first-type data packets.

[0679] Among them, the first measurement result at least includes the delay of the first-type data packets; the delay includes any one or more of the following: average delay, minimum delay, maximum delay, excess packet delay.

[0680] In one embodiment, the first measurement result includes the delay of the second type of data packet.

[0681] In one embodiment, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0682] In one embodiment, the first type of data packet is a PDCP source packet, and the base station 200 may further execute step S1300 and step S1302. Among them, step S1300 occurs before receiving the first measurement report, that is, sending the first measurement configuration, which includes the first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet. The first measurement report at least includes the delay of the PDCP source packet.

[0683] In one embodiment, the first type of data packet is a PDCP source packet, and the base station 200 may further execute step S1302, that is, receiving the second measurement report, which is generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than that of the first measurement report. Step S1302 is optional. Generally, step S1302 and step S1301 will not be executed simultaneously.

[0684] Specifically, the second measurement report in step S1302 depends on the first measurement configuration. When the first measurement configuration indicates that the measurement result is still reported when the first type of data packet is discarded, the second measurement report performs measurement and reporting based on the first measurement configuration.

[0685] In one embodiment, the delay is the excess packet delay, and the excess packet delay includes the first excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the first total number of data packets received by the terminal; where the first total number of data packets received by the terminal includes the number of the second type of data packets.

[0686] In one embodiment, the delay is the excess packet delay, and the excess packet delay includes the second excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement period to the second total number of data packets received by the terminal; where the second total number of data packets received by the terminal excludes the number of the second type of data packets.

[0687] In one embodiment, the first measurement report is part of the minimized drive test (MDT) report of the terminal.

[0688] In one embodiment, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0689] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet;

[0690] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0691] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0692] Regarding each term and concept in this embodiment, reference may be made to the descriptions in Embodiments 1 to 13.

[0693] Those skilled in the art understand that the steps in this embodiment can be regarded as execution steps corresponding to the relevant steps in the above Figure 1 、 Figures 5 to 8 shown embodiments. The two are complementary in specific implementation principles and logic. Therefore, for the communication method on the base station side, reference may be made to Figure 1 、 Figures 5 to 8 and the relevant descriptions of the embodiments shown in other drawings, which will not be elaborated here.

[0694] Example 15

[0695] Embodiment 15 exemplifies a structural block diagram of a processing device in a terminal according to an embodiment of the present application; as shown in the appendix Figure 14 shown. In the appendix Figure 14 shown, the processing device 1400 of the terminal includes a processor 1401, a transmitter 1402, and a processor 1403.

[0696] In one embodiment, the processor 1401 measures data packets in a data radio bearer to generate a first measurement result. The data packets include a first type of data packet and a second type of data packet, and the generation of the second type of data packet depends on the first type of data packet; the first measurement result at least includes the delay of the first type of data packet; wherein, the delay includes any one or more of the following: average delay, minimum delay, maximum delay, excessive packet delay.

[0697] In one embodiment, the first measurement result includes the delay of the second type of data packet.

[0698] In one embodiment, the transmitter 1402 transmits a first measurement report, and the first measurement report includes the first measurement result.

[0699] In one embodiment, the generation of the second type of data packet depends on the first type of data packet, which means that the second type of data packet used to repair the first type of data packet is generated based on the first type of data packet.

[0700] In one embodiment, the processor 1401 includes a processing sub-module (not shown in the figure), which measures the first type of data packet in the data radio bearer and measures the second type of data packet; alternatively, the processing sub-module measures the first type of data packet in the data radio bearer and ignores the second type of data packet.

[0701] In one embodiment, the first type of data packet is a PDCP source packet. Before measuring the data packets in a data radio bearer (DRB), the receiver 1403 receives a first measurement configuration, which includes a first uplink delay configuration for configuring the delay measurement of the uplink PDCP source packet. After measuring the data packets in a data radio bearer, the transmitter 1402 transmits a first measurement report, and the first measurement report at least includes the delay of the PDCP source packet.

[0702] In one embodiment, the transmitter 1402 transmits a second measurement report, which is generated when the first type of data packet is discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0703] In one embodiment, the delay is an excess packet delay, and the excess packet delay includes a first excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement to the first total number of data packets received by the terminal. Among them, the first total number of data packets received by the terminal includes the number of the second type of data packets.

[0704] In one embodiment, the delay is an excess packet delay, and the excess packet delay includes a second excess packet delay, which is the ratio of the number of the first type of data packets exceeding the configured delay threshold during the measurement to the second total number of data packets received by the terminal. Among them, the second total number of data packets received by the terminal excludes the number of the second type of data packets.

[0705] In one embodiment, the first measurement report is part of the minimized drive test (MDT) report of the terminal.

[0706] In one embodiment, the first type of data packet and the second type of data packet respectively belong to any one of the following groups:

[0707] The first type of data packet is a UL PDCP source packet, and the second type of data packet is a repair packet of the source UL PDCP packet;

[0708] The first type of data packet is a UL RLC source packet, and the second type of data packet is a repair packet of the UL RLC source packet;

[0709] The first type of data packet is a UL MAC source packet, and the second type of data packet is a repair packet of the source UL MAC packet.

[0710] As one embodiment, the terminal is a user equipment (UE).

[0711] As one embodiment, the terminal is a terminal supporting large delay differences.

[0712] As one embodiment, the terminal is a terminal supporting NTN.

[0713] As one embodiment, the terminal is an aircraft or a ship.

[0714] As one embodiment, the terminal is a mobile phone or a vehicle-mounted terminal.

[0715] As one embodiment, the terminal is a helmet or glasses.

[0716] As one embodiment, the terminal is an Internet of Things terminal or an industrial Internet of Things terminal.

[0717] As one embodiment, the terminal is a device supporting low-latency and high-reliability transmission.

[0718] As one embodiment, the receiver 1403 includes at least one of the antenna 452, receiver 454, receiving processor 456, multi-antenna receiving processor 458, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0719] As one embodiment, the transmitter 1402 includes at least one of the antenna 452, transmitter 454, transmitting processor 468, multi-antenna transmitting processor 457, controller / processor 459, memory 460, or data source 467 in Embodiment 4.

[0720] For more content about the working principle and working mode of the processing device 1400, reference can be made to the above Figures 1 to 12Descriptions of related technical solutions and embodiments are shown above and will not be elaborated here.

[0721] Example 16

[0722] Embodiment 16 exemplifies a structural block diagram of a processing device in a base station according to an embodiment of the present application; as shown in the appendix Figure 15 shown. In the appendix Figure 15 In it, the processing device 1500 in the base station includes a receiver 1501 and a transmitter 1502.

[0723] In a specific implementation, the receiver 1501 receives a first measurement report, the first measurement report includes a first measurement result, the first measurement result is generated by a terminal measuring data packets in a data radio bearer, the data packets include first-class data packets and second-class data packets, and the generation of the second-class data packets depends on the first-class data packets; wherein, the first measurement result at least includes the delay of the first-class data packets; the delay includes any one or more of the following: average delay, minimum delay, maximum delay, excess packet delay.

[0724] As an embodiment, the first measurement result includes the delay of the second-class data packets.

[0725] As an embodiment, the fact that the generation of the second-class data packets depends on the first-class data packets means that the second-class data packets used to repair the first-class data packets are generated based on the first-class data packets.

[0726] As an embodiment, the first-class data packets are PDCP source packets, and before receiving the first measurement report, the transmitter 1502 sends a first measurement configuration, the first measurement configuration includes a first uplink delay configuration, and the first uplink delay configuration is used to configure the delay measurement of uplink PDCP source packets; wherein, the first measurement report at least includes the delay of the PDCP source packets.

[0727] As an embodiment, the receiver 1501 receives a second measurement report, the second measurement report is generated when the first-class data packets are discarded, and the number of bits of the second measurement report is less than the number of bits of the first measurement report.

[0728] As an embodiment, the delay is an excess packet delay, the excess packet delay includes a first excess packet delay, and the first excess packet delay is the ratio of the number of first-class data packets exceeding a configured delay threshold during the measurement period to the total number of first data packets received by the terminal; wherein, the total number of first data packets received by the terminal includes the number of the second-class data packets.

[0729] As an embodiment, the time delay is an excessive packet time delay, and the excessive packet time delay includes a second excessive packet time delay, where the second excessive packet time delay is the ratio of the number of the first type of data packets exceeding a configured time delay threshold during a measurement period to the second total number of data packets received by the terminal; where the second total number of data packets received by the terminal excludes the number of the second type of data packets.

[0730] As an embodiment, the first measurement report is a part of the minimized drive test (MDT) report of the terminal.

[0731] As an embodiment, the first type of data packets and the second type of data packets respectively belong to any one of the following groups:

[0732] The first type of data packets are UL PDCP source packets, and the second type of data packets are repair packets of the source UL PDCP packets;

[0733] The first type of data packets are UL RLC source packets, and the second type of data packets are repair packets of the UL RLC source packets;

[0734] The first type of data packets are UL MAC source packets, and the second type of data packets are repair packets of the source UL MAC packets. As an embodiment, the receiver 1501 includes the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456, the controller / processor 459, the memory 460, and the data source 467 attached in this application. Figure 4 in the present application.

[0735] As an embodiment, the receiver 1501 includes the antenna 452, the receiver 454, the multi-antenna receiving processor 458, and the receiving processor 456 attached in this application. Figure 4 in the present application.

[0736] As an embodiment, the receiver 1501 includes the antenna 452, the receiver 454, and the receiving processor 456 attached in this application. Figure 4 in the present application.

[0737] For more content regarding the working principle and working mode of the processing device 1500, reference may be made to the relevant descriptions of the technical solutions shown in the above Figures 1 to 8 、 Figure 13 and details are not described herein again.

[0738] Those of ordinary skill in the art can understand that all or part of the steps in the above methods can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disc, etc. Optionally, all or part of the steps of the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module unit in the above embodiments can be implemented in a hardware form or in the form of a software function module. This application is not limited to any specific form of the combination of software and hardware. The user equipment, terminal, and UE in this application include, but are not limited to, unmanned aerial vehicles, communication modules on unmanned aerial vehicles, remote control airplanes, aircraft, small airplanes, mobile phones, tablet computers, laptops, vehicle-mounted communication devices, wireless sensors, network cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, network cards, vehicle-mounted communication devices, low-cost mobile phones, low-cost tablet computers, satellite communication devices, vessel communication devices, NTN user equipment and other wireless communication devices. The base station or system equipment in this application includes, but is not limited to, macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point), NTN base stations, satellite equipment, flight platform equipment and other wireless communication devices.

[0739] The present invention may be embodied in other specific forms without departing from its core or essential characteristics. Therefore, the presently disclosed embodiments should in any event be considered as illustrative rather than restrictive. The scope of the invention is determined by the appended claims rather than the foregoing description, and all changes within the meaning and range of equivalents thereof are considered to be included therein.

Claims

1. A method for measuring delay in a terminal, characterized in that: include: Measuring data packets in a data radio bearer to generate a first measurement result, wherein the data packets include first-category data packets and second-category data packets, and generation of the second-category data packets depends on the first-category data packets; The first measurement result at least includes a delay of the first type of data packets; The delay includes any one or more of the following: average delay, minimum delay, maximum delay, and excess packet delay.

2. The delay measurement method according to claim 1, characterized in that: The first measurement result includes a delay of the second type of data packets.

3. The delay measurement method according to claim 1 or 2, characterized in that: include: A first measurement report is sent, where the first measurement report includes the first measurement result.

4. The delay measurement method according to any one of claims 1 to 3, characterized in that: The generation of the second type of data packets depends on the first type of data packets, which means that the second type of data packets used to repair the first type of data packets are generated based on the first type of data packets.

5. The delay measurement method according to claim 1, characterized in that: The measuring of the data packets in a data radio bearer comprises: measuring the first type of data packets in the data radio bearer, and measuring the second type of data packets; or, The first type of data packets in the data radio bearer are measured, and the second type of data packets are ignored.

6. The delay measurement method according to any one of claims 1, 2, 4 or 5, characterized in that: The first type of data packets are PDCP source packets, and the delay measurement method includes: Before measuring the data packets in a data radio bearer, Receiving a first measurement configuration, the first measurement configuration comprising a first uplink delay configuration, the first uplink delay configuration being used to configure a delay measurement of an uplink PDCP source packet; After measuring the data packets in a data radio bearer, a first measurement report is sent, wherein the first measurement report at least includes a delay of the PDCP source packet.

7. The delay measurement method according to claim 6, characterized in that: include: Send a second measurement report, where the second measurement report is generated when the first type of data packets are discarded, and the number of bits in the second measurement report is less than the number of bits in the first measurement report.

8. The delay measurement method according to any one of claims 1 to 7, characterized in that: The delay is an excess packet delay, The excess packet delay comprises a first excess packet delay, where the first excess packet delay is a ratio of the number of the first type of data packets exceeding a configured delay threshold to the first total data packets received by the terminal during a measurement period; The first total data packets received by the terminal include the number of the second type of data packets.

9. The delay measurement method according to any one of claims 1 to 7, characterized in that: The delay is an excess packet delay, The excess packet delay includes a second excess packet delay, where the second excess packet delay is a ratio of the number of the first type of data packets exceeding a configured delay threshold to a second total number of data packets received by the terminal during a measurement period; The second total data packets received by the terminal exclude the number of the second category data packets.

10. The delay measurement method according to claim 3 or 6, characterized in that: The first measurement report is a part of a minimization of drive tests (MDT) report of the terminal.

11. The delay measurement method according to any one of claims 1 to 10, characterized in that: The first type of data group and the second type of data group belong to any of the following groups respectively: The first type of data packets are UL PDCP source packets, and the second type of data packets are repair packets of the UL PDCP source packets; The first type of data packets are UL RLC source packets, and the second type of data packets are repair packets of the UL RLC source packets; The first type of data packets are UL MAC source packets, and the second type of data packets are repair packets of the UL MAC source packets.

12. A terminal, characterized in that: The terminal comprises: one or more processors and memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions. The one or more processors call the computer instructions to enable the terminal to execute the delay measurement method according to any one of claims 1 to 11.

13. A method for receiving a measurement report in a base station, characterized in that: include: receiving a first measurement report, where the first measurement report includes a first measurement result, where the first measurement result is generated by the terminal measuring a data packet in a data radio bearer, where the data packet includes a first category of data packets and a second category of data packets, where generation of the second category of data packets depends on generation of the first category of data packets; The first measurement result at least includes the delay of the first type of data packets; The delay includes any one or more of the following: average delay, minimum delay, maximum delay, excess packet delay.

14. The measurement report receiving method according to claim 13, characterized in that: The first measurement result includes a delay of the second type of data packets.

15. The measurement report receiving method according to claim 13 or 14, characterized in that: The generation of the second type of data packets depends on the first type of data packets, which means that the second type of data packets used to repair the first type of data packets are generated based on the first type of data packets.

16. The method for receiving a measurement report according to any one of claims 13 to 15, characterized in that: The first type of data packets are PDCP source packets, and the measurement report receiving method includes: Before receiving the first measurement report, Sending a first measurement configuration, where the first measurement configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure a delay measurement of an uplink PDCP source packet; The first measurement report at least includes the delay of the PDCP source packet.

17. The method for receiving a measurement report according to any one of claims 13 to 16, characterized in that: include: A second measurement report is received, where the second measurement report is generated when the first type of data packets are discarded, and the number of bits in the second measurement report is less than the number of bits in the first measurement report.

18. The method for receiving a measurement report according to any one of claims 13 to 17, characterized in that: The delay is an excess packet delay, The excess packet delay comprises a first excess packet delay, where the first excess packet delay is a ratio of the number of the first type of data packets exceeding a configured delay threshold to the first total data packets received by the terminal during a measurement period; The first total data packets received by the terminal include the number of the second type of data packets.

19. The method for receiving a measurement report according to any one of claims 13 to 17, characterized in that: The delay is an excess packet delay, The excess packet delay includes a second excess packet delay, where the second excess packet delay is a ratio of the number of the first type of data packets exceeding a configured delay threshold to a second total number of data packets received by the terminal during a measurement period; The second total data packets received by the terminal exclude the number of the second category data packets.

20. The method for receiving a measurement report according to any one of claims 13 to 19, characterized in that: The first measurement report is a part of a minimization of drive tests (MDT) report of the terminal.

21. The method for receiving a measurement report according to any one of claims 13 to 20, characterized in that: The first type of data group and the second type of data group belong to any of the following groups respectively: The first type of data packets are UL PDCP source packets, and the second type of data packets are repair packets of the UL PDCP source packets; The first type of data packets are UL RLC source packets, and the second type of data packets are repair packets of the UL RLC source packets; The first type of data packets are UL MAC source packets, and the second type of data packets are repair packets of the UL MAC source packets.

22. A base station, characterized in that: The base station comprises: one or more processors and memory; The memory is coupled to the one or more processors, and the memory is used to store computer program codes, where the computer program codes include computer instructions, and the one or more processors call the computer instructions to enable the base station to execute the measurement report receiving method according to any one of claims 13 to 21.

Images