Packet loss rate detection method, communication device, and communication system

Abstract

The present application provides a packet loss rate detection method, a communication device, and a communication system. The method includes the steps of: a session management network element determining that link status detection needs to be performed on a link on which a service flow is located; and the session management network element sending a link status detection indication to a first device and / or a second device, the link status detection indication being for enabling a link status detection function, and the link status detection function includes a packet loss rate detection function. In this solution, the session management network element may send the link status detection indication to the first device and / or the second device to enable the link status detection function of the first device and / or the second device of the link. Thus, the first device and / or the second device may quickly and accurately detect a packet loss rate of a service data packet on the link based on the enabled link status detection function.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202110152262.X, entitled “PACKET LOSS RATE DETECTION METHOD, COMMUNICATION DEVICE, AND COMMUNICATION SYSTEM,” filed with the State Intellectual Property Office of the People's Republic of China on February 3, 2021, the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communication technologies, and in particular to a packet loss rate detection method, a communication device, and a communication system. [Background technology]

[0003] When a service data packet is transmitted between communication devices, the service data packet may be lost due to reasons such as link abnormality, etc. For example, when a first device transmits a service data packet to a second device, the service data packet may be lost.

[0004] How to quickly and accurately detect the packet loss rate of service data packets on a link currently needs to be solved. Summary of the Invention [Means for solving the problem]

[0005] The present application provides a packet loss rate detection method, a communication device, and a communication system for quickly and accurately detecting the packet loss rate of service data packets on a link.

[0006] According to a first aspect, an embodiment of the present application provides a packet loss rate detection method, the method includes the steps of: a session management network element determining that link status detection needs to be performed on a link on which a service flow is located, and the session management network element sending a link status detection indication to a first device and / or a second device, the link status detection indication is for enabling a link status detection function, and the link status detection function includes a packet loss rate detection function.

[0007] Based on the aforementioned solution, the session management network element may send a link status detection indication to the first device and / or the second device to enable a link status detection function of the first device and / or the second device, so that the first device and / or the second device may quickly and accurately detect a packet loss rate of a service data packet on a link based on the enabled link status detection function.

[0008] In one possible implementation method, the session management network element sends a counting instruction to the second device, where the counting instruction instructs the second device to count a quantity of service data packets sent by the first device to the second device over the link, or the counting instruction instructs the second device to calculate a quantity of service data packets received over the link upon receiving the link status detection information and send the quantity of service data packets received over the link to the first device.

[0009] Based on the aforementioned solution, the session management network element sends a counting instruction to the second device, so that the second device can accurately count the received service data packets, thereby helping to improve the accuracy of the packet loss rate calculation.

[0010] In one possible implementation method, the session management network element sends a packet loss rate detection instruction to the second device, where the packet loss rate detection instruction instructs the second device to calculate a packet loss rate of service data packets when receiving the link status detection information, or the packet loss rate detection instruction instructs the second device to calculate a quantity of service data packets received on the link when receiving the link status detection information, and calculate a packet loss rate of the service data packets by using the quantity of service data packets received on the link.

[0011] In one possible implementation method, the session management network element sends a counting instruction to the first device, where the counting instruction instructs the first device to count a quantity of service data packets transmitted by the first device to the second device over the link.

[0012] Based on the aforementioned solution, the session management network element sends a counting instruction to the first device, so that the first device can accurately count the transmitted service data packets, thereby helping to improve the accuracy of the packet loss rate calculation.

[0013] In one possible implementation method, the session management network element sends a packet loss rate detection instruction to the first device, where the packet loss rate detection instruction instructs the first device to calculate a packet loss rate of the service data packets upon receiving from the second device a quantity of received service data packets counted by the second device.

[0014] In one possible implementation method, the session management network element sends a link status reporting instruction to the first device and / or the second device, where the link status reporting instruction instructs the first device and / or the second device to report a packet loss rate of the service data packets, or the session management network element sends a link status reporting frequency to the first device and / or the second device, where the link status reporting frequency instructs the frequency to report the packet loss rate of the service data packets, or the session management network element sends a link status reporting period to the first device and / or the second device, where the link status reporting period instructs the period to report the packet loss rate of the service data packets.

[0015] Based on the aforementioned solution, the session management network element notifies the first device and / or the second device to report the packet loss rate, so that a network side, such as the session management network element or the policy control network element, can implement network control based on the received packet loss rate, thereby helping to improve network performance.

[0016] In one possible implementation method, the service flow includes at least one quality of service QoS flow, the QoS flow includes at least one service data flow, and the step of the session management network element determining that link status detection needs to be performed on the link on which the service flow is located includes the steps of: when the steering function of the service data flow in the service flow is determined to be ATSSS-LL, the session management network element determining that link status detection needs to be performed on the link on which the service flow is located; when the steering function of the service data flow in the service flow is ATSSS-LL and the steering mode of the service data flow is one of a load balancing mode, a minimum latency mode, a priority-based mode, or an active-standby mode, the session management network element determining that link status detection needs to be performed on the link on which the service flow is located; or when the session management network element determines that a link status threshold for the service flow has been received from the policy control network element, the link status threshold includes a packet loss rate threshold.

[0017] Based on the above solution, the detection of the packet loss rate of the service data packets is performed only when it is determined that the link status detection needs to be performed on the link where the service flow is located. In this way, unnecessary overhead can be reduced.

[0018] In one possible implementation, the service flow includes any one of a protocol data unit PDU session, a service data flow SDF, an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0019] In one possible implementation method, the second device is a terminal device or a user plane network element.

[0020] In one possible implementation, the link status detection indication includes an IP address and / or a port number of the link status detection function.

[0021] In one possible implementation method, the session management network element sends identification information of the service flow to the first device and / or the second device, where the identification information includes a PDU session identifier, service data flow description information, IP5 tuple information, Ethernet flow description information, or at least one QFI, and the link status detection indication is for enabling a link status detection function includes that the link status detection indication is for enabling a link status detection function of the service flow.

[0022] According to a second aspect, an embodiment of the present application provides a packet loss rate detection method, the method includes: a second device receiving first link status detection information from a first device via a link, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device on the link; the second device obtaining a packet loss rate of the service data packets on the link based on the first link status detection information; and the second device transmitting the packet loss rate of the service data packets to the first device.

[0023] Based on the above solution, the first device can inform the second device of the quantity of service data packets sent by the first device to the second device on the link by using the link status detection information, so that the second device can quickly calculate the packet loss rate of the service data packets based on the link status detection information. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate can be improved.

[0024] In one possible implementation method, before the step of the second device receiving first link status detection information from the first device, the second device receives second link status detection information from the first device by using the link, and the first link status detection information indicating a quantity of service data packets transmitted by the first device over the link to the second device includes the first link status detection information indicating a first quantity of service data packets transmitted by the first device over the link to the second device within a time period during which the first device transmits the second link status detection information and the first device transmits the first link status detection information.

[0025] In one possible implementation method, the step of the second device obtaining a packet loss rate of service data packets on the link based on the first link status detection information includes a step of the second device obtaining, based on the first link status detection information, a packet loss rate of service data packets on the link within a time period during which the first device transmits the second link status detection information and the first device transmits the first link status detection information.

[0026] In one possible implementation, the second link status detection information indicates an initial data packet or an initial time for calculating a packet loss rate.

[0027] In one possible implementation method, after the second device receives first link status detection information from the first device, the second device receives third link status detection information from the first device by using the link, and the third link status detection information indicates a first quantity and a second quantity of service data packets transmitted by the first device over the link to the second device within a time period between when the first device transmits the first link status detection information and when the first device transmits the third link status detection information.

[0028] Based on the above solution, multiple quantities of service data packets are carried in one link status detection information, which helps to eliminate the impact caused by the loss of link status detection information, thereby improving the accuracy of packet loss rate calculation.

[0029] In one possible implementation method, the step of the second device acquiring a packet loss rate of service data packets on the link based on the first link status detection information includes: the second device acquiring, based on the first link status detection information, a packet loss rate of service data packets on the link within a time period when the first device transmits the second link status detection information and the first device transmits the third link status detection information; and / or the second device acquiring, based on the first link status detection information, a packet loss rate of service data packets on the link within a time period when the first device transmits the first link status detection information and the first device transmits the third link status detection information.

[0030] In one possible implementation method, the first link status detection information and the second link status detection information are two adjacent link status detection information.

[0031] In one possible implementation method, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device over the link includes the first link status detection information indicating a third quantity of service data packets transmitted by the first device over the link to the second device within a time period between when the first device transmits an initial service data packet over the link and when the first device transmits the first link status detection information.

[0032] In one possible implementation method, the step of the second device obtaining a packet loss rate of service data packets on the link based on the first link status detection information includes a step of the second device obtaining, based on the first link status detection information, a packet loss rate of service data packets on the link within a time period during which the first device transmits an initial data packet and the first device transmits the first link status detection information.

[0033] In one possible implementation method, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device over the link includes the first link status detection information instructing the first device to transmit a default quantity of service data packets to the second device over the link.

[0034] Based on the above solution, the first device does not need to add quantity information of the transmission service data packets to the link status detection information, thereby reducing overhead.

[0035] In one possible implementation, the second device receives indication information from the first device, the indication information indicating a value of the default quantity.

[0036] In one possible implementation method, after the step of the second device receiving first link status detection information from the first device, the second device receives fourth link status detection information from the first device by using the link, where the fourth link status detection information indicates a fourth quantity of service data packets transmitted by the first device to the second device on the link within a time period when the first device transmits the first link status detection information and the first device transmits the fourth link status detection information, and the step of the second device obtaining a packet loss rate of the service data packets based on the first link status detection information includes the step of the second device obtaining a packet loss rate of the service data packets within a time period when the first device transmits the second link status detection information and the first device transmits the fourth link status detection information based on the first link status detection information and the fourth link status detection information.

[0037] Based on the above solution, the packet loss rate of service data packets between non-adjacent link status detection information is calculated, so that the influence caused by the disorder of service data packets can be eliminated, thereby improving the accuracy of packet loss rate calculation.

[0038] In one possible implementation method, the first link status detection information, the second link status detection information, the third link status detection information, and the fourth link status detection information all include a link status detection data packet.

[0039] In one possible implementation, a service flow on a link includes any one of a protocol data unit PDU session, a service data flow SDF, an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0040] In one possible implementation method, the first device is a terminal device and the second device is a user plane network element, or the first device is a user plane network element and the second device is a terminal device.

[0041] In one possible implementation method, the second device receives a link status detection indication from the session management network element, the link status detection indication being for enabling a link status detection function, the link status detection function including a packet loss rate detection function.

[0042] In one possible implementation method, the second device receives identification information of a service flow from a session management network element, the identification information including a PDU session identifier, service data flow description information, IP5 tuple information, Ethernet flow description information, or at least one QFI, and the link status detection indication is for enabling a link status detection function includes that the link status detection indication is for enabling a link status detection function of the service flow.

[0043] In one possible implementation method, the second device receives a counting instruction from the session management network element, where the counting instruction instructs the second device to count a quantity of service data packets sent by the first device to the second device on the link, or the counting instruction instructs the second device to calculate a quantity of received service data packets on the link and send the quantity of received service data packets on the link to the first device when receiving the link status detection information.

[0044] In one possible implementation method, the second device receives a packet loss rate detection instruction from the session management network element, and the packet loss rate detection instruction instructs the second device to calculate a packet loss rate of service data packets when receiving the link status detection information, or the packet loss rate detection instruction instructs the second device to calculate a quantity of service data packets received on the link when receiving the link status detection information, and calculate a packet loss rate of the service data packets by using the quantity of service data packets received on the link.

[0045] In one possible implementation method, the second device receives a link status reporting instruction from the session management network element, where the link status reporting instruction instructs the second device to report a packet loss rate of service data packets, or the second device receives a link status reporting frequency from the session management network element, where the link status reporting frequency instructs the second device to report a packet loss rate of service data packets, or the second device receives a link status reporting period from the session management network element, where the link status reporting period instructs the second device to report a packet loss rate of service data packets.

[0046] According to a third aspect, an embodiment of the present application provides a packet loss rate detection method, the method including: a first device transmitting first link status detection information to a second device via a link, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device on the link, and the first device receiving a packet loss rate of the service data packets, the packet loss rate of the service data packets being obtained based on the first link status detection information.

[0047] Based on the above solution, the first device can inform the second device of the quantity of service data packets sent by the first device to the second device on the link by using the link status detection information, so that the second device can quickly calculate the packet loss rate of the service data packets based on the link status detection information. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate can be improved.

[0048] In one possible implementation method, before the step of the first device transmitting first link status detection information to the second device, the first device transmitting second link status detection information to the second device by using the link, wherein the first link status detection information indicating a quantity of service data packets transmitted by the first device over the link to the second device includes the first link status detection information indicating a first quantity of service data packets transmitted by the first device over the link to the second device within a time period during which the first device transmits the second link status detection information and the first device transmits the first link status detection information.

[0049] In one possible implementation, the second link status detection information indicates an initial data packet or an initial time for calculating a packet loss rate.

[0050] In one possible implementation method, after the step of the first device transmitting first link status detection information to the second device, the first device transmits third link status detection information to the second device by using the link, and the third link status detection information indicates a first quantity and a second quantity of service data packets transmitted by the first device over the link to the second device within a time period from when the first device transmits the first link status detection information to when the first device transmits the third link status detection information.

