Measurement methods and apparatus

Abstract

The embodiment of the application discloses a kind of measurement method and equipment, belong to communication technical field.The measurement method of the embodiment of the application includes: integrated access and backhaul (IAB) node is measured to first parameter and obtains measurement result, the first parameter includes layer 2 parameter, the first parameter includes at least one of the following: average throughput, data packet delay and data packet loss rate.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of communication, and particularly relates to a measurement method and equipment, which can include an integrated access and backhaul (IAB) node. BACKGROUND

[0002] The IAB system is introduced to solve the problem of insufficient deployment of wired transmission networks in the case of dense deployment of access points, that is, in the absence of a wired transmission network, the access point can rely on wireless backhaul.

[0003] Due to the particularity of the IAB system, the measurement method in the related art cannot be directly used for the IAB system, and the related art does not propose a measurement method suitable for the IAB system, so that quality of service (QoS) verification or QoS monitoring cannot be achieved, resulting in low communication quality. SUMMARY

[0004] Embodiments of the present application provide a measurement method and equipment, which can solve the problem of low communication quality caused by the inability to measure the IAB system in related systems.

[0005] In a first aspect, a measurement method is provided, including: an IAB node measuring a first parameter to obtain a measurement result, the first parameter including a layer 2 parameter, and the first parameter including at least one of: average throughput, packet delay, and packet loss rate.

[0006] In a second aspect, an IAB node is provided, including: a measurement module configured to measure a first parameter to obtain a measurement result, the first parameter including a layer 2 parameter, and the first parameter including at least one of: average throughput, packet delay, and packet loss rate.

[0007] In a third aspect, an IAB node is provided, including a processor, a memory, and a program or instructions stored on the memory and executable on the processor, and the program or instructions are executed by the processor to implement the method of the first aspect.

[0008] In a fourth aspect, an IAB node is provided, including a processor and a communication interface, and the processor is configured to measure a first parameter to obtain a measurement result, the first parameter including a layer 2 parameter, and the first parameter including at least one of: average throughput, packet delay, and packet loss rate.

[0009] In a fifth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, and the program or instructions are executed by a processor to implement the method of the first aspect.

[0010] In a sixth aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface and the processor coupled, the processor configured to execute a program or instructions to implement the method according to the first aspect.

[0011] In a seventh aspect, a computer program / program product is provided, the computer program / program product stored in a non-transitory storage medium, the program / program product executed by at least one processor to implement the method according to the first aspect.

[0012] In the embodiments of the present application, the IAB node measures at least one of the average throughput, the packet delay and the packet loss rate to obtain a measurement result, so that the IAB node can also support the measurement reporting of the instant MDT, and the performance indicators can be monitored by the OAM, or the QoS verification or QoS monitoring of the MDT can be implemented, and the communication efficiency is improved. BRIEF DESCRIPTION OF DRAWINGS

[0013] Figure 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

[0014] Figure 2 is a schematic flowchart of a measurement method according to an embodiment of the present application;

[0015] Figure 3 is a schematic diagram of delay measurement in a measurement method according to an embodiment of the present application;

[0016] Figure 4 is a schematic diagram of delay measurement in a measurement method according to an embodiment of the present application;

[0017] Figure 5 is a schematic diagram of the structure of an IAB node according to an embodiment of the present application;

[0018] Figure 6 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;

[0019] Figure 7 is a schematic diagram of the structure of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] The technical solutions in the embodiments of the present application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0021] The terms "first", "second", and the like in the description and in the claims of the present application are used for distinguishing between similar objects discussed in the specification and claims and do not necessarily indicate a specific order or sequence. It should be understood that the terms so used are interchangeable under appropriate circumstances and embodiments of the present application might operate in other sequences or orders than those described or otherwise illustrated herein. Furthermore, the terms "comprise", "include", "contain", and / or "have" should be understood to be open terms, i.e., to mean including but not limited to. The terms "and / or" and / or "and / or" in the description and in the claims of the present application are to be interpreted as open terms, i.e., indicating that there is at least one of the stated alternatives, but that there can be more than one of each alternative, and that the alternatives can be used individually or in any combination. The terms "and / or" and / or "and / or" in the description and in the claims of the present application are to be interpreted as open terms, i.e., indicating that there is at least one of the stated alternatives, but that there can be more than one of each alternative, and that the alternatives can be used individually or in any combination.

[0022] It is worth noting that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably in the embodiments of the present application, and the described techniques can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for the purpose of example, and NR terminology is used in most of the following description, and these techniques can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems. th Generation,6G) communication systems.

[0023] Figure 1A schematic diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a palm computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR) / virtual reality (VR) device, a robot, a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (a home device with wireless communication function, such as a refrigerator, a television, a washing machine, or furniture, etc.), and the like. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart ankle bracelet, a smart ankle chain, etc.), a smart wristband, smart clothing, a game console, and the like. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a next generation node B (gNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art, as long as the same technical effects are achieved. The base station is not limited to a specific technical term, and it should be noted that only the base station in the NR system is taken as an example in the embodiments of the present application, but the specific type of the base station is not limited.

[0024] The measurement method and device provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0025] Since the F1-U protocol stack established between the IAB Donor Unit (IAB) and the Access IAB Distributed Unit (DU) lacks the concept of a Data Radio Bearer (DRB), for IAB Mobile Termination (MT) (including Access IAB and Intermediate IAB), what is visible is the transmission of data packets in the Backhaul (BH) Radio Link Control (RLC) channel. Traditional measurements are based on DRB-level granularity calculations, therefore, traditional measurement methods are not applicable to IAB systems.

[0026] In addition, since a new protocol sublayer, the Backhaul Adaptation Protocol (BAP) layer, has been introduced into the IAB system, the latency generated when data packets are processed at the BAP layer needs to be considered. If the traditional side measurement method is used directly, the measurement calculation will be inaccurate.

[0027] In summary, it is necessary to define Layer 2 measurement parameters (such as average throughput, packet latency, and packet loss rate) in the IAB scenario, so that IAB nodes can also support the reporting of immediate minimum path test (MDT) measurements, enabling Operations and Maintenance (OAM) to monitor performance indicators, or to perform QoS verification or QoS monitoring of MDTs.

[0028] like Figure 2 As shown in the figure, this application embodiment provides a measurement method 200, which can be executed by an IAB node. In other words, the method can be executed by software or hardware installed on the IAB node, and the method includes the following steps.

[0029] S202: The IAB node measures the first parameter to obtain the measurement result. The first parameter includes layer 2 parameters, which include at least one of the following: average throughput, packet latency, and packet loss rate.

[0030] Optionally, the IAB node (i.e. the executor of the measurement) can be at least one of the following: 1) IAB Mobile Termination (MT), 2) IAB Distributed Unit (DU), 3) IAB Host Distributed Unit (IAB-donor-DU), and 4) IAB Host Integration Unit (IAB-donor-CU).

[0031] The measurement method provided by the embodiments of the present application enables the IAB node to support the measurement reporting of instant MDT, and thus the performance index monitoring of OAM, or the QoS verification or QoS monitoring of MDT, and improves the communication efficiency.

[0032] The measurement methods of the average throughput, the packet delay, and the packet loss rate will be introduced in detail in the following three parts.

[0033] First part

[0034] In this embodiment, the first parameter includes the average throughput, and the average throughput is measured according to at least one of the following granularities: 1) each BH link, 2) each BH RLC channel of each BH link, 3) each GPRS Tunneling Protocol-User plane Tunnel Endpoint Identifier (GTP-UTEID), and 4) each IAB node.

