Communication method, apparatus, computer readable storage medium and program product

Abstract

This disclosure provides a communication method, apparatus, readable storage medium, and computer program product. In the method, a terminal device measures the time interval between adjacent data units of a received service stream. Based on the time interval and a first measurement adjustment parameter for the terminal device, the terminal device monitors whether a timeout has occurred in the received service stream. The first measurement adjustment parameter includes a threshold related to timeout monitoring. Based on determining that a timeout has been detected, the terminal device reports the timeout information of the service stream. In this manner, for continuous service streams, network nodes experiencing QoS issues can be accurately located without relying on high-precision time synchronization between networks; the nodes causing timeout delays can be statistically identified using only a single-sided data stream.

Description

Technical Field

[0001] This disclosure generally relates to the field of communications, and more specifically to a communication method, apparatus, computer-readable storage medium, and computer program product. Background Technology

[0002] To ensure the normal transmission of data packets, it is necessary to locate the nodes that are experiencing problems during data packet transmission in order to address these issues. Some related solutions use round-trip time (RTT) measurement or timestamping probe packets to measure latency. However, since RTT is round-trip time, RTT measurement methods cannot locate problems in network nodes operating on a single flow (i.e., a service flow with only one transmission direction). Adding timestamping probe packets requires high-precision time synchronization between network elements, which is complex to implement, and individual probe packets are often not sent along with quality of service (QoS) flow data packets, making it difficult to accurately assess information about a specific service flow. Therefore, ensuring the transmission of data packets for continuous service flows requires further discussion. Summary of the Invention

[0003] Embodiments of this disclosure provide a communication method, apparatus, system, computer-readable storage medium, and computer program product that can accurately determine the nodes causing transmission delays for continuous service flows, thereby locating the nodes with QoS problems, without relying on high-precision time synchronization between network nodes, and can statistically identify the nodes causing timeout delays based solely on a single-sided data flow.

[0004] Firstly, a communication method is provided. The execution entity of the method provided in the first aspect can be a terminal device. Unless otherwise specified, the terminal device, as the execution entity in this embodiment, can refer to a terminal equipment, a component within the terminal equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal equipment's functions. In this method, the terminal device measures the time interval between adjacent data units of a received service stream; based on the time interval and a first measurement adjustment parameter for the terminal device, the terminal device monitors whether the received service stream has timed out, the first measurement adjustment parameter including a threshold related to timeout monitoring; and based on determining that the timeout has been detected, the terminal device reports the timeout information of the service stream. In this way, the monitoring and reporting of timeout conditions of the received service stream can be achieved, which helps to accurately locate the nodes causing transmission delays on the transmission path of continuous service streams, thereby locating the nodes with QoS problems. It does not rely on high-precision time synchronization between network nodes; it only relies on a single-sided data stream to statistically identify the nodes causing timeout delays.

[0005] In some implementations, the first aspect of the method further includes: the terminal device performing measurements based on the determination that the first measurement adjustment parameter has taken effect. In this way, it can be ensured that each receiving node in the service flow can perform measurements in a coordinated manner, which helps to accurately locate nodes experiencing QoS issues and also avoids unnecessary measurements by the terminal device, saving terminal resources.

[0006] In some implementations, the first aspect of the method further includes: the terminal device determining the effectiveness of the first measurement adjustment parameter based on one or more of the following: determining that the received service flow is a specific service flow; or receiving first indication information indicating that the first measurement adjustment parameter is effective. In this way, the measurement operation is triggered only under specific conditions, achieving QoS guarantees for specific service flows, ensuring that the measurement can be accurately applied to the target critical service, and guaranteeing that each receiving node of the service flow can perform the measurement in a coordinated and consistent manner.

[0007] In some implementations, the terminal device receives the first indication information via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in receiving the first indication information; using a dedicated layer of data packets enables low-latency and high-efficiency information reception; while receiving via control signaling ensures reliable information reception.

[0008] In some implementations, the first aspect of the method further includes: the terminal device sending indication information indicating that the measurement adjustment parameters of at least one other receiving node on the transmission path of the service flow have taken effect. In this way, the terminal device can trigger each node to perform measurements, which helps to accurately locate the node causing transmission delay on the transmission path of the continuous service flow, thereby pinpointing the node experiencing QoS issues.

[0009] In some implementations, the terminal device sends indication information via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in sending indication information; using a dedicated layer of data packets enables low-latency and high-efficiency parameter transmission; while sending via control signaling ensures reliable transmission.

[0010] In some implementations, the first aspect of the method further includes: before measuring the time interval, the terminal device reports capability information, indicating that the terminal device has the capability to measure the time interval of adjacent data units in the service flow. In this way, capability negotiation between the terminal and the network is achieved, ensuring that the network side only coordinates each node to perform measurements if it confirms that the terminal supports it. This helps to accurately locate nodes causing transmission delays on the transmission path of continuous service flows.

[0011] In some implementations, the first aspect of the method further includes: the terminal device receiving response information indicating that other receiving nodes on the transmission path of the service flow have the ability to measure the time interval between adjacent data units of the service flow. In this way, the terminal can learn about the measurement capabilities of each node on the transmission path of the service flow, thereby better coordinating with the network in local or network-coordinated decision-making, and helping to accurately locate nodes causing transmission delays on the transmission path of continuous service flows.

[0012] In some implementations, the threshold includes a first time interval threshold and a first proportion threshold, and the terminal device determines that a timeout has been detected by determining that the first quantity proportion exceeds the first proportion threshold. The first quantity proportion is the proportion of adjacent data units in the received service flow whose time interval exceeds the first time interval threshold. In this way, false judgments caused by momentary jitter or single-packet anomalies can be effectively filtered out, making timeout judgments more accurate, thereby improving the accuracy of adjustment decisions, while avoiding resource waste caused by frequent reporting.

[0013] In some implementations, the first aspect of the method further includes: a terminal device determining a total time interval threshold for adjacent data units of a service flow across multiple receiving nodes on the transmission path, wherein the terminal device is one of the multiple receiving nodes; and the terminal device determining measurement adjustment parameters for the multiple receiving nodes based on the total time interval threshold, wherein the measurement adjustment parameters for the multiple receiving nodes include a first measurement adjustment parameter. In this manner, the terminal device possesses the ability to allocate measurement adjustment parameters to each node, thereby flexibly determining the measurement adjustment parameters for each segment of the service flow transmission path based on the actual needs of the service or the overall network resource status, achieving accurate measurement.

[0014] In some implementations, the measurement adjustment parameters for multiple receiving nodes also include measurement adjustment parameters for at least one other receiving node. The first aspect of the method further includes: the terminal device sending measurement adjustment parameters for at least one other receiving node. In this manner, the terminal device can allocate the measurement adjustment parameters, which helps to accurately locate nodes causing transmission delays on the transmission path of a continuous service flow.

[0015] In some implementations, the terminal device sends measurement adjustment parameters for at least one other receiving node via a dedicated layer of data packets or via control signaling. This approach allows for flexible configuration of the measurement adjustment parameters, enables low-latency and high-efficiency parameter transmission using the dedicated layer of data packets, and ensures reliable transmission by issuing control signaling.

[0016] In some implementations, the first aspect of the method further includes: the terminal device determining a total time interval threshold for adjacent data units of a service flow across multiple receiving nodes on the transmission path, wherein the terminal device is one of the multiple receiving nodes; and the terminal device sending information indicating the total time interval threshold. In this manner, the terminal device is allowed to report the total time interval threshold to the network side, which helps the network side to configure global measurement parameters to accurately locate nodes causing transmission delays on the transmission path of continuous service flows.

[0017] In some implementations, the first aspect of the method further includes: the terminal device receiving first measurement adjustment parameters. In this way, the terminal device can obtain measurement adjustment parameters from the network side that match the overall network optimization strategy, which helps to accurately locate nodes causing transmission delays on the transmission path of continuous service flows.

[0018] In some implementations, the terminal device receives the first measurement adjustment parameters either via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in receiving the first measurement adjustment parameters; using a dedicated layer of data packets enables low-latency and high-efficiency parameter reception; while receiving via control signaling ensures the reliability of parameter reception.

[0019] In some implementations, the first measurement adjustment parameters come from one or more of the following: access network devices, user plane functions (UPF), or session management functions (SMF). This approach diversifies the sources of measurement adjustment parameter configuration, enhances the flexibility of solution deployment, and allows for adaptation to different scenarios.

[0020] In some implementations, the first aspect of the method further includes: the terminal device receiving information related to adjustments of one or more of the following: transmission resources; transmission priority; transmission path, or serving cell. In this way, the terminal device can promptly learn of the optimization decisions made by the network side based on timeout measurement results and make corresponding adjustments accordingly.

[0021] In some implementations, the first aspect of the method further includes: the terminal device receiving second indication information, which indicates the adjusted value of the packet delay budget (PDB) for the service flow. In this way, the terminal device can be aware of the network-side adjustment to the PDB, and thus update its local service processing strategy or buffer management accordingly.

[0022] In some implementations, the first aspect of the method further includes: the terminal device sending a request message to request that the PDB of the service flow be adjusted to a first PDB value, wherein the request message includes the first PDB value. In this way, the terminal device has the ability to proactively initiate PDB adjustments, and when it detects QoS degradation, it can directly request the network to adjust the PDB to ensure service quality.

[0023] In some implementations, a data unit includes one or more of the following: one or more data packets; one or more frames; or one or more Protocol Data Units (PDUs). This allows for different transmission granularities to be applied, thereby adapting to different service protocol stacks and transmission characteristics and meeting the QoS requirements of service flows.