[0051] Based on the above solution, multiple quantities of service data packets are carried in one link status detection information, which helps to eliminate the impact caused by the loss of link status detection information, thereby improving the accuracy of packet loss rate calculation.

[0052] In one possible implementation method, the first link status detection information and the second link status detection information are two adjacent link status detection information.

[0053] In one possible implementation method, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device over the link includes the first link status detection information indicating a third quantity of service data packets transmitted by the first device over the link to the second device within a time period between when the first device transmits an initial service data packet over the link and when the first device transmits the first link status detection information.

[0054] In one possible implementation method, the first link status detection information indicating a quantity of service data packets transmitted by the first device to the second device over the link includes the first link status detection information instructing the first device to transmit a default quantity of service data packets to the second device over the link.

[0055] Based on the above solution, the first device does not need to add quantity information of the transmission service data packets to the link status detection information, thereby reducing overhead.

[0056] In one possible implementation, the first device transmits indication information to the second device, where the indication information indicates a value of the default quantity.

[0057] In one possible implementation method, the first link status detection information, the second link status detection information, and the third link status detection information all include a link status detection data packet.

[0058] In one possible implementation, a service flow on a link includes any one of a protocol data unit PDU session, a service data flow SDF, an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0059] In one possible implementation method, the first device is a terminal device and the second device is a user plane network element, or the first device is a user plane network element and the second device is a terminal device.

[0060] In one possible implementation method, the first device receives a link status detection indication from a session management network element, the link status detection indication being for enabling a link status detection function, the link status detection function including a packet loss rate detection function.

[0061] In one possible implementation method, the first device receives identification information of a service flow from a session management network element, the identification information including a PDU session identifier, service data flow description information, IP5 tuple information, Ethernet flow description information, or at least one QFI, and the link status detection indication is for enabling a link status detection function includes that the link status detection indication is for enabling a link status detection function of the service flow.

[0062] In one possible implementation method, the first device receives a counting instruction from a session management network element, the counting instruction instructing the first device to count a quantity of service data packets transmitted by the first device to the second device over the link.

[0063] In one possible implementation method, the first device receives a link status reporting instruction from the session management network element, where the link status reporting instruction instructs to report a packet loss rate of service data packets, or the first device receives a link status reporting frequency from the session management network element, where the link status reporting frequency instructs the frequency to report the packet loss rate of service data packets, or the first device receives a link status reporting period from the session management network element, where the link status reporting period instructs the period to report the packet loss rate of service data packets.

[0064] According to a fourth aspect, an embodiment of the present application provides a packet loss rate detection method, the method including: a second device receiving fifth link status detection information from a first device via a link, the second device determining a quantity of service data packets received by the second device from the first device on the link based on the fifth link status detection information, and the second device sending a quantity of service data packets to the first device, where the quantity of service data packets is for determining a packet loss rate of the service data packets on the link.

[0065] Based on the above solution, the second device may inform the first device of the quantity of service data packets received by the second device from the first device over the link by using the link status detection information, so that the first device may quickly calculate the packet loss rate of the service data packets based on the quantity of the service data packets received by the second device from the first device over the link. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate may be improved.

[0066] In one possible implementation method, before the step of the second device receiving a fifth link status detection information from the first device, the second device receives a sixth link status detection information from the first device by using the link, and the step of the second device determining a quantity of service data packets received by the second device from the first device over the link based on the fifth link status detection information includes a step of the second device determining a quantity of service data packets received by the second device from the first device over the link within a time period when the first device transmits the sixth link status detection information and when the first device transmits the fifth link status detection information.

[0067] In one possible implementation method, the second device sends time information corresponding to the quantity of the service data packets to the first device.

[0068] In one possible implementation method, the time information includes a period between the first device transmitting the sixth link status detection information and the first device transmitting the fifth link status detection information.

[0069] In one possible implementation method, the fifth link status detection information and the sixth link status are link status detection data packets, and the time information includes sequence number information corresponding to the link status detection data packets.

[0070] In one possible implementation, a service flow on a link includes any one of a protocol data unit PDU session, a service data flow SDF, an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0071] In one possible implementation method, the first device is a terminal device and the second device is a user plane network element, or the first device is a user plane network element and the second device is a terminal device.

[0072] In one possible implementation method, the second device receives a link status detection indication from the session management network element, the link status detection indication being for enabling a link status detection function, the link status detection function including a packet loss rate detection function.

[0073] In one possible implementation method, the second device receives identification information of a service flow from a session management network element, the identification information including a PDU session identifier, service data flow description information, IP5 tuple information, Ethernet flow description information, or at least one QFI, and the link status detection indication is for enabling a link status detection function includes that the link status detection indication is for enabling a link status detection function of the service flow.

[0074] In one possible implementation method, the second device receives a counting instruction from the session management network element, where the counting instruction instructs the second device to count a quantity of service data packets sent by the first device to the second device on the link, or the counting instruction instructs the second device to calculate a quantity of received service data packets on the link and send the quantity of received service data packets on the link to the first device when receiving the link status detection information.

[0075] According to a fifth aspect, an embodiment of the present application provides a packet loss rate detection method, the method including: a first device transmitting fifth link status detection information to a second device over a link; the first device receiving from the second device a quantity of service data packets received from the first device over the link by the second device, where the quantity of service data packets is determined based on the fifth link status detection information; and the first device determining a packet loss rate of service data packets on the link based on the quantity of service data packets.

[0076] Based on the above solution, the second device may inform the first device of the quantity of service data packets received by the second device from the first device over the link by using the link status detection information, so that the first device may quickly calculate the packet loss rate of the service data packets based on the quantity of the service data packets received by the second device from the first device over the link. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate may be improved.

[0077] In one possible implementation method, before the step of the first device transmitting the fifth link status detection information to the second device, the first device transmits sixth link status detection information to the second device by using the link, and the quantity of service data packets is the quantity of service data packets received from the first device by the second device on the link within a time when the first device transmits the sixth link status detection information and the first device transmits the fifth link status detection information. The step of the first device determining a packet loss rate of the service data packets on the link based on the quantity of the service data packets includes the step of the first device determining a packet loss rate of the service data packets on the link based on the quantity of the service data packets and the quantity of the service data packets transmitted by the first device to the second device on the link within a time when the first device transmits the sixth link status detection information and the first device transmits the fifth link status detection information.

[0078] In one possible implementation method, the first device receives time information corresponding to a quantity of service data packets from the second device.

[0079] In one possible implementation method, the time information includes a period between the first device transmitting the sixth link status detection information and the first device transmitting the fifth link status detection information.

[0080] In one possible implementation method, the fifth link status detection information and the sixth link status are link status detection data packets, and the time information includes sequence number information corresponding to the link status detection data packets.

[0081] In one possible implementation, a service flow on a link includes any one of a protocol data unit PDU session, a service data flow SDF, an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0082] In one possible implementation method, the first device is a terminal device and the second device is a user plane network element, or the first device is a user plane network element and the second device is a terminal device.

[0083] In one possible implementation method, the first device receives a link status detection indication from a session management network element, the link status detection indication being for enabling a link status detection function, the link status detection function including a packet loss rate detection function.

[0084] In one possible implementation method, the first device receives identification information of a service flow from a session management network element, the identification information including a PDU session identifier, service data flow description information, IP5 tuple information, Ethernet flow description information, or at least one QFI, and the link status detection indication is for enabling a link status detection function includes that the link status detection indication is for enabling a link status detection function of the service flow.

[0085] In one possible implementation method, the first device receives a counting instruction from a session management network element, the counting instruction instructing the first device to count a quantity of service data packets transmitted by the first device to the second device over the link.

[0086] In one possible implementation method, a first device receives a packet loss rate detection instruction from a session management network element, the packet loss rate detection instruction instructing the first device to calculate a packet loss rate of service data packets upon receiving from a second device a quantity of received service data packets counted by the second device.

[0087] In one possible implementation method, the first device receives a link status reporting instruction from the session management network element, where the link status reporting instruction instructs to report a packet loss rate of service data packets, or the first device receives a link status reporting frequency from the session management network element, where the link status reporting frequency instructs the frequency to report the packet loss rate of service data packets, or the first device receives a link status reporting period from the session management network element, where the link status reporting period instructs the period to report the packet loss rate of service data packets.

[0088] According to a sixth aspect, an embodiment of the present application provides a communication device. The device may be a session management network element, or a chip used in a session management network element. The device has a function for implementing any of the implementation methods in the first aspect. The function may be implemented by hardware, or may be implemented by the hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0089] According to a seventh aspect, an embodiment of the present application provides a communication device. The device may be a second device or a chip used in the second device. The device has a function of performing any of the implementation methods in the second or fourth aspects. The function may be performed by hardware, or may be performed by the hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0090] According to an eighth aspect, an embodiment of the present application provides a communication device. The device may be a first device or a chip used in the first device. The device has a function of performing any of the implementation methods in the third or fifth aspects. The function may be performed by hardware, or may be performed by the hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the function.

[0091] According to a ninth aspect, an embodiment of the present application provides a communications device including a processor and a memory, the memory being configured to store computer instructions, and wherein, when the device is operated, the processor executes the computer instructions stored in the memory, such that the device performs an implementation method of any of the first to fifth aspects.

[0092] According to a tenth aspect, an embodiment of the present application provides a communication device including a unit or means for performing the steps of any of the methods in the first to fifth aspects.

[0093] According to an eleventh aspect, an embodiment of the present application provides a communication device including a processor and an interface circuit. The processor is configured to communicate with another device by using the interface circuit and to perform any of the methods according to the first to fifth aspects. There are one or more processors.

[0094] According to a twelfth aspect, an embodiment of the present application provides a communication device including a processor configured to be coupled to a memory. The processor is configured to invoke a program stored in the memory to perform any of the implementation methods in the first to fifth aspects. The memory may be located internally or externally to the device. There may be one or more processors.

[0095] According to a thirteenth aspect, an embodiment of the present application further provides a computer-readable storage medium, the computer-readable storage medium storing instructions, which, when executed on a computer, perform any of the methods in the first to fifth aspects.

[0096] According to a fourteenth aspect, an embodiment of the present application further provides a computer program product, the computer program product including a computer program, the computer program being configured to, when executed, perform any of the methods of the first to fifth aspects.

[0097] According to a fifteenth aspect, an embodiment of the present application further provides a chip system including a processor configured to perform any of the implementation methods in the first to fifth aspects.

[0098] According to a sixteenth aspect, an embodiment of the present application further provides a communication system including a second device configured to perform any of the implementation methods in the second aspect, and a first device configured to perform any of the implementation methods in the third aspect.

[0099] In one implementation method, the communication system further includes a session management network element configured to perform any of the implementation methods in the first aspect.

[0100] According to a seventeenth aspect, an embodiment of the present application further provides a communication system including a second device configured to perform any of the implementation methods in the fourth aspect, and a first device configured to perform any of the implementation methods in the fifth aspect.

[0101] In one implementation method, the communication system further includes a session management network element configured to perform any of the implementation methods in the first aspect.

[0102] According to an eighteenth aspect, an embodiment of the present application further provides a communication system including a session management network element configured to perform any of the implementation methods in the first aspect, and a first device or a second device configured to receive a link status detection indication from the session management network element, where the link status detection indication is for enabling a link status detection function. [Brief description of the drawings]

[0103] [Figure 1a] FIG. 1 is a schematic diagram of a 5G network architecture based on a service-based architecture. [Figure 1b] FIG. 1 is a schematic diagram of a 5G network architecture based on a point-to-point interface. [Figure 1c] FIG. 2 is another schematic diagram of a 5G network architecture based on a point-to-point interface. [Diagram 2] A schematic diagram of the relationship between PDU sessions and access technologies. [Diagram 3] FIG. 2 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application; [Figure 4a] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4b] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4c] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4d] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4e] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4f] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 4g] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Diagram 5] FIG. 2 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application; [Figure 6] FIG. 2 is a diagram of an example of transmission of link status detection information and service data packets according to one embodiment of the present application. [Figure 7] FIG. 2 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application; [Figure 8] FIG. 2 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application; [Figure 9] 1 is a schematic diagram of a communication device according to an embodiment of the present application; [Figure 10] 1 is a schematic diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0104] In order to make the objectives, technical solutions and advantages of the present application clearer, the following will further describe the present application in detail with reference to the accompanying drawings. Certain operation methods in the method embodiments may also be applied to the device embodiments or system embodiments.

[0105] Figure 1a is a schematic diagram of a fifth generation (5G) network architecture based on a service-based architecture. The 5G network architecture shown in Figure 1a may include three parts: a terminal device part, a data network (DN), and an operator network part. The following briefly describes some functions of the network elements.

