WO2024245260A1 - Method and device used in wireless communication - Google Patents

Abstract

The present application discloses a method and device used in wireless communication. The method comprises: receiving a first measurement configuration, the first measurement configuration comprising a first report configuration, the first report configuration comprising a first uplink latency configuration, and the first uplink latency configuration being used for configuring an uplink PDCP packet group latency measurement; performing the uplink PDCP packet group latency measurement according to the first uplink latency configuration; processing N PDCP packet groups; and sending a first report, the first report comprising a first latency, and the ratio of the sum of the first latency and the latency of each of the N PDCP packet groups to the N being equal. According to the method provided by the present application, a more accurate measurement result can be obtained.

Description

A method and device for wireless communication Technical Field

The present application relates to a transmission method and device in a wireless communication system, and to monitoring of service quality to better support interactive service transmission.

Background Art

The application scenarios of wireless communication systems in the future will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #72 plenary meeting decided to study the new air interface technology (NR, New Radio) (or Fifth Generation, 5G), and the NR WI (Work Item) was passed at the 3GPP RAN #75 plenary meeting, starting the standardization work on NR.

In communication, both LTE (Long Term Evolution) and 5G NR involve accurate reception of reliable information, optimized energy efficiency, determination of information validity, flexible resource allocation, scalable system structure, efficient non-access layer information processing, low service interruption and drop rate, and support for low power consumption. This is of great significance to the normal communication between base stations and user equipment, the reasonable scheduling of resources, and the balancing of system load. 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 (ehanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication) and eMTC (enhanced Machine Type Communication). At the same time, in IIoT (Industrial Internet of Things), V2X (Vehicular to X), device to device, unlicensed spectrum communication, user communication quality monitoring, network planning optimization, NTN (Non Territerial Network), TN (Territial Network), dual connectivity system, wireless resource management and multi-antenna codebook selection, signaling design, neighbor management, business management, beamforming, there are extensive demands. Information transmission methods are divided into broadcast and unicast. Both transmission methods are essential for 5G systems because they are very helpful in meeting the above requirements. The UE can be connected to the network directly or through a relay.

As the scenarios and complexity of the system continue to increase, higher requirements are put forward for reducing the interruption rate, reducing latency, enhancing reliability, enhancing system stability, business flexibility, and power saving. At the same time, the compatibility between different versions of different systems needs to be considered during system design. At the same time, the types of services supported by 5G systems are becoming more and more abundant, and these new services have also brought corresponding challenges to the system.

The 3GPP standardization organization has done relevant standardization work for 5G and formed a series of standards. The standard contents can be referenced:

https://www.3gpp.org/ftp/Specs/archive/38_series/38.331/38331-h10.zip

https://www.3gpp.org/ftp/Specs/archive/38_series/38.323/38323-h10.zip

https://www.3gpp.org/ftp/Specs/archive/38_series/38.321/38321-h10.zip

Summary of the invention

In wireless communication systems, QoS (Quality of Service) monitoring is an important issue, because for communication networks, it is necessary to ensure the required QoS, so QoS needs to be monitored during the communication process. A very important aspect of QoS monitoring is monitoring latency. In scenarios where latency needs to be measured and reported, how to measure and report the latency of PDCP packet groups is a problem that needs to be solved. Researchers have found that both uplink and downlink transmissions need to meet QoS requirements, including latency requirements, and important components of latency include PDCP packet latency and PDCP packet group latency. For downlink, the network can generally measure it by itself, and for uplink, the UE needs to measure and report the uplink PDCP packet latency and PDCP packet group latency. The researchers also found that in different scenarios, even if the PDCP packet delay can meet the requirements, the PDCP packet group may still not meet the PDCP packet group delay requirements. Similarly, in different scenarios, even if the PDCP packet delay fails to meet the requirements, the PDCP packet group may still meet the PDCP packet group delay requirements. Therefore, for communications involving PDCP packet groups, determining and monitoring the PDCP packet group delay is of special significance, which can more truly and accurately reflect the QoS status during the communication process.

In view of the above-mentioned problems, this application provides a solution.

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

The present application discloses a method in a first node used for wireless communication, comprising:

Receiving a first measurement configuration, where the first measurement configuration includes a first report configuration, where the first report configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement;

Perform uplink PDCP packet group delay measurement according to the first uplink delay configuration; process N PDCP packet groups;

Sending a first report, the first report comprising a first delay, the first delay being equal to a ratio of a sum of a delay of each of the N PDCP packet groups and N, where N is a positive integer;

Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, the problems to be solved by the present application include: how to measure and determine the PDCP packet group delay; how to monitor QoS; and how to better support low-latency interactive services.

As an embodiment, the benefits of the above method include: it can more accurately reflect the delay status, can more accurately reflect the delay of the PDCP packet group, can better support transmission based on the PDCP packet group, can more accurately monitor QoS, can better support interactive services, and can better support XR services.

Specifically, according to one aspect of the present application, any one of the N PDCP packet groups is composed of one or more PDUs carrying a load of a unit of information generated by the application layer.

Specifically, according to one aspect of the present application, the first report configuration includes a second uplink delay configuration, and the second uplink delay configuration is used to configure the uplink PDCP packet delay measurement; the result of the uplink PDCP packet delay measurement includes a second delay, and the second delay is equal to the ratio of the sum of the delays of each PDCP packet in the M PDCP packets arriving within the first time length to the M; the M is a positive integer; the delay of any PDCP packet in the M PDCP packets is equal to the time interval between the arrival time of any PDCP packet in the M PDCP packets and the time when the uplink MAC PDU carrying at least the first part of the any PDCP packet in the M PDCP packets is scheduled to be sent.

Specifically, according to one aspect of the present application, the sentence that the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups includes: the delay of any of the N PDCP packet groups is equal to the time interval between the arrival of the first PDCP packet in any of the N PDCP packet groups and the processing of the last PDCP packet; the phrase the last PDCP packet is processed means that the last PDCP packet is sent or at least the first part of the last PDCP packet is scheduled to be sent.

Specifically, according to one aspect of the present application, the sentence that the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups includes: the delay of any of the N PDCP packet groups is equal to the average value of the delay of each PDCP packet group in the N PDCP packet groups.

Specifically, according to one aspect of the present application, an uplink PDCP delay measurement exceeding a packet group is performed; wherein, the first report configuration includes a third uplink delay configuration; the third uplink delay configuration includes a first threshold; the third uplink delay configuration is used to configure the uplink PDCP delay measurement exceeding the packet group; the measurement result of the uplink PDCP delay exceeding the packet group includes the ratio between the number of PDCP packet groups in which the delay exceeds the first threshold in the PDCP packet groups measured within a first time length and the total number of PDCP packet groups measured within the first time length.

Specifically, according to one aspect of the present application, the first report configuration includes a fourth uplink delay configuration; the fourth uplink delay configuration includes a second threshold; the fourth uplink delay configuration is used to configure the uplink PDCP exceeding packet delay measurement; the measurement result of the uplink PDCP exceeding packet delay includes the ratio between the number of PDCP packets in which the delay exceeds the second threshold in the PDCP packets measured within the first time length and the total number of PDCP packets measured within the first time length.

Specifically, according to one aspect of the present application, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating multiple DRBs, and the N PDCP packet groups occupy the multiple DRBs.

Specifically, according to one aspect of the present application, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating the identity of the first DRB and the first PDCP packet group type, the N PDCP packet groups occupy the first DRB and belong to the first PDCP packet group type; the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type; the uplink PDCP packet group delay measurement is only for the PDCP packet group of the first PDCP packet group type.

Specifically, according to one aspect of the present application, the first delay is determined only by the delay of the PDCP packet group that is not discarded; the delay of the PDCP packets whose MAC PDUs occupied by at least a part of the M PDCP packets are scheduled and then discarded is still included in the second delay.

Specifically, according to one aspect of the present application, the first node is an Internet of Things terminal.

Specifically, according to one aspect of the present application, the first node is a user equipment.

Specifically, according to one aspect of the present application, the first node is a relay.

Specifically, according to one aspect of the present application, the first node is an access network device.

Specifically, according to one aspect of the present application, the first node is a vehicle-mounted terminal.

Specifically, according to one aspect of the present application, the first node is an aircraft.

Specifically, according to one aspect of the present application, the first node is a mobile phone.

The present application discloses a first node used for wireless communication, comprising:

A first receiver receives a first measurement configuration, where the first measurement configuration includes a first report configuration, where the first report configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement;

A first processor performs uplink PDCP packet group delay measurement according to the first uplink delay configuration; and processes N PDCP packet groups;

A first transmitter sends a first report, wherein the first report includes a first delay, wherein the first delay is equal to a ratio of a sum of a delay of each PDCP packet group in the N PDCP packet groups to N, where N is a positive integer;

Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, compared with the traditional solution, this application has the following advantages:

More accurately understand the latency of monitoring services and verify whether QoS requirements are met.

The delay measurement of the PDCP packet group can be controlled more accurately.

Better support for the transmission of services based on PDCP packet groups.

The QoS status of XR services can be accurately monitored.

It can support richer business types, such as XR business.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

FIG1 shows a flowchart of receiving a first measurement configuration, performing uplink PDCP packet group delay measurement according to the first uplink delay configuration, processing N PDCP packet groups, and sending a first report according to an embodiment of the present application;

FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

FIG3 is a schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

FIG5 shows a flow chart of wireless signal transmission according to an embodiment of the present application;

FIG6 is a schematic diagram showing that the arrival time of at least the first PDCP packet in any PDCP packet group among N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any PDCP packet group among the N PDCP packet groups is processed are used to determine the delay of any PDCP packet group among the N PDCP packet groups according to an embodiment of the present application;

FIG7 shows a schematic diagram of a first time delay according to an embodiment of the present application;

FIG8 shows a schematic diagram of a first time delay according to an embodiment of the present application;

FIG9 shows a schematic diagram of uplink PDCP exceeding packet group delay measurement according to an embodiment of the present application;

FIG10 is a schematic diagram showing uplink PDCP exceeding packet group delay measurement according to an embodiment of the present application;

FIG11 illustrates a schematic diagram of a processing device used in a first node according to an embodiment of the present application.

Implementation

The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

Example 1

Embodiment 1 illustrates a flowchart of receiving a first measurement configuration according to an embodiment of the present application, performing uplink PDCP packet group delay measurement according to the first uplink delay configuration, and processing N PDCP packet groups; and sending a first report, as shown in FIG1. In FIG1, each box represents a step, and it is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence of the steps represented.

In Embodiment 1, the first node in the present application receives a first measurement configuration in step 101; performs uplink PDCP packet group delay measurement according to the first uplink delay configuration in step 102; processes N PDCP packet groups in step 103; and sends a first report in step 104;

Among them, the first measurement configuration includes a first report configuration, the first report configuration includes a first uplink delay configuration, and the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement; the first report includes a first delay, and the first delay is equal to the ratio of the sum of the delay of each PDCP packet group in the N PDCP packet groups and the N; the N is a positive integer; the arrival time of at least the first PDCP packet in any PDCP packet group in the N PDCP packet groups and the time when the default PDCP packet in any PDCP packet group in the N PDCP packet groups is processed are used to determine the delay of any PDCP packet group in the N PDCP packet groups; each PDCP packet group in the N PDCP packet groups is an uplink PDCP packet group; the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, the first node is UE (User Equipment).

As an embodiment, the first node is in an RRC connected state.

As an example, the interpretation of the terms in the present application refers to the definitions of the TS38 series of specification protocols of 3GPP.

As an embodiment, any parameter not explicitly described in the present application may be indicated by the network or configured by the network or pre-configured.

As an embodiment, any parameter not explicitly described in the present application can be determined by the first node according to its internal algorithm when not indicated by the network.

As an embodiment, any parameter in the present application may be initialized to 0 when not indicated by the network.

As an embodiment, any parameter in the present application may be set to a random number when not indicated by the network.

As an embodiment, any parameter in the present application can be selected based on simulation results when not indicated by the network.

As an embodiment, the serving cell refers to the cell where the UE resides. Performing a 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 residing on a cell; that is, a cell that is resided on is the serving cell of the UE relative to the UE. Staying in a cell in RRC idle or RRC inactive state has the following benefits: it allows the UE to receive system information from the PLMN or SNPN; after registration, if the UE wishes to establish an RRC connection or continue a suspended RRC connection, the UE can do so by performing initial access on the control channel of the cell where it is staying; the network can page the UE; and it allows the UE to receive ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) notifications.

As an embodiment, for a UE in an RRC connected state without configuring CA/DC (carrier aggregation/dual connectivity), there is only one serving cell including a primary cell. For a UE in an RRC connected state with configured CA/DC (carrier aggregation/dual connectivity), the serving cell is used to indicate a collection of cells including a special cell (SpCell) and all cells from the cells. The primary cell (Primary Cell) is a MCG (Master Cell Group) cell, which operates on the primary frequency. The UE performs an initial connection establishment process or initiates connection reconstruction on the primary cell. For dual connection operation, the special cell refers to the PCell (Primary Cell) of the MCG or the PSCell (Primary SCG Cell) of the SCG (Secondary Cell Group); if it is not a dual connection operation, the special cell refers to the PCell.

As an embodiment, the operating frequency of the SCell (Secondary Cell) is a secondary frequency.

As an example, individual contents of an information element are referred to as fields.

As an embodiment, MR-DC (Multi-Radio Dual Connectivity) refers to the dual connection of E-UTRA and NR nodes, or the dual connection between two NR nodes.

As an embodiment, in MR-DC, the wireless access node that provides the control plane connection to the core network is the master node, which may be a master eNB, a master ng-eNB, or a master gNB.

As an embodiment, MCG refers to a group of service cells associated with a master node in MR-DC, including SpCells, and may also, optionally, include one or more SCells.

As an embodiment, PCell is the SpCell of MCG.

As an embodiment, the PSCell is the SpCell of the SCG.

As an embodiment, in MR-DC, the control plane connection to the core network is not provided, and the radio access node that provides additional resources to the UE is a slave node. The slave node can be an en-gNB, a slave ng-eNB or a slave gNB.

As an embodiment, in MR-DC, a group of service cells associated with a slave node is a SCG (secondary cell group), including a SpCell and, optionally, one or more SCells.

As an embodiment, the first node is configured with at least an MCG, and the MCG configured with the first node includes at least one SCell.

As an embodiment, the first node is configured with MCG and SCG.

As a sub-embodiment of this embodiment, the MCG configured by the first node includes at least one SCell.

As a sub-embodiment of this embodiment, the SCG configured by the first node includes at least one SCell.

As an embodiment, the first measurement configuration includes RRC signaling.

As an embodiment, the first measurement configuration is or includes at least one information element in an RRCReconfiguration message.

As an embodiment, the first measurement configuration only includes a field whose name includes Meas or an information element whose name includes Meas in the RRCReconfiguration message.

As an embodiment, the first measurement configuration includes at least one information element in RRCConnectionReconfiguration.

As an embodiment, the first measurement configuration is or includes MeasConfig.

As an embodiment, the first measurement configuration is or includes L2-MeasConfig.

As an embodiment, the first measurement configuration is or includes appLayerMeasConfig.

As an embodiment, the first measurement configuration is used to configure a cell group.

As an embodiment, the first measurement configuration is unicast.

As an embodiment, the first measurement configuration is sent to the first node via a dedicated control channel.

As an embodiment, the first measurement configuration is sent to the first node using a dedicated channel.

As an embodiment, the phrase “the first measurement configuration includes a first reporting configuration” means that: the first measurement configuration includes a reporting configuration list, and the reporting configuration list includes the first reporting configuration.

As a sub-embodiment of this embodiment, the report configuration list is ReportConfigToAddModList.

As a sub-embodiment of this embodiment, the first report configuration is an item in the report configuration list.

As an embodiment, the first reporting configuration includes a first reporting configuration identity, and the first reporting configuration identity is the identity of the first reporting configuration.

As an embodiment, the first report configuration includes a report configuration.

As an embodiment, the first report configuration includes a report configuration.

As an embodiment, the first reporting configuration includes a reporting configuration for NR.

As an embodiment, the first reporting configuration includes a reporting configuration for NR, or one of the reporting configurations for other access technologies.

As an embodiment, the first report configuration includes ReportConfigNR.

As an embodiment, the first report configuration consists of the first report configuration identity and ReportConfigNR.

As an embodiment, the first report configuration includes a report type.

As an embodiment, the ReportConfigNR included in the first report configuration includes a report type.

As an embodiment, the reporting type is periodic.

As an embodiment, the report type is time triggered.

As an embodiment, the report type is conditionally triggered.

As an embodiment, the report type is periodic, and the first report configuration includes a reporting time interval (reportInterval).

As an embodiment, the report type is periodic, and the first report configuration includes the number of reports.

As an embodiment, the report type is periodic, and the reporting time interval included in the first report configuration is a first time length.

As an embodiment, the first uplink delay configuration is used to configure uplink delay measurement.

As an embodiment, the first uplink delay configuration is a configuration other than ul-DelayValueConfig.

As an embodiment, the first uplink delay configuration is ul-DelayPDUSetValueConfig.

As an embodiment, the first uplink delay configuration is ul-DelayValueConfigPDUSet.

As an embodiment, the first uplink delay configuration includes a domain indication whose name in the first reporting configuration includes PDUSet.

As an embodiment, the behavior of processing N PDCP packet groups includes: the N PDCP packet groups arrive at the PDCP entity.

As an embodiment, the behavior of processing N PDCP packet groups includes: the N PDCP packet groups are cached by the PDCP entity.

As an embodiment, the behavior of processing N PDCP packet groups includes: the N PDCP packet groups are submitted to a lower protocol layer.

As a sub-embodiment of this embodiment, the lower protocol layer includes an RLC layer.

As a sub-embodiment of this embodiment, the lower protocol layer includes the layer where the main RLC entity is located.

As a sub-embodiment of this embodiment, the lower protocol layer includes the layer where the RLC entity is located.

As a sub-embodiment of this embodiment, the lower protocol layer includes the layer where the AM RLC entity is located.

As a sub-embodiment of this embodiment, the lower protocol layer includes the layer where the UM RLC entity is located.

As a sub-embodiment of this embodiment, the lower protocol layer includes a MAC layer.