[0024] Secondly, a communication method is provided. The execution entity of the method provided in this second aspect can be a first network device. Unless otherwise specified, the first network device, as the execution entity in the embodiments of this disclosure, can refer to a first network node, a component within the first network node (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the first network device. In some implementations, the first network node can be a RAN node or a first core network element (e.g., a UPF). In this method, the first network device measures the time interval between adjacent data units of a service flow received from the first node; based on this time interval and a second measurement adjustment parameter for the first network device, the first network device monitors whether the received service flow has timed out, the second measurement adjustment parameter including a threshold related to timeout monitoring; the first network device receives timeout information of a service flow reported by a second node, the timeout information indicating that the service flow received by the second node from the first network device has timed out; and the first network device determines that the Quality of Service (QoS) of the first network device is abnormal based on receiving the timeout information and not detecting a timeout in the service flow received from the first node. In this way, the nodes causing transmission delays can be accurately identified for continuous service flows, thereby locating the nodes with QoS problems. It does not require high-precision time synchronization between network nodes; it can count and identify the nodes causing timeout delays based solely on the data flow on one side.

[0025] In some implementations, the second aspect of the method further includes: the first network device performing measurements based on the determination of the effectiveness of the second measurement adjustment parameters. In this way, it can be ensured that each receiving node of the service flow can perform measurements in a coordinated manner, which helps to accurately locate nodes experiencing QoS problems and also avoids unnecessary measurements by the first network device, saving the resources of the first network device.

[0026] In some implementations, the first network device determines the effectiveness of the second measurement adjustment parameter based on receiving a third indication message that indicates the second measurement adjustment parameter is in effect. In this way, the measurement operation is triggered only under specific conditions, ensuring that all receiving nodes in the service flow can perform measurements in a coordinated and consistent manner.

[0027] In some implementations, the first network device receives the third indication information via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in receiving the third indication information; receiving it via a dedicated layer of data packets enables low-latency and high-efficiency information reception; while receiving it via control signaling ensures reliable information reception.

[0028] In some implementations, the first network device is a User Plane Function (UPF), which determines the activation of the second measurement adjustment parameters based on whether the received service flow is a specific service flow. In this way, QoS guarantees for specific service flows are achieved, ensuring that measurements can be accurately applied to the target critical service.

[0029] In some implementations, the second aspect of the method further includes: a first network device sending indication information indicating that measurement adjustment parameters of at least one other receiving node on the transmission path of the service flow have taken effect, wherein the second node is one of the at least one other receiving node. In this way, it is ensured that the receiving nodes of the service flow can perform measurements in a coordinated manner.

[0030] In some implementations, the first network device sends indication information via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in how the indication information is sent; using a dedicated layer of data packets enables low-latency, high-efficiency information transmission; while issuing control signaling ensures reliable information transmission.

[0031] In some implementations, the second aspect of the method further includes: before measuring the time interval, the first network device receives first information indicating that a terminal device on the transmission path of the service flow has the capability to measure the time interval between adjacent data units of the service flow. In this way, the first network device can know the capabilities of the terminal devices, ensuring that the measurement mechanism is triggered only if the terminal device supports it, guaranteeing accurate location of the node with the current QoS problem, and without relying on high-precision time synchronization between network nodes.

[0032] In some implementations, the threshold includes a second time interval threshold and a second proportion threshold. Furthermore, the first network device's monitoring of whether a received service flow has timed out includes: the first network device monitoring whether a second quantity proportion exceeds the second proportion threshold. The second quantity proportion is the percentage of adjacent data units in the service flow received from the first node whose time interval exceeds the second time interval threshold. This approach allows for more accurate timeout determination, thereby improving the accuracy of adjustment decisions and avoiding resource waste caused by frequent reporting.

[0033] In some implementations, the first network device is a UPF (User-Defined Provider). The second aspect of the method further includes: the first network device determining a total time interval threshold for adjacent data units of a service flow across multiple receiving nodes on the transmission path, where the UPF is one of these receiving nodes. This approach enables the UPF to determine the total time interval threshold based on actual conditions, allowing for proactive resource optimization initiated from the core network side.

[0034] In some implementations, the second aspect of the method further includes: a first network device receiving second information, the second information indicating a threshold value for the total time interval between adjacent data units of a service flow and multiple receiving nodes on the transmission path. This facilitates the first network device in configuring global measurement parameters to accurately locate nodes causing transmission delays on the transmission path of a continuous service flow.

[0035] In some implementations, the second aspect of the method further includes: a first network device determining measurement adjustment parameters for multiple receiving nodes based on a total time interval threshold, wherein the measurement adjustment parameters for the multiple receiving nodes include a second measurement adjustment parameter. In this manner, the first network device can allocate the measurement adjustment parameters, which helps to accurately locate nodes causing transmission delays on the transmission path of a continuous service flow.

[0036] In some implementations, the measurement adjustment parameters for multiple receiving nodes also include measurement adjustment parameters for at least one other receiving node. The second aspect of the method further includes: a first network device transmitting measurement adjustment parameters for at least one other receiving node. In this manner, the first network device can allocate the measurement adjustment parameters, which helps to accurately locate nodes causing transmission delays on the transmission path of a continuous service flow.

[0037] In some implementations, the first network device transmits measurement adjustment parameters for at least one other receiving node via a dedicated layer of data packets or via control signaling. This approach allows for flexible configuration of the measurement adjustment parameters; the dedicated layer of data packets enables low-latency, high-efficiency parameter transmission; and the control signaling ensures reliable transmission.

[0038] In some implementations, the second aspect of the method further includes: the first network device sending information indicating a total time interval threshold. This can help other nodes configure measurement adjustment parameters to accurately pinpoint nodes causing transmission delays along the transmission path of a continuous service flow.

[0039] In some implementations, the second aspect of the method further includes: the first network device receiving second measurement adjustment parameters. In this way, the first network device can obtain measurement adjustment parameters from other nodes that match the overall network optimization strategy, which helps to accurately locate nodes causing transmission delays on the transmission path of continuous service flows.

[0040] In some implementations, the first network device receives the second measurement adjustment parameters either via a dedicated layer of data packets or via control signaling. This approach allows for flexibility in the reception of the measurement adjustment parameters; receiving them via a dedicated layer of data packets enables low-latency and high-efficiency parameter reception, while receiving them via control signaling ensures reliable parameter reception.

[0041] In some implementations, the first network device is an access network device, and the second measurement adjustment parameter comes from one or more of the following: a terminal device, a UPF, or a Session Management Function (SMF); or the first network device is a UPF, and the second measurement adjustment parameter comes from one or more of the following: a terminal device, an access network device, or an SMF. This approach achieves diversity in the sources of the measurement adjustment parameter configuration, enhances the flexibility of the solution deployment, and can adapt to different scenarios.

[0042] In some implementations, the second aspect of the method further includes: the first network device performing and adjusting one or more of the following related operations: transmission resources; transmission priority; transmission path, or serving cell. In this way, the network side can make corresponding optimization decisions based on timeout measurement results, so as to make timely adjustments.

[0043] In some implementations, the first network device is an access network device. The second aspect of the method further includes: the first network device sending second indication information, which indicates the adjusted value of the packet delay budget (PDB) for the service flow. In this way, the network side can initiate adjustments to the PDB to ensure quality of service.

[0044] In some implementations, the first network device is an access network device. The second aspect of the method further includes: the first network device receiving a request message requesting that the PDB of a service flow be adjusted to a first PDB value, wherein the request message includes the first PDB value; and the first network device adjusting the PDB of the service flow to the first PDB value. In this manner, the PDB can be adjusted according to a request, ensuring service quality.

[0045] In some implementations, a data unit includes one or more of the following: one or more data packets; one or more frames; or one or more Protocol Data Units (PDUs). This allows for different transmission granularities to be applied, thereby adapting to different service protocol stacks and transmission characteristics and meeting the QoS requirements of service flows.

[0046] Thirdly, a communication method is provided. The execution entity of the method provided in this third aspect can be a second network device. Unless otherwise specified, the second network device, as the execution entity in the embodiments of this disclosure, can refer to a second network node, a component within the second network node (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the second network device. In some implementations, the second network node can be a second core network element (e.g., SMF). In this method, the second network device determines measurement adjustment parameters for multiple receiving nodes on the transmission path of the service flow; and the second network device sends configuration information to the multiple receiving nodes, wherein the configuration information includes measurement adjustment parameters for the corresponding nodes, and the measurement adjustment parameters are used to monitor whether the service flow times out at the corresponding receiving node. In this way, for continuous service flows, the node causing transmission delay can be accurately determined, thereby locating the node with QoS problems. It does not rely on high-precision time synchronization between network nodes; it only relies on a single-sided data flow to statistically identify the node causing timeout delay.

[0047] In some implementations, multiple receiving nodes include terminal devices. The third aspect of the method further includes receiving capability information, which indicates that the terminal device has the ability to measure the time interval between adjacent data units of a service flow. In this way, the second network device can learn about the terminal's capabilities, ensuring that the terminal device can perform fine-grained measurements. This guarantees that the network sends and measures adjustment parameters when all receiving nodes have complete capabilities, avoiding invalid configurations and improving network resource utilization efficiency.

[0048] In some implementations, the third aspect further includes sending response information indicating that other receiving nodes on the transmission path of the service flow have the capability to measure the time interval between adjacent data units of the service flow, and these other receiving nodes are different from the terminal device. In this way, the second network device can learn about the capabilities of each node, ensuring that each receiving node can perform fine-grained measurements. This guarantees that the network sends and measures adjustment parameters when each receiving node has the full capability, avoiding invalid configurations and improving network resource utilization efficiency.

[0049] In some implementations, the third aspect further includes sending first information indicating that the terminal device has the capability to measure the time interval between adjacent data units of a service flow. In this way, other nodes in the network are aware of the terminal's capabilities, ensuring the coordination of measurement operations among nodes and helping to accurately locate nodes causing transmission delays on the transmission path of continuous service flows, thereby pinpointing nodes experiencing QoS issues.

[0050] In some implementations, the third aspect of the method further includes receiving third information, which indicates a total time interval threshold for adjacent data units of a service flow across multiple receiving nodes. This total time interval threshold is used to determine measurement adjustment parameters for the multiple receiving nodes. In this way, the second network device can determine the global configuration of the measurement adjustment parameters for each node, and can accurately locate the nodes causing transmission delays on the transmission path of continuous service flows, thereby pinpointing the nodes experiencing QoS issues.

[0051] In some implementations, a data unit includes one or more of the following: one or more data packets; one or more frames; or one or more Protocol Data Units (PDUs). This allows for different transmission granularities to be applied, thereby adapting to different service protocol stacks and transmission characteristics and meeting the QoS requirements of service flows.

[0052] In a fourth aspect, a communication device is provided, which has the function of implementing the behavior in the method examples of any one of the first to third aspects described above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described function. The description of the device in any one of the first to third aspects also applies to the communication device of the fourth aspect; that is, the communication device of the fourth aspect can refer to the communication device itself, or to components within the communication device (e.g., a processor, a chip, or a chip system), or to logic modules or software capable of implementing all or part of the functions of the communication device. In one possible design, the communication device includes a unit that performs the method of any one of the first to third aspects, or implementations thereof. The beneficial effects of the communication device provided in the fourth aspect can be found in the description of any one of the first to third aspects, and will not be repeated here.

[0053] Fifthly, an apparatus is provided. The apparatus includes a processor and a memory storing a computer program or instructions. When executed by the processor, the computer program or instructions cause the apparatus to perform any method according to any one of the first to third aspects and their implementations.

[0054] Sixthly, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program or instructions, which, when executed by an electronic device, cause the electronic device to perform the methods performed by the apparatus in the above aspects.

[0055] In a seventh aspect, a computer program or computer program product is provided. The computer program or computer program product includes computer instructions that, when executed by an electronic device, cause the electronic device to perform the methods performed by the apparatus in the above aspects.

[0056] Eighthly, embodiments of this disclosure provide a chip system including a processor for implementing the functions of the apparatus in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing computer programs or instructions and / or data. The chip system may be composed of chips or may include chips and other discrete devices.

[0057] Ninthly, embodiments of this disclosure also provide a communication system. The communication system includes core network elements for performing one or more of the first to third aspects. Attached Figure Description

[0058] Figure 1 A schematic diagram of the system architecture of some embodiments of this disclosure is shown.

[0059] Figure 2 A schematic diagram of the communication process of some embodiments of this disclosure is shown.

[0060] Figure 3 The diagram illustrates some embodiments of this disclosure that implement QoS guarantees.

[0061] Figure 4 The diagram illustrates a process flow for implementing QoS guarantees using some embodiments of this disclosure.

[0062] Figures 5 to 8 A schematic flowchart illustrating the configuration measurement adjustment parameters of some embodiments of this disclosure is shown.

[0063] Figures 9 to 10 A schematic diagram of the process for triggering PDB adjustments according to some embodiments of this disclosure is shown.

[0064] Figure 11 A schematic process block diagram of some embodiments of the present disclosure implemented at a terminal device is shown.

[0065] Figure 12 A schematic process block diagram of some embodiments of the present disclosure implemented at a first network device is shown.

[0066] Figure 13A schematic process block diagram illustrating some embodiments of the present disclosure is shown at a second network device.

[0067] Figure 14 This is a block diagram of a device that can be used to implement some embodiments of this application.

[0068] Figure 15-17 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application. Detailed Implementation

[0069] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that embodiments of this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0070] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0071] The embodiments disclosed herein can be implemented according to any suitable communication protocol, including but not limited to third-generation (3G), fourth-generation (4G), fifth-generation (5G), and future communication protocols (e.g., future cellular communication protocols, wireless LAN communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future). The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0072] During the transmission of data packets in a continuous service flow, network nodes through which the packets pass may encounter problems, such as QoS anomalies like latency issues. Therefore, to ensure normal packet transmission, it is necessary to locate the problematic network node and adjust it accordingly. Some solutions mentioned above use RTT measurement or add timestamps to probe packets to measure latency. However, these solutions cannot accurately measure latency in a single transmission direction of the service flow. They rely on high-precision timestamps from network nodes for time synchronization, and individual probe packets are often not sent with the service flow's data packets, making it difficult to accurately assess the QoS information of a specified 5QI flow. Furthermore, in some solutions, the PDB is mainly used to control the RAN and UPF sides. The network element sending data packets compares the arrival time of the packet with the PDB budget to determine whether the current packet is urgent or has expired. However, sending a data packet does not guarantee that it will be received. Errors and interference may occur during transmission, leading to unsuccessful reception.