[0106] The operator network may include one or more of the following network elements: an Authentication Server Function (AUSF) network element, a network exposure function (NEF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a unified data repository (UDR) network element, a network repository function (NRF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a radio access network (RAN) network element, and a user plane function (UPF) network element. In the above-mentioned operator network, a part other than the radio access network may be called a core network. In one possible implementation method, the operator network further includes an Application Function (AF) network element.

[0107] A terminal device is a device having a wireless transceiver function. The terminal device may be deployed on land, including an indoor device, an outdoor device, a handheld device, or an in-vehicle device, on water (e.g., on a ship), or in the air (e.g., on an airplane, a balloon, or a satellite). The terminal device may be a mobile phone, a tablet computer (pad), a computer having a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or a user equipment (UE).

[0108] The terminal device may establish a connection to the operator network through an interface (e.g., N1) provided by the operator network, and use services such as data and / or voice provided by the operator network. The terminal device may further access the DN through the operator network, and use the operator services deployed on the DN and / or services provided by a third party. The third party may be a service provider other than the operator network and the terminal device, and may provide other services such as data and / or services to the terminal device. The specific expression form of the third party may be specifically determined based on the actual application scenario, and is not limited here.

[0109] The RAN is a sub-network of an operator network and is an implementation system between a service node in the operator network and a terminal device. To access the operator network, the terminal device may first pass through the RAN and then be connected to a service node in the operator network via the RAN. The RAN device is a device that provides wireless communication capabilities to the terminal device, and is also called an access network device. The RAN device includes, but is not limited to, a next generation node B (g node B, gNB), an evolved node B (eNB), a radio network controller (RNC), a node B (node ​​B, NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B or home node B, HNB), a baseband unit (baseBand unit, BBU), a transmitting and receiving point (TRP), a transmitting point (TP), or a 5G mobile switching center.

[0110] The AMF network element mainly performs functions such as mobility management and access authentication / authorization. In addition, the AMF network element is also responsible for the transfer of user policies between the UE and the PCF.

[0111] The SMF network element mainly performs functions such as session management, enforcement of control policies delivered by the PCF, UPF selection, and UE internet protocol (IP) address allocation.

[0112] The UPF network element serves as the interface to the data network and performs functions such as user plane data forwarding, session or flow level charging statistics, and bandwidth regulating.

[0113] The UDM network element is mainly responsible for functions such as subscriber data management and user access authorization.

[0114] The UDR is primarily responsible for the functionality of accessing subscriber data, policy data, application data, and other types of data.

[0115] The NEF network element is primarily configured to support capability and event publication.

[0116] The AF network element mainly forwards application side requirements on the network side, such as Quality of Service (QoS) requirements and user status event subscriptions. The AF may be a third-party functional entity or an operator-deployed application service, such as IP Multimedia Subsystem (IMS) voice service.

[0117] The PCF network element is mainly responsible for policy control functions such as charging on session level or service data flow level, QoS bandwidth guarantee, mobility management, and UE policy decision. In this architecture, the PCFs connected to the AMF and SMF are AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management), respectively. In real deployment scenarios, the PCFs may not be the same PCF entity.

[0118] The NRF network element may be configured to provide network element discovery functionality and provide network element information corresponding to a network element type based on a request from another network element. The NRF further provides network element management services, such as network element registration, update, and deregistration, as well as subscription and push of network element status.

[0119] The AUSF network element is primarily responsible for authenticating users to determine whether a user or device should be allowed to access the network.

[0120] A DN is a network outside an operator network. An operator network may access multiple DNs. Multiple services may be deployed on a DN, and a DN may provide services such as data and / or voice to a terminal device. For example, a DN is a private network of a smart factory, a sensor installed in a workplace of the smart factory may be a terminal device, and a control server of the sensor may be deployed on the DN, and the control server may provide services to the sensor. The sensor may communicate with the control server to obtain an instruction of the control server, and based on the instruction, transmit the collected sensor data to the control server. As another example, a DN is an internal office network of a company, and a mobile phone or computer of an employee of the company may be a terminal device, and the employee's mobile phone or computer may access information, data resources, etc. in the internal office network of the company.

[0121] Nausf, Nnef, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 in Figure 1a are interface sequence numbers. For the meaning of these interface sequence numbers, please refer to the meaning defined in the 3rd generation partnership project (3GPP) standard protocol, which is not limited here.

[0122] Figure 1b is a schematic diagram of a 5G network architecture based on a point-to-point interface. For the functional description of the network elements, please refer to the functional description of the corresponding network elements in Figure 1a. The details will not be described again here. The main difference between Figure 1a and Figure 1b is that the interface between the network elements in Figure 1b is a point-to-point interface, and the interface between the network elements in Figure 1a is a service-based interface.

[0123] In the architecture shown in FIG. 1b, the names and functions of the interfaces between the network elements are as follows:

[0124] (1) N7 is an interface between the PCF and the SMF and may be configured to deliver protocol data unit (PDU) session granularity control policies and service data flow granularity control policies.

[0125] (2) N15 is an interface between the PCF and the AMF and may be configured to deliver UE policies and access control related policies.

[0126] (3) N5 is an interface between the AF and the PCF and may be configured to deliver application service requests and report network events.

[0127] (4) N4 is an interface between the SMF and the UPF and may be configured to transfer information between the control plane and the user plane, including distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, and reporting of user plane information.

[0128] (5) N11 is an interface between the SMF and the AMF and may be configured to transfer PDU session tunnel information between the RAN and the UPF, transfer control messages to be sent to the UE, and transfer radio resource control information to be sent to the RAN.

[0129] (6) N2 is an interface between the AMF and the RAN, and may be configured to transfer radio bearer control information, etc. from the core network side to the RAN.

[0130] (7) N1 is an interface between the AMF and the UE and may be configured to transfer QoS control rules, etc. to the UE.

[0131] (8) N8 is an interface between the AMF and the UDM, and may be used by the AMF to obtain subscriber data and authentication data related to access and mobility management from the UDM, and may be used by the AMF to register the UE's current mobility management-related information to the UDM.

[0132] (9) N10 is an interface between the SMF and the UDM, and may be used by the SMF to obtain subscriber data related to session management from the UDM, and may be used by the SMF to register the UE's current session-related information to the UDM.

[0133] (10) N35 is an interface between the UDM and the UDR and may be used by the UDM to obtain user subscriber data information from the UDR.

[0134] (11) N36 is an interface between the PCF and the UDR and may be used by the PCF to obtain policy-related subscriber data and application data-related information from the UDR.

[0135] (12) N12 is an interface between the AMF and the AUSF, and may be used by the AMF to initiate an authentication procedure towards the AUSF, and may carry a subscription concealed identifier (SUCI) as the subscriber identifier.

[0136] (13) N13 is an interface between the UDM and the AUSF and may be used by the AUSF to obtain a user authentication vector from the UDM to perform the authentication procedure.

[0137] A 5G network architecture based on a point-to-point interface when the 5G core network supports untrusted Non-3GPP access is shown in Figure 1c. The access network includes a 3GPP access network and a non-3GPP access network. The access device in the 3GPP access network may also be called a radio access network (RAN) device. The access device in the non-3GPP access network may also be called a Non-3GPP InterWorking Function (N3IWF) device. The N3IWF device may include, for example, a router.

[0138] It should be noted that when the 5G core network supports trusted non-3GPP access, the 5G network architecture of the 5G core network is similar to the 5G network architecture of Figure 1c. The untrusted non-3GPP access in Figure 1c may be replaced with a trusted non-3GPP access, and the N3IWF may be replaced with a trusted non-3GPP access gateway.

[0139] It should be understood that the aforementioned network elements or functions may be network elements in a hardware device, software functions running on dedicated hardware, or virtual functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements or functions may be implemented by one device, may be implemented jointly by multiple devices, or may be one functional module in one device. This is not particularly limited in the embodiments of the present application.

[0140] The mobility management network element, session management network element, policy control network element, access network device, and user plane network element in this application may be the AMF, SMF, PCF, and UPF of FIG. 1a, FIG. 1b, or FIG. 1c, or may be a network element having the functions of AMF, SMF, PCF, UPF, and RAN in future communications such as a 6th generation (6G) network. This is not limited in this application. For ease of explanation, this application uses an example in which the mobility management network element, session management network element, policy control network element, access network device, and user plane network element are AMF, SMF, PCF, RAN, and UPF, respectively. Furthermore, this application uses an example in which the terminal device is a UE for explanation.

[0141] In order to facilitate understanding of the solutions in the embodiments of the present application, the following will first explain and describe some terms or nouns in the embodiments of the present application.

[0142] 1. Multi-access PDU (MAPDU) Session A single PDU session may support multiple access technologies. Figure 2 is a schematic diagram of the relationship between PDU sessions and access technologies. See Figure 2. A PDU session may be accessed using a first access technology or by using a second access technology. In this scenario, the PDU session may also be referred to as a MAPDU session.

[0143] The first access technology is different from the second access technology, or the first access technology and the second access technology are the same access technology but are used separately by different access network devices. The first access technology and the second access technology may be any two of the following access technologies, including, but not limited to, 3GPP access, non3GPP access, long term evolution (LTE) access, 5GRAN access, trusted non3GPP access, untrusted non3GPP access, wireless local area network (WLAN) access, fixed network access, etc.

[0144] A MAPDU session may implement mobility or parallel processing of a service flow between different access technologies. If a service flow is transmitted by using a first access technology, the service flow is subsequently moved to be transmitted by using a second access technology. Alternatively, service data packets of a service flow are transmitted by using both the first and second access technologies to increase bandwidth.

[0145] 2. Service Flow In an embodiment of the present application, a service flow includes a PDU session, a service data flow (SDF), an IP data flow, an Ethernet data flow, or at least one QoS flow.

[0146] A PDU session includes one or more QoS flows and is identified by a PDU session ID.

[0147] A QoS flow includes one or more SDFs.

[0148] One SDF contains one or more IP flows or contains one or more Ethernet flows. The IP data packets or the Ethernet data packets in one SDF correspond to the same service data flow description information.

[0149] An IP flow includes one or more IP data packets, and the IP data packets in an IP flow have the same IP5 tuple information, which includes at least one of a source IP address, a destination IP address, a source port number, a destination port number, or a protocol number.

[0150] An Ethernet flow includes one or more Ethernet data packets, and the Ethernet data packets in an Ethernet flow have the same Ethernet flow description information, which includes at least one of a source MAC address or a destination MAC address.

[0151] In the embodiment of the present application, the service data packets include IP data packets, Ethernet data packets, etc.

[0152] 2. Service Data Flow (SDF) steering mode The steering mode of the service data flow indicates how the service data flow is selected, moved, or split in the data transmission channels of the two access technologies. The steering mode of the service data flow includes, but is not limited to:

[0153] 1. Active-standby mode A link corresponding to an Active access technology is an Active link and can provide services. A link corresponding to a Standby access technology is a Standby link and is in a Standby state. The two links can be switched when a policy is updated.

[0154] In this mode, when a link corresponding to an active access technology is available, the service data flow is transmitted on that access technology, and when the link corresponding to the active access technology is unavailable, the service data flow is switched to a standby link corresponding to the standby access technology. When the link of the active access technology recovers from an unavailable state to an available state, the service data flow can be switched to the active access technology. If a standby access technology is not defined, the service data flow can only be transmitted on the active access technology.

[0155] 2. Smallest delay mode In this mode, the service data flow is allocated to the access technology with the smallest round-trip time (RTT) for transmission. The UE and UPF may measure the RTT of the link of the first access technology and the RTT of the link of the second access technology and compare the RTTs of the two links. If the RTT of the link of the first access technology is smaller than the RTT of the link of the second access technology, the UE and UPF select to transmit the service data flow in the first access technology. If the RTT of the link of the second access technology is smaller than the RTT of the link of the first access technology, the UE and UPF select to transmit the service data flow in the second access technology. If the RTT of the link of the first access technology is equal to the RTT of the link of the second access technology, the UE and UPF select to transmit the service data flow in the first access technology or the second access technology. In addition, if one access technology is unavailable and Policy and Charging Control (PCC) rules allow, all service data flows may be switched to the data transmission channel of another access technology.

[0156] 3. Load-balancing mode In this mode, if two access technologies are available, the service data flow is transmitted in the two access technologies, and the service data flow is transmitted on the data transmission channels of the two access technologies according to the percentage of the service data flow transmitted.

[0157] If one access technology is unavailable, all service data flows are switched to another access technology, which equates to a percentage of the service data flows transmitted in the available access technology being 100%.

[0158] 4. Priority-based mode In this mode, all service data flows are directed to the high priority access technology until the access technology link becomes congested. When the high priority access technology link is unavailable, all service data flows are switched to the low priority access technology for transmission.

[0159] 3. Steering function of Service Data Flow (SDF) The steering function of the service data flow indicates the function that steers the service data flow. The steering function of the service data flow includes but is not limited to the following:

[0160] 1. Access traffic steering, switching, splitting low-layer (ATSSS-LL) The ATSSS-LL function is implemented at or below the IP layer. Therefore, the ATSSS-LL function is referred to as a steering function at the lowest layer. The aforementioned steering function selects a link corresponding to an access technology for a service data packet to be transmitted based on a steering mode and a current link status. The link status is a link status of at least one link between the UE and the UPF. The UE and the UPF detect the link status based on a link status detection protocol, such as a performance measurement function (PMF) protocol. The ATSSS-LL selects, switches, or splits a service flow based on the link status detection result and the steering mode.

[0161] 2. Multipath transmission control protocol (MPTCP) The MPTCP steering function is a steering, switching or splitting function of a service data packet implemented based on MPTCP. According to a steering mode and a link condition detected by the TCP layer, the steering function selects, for a service data packet, a link corresponding to an access technology for transmitting the service data packet.

[0162] In a multi-access scenario, for a service flow (such as a PDU session, an IP flow, an Ethernet flow, an SDF, or at least one QoS flow), an access technology needs to be selected based on the link status (such as packet loss rate, delay, bandwidth, etc.), so the UE and the UPF need to detect the link status in real time. Of course, in a single-access scenario, the UE and the UPF may still need to detect the link status in real time for a service flow. For example, the UE or the UPF needs to determine how to adjust the transmission rate of a service data packet based on the link status.

[0163] Currently, a method for detecting a packet loss rate in a link state by a UE and a UPF is to recognize the link state based on a transport layer protocol, such as a Transmission Control Protocol (TCP) or a quick UDP internet connections (QUIC) protocol, where UDP is an abbreviation of user datagram protocol. Specifically, the transmitting end adds a sequence number to each transmitted service data packet, and the receiving end transmits an acknowledgement (ACK) for each service data packet to the transmitting end after receiving each service data packet, so that the receiving end can determine the number of service data packets actually transmitted by the transmitting end based on the sequence number of each service data packet, and further determine the packet loss rate of the service data packets based on the number of service data packets actually transmitted by the transmitting end and the number of service data packets actually received by the receiving end. The transmitting end can determine the packet loss rate of the service data packets based on the number of acknowledgements of the service data packets transmitted by the receiving end and the number of service data packets actually transmitted by the transmitting end.

[0164] In the uplink direction, the transmitting end is the UE and the receiving end is the UPF. In the downlink direction, the transmitting end is the UPF and the receiving end is the UE.

[0165] The above solution of determining the packet loss rate of service data packets based on the transport layer protocol has the following problems.

[0166] First, there is a certain delay. For example, when the packet loss rate is measured based on TCP, the sending end needs one or more minimum round trip times (RTTs) after sending a service data packet to the receiving end. If an acknowledgement for the service data packet is not received before one or more RTTs, the sending end determines that the service data packet is lost, i.e., the service data packet is not received by the receiving end. Therefore, there is a certain delay when the sending end calculates the packet loss rate, and the delay is related to the time to wait for an acknowledgement.

[0167] Second, the efficiency is low. Since the packet loss rate is determined based on the transport layer protocol, the sending end or receiving end needs to parse the service data packets based on the transport layer protocol, so the efficiency of determining the packet loss rate is low.

[0168] In order to quickly and accurately determine the packet loss rate, an embodiment of the present application provides a corresponding packet loss rate detection method.

[0169] It should be noted that in the embodiment of the present application, the first device serves as a sender of a service data packet, and the second device serves as a receiver of the service data packet. In the uplink direction, the first device is a UE, and the second device is a UPF. In the downlink direction, the first device is a UPF, and the second device is a UE.

[0170] In the embodiment of the present application, it should be noted that the link status detection information (for example, in the following embodiment, the first link status detection information, the second link status detection information, the third link status detection information, the fourth link status detection information, the fifth link status detection information, and the sixth link status detection information) may include a link status detection data packet, and the link status detection data packet is different from the service data packet. Specifically, the service data packet is used to transmit data, the link status detection data packet indicates the quantity of received or transmitted service data packets, and the link status detection data packet can be used to calculate the packet loss rate of the service data packet.

[0171] It should be noted that in the embodiment of the present application, a "link" may be understood as a "channel", for example, a 3GPP link or a non3GPP link. A service flow is transmitted on the link, and the service flow may be a PDU session, an SDF, an IP flow, an Ethernet flow, or at least one QoS flow. Link status detection is to detect the status of the link on which the service flow is located.

[0172] In the embodiment of the present application, the smallest transmission unit transmitted in a service flow is a service data packet. In other words, a PDU session, an SDF, an Ethernet flow, an IP flow, or at least one QoS flow includes one or more service data packets.

[0173] 3 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application. The method includes the following steps:

[0174] Step 301: A first device transmits first link status detection information to a second device via a link, and in response, the second device receives the first link status detection information.

[0175] The first link status detection information indicates a quantity of service data packets transmitted by the first device over the link to the second device.

[0176] Step 302: The second device obtains a packet loss rate of service data packets on the link based on the first link status detection information.

[0177] For example, the second device may determine a quantity of service data packets sent by the first device to the second device over the link based on the first link status detection information, and then the second device may further obtain a quantity of service data packets received from the first device over the link by the second device, so that the second device may calculate a packet loss rate of the service data packets based on a ratio of the two quantities.

[0178] Step 303: The second device sends a packet loss rate of the service data packet to the first device, and in response, the first device receives the packet loss rate of the service data packet.

[0179] After receiving the packet loss rate of the service data packets, the first device may evaluate the link, to determine a corresponding policy based on the evaluation result, or to report the packet loss rate of the service data packets to another device (such as an SMF or a PCF).

[0180] Based on the above solution, the first device can inform the second device of the quantity of service data packets sent by the first device to the second device on the link by using the link status detection information, so that the second device can quickly calculate the packet loss rate of the service data packets based on the link status detection information. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate can be improved.

[0181] In one implementation method, before step 301, the first device further transmits second link status detection information to the second device by using the link. Correspondingly, the second device receives the second link status detection information, and the first link status detection information specifically indicates a first quantity of service data packets transmitted by the first device to the second device on the link within a time when the first device transmits the second link status detection information and the first device transmits the first link status detection information. In this case, step 302 may specifically be a step of the second device obtaining a packet loss rate of the service data packets on the link within a time when the first device transmits the second link status detection information and the first device transmits the first link status detection information based on the first link status detection information. The second link status detection information and the first link status detection information may be two adjacent link status detection information or two non-adjacent link status detection information.

[0182] The following describes this solution with reference to a concrete example.

[0183] FIG. 4a is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which the first link status detection information and the second link status detection information are two adjacent link status detection information. When the first link status detection information is link status detection information d, the second link status detection information is link status detection information c, when the first link status detection information is link status detection information c, the second link status detection information is link status detection information b, and when the first link status detection information is link status detection information b, the second link status detection information is link status detection information a. The link status detection information d carries the number of service data packets between the link status detection information c and the link status detection information d, i.e., the number of service data packets carried in the link status detection information d is 3. The link status detection information c carries the number of service data packets between the link status detection information b and the link status detection information c, i.e., the number of service data packets carried in the link status detection information c is 2. The link status detection information b carries the number of service data packets between the link status detection information a and the link status detection information b, i.e., the number of service data packets carried in the link status detection information b is 2.

[0184] In this example, the quantity of service data packets transmitted between two adjacent link status detection information is indicated or carried by the later of the two adjacent link status detection information.

[0185] In this example, the second device may calculate the packet loss rate of the service data packets between two adjacent link status detection information. For example, assuming that service data packet 3 and service data packet 7 are lost, that is, the second device does not receive service data packet 3 and service data packet 7, the second device may obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 50%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information c is 0%; The packet loss rate of the service data packets between the link status detection information c and the link status detection information d is 33.3%.

[0186] Of course, the second device may further obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 25%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information d is 28.6%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information d is 20%.

[0187] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or specifically calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time point for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0188] When the first link status detection information is not adjacent to the second link status detection information, the second link status detection information indicates an initial data packet or an initial time for calculating a packet loss rate, i.e., the quantity of service data packets transmitted by the first device indicated by the first link status detection information is calculated by using the second link status detection information as a reference.

