Communication method and device

Abstract

The present application provides a communication method and a communication device. The method includes a step of a first device determining information about a service flow arrival time, where the information about the service flow arrival time includes a service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time when a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element. The first device determines information about a service flow transmission time based on the information about the service flow arrival time. The first device instructs the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element. According to the above method, the deterministic latency requirement of the first service flow can be met, and the overall network performance can be improved.

Description

[Technical Field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202111468102.2, filed with the State Intellectual Property Office of China on December 3, 2021, entitled "Communication Method and Apparatus," which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD Embodiments of the present application relate to the field of wireless communications, and more particularly to communication methods and devices. [Background technology]

[0003] In the data packet transmission process of the conventional Ethernet, when a large number of data packets arrive at a transmission port within a short time, the transmission latency is high or packet loss problems occur. Therefore, the conventional Ethernet cannot provide services with high reliability and guaranteed transmission latency, and cannot meet the requirements of fields such as vehicle control and industrial Internet.

[0004] The Institute of Electrical and Electronics Engineers (IEEE) has defined the time sensitive networking (TSN) standard to meet the requirements of reliable, latency-sensitive transmission. The standard provides reliable, latency-sensitive transmission services based on Layer 2 switching, ensuring data transmission reliability for latency-sensitive services and ensuring predictable end-to-end transmission latency.

[0005] As shown in Figure 1, a TSN system may include a centralized network configuration (CNC) network element, a centralized user configuration (CUC) network element, TSN terminals (end stations), and switching nodes (TSN Bridges). The TSN terminals include a transmitter (talker) and a receiver (listener).

[0006] The entire 5G system (5GS) can be used as a switching node. A CNC network element can configure each switching node based on information reported by the 5GS and other switching nodes to ensure end-to-end deterministic latency (from the TSN talker to the TSN listener). As shown in Figure 2, a 5G system used as a switching node includes at least the following devices: a User Plane Function (UPF) network element, a TSN translator (TT) on the UPF network element side (hereinafter simply referred to as the TSN network side TT (NW-TT)), a next-generation NodeB (gNB), a user equipment (UE), and a UE-side TT (hereinafter simply referred to as the device side TT (DS-TT)). A downlink data packet is used as an example. Data packets are transmitted from the TSN system to the NW-TT, which then transmits the data packets to the DS-TT through the UPF network element, the gNB and the UE.

[0007] For data packets with deterministic latency requirements, 5GS needs to determine a corresponding packet delay budget (PDB) based on the latency requirements of the data packets, and ensure that the transmission time of the data packets between the UE and the UPF network element is not greater than the PDB. How to meet the deterministic latency requirements and improve the overall network performance is an urgent problem to be solved. Summary of the Invention

[0008] According to a first aspect, the present application provides a communication method, the method comprising:

[0009] A first device determines information about a service flow arrival time, where the information about the service flow arrival time includes a service flow arrival time or an offset of the service flow arrival time relative to a reference time, where the service flow arrival time is the time when the first service flow arrives at the second device, and the first service flow is a periodic service flow transmitted between the access network device and a user plane network element. The first device determines information about a service flow transmission time based on the information about the service flow arrival time. After receiving the first service flow, the first device instructs the second device to wait until the service flow transmission time and then transmit the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0010] According to the above method, the first device first determines information about a service flow arrival time, and then determines information about a service flow transmission time based on the information about the service flow arrival time, so that after receiving the first service flow, the second device can wait until the service flow transmission time before transmitting the first service flow. In other words, the first device configures the time at which the second device will transmit the first service flow, and the second device waits until the specified service flow transmission time to transmit the first service flow according to the configuration and instructions of the first device. Through the coordinated configuration of the first device, congestion does not occur even when the second device receives multiple service flows simultaneously or within a certain period of time, so that the deterministic latency requirements of each flow can be met, thereby improving overall network performance.

[0011] In a possible design, when instructing the second device to wait until the service flow transmission time after receiving the first service flow before transmitting the first service flow, the first device transmits information about the service flow transmission time to the second device.

[0012] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time is no more than a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0013] In the above design, the service flow transmission time is not later than the latest transmission time, or the offset of the service flow transmission time relative to the reference time does not exceed the maximum offset, so that the latency requirement of the first service flow can be met when the second device transmits the first service flow.

[0014] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0015] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0016] In a possible design, the service flow transmission time determined by the first device at which the second device transmits the second service flow is different from the service flow transmission time determined by the first device at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0017] In the above design, the first device determines different service flow transmission times for the first service flow and the second service flow, thereby avoiding congestion between the first service flow and the second service flow and ensuring the deterministic latency requirements of the first service flow and the second service flow separately.

[0018] In a possible design, when determining information about a service flow transmission time based on information about the service flow arrival time, the first device obtains an offset selection value, where the offset selection value is greater than or equal to a minimum offset and less than or equal to a maximum offset, or the offset selection value is greater than or equal to an offset of the earliest transmission time relative to a reference time and less than or equal to an offset of the latest transmission time relative to the reference time; the first device determines the information about the service flow transmission time based on the offset selection value.

[0019] In the above design, the first device first determines the minimum offset and the maximum offset, or the offset of the earliest transmission time relative to a reference time and the offset of the latest transmission time relative to the reference time, then obtains an offset selection value, and determines information about the service flow transmission time based on the offset selection value.

[0020] In a possible design, when obtaining the offset selection value, the first device transmits the minimum offset and the maximum offset, or the offset of the earliest transmission time relative to the reference time and the offset of the latest transmission time relative to the reference time, to the fourth device; and the first device receives the offset selection value from the fourth device.

[0021] In a possible design, when obtaining the offset selection value, the first device determines a latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, a processing time for the first service flow at the second device, and a processing time for the first service flow at the third device; and the first device sends the latency requirement to the fourth device. The third device is a device for receiving the first service flow, and if the first service flow is an uplink service flow, the third device is a user plane network element, or if the first service flow is a downlink service flow, the third device is an access network device or a translator corresponding to the access network device.

[0022] In the above design, the fourth device may determine the offset selection value by referring to a latency requirement. In addition, the first device further transmits the priority of the first service flow to the fourth device. It may be understood that the fourth device may refer to multiple parameters when determining the offset selection value. How the fourth device determines the offset selection value is not limited in this application.

[0023] In a possible design, when determining information about a service flow transmission time based on an offset selection value, the first device determines information about the service flow transmission time based on the offset selection value and a jitter latency associated with the first service flow.

[0024] In a possible design, the information about the service flow transmission time includes a gated scheduling parameter. The first device may determine the gated scheduling parameter according to the following method: The first device obtains a cycle of the first service flow and a maximum burst size of the first service flow. The first device determines a maximum frame size of the first service flow based on the maximum burst size of the first service flow. The first device determines the gated scheduling parameter based on the cycle of the first service flow, the maximum frame size of the first service flow, and an offset selection value.

[0025] In the above design, the first device may determine a gate control scheduling parameter based on the cycle of the first service flow, the maximum burst size of the first service flow, and the offset selection value, where the gate control scheduling parameter is a gate control scheduling parameter for the second device.

[0026] In a possible design, when the first service flow is an uplink service flow, the first service flow arrives at the second device through a terminal device. When determining the information about the service flow arrival time, the first device obtains information about the time the first service flow arrives at a translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; the first device determines the information about the service flow arrival time based on the information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0027] In the above design, the first device may determine information about the service flow arrival time in a scenario where the first service flow is an uplink service flow.

[0028] In a possible design, the first device is a time-sensitive networking TSN application function network element. The first device determines the information about the time the first service flow arrives at the translator on the terminal device side when obtaining information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; the first device receives from the session management network element, the residence time of the first service flow at the translator on the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0029] In a possible design, the first device is a session management network element. The first device receives, from the policy control network element, information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device when obtaining the information about the time the first service flow arrives at the translator on the terminal device side; the first device receives, from the terminal device, the residence time of the first service flow at the terminal device and the translator on the terminal device side; and the first device determines a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0030] According to a second aspect, the present application provides a communication method, comprising: a second device receiving a first service flow, where the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; the second device receiving information about a service flow transmission time from the first device; and the second device waiting until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0031] According to the above method, after receiving a first service flow at the service flow arrival time, the second device waits until the service flow transmit time indicated by the first device before transmitting the first service flow. Therefore, the second device can transmit the first service flow based on the service flow transmit time indicated by the first device. In other words, the first device configures the time at which the second device will transmit the first service flow, and the second device waits until the specified service flow transmit time to transmit the first service flow according to the configuration and instructions of the first device. Through the coordinated configuration of the first device, congestion does not occur even when the second device receives multiple service flows simultaneously or within a certain period of time. As a result, the deterministic latency requirements of each flow can be met, thereby improving overall network performance.

[0032] In a possible design, the service flow transmission time at which the second device transmits the second service flow is different from the service flow transmission time at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0033] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time is no more than a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0034] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0035] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0036] In a possible design, the information about the service flow transmission times includes gate control scheduling parameters.

[0037] In a possible design, the first device is a TSN application function network element, or the first device is a session management network element.

[0038] According to a third aspect, the present application provides a communications apparatus. The apparatus is a first device or an apparatus having the functionality of a first device, the apparatus comprising: a processing unit configured to determine information about a service flow arrival time, where the information about the service flow arrival time includes a service flow arrival time or an offset of the service flow arrival time relative to a reference time, where the service flow arrival time is a time when a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element, where the processing unit is configured to determine information about a service flow transmission time based on the information about the service flow arrival time; and a transceiver unit configured to instruct the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0039] In a possible design, when instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow, the transceiver unit is configured to transmit information about the service flow transmission time to the second device.

[0040] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time is no more than a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0041] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0042] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0043] In a possible design, the service flow transmission time determined by the first device at which the second device transmits the second service flow is different from the service flow transmission time determined by the first device at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0044] In a possible design, when determining information about a service flow transmission time based on information about the service flow arrival time, the processing unit is configured to: obtain an offset selection value, where the offset selection value is greater than or equal to a minimum offset and less than or equal to a maximum offset, or the offset selection value is greater than or equal to an offset of the earliest transmission time relative to a reference time and less than or equal to an offset of the latest transmission time relative to the reference time; and determine the information about the service flow transmission time based on the offset selection value.

[0045] In a possible design, the transceiver unit is configured to transmit to the fourth device a minimum offset and a maximum offset, or an offset of the earliest transmission time relative to a reference time and an offset of the latest transmission time relative to the reference time; and to receive an offset selection value from the fourth device.

[0046] In a possible design, the processing unit is further configured to determine a latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, a processing time for the first service flow at the second device, and a processing time for the first service flow at the third device; and the transceiver unit is further configured to send the latency requirement to a fourth device. The third device is a device for receiving the first service flow, and if the first service flow is an uplink service flow, the third device is a user plane network element, or if the first service flow is a downlink service flow, the third device is an access network device or a translator corresponding to an access network device.

[0047] In a possible design, when determining information about a service flow transmission time based on an offset selection value, the processing unit is configured to determine information about the service flow transmission time based on the offset selection value and a jitter latency associated with the first service flow.

[0048] In one possible design, the information about the service flow transmission time includes a gated scheduling parameter, and the processing unit is configured to: obtain a cycle of the first service flow and a maximum burst size of the first service flow; determine a maximum frame size of the first service flow based on the maximum burst size of the first service flow; and determine the gated scheduling parameter based on the cycle of the first service flow, the maximum frame size of the first service flow, and the selected offset value.

[0049] In a possible design, when the first service flow is an uplink service flow, the first service flow arrives at the second device through the terminal device. When determining the information about the service flow arrival time, the processing unit is configured to: obtain information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determine the information about the service flow arrival time based on the information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0050] In a possible design, the first device is a time-sensitive networking TSN application function network element. When obtaining information about a time at which the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device, the processing unit is configured to determine the information about the time at which the first service flow arrives at the translator on the terminal device side. The transceiver unit is configured to receive, from the session management network element, the residence time of the first service flow at the translator on the terminal device side and the packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0051] In a possible design, the first device is a session management network element. When information about the arrival time of the first service flow at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device are obtained, the transceiver unit is configured to receive, from the policy control network element, the information about the arrival time of the first service flow at the translator on the terminal device side; and receive, from the terminal device, the residence time of the first service flow at the terminal device and the translator on the terminal device side. The processing unit is configured to determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0052] According to a fourth aspect, the present application provides a communications apparatus. The apparatus is a second device or an apparatus having the functionality of a second device, and the apparatus includes: a transceiver unit configured to receive a first service flow, where the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; and receive information about a service flow transmission time from the first device; and a processing unit configured to wait until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow to a third device. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to an access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0053] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time is no more than a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0054] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0055] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0056] In a possible design, the service flow transmission time at which the second device transmits the second service flow is different from the service flow transmission time at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0057] In a possible design, the information about the service flow transmission times includes gate control scheduling parameters.

[0058] In a possible design, the first device is a TSN application function network element, or the first device is a session management network element.

[0059] According to a fifth aspect, the present application further provides an apparatus, capable of carrying out the design of the above method, which may be a chip or circuit capable of carrying out functions corresponding to the above method, or a device including a chip or circuit.

[0060] In one possible implementation, the apparatus includes: a memory configured to store computer-executable program code; and a processor, wherein the processor is coupled to the memory. The program code stored in the memory includes instructions. When the processor executes the instructions, the apparatus, or a device in which the apparatus is installed, can perform the method in any one of the possible designs above.

[0061] The device may further include a communication interface. The communication interface may be a transceiver. Alternatively, if the device is a chip or circuit, the communication interface may be an input / output interface of the chip, for example an input / output pin.

[0062] In a possible design, the apparatus comprises corresponding functional units configured to separately implement the steps of the method. The functions can be implemented by hardware or by executing corresponding software. The hardware or software comprises one or more units corresponding to the functions.

[0063] According to a sixth aspect, the present application provides a computer-readable storage medium storing a computer program, the computer program, when executed on an apparatus, performing the method of any one of the above possible designs.

[0064] According to a seventh aspect, the present application provides a computer program product, the computer program product comprising a computer program, which, when run on an apparatus, performs the method of any one of the above possible designs.

[0065] According to an eighth aspect, the present application provides a communication system, the system including a first device and a second device, the first device configured to perform the method of any possible design of the first aspect, and the second device configured to perform the method of any possible design of the second aspect.

[0066] In a possible design, the first device is a TSN application function network element, or the first device is a session management network element.

[0067] In a possible design, if the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to an access network device; or, if the first service flow is a downlink service flow, the second device is a user plane network element.

[0068] In one possible design, the system further includes a third device for receiving the first service flow. When the first service flow is an uplink service flow, the third device is a user plane network element. When the first service flow is a downlink service flow, the third device is an access network device or a translator corresponding to the access network device.

[0069] According to a ninth aspect, the present application provides a communication system, the system including a second device and a third device, the second device configured to perform the method of any possible design of the second aspect, the third device being a device for receiving a first service flow.

[0070] For example, if the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to an access network device, and the third device is a user plane network element.

[0071] If the first service flow is a downlink service flow, the second device is a user plane network element, and the third device is an access network device or a translator corresponding to an access network device. [Brief explanation of the drawings]

[0072] [Figure 1] 1 is a schematic diagram of a fully centralized configuration model of a TSN system.

[0073] [Figure 2] 1 is a schematic diagram of a forwarding path of a first service flow in a 5G system.

[0074] [Figure 3] FIG. 1 is a schematic diagram of an evolved packet system architecture.

[0075] [Figure 4A] FIG. 1 is a system architecture diagram of the interaction between a 3GPP network and a TSN system.

[0076] [Figure 4B] FIG. 1 is a system architecture diagram of the interaction between a 3GPP network and a non-TSN system.

[0077] [Figure 5] FIG. 1 is a schematic diagram of the long tail effect.

[0078] [Figure 6A] 1 is a schematic diagram of an architecture to which embodiments of the present application are applied;

[0079] [Figure 6B] FIG. 2 is a schematic diagram of another architecture to which embodiments of the present application may be applied;

[0080] [Figure 7A] FIG. 1 is a schematic diagram of yet another architecture to which embodiments of the present application may be applied.

[0081] [Figure 7B] FIG. 1 is a schematic diagram of yet another architecture to which embodiments of the present application may be applied.

[0082] [Figure 8] 1 is a schematic flowchart of a communication method according to an embodiment of the present application;

[0083] [Figure 9] FIG. 2 is a schematic diagram of a forwarding path of a first service flow when the first service flow is an uplink service flow according to an embodiment of the present application;

[0084] [Figure 10]FIG. 2 is a schematic diagram of a forwarding path of a first service flow when the first service flow is a downlink service flow according to an embodiment of the present application;

[0085] [Figure 11] FIG. 2 is a schematic diagram of gate control states corresponding to a transmission queue according to an embodiment of the present application;

[0086] [Figure 12A] FIG. 1 is a schematic diagram of gate control states according to an embodiment of the present application.

[0087] [Figure 12B] FIG. 10 is a schematic diagram of another gate control state according to an embodiment of the present application.

[0088] [Figure 12C] FIG. 10 is a schematic diagram of yet another gate control state according to an embodiment of the present application.

[0089] [Figure 12D] FIG. 10 is a schematic diagram of yet another gate control state according to an embodiment of the present application.

[0090] [Figure 12E] FIG. 10 is a schematic diagram of yet another gate control state according to an embodiment of the present application.

[0091] [Figure 13] 3 is a transmission flowchart of a first service flow according to an embodiment of the present application;

[0092] [Figure 14] 10 is another transmission flowchart of the first service flow according to an embodiment of the present application;

[0093] [Figure 15A] 10 is yet another transmission flowchart of the first service flow according to an embodiment of the present application; [Figure 15B] 10 is yet another transmission flowchart of the first service flow according to an embodiment of the present application;

[0094] [Figure 16] 10 is yet another transmission flowchart of the first service flow according to an embodiment of the present application;

[0095] [Figure 17] FIG. 1 is a schematic diagram of yet another architecture to which embodiments of the present application may be applied.

[0096] [Figure 18A] 4 is yet another transmission flowchart according to an embodiment of the present application; [Figure 18B] 4 is yet another transmission flowchart according to an embodiment of the present application;

[0097] [Figure 19] 1 is a schematic diagram of the structure of an apparatus according to an embodiment of the present application;

[0098] [Figure 20] 1 is a schematic diagram of another configuration of an apparatus according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0099] The following clearly and completely describes the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. It is clear, however, that the described embodiments are merely a part, not all, of the embodiments of the present application. In the specification, claims, and accompanying drawings of the present application, terms such as "first" and "second" and their corresponding numerals are intended to distinguish similar objects, but do not necessarily indicate a specific order or sequence. It should be understood that the terms used in this manner are interchangeable in appropriate circumstances, and are merely a way of distinguishing objects having the same attributes when described in the embodiments of the present application. In addition, the terms "comprise" and "have" and any other variations thereof are intended to cover non-exclusive inclusions, such that a process, method, system, product, or device comprising a series of units is not necessarily limited to those units and may include other units not expressly listed or inherent in the process, method, product, or device.

[0100] In the present description, unless otherwise specified, " / " means "or." For example, A / B can mean A or B. In the present description, "and / or" only describes a correspondence relationship to describe related objects and indicates that three relationships may exist. For example, A and / or B can represent three cases: when only A is present, when both A and B are present, and when only B is present. In addition, in the present description, "at least one item" means one or more items, and "multiple items" means two or more items. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of singular item(s) or multiple items. For example, at least one of a, b, or c can refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can indicate singular or plural.

[0101] The technical solutions provided in the embodiments of the present application may be applied to various communication systems. For example, the technical solutions may be applied to a long term evolution (LTE) system or a 5G system, or may be applied to another future-oriented new system, such as a programmable user plane system. This is not particularly limited in the embodiments of the present application. In addition, the terms "system" and "network" are interchangeable.

[0102] Figure 3 is a schematic diagram of an evolved packet system (EPS) architecture. The system architecture is divided into two parts: an access network and a core network. The access network is configured to implement functions related to radio access. Access network elements include radio access network (RAN) devices. The core network mainly includes the following network elements: an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, a unified data repository (UDR) network element, an authentication server function (AUSF) network element, a network exposure function (NEF) network element, and an application function (AF) network element.

[0103] In the following, the device in the embodiment of the present application will be briefly described with reference to FIG.

[0104] A terminal device may be connected to an access network device to access a communication system. The terminal device may also be referred to as a terminal, UE, mobile station, mobile terminal, or the like. The terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in autonomous driving, a wireless terminal in remote surgery, a wireless terminal in smart grids, a wireless terminal in road safety, a wireless terminal in smart cities, a wireless terminal in smart homes, or the like. The specific technology and specific device configuration used for the terminal device are not limited in the embodiments of the present application. As shown in FIG. 3, the terminal device may be a UE.

[0105] The access network device may be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a gNB, a base station in a future mobile communication system, an access node in a Wi-Fi system, or the like. Alternatively, the access network device may be a module or unit that completes some functions of a base station, such as a central unit (CU) or a distributed unit (DU). The specific technology and specific device form used for the access network device are not limited in the embodiments of the present application. As shown in FIG. 3, the access network device may be an NR-RAN device.

[0106] The access management network element is used for mobility management, access management, and the like, such as updating the location of a terminal device, registering a terminal device to a network, and terminal device handover. The access management network element may be a mobility management entity (MME) function in a 4G mobile communication system or an AMF network element in a 5G mobile communication system. In future mobile communication systems, such as a 6G mobile communication system, the access management network element may still be an AMF network element or may have another name, which is not limited in this application. Namf is a service-based interface provided by AMF. The AMF may communicate with another network function through Namf. As shown in Figure 3, the access management network element may be an AMF network element.

[0107] A session management network element is used for session management, such as session establishment, modification, and release. The session management network element is further configured to assign an Internet Protocol (IP) address to a terminal device, select a UPF that provides a data packet forwarding function, and so on. In a 5G mobile communication system, the session management network element may be an SMF network element. In future mobile communication systems, such as a 6G mobile communication system, the session management function network element may still be an SMF network element or may have another name, which is not limited in this application. NSMF is a service-based interface provided by SMF. The SMF may communicate with another network function through NSMF. As shown in Figure 3, the session management network element may be an SMF network element.

[0108] The policy control network element is configured to provide policy rule information and the like, such as Quality of Service (QoS) policies and slice selection policies, to the access management network element or the session management network element. In a 5G mobile communication system, the policy control network element may be a PCF network element. In future mobile communication systems, such as a 6G mobile communication system, the policy control function network element may still be a PCF network element or may have another name, which is not limited in this application. As shown in Figure 3, the policy control network element may be a PCF network element.

[0109] The data management network element is configured to store data of a terminal device, such as subscription information and authentication / authorization information. In a 5G mobile communication system, the data management network element may be a UDM network element. In future mobile communication systems, such as a 6G mobile communication system, the data management network element may still be a UDM network element or may have another name. This is not a limitation in this application. As shown in Figure 3, the data management network element may be a UDM network element.

[0110] The data repository network element is responsible for storing structured data, and the stored contents include subscription data, policy data, publicly available structured data, and application-related data. In a 5G mobile communication system, the data repository network element may be a UDR network element. In future communication systems, such as a 6G mobile communication system, the data repository network element may still be a UDR network element or may have another name. This is not a limitation in this application.

[0111] The authentication server function network element is mainly responsible for providing authentication functions and supporting authentication for 3GPP access and non-3GPP access. In a 5G mobile communication system, the authentication server function network element may be an authentication server function AUSF network element. In future communication systems, such as a 6G mobile communication system, the authentication server function network element may still be an AUSF network element or may have another name. This is not a limitation in this application.

[0112] The network disclosure function network element mainly provides services to enable a 3GPP network to securely provide network service capabilities to third-party service providers, i.e., application function network elements. In a 5G communication system, the network disclosure function network element may be an NEF network element. In future communication systems, such as a 6G mobile communication system, the network disclosure function network element may still be an NEF network element or may have another name. This is not a limitation in this application.