[0035] In a specific example, the executor of the average throughput measurement is an IAB distribution unit (IAB-DU).

[0036] In this embodiment, the measurement of the first parameter by the IAB node to obtain the measurement result includes at least one of the following:

[0037] 1) In the case where the granularity of the measurement includes each BH link, the measurement result is obtained according to the quotient of the sum of the throughputs of the BH RLC channels on the first BH link in the first time period and the first time period.

[0038] The average throughput can be independently measured according to the uplink and the downlink.

[0039] Optionally, the BH RLC channels on the first BH link include at least one of the following: the uplink entry BH RLC channel on the first BH link, and the downlink exit BH RLC channel on the first BH link.

[0040] Optionally, in the uplink direction, the first time period is related to the following two time points: the time point at which the second last data packet in the burst data is successfully received on the BH RLC channel on the first BH link; and the time point at which the first data packet in the burst data starts to be sent on the BH RLC channel on the first BH link.

[0041] In the downlink direction, the first time period is related to the following two points: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the first BH link, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel, i.e., the burst data clears all data in the current BH RLC channel buffer; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDU on the BH RLC channel of the first BH link is generated and available for transmission, wherein there were previously no available RLC SDUs for transmission in the BH RLC channel.

[0042] 2) When the granularity of the measurement includes each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the first BH RLC channel during the second time period, and the second time period.

[0043] The average throughput can be measured independently for uplink and downlink.

[0044] Optionally, the first BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel and a downlink egress BH RLC channel.

[0045] Optionally, in the uplink direction, the second time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the first BH RLC channel; and the time point when the first data packet in the burst data begins to be transmitted on the first BH RLC channel.

[0046] In the downlink direction, the second time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the first BH RLC channel, wherein the transmission of the burst data includes available RLC SDUs on the first BH RLC channel, i.e., the burst data clears all data in the buffer of the first BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDU on the first BH RLC channel is generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the first BH RLC channel.

[0047] 3) When the granularity of the measurement includes each GTP-U TEID, the measurement result is obtained according to the quotient of the following two: the total throughput of data transmitted on the data radio bearer DRB or GTP-U of the first terminal UE during the third time period, wherein the first UE is a UE that uses the IAB node as an access node.

[0048] The average throughput can be measured independently for uplink and downlink.

[0049] Optionally, in the uplink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted on the DRB or GTP-U.

[0050] In the downlink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the DRB or GTP-U, the transmission of the burst data includes available RLC SDUs on the DRB or GTP-U, i.e., the burst data clears all data in the DRB or GTP-U buffer; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDU on the DRB or GTP-U is generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the DRB or GTP-U.

[0051] 4) When the granularity of the measurement includes each IAB node, the measurement result is obtained by the quotient of the following two: the total throughput of the BH RLC channel on the BH link of the IAB node during the fourth time period.

[0052] The average throughput can be measured independently for uplink and downlink.

[0053] Optionally, the BH RLC channel on the BH link of the IAB node includes at least one of the following: an uplink ingress BH RLC channel on the BH link of the IAB node, and a downlink egress BH RLC channel on the BH link of the IAB node.

[0054] Optionally, in the uplink direction, the fourth time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully received on the BH RLC channel of the BH link of the IAB node; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the BH link of the IAB node.

[0055] In the downlink direction, the fourth time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the BHRLC channel of the BH link of the IAB node, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel, i.e., the burst data clears all data in the current BH RLC channel buffer; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDU is generated and available for transmission on the BH RLC channel of the BH link of the IAB node, wherein there were no previously available RLC SDUs available for transmission in the BH RLC channel.

[0056] In the above embodiments, for buffered data that can be included in an initial Hybrid Automatic Repeat Request (HARQ) process for transmission (such as small databursts), the transmission time (or transmission period) corresponding to the burst data is determined to be 0 when measuring the average throughput. This embodiment essentially ignores the amount of small databursts when calculating the average throughput.

[0057] The average throughput calculated in the above embodiments may include the average throughput of data that has undergone local rerouting.

[0058] For data that has undergone local rerouting, when the BAP layer of the IAB node selects a route for the BAPPDU corresponding to the data: the egress BH link selected for the BAP PDU is different from the egress BH link indicated in the header of the BAP PDU, and / or the egress BH RLC channel selected for the BAP PDU is different from the first egress BH RLC channel, which is selected based on the ingress BH RLC channel of the BAP PDU.

[0059] Specifically, for data that has undergone local rerouting, when the BAP layer of the IAB node selects a route for the BAP PDU, it does not select the corresponding egress link according to the BAP route ID (Destination ID + Path ID) indicated in the header of the BAP PDU. Instead, the IAB node performs local rerouting and selects another egress link for the BAP PDU.

[0060] The following section will provide a detailed explanation of the specific calculation method for average throughput measurement using multiple examples.

[0061] a) In the uplink direction, the measurement granularity is per BH link per UL.

[0062] The execution node can maintain an independent counter for each BH RLC channel.

[0063] The formula for calculating the average throughput M5 is as follows:

[0064] If ∑ BH RLC CH ∑ ThpTimeUl >0,

[0065] If ∑ BH RLC CH ∑ ThpTimeUl =0, then M5 = 0 [kbit / s].

[0066] In the above formulas, for all buffered data that can be contained in a single initial HARQ process and transmitted as “small data bursts”, ThpTimeUl = 0; otherwise, ThpTimeUl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0067] In the above formulas:

[0068] T1 represents the time point at which the second-to-last data packet in the burst data is successfully received on the BH RLC channel of the BH link.

[0069] T2 represents the time point at which the first data packet in the burst data begins to be sent on the BH RLC channel on the BH link.

[0070] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0071] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0072] b) In the downlink direction, the measurement granularity is per BH link per DL.

[0073] The execution node can maintain an independent counter for each BH RLC channel.

[0074] The formula for calculating the average throughput M5 is as follows:

[0075] If ∑ BH RLC CH ∑ ThpTimeDl >0,

[0076] If ∑ BH RLC CH ∑ ThpTimeDl =0, M5=0[kbit / s].

[0077] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeDl = 0; otherwise, ThpTimeDl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0078] In the above formulas:

[0079] T1 represents the time point at which the second-to-last data packet in the burst data is successfully transmitted on the BH RLC channel on the BH link. The transmission of the burst data includes the available RLC SDUs on the BH RLC channel.

[0080] T2 represents the time point at which an RLC SDU is generated on the BH RLC channel of the BH link and can be used to start sending the first data packet in the burst data after transmission, and there were no RLC SDUs available for transmission in the BH RLC channel before.

[0081] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0082] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0083] c) In the uplink direction, the granularity of the measurement is per BH RLC channel per BH link per UL.

[0084] The execution node can maintain an independent counter for each BH RLC channel.

[0085] The formula for calculating the average throughput M5 is as follows:

[0086] If ∑ ThpTimeUl >0,

[0087] If ∑ ThpTimeUl =0, M5=0[kbit / s].

[0088] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeUl = 0; otherwise, ThpTimeUl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0089] In the above formulas:

[0090] T1 represents the time point at which the second-to-last data packet in a burst of data is successfully received on the BH RLC channel.

[0091] T2 represents the time point at which the first data packet in the burst data begins to be sent on the BH RLC channel.

[0092] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0093] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0094] d) In the downlink direction, the granularity of the measurement is per BH RLC channel per BH link per DL.

[0095] The execution node can maintain an independent counter for each BH RLC channel.

[0096] The formula for calculating the average throughput M5 is as follows:

[0097] If ∑ ThpTimeDl >0,

[0098] If ∑ ThpTimeDl =0, M5=0[kbit / s].