[0189] The following describes this solution with reference to a concrete example.

[0190] FIG. 4b is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which link status detection information a is taken as the reference link status detection information. Link status detection information a is also called second link status detection information, and the first link status detection information can be link status detection information b, c, or d. Link status detection information b carries the quantity of service data packets between link status detection information a and link status detection information b, i.e., the quantity of service data packets carried in link status detection information b is 2. Link status detection information c carries the quantity of service data packets between link status detection information a and link status detection information c, i.e., the quantity of service data packets carried in link status detection information c is 4. The link status detection information d carries the quantity of service data packets between the link status detection information a and the link status detection information d, that is, the quantity of service data packets carried in the link status detection information d is seven.

[0191] In this example, the quantity of service data packets carried in one link status detection information is the quantity of service data packets transmitted between the link status detection information and the reference link status detection information.

[0192] In this example, the second device may calculate the packet loss rate of the service data packets between adjacent link status detection information. For example, assuming that service data packet 3 and service data packet 7 are lost, that is, the second device does not receive service data packet 3 and service data packet 7, the second device may obtain the following through calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 50%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 25%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information d is 28.6%.

[0193] Alternatively, the second device may also calculate the number of service data packets transmitted between two adjacent link status detection information based on the number of service data packets carried in each link status detection information to calculate a packet loss rate of the service data packets between two adjacent link status detection information.

[0194] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0195] It should be noted that in this example, different link status detection information may correspond to the same reference link status detection information or may correspond to different reference link status detection information. For example, in the above example, the link status detection information b, c, and d all use the link status detection information a as the reference link status detection information. As another example, in the above example, the link status detection information b and c may use the link status detection information a as the reference link status detection information, and the link status detection information d may use the link status detection information b as the reference link status detection information. In this embodiment of the present application, it is not limited whether the reference link status detection information is fixed link status detection information or multiple link status detection information.

[0196] Optionally, the link status detection information may further carry identification information of reference link status detection information, so that the second device may know which link status detection information is used as a reference for counting the quantity of service data packets carried in the link status detection information. For example, in the above example, the link status detection information b, c, and d may carry identification information of the link status detection information a.

[0197] Of course, a time point before or after the service data packet transmission may be used as the reference time, in which case the quantity of the service data packets transmitted by the first device indicated by the link status detection information (e.g., the first link status detection information) is calculated based on the reference time. In one implementation method, the reference time may be a time point before the transmission time of the initial service data packet. Thus, the first link status detection information in step 301 specifically indicates the third quantity of the service data packets transmitted by the first device to the second device on the link within the time when the first device transmits the initial service data packet on the link and the first device transmits the first link status detection information. In this case, step 302 may specifically be a step in which the second device obtains a packet loss rate of the service data packets on the link within the time when the first device transmits the initial data packet and the first device transmits the first link status detection information based on the first link status detection information.

[0198] The following describes this solution with reference to a concrete example.

[0199] FIG. 4c is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which a time point before the transmission time point of service data packet 1 is used as a reference time. The first link status detection information can be link status detection information a, b, c, or d in this example. Link status detection information a carries the quantity of service data packets between the reference time and link status detection information a, i.e., the quantity of service data packets carried in link status detection information a is 1. Link status detection information b carries the quantity of service data packets between the reference time and link status detection information b, i.e., the quantity of service data packets carried in link status detection information b is 3. The link status detection information c carries the number of service data packets between the reference time and the link status detection information c, i.e., the number of service data packets carried in the link status detection information c is 5. The link status detection information d carries the number of service data packets between the reference time and the link status detection information d, i.e., the number of service data packets carried in the link status detection information d is 8.

[0200] In this example, the quantity of service data packets carried in one link status detection information is the quantity of service data packets transmitted between the link status detection information and the reference time.

[0201] In this example, the second device may calculate the packet loss rate of the service data packets between adjacent link status detection information. For example, assuming that service data packet 3 and service data packet 7 are lost, that is, the second device does not receive service data packet 3 and service data packet 7, the second device may obtain the following through calculation: The packet loss rate of the service data packets between the reference time and the link status detection information a is 0%; The packet loss rate of the service data packets between the reference time and the link status detection information b is 33.3%; The packet loss rate of the service data packets between the reference time and the link status detection information c is 20%; The packet loss rate of the service data packets between the reference time and the link status detection information d is 25%.

[0202] Alternatively, the second device may also calculate the number of service data packets transmitted between two adjacent link status detection information based on the number of service data packets carried in each link status detection information to calculate a packet loss rate of the service data packets between two adjacent link status detection information.

[0203] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0204] In one implementation method, before step 301, the first device further transmits second link status detection information to the second device by using the link, and after step 301, the first device further transmits third link status detection information to the second device by using the link. The third link status detection information indicates a first quantity and a second quantity. The first quantity refers to a quantity of service data packets transmitted by the first device to the second device over the link within a time when the first device transmits the second link status detection information and the first device transmits the first link status detection information. The second quantity refers to a quantity of service data packets transmitted by the first device to the second device over the link within a time when the first device transmits the first link status detection information and the first device transmits the third link status detection information. In this case, step 302 may specifically be a step in which the second device acquires, based on the first link status detection information, a packet loss rate of a service data packet on a link within a time period when the first device transmits the second link status detection information and the first device transmits the third link status detection information, and / or a step in which the second device acquires, based on the first link status detection information, a packet loss rate of a service data packet on a link within a time period when the first device transmits the first link status detection information and the first device transmits the third link status detection information. The second link status detection information and the first link status detection information may be two adjacent link status detection information or two non-adjacent link status detection information.

[0205] The following describes this solution with reference to a concrete example.

[0206] 4d is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which the first link status detection information is link status detection information c. The second link status detection information is link status detection information b, and the third link status detection information is link status detection information d.

[0207] The link status detection information c carries two quantity of service data packets between the link status detection information b and the link status detection information c, and two quantity of service data packets between the link status detection information a and the link status detection information b. The link status detection information d carries three quantity of service data packets between the link status detection information c and the link status detection information d, and two quantity of service data packets between the link status detection information b and the link status detection information c.