[0113] The application function network element is configured to provide a service to a 3GPP network, for example, to influence service routing and to interact with a policy control network element for policy control. In 5G communication, the application function network element may be an AF network element. In future communication, for example, 6G communication, the application function network element may still be an AF network element or may have another name. This is not limited in this application. As shown in Figure 3, the application function network element may be an AF network element.

[0114] The user plane network element is configured to process data packets of a terminal device, for example, to perform forwarding and charging. In 5G communication, the user plane network element may be a UPF network element. In future communication, for example, 6G communication, the user plane network element may still be a UPF network element or may have another name. This is not a limitation in this application. As shown in Figure 3, the user plane network element may be a UPF network element.

[0115] A data network (DN) is a network that provides data transmission services to terminal devices. A data network can be a private network, such as a local area network, or an external network not managed and controlled by an operator, such as the Internet, or a dedicated network deployed by an operator, such as a network providing IP multimedia core network subsystem (IMS) services. A terminal device can access a data network by establishing a connection from the terminal device to the data network through an access network device and a user plane network element.

[0116] Currently, a fully centralized configuration model is defined for TSN systems. Figure 1 is a schematic diagram of the fully centralized configuration model for TSN systems. The following briefly describes the functions of the devices in Figure 1.

[0117] A TSN terminal includes a talker and a listener, which are the sender and receiver of a service flow, respectively.

[0118] The CUC network element is responsible for discovering and managing TSN terminals, obtaining TSN terminal capability information and user requirements, sending service flow requirements to the CNC network element, and configuring the TSN terminals according to the instructions of the CNC network element.

[0119] The CNC network element is configured to determine an end-to-end (E2E) forwarding path of the service flow based on the topology of the user plane of the TSN system (including the topology between the TSN terminal and each switching node), the capability information of each switching node, and the requirements of the service flow sent by the CUC network element, and to configure the switching nodes on the forwarding path.

[0120] The switching node is configured to send capability information of the switching node to the CNC network element, determine gate control scheduling parameters based on the configuration information of the CNC network element, and schedule and forward the service flow based on the gate control scheduling parameters.

[0121] 4A is a system architecture diagram of the interaction between a 3GPP network and a TSN system. The entire 5G system (5GS) is used as a switching node. The TSN Application Function (AF) network element in the 5GS exchanges information with nodes in the TSN system.

[0122] Note that the DS-TT may be located inside or outside the UE, and the NW-TT may be located inside the UPF. A downlink data packet is used as an example. The DS-TT may determine gate control scheduling parameters based on configuration information sent by the CNC network element and transmit data packets based on the gate control scheduling parameters. To ensure that the data packets can be transmitted in time, the data packets cannot arrive at the DS-TT later than a certain time point, thereby ensuring that the data packets can be transmitted in a gate-opening process. The gate-opening process refers to the range of time during which the gate state is open. If a data packet arrives at the DS-TT before the start time of the gate state opening indicated by the gate control scheduling parameters, the data packet needs to be buffered in the DS-TT until the gate state opening time and then transmitted. If a data packet arrives at the DS-TT after the start time of the gate state opening indicated by the gate control scheduling parameters, the DS-TT needs to complete transmission of the data packet before the gate state is switched to a closed state. Similarly, the NW-TT may also determine gated scheduling parameters based on the configuration information sent by the CNC network element and transmit data packets based on the gated scheduling parameters. For example, the NW-TT may transmit an uplink service flow received over 5GS to a next-hop switching node adjacent to the 5GS on the forwarding path; or the NW-TT may be configured to receive a downlink service flow from a previous-hop switching node adjacent to the 5GS on the forwarding path and transmit the downlink service flow to the 5GS.

[0123] 4B is a system architecture diagram of the interaction between a 3GPP network and a non-TSN system. In a non-TSN scenario, a time sensitive communication and time synchronization function (TSCTSF) network element is used to support clock synchronization services and enable time sensitive communication (TSC) services in a non-TSN scenario. The TSCTSF network element in 5GS exchanges information directly with the AF network element, or the TSCTSF exchanges information with the AF network element through the NEF.

[0124] As shown in Figure 2, in deterministic low latency scenarios, such as some industrial control scenarios, very low end-to-end latency is required. For example, the latency between the UE (or DS-TT) and the UPF (or NW-TT) needs to be less than 2 ms. However, transmission between the gNB and the UPF is performed in tunnel mode. In other words, when a data packet of a service flow arrives at an egress port of the gNB, the UPF, or a transmission node (e.g., a switch) between the gNB and the UPF, as long as there are idle transmission resources, the data packet is transmitted directly without waiting. When data packets of multiple service flows arrive at one egress port of the node simultaneously (i.e., a microburst scenario), the transmission latency of the data packet between the gNB and the UPF may be high due to congestion, e.g., exceeding 0.5 ms. As a result, the end-to-end transmission latency may not meet service requirements, e.g., exceeding 2 ms, affecting the implementation of end-to-end low latency. It may be understood that the forwarding path between the gNB and the UPF may further include at least one transmitting node (not shown in Figures 4A and 4B), which may be a switch (shown in Figure 2), a router, or the like.

[0125] As shown in Figure 5, in a microburst scenario, a long tail effect occurs in the latency distribution of data packets, as shown in the left diagram of Figure 5. In other words, the maximum latency has no upper limit or the upper limit is very large. As a result, the end-to-end latency exceeds the transmission latency requirement of the service. To achieve low end-to-end latency, the latency of data packets needs to be limited within a certain range, as shown in the right diagram of Figure 5. In other words, the latency jitter between the gNB and the UPF needs to be limited within a certain time range.

[0126] It should be noted that in the embodiments of the present application, a data packet may also be referred to as a packet, a data packet, a data frame, a frame, or the like. In the following, a data packet is used as an example for explanation purposes only.

[0127] In a possible design, the embodiments of the present application may be applied to the network architectures shown in Figures 6A and 6B to implement low transmission latency between the gNB and the UPF. The network architecture in Figure 6A is applicable to a TSN scenario, and the network architecture in Figure 6B is applicable to a non-TSN scenario.

[0128] For example, as shown in FIG. 6A, two domains are involved in FIG. 6A. Domain 1 uses the architecture shown in FIG. 4A. The user plane includes TSN terminals, 5GS, another switching node, and a CUC network element. A CNC network element is a control plane network element in a TSN system, and a TSN AF exchanges information with the CNC network element. The dashed box in Domain 1 forms Domain 2, shown at the top with an arrow pointing in FIG. 6A. Domain 2 includes gNB and UPF network elements in 5GS, switches between the gNB and UPF network elements, SMF network elements, CNC-TN network elements, TSN AF network elements, and PCF network elements. In Domain 2, the user plane includes gNB and UPF network elements in 5GS and switches between the gNB and UPF network elements, and the control plane includes SMF network elements, CNC-TN network elements, TSN AF network elements, and PCF network elements.

[0129] In Domain 2, a translator corresponding to the access network device is added on the gNB side. The translator corresponding to the access network device may be denoted as an AN-TT (shown in FIG. 6A). The AN-TT is configured to implement deterministic transmission between the gNB and the UPF network element, and is specifically described with reference to the following flowchart. The AN-TT may be located inside or outside the gNB. When the AN-TT is located inside the gNB, the AN-TT may be understood as a functional module integrated inside the gNB. Alternatively, when the AN-TT is located outside the gNB, the AN-TT and the gNB may be understood as two devices deployed separately. In this case, the AN-TT may be deployed between the gNB and the UE, or the AN-TT may be deployed between the gNB and the UPF network element.

[0130] In addition, another translator corresponding to the UPF network element is added on the UPF network element side, and the translator is located inside the UPF network element. In other words, the functional modules of two translators are integrated inside the UPF. One translator is the above-mentioned NW-TT, and the other translator can be denoted as an N3 interface translator, i.e., N3-TT (shown in FIG. 6A). The newly added N3-TT is configured to implement deterministic transmission between the gNB and the UPF, as will be specifically described with reference to the following flowchart. Alternatively, the functionality of the existing NW-TT can be enhanced, so that the NW-TT has the functionality of the N3-TT. In this way, one translator functional module is reserved inside the UPF network element. In addition, if an intermediate user plane network element (intermediate UPF, I-UPF) is further included on the path between the gNB and the UPF network element, the newly added translator can be denoted as N9-TT. An example in which the newly added translator is N3-TT is used below for explanation purposes only.

[0131] In addition, the two newly added translators may alternatively have other names, which is not a limitation in this application.

[0132] Based on the network architecture layout in FIG. 6A, in both Domain 1 and Domain 2, the transmission of the first service flow by the user plane device can meet the deterministic latency requirement of the first service flow.

[0133] The network architecture shown in Figure 6B also includes two domains. Domain 1 uses the architecture shown in Figure 4B. The user plane includes end station devices, 5GS, and other switching nodes, such as switching nodes in the DN. The control plane includes 5GS control plane network elements and AF network elements. The dashed box in Domain 1 forms Domain 2, shown at the top with an arrow pointing in Figure 6B. Domain 2 includes gNB and UPF network elements in 5GS, switches between the gNB and UPF network elements, SMF network elements, CNC-TN network elements, TSCTSF network elements, and PCF network elements. In Domain 2, the user plane includes gNB and UPF network elements in 5GS and switches between the gNB and UPF network elements, and the control plane includes SMF network elements, CNC-TN network elements, TSCTSF network elements, and PCF network elements. Similarly, AN-TT and N3-TT are newly added in Domain 2. For details, see the description in Figure 6A. 6B, in both Domain 1 and Domain 2, the transmission of the first service flow by the user plane device can also satisfy the deterministic latency requirement of the first service flow.

[0134] In the network architecture shown in Figures 6A and 6B, the SMF in Domain 2 is configured to implement the following first device functions: Therefore, in the network architecture shown in Figures 6A and 6B, the SMF is connected to the CNC-TN, and information can be exchanged through the interface between the SMF and the CNC-TN.

[0135] In a possible design, the embodiments of the present application may be applied to Domain 2 shown in Figures 7A and 7B to implement low transmission latency between the gNB and the UPF. The network architecture in Figure 7A is applicable to a TSN scenario, and the network architecture in Figure 7B is applicable to a non-TSN scenario.

[0136] For example, as shown in Figure 7A, for Domain 1 and Domain 2, please refer to the related description in Figure 6A. The difference from Figure 6A is that in Figure 7A, the TSN AF network element in Domain 2 can be configured to implement the function of the first device in Domain 2. Therefore, in the network architecture shown in Figure 7A, the TSN AF is connected to the CNC-TN, and information can be exchanged through the interface between the TSN AF and the CNC-TN.

[0137] For example, as shown in Figure 7B, for Domain 1 and Domain 2, please refer to the related description in Figure 6B. The difference from Figure 6B is that in Figure 7B, the TSCTSF network element can be configured to implement the function of the first device in Domain 2. Therefore, in the network architecture shown in Figure 7B, the TSCTSF is connected to the CNC-TN, and information can be exchanged through the interface between the TSCTSF and the CNC-TN.

[0138] 6A, 6B, 7A, and 7B, it should be noted that the user plane forwarding behavior of Domain 1 may be independent from the user plane forwarding behavior of Domain 2. Specifically, when the control plane of Domain 1 controls the forwarding behavior of 5GS, 5GS is considered as a whole, and transmission status inside 5GS, specifically, transmission between the UE and the gNB and between the gNB and the UPF network element, is not considered. When the control plane of Domain 2 controls the forwarding behavior of switching nodes in Domain 2, when the first service flow is an uplink service flow, the gNB and the UPF network element are considered as the sender and receiver of the first service flow, respectively, or the AN-TT and the N3-TT are considered as the sender and receiver of the first service flow, respectively. When the first service flow is a downlink service flow, the UPF network element and the gNB are considered as the sender and receiver of the first service flow, respectively, or the N3-TT and the AN-TT are considered as the sender and receiver of the first service flow, respectively. The time at which the sender transmits the data packet is limited by the time at which the 5GS node in Domain 1 receives the data packet from the upstream switching node, but the specific transmission and forwarding behavior may not be influenced or controlled by Domain 1.

[0139] The present application provides a communication method for implementing low transmission latency between a gNB and a UPF and improving overall network performance, in which deterministic transmission is supported between the gNB and the UPF, so that data packets can arrive at the gNB or the UPF (or NW-TT) within a predetermined time window; in other words, the long tail effect shown in FIG. 5 is avoided.

[0140] The communication method involves a first device, a second device, and a third device. For example, the first device may be a session management network element, such as an SMF network element in FIG. 6A or 6B; or the first network element may be a TSN application function network element, such as a TSN AF network element in FIG. 7A; or the first device may be a time-sensitive communication and time synchronization function network element, such as a TSCTSF network element in FIG. 7B. In the uplink case, the second device is an access network device or translator (e.g., an AN-TT) corresponding to the access network device, and the third device is a user plane network element. Alternatively, in the downlink case, the second device is a user plane network element (e.g., a UPF with N3-TT functionality), and the third device is an access network device.

[0141] Optionally, the method may further involve a fourth device. For example, the fourth device may be a CNC transport network (TN) in FIG. 6A, 6B, 7A, or 7B. The CNC-TN may be a new network element having the function of a CNC network element, or the CNC-TN may be a functional module in the first device. This is not limited in the present application. For details, please refer to the following related description of the fourth device.

[0142] It should be noted that in a scenario where the first service flow is an uplink service flow (corresponding to scenario 1 below), the packet delay budget (PDB3) for transmitting the first service flow between the terminal device and the user plane network element indicates an upper limit on the latency from the time the terminal device receives a data packet of the first service flow to the time the user plane network element or NW-TT completes processing of the data packet and sends the data packet to the next hop node.

[0143] When the second device is an access network device and the third device is a user plane network element, a translator (i.e., AN-TT) corresponding to the access network device is used as a functional module inside the access network device. The packet delay budget (PDB1) for transmitting a first service flow between a terminal device and an access network device indicates an upper limit of the latency from the time when the terminal device receives a data packet of the first service flow to the time when the data packet of the first service flow arrives at the PDCP layer or SDAP layer of the access network device. The packet delay budget (PDB2) for transmitting a first service flow between an access network device and a user plane network element indicates an upper limit of the latency from the time when the data packet of the first service flow is sent from the PDCP layer or SDAP layer of the access network device to the time when the user plane network element or NW-TT completes processing of the data packet and sends it to the next hop node. PDB3 is equal to the sum of PDB1 and PDB2.

[0144] In this case, the packet delay budget for transmitting the first service flow between the second device and the third device corresponds to PDB2.

[0145] When the second device is a translator (i.e., AN-TT) corresponding to an access network device and the third device is a user plane network element, the AN-TT is a device independently deployed outside the access network device. A packet delay budget (PDB1′) for transmitting a first service flow between a terminal device and a translator (i.e., AN-TT) corresponding to the access network device indicates an upper limit of the latency from the time the terminal device receives a data packet of the first service flow to the time the data packet of the first service flow arrives at the AN-TT. A packet delay budget (PDB2′) for transmitting a first service flow between a translator corresponding to the access network device and a user plane network element indicates an upper limit of the latency from the time the AN-TT receives a data packet of the first service flow to the time the user plane network element or NW-TT completes processing of the data packet and sends the data packet to a next-hop node. PDB3 is equal to the sum of PDB1′ and PDB2′.

[0146] In this case, the packet delay budget for transmitting the first service flow between the second device and the third device corresponds to PDB2'.

[0147] For example, in a scenario where the first service flow is a downlink service flow (corresponding to scenario 2 below), the packet delay budget (PDB6) for transmitting the first service flow between a user plane network element and a terminal device indicates an upper limit on the latency from the time a packet of the first service flow is received from a previous hop switching node by a user plane network element or NW-TT to the time the packet arrives at the terminal device (e.g., the application layer of the terminal device).

[0148] When the second device is a user plane network element and the third device is an access network device, a translator (i.e., an AN-TT) corresponding to the access network device is used as a functional module inside the access network device. The packet delay budget (PDB4) for transmitting a first service flow between the user plane network element and the access network device indicates an upper limit of the latency from the time when a packet of the first service flow is received from a previous hop switching node by the user plane network element or NW-TT to the time when a general packet radio service (GPRS) tunnel protocol for the user plane (GTP-U) for the user plane layer of the access network device completes processing of the packet. The packet delay budget (PDB5) for transmitting a first service flow between the access network device and the terminal device indicates an upper limit of the latency from the time when a packet of the first service flow is sent from the PDCP layer or SDAP layer of the access network device to the time when the packet of the first service flow arrives at the terminal device (e.g., the application layer of the terminal device). PDB6 is equal to the sum of PDB4 and PDB5.

[0149] In this case, the packet delay budget for transmitting the first service flow between the second device and the third device corresponds to PDB4.

[0150] When the second device is a user plane network element and the third device is a translator (i.e., an AN-TT) corresponding to the access network device, the AN-TT is a device independently deployed outside the access network device. The packet delay budget (PDB4') for transmitting the first service flow between the user plane network element and the translator (i.e., an AN-TT) corresponding to the access network device indicates an upper limit of the latency from the time the user plane network element or NW-TT receives a packet of the first service flow to the time the AN-TT completes processing of the packet. The packet delay budget (PDB5') for transmitting the first service flow between the translator (i.e., an AN-TT) corresponding to the access network device and the terminal device indicates an upper limit of the latency from the time the packet of the first service flow is sent from the AN-TT to the time the packet of the first service flow arrives at the terminal device (e.g., the application layer of the terminal device). PDB6 is equal to the sum of PDB4' and PDB5'.

[0151] In this case, the packet delay budget for transmitting the first service flow between the second device and the third device corresponds to PDB4'.

[0152] The following describes a communication method with reference to Fig. 8. Fig. 8 is a signaling interaction diagram of a communication method according to an embodiment of the present invention. As shown in Fig. 8, the method includes the following steps:

[0153] Step 800: A first device determines information about a service flow arrival time, where the service flow arrival time is the time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element.

[0154] The information about the service flow arrival time may be the service flow arrival time or may be an offset of the service flow arrival time relative to a reference time.

[0155] The first service flow may be a TSN service flow, abbreviated as TSN flow. For example, the first service flow may be a TSN flow transmitted from the talker to the listener in FIG. 9. Alternatively, the first service flow may be a QoS flow obtained through aggregation, specifically a QoS flow that aggregates multiple TSN flows with the same or similar characteristics. The forwarding path of the first service flow may be determined by a CNC network element in the TSN system. In an example, a switching node in the forwarding path of the first service flow includes a mobile communication system, for example, a 4G system, a 5G system, or a 6G system. In other words, the entire mobile communication system is used as a switching node, for example, switching node 2 shown in FIG. 9.

[0156] It may be understood that the first device may determine at least one of the service flow arrival time or the offset of the service flow arrival time relative to a reference time. In a possible implementation, the first device may first determine the offset of the service flow arrival time relative to a reference time, and then determine the service flow arrival time based on the offset of the service flow arrival time relative to the reference time. Alternatively, after determining the offset of the service flow arrival time relative to the reference time, the first device does not further determine the service flow arrival time. In another possible implementation, the first device may first determine the service flow arrival time, and then determine the offset of the service flow arrival time relative to the reference time based on the service flow arrival time. Alternatively, after determining the service flow arrival time, the first device does not further determine the offset of the service flow arrival time relative to the reference time.

[0157] A specific process by which the first device determines information about the service flow arrival time is described below with reference to two scenarios by using examples.

[0158] Scenario 1: When the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device. In other words, the first service flow is an uplink service flow sent by the access network device to a user plane network element.

[0159] For example, the second device being an access network device or a translator corresponding to the access network device can be understood as follows: if the translator corresponding to the access network device and the access network device are deployed separately, the second device can be the translator corresponding to the access network device. For example, the service flow arrival time can be the time at which the first service flow arrives at the translator corresponding to the access network device (e.g., the above-mentioned AN-TT). If the translator corresponding to the access network device is used as a functional module inside the access network device, the second device can be an access network device including a translator function, in other words, the second device can be the access network device. Correspondingly, the service flow arrival time can be the time at which the first service flow arrives at the access network device. For example, the service flow arrival time is the time at which the first service flow arrives at the packet data convergence protocol (PDCP) layer or the Service Data Adaptation Protocol (SDAP) layer of the access network device.

[0160] In this case, a forwarding path of the first service flow in the mobile communication system includes at least a terminal device, an access network device, and a user plane network element, and optionally, at least one switch or router may be further included on the forwarding path between the access network device and the user plane network element.

[0161] For example, as shown in FIG. 9, a 5G system is used as switching node 2, and the first service flow is an uplink service flow. The entire forwarding path of the first service flow is: talker, switching node 1, switching node 2, switching node 3, and listener. The forwarding path of the first service flow in the 5G system (i.e., switching node 2) is: UE, gNB, and UPF network element. In FIG. 9, DS-TT and NW-TT are not identified. Referring to FIG. 2, the forwarding path of the first service flow in the 5G system may specifically be: DS-TT, UE, gNB, and UPF network element (or NW-TT). The forwarding path of the first service flow from the gNB to the UPF network element is: gNB (AN-TT, where AN-TT is located inside the gNB as a functional module of the gNB), transmission node 1, transmission node 2, and UPF network element (N3-TT, where N3-TT is located inside the UPF as a functional module of the UPF). Alternatively, the forwarding path of the first service flow from the gNB to the UPF network element is: gNB, AN-TT (where AN-TT and gNB are deployed separately), transmission node 1, transmission node 2, and UPF network element (N3-TT). In Figure 9, an example in which the AN-TT is located inside the gNB as a functional module of the gNB is used for explanation purposes only.

[0162] In implementation, the first device may obtain information about the time at which the first service flow arrives at a translator (e.g., DS-TT) on the terminal device side, the residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0163] For example, the information about the time at which the first service flow arrives at the translator (e.g., DS-TT) on the terminal device side specifically refers to information about the time at which data packets of the first service flow arrive at the translator on the terminal device side in a specific cycle, and can be determined based on the burst arrival time at which the first service flow arrives at the DS-TT and the cycle of the first service flow. The information about the time at which the first service flow arrives at the translator on the terminal device side can be the time at which the first service flow arrives at the translator on the terminal device side, or the offset of the time at which the first service flow arrives at the translator on the terminal device side relative to a reference time. The reference time refers to the start time of the time domain (e.g., January 1, 1970, 00:00:00).

[0164] The residence time of the first service flow in the terminal device and the translator on the terminal device side may be the residence time of the first service flow between the DS-TT and the UE in FIG. 2, that is, the UE-DS-TT Residence Time.

[0165] Furthermore, the first device may determine the service flow arrival time or an offset of the service flow arrival time relative to a reference time based on information about the time the first service flow arrives at the translator at the terminal device, the residence time of the first service flow at the terminal device and the translator at the terminal device, and a packet delay budget for transmitting the first service flow between the terminal device and the second device. Examples are provided below. T1 (uplink) = Burst Arrival Time 1 + UE-DS-TT Residence Time + PDB, Equation (1) T1-Offset (Uplink) = Burst Arrival Time 1* + UE-DS-TT Residence Time + PDB, Equation (2)

[0166] T1 (uplink) indicates the service flow arrival time in an uplink scenario, and T1-offset (uplink) indicates the offset of the service flow arrival time relative to a reference time in an uplink scenario. Burst Arrival Time 1 indicates the time at which the first service flow arrives at the DS-TT, and Burst Arrival Time 1* indicates the offset of the time at which the first service flow arrives at the DS-TT relative to the reference time. UE-DS-TT Residence Time indicates the residence time of the first service flow at the terminal device and the DS-TT. PDB indicates the packet delay budget for transmitting the first service flow between the terminal device and the second device, and may be the PDB1 or PDB1'. For example, the residence times of the service flows at the terminal device and the translator on the terminal device side may be the same or different.