[0099] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeDl = 0; otherwise, ThpTimeDl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0100] In the above formulas:

[0101] T1 represents the time point at which the second-to-last data packet in the burst data is successfully transmitted on the BH RLC channel. The transmission of the burst data includes the available RLC SDUs on the first BH RLC channel.

[0102] T2 represents the time point on the BH RLC channel when an RLC SDU is generated and can be used to start sending the first data packet in the burst data after transmission, and there were no RLC SDUs available for transmission in the first BH RLC channel before.

[0103] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0104] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0105] e) In the upward direction, the granularity measured is per GTP-U TEID (per GTP-U TEID per UL)

[0106] The execution node can maintain an independent counter for each mapped 5QI (5G QoS Identifier).

[0107] The formula for calculating the average throughput M5 is as follows:

[0108] If ∑ UEs ∑ ThpTimeUl >0,

[0109] If ∑ UEs ∑ ThpTimeUl =0, M5=0[kbit / s].

[0110] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeUl = 0; otherwise, ThpTimeUl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0111] In the above formulas:

[0112] T1 indicates the time point at which the second-to-last data packet in a burst of data is successfully received on DRB or GTP-U.

[0113] T2 represents the time point at which the first data packet in a burst of data begins to be sent on the DRB or GTP-U.

[0114] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0115] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0116] f) Downward direction, the granularity of the measurement is per GTP-U TEID (per GTP-U TEID per UL)

[0117] The execution node can maintain an independent counter for each mapped 5QI (5G QoS Identifier).

[0118] The formula for calculating the average throughput M5 is as follows:

[0119] If ∑ UEs ∑ ThpTimeDl >0,

[0120] If ∑ UEs ∑ ThpTimeDl =0, M5=0[kbit / s].

[0121] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeDl = 0; otherwise, ThpTimeDl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0122] In the above formulas:

[0123] T1 represents the time point at which the second-to-last data packet in the burst data is successfully transmitted on the DRB or GTP-U, and the transmission of the burst data includes the available RLC SDUs on the DRB or GTP-U.

[0124] T2 indicates the time point on the DRB or GTP-U when an RLC SDU is generated and can be used to start sending the first data packet in the burst data after transmission, and there were no RLC SDUs available for transmission on the DRB or GTP-U before.

[0125] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0126] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0127] g) In the upward direction, the granularity of the measurement is per IAB node (per IAB per UL).

[0128] The execution node can maintain an independent counter for each BH RLC channel.

[0129] The formula for calculating the average throughput M5 is as follows:

[0130] If ∑ BH link ∑ BH RLC CH ∑ ThpTimeUl >0,

[0131]

[0132] If ∑ BH link ∑ BH RLC CH ∑ ThpTimeUl =0, M5=0[kbit / s].

[0133] In the above formulas, for all buffered data that can be contained in a "small data burst" transmitted in an initial HARQ process, ThpTimeUl = 0; otherwise, ThpTimeUl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0134] In the above formulas:

[0135] T1 represents the time point at which the second-to-last data packet in the burst data is successfully received on the BH RLC channel of the BH link on the IAB node.

[0136] T2 represents the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the BH link on the IAB node.

[0137] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0138] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0139] h) Downward direction, the granularity of the measurement is per IAB node (per IAB per DL).

[0140] The execution node can maintain an independent counter for each BH RLC channel.

[0141] The formula for calculating the average throughput M5 is as follows:

[0142] If ∑BH link ∑ BH RLC CH ∑ ThpTimeDl >0,

[0143]

[0144] If ∑ BH link ∑ BH RLC CH ∑ ThpTimeDl =0, M5=0[kbit / s].

[0145] In the above formulas, for all buffered data that can be contained in a single initial HARQ process and transmitted as “small data bursts”, ThpTimeDl = 0; otherwise, ThpTimeDl = T1 - T2 [ms]. That is, this embodiment ignores the amount of small data bursts when calculating the average throughput.

[0146] In the above formulas:

[0147] T1 represents the time point at which the second-to-last data packet in the burst data is successfully transmitted on the BH RLC channel of the BH link of the IAB node. The transmission of the burst data includes the available RLC SDUs on the BH RLC channel.

[0148] T2 represents the time point at which an RLC SDU is generated on the BH RLC channel of the BH link of the IAB node and can be used to start sending the first data packet in the burst data after transmission, and there were no RLCSDUs available for transmission in the BH RLC channel before.

[0149] ThpTimeUl represents the time for transmitting burst data, excluding data transmitted in the time slot when the buffer is emptied.

[0150] ThpVolUl represents the RLC level capacity of burst data, excluding data transmitted in a time slot when the buffer is emptied.

[0151] Part Two

[0152] In this embodiment, the first parameter includes the data packet delay, which is measured with the following granularity: each BH RLC channel of each BH link.

[0153] In one example, the data packet delay includes at least one of the following: D2.5, D2.6; wherein D2.5 represents the delay experienced by the data packet in the uplink direction from the BAP layer to the RLC layer; D2.6 represents the delay experienced by the data packet in the uplink direction at the RLC layer, or D2.6 represents the delay experienced by the data packet in the uplink direction at both the RLC layer and the BAP layer.

[0154] In this embodiment, the measurement result obtained by the IAB node on the first parameter includes: the IAB node obtains the BH RLC channel delay between two IAB nodes according to one of the following: D2.5+D2.1+D2.6 or D2.5+D2.1; wherein, D2.1 represents the delay experienced by the data packet in the air interface in the uplink direction.

[0155] In this embodiment, D2.1 and D2.6 can be measured by IAB-DU, and D2.5 can be measured by IAB-MT.

[0156] Optionally, D2.5 is obtained based on at least one of the following: the time point at which the uplink BAP Service Data Unit (SDU) arrives at the BAP Upper Layer Service Access Point (SAP), the time point at which the uplink MAC PDU containing the first part of the data of the uplink BAP SDU is scheduled for transmission, and the number of uplink BAP SDUs arriving within the time interval T.

[0157] In the case where D2.6 represents the delay experienced by a data packet in the uplink direction at the RLC layer, D2.6 is obtained based on at least one of the following: the time point at which the uplink RLC SDU is sent to the upper layer SAP or BAP, the time point at which the uplink RLC PDU containing the first part of the data of the RLC SDU is received, and the number of the uplink RLC SDUs arriving within the time interval T.

[0158] In the case where D2.6 represents the delay experienced by data packets in the uplink direction at the RLC and BAP layers, D2.6 is obtained based on at least one of the following: the time point at which the uplink BAP SDU is sent to the upper-layer SAP, the time point at which the uplink RLC PDU containing the first part of the data of the uplink RLC SDU is received, and the number of said uplink RLC SDUs arriving within the time interval T.

[0159] In one example, the data packet delay includes at least one of the following: D5, D6; wherein D5 represents the delay experienced by the data packet in the downlink direction from the BAP layer to the RLC layer; and D6 represents the delay experienced by the data packet in the downlink direction from the MAC layer or the RLC layer to the BAP layer.

[0160] In this embodiment, the measurement result obtained by the IAB node on the first parameter includes: the IAB node obtains the BH RLC channel delay between two IAB nodes according to one of the following: D5+D1+D6 or D5+D1; where D1 represents the delay experienced by the data packet in the downlink direction at the air interface.

[0161] Optionally, D5 is obtained based on at least one of the following: the time point when the downlink BAP SDU arrives at the SAP above the BAP, the time point when the last part of the RLC SDU corresponding to the downlink BAP SDU is scheduled and sent, and the number of downlink BAP SDUs arriving within the time interval T.