[0208] In this example, one link status detection information may carry one or more quantities of service data packets. For example, in the above example, two quantities of service data packets are carried, and of course, three quantities or four quantities may also be carried. Of course, the initial link status detection information may carry one quantity of service data packets.

[0209] In this example, the second device may calculate the packet loss rate of the service data packets between adjacent link status detection information. For example, assuming that service data packet 3 and service data packet 7 are lost, that is, the second device does not receive service data packet 3 and service data packet 7, the second device may obtain the following through calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 50%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information c is 0%; The packet loss rate of the service data packets between the link status detection information c and the link status detection information d is 33.3%.

[0210] Of course, the second device may further obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 25%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information d is 28.6%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information d is 20%.

[0211] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0212] It should be noted that in the above implementation solution, two quantities of service data packets are carried in one link status information. In practical application, three or more quantities of service data packets may be carried in one link status detection information. In this embodiment of the present application, it is not limited that the link status detection information carries the quantity information of service data packets.

[0213] The advantage of carrying multiple quantities of service data packets in one link status detection information is that the impact caused by link status detection information can be reduced, thereby improving the accuracy and speed of packet loss rate detection of service data packets. Figure 4d is used as an example. When link status detection information b is lost, the second device cannot know the quantity of service data packets sent between link status detection information a and link status detection information b, but after receiving link status detection information c, the second device can know the quantity of service data packets sent between link status detection information a and link status detection information b, thereby eliminating the impact caused by the loss of link status detection information b.

[0214] In one implementation method, the first link status detection information in step 301 specifically instructs the first device to send a default quantity of service data packets to the second device over the link. Optionally, the default quantity may be pre-configured on the first device and the second device, or pre-defined in a protocol, or may be notified to the second device after the first device determines the default quantity. For example, instruction information is sent to the second device to indicate the value of the default quantity.

[0215] It should be noted that the default quantity may be dynamically updated, for example, the second device may dynamically inform the first device of the latest default quantity, or another network element, such as an SMF or PCF, may dynamically inform the first device of the latest default quantity.

[0216] The following describes this solution with reference to a concrete example.

[0217] FIG. 4e is a diagram of an example of transmission of link status detection information and service data packets. In this example, multiple service data packets are transmitted sequentially on one link, and one link status detection information is transmitted at intervals of a certain quantity. An example is used in which the default quantity is 100. One link status detection information is transmitted every time 100 service data packets are transmitted. Thus, 100 service data packets are transmitted between link status detection information a and link status detection information b, 100 service data packets are transmitted between link status detection information b and link status detection information c, and so on. In addition, the link status detection information does not need to carry the quantity of transmitted service data packets.

[0218] In this example, the second device may calculate the packet loss rate of the service data packets between adjacent link status detection information. For example, assuming that three service data packets are lost between the link status detection information a and the link status detection information b, and four service data packets are lost between the link status detection information b and the link status detection information c, the second device may obtain the following through calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 3%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information c is 4%.

[0219] Of course, the second device may further obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 3.5%.

[0220] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0221] In one implementation method, before step 301, the first device further transmits second link status detection information to the second device by using the link, and after step 301, the first device further transmits fourth link status detection information to the second device by using the link. The fourth link status detection information indicates a fourth quantity of service data packets transmitted by the first device to the second device on the link within a time when the first device transmits the first link status detection information and the first device transmits the fourth link status detection information. In this case, step 302 may specifically be a step of the second device obtaining a packet loss rate of the service data packets within a time when the first device transmits the second link status detection information and the first device transmits the fourth link status detection information based on the first link status detection information and the fourth link status detection information. The second link status detection information and the first link status detection information may be two adjacent link status detection information or two non-adjacent link status detection information.

[0222] The following describes this solution with reference to a concrete example.

[0223] FIG. 4f is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which the first link status detection information is link status detection information c. The second link status detection information is link status detection information b, and the fourth link status detection information is link status detection information d. An example is used in which the first link status detection information is link status detection information b. The second link status detection information is link status detection information a, and the fourth link status detection information is link status detection information c.

[0224] The link status detection information c carries a quantity of 4 service data packets between the link status detection information a and the link status detection information c. The link status detection information d carries a quantity of 5 service data packets between the link status detection information b and the link status detection information d.

[0225] In this example, the second device may calculate the packet loss rate of the service data packets between the link status detection information. For example, assuming that the service data packet 3 and the service data packet 7 are lost, that is, the second device does not receive the service data packet 3 and the service data packet 7, the second device may obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 25%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information d is 20%.

[0226] Of course, the second device may further obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 50%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information c is 0%; The packet loss rate of the service data packets between the link status detection information c and the link status detection information d is 33.3%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information d is 28.6%.

[0227] Whether the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information or calculates the packet loss rate of the service data packet between two non-adjacent link status detection information depends on a specific implementation method, which is not limited in this embodiment of the present application. In one implementation method, the second device may determine the time for calculating the packet loss rate of the service data packet based on configured parameters such as a packet loss rate detection period and a packet loss rate detection frequency.

[0228] It should be noted that in the above example, when the second device calculates the packet loss rate of the service data packet between two adjacent link status detection information, the packet loss rate of the service data packet can be calculated in a timely manner, so that the first device, the second device, or another device makes a prompt decision based on the packet loss rate. When the second device calculates the packet loss rate of the service data packet between two non-adjacent link status detection information, i.e., when it receives three or more link status detection information, the second device calculates the packet loss rate of the service data packet once, so that the effect caused by the disorder of the service data packet can be reduced, and the accuracy of the packet loss rate calculation of the service data packet is improved. For example, FIG. 4g is a diagram of an example of the transmission of link status detection information and service data packets. In this example, the first device sequentially transmits service data packets 1 to 8 to the second device. The order in which the second device first receives the service data packets is service data packet 1, service data packet 3, service data packet 2, service data packet 4, service data packet 5, service data packet 6, service data packet 7, and service data packet 8. An example is used in which service data packet 7 is lost and all other service data packets are received by the second device. When the second device calculates the packet loss rate of the service data packets between two adjacent link status detection information, the calculated packet loss rate of the service data packets transmitted between the link status detection information a and the link status detection information b is 50%, but the service data packet 2 is not actually lost. Therefore, the packet loss rate of the service data packets transmitted between the link status detection information a and the link status detection information b should be 0%. When the second device calculates the packet loss rate of the service data packets between two non-adjacent link status detection information, for example, it obtains by calculation that the packet loss rate of the service data packets transmitted between the link status detection information a and the link status detection information c is 0%, which is the actual packet loss rate.Therefore, when the second device calculates the packet loss rate of the service data packets between two non-adjacent link status detection information, the impact caused by the disorder of the service data packets can be reduced, and the accuracy of the packet loss rate calculation of the service data packets is improved.

[0229] 5 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application. The method includes the following steps:

[0230] Step 501: A first device transmits fifth link status detection information to a second device via a link, and in response, the second device receives the fifth link status detection information.

[0231] Step 502: The second device determines, based on the fifth link status detection information, a quantity of service data packets received by the second device from the first device over the link.

[0232] Some service data packets may be lost in the transmission process, so the amount of service data packets received by the second device from the first device over the link may be less than the amount of service data packets sent by the first device to the second device over the link.

[0233] Step 503: The second device transmits to the first device a quantity of service data packets received by the second device from the first device over the link, and in response, the first device receives a quantity of service data packets received by the second device from the first device over the link.

[0234] Step 504: The first device determines a packet loss rate of the service data packets on the link based on the quantity of the service data packets.

[0235] For example, the first device and the second device may calculate a packet loss rate of service data packets on the link based on a quantity of service data packets sent by the first device to the second device over the link and a quantity of service data packets received by the second device from the first device over the link, the packet loss rate being based on a ratio of the two quantities.

[0236] Based on the above solution, the second device may inform the first device of the quantity of service data packets received by the second device from the first device over the link by using the link status detection information, so that the first device may quickly calculate the packet loss rate of the service data packets based on the quantity of the service data packets received by the second device from the first device over the link. In addition, since there is no need to parse the service data packets to determine whether the service data packets are lost, the calculation speed of the packet loss rate may be improved.

[0237] In one implementation method, before step 501, the first device further transmits sixth link status detection information to the second device by using the link. Correspondingly, the second device receives the sixth link status detection information, and step 502 may specifically be a step of the second device determining a quantity of service data packets received from the first device on the link by the second device within a time when the first device transmits the sixth link status detection information and the first device transmits the fifth link status detection information (hereinafter referred to as the fifth quantity). Step 504 may specifically be a step of the first device determining a packet loss rate of the service data packets on the link based on the fifth quantity and the sixth quantity. The sixth quantity refers to a quantity of service data packets transmitted by the first device to the second device on the link within a time when the first device transmits the sixth link status detection information and the first device transmits the fifth link status detection information.

[0238] Optionally, the first device further transmits to the second device time information corresponding to the determined quantity of service data packets, where the time information includes a period from when the first device transmits the sixth link status detection information to when the first device transmits the fifth link status detection information. Optionally, the fifth link status detection information and the sixth link status detection information are link status detection data packets, where the time information includes sequence number information corresponding to the link status detection data packets.

[0239] The sixth link status detection information and the fifth link status detection information may be two adjacent link status detection information, or may be two non-adjacent link status detection information.

[0240] The following describes this solution with reference to a concrete example.

[0241] FIG. 6 is a diagram of an example of transmission of link status detection information and service data packets. In this example, service data packet 1 to service data packet 8 are transmitted sequentially on one link. In addition, link status detection information a is transmitted after service data packet 1, link status detection information b is transmitted after service data packet 3, link status detection information c is transmitted after service data packet 5, and link status detection information d is transmitted after service data packet 8. An example is used in which the fifth link status detection information and the sixth link status detection information are two adjacent link status detection information. When the fifth link status detection information is link status detection information d, the sixth link status detection information is link status detection information c, when the fifth link status detection information is link status detection information c, the sixth link status detection information is link status detection information b, and when the fifth link status detection information is link status detection information b, the sixth link status detection information is link status detection information a.

[0242] For example, assuming that service data packet 3 and service data packet 7 are lost, i.e., the second device does not receive service data packet 3 and service data packet 7, the second device may send the following information to the first device: The quantity of service data packets received between the link status detection information a and the link status detection information b is 1; The number of service data packets received between the link status detection information b and the link status detection information c is 2; The number of service data packets received between the link status detection information c and the link status detection information d is two.

[0243] Alternatively, the second device may transmit the following information to the first device: The number of service data packets received between the link status detection information a and the link status detection information c is 3; The number of service data packets received between the link status detection information a and the link status detection information d is 5; The number of service data packets received between the link status detection information b and the link status detection information d is four.

[0244] Whether the second device specifically transmits the quantity of service data packets received between two adjacent link status detection information to the first device, or transmits the quantity of service data packets received between two non-adjacent link status detection information to the first device depends on a specific implementation method, which is not limited in this embodiment of the present application.

[0245] The first device may obtain by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information b is 50%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information c is 0%; The packet loss rate of the service data packets between the link status detection information c and the link status detection information d is 33.3%.

[0246] Of course, the first device may further obtain the following by calculation: The packet loss rate of the service data packets between the link status detection information a and the link status detection information c is 25%; The packet loss rate of the service data packets between the link status detection information a and the link status detection information d is 28.6%; The packet loss rate of the service data packets between the link status detection information b and the link status detection information d is 20%.

[0247] In one implementation method, in any of the implementation solutions of FIG. 3 or FIG. 5, for each link status detection information sent by the first device, after receiving the link status detection information, the second device sends response information to the first device for the link status detection information, and the response information can also be one link status detection information. For example, in any of the implementation solutions corresponding to FIG. 3, after obtaining the packet loss rate of the service data packet by calculation, the second device may add the packet loss rate of the service data packet to the response information. As another example, in any of the implementation solutions corresponding to FIG. 5, the second device adds the quantity of received service data packets to the response information.

[0248] In one implementation method, in either the implementation solution of FIG. 3 or FIG. 5, when sending link status detection information to the second device, the first device may add identification information to the link status detection information, and the identification information may include a procedure transport identifier (PTI), or may include a procedure transport identifier and a sequence number.

[0249] For example, when the identification information carried in the link status detection information sent by the first device to the second device includes a procedure transport identifier (PTI), the response information sent by the second device to the first device to the link status detection information also carries the procedure transport identifier. In this solution, the function of the procedure transport identifier is as follows: first, the procedure transport identifier is used to identify the link status detection information, i.e., to distinguish different link status detection information, second, the procedure transport identifier is used to sort different link status detection information, and third, the procedure transport identifier is used to associate the link status detection information with the response information to the link status detection information. For example, the link status detection information sent by the first device to the second device is, in sequence, link status detection information 1 (PTI-1), link status detection information 2 (PTI-2), link status detection information 3 (PTI-3), and link status detection information 4 (PTI-4), and the response information sent by the second device is, in sequence, link status detection information 1' (PTI-1), link status detection information 2' (PTI-2), link status detection information 3' (PTI-3), and link status detection information 4' (PTI-4). For example, if the second device does not receive the link status detection information 2, the second device may infer based on PTI-1, PTI-3, and PTI-4 that the link status detection information 2 corresponding to PTI-2 has not been received.