[0167] It can be understood that when the first device is implemented by using different devices, the manner in which the first device acquires the three parameters is also different. The following uses Scheme 1 and Scheme 2 as examples to describe the specific process in which the first device acquires the three parameters.

[0168] Method 1: When the first device is a session management network element (e.g., an SMF network element in FIG. 6A or FIG. 6B), the first device may obtain the three parameters in the following ways, including but not limited to:

[0169] Regarding the information about the time at which the first service flow arrives at the translator on the terminal device side, the session management network element may determine the information about the time at which the first service flow arrives at the translator on the terminal device side based on information obtained from the policy control network element.

[0170] For example, the information about the time at which the first service flow arrives at the translator on the terminal device side specifically refers to the information about the time at which the data packets of the first service flow in a particular cycle arrive at the translator on the terminal device side.

[0171] For example, the policy control network element sends parameters such as information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow to the session management network element.

[0172] The information about the burst arrival time of the first service flow may be the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, the time length from a reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, or an offset from the reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system. The reference time is the start time in the time domain (e.g., January 1, 1970, 00:00:00). When the direction of the first service flow indicates that the first service flow is an uplink service flow, the ingress port of the 5G system here refers to the port of a translator (e.g., DS-TT) on the terminal device side. In this case, the information about the burst arrival time of the first service flow is information about the time at which the first data packet in a data burst of the first service flow arrives at the translator on the terminal device side.

[0173] In addition, the cycle of the first service flow may also be described as the time length of the interval between two adjacent points of the burst start time of the first service flow.

[0174] In a possible implementation, the policy control network element may obtain parameters such as information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow from a TSN application function network element (e.g., the TSN AF network element shown in FIG. 6A) or a time-sensitive communication and time synchronization function network element (e.g., the TSCTSF network element shown in FIG. 6B).

[0175] For example, for the network architecture shown in FIG. 6A, the TSN AF network element is used as the control plane of the 5GS switching node, and the TSN AF network element determines parameters based on information obtained from the CNC network element and sends the parameters to the policy control network element.

[0176] In another example, for the network architecture shown in FIG. 6B, a TSCTSF network element is used as the control plane of the 5GS switching node, and the TSCTSF network element determines parameters based on information obtained from the application function network element and sends the parameters to the policy control network element.

[0177] For example, the policy control network element sends a policy control and charging (PCC) rule to the session management network element. The PCC rule includes information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow. For example, the PCC rule includes a TSC assistance container. The TSC assistance container holds information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow.

[0178] In addition, the PCC rule may further include service requirement description parameters, which are obtained by the policy control network element from the TSN application function network element or the time-sensitive communication and time synchronization function network element. The service requirement description parameters may include at least one of a maximum burst size, a priority of the first service flow, a latency requirement of the first service flow, a maximum flow bit rate, and the like.

[0179] After receiving multiple parameters, specifically information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow from the policy control network element, the session management network element can determine, based on these parameters, information about the time at which data packets of the first service flow in a particular cycle arrive at the translator on the terminal device side, i.e., information about the time at which the first service flow arrives at the translator on the terminal device side.

[0180] In other words, Burst Arrival Time 1 in equation (1) or Burst Arrival Time 1* in equation (2) can be determined in the above manner.

[0181] Regarding the residence time of the first service flow in the terminal device and the translator on the terminal device side, the session management network element may obtain the residence time of the first service flow in the terminal device and the translator on the terminal device side from the terminal device.

[0182] For example, in a protocol data unit (PDU) session establishment process, a session management network element may receive a PDU session establishment request message from a terminal device, where the PDU session establishment request message carries a residence time of a first service flow in the terminal device and a translator on the terminal device side. Optionally, the PDU session establishment request message may further carry a media access control address (MAC) address of a DS-TT port.

[0183] In other words, the UE-DS-TT Residence Time in equation (1) or equation (2) can be determined in the above manner.

[0184] Regarding the packet delay budget for transmitting the first service flow between the terminal device and the second device, the session management network element may determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0185] For example, the session management network element may determine PDB1 or PDB1' based on a 5G QoS Identifier (5QI) in the PCC rule. For example, the session management network element may configure PDB2 or PDB2' and further determine PDB3 based on the 5QI. Furthermore, the difference between PDB3 and PDB2 may be calculated to obtain PDB1. Alternatively, the difference between PDB3 and PDB2' may be calculated to obtain PDB1'. For details, please refer to the related content above.

[0186] In other words, PDB1 and PDB1' can be determined in the above manner. The example where the PDB is PDB1 is used below for illustration purposes only.

[0187] Method 2: When the first device is a TSN application function network element (e.g., the TSN AF network element shown in FIG. 7A) or a time-sensitive communication and time synchronization function network element (e.g., the TSCTSF network element shown in FIG. 7B), the first device may obtain the three parameters in the following manner, but not limited to the following manner.

[0188] Regarding the information about the time at which the first service flow arrives at the translator at the terminal device side, the first device may determine the information about the time at which the first service flow arrives at the translator at the terminal device side.

[0189] For example, the information about the time at which the first service flow arrives at the translator on the terminal device side specifically refers to the information about the time at which the data packets of the first service flow in a particular cycle arrive at the translator on the terminal device side.

[0190] For example, when the first device is a TSN application function network element, the TSN application function network element is further used as a control plane of the 5GS switching node and determines, based on information obtained from the CNC network element, parameters such as information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow. In another example, when the first device is a time-sensitive communication and time synchronization function network element, the time-sensitive communication and time synchronization function network element is further used as a control plane of the 5GS switching node and determines, based on information obtained from the application function network element, parameters such as information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow.

[0191] The information about the burst arrival time of the first service flow may be the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, the time length from a reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, or an offset from the reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system. The reference time is the start time in the time domain (e.g., January 1, 1970, 00:00:00). When the direction of the first service flow indicates that the first service flow is an uplink service flow, the ingress port of the 5G system here refers to the port of a translator (e.g., DS-TT) on the terminal device side. In this case, the information about the burst arrival time of the first service flow is information about the time at which the first data packet in a data burst of the first service flow arrives at the translator on the terminal device side.

[0192] Regarding the residence time of the first service flow in the terminal device and the translator on the terminal device side and the packet delay budget for transmitting the first service flow between the terminal device and the second device, by referring to Scheme 1, it can be seen that the session management network element can obtain the residence time of the first service flow in the terminal device and the translator on the terminal device side from the terminal device, and the session management network element can further determine the packet delay budget (i.e., PDB1 or PDB1′) for transmitting the first service flow between the terminal device and the second device. For example, the first device can receive the above information directly from the session management network element, or can receive the above information from the session management network element through another network element (e.g., a policy control network element). Alternatively, the session management network element can store the above information in a data repository network element (e.g., a UDR network element) through a data management network element (e.g., a UDM network element), and the first device can obtain the above information from the data repository network element.

[0193] Scenario 2: When the first service flow is a downlink service flow, the second device is a user plane network element. In other words, the first service flow is a downlink service flow transmitted by a user plane network element to an access network device.

[0194] In this case, the forwarding path of the first service flow in the mobile communication system is a user plane network element, an access network device, and a terminal device. Optionally, at least one switch or router can be further included between the user plane network element and the access network device.

[0195] For example, as shown in FIG. 10, a 5G system is used as switching node 2, and the first service flow is a downlink service flow. The forwarding path of the first service flow is the talker, switching node 1, switching node 2, switching node 3, and listener. The forwarding path of the first service flow in the 5G system (i.e., switching node 2) is the UPF network element, the gNB, and the UE. In FIG. 10, DS-TT and NW-TT are not identified. Referring to FIG. 2, the forwarding path of the first service flow in the 5G system may specifically be the UPF (or NW-TT), the gNB, the UE, and the DS-TT. The forwarding path of the first service flow from the UPF network element to the gNB is: the UPF network element (N3-TT, where N3-TT is located inside the UPF as a functional module of the UPF), transmission node 1, transmission node 2, and the gNB (AN-TT, where AN-TT is located inside the gNB as a functional module of the gNB). Alternatively, the forwarding path of the first service flow from the UPF network element to the gNB is: UPF network element (N3-TT), transmission node 1, transmission node 2, AN-TT (AN-TT is located outside the gNB), and the gNB. In Figure 10, an example in which the AN-TT is located inside the gNB as a functional module of the gNB is used for explanation purposes only.

[0196] In implementation, the information about the service flow arrival time can be understood as information about the time when the first service flow arrives at the user plane network element, or information about the time when the first service flow arrives at the NW-TT. The NW-TT is located inside the user plane network element, and the time when the first service flow arrives at the NW-TT is equal to the time when the first service flow arrives at the user plane network element. The information about the service flow arrival time can include the time when the first service flow arrives at the user plane network element, or an offset of the time when the first service flow arrives at the user plane network element relative to a reference time. Examples are provided below. T1 (downlink) = Burst Arrival Time 2, Equation (3) T1-Offset (Downlink) = Burst Arrival Time 2*, Equation (4)

[0197] T1(downlink) indicates the service flow arrival time in the downlink scenario, T1-offset(downlink) indicates the offset of the service flow arrival time relative to the reference time in the downlink scenario, Burst Arrival Time 2 indicates the time when the first service flow arrives at the NW-TT, and Burst Arrival Time 2* indicates the offset of the time when the first service flow arrives at the NW-TT relative to the reference time.

[0198] Similarly, when the first device is implemented using different devices, the manner in which the first device obtains information about the service flow arrival time is also different. In the following, Scheme 3 and Scheme 4 are used as examples to describe the specific process in which the first device obtains information about the service flow arrival time.

[0199] Manner 3: When the first device is a session management network element (eg, the SMF network element in FIG. 6A or 6B), the first device may receive information about the service flow arrival time from the policy control network element.

[0200] Method 3 is similar to Method 1, in which the session management network element may obtain information about the time at which the first service flow arrives at the translator on the terminal device side from the policy control network element. The difference is that the information about the burst arrival time of the first service flow may be the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, the time length from a reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, or the offset of the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time. Therefore, when the direction of the first service flow indicates that the first service flow is a downlink service flow, the ingress port of the 5G system here refers to a port of the NW-TT. In this case, the information about the burst arrival time of the first service flow is information about the time at which the first data packet in a data burst of the first service flow arrives at the NW-TT.

[0201] Method 4: When the first device is a TSN application function network element or a time-sensitive communication and time synchronization function network element, the first device may determine information about the service flow arrival time.

[0202] Scheme 4 is similar to Scheme 2 in that the first device can determine information about the time at which the first service flow arrives at the translator on the terminal device side. The difference is that the information about the burst arrival time of the first service flow can be the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, the time length from a reference time to the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system, or the offset of the time at which the first data packet in a data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time. Therefore, when the direction of the first service flow indicates that the first service flow is a downlink service flow, the ingress port of the 5G system here refers to a port of the NW-TT. In this case, the information about the burst arrival time of the first service flow is information about the time at which the first data packet in a data burst of the first service flow arrives at the NW-TT.

[0203] Step 810: The first device determines information about a service flow transmission time based on the information about the service flow arrival time.

[0204] In a first implementation, the first device determines an earliest transmit time and a latest transmit time based on information about the service flow arrival times. The earliest transmit time may be understood as the earliest time at which the second device transmits the first service flow, and the latest transmit time may be understood as the latest time at which the second device transmits the first service flow. The service flow transmit time is not earlier than the earliest transmit time, and the service flow transmit time is not later than the latest transmit time. The first device may determine a service flow transmit time that is not earlier than the earliest transmit time or not later than the latest transmit time. The service flow transmit time may be understood as a time recommended for the second device to transmit the service flow.

[0205] The earliest transmission time is the sum of the service flow arrival time and the processing time of the first service flow at the second device.

[0206] For example, in a scenario where jitter is not considered: T2 = T1 + processing time of the second device, Equation (5-1)

[0207] T2 denotes the earliest transmission time. T1 denotes the service flow arrival time, which can be T1 (uplink) obtained according to equation (1) or T1 (downlink) obtained according to equation (3).

[0208] For example, when the first service flow is an uplink service flow: T2 (uplink) = T1 (uplink) + T AN , formula (5-2)

[0209] T AN is the processing time of the first service flow in the access network device or AN-TT.

[0210] In addition, the first device may further skip the process of calculating T1 (uplink) and directly calculate T2 (uplink). T2 (uplink) = Burst Arrival Time 1 + UE-DS-TT Residence Time + PDB + T AN , formula (5-3)

[0211] For example, when the first service flow is a downlink service flow: T2 (downlink) = T1 (downlink) + T UPF , formula (5-4)

[0212] T UPF is the processing time of the first service flow in the user plane network element.

[0213] In addition, the first device may further skip the process of calculating T1 (downlink) and directly calculate T2 (downlink). T2 (uplink) = Burst Arrival Time 2 + T UPF , formula (5-5)

[0214] In a scenario where jitter is taken into account, the following occurs: T2 = T1 + Processing time of the second device + Jitter, Equation (6-1)

[0215] For example, when the first service flow is an uplink service flow: T2 (uplink) = T1 (uplink) + T AN +Jitter, formula (6-2)

[0216] For example, when the first service flow is a downlink service flow: T2 (downlink) = T1 (downlink) + T UPF +Jitter, formula (6-3)

[0217] In addition, in a scenario where jitter is taken into consideration, the first device may further skip the process of calculating T1 and directly calculate T2, the details of which will not be described again here.

[0218] Jitter indicates the jitter latency associated with the first service flow, which is the transmission latency caused by the presence of a service flow with the same priority as the first service flow, and may be determined based on the maximum frame size of the service flow with the same priority as the first service flow.

[0219] For example, if there is no flow with the same priority as a given flow, the jitter value of that flow is 0. If there is a flow with the same priority as a given flow, the jitter value of that flow is affected by the [MaxFrameSize] of all other flows with the same priority. [MaxFrameSize] refers to the time required to transmit the largest data packet of a service flow or the longest time to transmit a frame of a service flow.

[0220] For example, flow J and flow K have the same priority. Based on the [MaxFrameSize] of flow J, the longest time to transmit a frame of flow J is determined to be 120 μs, and based on the [MaxFrameSize] of flow K, the longest time to transmit a frame of flow K is determined to be 80 μs. The jitter of flow K depends on the longest time to transmit a frame of flow J. For example, the jitter of flow K is determined based on half the longest time to transmit a frame of flow J, i.e., 60 μs. Since flow J and flow K have the same priority, it can be understood that flow J and flow K enter the same transmission queue. When flow J and flow K simultaneously wait to be transmitted in the same transmission queue, if flow J transmits first, flow K needs to wait for a maximum time length, where the maximum time length is the longest time to transmit a frame of flow J; and if flow K transmits first, flow K needs to wait for a minimum time length, where the minimum time length is 0. Therefore, here, the jitter of flow K is defined as half the longest time (120 μs) to transmit a frame of flow J, based on probability, i.e., 60 μs. Similarly, the jitter of flow J is 40 μs.

[0221] In another example, flows J, K, and G have the same priority. Based on the [MaxFrameSize] of flow J, the longest time to transmit a frame of flow J is determined to be 120 μs, based on the [MaxFrameSize] of flow K, the longest time to transmit a frame of flow K is determined to be 80 μs, and based on the [MaxFrameSize] of flow G, the longest time to transmit a frame of flow G is determined to be 100 μs. Similarly, the jitter of flow J depends on the longest time to transmit a frame of flow K and the longest time to transmit a frame of flow G. For example, the jitter of flow J is determined based on the sum of half the longest time to transmit a frame of flow K and half the longest time to transmit a frame of flow K, i.e., the jitter of flow J is 90 μs. Similarly, the jitter of flow K is 110 μs, and the jitter of flow G is 100 μs.

[0222] Additionally, the processing time of the first service flow at the second device in the above equation can be understood as the time required for the second device to decapsulate the data packets of the first service flow, process the data packets of the first service flow, encapsulate the data packets of the first service flow, and transmit the encapsulated data packets to an egress port of the second device after the data packets of the first service flow arrive at the second device. The egress port is the egress port used by the second device to transmit the first service flow. In other words, the processing time of the first service flow at the second device can be understood as the length of time from when the second device receives the data packets of the first service flow to when the data packets arrive at the egress port of the second device and are ready for transmission. For example, it is assumed that the second device receives the data packets of the first service flow from an upstream node at time t1, and after being processed by the second device, the data packets arrive at the egress port of the second device at time t2 and wait to be transmitted to the next device. In this case, t2 - t1 is the processing time of the first service flow at the second device. The instant t1 corresponds to the service flow arrival time, and the instant t2 corresponds to the earliest transmission time when jitter is not considered.

[0223] In this implementation, when the second device is a user plane network element, t1 is the time when a data packet of the first service flow arrives at an ingress port of the NW-TT corresponding to the user plane network element, and t2 is the time when a data packet of the first service flow arrives at an egress port of the user plane network element or the NW-TT. For example, when the forwarding path from the second device to the access network device does not include an I-UPF, t2 is the time when a data packet of the first service flow arrives at an egress port of the N3-TT. The egress port here is the egress port used for transmission to the access network device or the AN-TT. For example, when the forwarding path from the second device to the access network device includes an I-UPF, t2 is the time when a data packet of the first service flow arrives at an egress port of the N9-TT. The egress port here is the egress port used for transmission to the I-UPF.

[0224] In another implementation, when the second device is an access network device, t1 is the time at which a data packet of the first service flow arrives at the access network device after being transmitted over the air interface, for example, it may be the time at which a data packet of the first service flow arrives at the PDCP layer or SDAP layer of the access network device, and t2 is the time at which a data packet of the first service flow arrives at the egress port after being processed by the access network device.

[0225] In yet another implementation, when the second device is a translator corresponding to an access network device, t1 is the time at which a data packet of the first service flow arrives at an AN-TT outside the access network device after being transmitted over the air interface, and t2 is the time at which a data packet of the first service flow arrives at an egress port after being processed by the AN-TT.

[0226] For example, the first device may obtain processing time information of the second device from the second device, and determine the processing time of the first service flow in the second device based on the processing time information of the second device.

[0227] The processing time information of the second device may include a 5QI and a processing time of the service flow corresponding to the 5QI at the second device. Further, the first device may determine a processing time of the first service flow at the second device based on the 5QI of the first service flow and the processing time information of the second device.

[0228] Alternatively, the processing time information of the second device may include a data packet size range and a processing time of a service flow that satisfies the data packet size range at the second device. Further, the first device may determine a data packet size range that includes data packets of the first service flow based on the size of the data packets of the first service flow, and may determine a processing time of the first service flow at the second device based on the processing time information of the second device.

[0229] Alternatively, the processing time information of the second device includes the processing time of the service flow in the second device, in other words, the processing time of all the service flows in the second device is the same time length. Furthermore, the second device determines the processing time of the service flow in the second device in the processing time information of the second device as the processing time of the first service flow in the second device.

[0230] Referring to scenario 1 and scenario 2, the following uses an example to describe an implementation in which a first device obtains the processing time information of a second device from the second device.

[0231] According to Scenario 1, when a translator corresponding to an access network device is used as a function module inside the access network device, the first device can obtain the processing time information of the second device from the access network device. In this case, the processing time information of the second device is also referred to as the processing time information of the access network device.

[0232] When the translator corresponding to the access network device is a device independently deployed outside the access network device, the translator corresponding to the access network device may send the processing time information of the second device to the access network device, and the first device may obtain the processing time information of the second device from the access network device; or the processing time information of the second device is configured on the access network device; or the first device may obtain the processing time information of the second device from the translator corresponding to the access network device. In this case, the processing time information of the second device is also referred to as the processing time information of the translator corresponding to the access network device.

[0233] For example, when the first device is a session management network element, the access network device may send a setup request (NG Setup Request) message to the access and mobility management function network element when establishing a connection with the access and mobility management function network element, where the NG Setup Request message carries processing time information of the second device. Alternatively, the access network device may send a configuration update (RAN Configuration Update) message to the access and mobility management function network element, where the RAN Configuration Update message carries processing time information of the second device. Alternatively, in the registration process of a terminal device (e.g., a first terminal device), the access network device may send the processing time information of the second device to the access and mobility management function network element. Furthermore, the access and mobility management function network element sends the processing time information of the second device to the session management network element in the PDU session establishment process. Alternatively, the processing time information of the second device may be configured on the session management network element. Alternatively, in the session establishment process of the terminal device (e.g., the session establishment request carries a specific single network slice selection assistance information (S-NSSAI) and data network name (DNN)), the access network device may send the processing time information of the second device to the session management network element through the access and mobility management network element.

[0234] Corresponding to scenario 2, the first device may obtain the processing time information of the user plane network element from the user plane network element. For example, when the first device is a session management network element, the session management network element sends a request message to the user plane network element, where the request message is used to request the processing time information of the user plane network element. For example, the request message may be an N4 session establishment message or an N4 session modification request message. The user plane network element may send a response message for the request message to the first device, where the response message for the request message holds the processing time information of the user plane network element. For example, when the request message is an N4 session establishment message, the response message for the request message is a response message for the N4 session establishment message. When the request message is an N4 session modification request message, the response message for the request message is a response message for the N4 session modification message. Alternatively, the user plane network element may directly report the processing time information of the user plane network element to the session management network element, and the session management network element does not need to request the processing time of the first service flow at the user plane network element from the user plane network element. Alternatively, the processing time information of the user plane network element may be configured on the session management network element.

[0235] Additionally, when the first device is a device other than a session management network element, the session management network element may transmit the processing time of the first service flow at the second device and the processing time information of the second device to the first device, and the first device may receive the information directly from the session management network element or may receive the information from the session management network element through another network element (e.g., a policy control network element). Alternatively, the session management network element may store the information in a data repository network element (e.g., a UDR network element) through a data management network element (e.g., a UDM network element), and the first device may obtain the information from the data repository network element. Alternatively, the processing time information of the second device may be configured on the first device.

[0236] In the above manner, the earliest transmission time can be determined. In addition, the service flow transmission time is not later than the latest transmission time. The latest transmission time can be determined in the following manner A, B, or C, but is not limited to these.

[0237] Scheme A: Because the first service flow is a periodic service flow, the data packet of the first service flow currently arriving at the second device must be transmitted before the data packet of the first service flow in the next cycle arrives at the second device. In other words, the second device must transmit the data packet of the first service flow within a time length corresponding to the cycle of the first service flow after the service flow arrival time. Therefore, the latest time at which the second device transmits the data packet of the first service flow (i.e., the latest transmission time) must be earlier than the sum of the service flow arrival time and the cycle of the first service flow. Furthermore, to implement that the data packet of the first service flow currently arriving at the second device has already been transmitted and is not currently being transmitted before the data packet of the first service flow in the next cycle arrives at the second device, based on the above description, the latest time at which the second device transmits the first service flow (i.e., the latest transmission time) may be equal to the difference between the sum of the service flow arrival time and the cycle of the first service flow and the time length corresponding to transmitting the maximum data packet of the first service flow.

[0238] For example, the latest transmission time is determined based on the service flow arrival time, the cycle of the first service flow, and the maximum frame size of the first service flow.

[0239] In a scenario where jitter is not considered: T3 A =T1+Interval-[MaxFrameSize], formula (7-1)

[0240] T3 Adenotes the latest transmission time determined in scheme A. T1 denotes the service flow arrival time, which may be T1 (uplink) obtained according to equation (1) or T1 (downlink) obtained according to equation (3). Interval denotes the cycle of the first service flow, and [MaxFrameSize] denotes the time length corresponding to the transmission of a data packet having a size of MaxFrameSize through the egress port of the second device, i.e., the time length corresponding to the transmission of the largest data packet of the first service flow.