As an embodiment, the behavior of processing N PDCP packet groups includes: the first PDCP packet in any PDCP packet group among the N PDCP packet groups arrives.

As an embodiment, the behavior of processing N PDCP packet groups includes: the first PDCP packet in any PDCP packet group among the N PDCP packet groups arrives.

As an embodiment, the behavior of processing N PDCP packet groups includes: the last PDCP packet in any PDCP packet group among the N PDCP packet groups is submitted to a lower layer.

As an embodiment, the behavior of processing N PDCP packet groups includes: the MAC PDU carrying the last PDCP packet of any PDCP packet group among the N PDCP packet groups is scheduled to be sent.

As an embodiment, the behavior of processing N PDCP packet groups includes: a MAC PDU carrying at least the first part of the last PDCP packet of any PDCP packet group among the N PDCP packet groups is scheduled to be sent.

As an embodiment, the behavior of processing N PDCP packet groups does not include: discarding any PDCP packet group among the N PDCP packet groups.

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that the delay measurement is for the uplink PDCP packet group.

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP packet group delay measurement is for an uplink PDCP packet group of the first PDCP packet group type.

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP packet group delay measurement is for PDCP packet groups on multiple DRBs (data radio bearers).

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP packet group delay measurement is based on the maximum delay of the uplink PDCP packet group.

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that delay measurement is performed according to the importance of the PDCP packet group.

As an embodiment, the sentence that the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes: the first uplink delay configuration indicates that the uplink PDCP packet group delay measurement is based on the average delay of the uplink PDCP packet group.

As an embodiment, the behavior of performing uplink PDCP packet group delay measurement according to the first uplink delay configuration includes counting the delay of the uplink PDCP packet group.

As an embodiment, the behavior of performing uplink PDCP packet group delay measurement according to the first uplink delay configuration includes generating a first delay.

As an embodiment, the behavior of performing uplink PDCP packet group delay measurement according to the first uplink delay configuration includes counting the delay of the PDCP packet group measured within a first time length.

As an embodiment, the first report includes a MeasurementReport message.

As an embodiment, the first report includes measurement results.

As an embodiment, the first report includes at least one field in a MeasurementReport message.

As an embodiment, the first report includes at least one field in a UEAssistanceInformation message.

As an embodiment, the first report is transmitted in a dedicated manner.

As an embodiment, the logical channel used for the first report is DCCH (dedicated Control channel).

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

As an embodiment, the first report is transmitted using SRB4, SRB5 or SRB6.

As an embodiment, the first report is unicast.

As an embodiment, the first report is uplink.

As an embodiment, N is equal to the number of PDCP packet groups sent.

As an embodiment, N is equal to the number of PDCP packet groups sent within the measurement time.

As an embodiment, N is equal to the number of PDCP packet groups sent within the first time length.

As an embodiment, the time period for performing the measurement is a first time length.

As an embodiment, the behavior of performing uplink PDCP packet group delay measurement is a measurement performed within the first time length.

As an embodiment, the N PDCP packet groups sent are N uplink PDCP packet groups sent by the first node.

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

As an embodiment, the sentence "the first delay is equal to the ratio of the sum of the delays of each PDCP packet group in the N PDCP packet groups sent to N" means that the first delay is equal to the ratio of the sum of the delays of each PDCP packet group in the N PDCP packet groups sent to N.

As an embodiment, the sentence "the first delay is equal to the ratio of the sum of the delays of each of the N PDCP packet groups sent and N" means that each of the N PDCP packet groups has its own delay, and the N PDCP packet groups have a total of N delays, and the first delay is equal to the sum of the N delays divided by N.

As an embodiment, the number of PDCP packet groups counted in the uplink PDCP packet group delay measurement performed in different time periods may be different.

As an embodiment, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups means or includes: the delay of any one of the N PDCP packet groups depends on the arrival time of the first PDCP packet in any one of the N PDCP packet groups, and at the same time, the delay of any one of the N PDCP packet groups depends on the time when the default PDCP packet in any one of the N PDCP packet groups is processed.

As an embodiment, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups means or includes: at least two PDCP packets in any one of the N PDCP packet groups are used to determine the delay of any one of the N PDCP packet groups, and the at least two PDCP packets include the first PDCP packet in any one of the N PDCP packet groups and the default PDCP packet in any one of the N PDCP packet groups.

As an embodiment, the first PDCP packet in any one of the PDCP packet groups is the earliest PDCP packet to arrive in any one of the PDCP packet groups.

As an embodiment, the first PDCP packet in any one of the PDCP packet groups is the PDCP packet with the earliest sequence number in any one of the PDCP packet groups.

As an embodiment, the first uplink delay configuration indicates which PDCP packet in the PDCP packet group is a default PDCP packet.

As an embodiment, the default PDCP packet is an intermediate PDCP packet.

As an embodiment, the default PDCP packet is the last PDCP packet.

As an embodiment, the default PDCP packet is the PDCP packet with the latest sequence number.

As an embodiment, the last PDCP packet is the last data packet transmitted in a PDCP packet group.

As an embodiment, the last PDCP packet is the last data packet that is transmitted in a PDCP packet group.

As an embodiment, the last PDCP packet is the latest scheduled PDCP packet in a PDCP packet group.

As a sub-embodiment of this embodiment, the latest scheduling is scheduled for transmission (scheduled for transmission).

As a sub-embodiment of this embodiment, the latest scheduled PDCP packet is the PDCP packet carried by the latest scheduled MAC PDU among the MAC PDUs that carry at least the first part of the PDCP packets in any PDCP packet group.

As a sub-embodiment of this embodiment, the latest scheduled PDCP packet is the PDCP packet carried by the latest scheduled MAC PDU among the MAC PDUs that carry the first part of each PDCP packet in any PDCP packet group.

As a sub-embodiment of this embodiment, the latest scheduled PDCP packet is the PDCP packet carried by the latest scheduled MAC PDU among the MAC PDUs carrying the PDCP packets in any of the PDCP packet groups.

As a sub-embodiment of this embodiment, any one of the PDCP packet groups includes K PDCP packets, where K is a positive integer, and the earliest scheduled MAC PDU among the MAC PDUs carrying at least a part of the i-th PDCP packet among the K PDCP packets is MAC PDU i; wherein i is any integer between 1 and K (including 1 and K), then the latest scheduled MAC PDU among MAC PDU 1, MAC PDU 2,…, MAC PDU K is MAC PDU j, and the latest scheduled PDCP packet in any one of the PDCP packet groups is the j-th PDCP packet.

As an embodiment, the PDCP packet included in any PDCP packet group among the N PDCP packet groups is a PDCP PDU (protocol data unit).

As an embodiment, the PDCP packet included in any PDCP packet group among the N PDCP packet groups is a PDCP SDU (service data unit).

As an embodiment, the PDCP packets included in any one of the N PDCP packet groups are PDCP SDUs assigned with COUNT values.

As an embodiment, the uplink PDCP packet group is a PDCP packet group generated by an uplink PDCP entity.

As an embodiment, the uplink PDCP packet group is a PDCP packet group processed by an uplink PDCP entity.

As an embodiment, the uplink PDCP packet group is a PDCP packet group received by the uplink PDCP entity from a higher layer.

As an embodiment, the uplink PDCP packet group includes at least one PDCP packet generated by an uplink PDCP entity.

As an embodiment, the uplink PDCP packet group includes at least one PDCP packet processed by the uplink PDCP entity.

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

As an embodiment, the arrival time of the first PDCP packet is the time when the first PDCP packet arrives at the PDCP layer from a protocol layer above PDCP.

As an embodiment, the protocol layer above the PDCP is the SDAP layer.

As an embodiment, the arrival time of the first PDCP packet is the time when the first PDCP packet arrives at the PDCP layer from the SDAP layer.

As an embodiment, the arrival time of the first PDCP packet is the time of arrival at the uplink PDCP entity.

As an embodiment, the sentence that the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets means that at least one PDCP packet group among the N PDCP packet groups includes multiple PDCP packets.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when the default PDCP packet in any one of the N PDCP packet groups is scheduled.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when the default PDCP packet in any one of the N PDCP packet groups is transmitted.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when confirmation of the default PDCP packet in any one of the N PDCP packet groups is received from the receiving end.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when the default PDCP packet in any one of the N PDCP packet groups is scheduled.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when at least the first part of the default PDCP packet in any one of the N PDCP packet groups is scheduled.

As an embodiment, the moment when the default PDCP packet in any one of the N PDCP packet groups is processed is the moment when the MAC PDU carrying at least the first part of the default PDCP packet in any one of the N PDCP packet groups is scheduled.

As an embodiment, any one of the N PDCP packet groups is composed of one or more PDUs carrying a payload of a unit of information generated by the application layer.

As a sub-sub-embodiment of this embodiment, any PDCP packet group among the N PDCP packet groups is a PDU set, or carries a PDU set.

As a sub-embodiment of this embodiment, a PDU set includes, for example, a frame of video, a video slice.

As a sub-embodiment of this embodiment, in some applications, the data of a PDU set needs to be decoded together to be meaningful.

As a sub-embodiment of this embodiment, the PDU in a PDU set is a PDU of the application layer or a PDU of other protocol layers that carries application layer information.