[0250] As another example, when the identification information carried in the link status detection information sent by the first device to the second device includes a procedure transport identifier (PTI) and a sequence number, the response information sent by the second device to the first device for the link status detection information also carries the procedure transport identifier and the sequence number. The procedure transport identifier in the link status detection information sent by the first device and the procedure transport identifier in the receiving response information for the link status detection information may be the same or different, and the sequence number in the link status detection information sent by the first device and the sequence number in the receiving response information for the link status detection information may be the same or different. In this solution, the function of the procedure transport identifier is as follows: first, the procedure transport identifier is used to identify the link status detection information, i.e., to distinguish different link status detection information, and second, the procedure transport identifier is used to associate the link status detection information with the response information for the link status detection information. The sequence number is used to sort different link status detection information. For example, the link status detection information transmitted by a first device to a second device is, in sequence, link status detection information 1 (PTI-a, SN-1), link status detection information 2 (PTI-b, SN-2), link status detection information 3 (PTI-c, SN-3), and link status detection information 4 (PTI-d, SN-4), and the response information transmitted by the second device to the first device in response to the received link status detection information is, in sequence, link status detection information 1' (PTI-a, SN-1'), link status detection information 2' (PTI-b, SN-2'), link status detection information 3' (PTI-c, SN-3'), and link status detection information 4' (PTI-d, SN-4'). SN-1 and SN-1' may be the same or different, SN-2 and SN-2' may be the same or different, SN-3 and SN-3' may be the same or different, and SN-4 and SN-4' may be the same or different.Optionally, the response information sent by the second device to the first device in response to the received link status detection information may alternatively not carry a sequence number. For example, in the above example, SN-1', SN-2', SN-3', and SN-4' are not carried. For example, if the second device does not receive link status detection information 2, the second device may infer based on SN-1, SN-3, and SN-4 that the link status detection information 2 corresponding to PTI-2 has not been received.

[0251] In one implementation method, when calculating the packet loss rate of the service data packet, the first device or the second device may take into account the loss status of the link status detection information, or may not take into account the loss status of the link status detection information. After transmitting the link status detection information, the first device may determine whether the transmitted link status detection information is lost based on whether response information to the link status detection information is received. The second device may determine whether one or more link status detection information are lost based on identification information (the identification information may include a procedure transport identifier, or may include a procedure transport identifier and a sequence number) in the multiple received link status detection information.

[0252] Optionally, in this embodiment of the present application, the link status detection information may be a link status detection data packet. When sending the link status detection data packet, the first device may add a PMF request message to the link status detection data packet. The PMF request message carries identification information (the identification information may include a procedure transport identifier, or may include a procedure transport identifier and a sequence number). Optionally, the PMF request message may further carry a quantity indicating a transmission service data packet. For specific implementation methods, please refer to the description in the preceding embodiment. After receiving the link status detection data packet, the second device sends response information to the link status detection information to the first device, and the response information is also a link status detection data packet, and the link status detection data packet carries a PMF response message, and the procedure transport identifier carried in the PMF response message is the same as the procedure transport identifier carried in the PMF request message, so that the first device can identify the correspondence between the received link status detection information and the transmitted link status detection information. Optionally, the PMF response message carries the quantity of the service data packets received by the second device from the first device, or the packet loss rate of the service data packets. For specific implementation methods, please refer to the description in the above embodiment.

[0253] In one implementation method, when a UE or a UPF calculates a packet loss rate of a QoS flow, the PMF of the UE or the UPF may determine an identifier (i.e., a QoS flow identity (QFI)) of the QoS flow to which the service data packet belongs, i.e., determine the QoS flow to which the transmitted service data packet or the received service data packet belongs, and then count or calculate the packet loss rate of the service data packet of the corresponding QoS flow. For example, as follows:

[0254] For a downlink service flow, after receiving a downlink service data packet on a link, the access chip of the UE sends the downlink service data packet to the PMF of the UE. The PMF determines the QFI of the QoS flow to which the downlink service data packet belongs based on a QoS policy (i.e., a QoS rule). The above QoS rule is the same as that of the current technology, and includes a correspondence between service data flow (SDF) description information and a QFI. Alternatively, after receiving a downlink service data packet on a link, the access chip of the UE parses a service data adaptation protocol (SDAP) layer of the downlink service data packet, obtains the QFI carried in the SDAP layer, and sends the QFI to the PMF. Optionally, when the packet loss rates of different links corresponding to different access technologies need to be calculated, the access chip of the UE sends an access technology indication corresponding to the transmission link of each downlink service data packet to the PMF of the UE.

[0255] For a downlink service flow, after the UPF receives a downlink service data packet, the PMF determines a QFI corresponding to the downlink service data packet based on a policy (e.g., QER) received on the N4 interface, and counts the downlink data packet corresponding to the QFI when sending the downlink service data packet to the UE.

[0256] For an uplink service flow, after the PMF of the UE receives a service data packet generated by an upper layer application, the PMF determines a QFI corresponding to the service data packet based on a QoS rule, and counts the service data packets corresponding to the QFI.

[0257] For an uplink service flow, after receiving an uplink service data packet on the link, the UPF sends the uplink data packet to the PMF of the UPF, and the PMF determines the QFI to which the uplink service data packet belongs based on the policy (e.g., QoS enforcement rule (QER)) received on the N4 interface. Alternatively, after receiving an uplink service data packet on the link, the UPF obtains the QFI carried in the general packet radio service (GPRS) tunneling protocol-user (GTP-U) layer of the service data packet, and sends the QFI to the PMF of the UPF.

[0258] In one implementation method, when the UE or UPF calculates the packet loss rate of at least one QoS flow, the UE may obtain data radio bearer (DRB) information corresponding to the QoS flow based on the current technology. That is, at least one QoS flow on the air interface side is aggregated to one DRB link. The access chip of the UE sends the correspondence between the DRB and the QFI(s) to the PMF of the UE. The PMF of the UE counts the quantity of downlink service packets received on the DRB link and calculates the packet loss rate at the DRB granularity. In addition, the UE may send at least one QoS flow information, e.g., QFI(s), aggregated to one DRB to the UPF, and the UPF may calculate the quantity or packet loss rate of service data packets transmitted or received on multiple QoS flows. For how the UPF or the UE determines the QoS flow to which the service data packet belongs, please refer to the above description.

[0259] Figure 7 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application. The method may be implemented in combination with the embodiment corresponding to Figure 3 and / or the embodiment corresponding to Figure 5, or in combination with another embodiment, or may be implemented separately. This is not limited in the present application. Please note that in the following description, the first device acts as a sender of service data packets, and the second device acts as a receiver of service data packets.

[0260] The method includes the following steps.

[0261] Step 701: The SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0262] Alternatively, it is understood that the SMF determines that link status detection needs to be performed for the service flow.

[0263] In one implementation method, when a service flow includes at least one QoS flow, and the QoS flow includes at least one service data flow, or the service flow includes a service data flow, the SMF may determine that link status detection needs to be performed on the link on which the service flow is located according to any one of the following methods:

[0264] Method 1: When the steering function of a service data flow in a service flow is determined to be ATSSS-LL, the SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0265] Method 2: When the SMF determines that the steering function of a service data flow in a service flow is ATSSS-LL and the steering mode of the service data flow is load balancing mode, the SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0266] Method 3: When the SMF determines that the steering function of a service data flow in a service flow is ATSSS-LL and the steering mode of the service data flow is minimum delay mode, the SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0267] Method 4: When the steering function of a service data flow in a service flow is ATSSS-LL and the steering mode of the service data flow is determined to be priority-based mode, the SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0268] Method 5: When the steering function of a service data flow in a service flow is ATSSS-LL and the steering mode of the service data flow is determined to be active-standby mode, the SMF determines that link status detection needs to be performed on the link on which the service flow is located.

[0269] Method 6: When the SMF determines that a link status threshold for the service flow has been received from the PCF, the SMF determines that link status detection needs to be performed on the link on which the service flow is located, and the link status threshold includes a packet loss rate threshold.

[0270] Step 702: The SMF sends a link status detection indication to the first device and / or the second device. In response, the first device and / or the second device receives the link status detection indication.

[0271] The link status detection instruction is for enabling a link status detection function, and the link status detection function includes a packet loss rate detection function. Here, "enabling the link status detection function" may be understood as an instruction for enabling the link status detection function.

[0272] Based on the above solution, the SMF may send a link status detection indication to the first device and / or the second device to enable a link status detection function of the first device and / or the second device, so that the first device and / or the second device may quickly and accurately detect a packet loss rate of service data packets on the link based on the enabled link status detection function.

[0273] In one implementation method, the SMF may further send identification information of the service flow to the first device and / or the second device, where the identification information includes a PDU session identifier, a service data flow description information, an IP5 tuple information, an Ethernet flow description information, or at least one QFI. The link status detection indication in step 702 is specifically for enabling a link status detection function of the service flow.

[0274] In one implementation method, the SMF may allocate a corresponding IP address and / or port number to the link status detection function, and then the SMF configures the IP address and / or port number on the first device and / or the second device. For example, the link status detection indication includes the IP address and / or port number. Optionally, when the IP address and / or port number are configured with QoS granularity, the SMF further sends a QFI corresponding to the IP address and / or port number to the first device and / or the second device to instruct them to allocate the IP address and / or port number to the link status detection function of the QoS flow indicated by the QFI.

[0275] In another implementation method, the first device (or the second device) may allocate an IP address and / or a port number corresponding to the link status detection function, and then send the IP address and / or the port number to the SMF, which then configures the IP address and / or the port number in the second device (or the first device). Optionally, when the IP address and / or the port number are configured with QoS granularity, the first device (or the second device) further sends a QFI corresponding to the IP address and / or the port number to the SMF, and the SMF then further sends the QFI to the second device (or the first device) to instruct it to allocate the IP address and / or the port number to the link status detection function of the QoS flow indicated by the QFI.

[0276] In one implementation method, the SMF may further send a counting instruction to the first device, where the counting instruction instructs the first device to count the quantity of service data packets transmitted by the first device to the second device over the link. For example, the first device may carry the quantity of transmitted service data packets in the transmitted link status detection information (e.g., one or more of the first link status detection information, the second link status detection information, the third link status detection information, the fourth link status detection information, the fifth link status detection information, or the sixth link status detection information in the above example).

[0277] In one implementation method, the SMF sends a counting instruction to the second device, where the counting instruction instructs the second device to count the number of service data packets sent by the first device to the second device over the link, or the counting instruction instructs the second device to stop counting the number of service data packets received over the link, reset a counter, and store or send to the first device the number of service data packets received over the link when receiving link status detection information, or the counting instruction instructs the second device to calculate the number of service data packets received over the link and store or send to the first device the number of service data packets received over the link when receiving link status detection information.

[0278] In one implementation method, the SMF may further send a link status report indication to the first device and / or the second device, where the link status report indication instructs the first device and / or the second device to report a packet loss rate of the service data packets. Alternatively, the SMF sends a link status report frequency to the first device and / or the second device, where the link status report frequency instructs the frequency of reporting the packet loss rate of the service data packets. Alternatively, the SMF sends a link status report periodicity to the first device and / or the second device, where the link status report periodicity instructs the period of reporting the packet loss rate of the service data packets. Thus, the first device and / or the second device may report the detected packet loss rate of the service data packets to the SMF, the PCF, or another network element based on the link status report indication, the link status report frequency, or the link status report periodicity.

[0279] In one implementation method, when the first device calculates a packet loss rate of the service data packets, the SMF may further send a packet loss rate detection indication to the first device, where the packet loss rate detection indication instructs the first device to calculate a packet loss rate of the service data packets when receiving from the second device a quantity of received service data packets counted by the second device.

[0280] In one implementation method, when the second device calculates the packet loss rate of the service data packets, the SMF may further send a packet loss rate detection indication to the second device, where the packet loss rate detection indication instructs the second device to calculate the packet loss rate of the service data packets when receiving the link status detection information. Alternatively, the packet loss rate detection indication instructs the second device to calculate the quantity of service data packets received on the link when receiving the link status detection information, and calculate the packet loss rate of the service data packets by using the quantity of service data packets received on the link. Alternatively, the packet loss rate detection indication instructs the second device to stop counting the quantity of service data packets received on the link when receiving the link status detection information, reset the counter, and calculate the packet loss rate of the service data packets by using the counted quantity of service data packets received on the link.

[0281] In order to facilitate understanding of the contents of the embodiment of the present application, the following describes the configuration process shown in Fig. 7 with reference to a specific example. Fig. 8 is a schematic diagram of a packet loss rate detection method according to an embodiment of the present application. In this embodiment, an example in which the packet loss rate at QoS granularity is calculated is used for explanation.

[0282] The method includes the following steps.

[0283] Step 801: The UE initiates a PDU session establishment or update procedure.

[0284] For example, when the UE initiates a PDU session establishment procedure, the UE sends a non-access stratum (NAS) message to the AMF by using the RAN, and the NAS message includes a PDU session establishment request message. After receiving the NAS message, the AMF forwards the PDU session establishment request message to the SMF.