[0241] For the cycle of the first service flow, please refer to the related contents in Schemes 1 to 4. MaxFrameSize may be determined based on information obtained from the service requirement description parameters, and MaxFrameSize is the difference between the maximum burst size in the service requirement description parameters and the size of the media framing field. The media framing field may include at least one of a preamble, an IEEE 802.3 header, a priority or virtual local area network identifier (VLAN Identifier, VID), a cyclic redundancy check (CRC), an interframe gap, and the like.

[0242] In addition, the first device further skips the process of calculating T1 (uplink) and calculates T3 A (uplink) can be calculated directly. T3 A (Uplink) = Burst Arrival Time 1 + UE-DS-TT Residence Time + PDB + Interval - [MaxFrameSize], Equation (7-2)

[0243] Similarly, the first device may further skip the process of calculating T1 (downlink) and calculate T3 A (downlink) can be calculated directly. T3 A(Downlink) = Burst Arrival Time 2 + Interval - [MaxFrameSize], Equation (7-3)

[0244] Optionally, in a scenario where jitter is taken into consideration, the following: T3 A =T1+Interval-[MaxFrameSize]-Jitter, formula (8)

[0245] In a scenario where jitter is taken into consideration, the second device transmits the data packets of the first service flow earlier than T1+Interval-[MaxFrameSize]-Jitter, so that when the data packets of the first service flow in the next cycle arrive at the second device, it can be understood that the data packets of the first service flow in the current cycle have already been transmitted by the second device and are not currently being transmitted. Therefore, the jitter is subtracted here.

[0246] Similarly, the first device may also skip the process of calculating T1, and the details will not be described again here.

[0247] Scheme B: After the first service flow arrives at the second device, the second device needs to process the first service flow, which is limited by the maximum buffer time length of the first service flow at the second device. Therefore, the latest time at which the second device transmits the first service flow (i.e., the latest transmission time) may be equal to the sum of the service flow arrival time, the processing time of the first service flow at the second device, and the maximum buffer time length of the first service flow at the second device.

[0248] For example, the latest transmission time may be determined based on the service flow arrival time, the processing time of the first service flow at the second device, and the maximum buffering time of the first service flow at the second device, which is the maximum time that the first service flow may be buffered at the second device.

[0249] In a scenario where jitter is not considered: T3 B =T1+T'+T * , formula (9-1)

[0250] T3 B denotes the latest transmission time determined in scheme B. T1 denotes the service flow arrival time, which may be T1 (uplink) obtained according to equation (1) or T1 (downlink) obtained according to equation (3). T' denotes the processing time of the first service flow in the second device. T * indicates the maximum buffer time length of the first service flow in the second device.

[0251] In addition, the first device further skips the process of calculating T1 (uplink) and calculates T3 B (uplink) can be calculated directly. T3 B (Uplink) = Burst Arrival Time 1 + UE-DS-TT Residence Time + PDB + T' + T * , formula (9-2)

[0252] The first device further skips the process of calculating T1 (downlink) and calculates T3 B (downlink) can be calculated directly. T3 B (Downlink) = Burst Arrival Time 2 + T' + T * , formula (9-3)

[0253] In a scenario where jitter is taken into account, the following occurs: T3 B =T1+T'+T * -Jitter, formula (10-1)

[0254] In a scenario where jitter is taken into account, the second device * It can be understood that the data packets of the first service flow need to be sent faster than -Jitter, so that the buffering time of the data packets of the first service flow in the second device does not exceed the maximum buffering time length.

[0255] Similarly, the first device may also skip the process of calculating T1, and the details will not be described again here.

[0256] Regarding the processing time T′ of the first service flow in the second device that needs to be used to calculate the latest transmission time in scheme B, please refer to the description of how to determine the processing time of the first service flow in the second device in determining the earliest transmission time, and the details will not be described again here.

[0257] In a possible implementation, the maximum buffer time length T of the first service flow in the second device that needs to be used to calculate the latest transmission time in scheme B. *The maximum buffer time length for the first service flow at the second device may be related to the buffer capability of the second device, or the maximum buffer time length for the first service flow at the second device may be related to a 5QI corresponding to the first service flow, or the maximum buffer time length for the first service flow at the second device may be related to a data packet size range. For example, the first device may obtain maximum buffer time length information for the second device and determine the maximum time length for which the first service flow can be buffered at the second device based on the maximum buffer time length information of the second device. For example, when the first device is a session management network element, the maximum buffer time length information includes at least one 5QI and the maximum time length for which the service flow corresponding to each 5QI can be buffered at the second device. The session management network element may further determine the maximum buffer time length for the first service flow at the second device by referring to the 5QI of the first service flow. Alternatively, the maximum buffer time length information may include a data packet size range and a maximum buffer time length for a service flow that satisfies the data packet size range at the second device. The session management network element may further determine the maximum buffer time length of the first service flow in the second device by referring to the size of the data packets of the first service flow. Alternatively, the maximum buffer time length information includes the maximum buffer time length of the service flow in the second device; in other words, the maximum buffer time lengths of all service flows in the second device are the same. The implementation in which the session management network element obtains the maximum buffer time length information of the second device may be the same as the implementation in which the first device obtains the processing time information of the second device from the second device. For details, please refer to the description in step 810. The details will not be described again here.

[0258] In another possible implementation, the first device determines a maximum buffer time length T for the first service flow at the second device based on the processing time information of the second device, the processing time information of the third device, a packet delay budget for transmitting the first service flow between the second device and the third device, and a maximum transmission latency of the first service flow between the second device and the third device. * = Packet delay budget for transmitting the first service flow between the second device and the third device - Processing time of the first service flow at the third device - Processing time of the first service flow at the second device - Maximum transmission latency of the first service flow between the second device and the third device.

[0259] For example, when the first device is a session management network element, the session management network element may determine a packet delay budget for transmitting the first service flow between the second device and the third device based on the 5QI corresponding to the first service flow, and may determine a processing time for the first service flow at the second device based on the processing time information of the second device. The session management network element may further determine a maximum transmission latency for the first service flow between the second device and the third device, and further calculate a maximum buffer time length for the first service flow at the second device based on the above parameters.

[0260] For example, for the packet delay budget for transmitting the first service flow between the second device and the third device, please refer to the related descriptions of PDB2 (or PDB2') and PDB4 (or PDB4') in Scenario 1 and Scenario 2. For example, the first service flow is an uplink service flow. If the latency requirement for transmitting the first service flow between the terminal device and the user plane network element is 2 ms, the session management network element may determine that the packet delay budget (PDB3) for transmission between the terminal device and the user plane network element is 2 ms, and that the packet delay budget (PDB2) for transmission between the second device and the third device is 1 ms.

[0261] For the processing time of the first service flow in the second device, please refer to the related description above.

[0262] The maximum transmission latency of the first service flow between the second device and the third device depends on the capabilities of each transmission node between the second device and the third device and indicates the latency required to transmit the first service flow between the second device and the third device. The maximum transmission latency of the first service flow between the second device and the third device is the length of time from when the second device (access network device or AN-TT) transmits a data packet of the first service flow to when the third device (user plane network element, N3-TT, or N9-TT) receives the data packet of the first service flow when the second device, the third device, and another transmission node between the second device and the third device forward the data packet of the first service flow based on gated scheduling parameters under the control of the CNC-TN.

[0263] The maximum transmission latency of the first service flow between the second device and the third device may be preconfigured on the session management network element. For example, the maximum transmission latency between different access network devices (or translators corresponding to the access network devices) and different user plane network elements may be configured on the session management network element. Alternatively, the maximum transmission latency may be configured based on different 5QIs. Specifically, for a specific access network device (or a translator corresponding to the access network device) and a specific user plane network element, the corresponding maximum transmission latency may be preconfigured separately for different 5QIs, or a uniform value of the maximum transmission latency may be configured; in other words, the 5QIs corresponding to different services may not be distinguished.

[0264] The processing time of a first service flow at a third device may be understood as the time required by the third device to decapsulate and process the data packets of the first service flow, encapsulate the first service flow, and transmit the encapsulated first service flow to an egress port of the third device after the data packets of the first service flow arrive at the third device. The egress port is the egress port used by the third device to transmit the first service flow to the next hop device. In other words, the processing time of a first service flow at a third device may be understood as the length of time from when the third device receives the data packets of the first service flow to when the data packets arrive at the egress port of the third device and are ready for transmission. For example, assume that the third device receives data packets of the first service flow from an upstream node at time t3, and the data packets arrive at the egress port of the third device at time t4 after being processed by the third device and waiting to be transmitted to the next hop device. In this case, t4 - t3 is the processing time of the first service flow at the third device.

[0265] In this implementation, when the third device is a user plane network element, t3 is the time when the data packet of the first service flow arrives at the ingress port of the N3-TT or N9-TT corresponding to the user plane network element, and t4 is the time when the data packet of the first service flow arrives at the egress port of the user plane network element or the NW-TT of the user plane network element. For example, when the determined forwarding path from the second device to the third device does not include an I-UPF, t3 is the time when the data packet of the first service flow arrives at the ingress port of the N3-TT. For example, when the determined forwarding path from the second device to the third device includes an I-UPF, t3 is the time when the data packet of the first service flow arrives at the ingress port of the N9-TT.

[0266] In another implementation, when the third device is an access network device, t3 is the time at which a data packet of the first service flow arrives at the access network device after being transmitted through the N3 link, for example, it may be the time at which a data packet of the first service flow arrives at the ingress port of the access network device, and t4 is the time at which a data packet of the first service flow arrives at the PDCP layer or SDAP layer after being processed by the access network device.

[0267] In yet another implementation, when the third device is a translator corresponding to the access network device, t3 is the time at which the data packet of the first service flow arrives at the ingress port of the AN-TT outside the access network device after being transmitted through the N3 link, and t4 is the time at which the data packet of the first service flow is processed by the AN-TT.

[0268] For example, the first device may obtain processing time information of the third device from the third device, and determine the processing time of the first service flow in the third device based on the processing time information of the third device.

[0269] The processing time information of the third device may include a 5QI and a processing time of the service flow corresponding to the 5QI at the third device. Further, the first device may determine a processing time of the first service flow at the third device based on the 5QI of the first service flow and the processing time information of the third device.

[0270] Alternatively, the processing time information of the third device may include a data packet size range and a processing time of a service flow that satisfies the data packet size range at the third device. Further, the first device may determine a data packet size range that includes data packets of the first service flow based on the size of the data packets of the first service flow, and may determine a processing time of the first service flow at the third device based on the processing time information of the third device.

[0271] Alternatively, the processing time information of the third device includes the processing time of the service flow in the third device, in other words, the processing time of all service flows in the third device is the same length of time, and as a result, the third device determines the processing time of the service flow in the third device in the processing time information of the third device as the processing time of the first service flow in the third device.

[0272] In addition, when the first device is a device other than the session management network element, the session management network element may send the processing time of the first service flow in the third device or processing time information of the third device to the first device.

[0273] Referring to Scenario 1 and Scenario 2, the following uses an example to describe an implementation in which the first device obtains the processing time information of the third device from the third device.

[0274] According to Scenario 1, the first device may obtain the processing time information of the user plane network element from the user plane network element. For details, please refer to the above related content. The overlapping part is not described.

[0275] According to Scenario 2, the first device may obtain the processing time information of the access network device or the processing time information of the translator corresponding to the access network device. For details, please refer to the above related content. The overlapping parts are not described.

[0276] In addition, when the first device is a device other than the session management network element, the session management network element may transmit the processing time of the first service flow at the third device and the processing time information of the third device to the first device, and the first device may receive the above information directly from the session management network element or may receive the above information from the session management network element through another network element (e.g., a policy control network element). Alternatively, the session management network element may store the above information in a data repository network element (e.g., a UDR network element) through a data management network element (e.g., a UDM network element), and the first device may obtain the above information from the data repository network element. Alternatively, the processing time information of the third device may be configured on the first device.

[0277] In addition, when the first device is a device other than a session management network element, the session management network element may send the maximum buffer time length information of the second device or the maximum buffer time length of the first service flow in the second device to the first device, or the maximum buffer time length information of the second device may be configured on the first device.

[0278] In the above scheme, the first device may determine the maximum buffer time length of the first service flow at the second device, and then determine the latest transmission time according to equation (9-1), equation (9-2), equation (9-3), or equation (10-1).

[0279] In addition, the maximum buffer time T of the first service flow in the second device* may not be determined first, and the latest transmission time may be determined by referring to equation (9-1), equation (9-2), equation (9-3), or equation (10-1) to determine the maximum buffer time T of the first service flow in the second device. * can be determined directly in the above manner for determining

[0280] For example, in a scenario where jitter is not considered, with reference to equation (9-1) it can be seen that: T3 B = T1 + packet delay budget for transmitting the first service flow between the second device and the third device - processing time of the first service flow at the third device - maximum transmission latency of the first service flow between the second device and the third device, Equation (9-4)

[0281] In a scenario where jitter is taken into account, with reference to equation (10-1) it can be seen that: T3 B = T1 + packet delay budget for transmitting the first service flow between the second device and the third device - processing time of the first service flow in the third device - maximum transmission latency of the first service flow between the second device and the third device - Jitter, Equation (10-2)

[0282] Method C: Based on methods A and B, the smaller of the latest transmission times determined in method A and the latest transmission times determined in method B is selected as the latest transmission time. For example, T3 A and T3 B The smaller value of

[0283] It should be noted that the above three methods for determining the latest transmission time are merely examples.

[0284] Therefore, the first device may determine the earliest transmission time and the latest transmission time by referring to the above scheme, and then the first device may determine a time that is not earlier than the earliest transmission time and not later than the latest transmission time as the service flow transmission time. Alternatively, the first device may further determine an offset of the service flow transmission time relative to a reference time based on the determined service flow transmission time, and use the offset as information of the service flow transmission time.

[0285] In a second implementation, the first device may directly determine the offset of the service flow transmission time relative to a reference time.

[0286] For the second implementation, the first device may determine a minimum offset and a maximum offset based on information about the service flow arrival time. The minimum offset is the minimum offset of the time at which the second device transmits the first service flow relative to a reference time and is equal to the offset of the earliest transmission time relative to the reference time in the first implementation. The maximum offset is the maximum offset of the time at which the second device transmits the first service flow relative to the reference time and is equal to the offset of the latest transmission time relative to the reference time in the first implementation. Further, the first device may obtain an offset selection value, where the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset. Further, the first device determines information about the service flow transmission time based on the offset selection value. The offset selection value may be used as the offset of the service flow transmission time relative to the reference time, or the difference between the offset selection value and the jitter latency associated with the first service flow may be used as the offset of the service flow transmission time relative to the reference time.

[0287] For example, the minimum offset may be the earliest transmit offset (EarliestTransmitOffset) in TSpecTimeAware, which is used to define the earliest time offset relative to the reference time at which the second device can start transmitting a data packet in a cycle (Interval) of the first service flow.

[0288] For the minimum offset, the first device may determine the minimum offset based on information about the service flow arrival time and the processing time of the first service flow at the second device, for example, the minimum offset is the sum of the offset of the service flow arrival time relative to a reference time and the processing time of the first service flow at the second device, or the minimum offset is the sum of the offset of the service flow arrival time relative to a reference time, the processing time of the first service flow at the second device, and the jitter latency associated with the first service flow.

[0289] For example, in a scenario where jitter is not considered: EarliestTransmitOffset = T1 - offset + processing time of the second device, Equation (11-1)

[0290] T1-offset indicates the offset of the service flow arrival time relative to the reference time, and may be the T1-offset (uplink) obtained according to equation (2) or the T1-offset (downlink) obtained according to equation (4).

[0291] For example, when the first service flow is an uplink service flow: EarliestTransmitOffset(uplink) = T1-Offset(uplink) + T AN , formula (11-2)

[0292] In addition, the first device may further skip the process of calculating the T1-Offset (uplink) and directly calculate the EarliestTransmitOffset (uplink). EarliestTransmitOffset(uplink)=Burst Arrival Time 1*+UE-DS-TT Residence Time+PDB+T AN , formula (11-3)

[0293] For example, when the first service flow is a downlink service flow: EarliestTransmitOffset(downlink) = T1 - Offset(downlink) + T UPF , formula (11-4)

[0294] In addition, the first device may further skip the process of calculating the T1-Offset (downlink) and directly calculate the EarliestTransmitOffset (downlink). EarliestTransmitOffset(downlink)=Burst Arrival Time 2*+T UPF , formula (11-5)

[0295] In a scenario where jitter is taken into account, the following occurs: EarliestTransmitOffset = T1 - Offset + Processing time of second device + Jitter, Equation (12-1)

[0296] For example, when the first service flow is an uplink service flow: EarliestTransmitOffset(uplink) = T1-Offset(uplink) + T AN +Jitter, formula (12-2)

[0297] For example, when the first service flow is a downlink service flow: EarliestTransmitOffset(downlink) = T1 - Offset(downlink) + T UPF +Jitter, formula (12-3)

[0298] Similarly, the first device may also skip the process of calculating the T1-offset, and the details will not be described again here.

[0299] For a specific manner in which the first device determines the processing time of the first service flow in the second device, please refer to the relevant description above, and the details will not be described again.

[0300] For example, the maximum offset may be the latest transmit offset (LatestTransmitOffset) in TSpecTimeAware, which is used to define the latest time offset relative to a reference time at which the second device can start transmitting a frame in a cycle (Interval) of the first service flow.

[0301] Regarding the maximum offset, the maximum offset corresponds to the latest transmission time. Therefore, for the manner in which the first device determines the maximum offset, please refer to the above manner in which the latest transmission time is determined.

[0302] Method A*: The scenario where jitter is not considered is as follows. LatestTransmitOffset=T1-Offset+Interval-[MaxFrameSize], Equation (13-1)

[0303] In addition, the first device may further skip the process of calculating the T1-Offset (uplink) and directly calculate the LatestTransmitOffset (uplink). LatestTransmitOffset(uplink)=Burst Arrival Time 1*+UE-DS-TT Residence Time+PDB+Interval-[MaxFrameSize], Equation (13-2)

[0304] The first device may further skip the process of calculating the T1-offset (downlink) and directly calculate the LatestTransmitOffset (downlink). LatestTransmitOffset (downlink) = Burst Arrival Time 2 * + Interval - [MaxFrameSize], Equation (13-3).

[0305] In a scenario where jitter is taken into account, the following occurs: LatestTransmitOffset=T1-Offset+Interval-[MaxFrameSize]-Jitter, Equation (14)

[0306] Similarly, the first device may also skip the process of calculating the T1-offset, and the details will not be described again here.

[0307] For Scheme A*, please refer to the related description of Scheme A, which corresponds to the slowest transmission time in the first implementation.

[0308] Scheme B*: In a scenario where jitter is not considered, the following occurs: LatestTransmitOffset=T1-Offset+T'+T * , formula (15-1)

[0309] In addition, the first device may further skip the process of calculating the T1-Offset (uplink) and directly calculate the LatestTransmitOffset (uplink). LatestTransmitOffset(uplink)Burst Arrival Time 1*+UE-DS-TT Residence Time+PDB+T'+T* , formula (15-2)

[0310] The first device may further skip the process of calculating the T1-Offset (downlink) and directly calculate the LatestTransmitOffset (downlink). LatestTransmitOffset(downlink)=Burst Arrival Time 2*+L'+T * , formula (15-3)

[0311] In a scenario where jitter is taken into account, the following occurs: LatestTransmitOffset=T1-Offset+T'+T * -Jitter, formula (16)

[0312] Similarly, the first device may also skip the process of calculating the T1-offset, and the details will not be described again here.

[0313] For Scheme B*, please refer to the related description of Scheme B, which corresponds to the slowest transmission time in the first implementation.

[0314] Method C*: Based on methods A* and B*, the smaller of the maximum offset determined in method A* and the maximum offset determined in method B* is selected as the maximum offset.

[0315] For method C*, please refer to the related description of method C, which corresponds to the slowest transmission time in the first implementation.

[0316] For example, after the minimum offset and the maximum offset are determined in the above manner, the first device may obtain an offset selection value in the following manner, but is not limited thereto.

[0317] In a possible design, the first device may send a minimum offset and a maximum offset to the fourth device, and the fourth device may determine an offset selection value based on the minimum offset and the maximum offset and send the offset selection value to the first device.

[0318] In addition, the above method is also applicable to the first implementation. For example, the first device transmits the offset of the earliest transmission time relative to a reference time and the offset of the latest transmission time relative to the reference time to the fourth device. The fourth device may determine an offset selection value based on the offset of the earliest transmission time relative to the reference time and the offset of the latest transmission time relative to the reference time and transmit the offset selection value to the first device. The offset selection value for the first service flow is greater than or equal to the minimum offset for the first service flow and less than or equal to the maximum offset for the first service flow.

[0319] It can be understood that the offset of the earliest transmission time relative to the reference time is equal to the minimum offset, and the offset of the latest transmission time relative to the reference time is equal to the maximum offset. In the following, the maximum and minimum offsets are used purely as illustrative examples.

[0320] In a possible implementation, in addition to the minimum and maximum offsets of the first service flow, the fourth device may further obtain the minimum and maximum offsets of the second service flow, where the second service flow and the first service flow arrive at the second device at the same time, or the difference between the time the second service flow arrives at the second device and the time the first service flow arrives at the second device is less than or equal to a threshold.

[0321] The fourth device may determine an offset selection value for the first service flow and an offset selection value for the second service flow based on the minimum and maximum offsets of the first service flow and the minimum and maximum offsets of the second service flow.

[0322] The offset selection value for the first service flow is greater than or equal to the minimum offset and less than or equal to the maximum offset of the first service flow, and the offset selection value for the second service flow is greater than or equal to the minimum offset and less than or equal to the maximum offset of the second service flow, thereby ensuring deterministic latency requirements for the first service flow and the second service flow. Additionally, the difference between the offset selection value for the first service flow and the offset selection value for the second service flow is greater than or equal to the length of time corresponding to MaxFrameSize data packets of the first service flow (when the fourth device determines that the offset selection value for the first service flow is less than the offset selection value for the second service flow) or the length of time corresponding to MaxFrameSize data packets of the second service flow (when the fourth device determines that the offset selection value for the first service flow is greater than the offset selection value for the second service flow), thereby avoiding congestion between the first service flow and the second service flow.

[0323] Optionally, the first device may further transmit the priority of the first service flow to the fourth device. The fourth device may determine an offset selection value based on the obtained maximum offset and minimum offset of the first service flow and the priority of the first service flow. For example, a small offset selection value is set for a service flow with a high priority. A smaller offset selection value indicates a shorter time for caching data packets of the service flow in the second device, and a larger offset selection value indicates a longer time for caching data packets of the service flow in the second device. Setting a small offset selection value for a service flow with a high priority ensures that data packets of the service flow are transmitted preferentially, and therefore ensures low transmission latency of the service flow.

[0324] Optionally, the first device may further transmit the priority of the second service flow to the fourth device, and the fourth device may determine the offset selection value for each service flow by taking into consideration the priority of the service flow as a whole.

[0325] Optionally, the first device further transmits to the fourth device a maximum latency requirement for transmitting the first service flow between the second device and the third device. The fourth device may determine an offset selection value by referring to the maximum latency requirement, the minimum offset, and the maximum offset for transmitting the first service flow between the second device and the third device, and transmit the offset selection value to the first device. The maximum latency requirement for transmitting the first service flow between the second device and the third device is a maximum allowable value for the length of time from when the second device transmits the first service flow to when the third device receives the first service flow, or the length of time from when the third device transmits the first service flow to when the second device receives the first service flow.

[0326] For example, the first device may determine a maximum latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device and the processing time of the first service flow at the second device. For the packet delay budget for transmitting the first service flow between the second device and the third device and the processing time of the first service flow at the second device, please refer to the above description. Details will not be described again here. For example, the maximum latency requirement for transmitting the first service flow between the second device and the third device = the packet delay budget for transmitting the first service flow between the second device and the third device - the processing time of the first service flow at the second device.