[0162] D6 is obtained based on at least one of the following: the time point when the downlink MAC SDU arrives at the MAC layer or the time point when the downlink RLC SDU arrives at the RLC layer, the time point when the downlink MAC SDU or the downlink RLC SDU is sent to the upper-layer SAP, and the number of downlink MAC SDUs or downlink RLC SDUs arriving within the time interval T.

[0163] The following section will provide a detailed explanation of the specific calculation method for data packet latency using multiple examples.

[0164] a) In the uplink direction, the measurement granularity is per BH RLC channel per BH link per UL.

[0165] This embodiment introduces BAP layer-related delay measurements D2.5 and D2.6, specifically as follows: Figure 3 As shown.

[0166] Define the BH RLC channel delay (i.e., BH RLC channel per hop) between IAB nodes as D2.5 + D2.1 + D2.6 or D2.5 + D2.1, where D2.6 is an optional measurement.

[0167] D2.1 represents the latency experienced by the data packet in the uplink direction over the air interface.

[0168] The formula for calculating D2.5:

[0169]

[0170] In this formula, M(T,BH RLC CH ID) represents the packet delay experienced in the uplink direction from the BAP layer to the RLC layer, and the delay result is the average value calculated over the time interval T.

[0171] tSched(i, BH RLC CH ID) represents the time when the i-th uplink BAPSDU arrives at the Service Access Point SAP (SAP) of the BAP.

[0172] tSucc(i, BH RLC CH ID) indicates that "the k-th uplink MAC PDU containing the first part of the data of the i-th uplink BAP SDU is scheduled for transmission at the time point".

[0173] I(T) represents the number of uplink BAP SDUs arriving within time interval T.

[0174] i represents an uplink BAP SDU that arrives at the BAP layer within time interval T.

[0175] T represents the measurement time interval.

[0176] BH RLC CH ID represents the ID of the measured BH RLC channel.

[0177] The formula for calculating D2.6:

[0178] Option 1: D2.6 only includes the latency of the RLC layer.

[0179]

[0180] In this formula, M(T, BH RLC CH ID) represents the packet delay experienced in the uplink direction from the RLC layer to the BAP layer, and the delay result is the average value calculated over time interval T.

[0181] tSent(i,BH RLC CH ID) represents the time point at which the i-th uplink RLC SDU is sent to the upper-layer SAP or BAP.

[0182] tReceiv(i, BH RLC CH ID contains the time point at which the uplink RLC PDU containing the first part of the data of the RLC SDU is received.

[0183] I(T) represents the number of upstream RLC SDUs.

[0184] i represents an uplink RLC SDU received by the RLC layer within time interval T.

[0185] T represents the measurement time interval.

[0186] BHRLCCHID represents the ID of the measured BH RLC channel.

[0187] Option 2: D2.6 includes delay of BAP+RLC layer

[0188]

[0189] In this formula, M(T,BH RLC CH ID) represents the packet delay experienced in the uplink direction from the RLC layer to the BAP layer, and the delay result is the average value calculated with time interval T.

[0190] tSent(i, BHRLCCHID) represents the time point at which the i-th uplink BAP SDU is sent to the upper-layer SAP.

[0191] tReceiv(i,BHRLCCHID) represents the time point at which the uplink RLC PDU containing the first part of the RLC SDU data is received.

[0192] I(T) represents the number of upstream RLC SDUs.

[0193] i represents an uplink RLC SDU received by the RLC layer within time interval T.

[0194] T represents the measurement time interval.

[0195] BHRLCCHID represents the ID of the measured BH RLC channel.

[0196] b) In the downlink direction, the granularity of the measurement is per BH RLC channel per BH link per DL.

[0197] This embodiment introduces BAP layer-related delay measurements D5 and D6, specifically as follows: Figure 4 As shown.

[0198] Define the BH RLC channel delay (i.e., BH RLC channel per hop) between IAB nodes as D5+D1+D6 or D5+D1, where D6 is an optional measurement.

[0199] D1 represents the latency experienced by the data packet in the downlink direction over the air interface.

[0200] The formula for calculating D5:

[0201]

[0202] In this formula, M(T,BH RLC CH ID) represents the packet delay experienced in the downlink direction from the BAP layer to the RLC layer, and the delay result is the average value calculated over the time interval T.

[0203] tReceiv(i,BH RLC CH ID) represents the time point at which the downlink BAP SDUi arrives at the upper layer SAP of the BAP.

[0204] tSent(i,BH RLC CH ID) represents the time point at which the last part of the RLC SDU corresponding to the downlink BAP SDU is scheduled and sent.

[0205] I(T) represents the number of downlink BAP SDUs.

[0206] i represents a downlink BAP SDU received by the BAP layer within time interval T.

[0207] T represents the measurement time interval.

[0208] BH RLC CH ID represents the ID of the measured BH RLC channel.

[0209] The formula for calculating D6:

[0210]

[0211] M(T,BH RLC CH ID) represents the data packet delay experienced in the downlink direction from the MAC layer or RLC layer to the BAP layer. The delay result is the average value calculated over the time interval T.

[0212] tReceiv(i,BH RLC CH ID) represents the time point when the downlink MAC SDUi arrives at the MAC layer or the time point when the downlink RLCSDUi arrives at the RLC layer.

[0213] tSent(i,BH RLC CH ID) represents the time point at which the downlink MAC SDU or the downlink RLC SDU is sent to the upper-layer SAP.

[0214] I(T) represents the number of downlink MAC SDUs or downlink RLC SDUs that arrive within time interval T.

[0215] i represents a downlink MAC SDU received by the MAC layer or a downlink RLCSDU received by the RLC layer within a time interval T.

[0216] T represents the measurement time interval.

[0217] BH RLC CH ID represents the ID of the measured BH RLC channel.

[0218] Part Three

[0219] In this embodiment, the first parameter includes the packet loss rate, which is measured at at least one of the following granularities: 1) per BH link, 2) per BH RLC channel of each BH link, and 3) per IAB node.

[0220] In a specific example, the uplink packet loss rate measurement is performed by the IAB Distributed Unit (IAB-DU), while the downlink packet loss rate measurement is performed by the IAB Mobile Terminal (IAB-MT).

[0221] In this embodiment, the measurement result obtained by the IAB node on the first parameter includes at least one of the following:

[0222] 1) When the measurement granularity is each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel on the second BH link during the fifth time period, and the total number of data packets transmitted on the BH RLC channel on the second BH link during the fifth time period.

[0223] The packet loss rate can be measured independently for uplink and downlink.

[0224] Optionally, the BH RLC channel on the second BH link includes at least one of the following: an uplink ingress BH RLC channel on the second BH link, and a downlink egress BH RLC channel on the second BH link.

[0225] 2) When the measurement granularity is each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses of the second BH RLC channel in the sixth time period, and the total number of data packets transmitted by the second BH RLC channel in the sixth time period.

[0226] The packet loss rate can be measured independently for uplink and downlink.

[0227] Optionally, the second BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel and a downlink egress BH RLC channel.

[0228] 3) When the measurement granularity is each IAB node, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the IAB node's BH link during the seventh time period, and the total number of data packets transmitted on the BH RLC channel of the IAB node's BH link during the seventh time period.

[0229] The packet loss rate can be measured independently for uplink and downlink.

[0230] Optionally, the BH RLC channel on the BH link of the IAB node includes at least one of the following: an uplink ingress BH RLC channel on the BH link of the IAB node, and a downlink egress BH RLC channel on the BH link of the IAB node.

[0231] The following section will provide a detailed explanation of the specific calculation method for packet loss rate using multiple examples.