As a sub-embodiment of this embodiment, a PDU set consists of one or more PDUs carrying a payload of a unit of information generated by the application layer.

As a sub-embodiment of this embodiment, any PDU in a PDU set includes an identity or index for identifying the PDU set.

As an embodiment, each PDCP packet in any one of the N PDCP packet groups carries an identifier or an identity or an index indicating any one of the N PDCP packet groups.

As an embodiment, the protocol header of each PDCP packet in any one of the N PDCP packet groups carries an identifier or an identity or an index indicating the any one of the N PDCP packet groups.

As an embodiment, the protocol header of the SDAP PDU included in each PDCP packet in any one of the N PDCP packet groups carries an identifier, identity or index indicating any one of the N PDCP packet groups.

As an embodiment, the protocol header of the higher layer PDU included in each PDCP packet in any one of the N PDCP packet groups carries an identifier or identity or index indicating any one of the N PDCP packet groups.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating a plurality of DRBs, and the N PDCP packet groups occupy the plurality of DRBs.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating a DRB, and the N PDCP packet groups occupy the one DRB.

As a sub-embodiment of this embodiment, indicating one DRB can be regarded as a special case of indicating multiple DRBs.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement includes indicating multiple DRBs, and the uplink PDCP packet group delay measurement is to measure the delay of the N PDCP packet groups on the multiple DRBs.

As an embodiment, the benefit of performing uplink PDCP packet group delay measurement on multiple DRBs is that for certain services occupying multiple DRBs, including the N PDCP packet groups occupying multiple DRBs, performing uplink PDCP packet group measurement on multiple DRBs is helpful in understanding the delay of services occupying multiple DRBs, thereby better performing QoS monitoring.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating the identity of the first DRB and the first PDCP packet group type, the N PDCP packet groups occupy the first DRB and belong to the first PDCP packet group type; the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type; the uplink PDCP packet group delay measurement is only for the PDCP packet group of the first PDCP packet group type.

As a sub-embodiment of this embodiment, there are multiple candidate values for the PDCP packet group type.

As a sub-embodiment of this embodiment, the PDCP packet group type depends on the importance of the PDCP packet group.

As a sub-embodiment of this embodiment, the PDCP packet group type refers to the importance of a specific PDCP packet group.

As a sub-embodiment of this embodiment, candidate values of the PDCP packet group type include one of an I frame and a P frame.

As a sub-embodiment of this embodiment, candidate values of the PDCP packet group type include a specific type of video slices.

As a sub-embodiment of this embodiment, the first PDCP packet group type is any one of all PDCP packet group types.

As a sub-embodiment of this embodiment, the first delay only includes the delay of the PDCP packet group belonging to the first PDCP packet group type.

As an embodiment, the sentence "the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type" means or includes: at least one PDCP packet group that does not belong to the first PDCP packet group type uses the first DRB for transmission.

As an embodiment, the sentence "the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type" means or includes: the first DRB is configured to transmit a PDCP packet group of a PDCP packet group type other than the first PDCP packet group type.

As an embodiment, the N PDCP packet groups are all PDCP packet groups of the first PDCP packet group type.

As an embodiment, the benefit of performing uplink PDCP packet group delay measurement for a specific PDCP packet group type, such as the first PDCP packet group type, is that the delay of the PDCP packet group of a certain PDCP packet group type, such as the first PDCP packet group type, can be more accurately grasped, thereby better performing QoS monitoring; especially when the first DRB is used to carry PDCP packet groups of multiple PDCP packet group types, and each PDCP packet group type will be processed differently, it is more meaningful to perform uplink PDCP packet group delay measurement for a specific PDCP packet group type, and the results obtained are more refined and accurate.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to the present application, as shown in FIG2 .

FIG2 illustrates a diagram of a network architecture 200 of a 5G NR, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) system. The 5G NR or LTE network architecture 200 may be referred to as a 5GS (5G System)/EPS (Evolved Packet System) 200 or some other suitable terminology. 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, 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 shown, 5GS/EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting receiving node), or some other suitable term. gNB 203 provides an access point to 5GC/EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, 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 devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a 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 MME (Mobility Management Entity)/AMF (Authentication Management Field)/SMF (Session Management Function) 211, other MME/AMF/SMF 214, S-GW (Service Gateway)/UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway)/UPF 213. The MME/AMF/SMF 211 is a control node that processes signaling between the UE 201 and the 5GC/EPC 210. In general, the MME/AMF/SMF 211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW/UPF212, which is itself connected to P-GW/UPF213. P-GW provides UE IP address allocation and other functions. P-GW/UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

As an embodiment, the first node in the present application is UE201.

As an embodiment, the base station of the second node in the present application is gNB203.

As an embodiment, the wireless link from the UE201 to the NR Node B is an uplink.

As an embodiment, the wireless link from the NR Node B to UE201 is a downlink.

As an embodiment, the UE 201 supports relay transmission.

As an embodiment, the UE 201 includes a mobile phone.

As an embodiment, the UE 201 is a vehicle including a car.

As an embodiment, the gNB203 is a macrocellular base station.

As an embodiment, the gNB203 is a micro cell base station.

As an embodiment, the gNB203 is a picoCell base station.

As an embodiment, the gNB203 is a flying platform device.

As an embodiment, the gNB203 is a satellite device.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3. FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 shows the radio protocol architecture of the control plane 300 for a first node (UE, satellite or aircraft in gNB or NTN) and a second node (satellite or aircraft in gNB, UE or NTN), or between two UEs using 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. The L1 layer will be referred to as PHY301 herein. Layer 2 (L2 layer) 305 is above PHY301 and is responsible for the link between the first node and the second node and the two UEs through PHY301. The L2 layer 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, which 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 support for inter-zone mobility of the first node between the second node. 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 out-of-order 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) in 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 processing 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 substantially 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 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers (DRBs) to support the diversity of services. SRBs can be regarded as services or interfaces provided by the PDCP layer to higher layers, such as the RRC layer. In the NR system, SRBs include SRB1, SRB2, SRB3, and SRB4 when sidelink communication is involved, which are used to transmit different types of control signaling. SRBs are bearers between UE and access network, and are used to transmit control signaling including RRC signaling between UE and access network. SRB1 has special significance for UE. After each UE establishes an RRC connection, there will be SRB1 for transmitting 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. UE may not configure SRB3. Except for emergency services, the UE must establish an RRC connection with the network for 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., remote UE, server, etc.). A protocol sublayer may also be referred to as a protocol layer.

As an embodiment, the wireless protocol architecture in FIG. 3 is applicable to the first node in the present application.

As an embodiment, the wireless protocol architecture in FIG. 3 is applicable to the second node in the present application.

As an embodiment, the first measurement configuration is generated in RRC306.

As an embodiment, the first report is generated in RRC306.

As an embodiment, the PDCP packet group in the present application is generated by PDCP354.

Example 4

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 shown in Figure 4. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

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 may optionally also include a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454 and an antenna 452.

The second communication device 410 includes a controller/processor 475 , a memory 476 , a receiving processor 470 , a transmitting processor 416 , and may optionally also include a multi-antenna receiving processor 472 , a multi-antenna transmitting processor 471 , a transmitter/receiver 418 and an antenna 420 .

In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the 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 the 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, as well as 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, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and/or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then 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 a different antenna 420.

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 a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding/beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding/beamforming operation 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 receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller/processor 459. The controller/processor 459 implements the functions of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes 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 multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a 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 at the second communication device 410 described 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 L2 layer functions for user plane and control plane. The controller/processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier/single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding/beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the multi-antenna The baseband symbol stream provided by the transmit processor 457 is converted into a radio frequency symbol stream, and then provided to the antenna 452 .

In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller/processor 475 implements the L2 layer functions. The controller/processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can 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 multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller/processor 475 may be provided to the core network.

As an embodiment, the first communication device 450 comprises: at least one processor and at least one memory, the at least one memory comprising computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: receives a first measurement configuration, the first measurement configuration comprises a first report configuration, the first report configuration comprises a first uplink delay configuration, the first uplink delay configuration is used to configure an uplink PDCP packet group delay measurement; performs an uplink PDCP packet group delay measurement according to the first uplink delay configuration; processes N PDCP packet groups; sends a first report, the first The report includes a first delay, which is equal to the ratio of the sum of the delay of each PDCP packet group in the N PDCP packet groups and N; N is a positive integer; wherein, the arrival time of at least the first PDCP packet in any PDCP packet group in the N PDCP packet groups and the time when the default PDCP packet in any PDCP packet group in the N PDCP packet groups is processed are used to determine the delay of any PDCP packet group in the N PDCP packet groups; each PDCP packet group in the N PDCP packet groups is an uplink PDCP packet group; the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates an action when executed by at least one processor, the action including: receiving a first measurement configuration, the first measurement configuration including a first report configuration, the first report configuration including a first uplink delay configuration, the first uplink delay configuration being used to configure an uplink PDCP packet group delay measurement; performing an uplink PDCP packet group delay measurement according to the first uplink delay configuration; processing N PDCP packet groups; sending a first report, the first report including a first delay, the first delay being related to the N The ratio of the sum of the delays of each PDCP packet group in the N PDCP packet groups is equal to the ratio of N; N is a positive integer; wherein, the arrival time of at least the first PDCP packet in any PDCP packet group in the N PDCP packet groups and the time when the default PDCP packet in any PDCP packet group in the N PDCP packet groups is processed are used to determine the delay of any PDCP packet group in the N PDCP packet groups; each PDCP packet group in the N PDCP packet groups is an uplink PDCP packet group; the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, the first communication device 450 corresponds to the first node in this application.