[0073] Based on the above discussion of some related solutions, this disclosure proposes a solution for ensuring the transmission of data packets for continuous service flows. This solution can more accurately locate problematic or abnormal network nodes and make corresponding adjustments and QoS guarantees. It does not require high-precision time synchronization between networks and can count and identify nodes that cause timeout delays (i.e., transmission delays that cause timeouts) by relying solely on a single-sided data flow.

[0074] Figure 1 A schematic diagram of the system architecture of some embodiments of this disclosure is shown. For example... Figure 1 The system architecture shown involves one or more core network elements of a terminal device 110, a radio access network (RAN) node 120, and a core network 150, such as core network elements 130, 140, and 170. The core network element 130 is also referred to as the first core network element (e.g., UPF), and the core network element 140 is also referred to as the second core network element (e.g., SMF). Core network element 170 can be used to enable communication between the terminal device 110 and the second core network element 140, or to enable communication between the RAN node 120 and the second core network element 140. In some embodiments, core network element 170 can be an access and mobility management function (AMF). In some embodiments, the second core network element 140 can send configuration information, such as configured parameters, to the terminal device 110, the RAN node 120, and the first core network element 130. Figure 1A data network (DN) node, denoted as DN 160, is also shown. In some embodiments, data units of a continuous service flow (e.g., one or more data packets, one or more frames, or one or more sets of PDUs) can be transmitted from terminal device 110 to DN 160 via RAN node 120 and first core network element 130. In other embodiments, data units of a continuous service flow (e.g., one or more data packets, one or more frames, or one or more sets of PDUs) can be transmitted from DN 110 to terminal device 110 via first core network element 130 and RAN node 120.

[0075] The communication systems disclosed in this embodiment include, but are not limited to: narrowband Internet of Things (NB-IoT), Global System for Mobile Communications (GSM), enhanced data rate for GSM Evolution (EDGE), wideband code division multiple access (WCDMA), code division multiple access 2000 (CDMA2000), time division-synchronization code division multiple access (TD-SCDMA), long term evolution (LTE), long term evolution advanced (LTE-A), 5th generation (5G) mobile communication systems, and the three major application scenarios in 5G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and enhanced machine-type communication (EMC). Communication, eMTC), and future mobile communication systems, etc.

[0076] The solutions disclosed herein are applicable to LTE systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, fifth-generation communication systems, and future communication systems. Of course, the solutions disclosed herein can also be applied to other possible communication systems, such as Internet of Things (IoT) networks, wireless local area network systems supporting the 802.11 series protocols, wireless personal area network systems based on Ultra-Wideband (UWB), sensing systems, vehicle-to-everything (V2X), machine-type communication (MTC), long-term evolution-machine (LTE-M), machine-to-machine (M2M), vehicle-to-vehicle (V2V), long-term evolution-vehicle (LTE-V), and satellite communication systems. The communication systems described above that are applicable to the embodiments of this disclosure are merely illustrative examples. The communication systems applicable to the embodiments of this disclosure are not limited thereto. They will be uniformly described here and will not be repeated below.

[0077] A terminal device is a device with wireless transceiver capabilities. Terminal devices can communicate with one or more core network (CN) devices (or core network elements) via access network devices (or access equipment, access network nodes) in the RAN. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as on ships); and they can also be deployed in the air (such as on airplanes, balloons, and satellites). In this disclosure, the terminal device may also be referred to as user equipment (UE), which may be a mobile phone, mobile station (MS), tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, subscriber unit, cellular phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, laptop computer, machine type communication (MTC) terminal device, drone, etc. Terminal devices may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. Optionally, terminal devices may be handheld devices with wireless communication capabilities, terminal devices in the Internet of Things or the Internet of Vehicles, or any form of terminal device in 5G and subsequent communication systems; this disclosure does not limit this. In this disclosure, the means for implementing the functions of the terminal device may be the terminal device itself, or it may be a means that enables the terminal device to implement the functions, such as a chip system or a chip, which may be installed in the terminal device. In this application, the chip system may consist of chips or may include chips and other discrete components.

[0078] Access network equipment can be any device with wireless transceiver capabilities that can communicate with terminal devices, such as a radio access network (RAN) node that connects terminal devices to a wireless network. Examples of RAN nodes currently include: macro base stations, micro base stations (also known as small cells), relay stations, access points, gNBs, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), home base stations (e.g., home evolved Node Bs, or home Node Bs, HNBs), base band units (BBUs), WiFi access points (APs), integrated access and backhaul (IABs), satellites, and drones.

[0079] Furthermore, network devices such as access network equipment can connect to core network (CN) equipment, which can be used to provide core network services to access network equipment and terminal equipment. Core network equipment can correspond to different devices in different systems. For example, in 3G, core network equipment can correspond to the Serving GPRS Support Node (SGSN) and / or the Gateway GPRS Support Node (GGSN) of the General Packet Radio System (GPRS). In 4G, core network equipment can correspond to the Mobility Management Entity (MME) and / or the Serving Gateway (S-GW) and / or the Public Data Network Gateway (P-GW). In 5G, core network equipment can correspond to the Access and Mobility Management Function (AMF), the Session Management Function (SMF), and / or the User Plane Function (UPF), etc.

[0080] In this embodiment of the disclosure, the means for implementing the functions of the network device can be the network device itself, or it can be a means that enables the network device to implement the functions, such as a chip system or a chip, which can be installed in the network device. In this embodiment of the application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0081] Figure 2 A schematic diagram of the communication process of some embodiments of this disclosure is shown. Figure 2 The communication process 200 shown may involve a first node 210, a second node 220, a first network device 230, and a second network device 240. The service flow involved in the communication process 200 may be transmitted in the downlink transmission direction (the direction from the network to the terminal device) or in the uplink transmission direction (the direction from the terminal device to the network).

[0082] In some implementations, the first node 210 can be a terminal device (e.g., terminal device 110), the first network device 230 can be a RAN node (e.g., RAN node 120), the second node 220 can be a first core network element (e.g., first core network element 130 or UPF), and the second network device 240 can be a second core network element (e.g., second core network element 140 or SMF). The transmission direction of the service flow is uplink. In such implementations, the communication process 200 may also involve nodes in the DN (e.g., DN 160), and the first core network element can send the service flow to the DN, which is not shown in the figure.

[0083] In some implementations, the first node 210 can be a first core network element (e.g., first core network element 130 or UPF), the first network device 230 can be a RAN node (e.g., RAN node 120), the second node 220 can be a terminal device (e.g., terminal device 110), and the second network device 240 can be a second core network element (e.g., second core network element 140 or SMF). The transmission direction of the service flow is downlink. In such implementations, the communication process 200 may also involve nodes in the DN (e.g., DN 160), and the service flow may be sent from the DN to the first core network element, which is not shown in the figure.

[0084] In some implementations, the first node 210 can be a RAN node (e.g., RAN node 120), the first network device 230 can be a first core network element (e.g., first core network element 130 or UPF), the second node 220 can be a DN (e.g., DN 160), and the second network device 240 can be a second core network element (e.g., second core network element 140 or SMF). The transmission direction of the service flow is uplink. In such an implementation, the service flow can be sent from the UE to the RAN node, which is not shown in the figure.

[0085] In some implementations, the first node 210 can be a DN (e.g., DN 160), the first network device 230 can be a first core network element (e.g., first core network element 130 or UPF), the second node 220 can be a RAN node (e.g., RAN node 120), and the second network device 240 can be a second core network element (e.g., second core network element 140 or SMF). The transmission direction of the service flow is downlink. In such an implementation, the RAN node can further transmit the service flow to the UE, which is not shown in the figure.

[0086] Examples of terminal devices in this disclosure can be terminal equipment or components within a terminal equipment (e.g., processors, chips, or chip systems), or they can be logic modules or software capable of implementing all or part of the functions of the terminal equipment. The number of UPFs can be one or more.