[0232] a) In the uplink direction, the granularity of the measurement is per BH RLC channel per BH link per UL.

[0233] The formula for calculating packet loss rate:

[0234]

[0235] In this formula, M(T,BH RLC CH ID) represents the packet loss rate.

[0236] Dloss(T,BH RLC CH ID) represents the number of uplink data packets sent on BH RLC CH ID within time interval T but not successfully received by the peer.

[0237] N(T,BH RLC CH ID) represents the number of uplink data packets sent on BH RLC CH ID and successfully received by the peer within time interval T.

[0238] T represents the measurement time interval.

[0239] BH RLC CH ID represents the ID of the measured BH RLC channel.

[0240] b) In the downlink direction, the granularity of the measurement is per BH RLC channel per BH link per DL.

[0241] The formula for calculating packet loss rate:

[0242]

[0243] In this formula, M(T,BHRLCCHID) represents the packet loss rate.

[0244] Dloss(T,BHRLCCHID) represents the number of downlink data packets sent on BHRLCCHID within time interval T but not successfully received by the peer.

[0245] N(T,BHRLCCHID) represents the number of downlink data packets sent on BHRLCCHID and successfully received by the peer within time interval T.

[0246] T represents the measurement time interval.

[0247] BHRLCCHID represents the ID of the measured BH RLC channel.

[0248] c) In the uplink direction, the measurement granularity is per BH link per UL.

[0249] The formula for calculating packet loss rate:

[0250]

[0251] The meaning of each parameter in this formula can be found in the description in a).

[0252] d) In the downlink direction, the measurement granularity is per BH link per DL.

[0253] The formula for calculating packet loss rate:

[0254]

[0255] The meaning of each parameter in this formula can be found in the description in b).

[0256] e) In the uplink direction, the granularity of the measurement is per IAB node (Per IAB-node per UL).

[0257] The formula for calculating packet loss rate:

[0258]

[0259] The meaning of each parameter in this formula can be found in the description in a).

[0260] f) Downlink direction, the granularity of measurement is per IAB node (Per IAB-node per DL).

[0261] The formula for calculating packet loss rate:

[0262]

[0263] The meaning of each parameter in this formula can be found in the description in b).

[0264] It should be noted that the measurement method provided in this application embodiment can be executed by an IAB node, or by a control module within the IAB node for executing the measurement method. This application embodiment uses the execution of the measurement method by an IAB node as an example to illustrate the IAB node provided in this application embodiment.

[0265] Figure 5 This is a structural diagram of an IAB node according to an embodiment of this application, as shown below. Figure 5 As shown, IAB node 500 includes the following modules.

[0266] The measurement module 502 can be used to measure a first parameter to obtain a measurement result. The first parameter includes a layer 2 parameter, which includes at least one of the following: average throughput, data packet latency, and data packet loss rate.

[0267] In the embodiments of this application, the IAB node measures at least one of the average throughput, packet latency, and packet loss rate to obtain the measurement results, thereby enabling the IAB node to support real-time MDT measurement reporting, realize OAM's monitoring of performance indicators, or QoS verification or QoS monitoring of MDT, and improve communication efficiency.

[0268] Optionally, as an embodiment, the IAB node includes at least one of the following: an IAB mobile terminal, an IAB distribution unit, an IAB host distribution unit, and an IAB host integration unit.

[0269] Optionally, as an embodiment, the first parameter includes the average throughput, which is measured at at least one of the following granularities: per BH link, per BH RLC channel of each BH link, per GTP-U TEID, and per IAB node.

[0270] Optionally, as an embodiment, the measurement module 502 is used for at least one of the following:

[0271] 1) When the granularity of the measurement includes each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the BH RLC channel on the first BH link during a first time period.

[0272] 2) When the granularity of the measurement includes each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the first BH RLC channel during the second time period, and the second time period.

[0273] 3) When the granularity of the measurement includes each GTP-U TEID, the measurement result is obtained according to the quotient of the following two: the total throughput of data transmitted on the data radio bearer DRB or GTP-U of the first terminal UE during the third time period, wherein the first UE is a UE that uses the IAB node as an access node.

[0274] 4) When the granularity of the measurement includes each IAB node, the measurement result is obtained by the quotient of the following two: the total throughput of the BH RLC channel on the BH link of the IAB node during the fourth time period.

[0275] Optionally, as an embodiment, the BH RLC channel on the first BH link includes at least one of the following: an uplink ingress BH RLC channel on the first BH link, and a downlink egress BH RLC channel on the first BH link; the first BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel, and a downlink egress BH RLC channel; the BH RLC channel on the BH link of the IAB node includes at least one of the following: an uplink ingress BH RLC channel on the BH link of the IAB node, and a downlink egress BH RLC channel on the BH link of the IAB node.

[0276] Alternatively, as an example, the average throughput is measured independently for uplink and downlink.

[0277] Optionally, as an embodiment, in the uplink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully received on the BH RLC channel of the first BH link; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the first BH link. In the downlink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the first BH link, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDUs on the BH RLC channel of the first BH link are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the BH RLC channel.

[0278] Optionally, as an embodiment, in the uplink direction, the second time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the first BH RLC channel; and the time point when the first data packet in the burst data begins to be transmitted on the first BH RLC channel. In the downlink direction, the second time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the first BH RLC channel, wherein the transmission of the burst data includes available RLC SDUs on the first BH RLC channel; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDUs on the first BH RLC channel are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the first BH RLC channel.

[0279] Optionally, as an embodiment, in the uplink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted on the DRB or GTP-U. In the downlink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the DRB or GTP-U, wherein the transmission of the burst data includes available RLC SDUs on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDUs on the DRB or GTP-U are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the DRB or GTP-U.

[0280] Optionally, as an embodiment, in the uplink direction, the fourth time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the BH RLC channel on the BH link of the IAB node; and the time point when the first data packet in the burst data begins to be transmitted on the BH RLC channel on the BH link of the IAB node. In the downlink direction, the fourth time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel on the BH link of the IAB node, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point when the first data packet in the burst data begins to be transmitted on the BH RLC channel on the BH link of the IAB node after the RLC SDU is generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the BH RLC channel.

[0281] Optionally, as an embodiment, for burst data that can be included in an initial HARQ process for transmission, the transmission time corresponding to the burst data is determined to be 0 when measuring the average throughput.

[0282] Optionally, as an example, the average throughput includes the average throughput of data that has undergone local rerouting.

[0283] Optionally, as an embodiment, when the Backhaul Adaptation Protocol (BAP) layer of the IAB node performs routing selection for the BAPPDU corresponding to the data, it corresponds to at least one of the following: the egress BH link selected for the BAP PDU is different from the egress BH link indicated in the header of the BAP PDU; the egress BH RLC channel selected for the BAP PDU is different from the first egress BH RLC channel, wherein the first egress BH RLC channel is selected based on the ingress BH RLC channel of the BAP PDU.

[0284] Optionally, as an embodiment, the first parameter includes the data packet delay, which is measured at the following granularity: each BH RLC channel of each BH link.

[0285] Optionally, as an embodiment, the data packet delay includes at least one of the following: D2.5, D2.6; wherein, D2.5 represents the delay experienced by the data packet from the BAP layer to the RLC layer in the uplink direction; D2.6 represents the delay experienced by the data packet at the RLC layer in the uplink direction, or D2.6 represents the delay experienced by the data packet at both the RLC layer and the BAP layer in the uplink direction.

[0286] Optionally, as an embodiment, the measurement module 502 is used to obtain the BH RLC channel delay between two IAB nodes according to one of the following: D2.5+D2.1+D2.6 or D2.5+D2.1; wherein, D2.1 represents the delay experienced by the data packet in the uplink direction on the air interface.