As an embodiment, the second communication device 410 corresponds to the second node in this application.

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

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

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

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

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

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

As an embodiment, the receiver 454 (including the antenna 452, the receiving processor 456 and the controller/processor 459) is used to receive the first measurement configuration in the present application.

As an embodiment, transmitter 454 (including antenna 452, transmit processor 468 and controller/processor 459) is used to send the first report in the present application.

As an embodiment, the transmitter 454 (including the antenna 452, the transmit processor 468 and the controller/processor 459) is used to send the N PDCP packet groups in the present application.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. In FIG5, U01 corresponds to the first node of the present application, and U02 corresponds to the second node of the present application. It is particularly noted that the order in this example does not limit the signal transmission in the present application. The order of transmission and implementation of the numbers, where the steps within F51 are optional.

For the first node U01 , first QoS information is received in step S5101; a first measurement configuration is received in step S5102; N PDCP packet groups are processed in step S5103; uplink PDCP packet group delay measurement is performed according to the first uplink delay configuration in step S5104; and a first report is sent in step S5105.

For the first node U02 , first QoS information is sent in step S5201; a first measurement configuration is sent in step S5202; and a first report is received in step S5203.

In embodiment 5, the first measurement configuration includes a first report configuration, the first report configuration includes a first uplink delay configuration, the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement; the first report includes a first delay, the first delay and the ratio of the sum of the delays of each PDCP packet group in the N PDCP packet groups to N is equal; N is a positive integer;

Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, the first node U01 is a UE, and the second node U02 is a service cell or a cell group of the first node U01.

As an embodiment, the first node U01 is a UE, and the second node U02 is a base station serving the first node U01.

As an embodiment, the first node U01 is a UE, and the second node U02 is the SpCell of the first node U01 or a base station corresponding to the SpCell.

As an embodiment, the first node U01 is a UE, and the second node U02 is the PCell of the first node U01 or a base station corresponding to the PCell.

As an embodiment, the interface between the first node U01 and the second node U02 is a Uu interface.

As an embodiment, step S5101 precedes step S5102.

As an embodiment, step S5102 precedes step S5103.

As an embodiment, step S5103 precedes step S5104.

As an embodiment, step S5103 and step S5104 have no sequence relationship and can be performed simultaneously, for example.

As an embodiment, step S5105 is after step S5104.

As an embodiment, step S5105 is after step S5103.

As an embodiment, when step S5101 does not exist, the first node U01 may use a default configuration to determine the QoS information of the N PDCP packet groups, although it is not very flexible.

As an embodiment, the N PDCP packet groups are associated with the first QoS information.

As an embodiment, the QoS of the N PDCP packet groups is determined by the first QoS information.

As an embodiment, the first QoS information is the QoS information of the N PDCP packet groups.

As an embodiment, the first QoS information is used to configure the PDCP packet group type of the N PDCP packet groups.

As an embodiment, the first QoS information is used to configure the importance of the N PDCP packet groups.

As an embodiment, the first QoS information is used to configure the arrival characteristics of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the arrival characteristics of the PDCP packet group are used to calculate the delay of the uplink PDCP packet group.

As an embodiment, the first QoS information is used to configure the delay requirements of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the delay requirement of the PDCP packet group is used to calculate the delay of the uplink PDCP packet group.

As a sub-embodiment of this embodiment, the delay requirement of the PDCP packet group is used to calculate the delay of the uplink PDCP exceeding the packet group.

As an embodiment, N is equal to 5.

As an embodiment, the delay of each PDCP packet group in the N PDCP packet groups is 10ms, 2ms, 5ms, 11ms, and 4ms respectively, and the first delay is equal to 6.4ms.

As a sub-embodiment of this embodiment, the first PDCP packet group among the N PDCP packet groups includes 3 PDCP packets, where the arrival time of the first PDCP packet is 0ms, and the time when the last PDCP packet is sent is 10ms, then the delay of the first PDCP packet group is 10ms; the calculation method of the delay of other PDCP packet groups is the same.

As an embodiment, the first measurement configuration is sent via SRB1.

As an embodiment, the first report is sent via SRB1.

As an embodiment, the first report includes the result of uplink PDCP packet group delay measurement.

As an embodiment, reporting the result of uplink PDCP packet group delay measurement is triggered periodically, and the first report includes a single result of uplink PDCP packet group delay measurement.

As an embodiment, the first report includes the identity of the first uplink delay configuration.

As an embodiment, the first report includes the N.

As an embodiment, the first report configuration includes a second uplink delay configuration, and the second uplink delay configuration is used to configure the uplink PDCP packet delay measurement; the result of the uplink PDCP packet delay measurement includes a second delay, and the second delay is equal to the ratio of the sum of the delays of each PDCP packet among the M PDCP packets arriving within the first time length to the M; the M is a positive integer; the delay of any PDCP packet among the M PDCP packets is equal to the time interval between the arrival time of any PDCP packet among the M PDCP packets and the time when the uplink MAC PDU carrying at least the first part of the any PDCP packet among the M PDCP packets is scheduled to be sent.

As an embodiment, the second uplink delay configuration is an item in the report configuration list included in the first report configuration.

As an embodiment, the second uplink delay configuration is ul-DelayValueConfig.

As an embodiment, the second uplink delay configuration includes the identity of the target DRB.

As an embodiment, the second uplink delay configuration is used to configure the uplink PDCP packet delay measurement, which means that the uplink PDCP packet delay measurement is to measure the delay of the uplink PDCP packet on the target DRB.

As an embodiment, if the N PDCP packet groups are not transmitted on the target DRB, the M and the N have no relationship.

As an embodiment, if the N PDCP packet groups are transmitted on the target DRB, M is equal to the number of all PDCP packets included in the N PDCP packet groups.

As an embodiment, the phrase scheduled to send means that the scheduling is used for sending, for example, indicating resources used for sending.

As an embodiment, the sentence "the moment when the uplink MAC PDU carrying at least the first part of any one of the M PDCP packets is scheduled to be sent" means or includes: the moment when the earliest uplink MAC PDUs carrying any one of the M PDCP packets are scheduled to be sent.

As an embodiment, as an embodiment, the sentence "the moment when the uplink MAC PDU carrying at least the first part of any one of the M PDCP packets is scheduled to be sent" means or includes: the moment when the MAC layer requests the PDCP to send any one of the M PDCP packets.

As an embodiment, when receiving scheduling signaling, MAC requests data from the PDCP layer.

As a sub-embodiment of this embodiment, even if a PDCP packet cannot be sent completely at one time, PDCP will take the entire packet out of the PDCP buffer and submit it to a lower layer.

As an embodiment, the second delay is equal to the average time that each of the M PDCP packets is cached in the PDCP entity.

As an embodiment, the result of the uplink PDCP packet delay measurement is the second delay.

As an embodiment, the at least first part of any one of the PDCP packets is the earliest sent part of any one of the PDCP packets.

As an embodiment, when the scheduled resources fail to transmit any of the PDCP packets, the at least first part of any of the PDCP packets is the part of any of the PDCP packets that is sent first, and the size of the at least first part depends on the amount of scheduled resources.

As an embodiment, the first delay is determined only by the delay of the PDCP packet group that is not discarded.

As a sub-embodiment of this embodiment, when a PDCP packet group is discarded, no matter whether any PDCP packet in the PDCP packet group is sent, the delay of the PDCP packet group is not included in the first delay.

As a sub-embodiment of this embodiment, the meaning of a PDCP packet group being discarded is that at least one PDCP packet in the PDCP packet group is discarded before completing transmission.

As a sub-embodiment of this embodiment, the meaning of a PDCP packet group being discarded is that at least one PDCP packet in the PDCP packet group has not been confirmed to be transmitted.

As a sub-embodiment of this embodiment, the meaning of a PDCP packet group being discarded is that at least one PDCP packet in the PDCP packet group is discarded without being transmitted.

As an embodiment, the delay of the PDCP packets whose MAC PDUs occupied by at least a part of the M PDCP packets are scheduled and then discarded is still included in the second delay.

As a sub-embodiment of this embodiment, the at least a portion of the M PDCP packets is at least a portion of the PDCP packets.

As a sub-embodiment of this embodiment, the at least part of the M PDCP packets is a portion of bits of at least a portion of the PDCP packets.

As a sub-embodiment of this embodiment, the at least part of the M PDCP packets belongs to a PDCP packet group, and the one PDCP packet group is discarded after the at least part of the M PDCP packets are sent.

As a sub-embodiment of this embodiment, the condition that a PDCP packet group is included in the first delay includes: each PDCP packet in the PDCP packet group is sent.

As a sub-embodiment of this embodiment, the condition for a PDCP packet group to be included in the first delay includes: all MAC PDUs carrying each PDCP packet in the PDCP packet group are scheduled to be sent.