[0087] The service flow in this embodiment is a continuous service flow, which is transmitted or received in data units, and the continuous service flow includes multiple data units. The term "transmitting service flow" as mentioned below specifically refers to the data units of the transmitting service flow. Correspondingly, the term "receiving service flow" specifically refers to the data units of the receiving service flow.

[0088] In some implementations, a data unit includes one or more data packets. In other implementations, a data unit includes one or more frames. In still other implementations, a data unit includes one or more sets of PDUs. The node receiving the data unit of the service flow is a receiving node on the transmission path of the service flow.

[0089] In communication process 200, in step 206, the first node 210 sends service flow 217 to the first network device 230. The first network device 230 receives service flow 217 sent by the first node 210.

[0090] In step 208, the first network device 230 sends service flow 217 to the second node 220. The second node 220 receives service flow 217 sent by the first network device.

[0091] In step 212, the first network device 230 measures the time interval between receiving adjacent data units of the service flow 217 from the first node 210, that is, measures the time interval between receiving one data unit and receiving the next data unit.

[0092] In step 214, the first network device 230 monitors whether the service flow 217 received by the first network device 230 has timed out based on the time interval measured by the first network device 230 and the second measurement adjustment parameters for the first network device 230. The second measurement adjustment parameters include a threshold related to monitoring the timeout.

[0093] In some implementations, after detecting a timeout in the received service flow 217, the first network device 230 can report timeout information indicating that the received service flow 217 has timed out to the first node 210. This step is in Figure 2 Not shown in the image.

[0094] In step 213, the second node 220 measures the time interval between adjacent data units received by the second node 220 from the service flow 217.

[0095] In step 215, the second node 220 monitors whether the received service flow 217 has timed out based on the time interval measured by the second node 220 and the measurement adjustment parameters used by the second node 220. The measurement adjustment parameters used by the second node 220 include a threshold related to monitoring the timeout.

[0096] In step 216, the second node 220, based on the detection that a timeout has occurred in the service flow received by the second node 220, reports timeout information 227 to the first network device 230, indicating that the service flow 217 received by the second node 220 from the first network device 230 has timed out. Accordingly, the first network device 230 receives the timeout information 227 of the service flow 217 reported by the second node 220.

[0097] In step 218, the first network device 230 determines that the QoS of the first network device 230 is abnormal based on the timeout information 227 reported by the second node 220 and the fact that no timeout was detected in the service flow 217 received by the first network device 230 from the first node 210.

[0098] It is understood that, similar to the above-described implementation of determining whether the QoS of the first network device 230 is abnormal, other intermediate nodes on the transmission path of the service flow that are used to receive the data unit of the service flow can also refer to the above implementation to determine whether their own QoS is abnormal. This disclosure does not describe this process one by one.

[0099] As described above, in some embodiments, the transmission direction of service flow 217 is uplink, and the first node 210 can be a terminal device. In other embodiments, the transmission direction of service flow 217 is downlink, and the second node 220 can be a terminal device. Figure 2 The following example illustrates the operation performed by a terminal device in an embodiment of this disclosure, where the second node 220 is a terminal device (e.g., terminal device 110) (i.e., the transmission direction of service flow 217 is downlink). In the embodiment where the transmission direction of service flow 217 is downlink, the terminal device is a receiving node of service flow 217. As an example of the second node 220, the terminal device can perform steps 213, 215, and 216. As shown in step 213, the second node 220 is the terminal device, and will be described directly as a terminal device below. In this embodiment, the measurement adjustment parameters for the second node 220 are the same as the first measurement adjustment parameters for the terminal device. The terminal device can measure the time interval between adjacent data units received from service flow 217. In step 215, the terminal device monitors whether the received service flow 217 has timed out based on the time interval measured by the terminal device and the first measurement adjustment parameters for the terminal device. The first measurement adjustment parameters include a threshold related to monitoring timeout. Based on the determination that a timeout has been detected, the terminal device reports the timeout information of service flow 217. This step can be referred to the description of step 216 above.

[0100] In some implementations, the threshold related to monitoring timeout included in the first measurement adjustment parameter may specifically include a first time interval threshold and a first proportion threshold. The terminal device determines that a timeout has been detected specifically by determining that a first quantity percentage exceeds the first proportion threshold, where the first quantity percentage is the proportion of adjacent data units in the received service flow 217 whose time interval exceeds the first time interval threshold.

[0101] In some implementations, the terminal device may generate measurement adjustment parameters for multiple receiving nodes on the transmission path of service flow 217. Specifically, the terminal device determines a total time interval threshold for adjacent data units of the service flow at multiple receiving nodes on the transmission path, and determines measurement adjustment parameters for the multiple receiving nodes based on the total time interval threshold, wherein the measurement adjustment parameters for the multiple receiving nodes include a first measurement adjustment parameter.

[0102] In some embodiments, the measurement adjustment parameters for multiple receiving nodes that can be generated by the terminal device also include measurement adjustment parameters for at least one other receiving node besides the terminal device, and the terminal device can send the measurement adjustment parameters for the at least one other receiving node. In some embodiments, the terminal device can send the measurement adjustment parameters for the at least one other receiving node via a dedicated layer of the data packet or via control signaling. The dedicated layer of the data packet involved in the embodiments of this disclosure is a layer added to the user plane, also called a coordination layer or cooperation layer, dedicated to transmitting control information and / or service information sent with the data packet. This will not be described again below.

[0103] In some implementations, measurement adjustment parameters for multiple receiving nodes along the transmission path of service flow 217 can be generated by nodes other than the terminal device. The terminal device can receive the first measurement adjustment parameters from other nodes. In some implementations, the terminal device receives the first measurement adjustment parameters from other nodes via a dedicated layer of data packets or via control signaling. The other nodes may be nodes that generate or forward the first measurement adjustment parameters.

[0104] In some implementations, the terminal device determines (e.g., generates) a total time interval threshold for adjacent data units of service flow 217 across multiple receiving nodes on the transmission path, and sends information indicating the total time interval threshold to other nodes. The total time interval threshold can be used by nodes other than the terminal device to generate measurement adjustment parameters for the multiple receiving nodes on the transmission path of service flow 217.

[0105] In an implementation where measurement adjustment parameters for multiple receiving nodes on the transmission path of service flow 217 are generated by nodes other than the terminal device, the first measurement adjustment parameters come from one or more of the following: access network device, UPF, or second network device 240 (e.g., SMF).

[0106] In the implementation where the first measurement adjustment parameter originates from the second network device 240, as shown in step 202, the second network device 240 can determine (e.g., generate) measurement adjustment parameters for multiple receiving nodes on the transmission path of service flow 217, including the first measurement adjustment parameter and the second measurement adjustment parameter. In steps 204a, 204b, and 204c, the second network device 240 sends configuration information to the multiple receiving nodes, wherein the configuration information includes measurement adjustment parameters 207a, 207b, and 207c for the corresponding nodes. These measurement adjustment parameters are used to monitor whether service flow 217 times out at the corresponding receiving node. The measurement adjustment parameters 207a, 207b, and 207c configured for each node can be different.

[0107] In some implementations, the second network device 240 may receive third information from a terminal device or a UPF, the third information being used to indicate a total time interval threshold for adjacent data units of a service flow across multiple receiving nodes, the total time interval threshold being used to determine measurement adjustment parameters for the multiple receiving nodes.

[0108] In some embodiments, the terminal device may report capability information before measuring the time interval between adjacent data units received from service flow 217. This capability information indicates that the terminal device has the capability to measure the time interval between adjacent data units of service flow 217. In some embodiments, taking data units as data packets as an example, this capability of the terminal device may be the capability to support neighbor packet measurement. In some embodiments, the terminal device may send this capability information to a second network device 240. Accordingly, the second network device 240 may receive this capability information. In some embodiments, the second network device 240 may send response information, which the terminal device may receive. This response information indicates that receiving nodes on the transmission path of service flow 217, other than the terminal device, have the capability to measure the time interval between adjacent data units of service flow 217.

[0109] In some implementations, the second network device 240 may send first information to receiving nodes other than the terminal device on the transmission path of the service flow 217, the first information indicating that the terminal device has the ability to measure the time interval between adjacent data units of the service flow 217.

[0110] In some implementations, the terminal device performs a measurement of the time interval between adjacent data units received from the service flow 217 based on determining the effectiveness of the first measurement adjustment parameter.

[0111] In some implementations, the measurement adjustment parameters configured for each receiving node can be triggered by the terminal device.

[0112] In some embodiments, the terminal device determines that the first measurement adjustment parameter is effective based on determining that the received service flow 217 is a specific service flow. Additionally or alternatively, the terminal device determines that the first measurement adjustment parameter is effective based on receiving first indication information indicating that the first measurement adjustment parameter is effective. In some embodiments, the terminal device receives the first indication information via a dedicated layer of a data packet or via control signaling.

[0113] In some embodiments, the terminal device may generate and send indication information indicating that the measurement adjustment parameters of at least one other receiving node on the transmission path of service flow 217 are in effect. In some embodiments, the terminal device sends the indication information via a dedicated layer of data packets or via control signaling.

[0114] Continue to refer to Figure 2On the first network device 230 side, the threshold related to the monitoring timeout performed at step 214 in the second measurement adjustment parameters may include a second time interval threshold and a second proportion threshold. The first network device 230 monitors whether a service flow 217 received from the first node 210 has timed out. Specifically, this may include monitoring whether a second quantity percentage exceeds a second proportion threshold. The second quantity percentage is the percentage of adjacent data units in the service flow 217 received from the first node whose time interval exceeds the second time interval threshold. For example, more than 20% (an example of the second quantity percentage) of neighboring packets (adjacent data packets, or adjacent data packets, an example of adjacent data units) have time intervals exceeding the second time interval threshold. Assuming the second proportion threshold is 5%, a timeout is detected in the received service flow 217.

[0115] As described above, measurement adjustment parameters for multiple receiving nodes on the transmission path of service flow 217 can be determined (e.g., generated) by nodes other than the terminal device. In an embodiment where the measurement adjustment parameters for the multiple receiving nodes are generated by the first network device 230, the first network device 230 can determine the measurement adjustment parameters for the multiple receiving nodes based on a threshold value of the total time interval between adjacent data units of service flow 217 on the transmission path of the multiple receiving nodes, wherein the measurement adjustment parameters for the multiple receiving nodes include a second measurement adjustment parameter.

[0116] In some embodiments, the measurement adjustment parameters for multiple receiving nodes also include measurement adjustment parameters for at least one other receiving node besides the first network device 230, and the first network device 230 may also transmit the measurement adjustment parameters for the at least one other receiving node. In some embodiments, the first network device 230 may transmit the measurement adjustment parameters for the at least one other receiving node via a dedicated layer of data packets or via control signaling.