[0287] Optionally, as an embodiment, D2.5 is obtained based on at least one of the following: the time point when the uplink BAP Service Data Unit (SDU) arrives at the BAP upper-layer service access point (SAP), the time point when the uplink MAC PDU containing the first part of the data of the uplink BAP SDU is scheduled for transmission, and the number of uplink BAP SDUs arriving within the time interval T; when D2.6 represents the delay experienced by data packets in the uplink direction at the RLC layer, D2.6 is obtained based on at least one of the following: the time point when the uplink RLC SDU is sent to the upper-layer SAP or BAP, the time point when the uplink RLCPDU containing the first part of the data of the RLC SDU is received, and the number of uplink RLC SDUs arriving within the time interval T; when D2.6 represents the delay experienced by data packets in the uplink direction at the RLC layer and BAP layer, D2.6 is obtained based on at least one of the following: the time point when the uplink BAPSDU is sent to the upper-layer SAP, the time point when the uplink RLC PDU containing the first part of the data of the uplink RLC SDU is received, and the number of uplink RLC PDUs arriving within the time interval T. The number of SDUs.

[0288] Optionally, as an embodiment, the data packet delay includes at least one of the following: D5, D6; wherein, D5 represents the delay experienced by the data packet from the BAP layer to the RLC layer in the downlink direction; and D6 represents the delay experienced by the data packet from the MAC layer or the RLC layer to the BAP layer in the downlink direction.

[0289] Optionally, as an embodiment, the measurement module 502 is used to obtain the BH RLC channel delay between two IAB nodes according to one of the following: D5+D1+D6 or D5+D1; where D1 represents the delay experienced by the data packet in the downlink direction at the air interface.

[0290] Optionally, as an embodiment, D5 is obtained based on at least one of the following: the time point when the downlink BAP SDU arrives at the SAP above the BAP, the time point when the last part of the RLC SDU corresponding to the downlink BAP SDU is scheduled and sent, and the number of downlink BAP SDUs arriving within the time interval T; D6 is obtained based on at least one of the following: the time point when the downlink MAC SDU arrives at the MAC layer or the time point when the downlink RLC SDU arrives at the RLC layer, the time point when the downlink MAC SDU or the downlink RLC SDU is sent to the SAP above the BAP, and the number of downlink MAC SDUs or downlink RLC SDUs arriving within the time interval T.

[0291] Optionally, as an embodiment, the first parameter includes the packet loss rate, which is measured at at least one of the following granularities: per BH link, per BH RLC channel of each BH link, and per IAB node.

[0292] Optionally, as an embodiment, the measurement module 502 is used for at least one of the following:

[0293] 1) When the measurement granularity is each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel on the second BH link during the fifth time period, and the total number of data packets transmitted on the BH RLC channel on the second BH link during the fifth time period.

[0294] 2) When the measurement granularity is each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses of the second BH RLC channel in the sixth time period, and the total number of data packets transmitted by the second BH RLC channel in the sixth time period.

[0295] 3) When the measurement granularity is each IAB node, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the IAB node's BH link during the seventh time period, and the total number of data packets transmitted on the BH RLC channel of the IAB node's BH link during the seventh time period.

[0296] Optionally, as an embodiment, the BH RLC channel on the second BH link includes at least one of the following: an uplink ingress BH RLC channel on the second BH link, and a downlink egress BH RLC channel on the second BH link; the second BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel, and a downlink egress BH RLC channel; the BH RLC channel on the BH link of the IAB node includes at least one of the following: an uplink ingress BH RLC channel on the BH link of the IAB node, and a downlink egress BH RLC channel on the BH link of the IAB node.

[0297] Optionally, as an example, the packet loss rate is measured independently for uplink and downlink.

[0298] According to the embodiments of this application, the IAB node 500 can refer to the process of the method 200 corresponding to the embodiments of this application. Furthermore, each unit / module in the IAB node 500 and the other operations and / or functions mentioned above are for implementing the corresponding processes in the method 200 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0299] The IAB node provided in this application embodiment can achieve... Figure 2 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0300] Optional, such as Figure 6 As shown, this application embodiment also provides a communication device 600, including a processor 601, a memory 602, and a program or instructions stored in the memory 602 and executable on the processor 601. For example, when the communication device 600 is an IAB node, the program or instructions executed by the processor 601 implement the various processes of the above measurement method embodiment and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0301] This application also provides a network-side device, including a processor and a communication interface. The processor is used to measure a first parameter to obtain a measurement result. The first parameter includes a Layer 2 parameter, which includes at least one of the following: average throughput, data packet latency, and data packet loss rate. This network-side device embodiment corresponds to the above-described IAB node method embodiment. All implementation processes and methods of the above method embodiments can be applied to this network-side device embodiment and achieve the same technical effects.

[0302] Specifically, embodiments of this application also provide a network-side device, which may be an IAB node. For example... Figure 7 As shown, the network-side device 700 includes an antenna 71, a radio frequency (RF) device 72, and a baseband device 73. The antenna 71 is connected to the RF device 72. In the uplink direction, the RF device 72 receives information through the antenna 71 and transmits the received information to the baseband device 73 for processing. In the downlink direction, the baseband device 73 processes the information to be transmitted and sends it to the RF device 72. The RF device 72 processes the received information and transmits it through the antenna 71.

[0303] The aforementioned frequency band processing device can be located in the baseband device 73. The method executed by the network-side device in the above embodiments can be implemented in the baseband device 73, which includes a processor 74 and a memory 75.

[0304] The baseband device 73 may include, for example, at least one baseband board on which multiple chips are disposed, such as... Figure 7 As shown, one of the chips, for example, is a processor 74, which is connected to a memory 75 to call the program in the memory 75 and execute the network-side device operations shown in the above method embodiments.

[0305] The baseband device 73 may also include a network interface 76 for exchanging information with the radio frequency device 72, such as a common public radio interface (CPRI).

[0306] Specifically, the network-side device in this application embodiment further includes: instructions or programs stored in memory 75 and executable on processor 74, wherein processor 74 calls the instructions or programs in memory 75 to execute. Figure 5 The methods executed by each module shown achieve the same technical effect, and to avoid repetition, they will not be described in detail here.

[0307] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described measurement method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

[0308] The processor may be the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0309] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above measurement method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0310] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0311] This application also provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement the various processes of the above measurement method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0312] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0313] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the methods described in the various embodiments of this application.

[0314] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A measurement method, characterized in that, include: The integrated access and backhaul IAB nodes measure the first parameter to obtain the real-time MDT measurement result. The first parameter includes layer 2 parameters, which include at least one of the following: average throughput and packet loss rate. The average throughput is measured at at least one of the following granularities: Each backhaul BH link, Each BH radio link controls the RLC channel of each BH link. Each General Packet Radio Service Tunneling Protocol - User Plane Tunnel Endpoint Identifier (GTP-UTEID) and Each IAB node; The packet loss rate is measured at at least one of the following granularities: Each BH link, Each BH RLC channel of each BH link, and Each IAB node.

2. The method according to claim 1, characterized in that, The IAB node includes at least one of the following: an IAB mobile terminal, an IAB distribution unit, an IAB host distribution unit, and an IAB host integration unit.