As an embodiment, at least a portion of one PDCP packet among the M PDCP packets is scheduled to be sent, and the one PDCP packet among the M PDCP packets is discarded, and the delay of the one PDCP packet among the M PDCP packets is included in the second delay.

As an embodiment, at least a portion of one PDCP packet among the M PDCP packets is scheduled to be sent, and a portion of bits of the one PDCP packet among the M PDCP packets are discarded, and the delay of the one PDCP packet among the M PDCP packets is included in the second delay.

As an embodiment, a first PDCP packet group set arrives at the PDCP of the first node U01, and the first PDCP packet group set includes the N PDCP packet groups and at least one PDCP packet group other than the N PDCP packet groups; the uplink PDCP packet delay measurement performed according to the second uplink delay configuration is to measure the at least one PDCP packet group other than the N PDCP packet groups included in the first PDCP packet group set.

As an embodiment, a first PDCP packet group set arrives at the PDCP of the first node U01, and the first PDCP packet group set includes the N PDCP packet groups and at least one PDCP packet group other than the N PDCP packet groups; the second delay only includes the delay of the at least one PDCP packet group other than the N PDCP packet groups included in the first PDCP packet group set.

As an embodiment, the first PDCP packet group set is a data burst.

Example 6

Example 6 illustrates a schematic diagram in which the arrival time of at least the first PDCP packet in any one of N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups according to an embodiment of the present application, as shown in Figure 6.

As an embodiment, when any one of the N PDCP packet groups includes only one PDCP packet, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups means that the arrival time of the PDCP packet included in any one of the N PDCP packet groups and the time when this PDCP packet is processed are jointly used to determine the delay of any one of the N PDCP packet groups.

As an embodiment, when any one of the N PDCP packet groups includes only one PDCP packet, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups. The meaning is that the time interval between the arrival time of the PDCP packet included in any one of the N PDCP packet groups and the time when this PDCP packet is processed is the delay of any one of the N PDCP packet groups.

As an embodiment, when any one of the N PDCP packet groups includes multiple PDCP packets, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups means that the arrival time of the first PDCP packet included in any one of the N PDCP packet groups and the processing time of the last processed PDCP packet are jointly used to determine the delay of any one of the N PDCP packet groups.

As an embodiment, when any one of the N PDCP packet groups includes multiple PDCP packets, the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups. The meaning of delay is that the delay of each PDCP packet included in any one of the N PDCP packet groups is commonly used to determine the delay of any one of the N PDCP packet groups.

As an embodiment, when any one of the N PDCP packet groups includes multiple PDCP packets, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups. The meaning is: the arrival time of the first PDCP packet included in any one of the N PDCP packet groups and the time when the last PDCP packet sent is sent jointly determine the delay of any one of the N PDCP packet groups.

As an embodiment, when any one of the N PDCP packet groups includes multiple PDCP packets, the sentence that the arrival time of at least the first PDCP packet in any one of the N PDCP packet groups and the time when the last PDCP packet of the default PDCP packet in any one of the N PDCP packet groups is processed are used to determine the delay of any one of the N PDCP packet groups. The meaning is: the arrival time of the first PDCP packet included in any one of the N PDCP packet groups and the time when the default PDCP packet is processed jointly determine the delay of any one of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the default PDCP packet included in any one of the N PDCP packet groups is the last processed PDCP packet included in any one of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the default PDCP packet included in any one of the N PDCP packet groups is the last transmitted PDCP packet included in any one of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the default PDCP packet included in any one of the N PDCP packet groups is the last scheduled PDCP packet included in any one of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the default PDCP packet included in any one of the N PDCP packet groups is the PDCP packet with the largest sequence number included in any one of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the default PDCP packet included in any one of the N PDCP packet groups is the second to last PDCP packet sent or scheduled included in any one of the N PDCP packet groups.

As an embodiment, the meaning of a PDCP packet being scheduled is that the MAC PDU carrying the PDCP packet is scheduled.

As an embodiment, the meaning of the PDCP packet being scheduled is that the resources indicated by the sent scheduling are used to transmit the PDCP packet.

As an embodiment, the PDCP packet is scheduled in the sense that the MAC PDU carrying at least the first part of the PDCP packet is scheduled.

As an embodiment, the PDCP packet is scheduled in the sense that the resources indicated by the sent scheduling are received for transmitting at least the first part of the PDCP packet.

Example 7

Embodiment 7 illustrates a schematic diagram of a first delay according to an embodiment of the present application, as shown in FIG7 .

Example 7 provides a specific implementation method for determining the first delay, where M(T) in Figure 7 is equal to the first delay, and M() represents a formula for calculating the uplink PDCP packet group delay, where T represents a period of time, i.e., the uplink PDCP packet group delay measurement performed within T.

As an embodiment, the result of uplink PDCP packet group delay measurement is the first delay.

As an embodiment, T is the first time length.

As an embodiment, the first node measures the N PDCP packet groups within the time T.

As an embodiment, the behavior processes N PDCP packet groups, including measuring the N PDCP packet groups.

As an example, Used to index any PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, It indicates that the delay of each PDCP packet group in the N PDCP packet groups is accumulated, wherein tProcess(i, n _i )-tArrival(i, 1 _i ) indicates the delay of the i-th PDCP packet group in the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, FIG. 7 shows that the delay of each PDCP packet group in the N PDCP packet groups is accumulated and then divided by the N, and then rounded.

As a sub-embodiment of this embodiment, the rounding is rounding down.

As an embodiment, tProcess(i, n _i ) in FIG. 7 represents the maximum number of packets in the i-th PDCP packet group among the N PDCP packet groups. The time when the next PDCP packet is processed.

As a sub-embodiment of this embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, n _i is used to index the nth PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and the i-th PDCP packet group among the N PDCP packet groups includes n PDCP packets; similarly, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, tArrival(i, 1 _i ) in FIG. 7 represents the arrival time of the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, n _i is used to index the n-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i is an arbitrary integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, the unit of the first delay is 0.1 milliseconds.

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

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

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

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

As an embodiment, the arrival time includes the time of arrival at a PDCP higher service access point.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival.

As a sub-embodiment of this embodiment, for example, the earliest arriving PDCP packet group among the N PDCP packet groups is the first PDCP packet group.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival time of the earliest arriving PDCP packet included therein.

As a sub-embodiment of this embodiment, for example, the PDCP packet group to which the earliest arriving PDCP packet among the N PDCP packet groups belongs is the first PDCP packet group.

As an embodiment, the meaning of processing in the phrase "at the moment of being processed" is the same as the meaning of the behavior of processing N PDCP packet groups.

As an example, the meaning of the processing at the moment when the phrase is processed can refer to Example 1, Example 5, and Example 6.

As an embodiment, the first delay determined by the above method is more accurate in measuring the maximum delay of the PDCP packet group, which is helpful in grasping the bottom line of network transmission.

Example 8

Embodiment 8 illustrates a schematic diagram of a first delay according to an embodiment of the present application, as shown in FIG8 .

Example 8 provides a specific implementation method for determining the first delay, where M(T) in Figure 8 is equal to the first delay, and M() represents a formula for calculating the uplink PDCP packet group delay, where T represents a period of time, i.e., the uplink PDCP packet group delay measurement performed within T.

As an embodiment, the first delay is a result of an uplink PDCP packet group delay measurement.

As an embodiment, T is the first time length.

As an embodiment, the result of uplink PDCP packet group delay measurement is the first delay.

As an embodiment, the first node measures the N PDCP packet groups within the time T.

As an embodiment, the behavior processes N PDCP packet groups, including measuring the N PDCP packet groups.

As an example, Used to index any PDCP packet group among the N PDCP packet groups.

As an embodiment, FIG. 8 shows that the average value of the delay of each PDCP packet of each PDCP packet group in the N PDCP packet groups is accumulated and then divided by N, and then rounded.

As a sub-embodiment of this embodiment, the rounding is rounding down.

As an embodiment, tProcess(i, j _i ) in FIG. 8 represents the time when the j th PDCP packet in the i th PDCP packet group among the N PDCP packet groups is processed.

As a sub-embodiment of this embodiment, the i is any integer belonging to [1, N], indexing the i-th packet in the N PDCP packet groups. PDCP packet group.

As a sub-embodiment of this embodiment, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups; similarly, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, tArrival(i, 1 _i ) in FIG. 8 represents the arrival time of the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i is an arbitrary integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an example, Represents the sum of the PDCP packet delays of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i-th PDCP packet group among the N PDCP packet groups includes K(i) PDCP packets.

As a sub-embodiment of this embodiment, the PDCP packets included in the i-th PDCP packet group among the N PDCP packet groups are numbered or indexed as 1, 2,…, K(i)-1, K(i).

As an example, Represents the average PDCP packet delay of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i-th PDCP packet group among the N PDCP packet groups includes K(i) PDCP packets.

As an example, Represents the average sum of the PDCP packet delays of each PDCP packet group in the N PDCP packet groups.

As an embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, in FIG8, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, the unit of the first delay is 0.1 milliseconds.

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

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

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

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

As an embodiment, the arrival time includes the time of arrival at a PDCP higher service access point.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival.

As a sub-embodiment of this embodiment, for example, the earliest arriving PDCP packet group among the N PDCP packet groups is the first PDCP packet group.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival time of the earliest arriving PDCP packet included therein.