[0285] As another example, when the UE initiates a PDU session update procedure, the UE sends a NAS message to the AMF by using the RAN. The NAS message includes a PDU session modification request message. After receiving the NAS message, the AMF forwards the PDU session modification request message to the SMF.

[0286] Step 802: The SMF sends a policy request to the PCF. In response, the PCF receives the policy request.

[0287] Step 803: The PCF determines the steering capability, steering mode, and link status threshold of the service data flow.

[0288] The determined steering function may be, for example, at least one of ATSSS-LL and MPTCP.

[0289] The determined steering mode may be, for example, one of a minimum latency mode, a load balancing mode, an active standby mode, or a priority-based mode.

[0290] The link condition thresholds include a maximum packet loss rate, and optionally further include a maximum RTT.

[0291] Step 804: The PCF sends a policy response to the SMF, where the policy response carries the service data flow description information, the steering mode, the steering function, and the link status threshold. In response, the SMF receives the policy response.

[0292] The service data flow description information is for matching a service data flow.

[0293] Optionally, the PCF further transmits a link status detection frequency or a link status detection cycle to the SMF. The link status detection frequency indicates how often to detect the link status, for example, 5 times / minute, i.e., the detection is performed 5 times per minute. The link status detection cycle indicates a cycle to detect the link status, for example, 5 seconds, i.e., the detection is performed every 5 seconds.

[0294] Optionally, the PCF further sends a link status reporting instruction, a link status reporting frequency, or a link status reporting period to the SMF. The link status reporting instruction instructs to report link status information. The link status reporting frequency instructs how often to report the link status information, e.g., twice per minute. That is, the report is made twice per minute. The link status reporting period instructs how often to report the link status information, e.g., 10 seconds. That is, the report is made once every 10 seconds. The link status information includes a packet loss rate. Optionally, the link status information further includes a delay, a bandwidth, etc.

[0295] Step 805: The SMF determines that link status detection needs to be performed on the link on which the QoS flow corresponding to the service data flow is located.

[0296] The SMF may determine that link status detection needs to be performed on the link on which the QoS flow corresponding to the service data flow is located based on at least one of the steering function, steering mode, or link status threshold of the service data flow.

[0297] For example, when the steering function of a service data flow received by the SMF is ATSSS-LL, the SMF determines that link status detection needs to be performed on the link on which the QoS flow corresponding to the service data flow is located.

[0298] As another example, when the steering function of a service data flow received by the SMF is ATSSS-LL and the steering mode is one of a load balancing mode, a priority-based mode, an active standby mode, or a minimum latency mode, the SMF determines that link status detection needs to be performed on the link on which the QoS flow corresponding to the service flow is located.

[0299] As another example, when the SMF determines that a link status threshold for a service data flow has been received, the SMF determines that link status detection needs to be performed on the link on which the QoS flow corresponding to the service flow is located.

[0300] Step 806: The SMF sends a session request / update message to the UPF, where the session request / update message carries a link status detection indication and a QoS flow identity (QFI). In response, the UPF receives the session request / update message.

[0301] When a session request message is sent, the session request message may be, for example, a packet forwarding control protocol (PFCP) session request message. When a session update message is sent, the session update message may be, for example, a PFCP session update message.

[0302] The link status detection indication is for enabling a link status detection function for the QoS flow. That is, the link status detection is performed based on the QoS granularity. In a particular implementation method, the link status detection indication may include a PMF enablement indication or a packet loss rate detection indication. The PMF enablement indication is for enabling a PMF-based link status detection function of the UPF, and the packet loss rate detection indication is for enabling a packet loss rate detection function of the UPF. Optionally, the link status detection indication further includes one or more of an RTT detection indication, a jitter detection indication, and a bandwidth detection indication. The RTT detection indication is for enabling the UPF to perform RTT detection, the jitter detection indication is for enabling the UPF to perform jitter detection, and the bandwidth detection indication is for enabling the bandwidth detection function.

[0303] Optionally, the SMF may further allocate IP addresses and port numbers for the link status detection function performed on the UPF, and send the IP addresses and port numbers to the UPF by using a session request / update message. The IP addresses and port numbers are allocated based on the QoS flow granularity. In this case, multiple IP addresses and multiple port numbers may be allocated, and one IP address corresponds to one port number.

[0304] Optionally, the SMF may further determine a link status detection frequency or a link status detection period at QoS flow granularity and send the link status detection frequency or the link status detection period to the UPF by using a session request / update message. It should be noted that if the link status detection frequency or the link status detection period is carried in step 804, the link status detection frequency or the link status detection period determined by the SMF may be determined based on the link status detection frequency or the link status detection period received in step 804, or may be determined by the SMF based on a local policy. If the link status detection frequency or the link status detection period is not carried in step 804, the link status detection frequency or the link status detection period determined by the SMF may be determined by the SMF based on a local policy.

[0305] Optionally, the SMF may further determine a link status reporting indication, a link status reporting frequency, or a link status reporting period at QoS flow granularity, and send the link status reporting indication, the link status reporting frequency, or the link status reporting period to the UPF by using a session request / update message. It should be noted that if a link status reporting indication, a link status reporting frequency, or a link status reporting period is carried in step 804, the link status reporting indication, the link status reporting frequency, or the link status reporting period determined by the SMF may be determined based on the link status reporting indication, the link status reporting frequency, or the link status reporting period received in step 804, or may be determined by the SMF based on a local policy. If a link status reporting indication, a link status reporting frequency, or a link status reporting period is not carried in step 804, the link status reporting indication, the link status reporting frequency, or the link status reporting period determined by the SMF may be determined by the SMF based on a local policy.

[0306] Step 807: The UPF enables the link status detection function based on the received link status detection indication, and allocates an IP address and a port number to the link status detection function.

[0307] It should be noted that if an IP address and a port number are carried in step 806, the UPF uses the received IP address and the received port number as the IP address and the port number of the link status detection function. The UPF receives the IP address and the port number with QoS flow granularity. Therefore, the SMF allocates the IP address and the port number to the link status detection function based on the QoS flow granularity. In other words, each QoS flow corresponds to one IP address and one port number.

[0308] If the IP address and port number are not conveyed in step 806, the UPF allocates an IP address and port number to the link status detection function based on local policy.

[0309] Step 808: The UPF sends a session request / update response to the SMF. In response, the SMF receives the session request / update response.

[0310] If the IP address and port number are not carried in step 806, the UPF allocates an IP address and port number to the link status detection function based on local policy in step 807. In this case, the session request / update response in step 808 may carry the IP address and port number allocated by the UP based on local policy.

[0311] Step 809: The SMF sends an N2 message to the RAN, where the N2 message carries a PDU session identifier and a PDU session establishment / update success message. In response, the RAN receives the N2 message.

[0312] The PDU Session Establishment / Update Success message carries a link status detection indication and a QFI.

[0313] Optionally, the PDU session establishment / update success message further includes a link status detection frequency or a link status detection period at QoS flow granularity. For details, please refer to the description of step 806. The details will not be described again here.

[0314] Optionally, the PDU session establishment / update success message further includes a link status reporting instruction at QoS flow granularity, a link status reporting frequency, or a link status reporting period. For details, please refer to the description of step 806. The details will not be described again here.

[0315] Optionally, the N2 message further includes an IP address and a port number of the link status detection function and a QFI, the QFI having a corresponding relationship with the IP address and the port number.

[0316] Since link status detection at QoS flow granularity is performed, the PDU Session Establishment / Update Success message may further carry service data flow description information (or service data flow template) and a counting instruction, where the counting instruction instructs the UE to count the amount of service data packets sent by the UE to the UPF on the link, the counting instruction instructs the UE to count the amount of service data packets sent by the UPF on the link to the UE, the counting instruction instructs the UE to stop counting the amount of service data packets received on the link, reset the counter, and store or send the amount of service data packets received on the link to the UPF when receiving the link status detection information, or the counting instruction instructs the UE to calculate the amount of service data packets received on the link, and store or send the amount of service data packets received on the link to the UPF when receiving the link status detection information.

[0317] In addition, the PDU session establishment / update success message may further carry PMF service data flow description information (or PMF service data flow template) and packet loss rate related information, where the packet loss rate related information includes a packet loss rate detection indication. The packet loss rate detection indication instructs the UE to calculate a packet loss rate of the service data packets when receiving from the UPF a number of received service data packets counted by the UPF. Alternatively, the packet loss rate detection indication instructs the UE to calculate a packet loss rate of the service data packets when receiving link status detection information. Alternatively, the packet loss rate detection indication instructs the UE to calculate a number of service data packets received on the link when receiving link status detection information, and calculate a packet loss rate of the service data packets by using the number of service data packets received on the link. Alternatively, the packet loss rate detection indication instructs the UE to stop counting the number of service data packets received on the link when receiving link status detection information, reset the counter, and calculate a packet loss rate of the service data packets by using the counted number of service data packets received on the link.

[0318] Step 810: The RAN sends a PDU session establishment / update success message to the UE. In response, the UE receives the PDU session establishment / update success message.

[0319] Step 811: The RAN allocates session-related resources, for example, allocates RAN-side tunnel identification information (including IP address and tunnel endpoint identifier (TEID)).

[0320] Step 812: The RAN sends an N2 message to the SMF, and the N2 message carries the tunnel identification information on the RAN side. In response, the SMF receives the N2 message.

[0321] Step 813: The SMF sends a session request / update message to the UPF, where the session request / update message carries the tunnel identification information on the RAN side. In response, the UPF receives the session request / update message.

[0322] When a session request message is sent, the session request message may be, for example, a PFCP session request message.When a session update message is sent, the session update message may be, for example, a PFCP session update message.

[0323] Since link status detection at QoS flow granularity is performed, the session request / update message may further carry service data flow description information (or service data flow template) and a counting instruction, where the counting instruction instructs the UPF to count the amount of service data packets sent by the UPF on the link to the UE, the counting instruction instructs the UPF to count the amount of service data packets sent by the UE on the link to the UPF, the counting instruction instructs the UPF to stop counting the amount of service data packets received on the link, reset the counter, and store or send the amount of service data packets received on the link to the UE when receiving the link status detection information, or the counting instruction instructs the UPF to calculate the amount of service data packets received on the link, and store or send the amount of service data packets received on the link to the UE when receiving the link status detection information.

[0324] In addition, the session request / update message may further carry PMF service data flow description information (or PMF service data flow template) and packet loss rate related information, where the packet loss rate related information includes a packet loss rate detection indication. The packet loss rate detection indication instructs the UPF to calculate a packet loss rate of the service data packets when receiving from the UE a number of received service data packets counted by the UE. Alternatively, the packet loss rate detection indication instructs the UPF to calculate a packet loss rate of the service data packets when receiving link status detection information. Alternatively, the packet loss rate detection indication instructs the UPF to calculate a number of service data packets received on the link when receiving link status detection information, and calculate a packet loss rate of the service data packets by using the number of service data packets received on the link. Alternatively, the packet loss rate detection indication instructs the UPF to stop counting the number of service data packets received on the link when receiving link status detection information, reset the counter, and calculate a packet loss rate of the service data packets by using the counted number of service data packets received on the link.

[0325] Step 814: The UPF sends a session request / update response to the SMF. In response, the SMF receives the session request / update response.

[0326] Based on the above solution, the link status detection functions of the UE and the UPF are enabled, and information related to link status detection is configured for the UE and the UPF, so that the UE and the UPF can quickly and accurately detect the packet loss rate of service data packets on the link based on the enabled link status detection functions.

[0327] 9 is a schematic diagram of a communication device according to an embodiment of the present application. The device is configured to perform the steps performed by the first device, the second device, or the session management network element in the above-mentioned embodiment. As shown in FIG. 9, the device 900 includes a transceiver unit 910 and a processing unit 920.

[0328] Optionally, the communication device 900 may further include a storage unit. The storage unit is configured to store data or instructions (which may also be referred to as code or program). The aforementioned units may interact with or be connected to the storage unit to perform corresponding methods or functions. For example, the processing unit 920 may read data or instructions in the storage unit so that the communication device performs the method in the aforementioned embodiment.

[0329] It should be understood that the division of units in the device is merely a logical division of functions. In actual implementation, the front or part of the units may be integrated into one physical entity or may be physically separated. In addition, all units in the device may be implemented in the form of a processing element calling software, or in the form of hardware, or some units may be implemented in the form of a processing element calling software and some units are implemented in the form of hardware. For example, each unit may be an independently located processing element or may be integrated into a chip of the device for implementation. In addition, each unit may alternatively be stored in a memory in the form of a program to be called by a processing element of the device to perform the function of the unit. In addition, all or some of the units may be integrated or implemented independently. The processing element here may be called a processor, and may be an integrated circuit having signal processing capabilities. In implementation, the steps in the above-mentioned method or the above-mentioned units may be implemented by using integrated logic circuits of hardware in the processor element, or in the form of software called by the processing element.