3. The method according to claim 1, characterized in that, The measurement results of the instantaneous MDT obtained by the IAB node measuring the first parameter include at least one of the following: When the measurement granularity includes each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the BH RLC channels on the first BH link within a first time period; When the measurement granularity includes each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the first BH RLC channel during the second time period; When the granularity of the measurement includes each GTP-U TEID, the measurement result is obtained by the quotient of the following two: the total throughput of data transmitted on the Data Radio Bearer (DRB) or GTP-U of the first terminal UE during the third time period, wherein the first UE is a UE that uses the IAB node as an access node. as well as When the measurement granularity includes each IAB node, the measurement result is obtained by the quotient of the following two factors: the total throughput of the BH RLC channels on the BH links of the IAB nodes during the fourth time period.

4. The method according to claim 3, characterized in that, The BH RLC channel on the first BH link includes at least one of the following: the uplink ingress BH RLC channel on the first BH link, and the downlink egress BH RLC channel on the first BH link; The first BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel and a downlink egress BH RLC channel; The BH RLC channel on the BH link of the IAB node includes at least one of the following: the uplink ingress BH RLC channel on the BH link of the IAB node, and the downlink egress BH RLC channel on the BH link of the IAB node.

5. The method according to claim 3, characterized in that, The average throughput is measured independently for both uplink and downlink.

6. The method according to claim 5, characterized in that, In the uplink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully received on the BH RLC channel of the first BH link; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the first BH link. In the downlink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the first BH link, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDUs on the BH RLC channel of the first BH link are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the BH RLC channel. In the uplink direction, the second time period is related to the following two: the time when the penultimate data packet in the burst data is successfully received on the first BH RLC channel; and the time when the first data packet in the burst data begins to be transmitted on the first BH RLC channel. In the downlink direction, the second time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the first BH RLC channel, wherein the transmission of the burst data includes available RLC SDUs on the first BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDUs on the first BH RLC channel are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the first BH RLC channel. In the uplink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted on the DRB or GTP-U. In the downlink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the DRB or GTP-U, the transmission of the burst data including available RLC SDUs on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDUs on the DRB or GTP-U are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the DRB or GTP-U. In the uplink direction, the fourth time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the BH RLC channel on the BH link of the IAB node; and the time point when the first data packet in the burst data begins to be transmitted on the BHRLC channel on the BH link of the IAB node. In the downlink direction, the fourth time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the BH link of the IAB node, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the BH link of the IAB node after the RLC SDU has been generated and is available for transmission, wherein there were no previously available RLC SDUs for transmission on the BH RLC channel.

7. The method according to claim 3, characterized in that, For bursts of buffered data that can be included in an initial Hybrid Automatic Repeat Request (HARQ) process for transmission, the transmission time corresponding to the bursts is determined to be 0 when measuring the average throughput.

8. The method according to claim 3, characterized in that, The average throughput includes the average throughput of data that has undergone local rerouting.

9. The method according to claim 8, characterized in that, When the Backhaul Adaptation Protocol (BAP) layer of the IAB node performs routing selection for the BAP Protocol Data Unit (PDU) corresponding to the data, it corresponds to at least one of the following: The egress BH link selected for the BAP PDU is different from the egress BH link indicated in the header of the BAP PDU; The egress BH RLC channel selected for the BAP PDU is different from the first egress BH RLC channel, which is selected based on the ingress BH RLC channel of the BAP PDU.

10. The method according to claim 1 or 2, characterized in that, The first parameter also includes data packet latency, which is measured with the following granularity: Each BH RLC channel of each BH link.

11. The method according to claim 10, characterized in that, The data packet delay includes at least one of the following: D2.5, D2.6; Where D2.5 represents the latency experienced by a data packet in the uplink direction from the BAP layer to the RLC layer; D2.6 represents the latency experienced by a data packet in the uplink direction at the RLC layer, or D2.6 represents the latency experienced by a data packet in the uplink direction at both the RLC and BAP layers.

12. The method according to claim 11, characterized in that, The measurement result obtained by the IAB node for the first parameter includes: the IAB node obtains the BH RLC channel delay between two IAB nodes according to one of the following: D2.5+D2.1+D2.6 or D2.5+D2.1; Where D2.1 represents the latency experienced by the data packet in the air interface in the uplink direction.

13. The method according to claim 11, characterized in that, D2.5 is obtained based on at least one of the following: the time point at which the uplink BAP Service Data Unit (SDU) arrives at the BAP Upper Layer Service Access Point (SAP), the time point at which the uplink MAC PDU containing the first part of the data of the uplink BAP SDU is scheduled for transmission, and the number of uplink BAP SDUs arriving within the time interval T. In the case where D2.6 represents the delay experienced by a data packet in the uplink direction at the RLC layer, D2.6 is obtained based on at least one of the following: the time point at which the uplink RLC SDU is sent to the upper layer SAP or BAP, the time point at which the uplink RLC PDU containing the first part of the data of the RLC SDU is received, and the number of the uplink RLC SDUs arriving within the time interval T. In the case where D2.6 represents the delay experienced by data packets in the uplink direction at the RLC and BAP layers, D2.6 is obtained based on at least one of the following: the time point at which the uplink BAP SDU is sent to the upper-layer SAP, the time point at which the uplink RLC PDU containing the first part of the data of the uplink RLC SDU is received, and the number of said uplink RLC SDUs arriving within the time interval T.

14. The method according to claim 11, characterized in that, The data packet delay includes at least one of the following: D5, D6; Where D5 represents the latency experienced by a data packet in the downlink direction from the BAP layer to the RLC layer; D6 represents the latency experienced by a data packet in the downlink direction from the MAC layer or RLC layer to the BAP layer.

15. The method according to claim 14, characterized in that, The measurement results of the instantaneous MDT obtained by the IAB node for measuring the first parameter include: the IAB node obtains the BH RLC channel delay between two IAB nodes according to one of the following: D5+D1+D6 or D5+D1. Where D1 represents the latency experienced by the data packet in the downlink direction over the air interface.

16. The method according to claim 14, characterized in that, D5 is obtained based on at least one of the following: the time point when the downlink BAP SDU arrives at the SAP above the BAP, the time point when the last part of the RLC SDU corresponding to the downlink BAP SDU is scheduled and sent, and the number of downlink BAP SDUs arriving within the time interval T. D6 is obtained based on at least one of the following: the time point when the downlink MAC SDU arrives at the MAC layer or the time point when the downlink RLC SDU arrives at the RLC layer, the time point when the downlink MAC SDU or the downlink RLC SDU is sent to the upper-layer SAP, and the number of downlink MAC SDUs or downlink RLC SDUs arriving within the time interval T.

17. The method according to claim 1, characterized in that, The measurement result obtained by the IAB node for the first parameter includes at least one of the following: When the measurement granularity is each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the second BH link during the fifth time period, and the total number of data packets transmitted on the BH RLC channel of the second BH link during the fifth time period. When the measurement granularity is each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses of the second BH RLC channel during the sixth time period, and the total number of data packets transmitted by the second BH RLC channel during the sixth time period. as well as When the measurement granularity is each IAB node, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the IAB node's BH link during the seventh time period, and the total number of data packets transmitted on the BH RLC channel of the IAB node's BH link during the seventh time period.

18. The method according to claim 17, characterized in that, The BH RLC channel on the second BH link includes at least one of the following: the uplink ingress BH RLC channel on the second BH link, and the downlink egress BH RLC channel on the second BH link; The second BH RLC channel includes at least one of the following: an uplink ingress BH RLC channel and a downlink egress BH RLC channel; The BH RLC channel on the BH link of the IAB node includes at least one of the following: the uplink ingress BH RLC channel on the BH link of the IAB node, and the downlink egress BH RLC channel on the BH link of the IAB node.

19. The method according to claim 17, characterized in that, The packet loss rate is measured independently for uplink and downlink.