As a sub-embodiment of this embodiment, for example, the PDCP packet group to which the earliest arriving PDCP packet among the N PDCP packet groups belongs is the first PDCP packet group.

As an embodiment, the meaning of processing in the phrase "at the moment of being processed" is the same as the meaning of the behavior of processing N PDCP packet groups.

As an example, the meaning of the processing at the moment when the phrase is processed can refer to Example 1, Example 5, and Example 6.

As an embodiment, the first delay determined by the above method is more accurate for measuring the average delay of the PDCP packet group, which is helpful for grasping the comprehensive performance of network transmission.

Example 9

Embodiment 9 illustrates a schematic diagram of uplink PDCP exceeding packet group delay measurement according to an embodiment of the present application, as shown in FIG9 .

Example 9 provides an implementation method for determining the uplink PDCP exceeding the packet group delay measurement. M(T) in FIG. 10 is equal to the first delay, M() represents a formula for calculating the uplink PDCP exceeding the packet group delay measurement, where T represents a period of time, that is, the uplink PDCP executed within T Perform PDCP over-packet group delay measurement.

As an embodiment, the first report configuration includes a third uplink delay configuration; the third uplink delay configuration includes a first threshold; the third uplink delay configuration is used to configure the uplink PDCP exceeding packet group delay measurement; the measurement result of the uplink PDCP exceeding packet group delay includes the ratio between the number of PDCP packet groups in which the delay exceeds the first threshold in the PDCP packet groups measured within the first time length and the total number of PDCP packet groups measured within the first time length.

As a sub-embodiment of this embodiment, the third uplink delay configuration in the sentence is used to configure the uplink PDCP exceeding packet group delay measurement including configuring the first threshold.

As an embodiment, the T in FIG. 9 is the first time length.

As an embodiment, the first node measures the N PDCP packet groups within the time T.

As an embodiment, the behavior processes N PDCP packet groups, including measuring the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior processes N PDCP packet groups, including the arrival of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior of processing N PDCP packet groups includes sending the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior processes N PDCP packet groups, including sending at least a portion of each PDCP packet in the N PDCP packet groups.

As an embodiment, a candidate value of the first threshold is 1 ms.

As an embodiment, a candidate value of the first threshold is 5ms.

As an embodiment, a candidate value of the first threshold is 10ms.

As an embodiment, the network determines the first threshold according to the QoS requirements of the services of the N PDCP packet groups.

As an embodiment, nExcess(T) is the number of PDCP packet groups whose delay exceeds the first threshold among the N PDCP packet groups measured within the time T.

As an embodiment, the delay of the i-th PDCP packet group among the N PDCP packet groups is tULdelay(i).

As a sub-embodiment of this embodiment, the i-th PDCP packet group is any PDCP packet group among the N PDCP packet groups.

As an embodiment, tProcess(i, n _i ) in FIG. 9 represents the time when the last PDCP packet in the i-th PDCP packet group among the N PDCP packet groups is processed.

As a sub-embodiment of this embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, wherein n _t is used to index the nth PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and the i-th PDCP packet group among the N PDCP packet groups includes n PDCP packets; similarly, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, tArrival(i, 1 _t ) in FIG. 9 represents the arrival time of the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, n _i is used to index the n-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i is an arbitrary integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, the unit of the first delay is 0.1 milliseconds.

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

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

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

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

As an embodiment, the arrival time includes the time of arrival at a PDCP higher service access point.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival.

As a sub-embodiment of this embodiment, for example, the earliest arriving PDCP packet group among the N PDCP packet groups is the first PDCP packet group.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival time of the earliest arriving PDCP packet included therein.

As a sub-embodiment of this embodiment, for example, the PDCP packet group to which the earliest arriving PDCP packet among the N PDCP packet groups belongs is the first PDCP packet group.

As an embodiment, the meaning of processing in the phrase "at the moment of being processed" is the same as the meaning of the behavior of processing N PDCP packet groups.

As an example, the meaning of the processing at the moment when the phrase is processed can refer to Example 1, Example 5, and Example 6.

As an embodiment, the uplink PDCP exceeding packet group delay determined by the above method is more accurate for obtaining the maximum delay based on the PDCP packet group, which is helpful for grasping the bottom line of network transmission.

Example 10

Embodiment 10 illustrates a schematic diagram of uplink PDCP exceeding packet group delay measurement according to an embodiment of the present application, as shown in FIG10 .

Example 10 provides another implementation method for determining that the uplink PDCP exceeds the packet group delay measurement. M(T) in Figure 10 is equal to the first delay, and M() represents a formula for calculating the uplink PDCP exceeds the packet group delay measurement, where T represents a period of time, that is, the uplink PDCP exceeds the packet group delay measurement performed within T.

As an embodiment, the first report configuration includes a third uplink delay configuration; the third uplink delay configuration includes a first threshold; the third uplink delay configuration is used to configure the uplink PDCP exceeding packet group delay measurement; the measurement result of the uplink PDCP exceeding packet group delay includes the ratio between the number of PDCP packet groups in which the delay exceeds the first threshold in the PDCP packet groups measured within the first time length and the total number of PDCP packet groups measured within the first time length.

As a sub-embodiment of this embodiment, the third uplink delay configuration in the sentence is used to configure the uplink PDCP exceeding packet group delay measurement including configuring the first threshold.

As an embodiment, the T in FIG. 10 is the first time length.

As an embodiment, the first node measures the N PDCP packet groups within the time T.

As an embodiment, the behavior processes N PDCP packet groups, including measuring the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior processes N PDCP packet groups, including the arrival of the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior of processing N PDCP packet groups includes sending the N PDCP packet groups.

As a sub-embodiment of this embodiment, the behavior processes N PDCP packet groups, including sending at least a portion of each PDCP packet in the N PDCP packet groups.

As an embodiment, a candidate value of the first threshold is one of 1ms, 2ms, 5ms, and 10ms.

As an embodiment, the network determines the first threshold according to the QoS requirements of the services of the N PDCP packet groups.

As an embodiment, nExcess(T) is the number of PDCP packet groups whose delay exceeds the first threshold among the N PDCP packet groups measured within the time T.

As an embodiment, the delay of the i-th PDCP packet group among the N PDCP packet groups is tULdelay(i).

As a sub-embodiment of this embodiment, the i-th PDCP packet group is any PDCP packet group among the N PDCP packet groups.

As an embodiment, tProcess(i, j _i ) in FIG. 10 represents the time when the j th PDCP packet in the i th PDCP packet group among the N PDCP packet groups is processed.

As a sub-embodiment of this embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups; similarly, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, tArrival(i, 1 _t ) in FIG. 10 represents the arrival time of the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i is an arbitrary integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an example, Represents the sum of the PDCP packet delays of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i-th PDCP packet group among the N PDCP packet groups includes K(i) PDCP packets.

As a sub-embodiment of this embodiment, the PDCP packets included in the i-th PDCP packet group among the N PDCP packet groups are numbered or indexed as 1, 2,…, K(i)-1, K(i).

As an example, Represents the average PDCP packet delay of the i-th PDCP packet group among the N PDCP packet groups.

As a sub-embodiment of this embodiment, the i-th PDCP packet group among the N PDCP packet groups includes K(i) PDCP packets.

As an embodiment, the i is any integer belonging to [1, N], indexing the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, in FIG. 10 , 1 _i is used to index the first PDCP packet of the i-th PDCP packet group among the N PDCP packet groups, and similarly, j _i is used to index the j-th PDCP packet of the i-th PDCP packet group among the N PDCP packet groups.

As an embodiment, the unit of the first delay is 0.1 milliseconds.

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

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

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

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

As an embodiment, the arrival time includes the time of arrival at a PDCP higher service access point.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival.

As a sub-embodiment of this embodiment, for example, the earliest arriving PDCP packet group among the N PDCP packet groups is the first PDCP packet group.

As an embodiment, the N PDCP packet groups are determined to be the PDCP packet group number according to the order of arrival time of the earliest arriving PDCP packet included therein.

As a sub-embodiment of this embodiment, for example, the PDCP packet group to which the earliest arriving PDCP packet among the N PDCP packet groups belongs is the first PDCP packet group.

As an embodiment, the meaning of processing in the phrase "at the moment of being processed" is the same as the meaning of the behavior of processing N PDCP packet groups.

As an example, the meaning of the processing at the moment when the phrase is processed can refer to Example 1, Example 5, and Example 6.

As an embodiment, the uplink PDCP exceeding packet group delay determined by the above method will be more accurate for obtaining the measurement result based on the average delay of the PDCP packet group, which is helpful for mastering the comprehensive performance of network transmission.

Embodiment 11

Embodiment 11 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application; as shown in FIG11. In FIG11, the processing device 1100 in the first node includes a first receiver 1101, a first transmitter 1102, and a first processor 1103. In Embodiment 11,

The first receiver 1101 receives a first measurement configuration, where the first measurement configuration includes a first report configuration, where the first report configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement;

The first processor 1103 performs uplink PDCP packet group delay measurement according to the first uplink delay configuration; and processes N PDCP packet groups;