[0327] In another example, the first device may determine a maximum latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, the processing time of the first service flow at the second device, and the processing time of the first service flow at the third device. For the processing time of the first service flow at the third device, please refer to the above description. Details will not be described again here. For example, the maximum latency requirement for transmitting the first service flow between the second device and the third device = packet delay budget for transmitting the first service flow between the second device and the third device - processing time of the first service flow at the second device - processing time of the first service flow at the third device.

[0328] It can be understood that a smaller value of the maximum latency requirement indicates that the latency requirement of the service flow is higher and that the service flow needs to be transmitted as soon as possible, whereas a larger value of the maximum latency requirement indicates that the latency requirement of the service flow is lower and that the service flow does not need to be transmitted as soon as possible.

[0329] For example, when the first service flow is an uplink service flow, the SMF network element may determine a packet delay budget (PDB2) (or PDB2′) for transmitting the first service flow between the second device and the third device, a processing time (T AN ), and the processing time of the first service flow in the user plane network element (T UPF ), a maximum latency requirement MaxLatency between the second device and the third device can be determined. The following uses PDB2 as an example: MaxLatency=PDB2-T AN -T UPF .

[0330] When the first service flow is a downlink service flow, the SMF network element determines a packet delay budget (PDB4) (or PDB4′) for transmitting the first service flow between the second device and the third device, a processing time (T UPF ), and the processing time of the first service flow in the access network device or AN-TT (T AN ), a maximum latency requirement MaxLatency between the second device and the third device can be determined. The following uses PDB4 as an example: MaxLatency=PDB4-T UPF -T AN .

[0331] For example, but not limited to, the fourth device may determine the offset selection value in the following manner:

[0332] In implementation, the fourth device may determine an offset selection value based on the obtained maximum and minimum offsets of the first service flow and the maximum latency requirement of the service flow. For example, a small offset selection value is set for a service flow having a small maximum latency requirement for transmitting the service flow between the second device and the third device. A smaller offset selection value indicates a shorter time for caching data packets of the service flow in the second device, and a larger offset selection value indicates a longer time for caching data packets of the service flow in the second device. Setting a small offset selection value for a service flow with a high latency requirement ensures that data packets of the service flow are transmitted preferentially, thus ensuring low transmission latency for the service flow.

[0333] Optionally, the first device may further transmit maximum latency requirements of the multiple service flows to the fourth device, and the fourth device may determine an offset selection value for each service flow by comprehensively considering the maximum latency requirements of the service flows. For example, if the maximum latency requirement of a service flow between the second device and the third device is small, the fourth device may determine a value close to the smallest offset corresponding to the service flow as the offset selection value corresponding to the service flow; if the maximum latency requirement of the service flow between the second device and the third device is large, the fourth device may determine a value close to the largest offset corresponding to the service flow as the offset selection value corresponding to the service flow.

[0334] It should be noted that the specific method for determining the offset selection value by the fourth device is not limited in this application. The above content is merely an example and is not intended to limit the present application. In addition, the above methods can be combined.

[0335] In another possible design, the first device may autonomously determine the offset selection value based on a minimum offset and a maximum offset.

[0336] It may be understood that the first device and the fourth device are integrated, or the first device integrates the functionality of the fourth device.

[0337] According to the above method, the first device may obtain an offset selection value and use the offset selection value as an offset of the service flow transmission time relative to a reference time, or may use the difference between the offset selection value and a jitter latency associated with the first service flow as an offset of the service flow transmission time relative to the reference time to obtain an offset of the service flow transmission time relative to the reference time.

[0338] Step 820: The first device instructs the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow.

[0339] For example, when the first service flow is an uplink service flow and the second device is an access network device, the first device may send information about the service flow transmission time to the access network device. When the second device is an AN-TT, the first device may send information about the service flow transmission time directly to the AN-TT. Alternatively, the first device may first send information about the service flow transmission time to the access network device, and then the access network device may notify the AN-TT of the information. When the first service flow is a downlink service flow, the first device may send information indicating the service flow transmission time to a user plane network element (N3-TT).

[0340] In a first possible design, the information about the service flow transmission time includes an offset of the service flow transmission time relative to a reference time, or the service flow transmission time.

[0341] It may be understood that in some special cases, the offset selection value may also be equal to the minimum offset, in other words, the service flow transmission time may be equal to the earliest transmission time. In the following, the offset selection value is used as an example for explanation. For example, at a certain time, no service flows other than the first service flow arrive at the second device, and the second device may transmit the first service flow based on the minimum offset. In another example, three service flows arrive at the second device simultaneously, where the service flows are service flow a, service flow b, and service flow c. For service flow a, the offset selection value corresponding to service flow a may be equal to the minimum offset corresponding to service flow a. In this case, after service flow a arrives at the second device and is processed by the second device, the second device immediately transmits service flow a to the third device. For service flow b, the offset selection value corresponding to service flow b may be greater than the minimum offset corresponding to service flow b and less than or equal to the maximum offset corresponding to service flow b (here, the offset selection value corresponding to service flow b is denoted as the first value). In this case, after service flow b arrives at and is processed by the second device, the second device needs to wait a period of time corresponding to the difference between the first value and the minimum offset corresponding to service flow b before sending service flow b to the third device. For service flow c, the selected offset value corresponding to service flow c may be greater than the minimum offset corresponding to service flow c and may be less than or equal to the maximum offset corresponding to service flow c (here, the selected offset value corresponding to service flow c is denoted as the second value), where the second value is greater than the first value. After service flow c arrives at and is processed by the second device, the second device needs to wait a period of time corresponding to the difference between the second value and the minimum offset corresponding to service flow c before sending service flow c to the third device.Therefore, different service flow transmission times are configured for the service flows according to the above method, so that no congestion occurs among the data packets of the three service flows and the latency requirements of the three service flows can be met separately.

[0342] Optionally, the difference between the first value and the minimum offset is a time length corresponding to data packets of MaxFrameSize for service flow a, and the difference between the second value and the first value is a time length corresponding to data packets of MaxFrameSize for service flow b. Based on the above configuration, service flow b can be transmitted after service flow a completes transmission, and service flow c can be transmitted after service flow b completes transmission. In this way, transmission congestion among service flows a, b, and c can be better avoided, network resources can be fully utilized, and overall network performance can be improved.

[0343] For example, the fourth device transmits interface configuration information about the second device to the first device. The first device transmits interface configuration information about the second device to the second device. For example, the interface configuration information about the second device includes an interface identifier (Interface ID) of the second device and information about a service flow transmission time. The interface identifier of the second device is used to identify an interface of the second device and may include a MAC address and an interface name (Interface Name). The interface corresponding to the interface identifier of the second device is the egress port used to transmit the first service flow. In other words, the second device may know which interface will be used as the egress port for transmitting the first service flow based on the interface identifier (Interface ID) of the second device, and may refer to the information about the service flow transmission time and wait until the service flow transmission time at the egress port based on the information about the service flow transmission time before transmitting the first service flow.

[0344] In addition, the fourth device may further transmit interface configuration information about the third device to the first device, and the first device transmits the interface configuration information about the third device to the third device. For example, the interface configuration information about the third device includes an interface identifier of the third device. Optionally, the interface configuration information about the third device may further include information about service flow transmission times. The interface identifier of the third device is used to identify an interface of the third device and may include a MAC address and an interface name. The interface corresponding to the interface identifier of the third device is a receive port used to receive the first service flow. In other words, the third device may know which interface to use as a receive port for receiving the first service flow based on the interface identifier of the third device.

[0345] In addition, the interface configuration information for the second device and the interface configuration information for the third device may further include a QoS flow identifier (QFI) and a corresponding priority. When encapsulating a data packet of the first service flow, the second device may include a priority corresponding to the QFI in the outer MAC, so that a switching node on the path between the second device and the third device determines a transmission queue corresponding to the data packet based on the priority of the included QFI.

[0346] For example, as shown in FIG. 11, eight transmission queues correspond to different priorities, and the second device may determine the transmission queue in which the data packets of the first service flow are located based on the priority of the QoS flow identifier.

[0347] In a possible design, the information about the service flow transmission times includes gate control scheduling parameters.

[0348] For example, the first device may further determine gate control scheduling parameters based on the cycle, maximum burst size, and service flow transmission time of the first service flow. The gate control scheduling parameters here are first gate control scheduling parameters, in other words, the first gate control scheduling parameters are gate control scheduling parameters determined by the first device. The first gate control scheduling parameters may include a port gate control cycle management value (AdminCycleTime), a base time management value (AdminBaseTime), and a port gate control list management value (AdminControlList).

[0349] The second device determines second gate control scheduling parameters based on the first gate control scheduling parameters. In other words, the second gate control scheduling parameters are gate control scheduling parameters determined by the second device. The second gate control scheduling parameters may include an operating value of a port gate control cycle (OperCycleTime), an operating value of a base time (OperBaseTime), a start time of a gate control cycle (CycleStartTime), and an operating value of a gate control list executed in the port (OperControlList).

[0350] The following describes the relationship between the first gate control scheduling parameter and the second gate control scheduling parameter.

[0351] AdminCycleTime is used to configure the gate control cycle of each port. The second device uses this parameter to set OperCycleTime. AdminCycleTime and OperCycleTime can be the same or different.

[0352] AdminBaseTime is used to configure the start time of the gate control cycle for each port. Typically, AdminBaseTime indicates the time length relative to the start time of the time domain (e.g., January 1, 1970, 00:00:00). The second device uses this parameter to set OperBaseTime. AdminBaseTime and AdminBaseTime can be the same or different. The second device can determine CycleStartTime based on OperBaseTime and OperCycleTime, where CycleStartTime=OperBaseTime+N*OperCycleTime, where N indicates the Nth cycle and N is a positive integer.

[0353] The AdminControlList is used to configure the transmission queue gate control action of each port and includes a gate control state (gateState) and a time interval (TimeInterval), where gateState is the gate control state (open or closed) of each transmission queue of the port. If the gate control state is open, the switching node can transmit the service flow; if the gate control state is closed, the switching node cannot transmit the service flow. The TimeInterval indicates the duration of the gate control state. The switching node uses this parameter to set the operation value of the OperControlList. The AdminControlList and OperControlList can be the same or different.

[0354] FIG. 11 is a schematic diagram of an AdminControlList or an OperControlList. The gate control list on the right side of FIG. 11 may represent an AdminControlList or an OperControlList. Below, the AdminControlList is used as an example for explanation. As shown in FIG. 11, at a time point corresponding to AdminBaseTime T00, the gate control states corresponding to the eight transmission queues corresponding to sequence numbers 7 to 0 are sequentially oCooCooo. C indicates that the gate control state is closed, in other words, data packets in the corresponding queues cannot be transmitted; o indicates that the gate control state is open, in other words, data packets in the corresponding queues can be transmitted. The duration of the state is the duration from T00 to T01. In other words, the gate control state changes at a time point corresponding to T01. Specifically, at a time point corresponding to T01, the gate control states corresponding to the eight transmission queues corresponding to sequence numbers 7 to 0 are sequentially CoCooCCo. For example, at the time corresponding to T05, the gate control state of the transmission queue corresponding to sequence number 7 is C, in other words, the second device does not transmit data packets in the transmission queue corresponding to sequence number 7 at the time corresponding to T05. At the time corresponding to T05, the gate control state of the transmission queue corresponding to sequence number 6 is o, in other words, the second device can transmit data packets in the transmission queue corresponding to sequence number 6 at the time corresponding to T05.

[0355] It can be understood that the second device may be configured to transmit multiple service flows, which may or may not arrive at the second device simultaneously, and the priorities of the multiple service flows may be the same or different. Currently, when the priorities of the multiple service flows are different, the second device may place each service flow in a different transmission queue based on the priority of the service flow. Multiple service flows with the same priority are placed in the same transmission queue. For each transmission queue, the first device may determine a corresponding first gate control scheduling parameter based on the service flow that needs to be transmitted in the transmission queue, and the second device may determine a second gate control scheduling parameter corresponding to the transmission queue based on the first gate control scheduling parameter corresponding to the transmission queue. In other words, the gate control scheduling parameter corresponding to the transmission queue is used to schedule one or more service flows with the same priority and transmitted using the transmission queue.

[0356] Specifically, for a method for configuring the first gate control scheduling parameter by the first device, please see the example below.

[0357] Example 1: When multiple service flows with the same priority arrive simultaneously, the first device places the multiple service flows in one transmission queue and transmits the minimum and maximum offsets (and optionally the priority) of each of the multiple service flows to the fourth device. The fourth device may configure a different offset selection value for each service flow. For example, the interval between the offset selection values ​​of any two adjacently transmitted service flows in the offset selection values ​​corresponding separately to the multiple service flows, as determined by the fourth device, is not smaller than the time length corresponding to the largest data packet of the service flow transmitted first among the two service flows, so that congestion does not occur during the transmission of the multiple service flows. In addition, the offset selection value corresponding to each service flow is greater than or equal to the minimum offset corresponding to the service flow and less than or equal to the maximum offset corresponding to the service flow, satisfying the deterministic latency requirement corresponding separately to the multiple service flows. Furthermore, the first device may determine information about the service flow transmission time of each service flow based on the offset selection values ​​corresponding separately to the multiple service flows and transmit the information to the second device.

[0358] In addition, the first device may further determine an AdminBaseTime based on the minimum value among the offset selection values ​​corresponding separately to the multiple service flows, determine an AdminCycleTime based on the least common multiple of the cycles corresponding separately to the multiple service flows, and determine the length of time that the gate state is open based on the length of time corresponding to the maximum data packet of each service flow.

[0359] In other words, in this example, the first device transmits the offset selection value and the first gate control scheduling parameter of the service flow to the second device.

[0360] For example, periodic service flow J and periodic service flow K have the same priority. Both periodic service flow J and periodic service flow K are downlink service flows. EarliestTransmitOffset corresponds to the minimum offset, LatestTransmitOffset corresponds to the maximum offset, and TimeAwareOffset corresponds to the offset selection value. In the following example, LatestTransmitOffset is calculated in scheme A* for determining the maximum offset. It can be understood that LatestTransmitOffset can alternatively be calculated in scheme B* or scheme C*. This is merely an example and is not limited to this embodiment of the present application.

[0361] The parameters of periodic service flow J are as follows: <Maximum Burst Size in time> (indicating the time length corresponding to the transmission of the largest data packet of periodic service flow J) = (120 μs); Processing time = 100 μs; Interval (representing the cycle of periodic service flow J) = 500 μs; and The offset of the arrival time of periodic service flow J relative to the reference time = 1600,000,000,000,110 μs.

[0362] The parameters of periodic service flow K are as follows: <Maximum Burst Size in time> (indicating the time length corresponding to the transmission of the largest data packet of periodic service flow K) = (80 μs); Processing time = 100 μs; Interval (representing the cycle of periodic service flow J) = 500 μs; and The offset of the arrival time of periodic service flow K relative to the reference time = 1600,000,000,000,110 μs.

[0363] In a scenario where latency jitter is not considered, the EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of flow J may be calculated according to equations (11-4) and (13-1). EarliestTransmitOffset = offset of arrival time of periodic service flow J relative to the reference time + processing time = 1600,000,000,000,210 μs; and LatestTransmitOffset = offset of the arrival time of periodic service flow J relative to the reference time + 500 - 120 = 1600,000,000,000,490 μs.

[0364] In a scenario where latency jitter is not considered, the EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of flow K may be calculated according to equations (11-4) and (13-1). EarliestTransmitOffset = offset of the arrival time of periodic service flow K relative to the reference time + 100 μs = 1600,000,000,000,210 μs; and LatestTransmitOffset = offset of the arrival time of periodic service flow K relative to the reference time + 500 - 80 = 1600,000,000,000,530 μs.

[0365] The TimeAwareOffset (corresponding to the offset selection value) returned by the fourth device is assumed to be: For periodic service flow J, TimeAwareOffset=1600,000,000,000,320 μs; and For periodic service flow K, TimeAwareOffset=1600,000,000,000,440 μs.

[0366] The fourth device is for flow J and flow K.<Maximum Burst Size in time> Note that by knowing the TimeAwareOffset of each service flow, the fourth device can obtain the jitter through calculation.<Maximum Burst Size in time> Therefore, the difference between the TimeAwareOffset corresponding to flow J and the TimeAwareOffset corresponding to flow K, as determined by the fourth device, is<Maximum Burst Size in time> Therefore, the deterministic transmission of flow J is ensured.

[0367] Further, based on the above results, the first device may determine: The offset of the transmission time of periodic service flow J relative to the reference time is 1600,000,000,000,320 μs, and the offset of the transmission time of periodic service flow K relative to the reference time is 1600,000,000,000,440 μs; and Gate control scheduling parameters corresponding to periodic service flow J and periodic service flow K: AdminBaseTime of 1600,000,000,000,320 μs, AdminCycleTime of 500 μs, and AdminControlList, where TimeInterval=200 μs if GateState=Open; and TimeInterval=300 μs if GateState=Closed.

[0368] The first device transmits the above determined parameters to the second device, and the second device determines the following based on these parameters: The offset of the transmission time of periodic service flow J relative to the reference time is 1600,000,000,000,320 μs, and the offset of the transmission time of periodic service flow K relative to the reference time is 1600,000,000,000,440 μs; and the OperBaseTime, OperCycleTime, and OperControlList of periodic service flow J and periodic service flow K, where, for example, OperCycleTime=AdminCycleTime=500 μs; OperBaseTime=AdminBaseTime=1600,000,000,000,320 μs; and AdminControlList is the same as OperControlList.

[0369] The second device may transmit periodic service flow J to the third device based on the offset of the transmission time of periodic service flow J relative to the reference time and the second gate-controlled scheduling parameter, and may transmit periodic service flow K to the third device based on the offset of the transmission time of periodic service flow K relative to the reference time and the second gate-controlled scheduling parameter, which may satisfy the deterministic latency requirements of periodic service flow J and periodic service flow K and avoid congestion between periodic service flow J and periodic service flow K.

[0370] An explanation will now be provided with reference to Figure 12A. Since the time length corresponding to the transmission of the largest data packet of periodic service flow J is 120 μs and the time length corresponding to the transmission of the largest data packet of periodic service flow K is 80 μs, the difference between the TimeAwareOffset corresponding to periodic service flow J and the TimeAwareOffset corresponding to periodic service flow K may be the time length corresponding to the largest data packet of periodic service flow J (i.e., 120 μs). The time length for which the gate state remains open in each cycle is 200 μs. In other words, the time length for which the gate state remains open in each cycle is the sum of the time length corresponding to the largest data packet of periodic service flow J and the time length corresponding to the largest data packet of periodic service flow K. After the gate state is switched to open for 200 μs, the gate state is switched to closed. In addition, the cycle of periodic service flow J is the same as that of periodic service flow K, i.e., 500 μs. In other words, the gate state is switched closed for 300 μs before the next cycle begins and the gate state is switched open again.

[0371] In the above scheme, different service flow transmission times for periodic service flow J and periodic service flow K and corresponding gate control scheduling parameters for periodic service flow J and periodic service flow K are configured, so that congestion between service flows with the same priority and arriving at the second device at the same time can be avoided and the deterministic latency requirements of the service flows can be ensured.

[0372] Example 2: When multiple service flows with the same priority arrive simultaneously, the first device places the multiple service flows in one transmission queue and sends the minimum offset, maximum offset, and priority of each of the multiple service flows to the fourth device. The fourth device may configure an offset selection value for each service flow. The offset selection value corresponding to each service flow is greater than or equal to the minimum offset corresponding to the service flow and less than or equal to the maximum offset corresponding to the service flow, satisfying the deterministic latency requirements corresponding to the multiple service flows separately. The first device may determine an AdminBaseTime based on the minimum value of the difference between the offset selection values ​​corresponding to the multiple service flows separately and the corresponding jitters, determine an AdminCycleTime based on the least common multiple of cycles corresponding to the multiple service flows separately, and determine the length of time the gate state is open based on the length of time corresponding to the largest data packet of each service flow.

[0373] In this case, the first device may implicitly indicate the service flow transmission times for the multiple service flows by using AdminBaseTime, rather than directly configuring the service flow transmission times corresponding to the multiple service flows separately. The service flow transmission time may be the service flow transmission time of any service flow in the multiple service flows, and a service flow after another service flow is transmitted randomly; in other words, the transmission order of each service flow is not specified. A sufficient length of time during which the gate state is open is ensured to ensure that all of the multiple service flows can be transmitted from the second device when the gate state is open.

[0374] For example, periodic service flow J and periodic service flow K have the same priority. For specific parameters of periodic service flow J and periodic service flow K, please refer to the description of Example 1.

[0375] Similarly, the jitter of periodic service flow J and periodic service flow K can be calculated based on the above related description of latency jitter. For periodic service flow J, Jitter = 40 μs; and For periodic service flow K, Jitter=60 μs.

[0376] Therefore, the EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of flow J can be calculated according to equations (12-3) and (14). EarliestTransmitOffset = arrival time offset of periodic service flow J relative to the reference time + processing time + Jitter = 1600,000,000,000,250 μs; and LatestTransmitOffset = offset of the arrival time of periodic service flow J relative to the reference time + 500 - 120 - Jitter = 1600,000,000,000,450 μs.

[0377] The EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of flow K can be calculated according to equations (12-3) and (14). EarliestTransmitOffset = offset of arrival time of periodic service flow K relative to the reference time + 100 μs + Jitter = 1600,000,000,000,270 μs; and LatestTransmitOffset = offset of arrival time of periodic service flow K relative to the reference time + 500 - 80 - Jitter = 1600,000,000,000,470 μs.

[0378] The TimeAwareOffset returned by the fourth device (corresponding to the offset selection value) is assumed to be: For periodic service flow J, TimeAwareOffset=1600,000,000,000,320 μs; and For periodic service flow K, TimeAwareOffset=1600,000,000,000,340 μs.

[0379] The first device subtracts the corresponding jitter from each TimeAwareOffset to obtain: the difference between the TimeAwareOffset corresponding to flow J and the corresponding jitter is 1600,000,000,000,320-40=1600,000,000,000,280 μs, and the difference between the TimeAwareOffset corresponding to flow K and the corresponding jitter is 1600,000,000,000,340-60=1600,000,000,000,280 μs. Furthermore, the first device may determine that the AdminBaseTime is 1600,000,000,000,280 μs based on the above results. The first device may further determine that the AdminCycleTime is 500 μs, and set the AdminCycleTime and<Maximum Burst Size in time> where if GateState=Open, then TimeInterval=200 μs; if GateState=Closed, then TimeInterval=300 μs.

[0380] The fourth device determines, based on the priority of the service flow sent by the first device, that the flow J and the flow K are service flows with the same priority, and<Maximum Burst Size in time> Note that the fourth device may obtain jitter through a calculation based on AdminBaseTime. When determining the TimeAwareOffset for each service flow, the fourth device may refer to the jitter, such that the difference between the TimeAwareOffset corresponding to flow J and the corresponding jitter, as determined by the first device, and the difference between the TimeAwareOffset corresponding to flow K and the corresponding jitter, correspond to the same time offset, i.e., AdminBaseTime.

[0381] An explanation will now be provided with reference to Figure 12B. Since the time length corresponding to the transmission of the largest data packet of periodic service flow J is 120 μs and the time length corresponding to the transmission of the largest data packet of periodic service flow K is 80 μs, the time during which the gate state remains open in each cycle is 200 μs. In other words, after the gate state is switched to open for 200 μs, the gate state is switched to closed. In addition, the cycle of periodic service flow J is the same as that of periodic service flow K, i.e., 500 μs. In other words, after the gate state is switched to closed for 300 μs, the next cycle begins and the gate state is switched to open again.

[0382] After receiving the AdminBaseTime, AdminCycleTime, and AdminControlList for periodic service flow J and periodic service flow K, the second device may determine the OperBaseTime, OperCycleTime, and OperControlList for periodic service flow J and periodic service flow K based on these parameters. For example, OperCycleTime=AdminCycleTime=500μs; OperBaseTime=AdminBaseTime=1600,000,000,000,280μs; ​​and AdminControlList is the same as OperControlList.