[0117] In some implementations, the first network device 230 is a UPF, which is one of a plurality of receiving nodes. The first network device 230 may determine (e.g., generate) a total time interval threshold for adjacent data units of traffic flow 217 across the plurality of receiving nodes on the transmission path.

[0118] In some implementations, the first network device 230 may send information indicating a total time interval threshold. The total time interval threshold is used by other nodes to determine (e.g., generate) measurement adjustment parameters for multiple receiving nodes on the transmission path of traffic flow 217.

[0119] In some embodiments, the first network device 230 can receive second information. In some embodiments, the first network device 230 is a RAN node, and the first network device 230 can receive the second information from a terminal device or a UPF. In some embodiments, the first network device 230 is a UPF, and the first network device 230 can receive the second information from a terminal device. The second information is used to indicate a threshold value for the total time interval between adjacent data units of service flow 217 at multiple receiving nodes on the transmission path.

[0120] In some embodiments, the measurement adjustment parameters for multiple receiving nodes are generated by nodes other than the first network device 230. The first network device 230 can receive the second measurement adjustment parameters from the other nodes. In some embodiments, the first network device 230 receives the second measurement adjustment parameters via a dedicated layer of data packets or via control signaling.

[0121] In some implementations, the first network device 230 is an access network device (e.g., a RAN node), and the second measurement adjustment parameter is derived from one or more of the following: a terminal device, a UPF, or a Session Management Function (SMF). Alternatively, the first network device 230 is a UPF, and the second measurement adjustment parameter is derived from one or more of the following: a terminal device, an access network device, or an SMF. Implementations where the second measurement adjustment parameter is derived from an SMF will be described in detail below at step 202.

[0122] In some implementations, the first network device 230 may perform the measurement shown in step 212 based on determining the effectiveness of the second measurement adjustment parameter.

[0123] In some embodiments, the first network device 230 determines the effectiveness of the second measurement adjustment parameter based on receiving third indication information indicating that the second measurement adjustment parameter is effective. In some embodiments, the first network device 230 receives the third indication information via a dedicated layer of data packets or via control signaling.

[0124] In some implementations, the first network device 230 is a UPF, and the first network device 230 determines the effectiveness of the second measurement adjustment parameter based on determining that the received service flow 217 is a specific service flow.

[0125] In some embodiments, the first network device 230 is a UPF (User-Defined Function), which can initiate the application of measurement adjustment parameters for multiple receiving nodes. For example, the first network device 230 determines the application of a second measurement adjustment parameter based on determining that the received traffic flow 217 is a specific traffic flow. Furthermore, the first network device 230 also sends an indication message indicating that the measurement adjustment parameters of at least one other receiving node on the transmission path of traffic flow 217 are in effect. In some embodiments, the first network device 230 sends this indication message via a dedicated layer of data packets or via control signaling.

[0126] In some implementations, before the first network device 230 performs the measurement in step 212, it may receive first information indicating that the terminal device on the transmission path of the service flow 217 has the ability to measure the time interval between adjacent data units of the service flow 217.

[0127] In some implementations, after determining that the QoS of the first network device 230 is abnormal, the first network device 230 performs corresponding adjustments, which can be done in various ways.

[0128] In some embodiments, the first network device 230 performs operations related to adjusting one or more of the following: transmission resources; transmission priority; transmission path; or serving cell. In some embodiments, the terminal device may receive information related to adjusting one or more of the following: transmission resources; transmission priority; transmission path; or serving cell. The information received by the terminal device related to adjusting transmission resources, transmission priority, transmission path, or serving cell may include, for example, uplink grant information in the embodiment of adjusting transmission resources; QoS flow identifiers in the embodiment of adjusting transmission priority; an indication of the adjusted transmission path in the embodiment of adjusting transmission path; and a cell handover command in the embodiment of adjusting serving cell. It should be noted that the above are merely examples of information related to adjusting one or more of the above-mentioned aspects, and may be replaced with other information or added according to implementation. This disclosure does not limit this.

[0129] In some implementations, the first network device 230 is an access network device, such as a RAN node. The first network device 230 can send second indication information to the terminal device. The second indication information is used to indicate the adjusted value of the packet delay budget (PDB) for service flow 217. The terminal device can receive the second indication information, which is used to indicate the adjusted value of the PDB for service flow 217.

[0130] In some implementations, the terminal device may send a request message to the first network device 230 (e.g., an access network device or a RAN node), the request message requesting that the PDB of the service flow 217 be adjusted to a first PDB value, wherein the request message includes the first PDB value. The first network device 230 (e.g., an access network device or a RAN node) receives the request message and adjusts the PDB of the service flow 217 to the first PDB value.

[0131] Figure 3 Schematic diagrams illustrating some embodiments of this disclosure that implement QoS guarantees are shown. Figure 3 In the illustrated embodiment, at the receiver (or receiving node, or packet receiving node) of the data packets in the continuous service flow, the arrival time interval of neighboring data packets in the continuous service flow is monitored. For example, the data packets in the continuous service flow are denoted as packet 1, packet 2, packet 3, etc., and the reception times of these data packets at the UE are T1, T2, and T3, respectively. The network (e.g., RAN node, UPF, or SMF) configures a maximum time interval T for each receiving node of the data packets in the service flow transmission. Taking the neighboring data packets received by the UE as an example, the UE counts the neighboring data packets whose arrival time interval is greater than the maximum time interval T. If the arrival time interval of more than a certain percentage (e.g., 20%) of the neighboring data packets is greater than the maximum time interval T, it means that the UE has detected a timeout in the received service flow, and the UE will report the timeout information to the upper node (i.e., the RAN node). For the RAN node, it will count the neighboring data packets whose arrival time interval is greater than the maximum time interval T from the data packets received from the UPF. If the RAN node receives the timeout information reported by the UE, and the proportion of neighboring data packets with an arrival time interval greater than the maximum time interval T among the data packets received from the UPF by the RAN node itself is 0%, then the RAN node can determine that there is a problem with the RAN node's QoS guarantee. The RAN node can improve the QoS, for example, by allocating more resources to ensure the transmission of this QoS stream, or by increasing the priority of the RAN node to send this QoS stream first.

[0132] Similarly, if the RAN node detects that more than a certain percentage (e.g., 20%) of neighboring data packets have arrival time intervals greater than the maximum time interval T, it means that the RAN node has detected a timeout in the received service flow. In this case, the RAN node will report the timeout information to the next higher node (i.e., the UPF). If the UPF does not detect a timeout at the UPF, the UPF determines that there is a problem with its QoS guarantee, and the UPF will increase the priority of the QoS flow.

[0133] The specific implementation of determining whether the DN has a QoS guarantee problem is similar to the operation performed by the RAN node or UPF mentioned above, and will not be repeated in this article.

[0134] It should be noted that, Figure 3 The embodiments described above use a single data packet as an example of a data unit in a service flow. Alternatively, a data unit can be implemented as multiple data packets, one or more frames, or one or more PDU sets, etc. For the other implementations of the data unit described above, the receiving node of the data unit counts the arrival time intervals of neighboring data units and compares these counted arrival time intervals with the maximum time interval T.

[0135] For service flows with high jitter requirements, since each data packet in the service flow needs to continuously reach the other end at the minimum interval within a specified time, the embodiments of this disclosure can achieve a significant QoS guarantee effect.

[0136] Figure 4 The diagram illustrates a process flow for implementing QoS guarantees using some embodiments of this disclosure. Figure 4 The illustrated process 400 involves UE 410, RAN node 120, UPF 430, SMF 440, and DN 450. UE 410 is an example of terminal device 110, UPF 430 is an example of first core network element 130, and SMF 440 is an example of second core network element 140. In some embodiments, RAN node 120, UPF 430, or first core network element 130 can be examples of first network device 220. SMF 440 or second core network element 140 can be examples of second network device 230. Process 400 takes the example of DN 450 sending data packets of service flow to UE 410 via UPF 430 and RAN node 120, i.e., the transmission direction of the service flow is the downlink transmission direction.

[0137] In step 402, UE 410 reports capability information indicating that UE 410 has the capability to support neighbor packet measurement. For example, when initiating a PDU session activation or modification request, UE 410 can include a capability indication of "supporting neighbor packet measurement" in the message it sends to SMF 440 to complete capability negotiation with the network side.

[0138] In some implementations, UE 410 may also receive response information indicating that other receiving nodes along the transmission path of the service flow (RAN node 120 and UPF 430 in this example) have the capability to support neighbor packet measurement. For example, SMF 440 carries this response information in a PDU session activation success message returned to UE 410.

[0139] Nodes (e.g., UE 410, RAN node 120, UPF 430) have the capability to support neighbor packet measurement, and there is an example implementation of the node having the ability to measure the time interval between adjacent data units of a traffic flow.

[0140] In some implementations, UE 410 can report this capability information through a PDU session establishment or PDU session modification process.

[0141] In step 404, SMF 440 determines (e.g., generates) neighbor packet measurement adjustment parameters for each node. In some embodiments, these neighbor packet measurement adjustment parameters may be referred to as measurement adjustment parameters.

[0142] In some implementations, the neighbor packet measurement adjustment parameters include a maximum neighbor packet time interval and a proportional threshold for the corresponding node. The maximum neighbor packet time interval may be referred to as a time interval threshold in some embodiments. In some implementations, the SMF 440 can configure the QoS parameters of each node based on user subscription information, and the SMF 440 may include the corresponding neighbor packet measurement adjustment parameters in the QoS parameters configured for the node.

[0143] In step 406a, SMF 440 sends the neighbor packet measurement adjustment parameters configured for UPF 430 to UPF 430. The neighbor packet measurement adjustment parameters in process 400 are referred to as measurement adjustment parameters in some embodiments.

[0144] In step 406b, SMF 440 sends the neighbor packet measurement adjustment parameters configured for RAN node 120 to RAN node 120.

[0145] In step 406c, SMF 440 sends the neighbor packet measurement adjustment parameters configured for UE 410 to UE 410. The neighbor packet measurement adjustment parameters configured for UE 410 can be an example of the first measurement adjustment parameters. For example, the notification message returned by SMF 440 to UE 410 to notify that the PDU session has been successfully activated / modified may include configured QoS parameters and may carry the neighbor packet measurement adjustment parameters configured for UE 410.

[0146] In steps 408a, 408b, and 408c, data packets of the continuous service flow are sent from DN 450 to UE 410 via UPF 430 and RAN node 120. UPF 430, RAN node 120, and UE 410 are the receiving nodes for the data packets.

[0147] As shown in steps 412a, 412b, and 412c, UPF 430, RAN node 120, and UE 410 adjust their parameters according to their respective neighbor packet measurements, measure the time interval for receiving neighbor packets, and count the percentage of neighbor packet time intervals that exceed the configured maximum neighbor packet time interval.