The first transmitter 1102 sends a first report, where the first report includes a first delay, where the first delay is equal to a ratio of a sum of a delay of each PDCP packet group in the N PDCP packet groups to N, where N is a positive integer;

Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.

As an embodiment, any one of the N PDCP packet groups is composed of one or more PDUs carrying a payload of a unit of information generated by the application layer.

As an embodiment, the first report configuration includes a second uplink delay configuration, and the second uplink delay configuration is used to configure the uplink PDCP packet delay measurement; the result of the uplink PDCP packet delay measurement includes a second delay, and the second delay is equal to the ratio of the sum of the delays of each PDCP packet in the M PDCP packets arriving within the first time length to the M; the M is a positive integer; the M The delay of any PDCP packet among the PDCP packets is equal to the time interval between the arrival time of any PDCP packet among the M PDCP packets and the time when the uplink MAC PDU carrying at least the first part of any PDCP packet among the M PDCP packets is scheduled to be sent.

As an embodiment, the sentence that the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups includes: the delay of any of the N PDCP packet groups is equal to the time interval between the arrival of the first PDCP packet in any of the N PDCP packet groups and the processing of the last PDCP packet; the phrase the last PDCP packet is processed means that the last PDCP packet is sent or at least the first part of the last PDCP packet is scheduled to be sent.

As an embodiment, the sentence that the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups includes: the delay of any of the N PDCP packet groups is equal to the average value of the delay of each PDCP packet group in the N PDCP packet groups.

As an embodiment, the first processor 1103 performs uplink PDCP exceeding packet group delay measurement;

Among them, the first report configuration includes a third uplink delay configuration; the third uplink delay configuration includes a first threshold; the third uplink delay configuration is used to configure the uplink PDCP exceeding packet group delay measurement; the measurement result of the uplink PDCP exceeding packet group delay includes the ratio between the number of PDCP packet groups in the PDCP packet groups measured within the first time length whose delay exceeds the first threshold and the total number of PDCP packet groups measured within the first time length.

As an embodiment, the first report configuration includes a fourth uplink delay configuration; the fourth uplink delay configuration includes a second threshold; the fourth uplink delay configuration is used to configure the uplink PDCP exceeding packet delay measurement; the measurement result of the uplink PDCP exceeding packet delay includes the ratio between the number of PDCP packets in which the delay exceeds the second threshold in the PDCP packets measured within the first time length and the total number of PDCP packets measured within the first time length.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating a plurality of DRBs, and the N PDCP packet groups occupy the plurality of DRBs.

As an embodiment, the phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating the identity of the first DRB and the first PDCP packet group type, the N PDCP packet groups occupy the first DRB and belong to the first PDCP packet group type; the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type; the uplink PDCP packet group delay measurement is only for the PDCP packet group of the first PDCP packet group type.

As an embodiment, the first delay is determined only by the delay of the PDCP packet group that is not discarded; the delay of the PDCP packets whose MAC PDUs occupied by at least a part of the M PDCP packets are scheduled and then discarded is still included in the second delay.

As an embodiment, the first node is a user equipment (UE).

As an embodiment, the first node is a terminal supporting a large delay difference.

As an embodiment, the first node is a terminal supporting NTN.

As an embodiment, the first node is an aircraft or a ship.

As an embodiment, the first node is a mobile phone or a vehicle-mounted terminal.

As an embodiment, the first node is a helmet or glasses.

As an embodiment, the first node is an Internet of Things terminal or an industrial Internet of Things terminal.

As an embodiment, the first node is a device supporting low-latency and high-reliability transmission.

As an embodiment, the first receiver 1101 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 Example 4.

As an embodiment, the first transmitter 1102 includes at least one of the antenna 452, transmitter 454, transmit processor 468, multi-antenna transmit processor 457, controller/processor 459, memory 460, or data source 467 in Embodiment 4.

A person skilled in the art can understand that all or part of the steps in the above method can be completed by instructing related 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 disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of software function modules. This application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IoT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers, satellite communication equipment, ship communication equipment, NTN user equipment and other wireless communication equipment. The base station or system equipment in this application includes but is not limited to macro cell base stations, micro cell 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 equipment.

The present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered as illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims (15)

A first node used for wireless communication, comprising: A first receiver receives a first measurement configuration, where the first measurement configuration includes a first report configuration, where the first report configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement; A first processor performs uplink PDCP packet group delay measurement according to the first uplink delay configuration; and processes N PDCP packet groups; A first transmitter sends a first report, wherein the first report includes a first delay, wherein the first delay is equal to a ratio of a sum of a delay of each PDCP packet group in the N PDCP packet groups to N, where N is a positive integer; Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets. The first node according to claim 1, characterized in that Any of the N PDCP packet groups consists of one or more PDUs carrying a payload of one unit of information generated by the application layer. The first node according to claim 2, characterized in that Any of the N PDCP packet groups is a PDU set, or carries a PDU set. The first node according to any one of claims 1 to 3, characterized in that: The first report configuration includes a second uplink delay configuration, and the second uplink delay configuration is used to configure the uplink PDCP packet delay measurement; the result of the uplink PDCP packet delay measurement includes a second delay, and the second delay is equal to the ratio of the sum of the delays of each PDCP packet among the M PDCP packets arriving within the first time length to the M; the M is a positive integer; the delay of any PDCP packet among the M PDCP packets is equal to the time interval between the arrival time of any PDCP packet among the M PDCP packets and the time when the uplink MAC PDU carrying at least the first part of the any PDCP packet among the M PDCP packets is scheduled to be sent. The first node according to any one of claims 1 to 4, characterized in that: The sentence "the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups" includes: the delay of any of the N PDCP packet groups is equal to the time interval between the arrival of the first PDCP packet in any of the N PDCP packet groups and the processing of the last PDCP packet; the phrase "the last PDCP packet is processed" includes the last PDCP packet being sent or at least the first part of the last PDCP packet being scheduled to be sent. The first node according to any one of claims 1 to 5, characterized in that: The sentence "the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the last PDCP packet is processed are used to determine the delay of any of the N PDCP packet groups" includes: the delay of any of the N PDCP packet groups is equal to the average value of the delay of each PDCP packet group in the N PDCP packet groups. The first node according to any one of claims 1 to 6, characterized in that it comprises: The first processor performs uplink PDCP exceeding packet group delay measurement; Among them, the first report configuration includes a third uplink delay configuration; the third uplink delay configuration includes a first threshold; the third uplink delay configuration is used to configure the uplink PDCP exceeding packet group delay measurement; the measurement result of the uplink PDCP exceeding packet group delay includes the ratio between the number of PDCP packet groups in the PDCP packet groups measured within the first time length whose delay exceeds the first threshold and the total number of PDCP packet groups measured within the first time length. The first node according to any one of claims 1 to 7, characterized in that: The first report configuration includes a fourth uplink delay configuration; the fourth uplink delay configuration includes a second threshold; the fourth uplink delay configuration is used to configure the uplink PDCP exceeding packet delay measurement; the measurement result of the uplink PDCP exceeding packet delay includes the ratio between the number of PDCP packets in which the delay exceeds the second threshold in the PDCP packets measured within the first time length and the total number of PDCP packets measured within the first time length. The first node according to any one of claims 1 to 8, characterized in that: The phrase "the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement, including indicating a plurality of DRBs, and the N PDCP packet groups occupy the plurality of DRBs. The first node according to any one of claims 1 to 9, characterized in that: The phrase "the first uplink delay configuration is used to configure the uplink PDCP packet group delay measurement, including indicating the identity of the first DRB and the first PDCP packet group type, the N PDCP packet groups occupy the first DRB and belong to the first PDCP packet group type; the first DRB is used to carry at least one PDCP packet group that does not belong to the first PDCP packet group type; the uplink PDCP packet group delay measurement is only for the PDCP packet group of the first PDCP packet group type. The first node according to claim 10, characterized in that The PDCP packet group type refers to the importance of a specific PDCP packet group. The first node according to any one of claims 1 to 11, characterized in that: The first delay is determined only by the delay of the PDCP packet group that is not discarded; The first node according to claim 4, characterized in that The first delay is determined only by the delay of the PDCP packet group that is not discarded; the delay of the PDCP packets whose MAC PDUs occupied by at least a part of the M PDCP packets are scheduled and then discarded is still counted into the second delay. The first node according to any one of claims 1 to 13, characterized in that: The default PDCP packet is the last PDCP packet. A method in a first node for wireless communication, comprising: Receiving a first measurement configuration, where the first measurement configuration includes a first report configuration, where the first report configuration includes a first uplink delay configuration, where the first uplink delay configuration is used to configure uplink PDCP packet group delay measurement; Perform uplink PDCP packet group delay measurement according to the first uplink delay configuration; process N PDCP packet groups; Sending a first report, the first report comprising a first delay, the first delay being equal to a ratio of a sum of a delay of each of the N PDCP packet groups and N, where N is a positive integer; Among them, the arrival time of at least the first PDCP packet in any of the N PDCP packet groups and the time when the default PDCP packet in any of the N PDCP packet groups is processed are used to determine the delay of any of the N PDCP packet groups; each of the N PDCP packet groups is an uplink PDCP packet group; and the N PDCP packet groups include at least one PDCP packet group consisting of multiple PDCP packets.