[0383] As shown in FIG. 12C , because periodic service flow J and periodic service flow K have the same priority, periodic service flow J and periodic service flow K are transmitted in the same transmission queue. For ease of explanation, it is assumed that the egress port of the second device supports only two transmission queues. It is assumed that periodic service flow J and periodic service flow K are transmitted in transmission queue 1, and another periodic service flow M is transmitted in transmission queue 0. To facilitate the explanation of the gate control operation process of the second device for periodic service flow J and periodic service flow K, it is assumed here that periodic service flow M does not have a low transmission latency requirement and that periodic service flow M is transmitted when the transmitting node has idle resources. The time point corresponding to AdminBaseTime T00 is used as an example. In this case, the gate control state of transmission queue 1 is open, and the second device can transmit periodic service flow J and periodic service flow K. If periodic service flow J and periodic service flow K arrive at the second device at the same time, periodic service flow J may be transmitted first, followed by periodic service flow K; or periodic service flow K may be transmitted first, followed by periodic service flow J. The length of time that the gate control state is open is 200 μs, and the second device completes the transmission of periodic service flow J and periodic service flow K. At a time corresponding to T01, the gate control state of each transmission queue changes. In this case, the gate control state of transmission queue 1 is closed, and the length of time that the gate control state is open is 300 μs. The second device stops transmitting periodic service flow J and periodic service flow K and starts transmitting periodic service flow M. At a time corresponding to T02, the gate control operation continues for one cycle, i.e., OperCycleTime (500 μs). The gate control operation at a time corresponding to T00 begins to be repeatedly executed at a time corresponding to T02.

[0384] Note that in Example 2, whenever the gate control states corresponding to periodic service flows J and K are open, the first device does not indicate the order in which to transmit periodic service flows J and K; in other words, the order in which to transmit periodic service flows J and K is not determined. For example, the second device may transmit periodic service flow J first, or may transmit periodic service flow K first, and microbursts and microcongestions at the second device and at the transmitting nodes between the second device and the third device still do not occur. This is because the first device may configure the second device to ensure sufficient transmission time for periodic service flows J and K; in other words, the length of time the gate control state is open is sufficient. For the second device, regardless of whether periodic service flow J or periodic service flow K is transmitted first, the transmission of periodic service flows J and K can be completed within the length of time the gate control state is open. Similarly, for a transmitting node between the second device and the third device, regardless of whether periodic service flow J or periodic service flow K is received first, the fourth device may configure the transmitting node to reserve a fixed and sufficient length of time for which the gate control state is open to transmit the two periodic service flows, so that the transmission of periodic service flow J and periodic service flow K can be completed within the length of time for which the gate control state is open. The solution provided in this embodiment of the present application can ensure that the second device and the transmitting node between the second device and the third device reserve sufficient resources to transmit periodic service flow J and periodic service flow K, so that deterministic transmission times for periodic service flow J and periodic service flow K can be implemented.

[0385] In other words, in Example 2, the gate control scheduling parameters are used to implicitly indicate the service flow transmission times for service flows with the same priority, and the service flow transmission times conveyed by using the gate control scheduling parameters can be used to sequentially transmit multiple service flows in a transmission queue, and the time during which the gate control state is open is sufficient to ensure the completion of transmission of the multiple service flows, thereby implementing deterministic transmission and improving overall network performance.

[0386] Example 3: When multiple service flows with different priorities do not arrive simultaneously, the first device places the multiple service flows in different transmission queues. The first device may transmit the minimum offset, maximum offset, and priority of each of the multiple service flows to the fourth device. The fourth device may configure a different offset selection value for each service flow. For example, the interval between the offset selection values ​​of any two adjacently transmitted service flows in the offset selection values ​​corresponding separately to the multiple service flows, determined by the fourth device, is not smaller than the time length corresponding to the largest data packet of the service flow with a higher priority among the two service flows, thereby ensuring that the service flow with a higher priority is transmitted before the service flow with a lower priority and that congestion does not occur during the transmission of the multiple service flows. In addition, the offset selection value corresponding to each service flow is greater than or equal to the minimum offset corresponding to the service flow and less than or equal to the maximum offset corresponding to the service flow, satisfying the deterministic latency requirement corresponding separately to the multiple service flows. Furthermore, the first device may determine a service flow transmission time for each service flow based on the offset selection values ​​corresponding separately to the multiple service flows and transmit the service flow transmission time to the second device.

[0387] Additionally, the first device determines the AdminBaseTime based on the minimum value among the offset selection values ​​corresponding to the plurality of service flows separately, and determines the AdminCycleTime based on the least common multiple of the cycles corresponding to the plurality of service flows separately.

[0388] For example, periodic service flow J and periodic service flow K have different priorities, and the priority of periodic service flow J is higher than the priority of periodic service flow K. In other words, periodic service flow J has transmission priority over periodic service flow K. Both periodic service flow J and periodic service flow K are downlink service flows. EarliestTransmitOffset corresponds to the minimum offset, LatestTransmitOffset corresponds to the maximum offset, and TimeAwareOffset corresponds to the offset selection value. In the following example, LatestTransmitOffset is calculated in scheme A* for determining the maximum offset. It can be understood that LatestTransmitOffset can alternatively be calculated in scheme B* or scheme C*. This is merely an example and is not limited to this embodiment of the present application.

[0389] The parameters of periodic service flow J are as follows: <Maximum Burst Size in time> (indicating the time length corresponding to the transmission of the largest data packet of periodic service flow J) = (120 μs); Interval (indicating the cycle of periodic service flow J) = 400 μs; Jitter (denoting the jitter of periodic service flow J) = 0 μs (the jitter is 0 because there is no other service flow with the same priority as periodic service flow J); Processing time = 100 μs; and The offset of the arrival time of periodic service flow J relative to the reference time = 1600,000,000,000,120 μs.

[0390] Therefore, the EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of periodic service flow J can be calculated according to equations (11-4) and (13-1). EarliestTransmitOffset = offset of arrival time of periodic service flow J relative to the reference time + 100 μs + Jitter = 1600,000,000,000,220 μs; and LatestTransmitOffset = offset of the arrival time of periodic service flow J relative to the reference time + 400 - 120 - Jitter = 1600,000,000,000,400 μs.

[0391] The parameters of periodic service flow K are as follows: <Maximum Burst Size in time> (denotes the time length corresponding to the transmission of the largest data packet of periodic service flow K) = (80 μs time) Interval (indicating the cycle of periodic service flow K) = 800 μs; Jitter (denoting the jitter of periodic service flow K) = 0 μs; Processing time = 100 μs; and The offset of the arrival time of periodic service flow K relative to the reference time = 1600,000,000,000,100 μs.

[0392] Similarly, the EarliestTransmitOffset (corresponding to the smallest offset) and LatestTransmitOffset (corresponding to the largest offset) of periodic service flow K can be calculated according to equations (11-4) and (13-1). EarliestTransmitOffset = offset of arrival time of periodic service flow K relative to the reference time + 100 μs + Jitter = 1600,000,000,000,200 μs; and LatestTransmitOffset = offset of the arrival time of periodic service flow K relative to the reference time + 800 - 80 - Jitter = 1600,000,000,000,820 μs.

[0393] The first device sends the EarliestTransmitOffset and LatestTransmitOffset of periodic service flow J and the priority of periodic service flow J to the fourth device, and sends the EarliestTransmitOffset and LatestTransmitOffset of periodic service flow K and the priority of periodic service flow K to the fourth device. The fourth device determines a TimeAwareOffset (corresponding to the selected offset value) in the range from EarliestTransmitOffset to LatestTransmitOffset for each of periodic service flow J and periodic service flow K. The TimeAwareOffset (corresponding to the selected offset value) returned by the fourth device for periodic service flow J and periodic service flow K is assumed to be as follows: For periodic service flow J, TimeAwareOffset=1600,000,000,000,260 μs; and For periodic service flow K, TimeAwareOffset=1600,000,000,000,380 μs.

[0394] The difference between the TimeAwareOffset of periodic service flow K and the TimeAwareOffset of periodic service flow J is<Maximum Burst Size in time> Note that in this way, periodic service flow K and periodic service flow J can be transmitted in a staggered manner and congestion does not occur. Of course, the present application is not limited in this respect. The difference between the TimeAwareOffset of periodic service flow K and the TimeAwareOffset of periodic service flow J can alternatively be expressed as the TimeAwareOffset of flow K.<Maximum Burst Size in time> It could be bigger.

[0395] The first device may determine, based on the TimeAwareOffsets of the different flows, that the AdminBaseTime is 1600,000,000,000,260 μs (e.g., the smallest value among the TimeAwareOffsets of the different flows). The first device may further determine that the AdminCycleTime is 800 μs (i.e., the least common multiple of the Interval corresponding to periodic service flow J and the Interval corresponding to periodic service flow K), and may use the AdminCycleTime, the Interval corresponding to periodic service flow J and periodic service flow K, and the Interval corresponding to periodic service flow J and periodic service flow K to determine the AdminBaseTime.<Maximum Burst Size in time> Configure the AdminControlList based on the

[0396] Here, an explanation will be provided with reference to Figure 12D. For the queue in which periodic service flow J is located, the time length corresponding to the transmission of the largest data packet of periodic service flow J is 120 μs, so the time for which the gate state remains open in each cycle is 120 μs. In other words, after the gate state of the queue in which periodic service flow J is located is switched to open for 120 μs, the gate state of the queue in which periodic service flow J is located is switched to closed. In addition, the cycle of periodic service flow J is 400 μs. In other words, after the gate state of the queue in which periodic service flow J is located is switched to closed for 280 μs, the next cycle begins and the gate state of the queue in which periodic service flow J is located is again switched to open. Therefore, the AdminControlList of periodic service flow J contains the following: if GateState=Open, then TimeInterval=120μs (indicating that the gate state is switched to open for 120μs); if GateState=Closed, then TimeInterval=280μs (indicating that the gate state is switched to open for 280μs); if GateState=Open, then TimeInterval=120μs; if GateState=Closed, then TimeInterval=280μs.

[0397] For the queue in which periodic service flow K is located, the gate state of periodic service flow K is initially closed and is switched to open until the gate state of periodic service flow J is closed. Other principles are the same as for periodic service flow J. Therefore, the AdminControlList of periodic service flow K includes: if GateState=Closed, then TimeInterval=120 μs; if GateState=Open, then TimeInterval=80 μs; if GateState=Closed, then TimeInterval=720 μs; if GateState=Open, then TimeInterval=80 μs; if GateState=Closed, then TimeInterval=720 μs.

[0398] In addition to determining the AdminBaseTime, AdminCycleTime, the AdminControlList of periodic service flow J, and the AdminControlList of periodic service flow K, the first device also determines the service flow transmission time of periodic service flow J, i.e., AdminBaseTime, and determines the service flow transmission time of periodic service flow K. Specifically, it can be understood that the first device determines the time during which the gate state of periodic service flow K is open as the service flow transmission time of periodic service flow K based on the AdminBaseTime, the AdminControlList of periodic service flow J, and the AdminControlList of periodic service flow K.

[0399] After receiving the AdminBaseTime, AdminCycleTime, and AdminControlList of periodic service flow J and periodic service flow K, the second device may determine the service flow transmission times of periodic service flow K and periodic service flow J based on these parameters, OperBaseTime, OperCycleTime, and the OperControlList of periodic service flow J and periodic service flow K. For example: OperCycleTime=AdminCycleTime=800μs; OperBaseTime=AdminBaseTime=1600,000,000,000,260μs; and AdminControlList is the same as OperControlList.

[0400] An explanation is now provided with reference to Figure 12D: At a time offset corresponding to OperBaseTime, the queues in which periodic service flow J and periodic service flow K are located separately perform operations based on their respective OperControlLists.

[0401] For example, for periodic service flow J, at a time offset corresponding to 1600,000,000,000,260 μs, the gate state of the transmission queue for periodic service flow J is open. The length of time that the gate state is open is 120 μs. At a time offset corresponding to 1600,000,000,000,380 μs, the gate state of the transmission queue for periodic service flow J is closed. The length of time that the gate state is closed is 280 μs. At a time offset corresponding to 1600,000,000,000,660 μs, the gate state of the transmission queue for periodic service flow J is open again, entering the next cycle. The rest can be deduced by analogy.

[0402] For periodic service flow K, at a time offset corresponding to 1600,000,000,000,260 μs, the gate state of the transmission queue for periodic service flow K is closed. The length of time that the gate state is closed is 120 μs. At a time offset corresponding to 1600,000,000,000,380 μs, the gate state of the transmission queue for periodic service flow K is open. The length of time that the gate state is open is 80 μs. At a time offset corresponding to 1600,000,000,000,460 μs, the gate state of the transmission queue for periodic service flow K is closed again, entering the next cycle. The rest can be deduced by analogy.

[0403] As shown in FIG. 12E, because periodic service flow J and periodic service flow K have different priorities, periodic service flow J and periodic service flow K are transmitted separately in different transmission queues. For ease of explanation, assume that periodic service flow J is transmitted in transmission queue 1 and periodic service flow K is transmitted in transmission queue 0. At a time point corresponding to AdminBaseTime T00, the gate control state of transmission queue 1 corresponding to periodic service flow J is open, and the gate control state of transmission queue 0 corresponding to periodic service flow K is closed. In this case, the second device can transmit periodic service flow J, and the length of time that the gate control state of transmission queue 1 is open is 120 μs. The second device completes the transmission of periodic service flow J. At a time point corresponding to T01, the gate control state of the transmission queues changes: the gate control state of transmission queue 1 corresponding to periodic service flow J is closed, and the gate control state of transmission queue 0 corresponding to periodic service flow K is open. In this case, the second device may transmit periodic service flow K, and the length of time that the gate control state of transmission queue 0 is open is 80 μs. The second device completes the transmission of periodic service flow K. At a time corresponding to T02, the gate control states of the transmission queues change again: the gate control state of transmission queue 1 corresponding to periodic service flow J is closed, and the gate control state of transmission queue 0 corresponding to periodic service flow K is closed. This state continues for 200 μs until a time corresponding to T03. At a time corresponding to T03, the gate control state of transmission queue 1 corresponding to periodic service flow J is open, and the gate control state of transmission queue 0 corresponding to periodic service flow K is closed. In this case, the second device may transmit periodic service flow J, and the length of time that the gate control state is open is 120 μs. The second device completes the transmission of periodic service flow J. At time T04, the gate control states of the transmission queues change: the gate control state of transmission queue 1 corresponding to periodic service flow J is closed, and the gate control state of transmission queue 0 corresponding to periodic service flow K is closed. This state continues for 280 μs.The gate control operation from the time corresponding to T00 to the time corresponding to T05 corresponds to one cycle, i.e., OperCycleTime (800 μs). The gate control operation corresponding to the time corresponding to T00 starts repeating at the time corresponding to T05.

[0404] It should be noted that in Example 1, periodic service flow J and periodic service flow K have different priorities and arrive at the second device at different times, but the method provided in this embodiment of the present application can ensure that the higher-priority service flow is transmitted preferentially. Specifically, the priority of periodic service flow J is higher than the priority of periodic service flow K. According to the method provided in this embodiment of the present application, the gate control states and time lengths corresponding to the different transmission queues in which periodic service flow J and periodic service flow K are located are controlled. When periodic service flow K arrives at the second device earlier than periodic service flow J, periodic service flow J with higher priority can still be transmitted preferentially. This avoids a situation where, because periodic service flow K is being transmitted, it is necessary to wait until the transmission of periodic service flow K is completed before transmitting periodic service flow J.

[0405] In some embodiments, the first device may further transmit information used to determine the gated scheduling parameters to the second device, where the second device determines the gated scheduling parameters, where the information used to determine the gated scheduling parameters may include a cycle for each service flow, an offset selection value for each service flow, a time length corresponding to a maximum data packet corresponding to each service flow, and the like.

[0406] In addition, it should be further noted that in this embodiment of the present application, the fourth device is further configured to determine a forwarding path (specifically, a forwarding path from the second device to the third device) for the first service flow based on the user plane topology (including access network devices, user plane network elements, and transmitting nodes between the access network devices and the user plane network elements), the capability information of each transmitting node, and information about the first service flow sent by the first device, such as the minimum offset and maximum offset in the above embodiment; and to configure the transmitting nodes on the forwarding path, specifically, to send corresponding gate control scheduling parameters to each transmitting node. The gate control scheduling parameters here are gate control scheduling parameters for the transmitting nodes. For example, the AdminBaseTime in the gate control scheduling parameters of the next-hop transmitting node of the second device may be the AdminBaseTime in the gate control scheduling parameters of the second device plus the maximum transmission latency required from the second device to the next-hop transmitting node of the second device. The contents of other parameters are the same. The transmitting node may further transmit its capability information (used by the fourth device to configure a forwarding path for the service flow and determine corresponding gate control scheduling parameters) to the fourth device, and the transmitting node receiving the gate control scheduling parameters forwards the first service flow based on the received gate control scheduling parameters. How the fourth device determines a forwarding path for the first service flow and configures the transmitting nodes on the forwarding path is not limited in this application. Therefore, through the configuration of the second device and the transmitting nodes on the determined forwarding path from the second device to the third device, a deterministic transmission latency requirement between the second device and the third device can be ensured.

[0407] The following Figures 13 and 14 describe the transmission procedure of the first service flow with reference to the architectures shown in Figures 6A and 6B. In the examples of Figures 13 and 14, the SMF is configured to implement the functionality of the first device. In Figure 13, the first service flow is an uplink service flow, and the AN-TT is a device independently deployed outside the gNB, or the AN-TT is used as a functional module inside the gNB.

[0408] S1301: The SMF network element obtains the DS-TT and the residence time of the first service flow in the UE (UE-DS-TT-Residence Time) from the UE.

[0409] In addition, the SMF network element may further obtain parameters, such as the MAC address of the DS-TT port, which is not limited in this application. The DS-TT and the residence time of the first service flow in the UE (UE-DS-TT-Residence Time) may be carried in the PDU session establishment request message and sent by the UE to the SMF network element through the gNB and the AMF network element.

[0410] For details, please refer to the relevant explanation in Method 1. The overlapping parts will not be explained again.

[0411] S1302: The SMF network element acquires the processing time information of the AN-TT and the port information of the AN-TT.

[0412] For example, when the AN-TT is a device independently deployed outside the gNB, the SMF network element may obtain the processing time information of the AN-TT and the port information of the AN-TT from the AN-TT, or may obtain the processing time information of the AN-TT and the port information of the AN-TT from the gNB. In this case, the processing time information of the AN-TT and the port information of the AN-TT are sent to the gNB by the AN-TT or configured on the gNB.

[0413] For example, when the AN-TT is used as a functional module inside the gNB, the SMF network element may obtain the processing time information of the AN-TT and the port information of the AN-TT from the gNB. In this case, the processing time information of the AN-TT is also referred to as the processing time information of the gNB.

[0414] The port information of the AN-TT specifically includes an identifier of each port, where the identifier of each port includes the MAC address and interface name of each port. In addition, the port information of the AN-TT may include other parameters, which are not limited in the present application.

[0415] For example, the SMF network element may determine the processing time of the first service flow in the AN-TT based on the processing time information of the AN-TT. For specific content of the processing time information of the AN-TT, please refer to the relevant description of the processing time information of the second device in step 810.

[0416] S1303: The PCF network element sends the PCC rule to the SMF network element.

[0417] The PCC rule includes a TSC assistance container, which includes information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow. The PCC rule may further include a service requirement description parameter, which may include a maximum burst size. In addition, the TSC assistance container and the service requirement parameter may further include other parameters. For specific details, please refer to the related content in Scheme 1. Here, the information about the burst arrival time of the first service flow refers to information about the time when the first service flow arrives at the DS-TT.

[0418] Corresponding to FIG. 6A, the PCF network element may obtain information about the burst arrival time of the first service flow, the cycle of the first service flow, the direction of the first service flow, and service requirement description parameters from the TSN AF network element.

[0419] Corresponding to FIG. 6B, the PCF network element may obtain information about the burst arrival time of the first service flow, the cycle of the first service flow, the direction of the first service flow, and service requirement description parameters from the TSCTSF network element.

[0420] For example, the PCF network element may generate a PCC rule based on information about the burst arrival time of the first service flow, the cycle of the first service flow, the direction of the first service flow, and the service requirement description parameters obtained from the TSN AF network element or the TSCTSF network element, and send the PCC rule to the SMF network element, which associates the PCC rule with a QoS flow, where the QoS flow is the QoS flow corresponding to the first service flow.

[0421] In a 5GS system, the first service flow may be a service flow obtained through aggregation by a TSN AF or a TSCTSF. In other words, the TSN AF or the TSCTSF aggregates multiple service flows with the same or similar characteristics to obtain the first service flow.

[0422] S1304: The SMF network element determines the minimum offset and the maximum offset.

[0423] The minimum offset may also be referred to as the earliest offset, and the maximum offset may also be referred to as the latest offset. For example, an SMF network element determines TSpecTimeAware. The minimum offset corresponds to EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to LatestTransmitOffset in TSpecTimeAware. An example in which the minimum offset is EarliestTransmitOffset and the maximum offset is LatestTransmitOffset is used below for explanation purposes only.

[0424] (1) The SMF network element determines the EarliestTransmitOffset.

[0425] For example, the SMF network element may determine the EarliestTransmitOffset according to equation (11-3) or equation (12-2) based on the UE-DS-TT-Residence Time in S1301, the gNB's processing time information in S1302, information about the burst arrival time of the first service flow in the PCC rule in S1303, and PDB1 determined based on the PCC rule.

[0426] (2) The SMF network element determines the LatestTransmitOffset.

[0427] For example, the SMF network element may determine LatestTransmitOffset according to equation (13-2) or equation (14) based on the UE-DS-TT-Residence Time in S1301, information about the burst arrival time of the first service flow in the PCC rule in S1303, the cycle of the first service flow, the maximum burst size included in the service requirement description parameters, and PDB1 determined based on the PCC rule.

[0428] Alternatively, when the SMF network element acquires the maximum buffer time length of the first service flow in the AN-TT, the SMF network element may determine LatestTransmitOffset according to Equation (15-2) or Equation (16) based on the processing time information of the AN-TT in S1302, the maximum buffer time length of the first service flow in the AN-TT, the UE-DS-TT-Residence Time in S1301, information about the burst arrival time of the first service flow in the PCC rule in S1303, and the PDB1 determined based on the PCC rule. For information about the SMF network element acquiring the maximum buffer time length of the first service flow in the AN-TT, please refer to the description in the relevant paragraph above. Details will not be described again here. For example, in this case, the SMF network element also needs to acquire the processing time information of the UPF network element from the UPF network element.

[0429] Alternatively, the SMF network element may determine two values ​​of LatestTransmitOffset and then select the smaller value as LatestTransmitOffset.

[0430] It can be understood that when the AN-TT is used as a functional module inside the gNB, the SMF network element determines PDB1 based on the PCC rule. When the AN-TT is a device independently deployed outside the gNB, the SMF network element determines PDB1' based on the PCC rule, in other words, PDB1 is replaced with PDB1'.

[0431] S1305: The SMF network element sends the identifier (Stream ID), minimum offset, and maximum offset of the first service flow to the CNC-TN network element.

[0432] In addition, the SMF network element may further transmit at least one parameter to the CNC-TN network element: the priority (StreamRank) of the first service flow, the cycle of the first service flow, the maximum frame size, the maximum latency requirement between the AN-TT and the N3-TT network elements, and the port information of the AN-TT.

[0433] The maximum frame size is determined based on the maximum burst size. For the method of determining the maximum latency requirement between the AN-TT and N3-TT network elements, please refer to the relevant description in the embodiment of Figure 8. The details will not be described again here.