[0148] In some embodiments, each node can measure the time interval for receiving neighboring packets when the service flow is a specific service flow. In some embodiments, each node can measure the time interval for receiving neighboring packets after receiving an indication message indicating that the neighboring packet measurement adjustment parameters have taken effect.

[0149] In some embodiments, indication information indicating that neighbor packet measurement adjustment parameters are effective can be received via a dedicated layer (or coordination layer, or cooperation layer) of the data packet. In other embodiments, indication information indicating that neighbor packet measurement adjustment parameters are effective can be received via control signaling. The indication information received by UE 410 indicating that neighbor packet measurement adjustment parameters of UE 410 are effective may be an example of the first indication information.

[0150] If the percentage of cases reported by one of the nodes, including UPF 430, RAN node 120, and UE 410, exceeds the percentage threshold configured for that node, that node reports timeout information to its parent node indicating that the service flow reception has timed out. Step 414a shows the timeout information reported by UE 410 to RAN node 120 indicating that the service flow reception has timed out. Step 414b shows the timeout information reported by RAN node 120 to UPF 430 indicating that the service flow reception has timed out. Step 414c shows the timeout information reported by UPF 430 to DN 450 indicating that the service flow reception has timed out.

[0151] For each node that receives a timeout message, based on the received timeout message, the node's measurement of the time interval for receiving neighboring packets, and the node's statistics on the timeout of the time interval for receiving neighboring packets, it determines whether the timeout of the service flow of the next node (here, the next node refers to the node receiving the service flow sent by this node) is due to an abnormality in the QoS of this node. For example, if the node that receives the timeout message finds that 0% of the time intervals for receiving neighboring packets are greater than the maximum time interval for neighboring packets configured for this node, it means that the service flow received at this node did not time out, but the service flow sent from this node to the next node (the node receiving the service flow sent by this node) timed out, then it can be determined that there is a QoS abnormality at this node. Then, the node that receives the timeout message can send information related to service flow transmission adjustment. For example, in step 416a, DN 450 sends information related to service flow transmission adjustment to UPF 430. In step 416b, UPF 430 sends information related to service flow transmission adjustment to RAN node 120. In step 416c, RAN node 120 sends information related to service flow transmission adjustment to UE 410. In this embodiment of the disclosure, the node preceding a node refers to the node that sends data packets to that node, and the node following a node refers to the node that receives the data packets sent by that node.

[0152] In some embodiments, service flow transmission adjustment may include adjusting transmission resources, such as allocating more resources. In some embodiments, service flow transmission adjustment may include adjusting transmission priority, such as prioritizing data packets that are about to exceed the maximum time interval between adjacent packets. In some embodiments, service flow transmission adjustment may include adjusting the transmission path, such as switching the service flow transmission path from UE→RAN→UPF→UPF→DN to UE→RAN→UPF→DN, where "→" indicates the transmission direction of the service flow. In some embodiments, service flow transmission adjustment may include adjusting the serving cell, such as allocating a new serving cell for UE410.

[0153] The embodiments disclosed herein are not limited to the case of sending data packets in the downlink transmission direction as shown in process 400 above, i.e., DN 450 sending service flow data packets to UE 410 via UPF 430 and RAN node 120. They are also applicable to the case of sending data packets in the uplink transmission direction, i.e., UE 410 sending service flow data packets to DN 450 via RAN node 120 and UPF 430. (See reference...) Figure 4In the case of sending data packets in the uplink transmission direction, the receiving nodes of the data packets are RAN nodes 120, UPF 430, and DN 450. Accordingly, the neighbor packet measurement adjustment parameters are configured for RAN nodes 120, UPF 430, and DN 450. RAN nodes 120, UPF 430, and DN 450 measure the time interval for receiving neighbor packets from their respective upstream nodes according to their respective neighbor packet measurement adjustment parameters, and count the proportion of neighbor packet time intervals that exceed the configured maximum neighbor packet time interval. For details, please refer to the process 400 for sending data packets in the downlink transmission direction, which will not be described in detail in this article.

[0154] The above text Figure 4 The illustrated embodiment shows an implementation in which the neighbor packet measurement adjustment parameters for each node are determined (e.g., generated) by the SMF 440 and configured to each receiving node of the traffic flow. Figure 5 The illustrated procedure for configuring measurement adjustment parameters details an example embodiment of configuring neighbor packet measurement adjustment parameters for each node using the SMF 440.

[0155] like Figure 5 As shown, in process 500, in step 502, SMF 440 uses an artificial intelligence (AI) model or based on empirical values ​​to determine the maximum time interval and proportion threshold for neighboring packets for each node.

[0156] Alternatively, in some embodiments, the SMF 440 may receive from the UE 410 or UPF 430 the total time interval threshold (or total threshold value) of neighboring packets of a service flow across multiple receiving nodes on the transmission path, as determined by the UE 410 or UPF 430. The SMF 440 performs splitting based on the total time interval threshold to obtain the maximum time interval for each neighboring packet.

[0157] In step 504a, SMF 440 sends the maximum neighbor time interval and ratio threshold configured for UPF 430 to UPF 430.

[0158] In step 504b, SMF 440 sends the maximum neighbor packet time interval and proportion threshold configured for RAN node 120 to RAN node 120.

[0159] In step 504c, SMF 440 sends the maximum neighbor packet time interval and ratio threshold configured for UE 410 to UE 410.

[0160] In other embodiments, the neighbor packet measurement adjustment parameters for each node are determined (e.g., generated) by one of the UE 410, RAN node 120, or UPF 430 and configured for the other receiving nodes of the traffic flow. Such embodiments can be referred to... Figures 6 to 8 . Figures 6 to 8 The method for generating and configuring neighbor packet measurement adjustment parameters, as shown in one example, can be used as an alternative. Figure 4 Steps 404, 406a, 406b, and 406c (i.e., the way SMF 440 generates and configures the neighbor packet measurement adjustment parameters). In other words, Figure 4 The steps of determining and sending the neighbor packet measurement adjustment parameters involved in the process can be flexibly replaced with other possible implementations of the present disclosure, and all combinations are within the protection scope of the present disclosure.

[0161] refer to Figure 6 In process 600, one implementation is shown whereby the UE 410 determines and transmits proximity packet measurement adjustment parameters for each node. For example... Figure 6 As shown, in step 602, UE 410 can determine the total threshold value based on the current service type, and determine the maximum time interval and proportion threshold of neighboring packets for each receiving node.

[0162] The total threshold is the sum of the maximum time intervals between adjacent packets of a service flow at each receiving node along the transmission path. The total threshold is an example of a threshold representing the total time interval between adjacent data units of a service flow across multiple receiving nodes along the transmission path. For example, UE 410 playing a 720 resolution... For 480-pixel (480P) video at 24fps, traffic estimation can be performed by considering the video encoding format used by the current service and the maximum transmission unit (MTU = 1440 bytes / packet) configured for the PDU session. Based on this calculation, transmitting one frame of 480P video image requires approximately 15 data packets in its uncompressed state, and approximately 3 data packets after video encoding compression. Therefore, to meet the requirement of transmitting 24 frames of video per second, 360 (i.e., 24 frames / second × 15 packets / frame) to 72 data packets per second (i.e., 24 frames / second × 3 packets / frame) are needed. From this, it can be further calculated that the total threshold is approximately 14 milliseconds when using data packets as the data unit. If considering frames as the data unit, the reception time interval between adjacent frames (containing approximately 3 packets) is approximately 40 milliseconds, meaning the total threshold is 40 milliseconds.

[0163] The maximum time interval for neighboring packets at each receiving node can be obtained by dividing the total threshold value. Specifically, UE410 can know the transmission delay between UE410 and RAN node 120, thereby determining the time interval for receiving neighboring packets between RAN node 120 and UE410, or between UE410 and RAN node 120. UE410 can further estimate the time interval for receiving neighboring packets between RAN node 120 and UPF430, or between UPF430 and RAN node 120, and the time interval for receiving neighboring packets between DN450 and UPF430, or between UPF430 and DN450. The estimated time intervals can be estimated using an AI model or based on empirical values. For example, for a total threshold value of 14 milliseconds, taking the transmission of data packets in the downlink direction as an example, UE410 can divide the 14 milliseconds into three segments: the maximum time interval for neighboring packets at the UE is 8ms, the maximum time interval for neighboring packets at RAN node 120 is 2ms, and the maximum time interval for neighboring packets at UPF430 is 4ms. UE 410 determines the proportional threshold for each segment, for example, the proportional threshold at UE 410 is 5%, the proportional threshold at RAN node 120 is 2%, and the proportional threshold at UPF 430 is 3%. In some embodiments, UE 410 may use an AI model or based on empirical values ​​to estimate the proportional threshold for each receiving node.

[0164] In steps 604 and 606, UE 410 sends the maximum neighbor packet time interval and proportional threshold for each receiving node via control signaling. Specifically, UE 410 sends the maximum neighbor packet time interval and proportional threshold for RAN node 120 and UPF 430, respectively. RAN node 120 further sends the maximum neighbor packet time interval and proportional threshold for UPF 430 to UPF 430.

[0165] refer to Figure 7 In procedure 700, an alternative implementation is shown whereby the UE 410 determines and transmits proximity packet measurement adjustment parameters for each node. Figure 7 In the process shown, step 702 can be referred to Figure 6 This will be achieved in step 602 of the above steps, and will not be described again here.

[0166] In steps 704 and 706, UE 410 transmits the maximum neighbor time interval and proportion threshold for each receiving node via the dedicated layer (or coordination layer) of the data packet. In other words, when transmitting data packets in the uplink transmission direction, UE 410 can carry the maximum neighbor time interval and proportion threshold for each receiving node in the dedicated layer of the data packet.

[0167] refer to Figure 8 This illustrates one implementation whereby network nodes determine and transmit neighbor packet measurement adjustment parameters for each receiving node. In procedure 800, the network node can be RAN node 120 or UPF 430.

[0168] Figure 8 An example of a network node being UPF 430 is shown. In step 802, taking the transmission of a service flow in the downlink direction as an example, UPF 430 can obtain the maximum neighbor packet time interval between UPF 430 and RAN node 120, and the maximum neighbor packet time interval between DN 450 and UPF 430. By subtracting the maximum neighbor packet time intervals between UPF 430 and RAN node 120, and between DN 450 and UPF 430, from the total threshold value, the maximum neighbor packet time interval between RAN node 120 and UE 410 can be obtained, thus obtaining the receiving nodes (UPF 430, RAN node 120, UE 410) in the downlink direction. In some embodiments, UPF 430 can use an AI model or empirical values ​​to estimate the proportional threshold for each receiving node. In steps 804 and 806, UPF 430 sends the maximum neighbor packet time interval and proportional threshold for each receiving node to the corresponding receiving node through the dedicated layer (or coordination layer or cooperation layer) of the downlink data packets. In other implementations, network nodes can send proximity packet measurement adjustment parameters for each receiving node via control signaling, for example, by configuring the proximity packet measurement adjustment parameters for each receiving node through a PDU session establishment signaling procedure.