20. An IAB node, characterized in that, include: The measurement module is used to measure the first parameter to obtain the measurement result of the real-time MDT. The first parameter includes layer 2 parameters, which include at least one of the following: average throughput and packet loss rate. Each BH link, Each BH radio link controls the RLC channel of each BH link. Each General Packet Radio Service Tunneling Protocol - User Plane Tunnel Endpoint Identifier (GTP-UTEID) and Each IAB node; The packet loss rate is measured at at least one of the following granularities: Each BH link, Each BH RLC channel of each BH link, and Each IAB node.

21. The IAB node according to claim 20, characterized in that, The IAB node includes at least one of the following: an IAB mobile terminal, an IAB distribution unit, an IAB host distribution unit, and an IAB host integration unit.

22. The IAB node according to claim 20, characterized in that, The measurement module is used for at least one of the following: When the measurement granularity includes each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the BH RLC channels on the first BH link within a first time period; When the measurement granularity includes each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total throughput of the first BH RLC channel during the second time period; When the granularity of the measurement includes each GTP-U TEID, the measurement result is obtained by the quotient of the following two: the total throughput of data transmitted on the Data Radio Bearer (DRB) or GTP-U of the first terminal UE during the third time period, wherein the first UE is a UE that uses the IAB node as an access node. as well as When the measurement granularity includes each IAB node, the measurement result is obtained by the quotient of the following two factors: the total throughput of the BH RLC channels on the BH links of the IAB nodes during the fourth time period.

23. The IAB node according to claim 22, characterized in that, The average throughput is measured independently for both uplink and downlink.

24. The IAB node according to claim 23, characterized in that, In the uplink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully received on the BH RLC channel of the first BH link; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the first BH link. In the downlink direction, the first time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the first BH link, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDUs on the BH RLC channel of the first BH link are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the BH RLC channel. In the uplink direction, the second time period is related to the following two: the time when the penultimate data packet in the burst data is successfully received on the first BH RLC channel; and the time when the first data packet in the burst data begins to be transmitted on the first BH RLC channel. In the downlink direction, the second time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the first BH RLC channel, wherein the transmission of the burst data includes available RLC SDUs on the first BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted after the RLC SDUs on the first BH RLC channel are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the first BH RLC channel. In the uplink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted on the DRB or GTP-U. In the downlink direction, the third time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully transmitted on the DRB or GTP-U, the transmission of the burst data including available RLC SDUs on the DRB or GTP-U; and the time point when the first data packet in the burst data begins to be transmitted after the RLC SDUs on the DRB or GTP-U are generated and available for transmission, wherein there were previously no RLC SDUs available for transmission on the DRB or GTP-U. In the uplink direction, the fourth time period is related to the following two: the time point when the penultimate data packet in the burst data is successfully received on the BH RLC channel on the BH link of the IAB node; and the time point when the first data packet in the burst data begins to be transmitted on the BHRLC channel on the BH link of the IAB node. In the downlink direction, the fourth time period is related to the following two: the time point at which the penultimate data packet in the burst data is successfully transmitted on the BH RLC channel of the BH link of the IAB node, wherein the transmission of the burst data includes available RLC SDUs on the BH RLC channel; and the time point at which the first data packet in the burst data begins to be transmitted on the BH RLC channel of the BH link of the IAB node after the RLC SDU has been generated and is available for transmission, wherein there were no previously available RLC SDUs for transmission on the BH RLC channel.

25. The IAB node according to claim 23, characterized in that, For burst data that can be included in an initial HARQ process for transmission, the transmission time corresponding to the burst data is determined to be 0 when measuring the average throughput.

26. The IAB node according to claim 20 or 21, characterized in that, The first parameter also includes data packet latency, which is measured with the following granularity: Each BH RLC channel of each BH link.

27. The IAB node according to claim 26, characterized in that, The data packet delay includes at least one of the following: D2.5, D2.6; Where D2.5 represents the latency experienced by a data packet in the uplink direction from the BAP layer to the RLC layer; D2.6 represents the latency experienced by a data packet in the uplink direction at the RLC layer, or D2.6 represents the latency experienced by a data packet in the uplink direction at both the RLC and BAP layers.

28. The IAB node according to claim 27, characterized in that, The measurement module is used to obtain the BH RLC channel delay between two IAB nodes according to one of the following: D2.5+D2.1+D2.6 or D2.5+D2.1; Where D2.1 represents the latency experienced by the data packet in the air interface in the uplink direction.

29. The IAB node according to claim 27, characterized in that, D2.5 is obtained based on at least one of the following: the time point at which the uplink BAP Service Data Unit (SDU) arrives at the BAP Upper Layer Service Access Point (SAP), the time point at which the uplink MAC PDU containing the first part of the data of the uplink BAP SDU is scheduled for transmission, and the number of uplink BAP SDUs arriving within the time interval T. In the case where D2.6 represents the delay experienced by a data packet in the uplink direction at the RLC layer, D2.6 is obtained based on at least one of the following: the time point at which the uplink RLC SDU is sent to the upper layer SAP or BAP, the time point at which the uplink RLC PDU containing the first part of the data of the RLC SDU is received, and the number of the uplink RLC SDUs arriving within the time interval T. In the case where D2.6 represents the delay experienced by data packets in the uplink direction at the RLC and BAP layers, D2.6 is obtained based on at least one of the following: the time point at which the uplink BAP SDU is sent to the upper-layer SAP, the time point at which the uplink RLC PDU containing the first part of the data of the uplink RLC SDU is received, and the number of said uplink RLC SDUs arriving within the time interval T.

30. The IAB node according to claim 26, characterized in that, The data packet delay includes at least one of the following: D5, D6; Where D5 represents the latency experienced by a data packet in the downlink direction from the BAP layer to the RLC layer; D6 represents the latency experienced by a data packet in the downlink direction from the MAC layer or RLC layer to the BAP layer.

31. The IAB node according to claim 30, characterized in that, The measurement module is used to obtain the BH RLC channel delay between two IAB nodes according to one of the following: D5+D1+D6 or D5+D1. Where D1 represents the latency experienced by the data packet in the downlink direction over the air interface.

32. The IAB node according to claim 30, characterized in that, D5 is obtained based on at least one of the following: the time point when the downlink BAP SDU arrives at the SAP above the BAP, the time point when the last part of the RLC SDU corresponding to the downlink BAP SDU is scheduled and sent, and the number of downlink BAP SDUs arriving within the time interval T. D6 is obtained based on at least one of the following: the time point when the downlink MAC SDU arrives at the MAC layer or the time point when the downlink RLC SDU arrives at the RLC layer, the time point when the downlink MAC SDU or the downlink RLC SDU is sent to the upper-layer SAP, and the number of downlink MAC SDUs or downlink RLC SDUs arriving within the time interval T.

33. The IAB node according to claim 20, characterized in that, The measurement module is used for at least one of the following: When the measurement granularity is each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the second BH link during the fifth time period, and the total number of data packets transmitted on the BH RLC channel of the second BH link during the fifth time period. When the measurement granularity is each BH RLC channel of each BH link, the measurement result is obtained by the quotient of the following two: the total number of packet losses of the second BH RLC channel during the sixth time period, and the total number of data packets transmitted by the second BH RLC channel during the sixth time period. as well as When the measurement granularity is each IAB node, the measurement result is obtained by the quotient of the following two: the total number of packet losses on the BH RLC channel of the IAB node's BH link during the seventh time period, and the total number of data packets transmitted on the BH RLC channel of the IAB node's BH link during the seventh time period.

34. An IAB node, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the measurement method as described in any one of claims 1 to 19.

35. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the measurement method as described in any one of claims 1 to 19.

Images