[0434] S1306: The CNC-TN network element determines an offset selection value based on the received minimum offset and maximum offset, and sends the identifier and interface configuration information of the first service flow to the SMF network element.

[0435] The interface configuration information may include an Interface ID and an offset selection value, where the Interface ID is used to identify the port indicated by the port information of the AN-TT in S1302.

[0436] The offset selection value is TimeAwareOffset, where TimeAwareOffset≧EarliestTransmitOffset and TimeAwareOffset≦LatestTransmitOffset.

[0437] S1307: The SMF network element determines gate control scheduling parameters based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0438] For example, the SMF network element determines the gate control scheduling parameters based on the offset selection value, the cycle and maximum burst size of the first service flow. For details, see Examples 1, 2 and 3, which are illustrated by using periodic service flow J and periodic service flow K. The details will not be repeated here.

[0439] S1308: The SMF network element sends gate control scheduling parameters.

[0440] When the AN-TT is a device independently deployed outside the gNB, the SMF network element transmits the gate control scheduling parameters to the AN-TT; or the SMF transmits the gate control scheduling parameters to the gNB, and the gNB transmits the gate control scheduling parameters to the AN-TT.

[0441] When the AN-TT is used as a functional module inside the gNB, the SMF network element sends the gate control scheduling parameters to the gNB, and the gNB notifies the AN-TT of the gate control scheduling parameters through the internal interface.

[0442] In addition, the SMF network element also sends an InterfaceID.

[0443] According to the above method, the SMF network element configures the gated scheduling parameters associated with the first service flow for the AN-TT, and the AN-TT transmits the service flow according to the configuration of the SMF network element, thereby avoiding congestion problems between the first service flow and another service flow. Therefore, the deterministic latency requirement of the first service flow is met, and low-latency transmission between the AN-TT and the N3-TT can be implemented, improving overall network performance.

[0444] In FIG. 14, the first service flow is a downlink service flow.

[0445] S1401: The SMF network element obtains the processing time information of the UPF network element and the port information of the N3-TT from the UPF network element.

[0446] The port information of the N3-TT specifically includes an identifier of each port, where the identifier of each port includes the MAC address and interface name of each port. In addition, the port information of the N3-TT may include other parameters, which are not limited in this application.

[0447] For example, the SMF network element may obtain the processing time information of the UPF network element from the UPF network element, and determine the processing time of the first service flow in the UPF network element based on the processing time information of the UPF network element. For specific content of the processing time information of the UPF network element, please refer to the relevant description of the processing time information of the second device in step 810. In addition, the manner of obtaining the processing time information of the UPF network element is similar to the manner of obtaining port information of the N3-TT. For details, please refer to the relevant description of the first device obtaining the processing time information of the user plane network element from the user plane network element in step 810. The overlapping parts will not be described again.

[0448] S1402: The PCF network element sends the PCC rule to the SMF network element.

[0449] For example, the PCC rule includes a TSC assistance container, which includes information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow. The PCC rule further includes a service requirement description parameter, which includes a maximum burst size. In addition, the TSC assistance container and the service requirement parameter may further include other parameters. For specific details, please refer to the related content in Scheme 1. The difference from S1303 is that the information about the burst arrival time of the first service flow here is information about the time when the first service flow arrives at the NW-TT.

[0450] S1403: The SMF network element determines the minimum offset and the maximum offset.

[0451] The minimum offset may also be referred to as the earliest offset, and the maximum offset may also be referred to as the latest offset. For example, an SMF network element determines TSpecTimeAware. The minimum offset corresponds to EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to LatestTransmitOffset in TSpecTimeAware. An example in which the minimum offset is EarliestTransmitOffset and the maximum offset is LatestTransmitOffset is used below for explanation purposes only.

[0452] (1) The SMF network element determines the EarliestTransmitOffset. For example, the SMF network element may determine the EarliestTransmitOffset according to equation (11-5) or equation (12-3) based on the processing time information of the UPF network element at S1401 and the information about the burst arrival time of the first service flow in the PCC rule at S1402.

[0453] (2) The SMF network element determines LatestTransmitOffset. For example, the SMF network element may determine LatestTransmitOffset according to equation (13-3) or equation (14) based on the information about the burst arrival time of the first service flow in the PCC rule at S1402, the cycle of the first service flow, and the maximum burst size included in the service requirement description parameters.

[0454] Alternatively, when the SMF network element determines the maximum buffer time length of the first service flow in the UPF network element, the SMF network element may determine LatestTransmitOffset according to Equation (15-3) or Equation (16) based on the processing time information of the UPF network element in S1401, the maximum buffer time length of the first service flow in the UPF, and information about the burst arrival time of the first service flow in the PCC rule in S1402. For the SMF network element obtaining the maximum buffer time length of the first service flow in the UPF network element, please refer to the description in the related paragraph above. Details will not be described again here. For example, in this case, the SMF network element also needs to obtain processing time information of the AN-TT.

[0455] Alternatively, the SMF network element may determine two values ​​of LatestTransmitOffset and then select the smaller value as LatestTransmitOffset.

[0456] S1404: The SMF network element sends the identifier, minimum offset, and maximum offset of the first service flow to the CNC-TN network element.

[0457] In addition, the SMF network element may further send at least one parameter to the CNC-TN network element: the priority of the first service flow, the cycle of the first service flow, the maximum frame size, the maximum latency requirement between the AN-TT and N3-TT network elements, and the port information of the N3-TT.

[0458] The maximum frame size is determined based on the maximum burst size. For the method of determining the maximum latency requirement between the AN-TT and N3-TT network elements, please refer to the relevant description in the embodiment of Figure 8. The details will not be described again here.

[0459] S1405: The CNC-TN network element determines an offset selection value based on the received minimum offset and maximum offset, and sends the identifier and interface configuration information of the first service flow to the SMF network element.

[0460] The interface configuration information may include an Interface ID and an offset selection value, and the Interface ID is used to identify the port of the N3-TT indicated by the port information of the N3-TT in S1401.

[0461] The offset selection value is TimeAwareOffset, where TimeAwareOffset≧EarliestTransmitOffset and TimeAwareOffset≦LatestTransmitOffset.

[0462] S1406: The SMF network element determines gate control scheduling parameters based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0463] For example, the SMF network element determines the gate control scheduling parameters based on the offset selection value, the cycle and maximum burst size of the first service flow. For details, see Examples 1, 2 and 3, which are illustrated by using periodic service flow J and periodic service flow K. The details will not be repeated here.

[0464] S1407: The SMF network element sends gate control scheduling parameters to the UPF network element.

[0465] The UPF network element may notify the gate control scheduling parameters to the N3-TT through an internal interface.

[0466] In addition, the SMF network element further sends the InterfaceID to the UPF network element, and the UPF network element notifies the InterfaceID to the N3-TT through the internal interface.

[0467] It may be understood that in the embodiments shown in Figures 13 and 14, the SMF network element may alternatively not determine the gated scheduling parameters but may transmit information used to determine the gated scheduling parameters, such as the transmission time of the first service flow or the offset of the transmission time of the first service flow relative to a reference time. The transmission time of the first service flow or the offset of the transmission time of the first service flow relative to a reference time may be determined based on the TimeAwareOffset. The information used to determine the gated scheduling parameters may include cycles corresponding separately to the multiple service flows, separate offset selection values ​​for the multiple service flows, time lengths corresponding to maximum data packets corresponding to the multiple service flows, priorities corresponding separately to the multiple service flows, and the like. The multiple service flows include the first service flow.

[0468] According to the above method, the SMF network element configures the gated scheduling parameters associated with the first service flow for the N3-TT, and the N3-TT transmits the service flow according to the SMF configuration, thereby avoiding congestion issues between the first service flow and another service flow. Therefore, the deterministic latency requirement of the first service flow is met, low-latency transmission between the AN-TT and the N3-TT can be implemented, and overall network performance can be improved.

[0469] 15A, 15B, and 16, the following describes a transmission procedure for the first service flow in the architecture shown in Figure 7A. In the examples of Figures 15A, 15B, and 16, the TSN AF network element is configured to implement the functionality of an SMF network element. In Figures 15A and 15B, the first service flow is an uplink service flow.

[0470] For S1501 and S1502, please refer to S1301 and S1302. The overlapping parts will not be explained again.

[0471] S1503: The SMF network element sends the information obtained in S1501 and S1502 to the TSN AF network element through the PCF network element.

[0472] For example, the processing time information of the AN-TT and the port information of the AN-TT may be encapsulated in a container, in other words, invisible to the SMF network element; or may not be encapsulated in a container, in which case the SMF network element may read the information.

[0473] S1504: The PCF network element sends the PCC rule to the SMF network element.

[0474] For details, see S1303.

[0475] S1505: The SMF network element determines, based on the PCC rule, either or both of a packet delay budget (PDB1) for transmitting the first service flow between the UE and the gNB and a packet delay budget (PDB2) for transmitting the first service flow between the gNB and the UPF network element.

[0476] S1506: The SMF network element sends, to the TSN AF network element through the PCF network element, either or both of a packet delay budget (PDB1) for transmitting the first service flow between the UE and the gNB and a packet delay budget (PDB2) for transmitting the first service flow between the gNB and the UPF network element. If the SMF sends only PDB2, the TSN AF network element further determines PDB1 based on PDB2.

[0477] In addition, the SMF network element may transmit to the TSN AF network element through the PCF network element the information obtained in S1501 and S1502 and either or both of the packet delay budget (PDB1) for transmitting the first service flow between the UE and the gNB and the packet delay budget (PDB2) for transmitting the first service flow between the gNB and the UPF network element, i.e., S1503 and S1506 may be combined into one step.

[0478] In addition, when the AN-TT is a device independently deployed outside the gNB, PDB1 and PDB2 are replaced with PDB1' and PDB2'.

[0479] S1507: The TSN AF network element determines the minimum offset and the maximum offset.

[0480] The method for determining the minimum offset and the maximum offset by the TSN AF network element may be the same as the method for determining the minimum offset and the maximum offset by the SMF network element. For details, see the related description in S1304.

[0481] S1508: The TSN AF network element sends the identifier, minimum offset, and maximum offset of the first service flow to the CNC-TN network element.

[0482] S1509: The TSN AF network element obtains the identifier and interface configuration information of the first service flow from the CNC-TN network element.

[0483] The interface configuration information may include an InterfaceID and an offset selection value, where the InterfaceID is used to identify the port in the port information of the AN-TT.

[0484] The offset selection value can be TimeAwareOffset, where TimeAwareOffset≧EarliestTransmitOffset and TimeAwareOffset≦LatestTransmitOffset.

[0485] S1510: The TSN AF network element determines gate control scheduling parameters based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0486] S1511: The TSN AF network element sends gate control scheduling parameters to the SMF network element through the PCF network element. In addition, the TSN AF network element may further send an Interface ID to the SMF network element through the PCF network element.

[0487] S1512: The SMF network element sends gate control scheduling parameters.

[0488] When the AN-TT is a device independently deployed outside the gNB, the SMF network element transmits the gate control scheduling parameters to the AN-TT; or the SMF transmits the gate control scheduling parameters to the gNB, and the gNB transmits the gate control scheduling parameters to the AN-TT.

[0489] When the AN-TT is used as a functional module inside the gNB, the SMF network element sends gate control scheduling parameters to the gNB.

[0490] In addition, the SMF network element also sends an InterfaceID.

[0491] According to the above method, the TSN AF network element configures a first gating scheduling parameter associated with a first service flow for the AN-TT through the SMF network element, and the AN-TT transmits the service flow according to the TSN AF configuration, thereby avoiding congestion problems between the first service flow and another service flow. Therefore, the deterministic latency requirement of the first service flow is met, and low-latency transmission between the AN-TT and the N3-TT can be implemented, thereby improving overall network performance.

[0492] In FIG. 16, the first service flow is a downlink service flow.

[0493] For S1601, please refer to S1401. The overlapping parts will not be explained again.

[0494] S1602: The SMF network element sends the information obtained in S1601 to the TSN AF network element through the PCF network element.

[0495] For example, the processing time information of the UPF network element and the port information of the N3-TT obtained from the UPF network element may be encapsulated in a container, in other words, invisible to the SMF network element; or may not be encapsulated in a container, in which case the SMF network element may read the information.

[0496] S1603: The TSN AF network element determines the minimum offset and the maximum offset.

[0497] For details, please refer to the related explanation of S1403.

[0498] S1604: The TSN AF network element sends the identifier, minimum offset, and maximum offset of the first service flow to the CNC-TN network element.

[0499] S1605: The TSN AF network element obtains the identifier and interface configuration information of the first service flow from the CNC-TN network element.

[0500] The interface configuration information may include an InterfaceID and an offset selection value, where the InterfaceID is used to identify an interface of a UPF network element or a port in the port information of an N3-TT.

[0501] The offset selection value can be TimeAwareOffset, where TimeAwareOffset≧EarliestTransmitOffset and TimeAwareOffset≦LatestTransmitOffset.

[0502] S1606: The TSN AF network element determines gate control scheduling parameters based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0503] S1607: The TSN AF network element sends gate control scheduling parameters to the SMF network element through the PCF network element.

[0504] In addition, the TSN AF network element further transmits the InterfaceID to the SMF network element through the PCF network element.

[0505] S1608: The SMF network element sends the gate control scheduling parameters to the UPF network element.

[0506] The UPF network element notifies the N3-TT of the gate control scheduling parameters.

[0507] In addition, the SMF network element sends the Interface ID to the UPF network element, and the UPF network element notifies the Interface ID to the N3-TT.

[0508] It may be understood that in the embodiments shown in Figures 15A, 15B, and 16, the TSN AF network element may alternatively not determine the gated scheduling parameters but may transmit information used to determine the gated scheduling parameters, such as the transmission time of the first service flow or the offset of the transmission time of the first service flow relative to a reference time. The transmission time of the first service flow or the offset of the transmission time of the first service flow relative to a reference time may be determined based on the TimeAwareOffset. The information used to determine the gated scheduling parameters may include cycles corresponding separately to the multiple service flows, separate offset selection values ​​for the multiple service flows, time lengths corresponding to maximum data packets corresponding to the multiple service flows, priorities corresponding separately to the multiple service flows, and the like. The multiple service flows include the first service flow.

[0509] According to the above method, the TSN AF network element configures a first gating scheduling parameter associated with a first service flow for the N3-TT through the SMF network element, and the N3-TT transmits the service flow according to the configuration of the TSN AF, thereby avoiding congestion problems between the first service flow and another service flow. Therefore, the deterministic latency requirement of the first service flow is met, and low-latency transmission between the AN-TT and the N3-TT can be implemented, thereby improving overall network performance.

[0510] It should be noted that the above embodiment can be applied to the architecture shown in FIG. 7B when the TSN AF network element in the embodiments shown in FIG. 15A, FIG. 15B and FIG. 16 is replaced with a TSCTSF network element.

[0511] In another embodiment, in addition to the network architectures in Figures 6A to 7B, a network architecture may also be shown in Figure 17. For Domain 1, please refer to the relevant descriptions of Figures 6A and 6B. In Domain 2, the user plane includes a gNB and a UPF network element in 5GS and a switch between the gNB and the UPF network element, and the control plane includes an element manager (EM) network element, a network manager (NM) network element, and a CNC-CN network element. In Figure 17, the NM network element may be configured to implement the functions of the first device in Domain 2.

[0512] The EM network element provides network element management functionality and manages one or more network elements.

[0513] The NM network element provides network management functionality and manages the network between the network elements managed by the EM.

[0514] 18A and 18B, the following describes the transmission procedure of the first service flow in the architecture shown in FIG.

[0515] S1801: The NM network element determines, according to network planning and service planning, the latency requirements of the transmission link between the AN-TT and the N3-TT and the flow characteristics obtained after flow aggregation.

[0516] For example, the flow characteristics obtained after flow aggregation include the cycle of the flow, the maximum number of data packets transmitted in a cycle, the maximum time length of a data packet, and the like.

[0517] Network planning means that the NM network element plans the data packet processing capabilities and data packet transmission capabilities of the AN-TT, N3-TT, and transmission nodes between the AN-TT and N3-TT network elements, the network topology between the AN-TT and N3-TT, and the like. Service planning means that the NM network element, in a phase before the network executes a service, obtains in advance multiple types of service flows that need to be transmitted between the AN-TT and N3-TT network elements, the latency requirements of each type of service flow, the characteristics (e.g., cycle or transmission time) of each type of service flow, and the like, determines one or more aggregate flows based on the characteristics of each type of service flow, and then determines the gate control scheduling parameters of the queues corresponding to each aggregate flow.

[0518] S1802: The NM network element further obtains the processing time information of the AN-TT, the port information of the AN-TT, the processing time information of the UPF network element, and the port information of the N3-TT.

[0519] The above information can be configured on the NM network element. Alternatively, when a gNB (where an AN-TT is deployed inside the gNB) or an AN-TT (deployed independently) is turned on, the processing time information of the AN-TT and the port information of the AN-TT are reported to the NM network element. Alternatively, when a UPF network element is turned on, the processing time information of the UPF network element and the port information of the N3-TT are reported to the NM network element.

[0520] S1803: The NM network element determines the minimum offset and the maximum offset based on the information acquired in S1801 and S1802. The NM network element may determine the minimum offset and the maximum offset based on the information acquired in the same processing manner as the SMF network element in Figure 13 or Figure 14, or the TSN AF network element in Figure 15A and Figure 15B or Figure 16. Details will not be described again here.

[0521] S1804: The NM network element sends the identifier, minimum offset, and maximum offset of the first service flow to the CNC-TN network element.

[0522] S1805: The CNC-TN network element sends the identifier and offset selection value of the first service flow to the NM network element.

[0523] When the first service flow is an uplink service flow, the interface configuration information includes an Interface ID and an offset selection value. The Interface ID is used to identify the port in the port information of the AN-TT.

[0524] When the first service flow is a downlink service flow, the interface configuration information includes an InterfaceID and an offset selection value, where the InterfaceID is used to identify the interface of the UPF network element or the port in the port information of the N3-TT.

[0525] S1806: The NM network element determines the gate control scheduling parameters based on the offset selection value returned by the CNC-TN network element.

[0526] S1807A: When the first service flow is an uplink service flow, the NM network element sends gate control scheduling parameters through the EM network element.

[0527] S1807B: When the first service flow is a downlink service flow, the NM network element sends gate control scheduling parameters through the EM network element.

[0528] According to the above method, the NM network element can first pre-determine gate control scheduling parameters according to network planning and service planning, and send the gate control scheduling parameters to the AN-TT or N3-TT network element, so that the deterministic latency requirements of the first service flow can be met and low latency transmission between the AN-TT and N3-TT network elements can be implemented.

[0529] 19 is a possible exemplary block diagram of an apparatus according to an embodiment of the present application. The apparatus 1900 includes a transceiving module 1910 and a processing module 1920. The transceiving module 1910 may include a receiving unit and a transmitting unit. The processing module 1920 is configured to control and manage actions of the apparatus 1900. The transceiving module 1910 is configured to support the apparatus 1900 in communication with another network entity. Optionally, the apparatus 1900 may further include a storage unit, configured to store program codes and data of the apparatus 1900.

[0530] Optionally, each module in the apparatus 1900 may be implemented by using software.

[0531] Optionally, the processing module 1920 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing module may implement or execute various exemplary logic blocks, modules, and circuits described with reference to the contents disclosed in the embodiments of the present application. A processor may alternatively be a combination of processors that implement computing functions, such as a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The transceiver module 1910 may be a communications interface, a transceiver, a transceiver circuit, or the like. The communications interface is a general term. In a specific implementation, the communications interface may include multiple interfaces, and the storage unit may be a memory.

[0532] When the apparatus 1900 is a first device or a chip in the first device, the processing module 1920 in the apparatus 1900 may support the apparatus 1900 to perform the actions of the first device in the above method examples, for example, may support the apparatus 1900 to perform steps 800 and 810 in FIG. 8, S1304 and S1307 in FIG. 13, S1403 and S1406 in FIG. 14, S1507 and S1510 in FIGS. 15A and 15B, S1603 and S1606 in FIG. 16, and S1801, S1802, S1803, and S1806 in FIGS. 18A and 18B.

[0533] The transceiver module 1910 may support communication between the apparatus 1900 and a second or third device. For example, the transceiver module 1910 may support the apparatus 1900 in performing step 820 in Figure 8, S1301, S1302, S1303, S1305, S1306, and S1308 in Figure 13, S1401, S1402, S1404, S1405, and S1407 in Figure 14, S1503, S1506, S1508, S1509, and S1511 in Figures 15A and 15B, S1602, S1604, S1605, and S1607 in Figure 16, and S1804, S1805, S1807A, and S1807B in Figures 18A and 18B.

[0534] An example is provided below.

[0535] In an implementation, the processing module 1920 is configured to determine information about a service flow arrival time, where the information about the service flow arrival time includes a service flow arrival time or an offset of the service flow arrival time relative to a reference time, where the service flow arrival time is a time when a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted by the second device between an access network device and a user plane network element; the processing module 1920 is configured to determine information about a service flow transmission time based on the information about the service flow arrival time; and the transceiver module 1910 is configured to instruct the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0536] In a possible design, when instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow, the transceiver module 1910 is configured to transmit information about the service flow transmission time to the second device.

[0537] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time does not exceed a maximum offset, the maximum offset being determined based on information about the offset of the service flow arrival time relative to the reference time, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on information about the offset of the service flow arrival time relative to the reference time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0538] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0539] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0540] In a possible design, a service flow transmission time determined by the first device at which the second device transmits the second service flow is different from a service flow transmission time determined by the first device at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0541] In a possible design, when determining information about a service flow transmission time based on information about the service flow arrival time, processing module 1920 is configured to: obtain an offset selection value, where the offset selection value is greater than or equal to a minimum offset and less than or equal to a maximum offset, or the offset selection value is greater than or equal to an offset of the earliest transmission time relative to a reference time and less than or equal to an offset of the latest transmission time relative to the reference time; and determine the information about the service flow transmission time based on the offset selection value.

[0542] In a possible design, the transceiver module 1910 is configured to transmit to the fourth device a minimum offset and a maximum offset, or an offset of the earliest transmission time relative to a reference time and an offset of the latest transmission time relative to the reference time; and to receive an offset selection value from the fourth device.

[0543] In one possible design, the processing module 1920 is further configured to determine a latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, a processing time for the first service flow at the second device, and a processing time for the first service flow at the third device; and the transceiver module 1910 is further configured to send the latency requirement to a fourth device. The third device is a device for receiving the first service flow, and if the first service flow is an uplink service flow, the third device is a user plane network element, or if the first service flow is a downlink service flow, the third device is an access network device or a translator corresponding to an access network device.

[0544] In a possible design, when determining information about the service flow transmission time based on the offset selection value, the processing module 1920 is configured to determine information about the service flow transmission time based on the offset selection value and a jitter latency associated with the first service flow.

[0545] In one possible design, the information about the service flow transmission time includes a gated scheduling parameter. The processing module 1920 is configured to: obtain a cycle of the first service flow and a maximum burst size of the first service flow; determine a maximum frame size of the first service flow based on the maximum burst size of the first service flow; and determine the gated scheduling parameter based on the cycle of the first service flow, the maximum frame size of the first service flow, and the selected offset value.

[0546] In a possible design, when the second device is an access network device and the third device is a user plane network element, the first service flow arrives at the second device through the terminal device. When determining the information about the service flow arrival time, the processing module 1920 is configured to: obtain information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determine the information about the service flow arrival time based on the information about the time the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0547] In a possible design, the first device is a time-sensitive networking TSN application function network element. When obtaining information about a time at which the first service flow arrives at the translator on the terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device, the processing module 1920 is configured to determine the information about the time at which the first service flow arrives at the translator on the terminal device side. The transceiver unit is configured to receive, from the session management network element, the residence time of the first service flow at the terminal device and the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0548] In one possible design, the first device is a session management network element. When information about the arrival time of the first service flow at the translator on the terminal device side, the residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device are obtained, the transceiver module 1910 is configured to receive, from the policy control network element, the information about the arrival time of the first service flow at the translator on the terminal device side; and receive, from the terminal device, the residence time of the first service flow at the terminal device and the translator on the terminal device side. The processing module 1920 is configured to determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.