[0169] In some implementations, the neighbor packet measurement adjustment parameters for each receiving node can be modified according to service requirements. For example, one or more neighbor packet measurement adjustment parameters for each receiving node can be adjusted individually for different QoS flows.

[0170] For the method by which RAN node 120 determines and sends the neighbor packet measurement adjustment parameters for each node, please refer to [reference needed]. Figure 8 The network node shown is an example implementation of UPF 430. For the implementation of uplink transmission of service flows, the UPF 430 or RAN node 120 determines the implementation method for adjusting the neighbor packet measurement parameters for each receiving node, similar to the process described in the implementation of downlink transmission of service flows, except that the receiving nodes in the uplink transmission method are UPF 430, RAN node 120, and DN 450. Specific implementation steps are not described in detail.

[0171] For a specific example of how the network side splits the neighbor packet measurement adjustment parameters for each receiving node based on the total threshold, please refer to the example in procedure 600 where UE 410 splits 14 milliseconds into three segments.

[0172] Figure 9 and Figure 10 A flowchart illustrating the triggering of PDB adjustments according to some embodiments of this disclosure is shown. Step 902 is the same as step 1002, and step 904 is the same as step 1004. In step 902, after the PDU session is activated and the dedicated QoS flow is successfully established, the network configures PDB parameters for the specified QoS flow (e.g., 200ms on the RAN node side). In step 904, UE 410 starts measuring the time interval of received neighboring packets and monitors whether the UE 410's received service flow has timed out. For example, it monitors whether the measured time interval exceeds the maximum neighboring packet time interval for UE 410, and further determines whether the proportion of time intervals exceeding the maximum neighboring packet time interval exceeds a proportional threshold for UE 410. If the proportion exceeds the proportional threshold, it is determined that the UE 410's received service flow has timed out. Implementation details of this process are described in the other embodiments above.

[0173] If UE 410 determines that the received service flow has timed out, it can trigger the adjustment of PDB.

[0174] refer to Figure 9 As shown, one implementation of triggering PDB adjustment is illustrated. In step 906, UE 410 reports timeout information to RAN node 120, indicating that UE 410 has timed out of receiving service flows. The timeout information may include the percentage of time intervals exceeding the maximum time interval of adjacent packets in the measured time intervals (e.g., percentage: 20%), where this percentage exceeds a proportional threshold (e.g., 5%). In step 908, RAN node 120, based on its own statistics on whether the service flows received from UPF 430 have timed out, and the timeout information reported by UE 410, decides that PDB adjustment is necessary. For example, if the timeout information reported by UE 410 indicates an excess of 20%, and the proportional threshold is 5%, meaning an excess of 4 times, RAN node 120 can adjust the PDB proportionally, such as adjusting it to 200 / 5 = 40ms, or adjusting it to 100ms based on experience.

[0175] refer to Figure 10Procedure 1000 illustrates another implementation of triggering PDB adjustment. In step 1006, UE 410 sends a request message requesting that the PDB of the service flow be adjusted to a first PDB value, for example, the request message carries a first PDB value, such as 40ms. In step 1008, RAN node 120 adjusts the PDB of the service flow to the first PDB value, i.e., 40ms, according to the indication of the first PDB value in the request message.

[0176] Figure 11 Schematic process block diagrams illustrating the implementation of some embodiments of this disclosure at a terminal device are shown. For example... Figure 11 As shown in the process block diagram 1100, the process can be executed by a terminal device, such as terminal device 110, or a chip, module, or assembly that can implement the functions of terminal device 110 in the embodiments of this disclosure. The following description uses the execution of the process by a terminal device as an example. In block 1110, the terminal device measures the time interval between adjacent data units of the received service stream; in block 1120, the terminal device monitors whether the received service stream has timed out based on the time interval and a first measurement adjustment parameter for the terminal device, the first measurement adjustment parameter including a threshold related to timeout monitoring; in block 1130, the terminal device reports the timeout information of the service stream based on the determination that a timeout has been detected. In some embodiments, the process may also include the combination of the embodiments of this disclosure... Figures 2 to 10 Other operations described that are performed at the terminal device.

[0177] Figure 12 Schematic process block diagrams illustrating other embodiments of this disclosure implemented at a first network device are shown. For example... Figure 12 As shown in the process block diagram 1200, the process can be executed by a first network device, such as first network device 230, or a chip, module, or assembly that can implement the functions of first network device 230 in this embodiment. The following description uses the execution of the process by the first network device as an example. In block 1210, the first network device measures the time interval between adjacent data units of a service flow received from the first node; in block 1220, the first network device monitors whether the received service flow has timed out based on the time interval and a second measurement adjustment parameter for the first network device, the second measurement adjustment parameter including a threshold related to timeout monitoring; in block 1230, the first network device receives timeout information of a service flow reported by the second node, the timeout information indicating that the service flow received by the second node from the first network device has timed out; in block 1240, the first network device determines that the Quality of Service (QoS) of the first network device is abnormal based on receiving the timeout information and not detecting a timeout in the service flow received from the first node. In some embodiments, the process may also include elements combined with those described in this embodiment. Figures 2 to 10Other operations performed at the first network device are described.

[0178] Figure 13 A schematic process block diagram illustrating some embodiments of this disclosure implemented at a second network device is shown. For example... Figure 13 As shown in the process block diagram 1300, the process can be executed by a second network device, such as second network device 240, or a chip, module, or assembly that can implement the functions of second network device 240 in this embodiment. The following description uses the execution of the process by a second network device as an example. In block 1310, the second network device determines measurement adjustment parameters for multiple receiving nodes on the transmission path of the service flow; and in block 1320, the second network device sends configuration information to the multiple receiving nodes, wherein the configuration information includes measurement adjustment parameters for the corresponding nodes, the measurement adjustment parameters being used to monitor whether the service flow times out at the corresponding receiving node. In some embodiments, the process may also include, in conjunction with, the embodiments of this disclosure. Figures 2 to 10 Other operations described that are performed at the second network device.

[0179] Figure 14This is a block diagram that can be used to implement the device 1400 according to some embodiments of this application. In some embodiments, device 1400 may be an element of a communication network infrastructure, such as a base station (e.g., a NodeB, an evolved NodeB (eNodeB or eNB), a next-generation NodeB (sometimes called a next-generation NodeB, gNodeB or gNB), a home subscriber server (HSS), a gateway (GW), such as a packet gateway (PGW) or a serving gateway (SGW), or various other nodes or functions within a core network (CN) or a Public Land Mobility Network (PLMN). In other embodiments, device 1400 may be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, a smartphone, or other such device that can be classified as User Equipment (UE). In some embodiments, device 1400 may be a Machine Type Communications (MTC) device (also known as a machine-to-machine (M2M) device), or another such device that, although not providing direct service to a user, can be classified as a UE. In some embodiments, device 1400 may be a roadside unit. The device 1400 can be classified as a mobile unit (RSU), vehicle UE (V-UE), pedestrian UE (P-UE), or infrastructure UE (I-UE). In some scenarios, the device 1400 may also be referred to as a mobile device, a term intended to reflect a device connected to a mobile network, regardless of whether the device itself is designed for or capable of being mobile. A particular device may utilize all or only a subset of the components shown, and the level of integration may vary depending on the device. Furthermore, the device 1400 may contain multiple instances of components, such as multiple processors, memory, transmitters, receivers, etc.

[0180] Device 1400 typically includes a processor 1402, such as a central processing unit (CPU), and may further include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, memory 1404, a network interface 1406, and a bus 1408 for connecting the components of device 1400. Optionally, device 1400 may also include components such as mass storage 1410, a video adapter 1412, and an I / O interface 1416 (shown in dashed lines).

[0181] Memory 1404 may include any type of non-transitory system memory readable by processor 1402, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1404 may include more than one type of memory, such as ROM used at startup and DRAM used for program and data storage during program execution. Bus 1408 may be one or more of a plurality of bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus.

[0182] Device 1400 may also include one or more network interfaces 1406, which may include at least one of wired network interfaces and wireless network interfaces. For example... Figure 14 As shown, network interface 1406 may include a wired network interface for connecting to network 1422, and may also include a wireless access network interface 1420 for connecting to other devices via a wireless link. When device 1400 is a network infrastructure element, the wireless access network interface 1420 may be omitted for nodes or functions that are elements of a PLMN rather than elements at the wireless edge. When device 1400 is infrastructure at the wireless edge of the network, both wired and wireless network interfaces may be included. When device 1400 is a wirelessly connected device, such as a user equipment, the wireless access network interface 1420 may be present and may be supplemented by other wireless interfaces such as a WiFi network interface. Network interface 1406 allows device 1400 to communicate with remote entities such as those connected to network 1422.

[0183] Mass storage 1410 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via bus 1408. Mass storage 1410 may include, for example, one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage 1410 may be located remotely from device 1400 and may be accessed using a network interface such as interface 1406. In the illustrated embodiment, mass storage 1410 is distinct from memory 1404, which includes it, and mass storage 1410 typically performs storage tasks compatible with higher latency but typically provides low or no fluctuation. In some embodiments, mass storage 1410 may be integrated with memory 1404.

[0184] Optional video adapter 1412 and I / O interface 1416 (shown in dashed lines) provide interfaces for coupling device 1400 to external input and output devices. Examples of input and output devices include a display 1414 coupled to video adapter 1412 and an I / O device 1418, such as a touchscreen, coupled to I / O interface 1416. Other devices may be coupled to device 1400 and may utilize additional or fewer interfaces. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand that in embodiments where device 1400 is part of a data center, I / O interface 1416 and video adapter 1412 may be virtualized and provided via network interface 1406.

[0185] Figure 15 This is a schematic diagram of the structure of a device 1500 according to some embodiments of this application. For example... Figure 15 As shown, the device 1500 includes a measurement unit 1502, a monitoring unit 1504, and a reporting unit 1506. The device 1500 can be applied to applications such as... Figure 1The system architecture shown can implement the methods provided in the preceding embodiments, such as method 1100. Optionally, the physical manifestation of device 1500 can be a communication device, such as a terminal device. Alternatively, device 1500 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 1500 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0186] In some embodiments, the measurement unit 1502 may be configured to measure the time interval between adjacent data units of the received service flow; the monitoring unit 1504 may be configured to monitor whether the received service flow has timed out based on the time interval and a first measurement adjustment parameter for the terminal device, the first measurement adjustment parameter including a threshold related to monitoring timeout; and the reporting unit 1506 may be configured to report timeout information of the service flow based on determining that a timeout has been detected.