[0330] In one example, the units in any one of the aforementioned devices may be one or more integrated circuits configured to perform the aforementioned method, such as one or more application specific integrated circuits (ASICs), one or more microprocessors (digital signal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, if the units in the device can be implemented in a form that schedules a program by a processing element, the processing element may be a general-purpose processor, such as a central processing unit (CPU), or another processor that can call a program. As yet another example, the units may be integrated and implemented in a form of a system-on-a-chip (SOC).

[0331] The aforementioned transceiver unit 910 is an interface circuit of the device, configured to receive signals from or transmit signals to another device. For example, if the device is implemented in the form of a chip, the transceiver unit 910 is an interface circuit of the chip configured to receive signals from or transmit signals to another chip or device.

[0332] 10 is a schematic diagram of a communication device according to an embodiment of the present application. The communication device is configured to perform the operations of the first device, the second device, or the session management network element in the above-mentioned embodiments. As shown in FIG. 10, the communication device includes a processor 1010 and an interface 1030. Optionally, the communication device further includes a memory 1020. The interface 1030 is configured to communicate with another device.

[0333] The method performed by the first device, the second device, or the session management network element in the aforementioned embodiment may be implemented by the processor 1010 by invoking a program stored in a memory (which may be the memory 1020 in the first device, the second device, or the session management network element, or may be an external memory). That is, the first device, the second device, or the session management network element may include the processor 1010. The processor 1010 invokes the program in the memory to perform the method performed by the first device, the second device, or the session management network element in the aforementioned method embodiment. The processor here may be an integrated circuit having signal processing capabilities, for example a CPU. The first device, the second device, or the session management network element may be implemented by one or more integrated circuits configured to perform the aforementioned method, for example one or more ASICs, one or more DSPs, one or more FPGAs, or a combination of at least two of the integrated circuit forms. Alternatively, the aforementioned implementation methods may be combined.

[0334] Specifically, the functions / implementation processes of the transceiver unit 910 and the processing unit 920 of Figure 9 may be implemented by the processor 1010 in the communication device 1000 shown in Figure 10 invoking computer-executable instructions stored in the memory 1020. Alternatively, the functions / implementation processes of the processing unit 920 of Figure 9 may be implemented by the processor 1010 in the communication device 1000 shown in Figure 10 invoking computer-executable instructions stored in the memory 1020, and the functions / implementation processes of the transceiver unit 910 of Figure 9 may be implemented by the interface 1030 in the communication device 1000 shown in Figure 10.

[0335] Those skilled in the art will understand that various numbers such as "first" and "second" in this application are used merely for distinction to facilitate description, and are not used to limit the scope of the embodiments of this application or to indicate a sequence. The term "and / or" describes an association relationship to describe associated objects, and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A is present, both A and B are present, and only B is present. The character " / " generally indicates an "or" relationship between associated objects. "At least one" means one or more. At least two means two or more. "At least one," "any one," or similar expressions indicate any combination of items, including a singular item or any combination of multiple items. For example, at least one of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural. "Plural" means two or more, as with other quantifiers.

[0336] It should be understood that the sequence numbers of the above processes do not mean the execution order in various embodiments of the present application. The execution order of the processes should be determined based on the functions and internal logic of the processes, and should not be construed as a limitation on the implementation process of the embodiments of the present application.

[0337] It will be clearly understood by those skilled in the art that for the purpose of convenience of description, the detailed operation processes of the above-mentioned systems, devices and units should be referred to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again here.

[0338] All or part of the above-mentioned embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When software is used to implement the above-mentioned embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in full or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired manner (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless manner (e.g., infrared, radio wave, microwave). The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or data center, incorporating one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state disks (SSDs)).

[0339] The various exemplary logic units and circuits described in the embodiments of this application may implement or operate the described functions by using a general purpose processor, a digital signal processor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. The general purpose processor may be a microprocessor. Optionally, the general purpose processor may also be any conventional processor, controller, microprocessor, or state machine. The processor may also be implemented by a combination of computing devices, such as a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors with a digital signal processor core, or any other similar configuration.

[0340] The steps of the method or algorithm described in the embodiments of the present application may be embodied directly in hardware, in a software unit executed by a processor, or in a combination thereof. The software unit may be stored in a Random Access Memory (RAM), a flash memory, a Read-Only Memory (ROM), an EPROM memory, an EEPROM memory, a register, a hard disk, a removable magnetic disk, a CD-ROM, or any other form of storage medium in the art. For example, the storage medium may be connected to the processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may be located in an ASIC.

[0341] These computer program instructions may also be loaded into a computer or another computer-programmable processing device such that a sequence of operations and steps are performed on the computer or another programmable device, thereby generating a computer-implemented process. Thus, the instructions executed on the computer or another programmable device provide steps for implementing a particular function within one or more processes of the flowcharts and / or one or more blocks of the block diagrams.

[0342] In one or more exemplary designs, the functions described in this application may be implemented by using hardware, software, firmware, or any combination thereof. If the functions are implemented by software, the functions may be stored on a computer-readable medium or transmitted to the computer-readable medium in the form of one or more instructions or cores. Computer-readable media includes computer storage media and communication media that enable a computer program to move from one place to another. A storage medium may be any available medium that can be accessed by any general-purpose or special-purpose computer. For example, such computer-readable media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, disk storage, or other magnetic storage, or any other medium that can be configured to hold or store program code, whether in the form of instructions or data structures or in a form that can be read by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, any connection may be properly defined as a computer-readable medium. For example, software is included in the defined computer readable medium if it is transmitted from a website, server, or another remote resource using coaxial cable, fiber optic computer, twisted pair, digital subscriber line (DSL), or by wireless methods such as infrared, radio, or microwave. Disk and disc include compact disc, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. A disc typically copies data in a magnetic manner, and a disk typically copies data optically in a laser manner. Combinations of the above may also be included in computer readable medium.

[0343] In one or more of the above examples, those skilled in the art should understand that the functions described in this application may be implemented by hardware, software, firmware, or any combination thereof. If the functions are implemented by software, the functions described above may be stored in a computer-readable medium or transmitted as one or more instructions or codes in a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any medium that allows a computer program to be transmitted from one place to another. Storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0344] In the above specific implementation methods, the objectives, technical solutions and beneficial effects of the present application are further described in detail. It should be understood that the above description is merely a specific implementation method of the present application, and is not intended to limit the protection scope of the present application. Modifications, equivalent replacements, improvements, etc. made based on the technical solutions of the present application shall be included in the protection scope of the present application. According to the above description in this specification in the present application, the technology in the art may use or implement the contents of the present application. Modifications based on the contents of the disclosure shall be deemed self-evident in the art. The basic principles described in this application may be applied to other variations without departing from the essence and scope of the present application. Therefore, the contents disclosed in the present application are not limited to the described embodiments and designs, but may be extended to the maximum extent consistent with the principles of the present application and the novel features of the disclosure.

[0345] Although the present application has been described with reference to certain features and embodiments thereof, it is clear that various modifications and combinations may be made to the present application without departing from the spirit and scope of the present application. Correspondingly, the present specification and the accompanying drawings are merely exemplary descriptions of the present application as defined by the appended claims, and any or all of the modifications, variations, combinations, or equivalents encompassing the scope of the present application are to be regarded as being included therein. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the scope of the present application. Thus, the present application is intended to include these modifications and variations to the extent that these modifications and variations are included within the scope of the claims of the present application and their equivalent technologies. [Explanation of symbols]

[0346] 1 Link status detection information, service data packet 1' Link status detection information 2 Link status detection information, service data packets 2' Link status detection information 3 Link status detection information, service data packets 3' Link status detection information 4 Link status detection information, service data packets 4' Link status detection information 5 Service Data Packet 6 Service Data Packets 7 Service Data Packet 8 Service Data Packets 900 Communication Equipment 910 Transceiver unit 920 Processing Unit 1010 Processor 1020 Memory 1030 Interface

Claims

1. A packet loss rate detection method, comprising: determining, by a session management network element, that link status detection needs to be performed for a quality of service flow in a multi-access protocol data unit session; sending, by the session management network element, an identification of the quality of service flow to a first device; sending, by the session management network element, to the first device, an IP address and / or a port number of a link status detection function, the IP address and / or the port number corresponding to the quality of service flow, the IP address and / or the port number being for enabling the link status detection function for the quality of service flow, the link status detection being link detection at quality of service flow granularity, and the link status detection function including a packet loss rate detection function; A method comprising:

2. The method comprises: sending, by the session management network element, a counting indication to a second device; the counting instruction instructs the second device to count a quantity of service data packets transmitted by the first device over a link to the second device; or the counting instruction instructs the second device, upon receiving link status detection information, to calculate a quantity of service data packets received on a link and to transmit the quantity of the service data packets received on the link to the first device. The method of claim 1, further comprising:

3. The method comprises: sending, by the session management network element, a packet loss rate detection indication to a second device; the packet loss rate detection instruction instructs the second device to calculate a packet loss rate of service data packets upon receiving link status detection information; or the packet loss rate detection instruction instructs the second device to calculate a quantity of service data packets received on a link when receiving link status detection information, and calculate a packet loss rate of the service data packets by using the quantity of the service data packets received on the link. The method of claim 1, further comprising:

4. The method comprises: sending, by the session management network element, a counting indication to the first device; the counting instruction instructs the first device to count a quantity of service data packets transmitted by the first device over a link to a second device. The method of claim 1, further comprising:

5. The method comprises: sending, by the session management network element, a packet loss rate detection indication to the first device; the packet loss rate detection instruction instructs the first device to calculate a packet loss rate of the received service data packets when receiving from a second device a quantity of the received service data packets counted by the second device; The method of claim 1, further comprising:

6. The method comprises: sending, by the session management network element, a link status report indication to the first device and / or the second device, the link status report indication instructing the first device and / or the second device to report a packet loss rate of service data packets; sending, by the session management network element, a link status reporting frequency to the first device and / or the second device, the link status reporting frequency indicating a frequency for reporting the packet loss rate of the service data packets; or sending, by the session management network element, a link status reporting period to the first device and / or the second device, the link status reporting period indicating a period for reporting the packet loss rate of the service data packets; The method of claim 1, further comprising:

7. The step of determining, by a session management network element, that link status detection needs to be performed on a quality of service flow, further comprising: determining, by the session management network element, that link status detection needs to be performed on the quality of service flow when determining that the steering function of the quality of service flow is access traffic steering, switching, low layer split ATSSS-LL; determining, by the session management network element, when determining that a steering function of the quality of service flow is ATSSS-LL and a steering mode of the quality of service flow is one of a load balancing mode, a minimum delay mode, a priority based mode, or an active standby mode, that link status detection needs to be performed on the quality of service flow; or determining, by the session management network element, that link status detection needs to be performed on the quality of service flow when determining that a link status threshold for the quality of service flow has been received from a policy control network element, the link status threshold comprising a packet loss rate threshold; 7. The method of any one of claims 1 to 6, comprising:

8. The method according to claim 1 , wherein the first device is a terminal device or a chip.

9. The method comprises: sending, by the session management network element, a link status detection indication to a second device, the link status detection indication being for enabling a link status detection function, the link status detection function including a packet loss rate detection function; 9. The method of claim 7 or 8, further comprising:

10. The method comprises: receiving, by the session management network element, an IP address and / or a port number of the link status detection function from a second device; 9. The method of claim 7 or 8, further comprising:

11. A method according to any one of claims 1 to 10, wherein the second device is a user plane network element.

12. The method comprises: allocating, by the second device, the IP address and / or the port number to the link status detection function corresponding to the quality of service flow.

12. The method of claim 10 or 11, further comprising:

13. 1. A communication method comprising: receiving, by the first device, an identification of a quality of service flow from a session management network element; receiving, by the first device, an IP address and / or a port number of a link status detection function from a session management network element, the IP address and / or the port number corresponding to the quality of service flow, the IP address and / or the port number for enabling the link status detection function for the quality of service flow in a multi-access protocol data unit session, the link status detection being link detection at quality of service flow granularity, and the link status detection function including a packet loss rate detection function; enabling, by the first device, the link status detection function; A method comprising:

14. The method comprises: receiving, by the first device, an identification of the quality of service flow from the session management network element; 14. The method of claim 13, further comprising:

15. The method comprises: sending, by the first device, link status detection information to a user plane function network element by using the quality of service flow; receiving, by the first device, a quantity of data packets from the user plane function network element, the quantity of data packets being a quantity of data packets received on the quality of service flow after receiving the link status detection information by the user plane function network element; determining, by the first device, a packet loss rate for the quality of service flow based on the quantity of the data packets; 15. The method of claim 13 or 14, further comprising:

16. A method according to any one of claims 13 to 15, wherein the first device is a terminal device or a chip.

17. 1. A communication device, comprising: a memory configured to store computer instructions; and a processor configured to execute the computer instructions stored in the memory to enable the communication device to perform the method according to any one of claims 1 to 12; 23. A communication device comprising:

18. A communication device, comprising: a memory configured to store computer instructions; and a processor configured to execute the computer instructions stored in the memory to enable the communication device to perform the method according to any one of claims 13 to 16; 23. A communication device comprising:

19. 1. A communication system comprising: A session management network element configured to perform the method according to any one of claims 1 to 12; A user plane function network element configured to receive an identification of a quality of service flow from a session management network element, a user plane function network element configured to receive an IP address and / or a port number of a link status detection function from the session management network element, the IP address and / or the port number corresponding to the quality of service flow, the IP address and / or the port number being for enabling the link status detection function for the quality of service flow, the link status detection being link detection at quality of service flow granularity, and the link status detection function including a packet loss rate detection function; 23. A communication system comprising:

Images