[0549] It should be understood that the apparatus 1900 in this embodiment of the present application may correspond to the first device in the above-mentioned method embodiment, and the operations and / or functions of the modules in the apparatus 1900 can be separately used to implement corresponding steps of the method of the first device in the above-mentioned method embodiment. Therefore, the beneficial effects in the above-mentioned method embodiment can also be implemented. For the sake of brevity, the details will not be described again here.

[0550] When the apparatus 1900 is a second device or a chip of a second device, the processing module 1920 in the apparatus 1900 may support the apparatus 1900 in performing the actions of the second device in the above method examples.

[0551] The transceiver module 1910 may support communication between the apparatus 1900 and the first device or the third device. For example, the transceiver module 1910 may support the apparatus 1900 to perform step 820 in Figure 8, S1302 and S1308 in Figure 13, S1401 and S1407 in Figure 14, S1502 and S1512 in Figures 15A and 15B, S1601 and S1608 in Figure 16, and S1807A and S1807B in Figures 18A and 18B.

[0552] For example, in an implementation, the transceiver module 1910 is configured to: receive a first service flow, where the first service flow is a periodic service flow transmitted by a second device between an access network device and a user plane network element; and receive information about a service flow transmission time from the first device; the processing module 1920 is configured to wait until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow to the third device. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0553] In possible designs, the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time, where the service flow transmission time is no later than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device. Alternatively, the offset of the service flow transmission time relative to the reference time is no more than a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, the cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time for the first service flow at the second device, and a maximum buffer length for the first service flow at the second device.

[0554] In a possible design, the service flow transmit time is no earlier than the earliest transmit time, where the earliest transmit time is determined based on the service flow arrival time and information about the processing time of the first service flow at the second device. Alternatively, the offset of the service flow transmit time relative to the reference time is greater than or equal to a minimum offset, where the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

[0555] In a possible design, the parameters for determining the latest transmit time, maximum offset, earliest transmit time, or minimum offset further include a jitter latency associated with the first service flow.

[0556] In a possible design, the service flow transmission time at which the second device transmits the second service flow is different from the service flow transmission time at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or the difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.

[0557] In a possible design, the information about the service flow transmission times includes gate control scheduling parameters.

[0558] In a possible design, the first device is a TSN application function network element, or the first device is a session management network element.

[0559] It should be understood that the apparatus 1900 in this embodiment of the present application may correspond to the second device in the above-mentioned method embodiment, and the operations and / or functions of the modules in the apparatus 1900 can be separately used to implement corresponding steps of the method of the second device in the above-mentioned method embodiment. Therefore, the beneficial effects in the above-mentioned method embodiment can also be implemented. For the sake of brevity, the details will not be described again here.

[0560] 20 is a schematic diagram of the structure of a communication device 2000 according to an embodiment of the present application. As shown in FIG. 20, the device 2000 includes a processor 2001.

[0561] When the apparatus 2000 is a first device or a chip in the first device, in a possible implementation, the processor 2001 is configured to invoke an interface to perform the following actions: determine information about a service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, where the service flow arrival time is the time when the first service flow arrives at the second device, and the first service flow is a periodic service flow transmitted by the second device between the access network device and a user plane network element; determine information about a service flow transmission time based on the information about the service flow arrival time; and instruct the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0562] It should be understood that the apparatus 2000 may be further configured to perform other steps and / or operations on the first device side in the above embodiments, and for the sake of brevity, the details will not be described again here.

[0563] When the apparatus 2000 is a second device or a chip in the second device, in a possible implementation, the processor 2001 is configured to invoke an interface to perform the following actions: receive a first service flow, where the first service flow is a periodic service flow transmitted by the second device between an access network device and a user plane network element; and wait until a service flow transmission time indicated by the information about the service flow transmission time, and then transmit the first service flow to a third device. If the first service flow is an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is a user plane network element.

[0564] It should be understood that the apparatus 2000 may be further configured to perform other steps and / or operations on the second device side in the above embodiments, and for the sake of brevity, the details will not be described again here.

[0565] It should be understood that the processor 2001 may invoke an interface to perform the above receiving and transmitting actions. The invoked interface may be a logical interface or a physical interface. This is not limited thereto. Optionally, the physical interface may be implemented by using a transceiver. Optionally, the apparatus 2000 further includes a transceiver 2003.

[0566] Optionally, the apparatus 2000 further includes a memory 2002, which may store program codes in the above-mentioned method embodiments, so that the processor 2001 invokes the program codes.

[0567] Specifically, when the device 2000 includes a processor 2001, a memory 2002, and a transceiver 2003, the processor 2001, the memory 2002, and the transceiver 2003 communicate with each other through internal connection paths to transmit control signals and / or data signals. In a possible design, the processor 2001, the memory 2002, and the transceiver 2003 may be implemented by using chips. The processor 2001, the memory 2002, and the transceiver 2003 may be implemented on the same chip or on different chips, or the functions of any two of the processor 2001, the memory 2002, and the transceiver 2003 may be combined and implemented on one chip. The memory 2002 may store program code, and the processor 2001 invokes the program code stored in the memory 2002 to implement the corresponding functions of the device 2000.

[0568] The methods disclosed in the embodiments of the present application may be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In the implementation process, each step of the above-described method embodiments may be implemented by using a hardware integrated logic circuit in the processor or by using instructions in software form. The processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, or a system on a chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or another integrated chip. The processor may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present application may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware and software modules in the decoding processor.The software module may be located in a storage medium that is mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads information in the memory and completes the steps of the method in combination with the hardware of the processor.

[0569] It may be understood that the memory in the embodiments of the present application may be volatile memory or nonvolatile memory, or may include volatile memory and nonvolatile memory. Nonvolatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) and is used as an external cache. By way of example and not limitation, many forms of RAM may be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchlink dynamic random access memory (SLDRAM), and direct rambus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0570] It should be understood that in the embodiments of the present application, the numbers "first," "second," and the like are merely intended to distinguish different objects, for example, to distinguish different parameter information or messages, and do not constitute a limitation on the scope of the embodiments of the present application, and the embodiments of the present application are not limited thereto.

[0571] It should be further understood that the sequence numbers of the above processes do not mean the order of execution in the embodiments of the present application. The order of execution of the processes should be determined based on the functions and internal logic of the processes. The numbers or sequence numbers in the above processes are merely for distinguishing and facilitating description, and should not constitute any limitations on the implementation process of the embodiments of the present application.

[0572] It should be further understood that the term "and / or" herein simply describes a correspondence between related objects and represents three possible relationships. For example, A and / or B may represent three cases: when only A is present, when both A and B are present, and when only B is present. Additionally, the symbol " / " herein generally indicates an "or" relationship between multiple related objects.

[0573] Unless otherwise specified, expressions used in this application similar to the expression "an item includes one or more of the following: A, B, and C" generally mean that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A, and A; A, A, and B; A, A, and C; A, B, and B; A, C, and C; B and B; B, B, and B; B, B, and C; C and C; C, C, and C; and another combination of A, B, and C. In the above description, three elements A, B, and C are used as an example to explain the optional case of an item. When the expression "an item includes at least one of the following: A, B, ..., and X" is used, in other words, when more elements are included in the expression, the item, if applicable, can also be obtained according to the above rules.

[0574] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the units and algorithm steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to go beyond the scope of this application.

[0575] For the purpose of simple and concise description, for the detailed operation processes of the aforementioned systems, devices and units, please refer to the corresponding processes in the above-mentioned method embodiments, which can be clearly understood by those skilled in the art, and the details will not be described again here.

[0576] In some embodiments provided herein, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into multiple units is merely a logical division of functionality, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. Furthermore, the shown or described interconnections or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0577] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, i.e., located in one location or distributed across multiple network units, some or all of which may be selected based on actual requirements for realizing the objectives of the solutions of the embodiments.

[0578] Additionally, each functional unit in an embodiment of the present application may be integrated into one processing unit, and each of these units may exist physically alone, or two or more units may be integrated into one unit.

[0579] When these functions are implemented in the form of software functional units and sold or used as independent products, the functions may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application may essentially be implemented in the form of a software product, or a portion of the technical solutions may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or a compact disk. (Other possible items) [Item 1] 1. A communication method comprising: a first device determining information about a service flow arrival time, wherein the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; the first device determining information about a service flow transmission time based on the information about the service flow arrival time; and the first device instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow; wherein: If the first service flow is an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is the user plane network element. method. [Item 2] The step of instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow, by the first device, includes: the first device transmitting the information about the service flow transmission time to the second device. Item 1. The method according to item 1, comprising: [Item 3] 3. The method of claim 1, wherein a service flow transmit time determined by the first device for transmitting the second service flow by the second device is different from the service flow transmit time determined by the first device for transmitting the first service flow by the second device, the second service flow is a periodic service flow transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or a difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold. [Item 4] the information about the service flow transmission time includes a service flow transmission time or an offset of the service flow transmission time relative to the reference time; the service flow transmission time is not slower than a slowest transmission time, the slowest transmission time being determined based on the information about the service flow arrival times, the cycle of the first service flow, and the maximum burst size of the first service flow, and / or the slowest transmission time being determined based on the information about the service flow arrival times, the processing time of the first service flow at the second device, and the maximum buffer time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time does not exceed a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time of the first service flow at the second device, and a maximum buffer time length of the first service flow at the second device; 4. The method according to any one of items 1 to 3. [Item 5] the service flow transmission time is no earlier than an earliest transmission time, the earliest transmission time being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time is greater than or equal to a minimum offset, the minimum offset being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device. The method according to item 4. [Item 6] 6. The method of claim 5, wherein the parameters for determining the latest transmission time, the maximum offset, the earliest transmission time, or the minimum offset further include a jitter latency associated with the first service flow. [Item 7] The step of the first device determining information about a service flow transmission time based on the information about the service flow arrival time comprises: the first device obtaining an offset selection value, wherein the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset, or the offset selection value is greater than or equal to the offset of the earliest transmission time relative to the reference time and less than or equal to the offset of the latest transmission time relative to the reference time; and the first device determining the information about the service flow transmission time based on the offset selection value. 7. The method according to any one of items 4 to 6, comprising: [Item 8] The step of the first device obtaining an offset selection value comprises: the first device transmitting the minimum offset and the maximum offset, or the offset of the earliest transmission time relative to the reference time and the offset of the latest transmission time relative to the reference time, to a fourth device; and the first device receiving the offset selection value from the fourth device; Item 7. The method according to item 7, comprising: [Item 9] The step of the first device obtaining an offset selection value further comprises: determining, by the first device, a latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, the processing time of the first service flow at the second device, and the processing time of the first service flow at the third device, wherein the third device is a device for receiving the first service flow, and if the first service flow is an uplink service flow, the third device is the user plane network element, or if the first service flow is a downlink service flow, the third device is the access network device or the translator corresponding to the access network device; and the first device transmitting the latency requirement to the fourth device. Item 9. The method according to item 8, comprising: [Item 10] The step of the first device determining the information about the service flow transmission time based on the offset selection value includes: the first device determining the information about the service flow transmission time based on the offset selection value and the jitter latency associated with the first service flow. 10. The method according to any one of items 7 to 9, comprising: [Item 11] The information about the service flow transmission time includes gated control scheduling parameters; The method further comprises: the first device obtaining the cycle of the first service flow and the maximum burst size of the first service flow; the first device determining a maximum frame size for the first service flow based on the maximum burst size for the first service flow; and the first device determining the gate control scheduling parameters based on the cycle of the first service flow, the size of the largest frame of the first service flow, and the offset selection value. 11. The method according to any one of items 7 to 10, comprising: [Item 12] When the first service flow is an uplink service flow, The step of the first device determining information about service flow arrival times comprises: The first device obtains information about the arrival time of the first service flow at a translator on a terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determining, by the first device, the information about the time at which the first service flow arrives at the translator at the terminal device, the residence time of the first service flow at the terminal device and at the translator at the terminal device, and the packet delay budget for transmitting the first service flow between the terminal device and the second device; 12. The method according to any one of items 1 to 11, comprising: [Item 13] the first device is a time-sensitive networking TSN application function network element; The step of the first device obtaining information about the arrival time of the first service flow at a translator on a terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device includes: the first device determining the information about the time at which the first service flow arrives at the translator at the terminal device; and the first device receiving from a session management network element the residence time of the first service flow at the terminal device and the translator at the terminal device, and the packet delay budget for transmitting the first service flow between the terminal device and the second device. Item 13. The method according to item 12, comprising: [Item 14] the first device is a session management network element; The step of the first device obtaining information about the arrival time of the first service flow at a translator on a terminal device side, a residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device includes: receiving, by the first device, from a policy control network element, the information about the time at which the first service flow arrives at the translator at the terminal device; receiving, by the first device, from the terminal device, the residence time of the first service flow at the terminal device and at the translator at the terminal device; and the first device determining the packet delay budget for transmitting the first service flow between the terminal device and the second device; Item 13. The method according to item 12, comprising: [Item 15] 1. A communication method comprising: receiving, by a second device, a first service flow, wherein the first service flow is a periodic service flow to be transmitted between an access network device and a user plane network element; receiving, by the second device, information about service flow transmission times from the first device; and the second device waiting until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. wherein: If the first service flow is an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is the user plane network element. method. [Item 16] a service flow transmit time at which the second device transmits the second service flow is different from the service flow transmit time at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or a difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold; Item 15. The method according to item 15. [Item 17] The information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time; the service flow transmission time is not slower than a slowest transmission time, the slowest transmission time being determined based on information about service flow arrival times, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the slowest transmission time being determined based on the information about service flow arrival times, a processing time of the first service flow at the second device, and a maximum buffer length of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time does not exceed a maximum offset, the maximum offset being determined based on information about service flow arrival times, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about service flow arrival times, a processing time of the first service flow at the second device, and a maximum buffer time length of the first service flow at the second device; Item 17. The method according to item 15 or 16. [Item 18] the service flow transmission time is no earlier than an earliest transmission time, the earliest transmission time being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time is greater than or equal to a mini...

Claims

1. 1. A communication method comprising: a first device determining information about a service flow arrival time, wherein the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; the first device determining information about a service flow transmission time based on the information about the service flow arrival time; and the first device instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow; wherein: If the first service flow is an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is the user plane network element. method.

2. When the first service flow is an uplink service flow, The step of the first device determining information about service flow arrival times comprises: The first device obtains information about the arrival time of the first service flow at a translator on the terminal device side, the residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determining, by the first device, the information about the time at which the first service flow arrives at the translator at the terminal device, the residence time of the first service flow at the terminal device and at the translator at the terminal device, and the packet delay budget for transmitting the first service flow between the terminal device and the second device; The method of claim 1 , comprising:

3. the first device is a session management network element; The step of the first device obtaining information about the arrival time of the first service flow at a translator on a terminal device side, the residence time of the first service flow at the terminal device and the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device includes: receiving, by the first device, the information about the time at which the first service flow arrives at the translator at the terminal device from a policy control network element; receiving, by the first device, from the terminal device, the residence time of the first service flow at the terminal device and at the translator at the terminal device; and The first device determines the packet delay budget for transmitting the first service flow between the terminal device and the second device. The method of claim 2 , comprising:

4. The step of the first device instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow includes: the first device transmitting the information about the service flow transmission time to the second device. The method of claim 1 , comprising:

5. 2. The method of claim 1, wherein a service flow transmit time determined by the first device for the second device to transmit a second service flow is different from the service flow transmit time determined by the first device for the second device to transmit the first service flow, the second service flow is a periodic service flow transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or a difference between a time at which the second service flow arrives at the second device and a time at which the first service flow arrives at the second device is less than or equal to a threshold.

6. the information about the service flow transmission time includes a service flow transmission time or an offset of the service flow transmission time relative to the reference time; the service flow transmission time is not slower than a latest transmission time, the latest transmission time being determined based on the information about the service flow arrival times, the cycle of the first service flow, and the maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about the service flow arrival times, the processing time of the first service flow at the second device, and the maximum buffer time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time does not exceed a maximum offset, the maximum offset being determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about the service flow arrival time, a processing time of the first service flow at the second device, and a maximum buffer time length of the first service flow at the second device. The method of claim 1.

7. the service flow transmission time is no earlier than an earliest transmission time, the earliest transmission time being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time is greater than or equal to a minimum offset, the minimum offset being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device. The method of claim 6.

8. 8. The method of claim 7, wherein parameters for determining the latest transmission time, the maximum offset, the earliest transmission time, or the minimum offset further comprise a jitter latency associated with the first service flow.

9. The step of the first device determining information about a service flow transmission time based on the information about the service flow arrival time comprises: the first device obtaining an offset selection value, wherein the offset selection value is greater than or equal to a minimum offset and less than or equal to the maximum offset, or the offset selection value is greater than or equal to an offset of the earliest transmission time relative to the reference time and less than or equal to an offset of the latest transmission time relative to the reference time; and the first device determining the information about the service flow transmission time based on the offset selection value. The method of claim 6, comprising:

10. The step of the first device obtaining an offset selection value comprises: the first device transmitting the minimum offset and the maximum offset, or the offset of the earliest transmission time relative to the reference time and the offset of the latest transmission time relative to the reference time, to a fourth device; and the first device receiving the offset selection value from the fourth device; 10. The method of claim 9, comprising:

11. The step of the first device obtaining an offset selection value further comprises: determining, by the first device, a latency requirement for transmitting the first service flow between the second device and the third device based on a packet delay budget for transmitting the first service flow between the second device and the third device, the processing time of the first service flow at the second device, and the processing time of the first service flow at the third device, wherein the third device is a device for receiving the first service flow, and if the first service flow is an uplink service flow, the third device is the user plane network element, or if the first service flow is a downlink service flow, the third device is the access network device or the translator corresponding to the access network device; and the first device transmitting the latency requirement to the fourth device. The method of claim 10, comprising:

12. The step of the first device determining the information about the service flow transmission time based on the offset selection value includes: the first device determining the information about the service flow transmission time based on the offset selection value and a jitter latency associated with the first service flow.

10. The method of claim 9, comprising:

13. the information about the service flow transmission time includes gated control scheduling parameters; The method further comprises: the first device obtaining the cycle of the first service flow and the maximum burst size of the first service flow; the first device determining a maximum frame size for the first service flow based on the maximum burst size for the first service flow; and the first device determining the gated scheduling parameters based on the cycle of the first service flow, the size of the largest frame of the first service flow, and the offset selection value. The method of claim 9 comprising:

14. A communication method, comprising: a first device determining information about a service flow arrival time, wherein the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; the first device determining information about a service flow transmission time based on the information about the service flow arrival time; and the first device instructing the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow; wherein: If the first service flow is an uplink service flow, the second device is a time-sensitive networking (TSN) translator corresponding to the access network device when the 5G network functions as a TSN bridge; or if the first service flow is a downlink service flow, the second device is the user plane network element, and the user plane network element is a user plane function (UPF) having the functionality of an N3 interface translator (N3-TT). method.

15. 1. A communication method comprising: receiving a first service flow by a second device, where the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; receiving, by the second device, information about service flow transmission times from the first device; and the second device waiting until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. wherein: If the first service flow is an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is the user plane network element. method.

16. The method of claim 15 , wherein the first device is a session management network element.

17. a service flow transmit time at which the second device transmits the second service flow is different from the service flow transmit time at which the second device transmits the first service flow, the second service flow is a periodic service flow transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device simultaneously, or a difference between the time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold; 16. The method of claim 15.

18. the information about the service flow transmission time includes the service flow transmission time or an offset of the service flow transmission time relative to a reference time; the service flow transmission time is not slower than a latest transmission time, the latest transmission time being determined based on information about service flow arrival times, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the latest transmission time being determined based on the information about service flow arrival times, a processing time of the first service flow at the second device, and a maximum buffer time length of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time does not exceed a maximum offset, the maximum offset being determined based on information about service flow arrival times, a cycle of the first service flow, and a maximum burst size of the first service flow, and / or the maximum offset being determined based on the information about service flow arrival times, a processing time of the first service flow at the second device, and a maximum buffer time length of the first service flow at the second device.

16. The method of claim 15.

19. the service flow transmission time is no earlier than an earliest transmission time, the earliest transmission time being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device; or the offset of the service flow transmission time relative to the reference time is greater than or equal to a minimum offset, the minimum offset being determined based on the information about the service flow arrival time and the processing time of the first service flow at the second device.

20. The method of claim 18.

20. 20. The method of claim 19, wherein parameters for determining the latest transmit time, the maximum offset, the earliest transmit time, or the minimum offset further include a jitter latency associated with the first service flow.

21. The method of claim 16, wherein the information about the service flow transmission time includes gated scheduling parameters.

22. A communication method comprising: receiving a first service flow by a second device, where the first service flow is a periodic service flow transmitted between an access network device and a user plane network element; receiving, by the second device, information about service flow transmission times from the first device; and the second device waiting until the service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. wherein: If the first service flow is an uplink service flow, the second device is a time-sensitive networking (TSN) translator corresponding to the access network device when the 5G network functions as a TSN bridge; or if the first service flow is a downlink service flow, the second device is the user plane network element, and the user plane network element is a user plane function (UPF) having the functionality of an N3 interface translator (N3-TT). method.

23. 1. A communication method comprising: determining, by the first device, information about a service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time at which a first service flow arrives at a second device, and the first service flow being a periodic service flow transmitted between an access network device and a user plane network element; determining, by the first device, information about a service flow transmission time based on the information about the service flow arrival time; instructing, by the first device, the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow; receiving, by the second device, the first service flow; receiving, by the second device, the information about service flow transmission times from the first device; and and waiting, by the second device, until a service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. Equipped with If the first service flow is an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or if the first service flow is a downlink service flow, the second device is the user plane network element. method.

24. A communication method comprising: determining, by the first device, information about a service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to a reference time, the service flow arrival time being a time at which a first service flow arrives at a second device, and the first service flow being a periodic service flow transmitted between an access network device and a user plane network element; determining, by the first device, information about a service flow transmission time based on the information about the service flow arrival time; instructing, by the first device, the second device to wait until the service flow transmission time after receiving the first service flow and then transmit the first service flow; receiving, by the second device, the first service flow; receiving, by the second device, the information about service flow transmission times from the first device; and and waiting, by the second device, until a service flow transmission time indicated by the information about the service flow transmission time before transmitting the first service flow. Equipped with If the first service flow is an uplink service flow, the second device is a time-sensitive networking (TSN) translator corresponding to the access network device when the 5G network functions as a TSN bridge; or if the first service flow is a downlink service flow, the second device is the user plane network element, and the user plane network element is a user plane function (UPF) having the functionality of an N3 interface translator (N3-TT). method.

25. A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to: receive signals from a communication device other than the communication device, transmit the signals to the processor, or transmit signals from the processor to a communication device other than the communication device; and the processor is configured to implement a method according to any one of claims 1 to 14 by using logic circuits or by executing code instructions.

26. A communication device comprising a processor and an interface circuit, wherein the interface circuit is configured to: receive signals from a communication device other than the communication device, transmit the signals to the processor, or transmit signals from the processor to a communication device other than the communication device; and wherein the processor is configured to implement a method according to any one of claims 15 to 22 by using logic circuits or by executing code instructions.

27. A communication system comprising a first device that is a communication device according to claim 25 and a second device that is a communication device according to claim 26.

28. A computer program product which, when executed by a communication device, implements the method of any one of claims 1 to 14 or claims 15 to 22.

Images