[0187] In some other embodiments, the apparatus 1500 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0188] Figure 16 This is a schematic diagram of the structure of the device 1600 according to other embodiments of this application. For example... Figure 16 As shown, the device 1600 includes a measurement unit 1602, a monitoring unit 1604, a receiving unit 1606, and a determination unit 1608. The device 1600 can be applied to applications such as... Figure 1The system architecture shown can implement the methods provided in the preceding embodiments, such as method 1200. Optionally, the physical manifestation of device 1600 can be a communication device, such as a first network device. Alternatively, device 1600 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 1600 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0189] In some embodiments, the measurement unit 1602 may be configured to measure the time interval between adjacent data units of a service flow received from the first node; the monitoring unit 1604 may be configured to monitor whether the received service flow has timed out based on the time interval and a second measurement adjustment parameter for the first network device, the second measurement adjustment parameter including a threshold related to monitoring timeout; the receiving unit 1606 may be configured to receive timeout information of a service flow reported by the second node, the timeout information indicating that the service flow received by the second node from the first network device has timed out; and the determining unit 1608 may be configured to determine that the QoS of the first network device is abnormal based on receiving the timeout information and not detecting a timeout of the service flow received from the first node.

[0190] In some other embodiments, the apparatus 1600 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0191] Figure 17 This is a schematic diagram of the structure of the device 1700 according to other embodiments of this application. For example... Figure 17 As shown, the device 1700 includes a determining unit 1702 and a transmitting unit 1704. The device 1700 can be applied to applications such as... Figure 1The system architecture shown can implement the methods provided in the preceding embodiments, such as method 1100. Optionally, the physical manifestation of device 1700 can be a communication device, such as a second network device. Alternatively, device 1700 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 1700 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0192] In some embodiments, the determining unit 1702 may be configured to determine measurement adjustment parameters for multiple receiving nodes on the transmission path of the service flow; the sending unit 1704 may be configured to send configuration information to multiple receiving nodes, wherein the configuration information includes measurement adjustment parameters for the corresponding node, and the measurement adjustment parameters are used to monitor whether the service flow times out at the corresponding receiving node.

[0193] In some other embodiments, apparatus 1700 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

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

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

[0196] Based on the above embodiments, this application also provides a computer program that, when run on a computer, causes the computer to execute any of the methods provided in the above embodiments.

[0197] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program. When executed by a computer, the computer program causes the computer to perform any of the methods provided in the above embodiments. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not limited to, a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code having the form of instructions or data structures and that can be accessed by a computer.

[0198] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory and implementing any of the methods provided in the above embodiments.

[0199] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

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

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

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

[0203] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable apparatus for implementation in a process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

Claims

1. A communication method, characterized in that, Applied to a terminal device, the method includes: Measure the time interval between adjacent data units received from the service stream; Based on the time interval and a first measurement adjustment parameter for the terminal device, it is monitored whether the received service stream has timed out, wherein the first measurement adjustment parameter includes a threshold related to monitoring the timeout; and Based on the confirmed timeout, the timeout information of the service flow is reported.

2. The method according to claim 1, characterized in that, Also includes: The measurement is performed based on the determination that the first measurement adjustment parameter is effective.

3. The method according to claim 2, characterized in that, It also includes determining the effectiveness of the first measurement adjustment parameter based on one or more of the following: Determine that the received service flow is a specific service flow; or A first indication message is received, indicating that the first measurement adjustment parameter is effective, wherein the first indication message is received via a dedicated layer of a data packet or via control signaling.

4. The method according to claim 2, characterized in that, Also includes: Sending indication information indicating that the measurement adjustment parameters of at least one other receiving node on the transmission path of the service flow are effective, wherein the indication information is sent via a dedicated layer of the data packet or via control signaling.

5. The method according to any one of claims 2 to 4, characterized in that, Before measuring the time interval, the following is also included: The terminal device reports capability information, which indicates that it has the ability to measure the time interval between adjacent data units of the service flow.

6. The method according to claim 5, characterized in that, Also includes: Receive response information indicating that other receiving nodes on the transmission path of the service flow have the ability to measure the time interval between adjacent data units of the service flow.

7. The method according to any one of claims 1 to 6, characterized in that, The threshold includes a first time interval threshold and a first proportion threshold, and determining that the timeout was detected includes: The first quantity percentage is determined to exceed the first proportion threshold, where the first quantity percentage is the percentage of adjacent data units whose time interval exceeds the first time interval threshold among the number of adjacent data units in the received service flow.

8. The method according to any one of claims 1 to 7, characterized in that, Also includes: Determine the total time interval threshold of adjacent data units of the service flow across multiple receiving nodes on the transmission path, wherein the terminal device is one of the multiple receiving nodes; as well as Measurement adjustment parameters for the plurality of receiving nodes are determined based on the total time interval threshold, wherein the measurement adjustment parameters for the plurality of receiving nodes include the first measurement adjustment parameter.

9. The method according to claim 8, characterized in that, The measurement adjustment parameters for the plurality of receiving nodes also include measurement adjustment parameters for at least one other receiving node, and the method further includes: The measurement adjustment parameters for at least one other receiving node are sent, wherein the measurement adjustment parameters for at least one other receiving node are sent via a dedicated layer of data packets or via control signaling.

10. The method according to any one of claims 1 to 7, characterized in that, Also includes: Determine the total time interval threshold of adjacent data units of the service flow across multiple receiving nodes on the transmission path, wherein the terminal device is one of the multiple receiving nodes; as well as Send information indicating the total time interval threshold.

11. The method according to any one of claims 1 to 7, or 10, characterized in that, Also includes: The first measurement adjustment parameter is received, wherein the first measurement adjustment parameter is received via a dedicated layer of a data packet or via control signaling.

12. The method according to claim 11, characterized in that, The first measurement adjustment parameter comes from one or more of the following: access network device, user plane function (UPF), or session management function (SMF).

13. The method according to any one of claims 1 to 12, characterized in that, Also includes: Receive information relating to adjustments to one or more of the following: transmission resources; transmission priority; transmission path, or serving cell.

14. The method according to any one of claims 1 to 12, characterized in that, Also includes: Receive a second indication message, which indicates the adjusted value of the packet delay budget (PDB) for the service flow; or Send a request message, the request message being used to request that the PDB of the service flow be adjusted to a first PDB value, wherein the request message includes the first PDB value.

15. The method according to any one of claims 1 to 14, characterized in that, The data unit includes one or more of the following: One or more data packets; One or more frames; or A collection of one or more Protocol Data Units (PDUs).

16. A communication method, characterized in that, Applied to a first network device, the method includes: Measure the time interval between adjacent data units received from the first node in the service flow; Based on the time interval and a second measurement adjustment parameter for the first network device, it is monitored whether the received service flow has timed out, wherein the second measurement adjustment parameter includes a threshold related to monitoring the timeout; Receive timeout information of the service flow reported by the second node, the timeout information indicating that the service flow received by the second node from the first network device has timed out; and Based on the receipt of the timeout information and the absence of a timeout detected in the service flow received from the first node, it is determined that the Quality of Service (QoS) of the first network device is abnormal.

17. The method according to claim 16, characterized in that, Also includes: The measurement is performed based on the determination that the second measurement adjustment parameter is effective.

18. The method according to claim 17, characterized in that, The effectiveness of the second measurement adjustment parameter is determined based on the receipt of a third indication message indicating that the second measurement adjustment parameter is effective, wherein the third indication message is received via a dedicated layer of a data packet or via control signaling.

19. The method according to any one of claims 16 to 18, characterized in that, The threshold includes a second time interval threshold and a second proportion threshold, and monitoring whether the received service flow times out includes: Monitor whether the second quantity percentage exceeds the second percentage threshold. The second quantity percentage is the percentage of adjacent data units whose time interval exceeds the second time interval threshold among the number of adjacent data units of the service flow received from the first node.

20. The method according to any one of claims 16-19, characterized in that, Also includes: Receive second information, which is used to indicate the total time interval threshold of adjacent data units of the service flow at multiple receiving nodes on the transmission path.

21. The method according to claim 20, characterized in that, Also includes: Based on the total time interval threshold, measurement adjustment parameters for the plurality of receiving nodes are determined, wherein the measurement adjustment parameters for the plurality of receiving nodes include the second measurement adjustment parameter and measurement adjustment parameters for at least one other receiving node, and The measurement adjustment parameters for at least one other receiving node are sent, wherein the measurement adjustment parameters for at least one other receiving node are sent via a dedicated layer of data packets or via control signaling.

22. The method according to claims 16 to 21, characterized in that, The first network device is a UPF, and the method further includes: Determine the total time interval threshold of adjacent data units of the service flow across multiple receiving nodes on the transmission path, wherein the UPF is one of the multiple receiving nodes; or Determine the total time interval threshold and send information indicating the total time interval threshold.

23. The method according to claim 22, characterized in that, Also includes: The second measurement adjustment parameter is received, wherein the second measurement adjustment parameter is received via a dedicated layer of a data packet or via control signaling.

24. The method according to claim 23, characterized in that, The first network device is an access network device, and the second measurement adjustment parameter comes from one or more of the following: a terminal device, a UPF, or a session management function (SMF); or The first network device is a UPF, and the second measurement adjustment parameter comes from one or more of the following: a terminal device, an access network device, or an SMF.

25. The method according to any one of claims 16 to 24, characterized in that, Also includes: Perform and adjust one or more of the following related operations: transmission resources; transmission priority; transmission path, or serving cell.

26. The method according to any one of claims 16 to 25, characterized in that, The first network device is an access network device, and the method further includes: Send a second indication message, which indicates the adjusted value of the packet delay budget (PDB) for the service flow; or A request message is received, the request message being used to request that the PDB of the service flow be adjusted to a first PDB value, wherein the request message includes the first PDB value; and the PDB of the service flow is adjusted to the first PDB value.

27. A communication method, characterized in that, Applied to a second network device, the method includes: Determine the measurement and adjustment parameters for multiple receiving nodes along the transmission path used for the service flow; and Configuration information is sent to the plurality of receiving nodes, wherein the configuration information includes the measurement adjustment parameters for the corresponding nodes, and the measurement adjustment parameters are used to monitor whether the service flow times out at the corresponding receiving node.

28. A communication device, comprising: A processor for performing the method according to any one of claims 1 to 15, 16-26, or 27.

29. A computer-readable storage medium storing instructions that, when executed, cause the method according to any one of claims 1 to 15, claims 16-26, or claim 27 to be performed.

30. A computer program product comprising instructions for causing the method according to any one of claims 1 to 15, 16-26, or 27 to be implemented.

Images